[syslinux] syslinux.com 5.01 pre3

[Bernd Blaauw]

Op 16-1-2013 21:30, Ady schreef:

> For example, in one of my attempts I received:
> Invalid Opcode at 11B1 89CF 0246 BA06 FFF8 0000 0000 0000 0000 1194
> 0000 0000 0000
>
> and the system hangs.

On that note, how are the destination checks done in the installer?
If my drive C: is a ramdisk (as created by the SHSURDRV driver by Jason 
Hood ) then "SYSLINUX C:" also ends up with lots of invalid opcodes. 
Usually the V8086 monitor built into JEMMEX/JEMM386 driver shows this.

Obviously the driver does just enough to have a FAT partition made 
available through a driveletter. No complete int13-alike fullproof 
implementation like MEMDISK does for example.