• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Installing a hard drive, problems.

FireCrack

Junior Member
Recently, as in the past few days. I have been trying to take a hard drive from a 486 computer (Seagate ST3120A) and install it into my newer computer.

Anways, i've gotten as far as getting my bios to recognise it (primary slave) but now windows either doesnt load (hangs at loading screen) or takes an inornately long time to load. The little thng that moves at the loading screen is still moving, but nothing happens, it just stays there.

So, can anyone offer some help? My motherboad is an ASUS A7N8X deluxe, the "old" hard drive is set as my primary slave and my normal hard drive is my primary master. My OS is windows XP.

If you need any more infromation just ask.
 
Did you check to make sure the old hard drive has its jumper set to Slave? I've had times where I "know" I looked, but when I go back to check again, the jumper wasn't set properly...

Also, since the old drive is probably ATA 33 at best, and likely even PIO 3 or slower, it's possible your Windows drive doesn't want to play nice with it. Try putting the old hard drive on your second IDE channel as primary or slave (whatever isn't being used on that channel) to see what happens.
 
You shouldn't use that hard drive on the same channel with the primary disk. If I remember correctly, on the same ribbon cable (or IDE controller) there can not be different addressing modes (like PIO and UDMA). This means that your primary hard drive will work very very slow.
Put it on another channel - you could even put it in the place of the CDROM for the time you need to move data
 
Well, it turns out i lost my patience, downloaded a linux liveCD, and just used it to copy my data to my normal HDD.

Thanks anyways though!

Ok, new problem, using knoppix i have no write acess to my disks? Any linux gurus (or mabye just people who know where the write acces switch is) care to help out?
 
Originally posted by: FireCrack
... and just used it to copy my data to my normal HDD.

Did you really? Then your next question would not be necessary.

Do not lose your patience and do not look for more problems. Walk away from the problem and allow yourself time to think it through to consider your options with less stress on your shoulders.

Due to the proprietary nature of MS Windows, it is difficult for the open source and Linux communities to create drivers to write data to NTFS filesystems. This assumes your partition is NTFS. If the partition is FAT, then Linux is able to write to the partition. Just mount the drive with the msdos switch and all is done. Google for "mount" and possibly "mount msdos". You could even try "mount ntfs" if you like.

It is not mentioned whether the second drive is being hooked up to work as additional permanent storage or only for long enough to copy the files over to the newer hard drive. If only the files are needed and no success is met with installing the old drive in the new system, then just put the old drive back into its original system and connect the two computers through a network or crossover cable to copy the data. If the drive is wished to serve as additional permanent storage, then I suggest putting the old drive as a slave to the secondary cable and recheck the jumpers for all connected devices.

Good luck with it.
 
Hehe, i had just come to edit my previous post that the problem had been solved (for real this time).

No i did not copy the data previously, as i couldnt get write acess, shoulda changed that part of the post too.

Anyways, it was basicly me being lazzy and not doing a 15 second google search on "Knoppix write premission"

Thanks anyways

(yes, I created a small FAT partition for doing this)
 
Very good. It is good to hear of your success. I assume then you learned about the mount command under unix. It is a good command to know for future or even daily use.
 
Back
Top