VOGONS


First post, by Marco

User metadata
Rank Oldbie
Rank
Oldbie

hello all,

I might be wrong but I roughly remember that some programs / OS were able to reboot directly to the boot init sequence. (Not to post/bios but directly to „starting msdos“.

Am I right here? If yes do you know any program / executable to do so?

Thank you

1) VLSI SCAMP 311 | 386SX25@TI486SXLC2-50@63 | 16MB | CL-GD5434 | CT2830| SCC-1 | MT32 | WDC160GB/7200/8MB | Fast-SCSI AHA 1542CF + BlueSCSI v2/15k U320
2) SIS486 | 486DX/2 66(@80) | 32MB | TGUI9440 | LAPC-I

Reply 1 of 10, by Disruptor

User metadata
Rank Oldbie
Rank
Oldbie

I remember such a program, but I do not know its name.
I had to use Ctrl-Shift-Shift as hotkey.

Reply 2 of 10, by BloodyCactus

User metadata
Rank Oldbie
Rank
Oldbie

you can do it with int 0x19 but it rarely works because of hooked interrupt handlers. qemm used to have a warm reboot mechanism that was more reliable.

--/\-[ Stu : Bloody Cactus :: [ https://bloodycactus.com :: http://kråketær.com ]-/\--

Reply 3 of 10, by Marco

User metadata
Rank Oldbie
Rank
Oldbie

Could Indeed be it was quemm. Would be great if that function would be available as dedicated executable.

1) VLSI SCAMP 311 | 386SX25@TI486SXLC2-50@63 | 16MB | CL-GD5434 | CT2830| SCC-1 | MT32 | WDC160GB/7200/8MB | Fast-SCSI AHA 1542CF + BlueSCSI v2/15k U320
2) SIS486 | 486DX/2 66(@80) | 32MB | TGUI9440 | LAPC-I

Reply 4 of 10, by wbahnassi

User metadata
Rank Oldbie
Rank
Oldbie

Later QEMM versions did that fast boot stuff. Ctrl+Alt+Delete skips the POST and goes directly to Starting MS DOS...
It was nice, but sometimes it caused issues and you had to reboot while rebooting to do a full POST and force reinit of some crazy stuff (e.g. a hanging Adlib sound).

Turbo XT 12MHz, 8-bit VGA, Dual 360K drives
Intel 386 DX-33, Speedstar 24X, SB 1.5, 1x CD
Intel 486 DX2-66, CL5428 VLB, SBPro 2, 2x CD
Intel Pentium 90, Matrox Millenium 2, SB16, 4x CD
HP Z400, Xeon 3.46GHz, YMF-744, Voodoo3, RTX2080Ti

Reply 5 of 10, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

Lilo can be abused for this.

It is able to be told to start an msdos boot sector, from the command line.

Reply 6 of 10, by Grzyb

User metadata
Rank l33t
Rank
l33t
BloodyCactus wrote on 2025-10-30, 16:01:

you can do it with int 0x19 but it rarely works because of hooked interrupt handlers. qemm used to have a warm reboot mechanism that was more reliable.

Exactly!

Nie rzucim ziemi, skąd nasz root!

Reply 7 of 10, by BloodyCactus

User metadata
Rank Oldbie
Rank
Oldbie

I actually have a tool to do it.

it runs a bootsector to grab all the original int vectors, then you run the stage2 tool which creates the tsr and hooks int19 and puts all the vectors back.
once it has the vectors, you dont need the bootdisk anymore to capture them. once you have the generated warm.com its specific to your machine and off you go!

things like himem.sys can break it tho.

https://bloodycactus.com/files/warmboot.zip

--/\-[ Stu : Bloody Cactus :: [ https://bloodycactus.com :: http://kråketær.com ]-/\--

Reply 8 of 10, by Marco

User metadata
Rank Oldbie
Rank
Oldbie

Great thanks. Although it’s sounds a bit like black magic I Will definitely try. 😀

1) VLSI SCAMP 311 | 386SX25@TI486SXLC2-50@63 | 16MB | CL-GD5434 | CT2830| SCC-1 | MT32 | WDC160GB/7200/8MB | Fast-SCSI AHA 1542CF + BlueSCSI v2/15k U320
2) SIS486 | 486DX/2 66(@80) | 32MB | TGUI9440 | LAPC-I

Reply 9 of 10, by igully

User metadata
Rank Newbie
Rank
Newbie

Be aware that flushing caches is a good preventive measure to avoid data/filesystem corruption, and you should also attempt to notify any network stack that could possibly be active, the same goes for any DOS multitasker. Later, reset the drive. And then finally, perform the fast reboot, which despite all these precautions, might not be safe due to interrupt interceptions, as mentioned above.

IMHO, best is to perform a cold reboot and live with the burden of a couple of additional seconds for the boot process to end, than to risk system integrity.

Reply 10 of 10, by Marco

User metadata
Rank Oldbie
Rank
Oldbie

Yes indeed. Cache flush is necessary in case you don’t use /x option.

Especially when you are really testing a lot configs etc it gets annoying with that long reboot time 😀

1) VLSI SCAMP 311 | 386SX25@TI486SXLC2-50@63 | 16MB | CL-GD5434 | CT2830| SCC-1 | MT32 | WDC160GB/7200/8MB | Fast-SCSI AHA 1542CF + BlueSCSI v2/15k U320
2) SIS486 | 486DX/2 66(@80) | 32MB | TGUI9440 | LAPC-I