MS-DOS Batch Files
Jan 17, 2021 14:50:45 GMT 1
Post by chrisr on Jan 17, 2021 14:50:45 GMT 1
My legacy MS-DOS software is running OK in a Windows XP virtual computer. But with an identical folder and file structure for vDos it is not.
In Windows XP, the software is started using the command C:\OASYS\RUNO.BAT SET, GEO1,GEO contained as the target in the shortcut. SET, GEO1 and GEO are supposed to be replaceable parameters in the batch file RUNO.BAT. What I get is the following:
A few return keys ends up at a command prompt and then I can exit from vDos.
What appears to be happening is that the replaceable parameters are not being recognised as such by vDos and not passed to the batch file. The rest of the responses illustrated are just failures of the batch file to do what it is supposed to do.
Obvious answer is to revise the batch file as most of these particular parameters are fixed for a fixed folder/file structure. But the way the software is run is by creating other batch files with different parameters as a means of passing control to menu software, then individual applications, then return back to the menu, then finish, makes this difficult. Some of these batch files are run by the software executables; some by other batch files. So if the first batch file fails, then others will as well.
This is the contents of the vDos.log file:
vDos 2020.03.01
C: => (Local) C:\vDos\OASYS\
C: => (Local) I:\DOS\
4.64 Execute: \OASYS\GETDRIVE.COM
Execute: driveset.EXE - C:\OASYS
Int 0 => 1bd:00e7
Int 0 => original
5.09 Delayed logging, set w/o DOS call:
Int 22 => original
264.78 Execute: \OASYS\GETDRIVE.COM
Invalid path reference: A:OL1.BAT
Execute: QUIZ.EXE - A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Int 0 => 299:00df
Int 23 => 299:00e6
Int 24 => 299:00ae
Int 3F => 299:00d7
264.82 Int 1B => 237:012d
268.10 Int 0 => original
Int 1B => original
Int 23 => original
Int 24 => original
Int 3F => original
273.81 vDos ended by EXIT (0)
Not sure that any of this helps except it seems to confirm some of the software tools are being run successfully [although the batch file should have bypassed some of these].
My question therefore is whether I am interpreting the problem correctly and it is an issue with batch file replaceable parameters, or whether I should be looking elsewhere.
In Windows XP, the software is started using the command C:\OASYS\RUNO.BAT SET, GEO1,GEO contained as the target in the shortcut. SET, GEO1 and GEO are supposed to be replaceable parameters in the batch file RUNO.BAT. What I get is the following:
A few return keys ends up at a command prompt and then I can exit from vDos.
What appears to be happening is that the replaceable parameters are not being recognised as such by vDos and not passed to the batch file. The rest of the responses illustrated are just failures of the batch file to do what it is supposed to do.
Obvious answer is to revise the batch file as most of these particular parameters are fixed for a fixed folder/file structure. But the way the software is run is by creating other batch files with different parameters as a means of passing control to menu software, then individual applications, then return back to the menu, then finish, makes this difficult. Some of these batch files are run by the software executables; some by other batch files. So if the first batch file fails, then others will as well.
This is the contents of the vDos.log file:
vDos 2020.03.01
C: => (Local) C:\vDos\OASYS\
C: => (Local) I:\DOS\
4.64 Execute: \OASYS\GETDRIVE.COM
Execute: driveset.EXE - C:\OASYS
Int 0 => 1bd:00e7
Int 0 => original
5.09 Delayed logging, set w/o DOS call:
Int 22 => original
264.78 Execute: \OASYS\GETDRIVE.COM
Invalid path reference: A:OL1.BAT
Execute: QUIZ.EXE - A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Int 0 => 299:00df
Int 23 => 299:00e6
Int 24 => 299:00ae
Int 3F => 299:00d7
264.82 Int 1B => 237:012d
268.10 Int 0 => original
Int 1B => original
Int 23 => original
Int 24 => original
Int 3F => original
273.81 vDos ended by EXIT (0)
Not sure that any of this helps except it seems to confirm some of the software tools are being run successfully [although the batch file should have bypassed some of these].
My question therefore is whether I am interpreting the problem correctly and it is an issue with batch file replaceable parameters, or whether I should be looking elsewhere.