I have a problem installing Windows NT 4.0 Workstation and Windows 2000 Professional. The entire installation process is successful, the computer restarts after the installation is completed. The system gets up and the system boot bar is displayed, but when the "graphic board" is about to pop up, the computer shows a blinking dash in the upper left corner of the screen and it stays like that (I waited 1 hour). The system does not respond to ALT + CTRL + DEL. I am enclosing a link to the start-up video after installation. https://vimeo.com/553705781
Where could the problem be?
Yes, I know, it shows a fan error - I don't have a second CPU fan (the one on the back of the case), but it is on its way and will be installed in days
I would like to add that the installation of Windows 2003 Server runs fine on the same hardware.
greetings
See if a linux live distro runs on the system. It may pick up the fault and display it. Or it just may run as it should 😉
There's a glitch in the matrix.
A founding member of the 286 appreciation society.
Apparently 32-bit is dead and nobody likes P4s. Of course, as always, I'm open to correction...😉
Might be worth installing the latest ROMPaq firmware (sp17300) and trying again - from your video it looks as if you're on v2.17, and there have been 4 or 5 updates since then
v3.05 ROMPaq for Professional Workstations SP750 and AP550 (686J4 ROM)
Hi! I guess I have the guilty party. The system freezes while turning on the AGP.
The LIVE distribution I reviewed was Linux AUROX Live 9.1, whose ISO image was / is dated 2003.
However, I am still wondering WHY installing a newer system like Windows 2003 and Windows XP is smooth?
The Compaq SP750 has a dedicated Windows NT 4.0 WKS as the operating system.
So I am still looking for a solution - I am asking for comments and suggestions.
Greetings.
Hi! After updating the firmware from 2.17 to 3.05 there is a slight progress. Linux Live (Aurox 9.1) starts without any problems, but still Windows NT 4 and Windows 2000 stop in the same place - so the firmware update did not help for them.
Tested on Radeon 9200, Riva TNT 32, 3dLabs Oxygen GVX1.
If necessary, I will put photos from the BIOS settings - maybe I have something wrong here. In addition, I wonder why Windows XP / 2003 and newer systems install / work without problems, and there are problems with NT 4 and Windows 2000?
I am still asking for help!
I have to look for a PCI graphics card and then we'll see if anything changes.
Greetings.
Hi! Another attempt with a PCI graphics card S3 ViRGE/DX (attached image) gives exactly the same results as described in the 1st and 2nd post.
I am asking for help in solving the problem. Let me remind you that Windows XP / 2003 and newer install without hassle.
Greetings.
OK - I took pictures of the BIOS settings (in my opinion the ones that are important). Please have a look and see if there is something wrongly set / configured.
I have no idea for this computer anymore. Yes, I could install XP or something newer, but I have a dozen servers and I wanted to finally have a real client running Windows 2000 and / or Windows NT 4.
Maybe you will finally be able to install one of the above systems.
As you can only attach 5 attachments, I allowed myself to put the photos on an external hosting.
Greetings.
Can't see anything particularly out of place in the BIOS screenshots...I had a look at the old CUSTOMER ADVISORIES on archive.org but again nothing relating to your issue
If its not a video thing, maybe it has something to do with the hdd...what's the make / model no. of your 4.33GB drive (although these were mainly based on SCSI storage, there were options for 7.2K ATA-6 drives between 20-40GB)
[...]
Hit F5 before the "press F6 for setup device" message shows and you'll get a menu that allows you to specify hardware type.
Unfortunately, the F5 key does not work during startup. And when the message "Press F6 ..." is displayed, when starting Windows 2000 the F5 key has the same operation as F5 - so there is no additional option ...
Thanks for the hint though.
----------------------
Additionally, I tried to install Windows 2000 and Windows NT 4 WKS with ONLY one CPU in slot "0" - but the same system behavior 🙁
-----------------------------------------
Here is the disk I am using. It is connected to the PRIMARY channel and set as MASTER.
Waiting for a 68pin SCSI drive. We'll see what he shows ...
Hello after the break 😉
I finally got a SCSI disk (68pin). The model I have is the IBM Ultrastar DDYS-T18350 18.2GB. Connected to channel A as a device with ID 2. Bios and Adaptec's software detects it.
With this disc, I took it a step further - namely:
Win NT 4 - exactly the same behavior as in the first post,
W2K - System boots but confuses after loading MUP.SYS file / driver. (photo attached)
I changed the RAM - still the same.
So continue please for help and suggestions for this computer.
Regards.
In a situation where Windows has a mysterious booting problem, you might like to download WinDbg and try remote kernel debugging to search for the root cause.
I would like to add that the installation of Windows 2003 Server runs fine on the same hardware.
I just spotted this and it made be wonder exactly which NT4, does it include SP6 ? I know that pre SP5 there was no support for big disks, but can't remember the size limits. I think then even with SP6 the boot partition MUST be < 4GB.
I would try creating a 1GB FAT-16 C: and a 1GB FAT-16 or NTFS D: and install NT4 onto D: with boot.ini, etc. ending up on the FAT-16 C:. If NT4 then plays ball create other volumes for W2K/2K3/etc..
I just looked at one of my systems and the volume and partition setup is as below.
Welcome!
Thanks for the response. However, either I wrote it wrong or you misunderstood 😉
Windows XP installs without any errors or anything else. Installs great and works flawlessly.
Windows NT 4.0 "hangs" during booting (movie in 1 post). I even tried to start the computer without HDD - same effect. So I am betting the disks / partitions (size / quantity / filesystem) do not cause an error.
Windows 2000 can be installed on a SCSI and IDE disk (information in previous posts), but restarting the system after installation causes what I described in previous posts.
However, in order to reassure me and you 😉, I will make a test installation on a 1GB hard disk (or more precisely on a CompactFlash card). Because only such a medium with this capacity can I access.
I'll be in touch soon, then. Regards.