Oil Palm application cannot run on vDOS

[prasglb]

Hello all,

My company has an legacy application requiring Windows 32bit. I believe it is DOS based. I tried using vDOS 2020.03.01 on Windows 10 1903 64bit. The app managed to start, but when I tried opening one of the menu, it returned an error message:

Main Menu is working:



Option Daily Harvesting returned error: (Proc INDEX_FILE line 0, undefined identifier (in macro) LOC)


I am able to provide the executable if required.

Path of vDos: C:\users\user\username\Documents\vDos\


Path of app: C:\users\user\username\Documents\vDos\Payroll

Content of autoexec.bat:

USE C: C:\Users\username\Documents\vDos\Payroll\


C:

call prprog\spay.exe


Content of the app directory:


Contents of PR51 folder (most likely the database, lots of .dbf file)



Contents of PRPROG folder (the executable are located here)



vDos Log:

vDos 2020.03.01
C: => (Local) C:\Users\username\Documents\vDos\
C: => (Local) C:\Users\username\Documents\vDos\Payroll\

10.40 Execute: spay.EXE
Int 24 => 2b9:0061
Int 24 => original
Int 0 => 2c34:162a
Int 23 => 395e:0d5e
Int 24 => 3a3f:02a8
10.42 Int 24 => 2b9:0061
Int 24 => 3a3f:02a8
11.01 Delayed logging, set w/o DOS call:
Int 22 => original
16.45 Int 24 => 2b9:0061
Int 24 => 3a3f:02a8
Int 24 => 2b9:0061
Int 24 => 3a3f:02a8
18.67 Int 24 => 2b9:0061
Int 24 => 3a3f:02a8
Int 0 => original
19.01 Delayed logging, set w/o DOS call:
Int 23 => original
Int 24 => original

Any help is appreciated, and I am glad to provide any additional information, Thank you very much.

[Jos]

The error message “Proc INDEX_FILE line 0, undefined identifier (in macro) LOC” doesn’t tell us much. You know that LOC identifier exists since the program runs in Windows 32. The vDos.log file doesn’t have any suspicious entries either.

You could shorten autoexec.txt to:
USE C: Payroll\
prprog\spay.exe
exit

This form of USE makes the app portable. Payroll is relative to Windows current work directory C:\Users\username\Documents\vDos. C: is redundant since that drive is already selected. Call is meaningless w/o a batchfile.

I would need a copy of the program to see what would be going on. Copy the vDos directory to somewhere else, and remove as much as possible (certainly data) leaving just that to still reproduce the error. Zip the lot and submit the zip file.

Jos