W2K SP4 goes ito loop after setup (NOT the cdrom problem)

PC is as Duron 900, 256 MB RAM, standard PC. ASll the parts have been tested.Is running on An ASUS Motherboard. No overclocking was ever done to it. Worked fine for a year.


The machine was installed with a downloaded copy of windows 2000 and ran fine for about a year. There was no servicepack installed. Then the owners decided to get legal and bought a windows 2000 SP4 Article Number:x05-22708

First a repair installation was tried, but setup replied that a sp4 cd could not update this. So we downloaded the servicepack4 from the internet and installed it with no problem.

The repair installation went smooth and easy, the new product key was entered and all looked ok.

Upon reboot after install, we encountered a error : SAS window: winlogon.exe - Application Error
        The instruction at "ox..." referenced memory at "0x..". The memory
could not be "written".
        Click OK to terminate the application.

We thought annother repair install might cure it. A googler search yielded nothing and it was late.

Now after setup when the PC switched into GUI mode it rebooted, started again, brought a black screen ("setup is restarting") and the rebooted.

After several attempts I removed the CD and found out that windows 2000 was searching for a file called nt5inf.cat. When it found the file, it rebooted without a word.

So i extracted nt5inf.cat from a servicepack 4 I had downloaded, (4 copies in 4 folders I386/ia  /ip  /id  /is) and tried them all with the same result.

As this file is a security catalogue i reckon it somehow found out that an illegal copie was used. But why are we prevented from going legal.

Upon closer examination of the CD I found the word OEM on it.

Anybody can help me with that? I am ready to shell out 500 points.
HarkonAsked:
Who is Participating?
 
PashaModConnect With a Mentor Commented:
PAQed - no points refunded (of 500)

PashaMod
Community Support Moderator
0
 
bkoehler-mprCommented:
Back up the data, clear the mbr, format the drive, and reload the OS.

OEM Windows 2000 is meant for a fresh install.
0
 
HarkonAuthor Commented:
Jeez, bKoehler,

is there not a workaround? This is a 40 GB full of stuff and programs, 4 user installation.

This would cost me the weekend.   Sorry, cant accept that (as of yet)
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
bkoehler-mprCommented:
I would burn and rebuild (partition magic, make a second partition, move the data, reinstall the OS).

Check your ProductId in the registry, and then reinstall Service Pack 4 from the network download version.
0
 
nader alkahtaniNetwork EngineerCommented:
If the SAS is pressed during logon but before the logon script process has started, you may receive a BSOD (Blue Screen Of Death) due to a Winlogon.exe access violation.

 

http://www.aclass.com/nttips1.html
0
 
jkrCommented:
>>is there not a workaround? This is a 40 GB full of stuff and programs, 4 user installation

You could try an in-place upgrade which will keep the installations and users untouched and replaces the system files:

http://support.microsoft.com/default.aspx?scid=KB;en-us;292175& ("How to Perform an In-Place Upgrade of Windows 2000")
0
 
ewtaylorCommented:
Do you happen to have pcanywhere on this computer?
0
All Courses

From novice to tech pro — start learning today.