_ Vbox 4.2.18 VM booted with FreeDOS floppy, kernel 2041, no config.sys, no autoexec.bat, no TSR's, no memory managers. _ The booting floppy includes syslinux.com 6.02. _ Two HDD images attached to the VM, MBR + 1 FAT16 formatted partition each. Executing syslinux.com -i c: (or "d:") results in the following error: "Invalid Opcode at AD04 5080 0206 5080 2021 3666 FFFD 0083 0000 5208 0000 0083 0000". The 2 relevant files (ldlinux.sys and ldlinux.c32) are copied to the destination volume anyway. The resulting volume is still not bootable. A similar scenario, but with memory manager(s) will fail with different errors. Hopefully this can be replicated and resolved. TIA, Ady.
> _ Vbox 4.2.18 VM booted with FreeDOS floppy, kernel 2041, no > config.sys, no autoexec.bat, no TSR's, no memory managers. > > _ The booting floppy includes syslinux.com 6.02. > > _ Two HDD images attached to the VM, MBR + 1 FAT16 formatted > partition each. > > Executing syslinux.com -i c: (or "d:") results in the following > error: > "Invalid Opcode at AD04 5080 0206 5080 2021 3666 FFFD 0083 0000 5208 > 0000 0083 0000". > > The 2 relevant files (ldlinux.sys and ldlinux.c32) are copied to the > destination volume anyway. The resulting volume is still not > bootable. > > A similar scenario, but with memory manager(s) will fail with > different errors. >Testing with VirtualBox 4.2.18 (I'm not ready to update to 4.3 yet) and using the same method described in the previous email, when executing "syslinux.com -i c:" I get the following results: _ 6.02-pre06/11/12/13 OK. _ 6.02-pre14 and 6.02-pre15 generate a "guru mediation" crash of the VM (Vbox itself is OK). _ 6.02-pre16 and 6.02 final generate an "Invalid Opcode" error in FreeDOS (as described in previous email); the VM and Vbox are OK (no crash). As I said before, with FreeDOS' memory managers, the resulting error is different. TIA, Ady.
H. Peter Anvin
2014-Jan-16 18:59 UTC
[syslinux] syslinux.com 6.02 Invalid Opcode under FreeDOS
On 10/15/2013 02:58 PM, Ady wrote:> _ Vbox 4.2.18 VM booted with FreeDOS floppy, kernel 2041, no > config.sys, no autoexec.bat, no TSR's, no memory managers. > > _ The booting floppy includes syslinux.com 6.02. > > _ Two HDD images attached to the VM, MBR + 1 FAT16 formatted > partition each. > > Executing syslinux.com -i c: (or "d:") results in the following > error: > "Invalid Opcode at AD04 5080 0206 5080 2021 3666 FFFD 0083 0000 5208 > 0000 0083 0000". > > The 2 relevant files (ldlinux.sys and ldlinux.c32) are copied to the > destination volume anyway. The resulting volume is still not > bootable. > > A similar scenario, but with memory manager(s) will fail with > different errors. > > Hopefully this can be replicated and resolved. >Just pushed a fix for it. -hpa