Message-ID: <049u3VANDUvzEwoj@netbook.demon.co.uk>
Date: Fri, 4 Jul 1997 19:28:29 +0100
To: Nate Eldredge <eldredge AT ap DOT net>
Cc: djgpp AT delorie DOT com
From: James MacDonald <trill AT xnetbook DOT demon DOT co DOT uk>
Subject: Re: CWSDPMI halting interrupt 19 (reboot)
In-Reply-To: <199707041814.LAA22009@adit.ap.net>
MIME-Version: 1.0
Precedence: bulk

In message <199707041814 DOT LAA22009 AT adit DOT ap DOT net>, Nate Eldredge
<eldredge AT ap DOT net> wrote :
>
>Ralf Brown's Interrupt List R53 has this to say about INT 19h:
>
>This interrupt reboots the system without clearing memory or restoring
>interrupt vectors.  Because interrupt vectors are preserved, this
>interrupt usually causes a system hang if any TSRs have hooked
>vectors from 00h through 1Ch, particularly INT 08.
>
>So perhaps INT 19 is not the best way to reboot. Other solutions:
>The standard way to reboot has always been a real-mode jump to F000h:FFF0h.
>For a warm boot, store 1234h at 0040h:0072h first; for a cold boot, store 0000h.
>
>I believe there is some port you can poke which has the same effect as a
>cold reboot. If the jump doesn't work, you could try disassembling the BIOS
>routine from there and look at what it does.
>
>HTH.
>
>Nate Eldredge
>eldredge AT ap DOT net

Well, how do you do that from C?
I don't want to use TASM.
-- 
Revised anti-spam in use : remove X to reply - 
'Xnetbook' becomes 'netbook'

Anti-spam thermonuclear warheads cheap at only $300!