|
Post by scotx on Feb 13, 2024 5:20:35 GMT 1
Hi Forum,
I have just recently moved to dBase V from dBase IV and currently trying to make/build the application, that already runs under dBase V when compiling all the PRGs to DBOs.
Using the Make menu Option in dBASE V I'm getting an "Illegal opcode FF at 0D0D:0009" vDos Exception at some point in the process before the vDOS windows dies. We are using vDOS 23.xx.xx that was built and sent to us on the 23.08.23
Here is the tailend of the vdos.log
.... FINDFIRST failed: C:\Y_PROC.DBO(18) FINDFIRST failed: C:\LE_73259.DEP(18) 388.48 FINDFIRST failed: C:\LE_96145.TXT(18) 388.49 CREATEFILE failed: DBASEV\DE\TMP71152.$DB(80) => E:\DBASEV\DE\TMP71152.$DB(80) 388.54 CREATEFILE failed: ZMUKL\APP\Y_PROC.DBO(80) => E:\ZMUKL\APP\Y_PROC.DBO(80) 388.65 CREATEFILE failed: PROJECT.CFG(80) => E:\zMUKL\CONFIG\vDOS-DBASE5\PROJECT.CFG(80) 388.74 FINDFIRST failed: C:\LE_76053.LST(18) 388.78 Delayed, directly set: INT 09 => original INT 1B => original INT 23 => original INT 24 => original
LOAD-EXEC: E:\DBASEV\DE\BDL.EXE -A -B MUKL_DSK -D DB437GE0 -E zMUKL -M -S @LE_76053.LST OPENFILE failed: DBASEV\DE\BDL.ETX(2) => E:\DBASEV\DE\BDL.ETX(2) INT 15 unhandled call BFDE INT 2F unhandled call 1687 INT 15 unhandled call BFDE
Regards Scot-X
|
|
|
Post by Jos on Feb 13, 2024 7:42:43 GMT 1
That exception states the emulated CPU encountered an illegal instruction. So the program cannot be executed any further and vDos has to quit. Whether opcode FF at address 0D0D:0009 is correct (it’s data, not code), or how the CPU came there, is unknown.
- If you use the 2023.05.01, you get the same error? - What when you execute BDL.EXE -A -B… directly at the command prompt?
Jos
|
|
|
Post by scotx on Feb 13, 2024 10:14:14 GMT 1
Hi Jos,
I've not tried using 2023.05.01 but I have just actually taken your advice and prepared a new file list of respective DBO files and packed the command in a batch file. The process ran through without an exception in vDOS Just got to see if the application runs. .
|
|