|
|
Post by pacific on May 1, 2019 12:29:35 GMT 1
Hi.
I'm having problems while running Novell Menu System V1.22 (1987!).
One of our users still uses this. It has a text file with menu options and dos commands to run when that option is selected. This runs fine in a 32bit command prompt but in vDos it doesn't appear to try to run the dos commands at all going straight back to the menu.
Any idea what may be the cause?
Thankls
|
|
|
|
Post by Jos on May 1, 2019 12:40:36 GMT 1
I guess something is off with the drive assignments or paths.
Start vDos with the log option (“…vDos.exe” /log). In the generated vDos.log file look for “FindFirst failed”, “Invalid path”, “Program not executed/loaded” and the like entries.
Jos
|
|
|
|
Post by pacific on May 1, 2019 14:05:26 GMT 1
I've run it with the log command and got the following errors:
5.35 Execute: menu.EXE - menu2
5.36 Int 21 unhandled call E3E3
Int 21 unhandled call DD00
Int 21 unhandled call BAB3
Int 21 unhandled call BA07
Execute: menuparz.COM - 5 7 6
5.38 Program not executed/loaded (2): menuparz.COM
Execute: menuparz.EXE - 5 7 6
5.39 Int 21 unhandled call EA01
6.19 Delayed logging, set w/o DOS call:
Int 22 => 1001:0c8c
9.57 Idle
10.04 Idle end
10.06 Int 21 unhandled call DD00
Int 21 unhandled call DD00
Int 21 unhandled call BAB3
Int 21 unhandled call BA07
Execute: menuparz.COM - 5 7 6
Program not executed/loaded (2): menuparz.COM
Execute: menuparz.EXE - 5 7 6
Int 21 unhandled call EA01
|
|
|
|
Post by Jos on May 1, 2019 14:39:09 GMT 1
That didn’t bring much (anything). The unhandled Int 21 calls are all NetWare specific and will neither work in NTVDM.
No indication something else than the menu program is tried to start. Given the real ancient date, could be the program still uses MS-DOS 1.x FCB calls, especially to test if command.com is present. Support of the MS-DOS 1.x API isn’t complete, so that test will fail.
You could try to create a dummy command.com file (doesn’t matter what that is), and see what happens. Else post the program to test.
Jos
|
|
