'Computer management' isn't a feature of the earlier Windows OS's
Are you making sure you are changing the drive id 'jumpers', and using the correct cable connectors, when you're moving these drives from system to system? If you are simply unplgging them from one machine, and plugging them into another, switching from 'Master' to 'slave' position as you go, then that won't work.
You need to corrctly configure each drive for the position it's being moved to.
Catweazle
Grandad
4,335 posts since Mar 2004
Reputation Points: 229
Solved Threads: 149
Yes, definitely make sure the master/slave jumpers on the drive are set correctly for the drive's location on the new computer's IDE chain.
If the jumpers are set correctly, open a DOS box and see what the "fdisk" has to report about the drive.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
DaveSW, that's not correct. Drives being limited to the speed of the slowest unit on the cable is only something that related to quite old systems. Most modern systems can run the drives at their correct speed, and that has been the case for some years now!
The feature is called "Independent Device Timing", and is so much a standard now that you don't see it even get a mention ;)
Catweazle
Grandad
4,335 posts since Mar 2004
Reputation Points: 229
Solved Threads: 149
The delay in boot times is a different thing to the actual speed of operation. Just because booting up is taking longer doesn't mean the drive is operating slower.
The behaviour you describe is most likely a delay in drive detection during POST, due to the configuration used.
Catweazle
Grandad
4,335 posts since Mar 2004
Reputation Points: 229
Solved Threads: 149