Installing Windows NT Server or Workstation on a Large IDE hard drive

Discussion in 'Windows XP / Older OS' started by wvv000, Aug 16, 2025 at 00:56.

  1. wvv000

    wvv000 MDL Addicted

    Feb 21, 2019
    701
    831
    30
    Code:
    If you are using Windows NT 4.0 Workstation, Server, or Terminal Server,
    follow these instructions:
    
    1. Download the updated Atapi.sys from Microsoft's FTP server
    
      
    
       and copy the file to a blank floppy disk. Run Atapi.exe on the diskette
       and the new Atapi.sys file will be extracted to the diskette. Label the
       disk "Microsoft ATAPI Service Pack 4 IDE Driver."
    
    2. Boot from the three setup disks supplied with Windows NT Server.
    
    3. When asked if you would like setup to detect your mass storage devices,
       press S so that detection is skipped and you specify a mass storage
       device.
    
    4. When setup list devices found, which should list <none>, press S again
       and insert the Microsoft ATAPI Service Pack 4 IDE Driver disk and press
       ENTER twice.
    
    5. After setup reads the disk and list the Microsoft ATAPI Service Pack 4
       IDE driver, press ENTER to accept the driver.
    
    6. Setup will now list Microsoft ATAPI Service Pack 4 IDE Driver as an
       installed driver. If you have additional drivers for other mass storage
       devices, press S; if not, press ENTER to continue through setup.
    
    7. Setup should continue through normally but, it will prompt you to insert
       the disk labeled "Microsoft ATAPI Service Pack 4 IDE Driver Support
       Disk" at the copy phase after you have chosen or formatted a partition
       on a hard drive.

    In a virtual machine, the file cannot be loaded or loading is unavailable, resulting in the large-capacity hard disk being unsupported. What are some feasible solutions?
     

    Attached Files:

  2. wvv000

    wvv000 MDL Addicted

    Feb 21, 2019
    701
    831
    30
    * Loading the driver by booting from the boot disk or CD is invalid
     
  3. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    2,864
    4,016
    90
    Did you write those files in ATAPI.7z/ATAPI.EXE to a floppy/floppy image?
     
  4. wvv000

    wvv000 MDL Addicted

    Feb 21, 2019
    701
    831
    30
    It must be loading the driver from the floppy disk. The startup disk loading driver is normal. At the beginning of the installation phase, it shows that the large hard disk cannot be recognized. The ISO is directly started and loaded with F6, and it shows that the driver cannot be loaded.
     
  5. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    2,864
    4,016
    90
    2025-08-16_033035.png

    2025-08-16_033104.png


    :huh: :hmm: ... i'll play around with this
     
  6. wvv000

    wvv000 MDL Addicted

    Feb 21, 2019
    701
    831
    30
  7. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    2,864
    4,016
    90
    @wvv000
    :good3:
    2025-08-17_084900.png
    2025-08-17_084948.png
    2025-08-17_085012.png

    Not done on this topic but I could load the driver.
    I just followed the readme instructions step by step.
    You need to do this with the floppies, booting from the cd would not work.
     
  8. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream
    Staff Member

    Dec 21, 2012
    7,314
    8,991
    240
    Clarified in the title that it also applies to Workstation.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. WindowsMyStyle

    WindowsMyStyle MDL Member

    May 2, 2018
    180
    85
    10
    Very rudimentary method...

    This is how I do it:

    Integrate the uniata.sys driver into the Bootable CD (you can find the method online)
    Overwrite the Windows 2000 SP4 NTDETECT.COM and NTLDR files on the CD
    Start the installation
    Format to the maximum allowed size (4 GB)
    Install SP6a (I don't know if it's necessary; I have it integrated into the installation)

    Use any program to change the hard drive size to whatever you want...

    Reboot the system

    Works perfectly in VirtualBox too

    VirtualBox_Windows NT 4_17_08_2025_14_26_54.png

    Thanks
     
  10. pammodnar

    pammodnar MDL Novice

    Dec 14, 2015
    31
    12
    0
    It's simple. I have replaced the atapi.sys file in nt4.0 ISO (I have Doesn'tWorkStation SP1) with atapi.sys version 4.0.1381.279 (I believe I took it out of SP6).
    There is no special recipe, just take the ISO, open it in ISO-editing program and replace atapi.sys in ISO in I386 directory. Save the ISO as new and it will happily install on larger drives in VM or PC.
     
  11. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    2,864
    4,016
    90
    Indeed and it was less hassle than using floppies, and faster too :)
     
  12. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    2,864
    4,016
    90
    I read about it, have not tried it yet but very nice approach indeed :)
    (still reading my self up on this one)
    :)
     
  13. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    2,864
    4,016
    90
  14. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    2,864
    4,016
    90
    On a sidenote, somebody knows why this setting is not honored? :hmm:

    2025-08-18_001827.png

    2025-08-18_001911.png
     
  15. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream
    Staff Member

    Dec 21, 2012
    7,314
    8,991
    240
    This setting is for hardware profiles. Set the boot selection delay directly in C:\boot.ini.

    nt4_bootsel_delay.png

    Alternatively, in the GUI here:
    nt4_bootsel_delay_GUI.png
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    2,864
    4,016
    90
    Excellent :hug2:

    Anyone hate this log on feature? I do... :D

    Bypass NT 4.0 logon.reg
    Code:
    REGEDIT4
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
    "DefaultUserName"="Administrator"
    "DefaultDomainName"="12345"
    "PowerdownAfterShutdown"="0"
    "DefaultPassword"=""
    "AutoAdminLogon"="1"
    
     

    Attached Files:

  17. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    2,864
    4,016
    90
    That's the max disk drive size Virtual PC 2007 managed to poop out :p

    2025-08-18_022928.png
     
  18. wvv000

    wvv000 MDL Addicted

    Feb 21, 2019
    701
    831
    30
    Since you asked this question, I would like to ask how to set up a normal shutdown of NT4 Terminal Server instead of logging off.
     
  19. WindowsMyStyle

    WindowsMyStyle MDL Member

    May 2, 2018
    180
    85
    10
    It's a limitation of the program, not of the operating system.


    I recommend UniATA over ATAPI because NOT support LBA48 (> 137 Gb) and UDMA (only PIO, SWDMA, MWDMA modes)

    I recommend using NTDETECT.COM and NTLDR of Windows 2000 SP4 for for better RAM management, this way you can get 3.5 GB
     
  20. Sajjo

    Sajjo MDL Member

    Feb 6, 2018
    2,864
    4,016
    90
    I was able to do a similare task on standard server, complete shutdown and power off - I can get back with some screenshots and how to later after testing with a terminal server.
    I did some trickery in register that i'm not sure is mandatory, but upgrading to latest service pack level and replace hal.dll with hal.dll.softex is "mandatory".
    I used the cmd version of shutdown found in resource kit for NT 4.0

    That is supported in VPC 2007.

    Btw, re-size disk drive beyond 7.8 GB before you do service pack update and... :eek::D

    2025-08-18_185304.png

    fyi :eekout: