Candidate for kernel bug of the month perhaps? some underlying malloc() call that way prog handles memory block integrity of the structures and become damaged. Step through config.sys/autoexec.bat to see the bad wolf and remove it..
--chris Arkady V.Belousov wrote: >Hi! > >5-Июн-2006 11:48 [EMAIL PROTECTED] (cherry chien) wrote to ><freedos-user@lists.sourceforge.net>: > >cc> After reboot from 2G-harddisk >cc> Invalid Opcode at 2A18 0EB4 0613 03F2 ..... >cc> dos mem corrupt, first_mcb=0000 >cc> prev 0000:0000|1C 12 CF 00 DF 11 CF 00 C3 E2 00 F0 DF 11 Cf 00 >cc> notMZ0000:0000|1C 12 CF 00 DF 11 CF 00 C3 E2 00 F0 DF 11 Cf 00 >cc> PANIC: MCB chain corrupted >cc> System halted >cc> How can I fix the boot problem? > > Not enough information: which config.sys and autoexec.bat content on >those disk? After which statement in config.sys you get this message (what >you see on screen before this message)? Which kernel and FreeCOM version you > > _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
