Community

TextPad seems to have changed its behavior between 4.6.2 and 4.7.1 (Win2K SP4) when launched through file associations from a DOS prompt.
Namely, when typing:

C:\> somefile.txt

TextPad is launched and file somefile.txt gets loaded as expected but the DOS shell does not give back a prompt until after TextPad is terminated. (Version 4.6.2 works correctly and gives back the prompt immediately after the launch.) This makes me to suspect that the shell does not receive back an signal that TextPad has launched so it keeps waiting for it. Exactly the same issue occurs when using:

C:\> start "foo" somefile.txt

Is this a known bug in 4.7.1? Are there any workarounds or configuration hacks?

TIA,
Carol

I noticed this problem as well and I did a search to see if anyone else had experienced this and if there was a solution. I just upgraded from 4.1 to 4.7.1 and I noticed this right away.
I support several systems over a WAN and getting to files is much quicker via a Command Line window ( DOS ). I launch many file to textpad in the way you expalined - by typing the filename. This is really a pain in the way it is working now.
Anyone have a solution?

It works OK for me on Win2K/SP4. Try reverting to the default association, using Explorer, then make the association again, using TextPad. If that doesn't help, close all other applications, in case any of them are blocking DDE messages.

Keith MacDonald
Helios Software Solutions

I got it working by uninstalling TextPad, resetting file association registry keys to values copied from a pristine box, and then re-installing TextPad. HTH

I tried reverting back to the default installation via Explorer and then re-establishing in Textpad - didn't work. I monkeyed with various things and nothing worked.

I then copied my Texpad directory to my temp directory and did an uninstall from the Control Panals Add/Remove programs. I then re-installed Texpad by running the same Zip file that I did the upgrade with. (I still had it.) I then copied the TaxtPad directory that I had saved to my temp directory and overwrote any existing files. Copying the saved directory back in did restore some of the settings that I had and also recognized it as a registered product so I didn't have to go through that again. I did lose a lot of the setups that I had such as filters and such and I had to set it all up again but ever since this, things are Working now .