Jump to content

Recommended Posts

Posted (edited)

Hi,

I am wanting to install Windows 2000 on a Dell Latitude 5490, a Kaby Lake machine. I've installed XP with XP2ESD 1.7 by @George King, and Windows Vista and Windows 7 on that laptop. And before anyone says it, no, I am not going to use a VM. And also, the legacy internal boot wouldn't be a problem, as even though it isn't supported, I can use something like WinSetupfromUSB to get around it as legacy external boot is supported. What would I need to do to get 2000 running on the Dell? The laptop has no CD drive, so I would have to install with USB. I have a SATA m2 SSD and USB 3.0. Also, @George King ported the Windows 8 drivers to Windows XP for AHCI and USB 3.0 in the XP2ESD pack, would they work on 2000? And how would I get ACPI working on 2000?

Edited by GD 2W10

Posted (edited)
On 7/19/2023 at 10:19 PM, GD 2W10 said:

Hi,

I am wanting to install Windows 2000 on a Dell Latitude 5490, a Kaby Lake machine. I've installed XP with XP2ESD 1.7 by @George King, and Windows Vista and Windows 7 on that laptop. And before anyone says it, no, I am not going to use a VM. And also, the legacy internal boot wouldn't be a problem, as even though it isn't supported, I can use something like WinSetupfromUSB to get around it as legacy external boot is supported. What would I need to do to get 2000 running on the Dell? The laptop has no CD drive, so I would have to install with USB. I have a SATA m2 SSD and USB 3.0. Also, @George King ported the Windows 8 drivers to Windows XP for AHCI and USB 3.0 in the XP2ESD pack, would they work on 2000? And how would I get ACPI working on 2000?

I tried another Windows 2000 ISO which had SATA drivers integrated into it. I installed with WinNTSetup and got past "Setup is starting Windows 2000" when pressing F7, but keyboard didn't work at all. I get the following error:

"The following value in the -SIF file used by Setup corrupted or missing: Value 1 on line 0 in section [Keyboard] Setup cannot continue. To quit Setup. press F3."

I can't turn on legacy keyboard emulation because my BIOS doesn't give an option for that and the laptop is too new. How do I get around this?

 

w2kproerrordelllatitude.jpg

Edited by GD 2W10
Posted
19 hours ago, GD 2W10 said:

I tried another Windows 2000 ISO which had SATA drivers integrated into it. I installed with WinNTSetup and got past "Setup is starting Windows 2000" when pressing F7, but keyboard didn't work at all. I get the following error:

"The following value in the -SIF file used by Setup corrupted or missing: Value 1 on line 0 in section [Keyboard] Setup cannot continue. To quit Setup. press F3."

I can't turn on legacy keyboard emulation because my BIOS doesn't give an option for that and the laptop is too new. How do I get around this?

 

w2kproerrordelllatitude.jpg

The only way which worked with me  is to create hfslip iso of blackwingcat :

http://blog.livedoor.jp/blackwingcat/archives/1823238.html

Disable the UAC if you use win vista and later in procedure of creation.

Posted

Almost every drivers in XP2ESD package are based on NTOSKRNL_EMU project. Sadly, it doesn't support Windows 2000.
You can find some modded drivers (Intel AHCI, acpi.sys, USB 3.0, etc) in @blackwingcat's blog and his update center. http://win2k.org

  • 7 months later...
Posted

Only throwing things on the wall and see if anything sticks but for what it costs I would try both:

[Keyboard]
kbdhid   = "USB Keyboard",files.kbdhid,kbdhid
USB      = "USB Keyboard",files.kbdhid,kbdhid

and:

[Keyboard]
STANDARD = "USB Keyboard",files.kbdhid,kbdhid
kbdhid   = "USB Keyboard",files.kbdhid,kbdhid
USB      = "USB Keyboard",files.kbdhid,kbdhid

and see what happens, though I remember seeing a lot of people having issues with attempts to install 2K with only USB mouse and keyboard on more modern hardware.

I don't think a "working for all" solution exists, maybe - if you *somehow* manage to workaround the error - some "fully unattended setup" you may get past the text mode and hve later in the GUI a fully working keyboard, but cannot really say.

Search on the board for related posts by bluebolt and tomasz86, they did a lot of work attempting to workaround similar USB keyboard issues, maybe some of those posts can provide some inspiration.

jaclaz

Posted
5 hours ago, jaclaz said:

Only throwing things on the wall and see if anything sticks but for what it costs I would try both:

[Keyboard]
kbdhid   = "USB Keyboard",files.kbdhid,kbdhid
USB      = "USB Keyboard",files.kbdhid,kbdhid

and:

[Keyboard]
STANDARD = "USB Keyboard",files.kbdhid,kbdhid
kbdhid   = "USB Keyboard",files.kbdhid,kbdhid
USB      = "USB Keyboard",files.kbdhid,kbdhid

and see what happens, though I remember seeing a lot of people having issues with attempts to install 2K with only USB mouse and keyboard on more modern hardware.

I don't think a "working for all" solution exists, maybe - if you *somehow* manage to workaround the error - some "fully unattended setup" you may get past the text mode and hve later in the GUI a fully working keyboard, but cannot really say.

Search on the board for related posts by bluebolt and tomasz86, they did a lot of work attempting to workaround similar USB keyboard issues, maybe some of those posts can provide some inspiration.

jaclaz

I will try that 

Posted
6 hours ago, jaclaz said:

Only throwing things on the wall and see if anything sticks but for what it costs I would try both:

[Keyboard]
kbdhid   = "USB Keyboard",files.kbdhid,kbdhid
USB      = "USB Keyboard",files.kbdhid,kbdhid

and:

[Keyboard]
STANDARD = "USB Keyboard",files.kbdhid,kbdhid
kbdhid   = "USB Keyboard",files.kbdhid,kbdhid
USB      = "USB Keyboard",files.kbdhid,kbdhid

and see what happens, though I remember seeing a lot of people having issues with attempts to install 2K with only USB mouse and keyboard on more modern hardware.

I don't think a "working for all" solution exists, maybe - if you *somehow* manage to workaround the error - some "fully unattended setup" you may get past the text mode and hve later in the GUI a fully working keyboard, but cannot really say.

Search on the board for related posts by bluebolt and tomasz86, they did a lot of work attempting to workaround similar USB keyboard issues, maybe some of those posts can provide some inspiration.

jaclaz

Ok so both changes gave me a BSOD. The first one gave me 0x01E, the second one gave me 0x07B.

  • 1 year later...
Posted (edited)
21 hours ago, GD 2W10 said:

Is there a way to get 2k to support textmode drivers?

Yes, Windows 2000 does support the installation of drivers while the Windows installation is still using a text mode. At the beginning of the installation you are being asked to press [F6] to install additional drivers.

Is there any specific problem you encountered? Are you looking for a solution to use additional drivers without the need to press a key on your keyboard?

Edited by Start Me Up
Posted (edited)
1 hour ago, Start Me Up said:

Yes, Windows 2000 does support the installation of drivers while the Windows installation is still using a text mode. At the beginning of the installation you are being asked to press [F6] to install additional drivers.

Is there any specific problem you encountered? Are you looking for a solution to use additional drivers without the need to press a key on your keyboard?

I meant PNP vs text mode drivers, like txtsetup.oem and txtsetup.sif.

Would the F6 thing work? Bc I might be able to get it working on the laptop, but I only have SATA and USB port because it’s Kaby Lake. 

Edited by GD 2W10
Posted (edited)
7 hours ago, Start Me Up said:

Yes, Windows 2000 does support the installation of drivers while the Windows installation is still using a text mode. At the beginning of the installation you are being asked to press [F6] to install additional drivers.

Is there any specific problem you encountered? Are you looking for a solution to use additional drivers without the need to press a key on your keyboard?

UPDATE: 

I was able to bypass the 0x07B BSOD. I used WinSetupFromUSB (which uses Grub4DOS) to emulate a floppy (by editing winsetup.lst) and put the UniATA files in there while booting from a HD with DOS 7.1 + vanilla Win2k SP4 setup installed. I pressed F5 --> Standard PC and F6. I loaded the UniATA driver. It booted and brought me to the Welcome to setup screen. BUT I cannot interact with it, so I have the keyboard issue from earlier.

I only used WinNTSetupfromUSB so I could have a way to get to the hard drive (bc i have an artifical block by BIOS on internal drives)

 

This is what my winsetup.lst looks like:
 

Quote

color black/cyan yellow/cyan
write 0x8274 0x2001
timeout 10
ls /windefault > nul && default /windefault

title ...Back to Main Menu
ls /usbdrive.tag > nul || find --set-root --devices=hf /usbdrive.tag > nul
configfile /menu.lst

title \n
root


title Auto-detect and use F6 SATA/RAID/SCSI Driver\nUse if your internal disk is not detected or getting BSOD 0x0000007B\nSelect once before Text mode of Setup or starting PE1\nCurrently 32 bit versions are supported.\nCreated by Chenall (www.chenall.net/) & Modified by Steve Si (www.rmprepusb.com)
#http://bbs.wuyou.com/viewthread.php?tid=197550
#http://chenall.net/
#http://www.rmprepusb.com
map --unmap=0:0xFF
map --unhook && map --rehook
ls /DPMS/DPMS.ISO > nul || find --set-root --devices=hf /DPMS/DPMS.ISO
map /DPMS/DPMS.ISO (0xfa)|| map --mem /DPMS/DPMS.ISO (0xfa)
map --hook
root (0xfa)
set FIRA=0
/dpms2.g4b 0
ls (0)/txtsetup.oem && map (0) (1) && set DPMS=1
map --unmap=0xfa
map --rehook
ls /usbdrive.tag > nul || find --set-root --devices=hf /usbdrive.tag
configfile /winsetup.lst


title Auto-detect and use F6 SATA/RAID/SCSI Driver + Firadisk\nTry this entry if the one above does not work on particular machine\nUse once, before Text mode of Setup
#http://bbs.wuyou.com/viewthread.php?tid=197550
#http://chenall.net/
#http://www.rmprepusb.com
map --unmap=0:0xFF
map --unhook && map --rehook
ls /DPMS/DPMS.ISO > nul || find --set-root --devices=hf /DPMS/DPMS.ISO
map /DPMS/DPMS.ISO (0xfa)|| map --mem /DPMS/DPMS.ISO (0xfa)
map --hook
root (0xfa)
set FIRA=0
/dpms2.g4b 0
ls (0)/txtsetup.oem && map (0) (1)
map --unmap=0xfa
map --rehook
ls (0)/txtsetup.oem && set LOADFIRA=1 && set DPMS=1
ls /usbdrive.tag > nul || find --set-root --devices=hf /usbdrive.tag
configfile /winsetup.lst


#F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6# #DO NOT REMOVE THESE LINES 


title \n
root

title First part of Windows 2000 SP4 setup from partition 0
set ISOPATH=/WINSETUP/20SP4.ISO
if NOT %DPMS%==1 map --unhook
if NOT %DPMS%==1 map --unmap=0:0xff  && map --rehook
savedefault +1
ls /shifthd.bat > nul || find --set-root --devices=hf /shifthd.bat
/shifthd.bat
root (hd%RDSK%,0)
ls %ISOPATH% > nul || find --set-root --devices=h %ISOPATH%
map --mem %ISOPATH% (0xff)
map --e820cycles=3
map --rehook
ls (0xff)/ > nul && root (0xff)
ls (0xff)/ > nul || echo Fatal error while creating virtual disk 0xFF...
if "%RDSK%"=="" pause Fatal error while swapping hard disk order, cannot continue! && configfile /winsetup.lst
if not %RDSK%==1 ls (0xff)/I386/TXTSETUP.SIF > nul && cat --locatei=rdisk(1) --replace=rdisk(%RDSK%) (0xff)/I386/TXTSETUP.SIF
if not %RDSK%==1 ls (0xff)/AMD64/TXTSETUP.SIF > nul && cat --locatei=rdisk(1) --replace=rdisk(%RDSK%) (0xff)/AMD64/TXTSETUP.SIF
if %LOADFIRA%==1 ls (0xff)/I386/TXTSETUP.SIF > nul && cat --locatei=;;FIRA;; --replace=;;FIRA\r\n (0xff)/I386/TXTSETUP.SIF
ls /I386/SETUPLDR.BIN > nul && set LDR=/I386/SETUPLDR.BIN
chainloader %LDR%
pause --wait=1 Launching Setup from (hd%RDSK%,0)
boot
#we should not get here but just in case of errors above...
map --unhook
map --unmap=0:0xff && map --rehook

title First part of Windows 2000 SP4 setup from partition 0 (with driver floppy)
set ISOPATH=/WINSETUP/20SP4.ISO

# Unhook/unmap if DPMS isn't active
if NOT %DPMS%==1 map --unhook
if NOT %DPMS%==1 map --unmap=0:0xff && map --rehook

# Save position for second part of setup
savedefault +1

# Find and run disk remap script
ls /shifthd.bat > nul || find --set-root --devices=hf /shifthd.bat
/shifthd.bat

# Set up drive root
root (hd%RDSK%,0)

# Make sure ISO exists
ls %ISOPATH% > nul || find --set-root --devices=h %ISOPATH%

# Map the Windows 2000 ISO to (0xff) as RAM drive
map --mem %ISOPATH% (0xff)

# Map floppy image as drive A: (fd0)
find --set-root /driver.img
map --mem /driver.img (fd0)

# Activate mappings
map --e820cycles=3
map --rehook

# Switch to ISO root
ls (0xff)/ > nul && root (0xff)
ls (0xff)/ > nul || echo Fatal error while creating virtual disk 0xFF...

# Fail-safe if RDSK is not set
if "%RDSK%"=="" pause Fatal error while swapping hard disk order, cannot continue! && configfile /winsetup.lst

# Patch rdisk if needed
if not %RDSK%==1 ls (0xff)/I386/TXTSETUP.SIF > nul && cat --locatei=rdisk(1) --replace=rdisk(%RDSK%) (0xff)/I386/TXTSETUP.SIF
if not %RDSK%==1 ls (0xff)/AMD64/TXTSETUP.SIF > nul && cat --locatei=rdisk(1) --replace=rdisk(%RDSK%) (0xff)/AMD64/TXTSETUP.SIF

# Patch FIRA if enabled
if %LOADFIRA%==1 ls (0xff)/I386/TXTSETUP.SIF > nul && cat --locatei=;;FIRA;; --replace=;;FIRA\r\n (0xff)/I386/TXTSETUP.SIF

# Set and chainload setup loader
ls /I386/SETUPLDR.BIN > nul && set LDR=/I386/SETUPLDR.BIN
chainloader %LDR%
pause --wait=1 Launching Setup from (hd%RDSK%,0)
boot

# Fallback cleanup
map --unhook
map --unmap=0:0xff && map --rehook


title Second part of Windows 2000 SP4 setup + Remap Driver IMG
savedefault

# Map floppy image into memory as A:
find --set-root /driver.img
map --mem /driver.img (fd0)
map --hook

# (Optional) Run disk swap script if needed
ls /shifthd.bat > nul || find --set-root --devices=hf /shifthd.bat
/shifthd.bat

# Make sure we have a valid target
if "%RDSK%"=="" pause Fatal error while swapping hard disk order, cannot continue! && configfile /menu.lst

# Chainload to internal HDD (Win2K setup will continue)
pause --wait=1 Booting MBR on hd0 with driver.img loaded as floppy A: ...
chainloader (hd0)+1
rootnoverify (hd0)
boot

title Boot Windows 2000 Setup ISO
find --set-root /win2k.iso
map --mem /win2k.iso (0xff)
map --hook
chainloader (0xff)/I386/SETUPLDR.BIN
boot

title \n
root
 

image_2025-06-07_201420909.png.9d0703051bcd6bebe7b2e95eb52874cc.png

Edited by GD 2W10
Posted (edited)
On 6/8/2025 at 2:08 AM, GD 2W10 said:

It booted and brought me to the Welcome to setup screen. BUT I cannot interact with it, so I have the keyboard issue from earlier.

There are 2 (or 3) post SP4 Windows updates which fix USB problems during the installation. But, they are both for the second phase when you see the graphical user interface. So my guess is, that Windows 2000 somehow uses the BIOS for keyboard input support during the first phase while you see the text based user interface.

KB823086.htm KB829759.htm KB838417.htm

Edited by Start Me Up

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...