Xref: utzoo comp.sys.ibm.pc.misc:4738 comp.os.msdos.programmer:2420
Path: utzoo!attcan!uunet!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!wuarchive!udel!rochester!pt.cs.cmu.edu!b.gp.cs.cmu.edu!Ralf.Brown@B.GP.CS.CMU.EDU
From: Ralf.Brown@B.GP.CS.CMU.EDU
Newsgroups: comp.sys.ibm.pc.misc,comp.os.msdos.programmer
Subject: Re: Reboot from software
Message-ID: <27677e85@ralf>
Date: 13 Dec 90 12:13:41 GMT
Sender: ralf@b.gp.cs.cmu.edu
Organization: Carnegie Mellon University School of Computer Science
Lines: 28
In-Reply-To: <34681@netnews.upenn.edu>

In article <34681@netnews.upenn.edu>, corry@eniac.seas.upenn.edu (Chris Corry) wrote:
}I'm writing a program that, under certain conditions, needs to reboot the
}computer. I figured that this was a simple generation of interrupt 25 (hex 19).
}However, everytime I try to use this mechanism (using geninterrupt or int86
}from Turbo C) the computer hangs. Anyone have any ideas?  Please mail or post

From the interrupt list:

INT 19 - DISK BOOT
   causes reboot of disk system (no memory test performed, interrupt vectors
   preserved).	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.

Notes:	to accomplish a warm boot equivalent to Ctrl-Alt-Del, store 1234h in
	  0040h:0072h and jump to FFFFh:0000h.	For a cold boot equivalent to
	  a reset, store 0000h at 0040h:0072h before jumping.
	VDISK.SYS hooks this interrupt to allow applications to find out how
	  much extended memory has been used by VDISKs (the three bytes at
	  offset 2Ch in the INT 19 handler's segment contain the linear address
	  of the first free extended memory).


--
UUCP: {ucbvax,harvard}!cs.cmu.edu!ralf -=- 412-268-3053 (school) -=- FAX: ask
ARPA: ralf@cs.cmu.edu  BIT: ralf%cs.cmu.edu@CMUCCVMA  FIDO: 1:129/3.1
Disclaimer?    |   I was gratified to be able to answer promptly, and I did.
What's that?   |   I said I didn't know.  --Mark Twain