VOGONS


First post, by appiah4

User metadata
Rank l33t++
Rank
l33t++

System specs are:

ASUS P2B-F
Celeron 533 on ASUS S370 Slocket
2x 128MB PC133 RAM
Seagate 80GB HDD (Primary Master)
LG DVD-ROM (Secondary Master)
GeForce FX5200
AWE64 Value
Zoltrix AV310

Installation of DOS on a 2GB Primary partition (C:) worked fine and that OS appears to be fully functional.

So the issue is, during copying of files to an NTFS partition on the same drive (D:) I always start getting errors near 70% mark. Setup complains about a file on the hard drive not being correct, and no amount of retrying fixes that.

The things I tried so far:
- Replace optical drive
- Replace ribbon cable
- Replace installation CD

All of these were no go. Interestingly enough it's always the same file that causes the hiccup until I do a cold boot, and then I start getting the error on another file, seemingly.

At this point I'm thinking I probably have a stick of bad RAM in there. So today I will try the RAM sticks separately and maybe try replacing both at some point.

Any other suggestions? Anyone else had this issue before?

Retronautics: A digital gallery of my retro computers, hardware and projects.

Reply 2 of 9, by xrror

User metadata
Rank Newbie
Rank
Newbie

I was going to say there was some weirdness with making bootable partitions past 2GB with some BIOS, but I guess with win2k and NTFS it was 8GB where things got weird. So that kinda shot my theory on "probably not this, but weird things I remember from back in the day."

In a totally different direction, I used to have awesome "luck" running the horribly unsupported (but awesome!) practice of just sticking with FAT32, and running both DOS/9x and NT/2K from the same partition sharing the Program Files dir. Just set the default win dir for win2k to... well WIN2K works.

Yea it's really really REALLY wrong but most apps of the era worked both in 9x and NT/2K. So dirty it hurts.... 🤣

EDIT ADD: to be more relevant. Try just "swapping" your ram sticks. like stick in slot 1 put into 2. slot 2 into 1. If your errors suddenly start at 30% there you go.

Reply 3 of 9, by bakemono

User metadata
Rank Oldbie
Rank
Oldbie

Is the error from attempting to read a file or to write one? Does the BIOS properly support an 80GB disk? Does the HDD have bad sectors?

Never heard about any problem with partition size under Win2k until you go beyond 128GB. At least not for service pack 3 and later.

It's true that it will run fine from FAT32, I've been doing it for 18 years. The default directory for 2k is WINNT so that's not even a concern.

yet another retro game on itch: https://90soft90.itch.io/super-wild-war-22

Reply 4 of 9, by comp_ed82

User metadata
Rank Newbie
Rank
Newbie

Bakemono already mentioned some of the things I'd want to eliminate as part of the diagnostic process, but I'd also add trying the drive on its own cable & controller (if possible) and I also wonder about the drive temperature.
I've had 80GB IDEs and SATAs start to give me errors when they get overheated (over 50-55 C). At least you're not using Maxtor drives..
Is there any way you can get some active airflow over the drive during installation?

Reply 5 of 9, by red-ray

User metadata
Rank Oldbie
Rank
Oldbie
appiah4 wrote on 2021-01-07, 06:20:

So the issue is, during copying of files to an NTFS partition on the same drive (D:) I always start getting errors near 70% mark. Setup complains about a file on the hard drive not being correct, and no amount of retrying fixes that.

How was D: created? How did you create the extended partition? If you used MS-DOS I suspect this is the root cause of your issues.

I would put the drive into a Windows 2003 or earlier system and use that to create the extended partition and logical drivers. As a minimum create them when installing W2K.

One of my quad boot systems is as below. I tend to copy the CDs onto the KITS disk and install from there.

file.php?id=99820

Attachments

  • RK3.png
    Filename
    RK3.png
    File size
    24.18 KiB
    Views
    266 views
    File license
    Public domain

Reply 6 of 9, by Towncivilian

User metadata
Rank Newbie
Rank
Newbie

Have you verified the installation media isn’t damaged in some way? You could try to install Win2k in a virtual machine using that installation CD to ensure it is capable of a proper installation.

HP d530 CMT: P4 EE 3.2GHz, 4GB DDR-400, ATI Radeon 9600XT, SB X-Fi XtremeMusic, WD VelociRaptor 80GB, WD Caviar Blue 500GB

Reply 7 of 9, by appiah4

User metadata
Rank l33t++
Rank
l33t++

It was RAM. I removed both sticks and stuck in a PC66 64MB known good stick, and Windows 2000 installation completed without issues.

Now I will need to do some RAM testing with memtest86. Fun times.

Retronautics: A digital gallery of my retro computers, hardware and projects.

Reply 8 of 9, by appiah4

User metadata
Rank l33t++
Rank
l33t++

One of the 128MB sticks was throwing crazy amounts of RAM errors, replacing that fixed everything!

Retronautics: A digital gallery of my retro computers, hardware and projects.

Reply 9 of 9, by pentiumspeed

User metadata
Rank l33t
Rank
l33t

See? This came from a discovery decades ago when I worked with a smart guy who ran his computer business, he said that was memory issue if any of the blue screen or odd problems with windows in general.

I had seen this happen occasionally including our family's computer that had third-party memory. Replacing the set fixed that.

Cheers,

Great Northern aka Canada.