Hey, I didn't know that! Thanks.
Chris Berry chris_berry@xxxxxxxxxxxxxxxxx Information Advisory Manager JM Associates
“If you have a strong enough why you can bear almost any how.” --Nietzsche
And instead of .bat make the file extension .cmd so it doesn't run in 16 bit mode. Jim Kenzig*****************************
"Richard F. Strait" <wrote: Thank you Grant, I hadn't worked with *.bat files for a long time. The use of the PAUSE command showed me the error of my ways and now I am off and running!
Thanks
rfstrait@xxxxxxxx
On Fri, 10 Mar 2006 16:59:59 -0800 "Grant, Lachlan ISMC:EX" writes:
Batch (*.bat)files still work, and are used very extensively.
Perhaps use the PAUSE command at the end of your batch file to see why
it isn't working. I'm guessing, but I think the batch file is running,
then erroring out (perhaps can't find the file specified?), then it
closes the command window as it has finished processing the commands.
Just a guess...!
Lachlan.
-----Original Message-----
From: windows2000-bounce@xxxxxxxxxxxxx
[mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Richard F. Strait
Sent: March 10, 2006 4:37 PM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] *.bat files under windows!
Is the concept of *.bat files obsolete under windows? I just installed
an MSDOS program that can be executed with *.bat files to access certain
DB files and find that they don't work?
Any comments!
TIA
Jim Kenzig CEO The Kenzig Group
http://www.kenzig.com
Sponsorships Available!
Blog: http://www.techblink.com
Terminal Services Downloads: http://www.thinhelp.com
Windows Vista: http://www.VistaPop.com
Virtualization: http://www.virtualize-it.com
Games: http://www.stressedpuppy.com