Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site moncol.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!mtunh!mtung!mtunf!ariel!vax135!petsd!moncol!john From: john@moncol.UUCP (John Ruschmeyer) Newsgroups: net.micro.att,net.micro.pc Subject: An AT&T 6300 bios bug??? Message-ID: <417@moncol.UUCP> Date: Wed, 17-Jul-85 00:34:59 EDT Article-I.D.: moncol.417 Posted: Wed Jul 17 00:34:59 1985 Date-Received: Sat, 13-Jul-85 10:53:57 EDT Organization: Monmouth College, West Long Branch, NJ 07764 Lines: 34 Xref: watmath net.micro.att:233 net.micro.pc:4518 I have recently gotten into using MS-DOS and bios interrupt calls and noticed the following peculiarity on the AT&T PC6300: From debug, I assemble the one-line program int 19 and execute it. This should invoke the bios interrupt to reboot the system. Running the program, it does begin a reboot, but the system then hangs immediately after printing out the compatability software and MS-DOS version messages. The reset switch must then be pressed to restart the system. The system also hangs at the same point when executing an int 18 (transfer to ROM BASIC on an IBM). If it matters, the system is an AT&T 6300 with 640k memory, one floppy, and a 10-meg hard disk. Oddly enough, both interrupts run correctly on my 256k, 2-drive Tandy 1000. Both machines have a compatability bios by Phoenix Associates. Am I doing something wrong or is this a bug in the bios? -- Name: John Ruschmeyer US Mail: Monmouth College, W. Long Branch, NJ 07764 Phone: (201) 222-6600 x366 UUCP: ...!vax135!petsd!moncol!john ...!princeton!moncol!john ...!pesnta!moncol!john Ingredients: Carbonated water, sugar, caramel color, phosphoric acid, natural flavorings, caffeine