jeffm@mmintl.UUCP (Jeffrey Miller) (08/09/85)
* Sorry it took me so long to respond about this int 19 bios bug. I tried doing the int 19 from debug on my 6300 and the system hung. I next tried it with a tiny .exe and the system hung. Next, I tried the same 2 things on an XT and they both rebooted properly. What does it all mean? -- I have no idea. Perhaps the next thing to do is contact Phoenix. Are you out there Phoenix? ************************************************* * Jeff Miller * * Multimate International Corp. * * 52 Oakland Avenue * * East Hartford, CT 06108-9911 * * (203) 522-2116 Ext. 257 * * UUCP: * * ...!seismo!utah-cs!utah-gr!pwa-b!mmintl!jeffm * ************************************************* *
jeffm@mmintl.UUCP (Jeffrey Miller) (08/20/85)
* I just tried doing an int 19 with debug again. This time I renamed config.sys to config.sav, and autoexec.bat to autoexec.sav. This prevented any loading of memory-resident drivers (for my ethernet card and ansi.sys) and any memory-resident programs (vterm for serial communications). This time int 19 worked on my 6300! I then restored the 2 .sav files, and int 19 worked again. It seems to get hung up reloading over existing stuff. When I tried to do it again with the drivers and vterm already loaded it failed. Perhaps the reboot with int 19 does not go far enough in initializing memory. It certainly does not do the ROM-resident diagnostics. I am running PC-DOS 3.1 by the way, with no problems and I have 640k on the motherboard. Maybe the discrepancy is in the difference in entry into the diagnostic routines? ************************************************* * Jeff Miller * * Multimate International Corp. * * 52 Oakland Avenue * * East Hartford, CT 06108-9911 * * (203) 522-2116 x257 * * UUCP: * * ...!seismo!utah-cs!utah-gr!pwa-b!mmintl!jeffm * * ps. I am unable to mail back to ARPA but I * * can receive mail from there. * ************************************************* *