> On Fri, Nov 13, 2009 at 3:14 PM, <ibid...@lavabit.com> wrote: >> Hello everyone, >> First, I have a bug report against the 1497 fdos.org build of sys >> (OW386/FAT32/UPX)-- >> if I specify a file to write the bootsector to (sys c: large.bin, with >> or >> without /BOOTONLY or /BOTH), sys crashes with "Invalid opcode at 00AB >> (etc.) > ... > > does it work if you specify a source e.g. > sys . c: large.bin /BOOTONLY > > Thanks, > Jeremy >
Interesting... _if_ I do not specify the source WHEN WRITING the bootsector to a file, it will corrupt the MCB chain & halt the computer. It works fine when source is specified, and the system won't crash if I do not write the boot sector to a file. This build simply gives a more verbose version of the error when it crashes. This should probably be noted/"source" might be labeled as mandatory to reduce the chance of this error. If it is labeled as mandatory, I would not suggest actually making it mandatory for simple stuff (sys a:|c: should be supported). Here is a sample of when it crashed: ================================ Invalid opcode at 04AF 3604 0617 9A00 FEF0 F01D 7967 ... (more stuff about next and previous) dos mem corrupt, first_mcb=0276 PANIC: MCB chain corrupted =================================== no drivers, 2 instances of command.com (freecom), nothing run before 32 mb/default DOS VM w/ a few tweaks: audio changed, cd turned off Thanks, Ibidem ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
