Discussion forum for all Windows batch related topics.
Moderator: DosItHelp
-
foxidrive
- Expert
- Posts: 6031
- Joined: 10 Feb 2012 02:20
#31
Post
by foxidrive » 10 Nov 2015 03:18
Samir wrote:Yes, we're working with the NT-based command.com equivalent, but it's still the same antiquated language that's been around since the late 1980s. Many of the bats you may write won't work in traditional DOS
Maybe it's the way your words come across, but they won't work because it's not "the same antiquated language".
Many batch files from MSDOS V6.22 era will also fail to run in Windows.
-
Samir
- Posts: 384
- Joined: 16 Jul 2013 12:00
- Location: HSV
-
Contact:
#32
Post
by Samir » 10 Nov 2015 09:53
foxidrive wrote:Samir wrote:Yes, we're working with the NT-based command.com equivalent, but it's still the same antiquated language that's been around since the late 1980s. Many of the bats you may write won't work in traditional DOS
Maybe it's the way your words come across, but they won't work because it's not "the same antiquated language".
Many batch files from MSDOS V6.22 era will also fail to run in Windows.
I'm not sure I'm following you.
Most everything I've tried from all of our DOS systems seems to work fine in NT+ command.com. Only when things like choice and other external commands that went missing in later versions wre used is there any issue, but this would happen even if someone deleted the file out of the \DOS directory.