Subj : Windows 2000 and legacy programs
To   : Dale Ross
From : Steven Horn
Date : Sat Feb 24 2001 01:32 pm

Dale Ross (1:379/1.99) wrote to Steven Horn at 10:04 on 23 Feb 2001:

 DR> OK here is a suggestion. Run everything from command.com NOT
 DR> CMD.EXE. That means that you should start timED from command.com
 DR> and not cmd.exe. In the bat file that you run timED from put the
 DR> following line at the very top of your bat file. 

 DR> command.com

 DR> This will force everything to run from command.com the real DOS
 DR> command processor and not CMD.exe.

 DR> Second question. Is Squish in D:\Binkley directory? If not is
 DR> Squish defined in any path? You have two choices with Windows
 DR> NT/Windows 2000 for defining your paths. In Windows 2000 you can:

 DR> Right Mouse Click "My Computer"
 DR> Choose "Properties"
 DR> Choose "Advanced"
 DR> Choose "Environment Variables"
 DR> Set your path.

 DR> However, these statements will not be good when you launch
 DR> command.com!!! 

 DR> For that you have file in \WINNT\SYSTEM32 called autoexec.nt 

 DR> Go into this file and add your path statements. If you want a
 DR> custom autoexec.nt file you can have it.

 DR> For example, maybe you want one just for you BBS. Call it
 DR> autoexec.bbs Create a shortcut to the main bat file and in that
 DR> shortcut under "Program" \ "Advanced" point to this file.

 DR> Any reason you are using DOS Binkley instead of Windows NT version?
 DR> I'd suggest Binkley/XE. I was running it before switching to Argus.
 DR> I never had problems with it handling errorlevel.

I'm trying the batch file with "command.com" and have addressed any possible 
outstanding "path" issues.  As for my Binkley, I use the Windows 32 version of 
Binkley 2.60.  Error levels do not seem to be a problem for it.

Take care,

Steven Horn (shorn@yknet.ca)
Moderator, ALASKA_CHAT and CAN_SYSLAW 
--- timEd/386 1.10.y2k+
 * Origin: North_of_60ø, Whitehorse, YT, Canada (1:17/67)

.