A friend of mine has an old system -- Shuttle Hot433 MB, AMD 486-DX4 CPU, Windows 95 OSR2 OS -- which she uses for word processing mainly. It was crashing and when I checked she had the HD almost filled to capacity, so I offered to install a new HD for her. I bought a Maxtor 13.6 Gig drive and a Promise Ultra 33 controller -- since the motherboard BIOS could not handle the large drive. Installed the Promise and the Maxtor without problem, FDISKed and FORMATed the drive to a single 13.6 partition and then tried to copy the old C drive, 1.2Gig, to the new Maxtor using the MAX Blast software. It can't see the drive. Maxtor says there is no way their software will work with the Promise controller. They suggested I just install the Maxtor on the secondary of the MB even though the BIOS can't see the full size. I tried that and no matter what I do, the system hangs as soon as it sees the Maxtor during bootup.
I have concluded two things from this. Maxtor tech support is non existent and do not volunteer to fix a friends old computer.
Any one have a suggestion of how to get around the problem? I had planned to copy the old C drive to the new Maxtor, set the Maxtor active so her system booted from the Maxtor and leave the old 1.2 Gig drive in her machine as an archive for Word Perfect documents -- which she prepares as a business. I have system transfer disks from Western Digital, IBM and other manufacturers, but they all expect to see one of their drives as the destination in the drive copy operation, and abort ther operation if they do not.
I have concluded two things from this. Maxtor tech support is non existent and do not volunteer to fix a friends old computer.
Any one have a suggestion of how to get around the problem? I had planned to copy the old C drive to the new Maxtor, set the Maxtor active so her system booted from the Maxtor and leave the old 1.2 Gig drive in her machine as an archive for Word Perfect documents -- which she prepares as a business. I have system transfer disks from Western Digital, IBM and other manufacturers, but they all expect to see one of their drives as the destination in the drive copy operation, and abort ther operation if they do not.