Disruptor wrote on 2026-02-26, 16:57:

This request was NOT for the documentation. It was for you to modify the code :) I just have tested it on my K6-3 machine but th […]
Show full quote

igully wrote on 2026-02-26, 15:58:

Disruptor wrote on 2026-02-26, 07:39:

For all enhancements you add, like BIOS calls, please ensure that the stop clock function should be called very late in your code to avoid a possible re-activation of the clock -
even when we know that font restauration and stop clock together have no sense.

This is valuable information. I have included it in the current documentation of SANE so that users are aware of this precaution.
Thank you very much.

This request was NOT for the documentation. It was for you to modify the code 😀
I just have tested it on my K6-3 machine but there was no reaction.
However, I have seen that STOPRTC is one of your first steps in the code. But it should be one of that last ones, perhaps just before the APM/ACPI shutdown command.
However, It may also have to do that my QDL Titanium IB+ does not contain a Dallas 😀

I also have to add that it does not shutdown the motors of my IDE disks jet. (That system does not have any SCSI disks that could be shutdown too via ASPI command.)
I just got that because an AT power supply could not be shutdown by software 😀

Hi, the code should be fine. Text message order has improved a lot, but was not always chronologically precise, as it was an add-on, and some functions required not to be interrupted and so messaging happened after the the task was carried out. The code logic operates this way (from what I can recall, since I am not in front of my computer atm):

The first steps of the code generally speaking, are video stabilization, audio muting, cache flushing, floppy motors stopping (if you have floppies), and if you have vintage drives (these are pre IDE era (before 1990, mostly MFM, RLL and proprietary interfaces) then parking occurs. IDE drives were designed to overcome several old issues, including drive parking, with a built-in microcontroller and associated firmware that does the job automatically if it is needed. IDE drives were also more CPU dependent, but way cheaper than SCSI ever was.

To the meat of the matter, this is exactly as I coded the Dallas part:
At the time the Dallas RTC stop occurs, right afterwards, the APM shutdown is attempted (3 APM operations and the computer powers off, or only 1 if no APM). If APM is not present, then a text message is displayed to inform the user to shut down manually and a halt instructions is issued to stop the CPU. Since some emulators/virtual systems ignore the halt, I also placed, behind it, an infinite loop, which does the job. There is no clock manipulation after Dallas RTC stop. But of course, a user might create some workaround or do some funky stuff with a TSR, so it is important to let them know. Hence the documentation approach.

igully wrote on 2026-02-26, 18:27:

Text message order has improved a lot, but was not always chronologically precise...

Ah 😀
Thank you.

igully wrote on 2026-02-26, 15:56:

1. There are several DOS font extraction programs which create small enough executables that load them. The last two years I have seen at least two new font editing programs for DOS which seems very feature rich. chances are they might do the trick: Fontraption and Fontana are their names (a Google search should provide you their locations).

Yes, in fact I already use one which slightly modifies and replaces the built-in VGA text font. It's a TSR which takes about 3kb (the size of the VGA 9x16 BIOS font is 4kb, but this TSR uniquely compresses it). This is called KeyRus, version 8.0:

https://archive.org/details/keyrus8b

That is why I asked if modifying brightness is possible without defaulting to the basic BIOS font. Resetting to it wipes out the TSR font. But, this is a small problem, and the fact the resetting restores brightness is more important.

I have never heard of Dimmer; thanks very much for mentioning it. I'll give it a try. As they say, "It's nice to have options" and thankfully we have a lot of options in DOS!

Summary of changes from version 2.17 to current 2.26:
- New option /K disables any video card output until a keyboard key is pressed.
- Added ERRORLEVEL output so that users may better integrate SANE within batch files, extending their possibilities (for more detailed information read the included document).
- Reworked and cleaned up more code: version 2.17 executable was 2,100 bytes long and v2.26 is now 2,022 bytes.

Find new version 2.27 attached to the first post of this thread.

igully wrote on 2026-03-23, 18:06:

Summary of changes from version 2.17 to current 2.26: - New option /K disables any video card output until a keyboard key is pre […]
Show full quote

Summary of changes from version 2.17 to current 2.26:
- New option /K disables any video card output until a keyboard key is pressed.
- Added ERRORLEVEL output so that users may better integrate SANE within batch files, extending their possibilities (for more detailed information read the included document).
- Reworked and cleaned up more code: version 2.17 executable was 2,100 bytes long and v2.26 is now 2,022 bytes.

Find new version 2.27 attached to the first post of this thread.

First of all thank you very much for this utility! Always good to see awesome DOS tools. I used this to try and shutdown my system. The motherboard is EX58 series from gigabyte. When I run SANE /Y, it shows a series of messages on flushing caches and resetting some stuff. But then it shows this:

No APM services were active to shut down this computer.
Please now power off this machine manually.
System halted!

Any idea why this kind of message could be appearing for my motherboard? Any way or fix I can use? Is an APM service something that's run in DOS as a driver/TSR?

xtreger wrote on Yesterday, 22:07:

First of all thank you very much for this utility! Always good to see awesome DOS tools. I used this to try and shutdown my syst […]
Show full quote

First of all thank you very much for this utility! Always good to see awesome DOS tools. I used this to try and shutdown my system. The motherboard is EX58 series from gigabyte. When I run SANE /Y, it shows a series of messages on flushing caches and resetting some stuff. But then it shows this:

No APM services were active to shut down this computer.
Please now power off this machine manually.
System halted!

Any idea why this kind of message could be appearing for my motherboard? Any way or fix I can use? Is an APM service something that's run in DOS as a driver/TSR?

APM is the power management system provided by the mainboard, it's unclear how much past it's introduction that mainboards kept backwards compatibility with the standard from the early-mid 90s. It seems pretty universal but an X58 is quite a ways down the road. If the mainboard lacks APM backwards compatibility the software would need to be updated to use ACPI as a backup I would think.

Actually I get the same message on a semi-modern I5 8250 Dell laptop. So, as with crippling DOS 16-bit video BIOS and other eliminations, it appears APM is completely gone on "modern" systems. The regular cold boot option works, but the "quick" reboot doesn't (it just reboots to my primary Windows SSD, not my DOS USB memory stick).

Thanks for all the reports, I will investigate further.

In any case be aware that recent motherboards are not designed to run DOS at all, and do not have a legacy BIOS interface, and this is essential to properly run DOS, as in itself, DOS is just a thin layer over the BIOS. There are workarounds, but they are not quite there yet.

In any case, I will do research on an ACPI DOS friendlier side of its API and see what I can do to mitigate these issues.

Thanks again.

igully wrote on Today, 09:17:

In any case be aware that recent motherboards are not designed to run DOS at all, and do not have a legacy BIOS interface, and this is essential to properly run DOS, as in itself, DOS is just a thin layer over the BIOS. There are workarounds, but they are not quite there yet.

Someone will always try and someone will always ask

Yes, post 2020 systems are sadly UEFI only and will not boot DOS, but mine is a 2018 system with a BIOS and legacy mode. (It also has UEFI as well). Its BIOS and "legacy" code seems crippled and partially incompatible. But, it does work to run DOS bare metal. It just seems to lack APM and a proper "fast boot" option.

I have just spend an hour or so looking at ACPI:

What a freaking mess!

ACPI is currently at version 6.6 and from version 2.0 they start using 64 bit pointers. It is to put it mildly, an extremely complex interface that has no generic way of addressing it, but you must create a hardware abstraction layer specific to YOUR hardware to interface ACPICA.

It is C code with more structures than a well-aged bureaucrat. It definitely was built for OEMs to implement their own drivers on modern Operating Systems.

However, I found out that some Russian masochist tried to implement it in DOS using C, of course, with the end result of bloated code (note that he seems to be pretty proficient at what he does, so it is not his fault). And the code being highly unreliable, it could work, or not on some motherboard using some parameters or others, as long as legacy ACPI code is supported and that implementation is not broken. Either way, I am attaching his program. Available parameters are readable in English from the executable code itself. I applaud him. Not my cup of tea. I am sorry, I won't go there.

If you have a system that does not support legacy APM in your BIOS/UEFI, or just the old brute force PC-AT style power off (play with the settings!), I highly suggest that if you want to run DOS, you either change the hardware or just run it on an emulation/virtualization environment.