update: the settings was not set /read. after a restart the power not work - fixed

feedback please

Sorry))) How to load your .sys driver in NT4?

Babasha wrote on 2026-10-01, 17:07:

Sorry))) How to load your .sys driver in NT4?

copy the sys in drivers and add a entry in registry. do you have the device manager, use install driver (Treiber einrichten).
then regedit, HKLM \system\curren control set \ services\ acpidrv
please set the correct image path System32\driver\Acpidrv.sys

Novanianer wrote on 2026-10-01, 17:39:

copy the sys in drivers and add a entry in registry. do you have the device manager, use install driver (Treiber einrichten). th […]
Show full quote

Babasha wrote on 2026-10-01, 17:07:

Sorry))) How to load your .sys driver in NT4?

copy the sys in drivers and add a entry in registry. do you have the device manager, use install driver (Treiber einrichten).
then regedit, HKLM \system\curren control set \ services\ acpidrv
please set the correct image path System32\driver\Acpidrv.sys

Tnx! Will try to manual setup next days and inform you.
PS. I dont have Device manager in my NT4. Is it additional (modern) utility?

Babasha wrote on 2026-10-01, 18:02:

Novanianer wrote on 2026-10-01, 17:39:

copy the sys in drivers and add a entry in registry. do you have the device manager, use install driver (Treiber einrichten). th […]
Show full quote

Babasha wrote on 2026-10-01, 17:07:

Sorry))) How to load your .sys driver in NT4?

copy the sys in drivers and add a entry in registry. do you have the device manager, use install driver (Treiber einrichten).
then regedit, HKLM \system\curren control set \ services\ acpidrv
please set the correct image path System32\driver\Acpidrv.sys

Tnx! Will try to manual setup next days and inform you.
PS. I dont have Device manager in my NT4. Is it additional (modern) utility?

the usb driver has a device manager ,the cpl file

@Novanier

While adding a service manually isn't for sure rocket science, and pretty easy for everyone with minimal skills, for sure bundling a .reg file in the zip was even easier, making the whole thing to appear less amateurish.

Novanianer wrote on 2026-10-01, 18:38:

Babasha wrote on 2026-10-01, 18:02:

Novanianer wrote on 2026-10-01, 17:39:

copy the sys in drivers and add a entry in registry. do you have the device manager, use install driver (Treiber einrichten).
then regedit, HKLM \system\curren control set \ services\ acpidrv
please set the correct image path System32\driver\Acpidrv.sys

Tnx! Will try to manual setup next days and inform you.
PS. I dont have Device manager in my NT4. Is it additional (modern) utility?

the usb driver has a device manager ,the cpl file

Ok! Currently its empty new system with SP6a + your CUPS installed only. Next steps are ACPI and your USB stack.

I add driver and .cpl to System32 folder and install it using Device manager
Check it with Devices in Control panel - driver is started OK
Get the error in its Control applet

Is it compatible with VirtualBox? or what settings it reqs?

is listed

Babasha wrote on 2026-10-02, 10:55:

I add driver and .cpl to System32 folder and install it using Device manager Check it with Devices in Control panel - driver is […]
Show full quote

I add driver and .cpl to System32 folder and install it using Device manager
Check it with Devices in Control panel - driver is started OK
Get the error in its Control applet

Is it compatible with VirtualBox? or what settings it reqs?

Not tested (yet) but I think VBOX/VMmare assume that NT has no ACPI support, and act consequently.

Try to set the machine to Win2000 or Win98 and see if it helps

Perhaps, the usual APM HALs from either SP or Dell or Fujustu works perfectly in NT4 and even nt3.51. But you have to powerdown the machine using its internal start menu, not the external commands provided by Vbox/VMware

I made a registry file for your convenience

1REGEDIT4
2
3[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Acpidrv]
4"ImagePath"="System32\\DRIVERS\\Acpidrv.sys"
5"Start"=dword:00000002
6"ErrorControl"=dword:00000001
7"DisplayName"="ACPI Driver for NT4"
8"Type"=dword:00000001

Just save it as acpidriv.reg, import and reboot, then use the cpl applet to configure (in vmware seem to work even with the VM set to NT4, not yet tested in vbox)

Novanianer wrote on 2026-10-01, 08:55:

Hi, here is a alternate ACPI driver for power off on nt4. […]
Show full quote

Hi,
here is a alternate ACPI driver for power off on nt4.

The lenvo driver an reg entry don't work on my board.
There's a dll and and a cpl.

Greeting.

Hi once more!
What config of your PC or what emulator you use?
Will try to recreate it and use in one-to-one config)))

Babasha wrote on 2026-10-02, 13:50:

Hi once more! What config of your PC or what emulator you use? Will try to recreate it and use in one-to-one config))) […]
Show full quote

Novanianer wrote on 2026-10-01, 08:55:

Hi, here is a alternate ACPI driver for power off on nt4. […]
Show full quote

Hi,
here is a alternate ACPI driver for power off on nt4.

The lenvo driver an reg entry don't work on my board.
There's a dll and and a cpl.

Greeting.

Hi once more!
What config of your PC or what emulator you use?
Will try to recreate it and use in one-to-one config)))

Hi,
In general, I recommend The Solutor's solution using the APM/ACPi files from SP, Dell, or Fujitsu. Maybe he'll even post the links. These developers definitely did a better job than I did.
As for the setup, I assume you’re talking about the hardware. There are plenty of options out there. Check out omores or here in the forum. Why do you want to buy hardware in the first place? Utility, price, hobby expenses? Of course, you have to decide that for yourself. Oh, and if there aren’t any drivers available, you’ll have to write them yourself!
Well, whatever. But sharing files isn't really that helpful.

Novanianer wrote on 2026-10-04, 12:18:

Hi, In general, I recommend The Solutor's solution using the APM/ACPi files from SP, Dell, or Fujitsu. Maybe he'll even post th […]
Show full quote

Babasha wrote on 2026-10-02, 13:50:

Hi once more! What config of your PC or what emulator you use? Will try to recreate it and use in one-to-one config))) […]
Show full quote

Novanianer wrote on 2026-10-01, 08:55:

Hi, here is a alternate ACPI driver for power off on nt4. […]
Show full quote

Hi,
here is a alternate ACPI driver for power off on nt4.

The lenvo driver an reg entry don't work on my board.
There's a dll and and a cpl.

Greeting.

Hi once more!
What config of your PC or what emulator you use?
Will try to recreate it and use in one-to-one config)))

Hi,
In general, I recommend The Solutor's solution using the APM/ACPi files from SP, Dell, or Fujitsu. Maybe he'll even post the links. These developers definitely did a better job than I did.
As for the setup, I assume you’re talking about the hardware. There are plenty of options out there. Check out omores or here in the forum. Why do you want to buy hardware in the first place? Utility, price, hobby expenses? Of course, you have to decide that for yourself. Oh, and if there aren’t any drivers available, you’ll have to write them yourself!
Well, whatever. But sharing files isn't really that helpful.

Hi! Tnx for your reply.
A little history of my WinNT hobby. It was my favorite OS in late 90 - early 2000 but since that times i lost a big part of my ild archives and knowledge (20 years without experience are not joke).
I read on Vogons here your topics about new USB STACK, CUPS and some drivers and its back my interest to WinNT4.
I dont look at WinNT 4 topics and news for 20 years as i say - so pls give links (if you can) if you write something understandable "by default" for you as i dont know who is Solutor and omores, etc)))
Everything about hardware - my direct interest is new WinNT 4 rig with good compatibility with USB, printing and maybe D3D-OGL wrapper (i dont play games but why not to test it). Currently i dont know my future rig config and just experimenting with AthlonXP, 256-512MB RAM, NVidia Riva TNT AGP 16MB.

The Solutor it's me , but I understand that looking one message above may be hard 😁

Not that hard is to search for something using duckduck or whatever else, after you got some the hint on forums

Whatever...

This is about the most obvious solution using what MS provides in the last service pack

https://nt4ref.zcm.com.au/softoff.htm

The hal softex dll comes in two flavours, single core and multicore

It works on most scenarios but not on 100% of cases

Alternate solutions come from fujitsu, Dell (and maybe other), but afaik there isn't a mps version.

These are for NT4 (two different flavours of the same thing, the kilometrage may vary)

And this is for NT 3.51

No need to overwrite rename dlls (with the risk of having an unbootable system)

You can just multiboot editing your boot ini, something like this

1[boot loader]
2timeout=3
3default=multi(0)disk(0)rdisk(0)partition(1)\WINNT4
4[operating systems]
5multi(0)disk(0)rdisk(0)partition(1)\WINNT4=Windows NT Workstation Version 4.00 (disk 0 partition 1)"
6multi(0)disk(0)rdisk(0)partition(1)\WINNT4=Windows NT Workstation Version 4.00 [VGA mode] (disk 0 partition 1)" /basevideo /sos
7multi(0)disk(0)rdisk(0)partition(1)\WINNT4=Windows NT Workstation Version 4.00 Halfmvn"  /hal=Halfmvn.dll
8multi(0)disk(0)rdisk(0)partition(1)\WINNT4="Windows NT Workstation Version 4.00 softex 2+ CPUs" /kernel=ntkrnlmp.exe /hal=halmpss.dll
9multi(0)disk(0)rdisk(0)partition(1)\WINNT4="Windows NT Workstation Version 4.00 softex" /kernel=ntkrnlmp.exe /hal=halmps.dll

That said Novanianer's (it's the OP 😀 ) solution, may be very valuable in vmware and virtualbox, given it's a proper ACPI solution rather than an APM one, which means that shutdown may be controlled from the VMware/Vbox GUI, not just from the guest OS itself (tested vmware only for now, it works)

It may be also a valuable resource for NT Server TSE where the softex dlls aren't working and the Fujitsu ones are just single core. (not yet tested)