Driver offer for NT 3.1 users: ATAPI for 1992/1993 builds

[TheCollector1988]

Compiled with the SDK tools they ship with (and with Visual C++ 1.0 in NT 3.1 RTM), I'm offering updated atapi.sys drivers for NT 3.10, more specifically from builds 297 onwards.

NT 3.10 Build 297 with source and compiler/link automated batch file + CD-ROM ISO test image:
https://yadi.sk/d/4tLEPLObvp4gj
Screenshot from 86Box 1.00:


NT 3.10 Build 340 with source:
https://yadi.sk/d/QYHklEZLvpHMw

NT 3.10 Build 511 with source (also works on 404 and 438) + Floppy Disk image for driver installation during the Text-based setup:
https://yadi.sk/d/ItcmL3_vvp5Eb

I hope this helps most NT 3.1 setups without SCSI, be it real hardware or emulated.

Note: for NT 3.10 Build 297 you need to patch setupapp.exe at offset 0x8DC2 (changing 74 to EB) for a proper detection during the Text-based setup from the 1.2MB boot disk. Same goes for 340, but at offset 0x7305.
Note2: for NT 3.10 Build 511+ (includes 528 and the Japanese checked 531) you need scsicdrm.sys and scsiport.sys from 438 otherwise you will have a hard time with CD-ROM images smaller than 150MB. No patch is required on setupapp.exe in this version of the driver.

[jimmsta]

This is awesome. Thanks for the contribution to these old builds!

[voidp]

Very much appreciated!

[louisw3]

wow that's pretty awesome!

[SistemaRayoXP]

Does this works in Final Windows NT 3.1?

[Beluga]

more specifically from builds 297 onwards.

[jinzou ningen]

That's awesome, thanks

[condor.07]

I tried this method, it works but on some languages from problems

Here's what happens in the Japanese version Build 531:



Every time I try to install the operating system I get the error in the penultimate image


Here's what happens in the Dutch version 3.10.5098.1



It comes out this error and can not continue with the installation


Last problem detected ... it works perfectly on VirtualBox, QEMU... but on VMWare with any configuration it exits this error




If anyone has a solution or answer to these problems I would be very happy

Thank you

[TheCollector1988]

VMware has problems with this, already known, so, don't use it for NT 3.1.

Note: 3.10.5098.1 is actually 3.10.511.1, don't trust the file version of the kernel, just trust what's actually inside the kernel.

[condor.07]

ok but why do not the Japanese and Dutch versions work?

[TheCollector1988]

The Japanese version works on my end with this driver I built.

[condor.07]

The Japanese version works on my end with this driver I built.

can I know what you have tested with the operation?
I tried it on VirtualBox 5.2 and QEMU
as the pictures show, it does not work
thank you

[TheCollector1988]

I've used 86box.

[condor.07]

I've used 86box.

same problem ...
thanks anyway

[TheCollector1988]

Also on 86box, you may use the SCSI adapters it emulates instead of atapi, for example, the Trantor 130B, Buslogic ISA/MCA/VLB/PCI (ISA compatibility), Aha154x or Aha164x MCA and 53c810 PCI, all of which have drivers for NT 3.1, and many of which NT 3.1 has built-in drivers for.

[backtofuture]

I can integrate the ATAPI.SYS file directly into the CD-ROM
I mean, at boot I have to select A: \ to find the Driver
I would like to integrate it into TXTSETUP.SIF, in this way it searches automatically
this is the TXTSETUP.OEM file

Code: Select all

[Disks]

d1  = "ATAPI CD-ROM Device Driver Installation Disk" , \atapi.sys, \

[Defaults]

scsi = Atapi

[scsi]

Atapi = "ATAPI CD-ROM Driver"


[Files.scsi.Atapi]

driver = d1, atapi.sys, Atapi


[Config.Atapi]

value = "", tag, REG_DWORD, 3
value = "", ErrorControl, REG_DWORD, 0
value = "", Group, REG_SZ, "SCSI miniport"
value = "", Start, REG_DWORD, 1
value = "", Type, REG_DWORD, 1

[Config.Dummy]

how do i integrate it into the TXTSETUP.SIF file?
however it is true, with the languages in Japanese and Dutch it does not work ...