Thanks, but, that was already tried, we even tried putting in the specs manually, still, no good.
Are both the drives from the same manufacture, are they the same size, you may have an ez-bios, ez-drive, drive-max whatever you call it / bios conflict. Check Western Digitals support pages that explain ez-bios in detail.
The old HD is sitting in a Dell GXa, the new drive is a Seagate 4.3G, which is the replacement drive, we have done this several times without any problems, win95 and NT, it's just that this one and another seem to have this problem. Thanks for the quick reply.
I'll take two... CPU's
One hard drive spins up and initializes faster than the other one does.
This will sometimes cause other problems also. Usually you see this only with pairing an old drive with a new one, and usually the old one wins!
SCSI drives usually have a jumper setting to delay the spin up to avoid this, but ide's usually don't.
gosh, all the responds were sucky.
first of all, did u try to use partition to partion? or disk to disk??
1-if u trying to use disk to disk, dont format the NEW harddrive, just copy to it.
2-the problem can also be if u r using the master hard drive as a slave . try changing the jumper to master when using as a single drive.
3-also, try using just regular version 5.1 fro norton, it sometimes better then the updated one.
I'll take two... CPU's
Gee...unknown is sucky too!
We replaced the old drive, so that is no longer even in the pc. We are at one hd now, we did do a disk to disk copy without formatting, it is using an ntfs file system, compressed, I do appreciate the attempted help though.
This even has our NT guru scratching his head, so I know it isn't an easy one, unless it's one of those that's so easy, everyone overlooked it.
Ghost and NT4.0 (sp4)
We used ghost ver. 5.1d to image a hard drive to another larger hard drive, the source drive was compressed. When we booted to the new drive, we got an error that the primary disk was not found, hit f1 to proceed, or f2 to enter setup. When f1 is selected, it boots fine with no other error messages, like normal. The bios detected the hard drive correctly. This has happened to us on another machine, we used a win 95 image and it worked well. Symantec web site had some closely related situations on their support page, but none of them worked, any others with this wonderful experience? Thanks in advance.
Next time, Hit F2 and go into the bios and change the seeting to "AUTO detect" for your harddrive(s). The bios was probably set up specifically for your old harddrive. Canging to Auto should clear this up.
New Security Features Planned for Firefox 4
Another Laptop Theft Exposes 21K Patients' Data
Oracle Hits to Road to Pitch Data Center Plans
Microsoft Preps Array of Windows Patches
Microsoft Nears IE9 Beta With Final Preview
Simplified Analytics Improve CRM, BI Tools
Android Passes RIM as Top Mobile OS in 2Q
VMware Updates Hyperic System Management
File Monitoring Key to Enterprise Security
LinkedIn Snaps Up SaaS Player mSpoke