TextPad command line parameters

Paul in NJ · Post by **Paul in NJ** » Fri Aug 08, 2008 8:15 pm

It seems that, despite what the Help file says, TextPad 5.0.3 ignores most, if not all, of its Command Line Parameters under XP including -m, -am, etc.

I'd like to call TextPad from a batch file and have it open multiple files for editing. I've long been able to do so in Win98, but not in XP.

According to the Help file:

@filename: Open all the files that are listed, one per line, in the specified file.

This works in 98. In XP, however, this command

start "C:\Program Files\TextPad 5\TextPad.exe" @filelist.txt

Returns "The system cannot find the file @filelist.txt"

I've learned to live with XP's stunted version of DOS, but I really need TextPad to work here. Any suggestions will be very much appreciated.

gan · Post by **gan** » Fri Aug 08, 2008 9:36 pm

This is almost identical to your question in another thread started by you. Every example given by you so far works fine for me both under XP and Vista. There is no need to start a new thread for each command line parameter that doesn't work for you.

Why not upgrade to the latest version 5.2 since the first 5.x releases had several bugs. I'm using version 5.2 so have no idea if version 5.0.3 have problems with the command line parameter or not. Version 5.2 works just fine for me.

Paul in NJ · Post by **Paul in NJ** » Mon Aug 11, 2008 6:19 pm

gan wrote:This is almost identical to your question in another thread started by you. Every example given by you so far works fine for me both under XP and Vista. There is no need to start a new thread for each command line parameter that doesn't work for you.

At the time of the second post, no one had replied to the first; I thought perhaps I had been unclear. You may also note that the second post was not identical but expanded on the problem.

gan wrote:Why not upgrade to the latest version 5.2 since the first 5.x releases had several bugs. I'm using version 5.2 so have no idea if version 5.0.3 have problems with the command line parameter or not. Version 5.2 works just fine for me.

Thank you for that, but upgrading did not help. Evidently there is something about my XP installation that is 'off' somehow. I shall next attempt the same feat on a different PC.

gan · Post by **gan** » Mon Aug 11, 2008 9:12 pm

Paul in NJ wrote:At the time of the second post, no one had replied to the first; I thought perhaps I had been unclear. You may also note that the second post was not identical but expanded on the problem.

Sure no problem, but it might be better to continue on the original thread and relpy with further information then starting a new thread. It's just a tip and i'm not making the rules in here so i hope you don't take it the wrong way.

gan wrote:Thank you for that, but upgrading did not help. Evidently there is something about my XP installation that is 'off' somehow. I shall next attempt the same feat on a different PC.

Well i didn't really believe that 5.2 would solve this problem since i have not heard anyone else with similar problem, but 5.2 have other enhancements. My guess is that the other computer will work just fine. Hard to tell why this happen, but i guess there is something in the registry that is wrong.

Paul in NJ · Post by **Paul in NJ** » Tue Aug 12, 2008 8:50 pm

gan wrote:My guess is that the other computer will work just fine. Hard to tell why this happen, but i guess there is something in the registry that is wrong.

Bingo - an uninstall, regclean, and re-install fixed the issue.

Now if I could get TextPad to work in a batch file across network drives... but that's another thread!