print problem

jemoore23 · Post by **jemoore23** » Wed Nov 19, 2003 7:36 pm

I am having a printing problem with Textpad 4.7.2. I am using a IBM T30 laptop with Win 2000 with the latest service pack. Whenever I click on the file>print option, I do not get the standard print pop-up, instead I get a box that says: "Program Error" in the title bar. The body says: "Textpad.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created."

When I click on the OK button, Textpad goes away. I've upgraded Textpad from 4.7.1 to 4.7.2 with no change. I've uninstalled Textpad and reinstalled, with no change. None of my other windows applications have this problem. They all print just fine. Another person in my group also uses Textpad with exactly the same machine and operating system on the same network, and he has not experienced any printing problems.

The problem started about a week ago, and I cannot associate it with any action on my part, such as installation of a new application, etc.

I tried to find the "error log" that is mentioned in the Program Error pop-up box, but can't find anything.

Does anyone have a recommendation.

mo · Post by mo » Wed Nov 19, 2003 8:22 pm

You can find the error log in C:\Documents and Settings\All Users\Documents\Dr. Watson...but good luck understanding it!

I get this error now and again on W2k (more with SP2 than with SP4) with massive amounts of RAM and Disk Space.

From the little I've heard (which is VERY little) it does have something to do with two programs jaming up against each other at some point in some way; trying to use the same space or some such. I have usually been able to go on with use of the program by simply starting again.

When you want to print next time try closing TextPad and Right clicking on the file and clicking print...not what you want but something to see if it works just to get the job done.

jemoore23 · Post by **jemoore23** » Wed Nov 19, 2003 8:45 pm

You are correct that the dump file is not very understandable. I got nothing useful from it. But thanks for pointing out where it is - I would never have found it.

I tried your other suggestion of doing a r. mouse click on a text file on the desktop. Interestingly enough, PRINT does not show up as an option! PRINT is an option for other file types, such as DOC. In those cases, when I r. click I get Open; New; and Print as options above the first line. However for TXT files, I only get "edit" above the top line.

Perhaps there is something wrong with my profile for TXT files that is involved with this problem.

mo · Post by mo » Wed Nov 19, 2003 9:43 pm

Did you have a look at your permissions? Are these files maybe being saved "Read Only" or maybe you don't have permission for some reason?
On the other hand I don't know why either of these would cause the error you are mentioning.

jemoore23 · Post by **jemoore23** » Wed Nov 19, 2003 10:24 pm

I can't see anything wrong with file permissions, and I would think that if it was the file's fault, I would have similar problems using Notepad or Word, which print the files just fine.

I did try to look at the printer setup for TXT document classes, and it blew up when I tried to access the Printer information. The sequence is:
Configure>Preferences...>Document Classes>Text>Printing>Printer...

So it looks like anytime I try to access the Windows system DLL (or whatever the heck it is called) that has to do with printers from within Textpad, it blows up.

Thanks for your suggestions.

CyberSlug · Post by **CyberSlug** » Wed Nov 19, 2003 10:45 pm

Newtorked or local printer? (Maybe it makes a difference?)

If the printer is on the network, you might want to try setting up a local printer:

Code: Select all

1)  Run the add-new-printer wizard (I think it's Start > Settings > Control Panel > Printers)

2)  Choose LOCAL printer, FILE as the port, and use the same driver as your normal printer.

3)  If you do a test page, it should generate a file in the location you specify.  (This file can be dragged-and-dropped onto your normal printer and it should physically print out)

4)  Set printer as default, then try to print from TextPad.

jemoore23 · Post by **jemoore23** » Thu Nov 20, 2003 1:34 pm

Yes, I do have a network printer. I tried your suggestion and created a generic local text file printer target. Unfortunately, Textpad blows up before it ever gets to the Printer selection screen, so the type of printer does not seem to be the problem.
Textpad also blows up if I try to do a Print Preview. So it looks like it is not the printer that is causing the problem, but some sort of interface with the standard windows print wizard (or whatever its called).
I wonder if its possible to reinstall the windows 2000 print wizard by itself? I've reinstalled Textpad a few times, to no avail.

jemoore23 · Post by **jemoore23** » Thu Dec 04, 2003 1:15 pm

Problem solved! I use my laptop at home and at work. The problem was that I had set up a default printer which pointed to a printer on my network at home for the text document class. Apparently, this information is stored in the registry. When I got to work and tried to print, Textpad would die, apparently because it couldn't find that printer. Even though I had uninstalled and reinstalled Textpad, apparently the registry information was staying around and causing a problem.

The solution, as suggested by Helios support, was to exit Textpad and run the windows regedit program. Then I deleted any printers in the document classes listed in the
Registry under "HKEY_CURRENT_USER\Software\Helios\TextPad 4\Document Classes".

Fortunately that worked. Whew, that was a close one.