Set Up Master/Slave Drive Relationships using Windows ME and Partition

[Guest_imported]

I am planning on setting up my new 45 gig hard drive using Windows ME and Partition Magic 6.0. My old machine has all of my important data on it and I would like to store it in one partition in my new hard drive.
My plan is to temporarily hook up my old hard drive to my new computer as a secondary hard drive, then dump the data into the new partitioned drive and then un-attach them and replace it back into the old machine and F Disk it before I sell it.
How does Windows Me react to a secondary hard drive and will a Plug and Play feature be able to find it after I set the jumpers or will I have to change any CMOS or BIOS settings?
Thanks in advance please feel free to recommend any web sites that might help.

 

[chiph]

You shouldn't have any problems doing this.

Your PC mfr probably hooked your CD/DVD drive up as the "slave" to the hard drive "master", so you'll need another cable to hook up your old drive.

The only potential problem is if you install new software while the old drive is connected -- adding the old drive will push your CDROM drive letter up, and if your new software records the drive letter, it may have problems after you remove the old drive.

Chip H.

 

[Alt255]

Also, since this was posted in the General Security Discussion forum and I assume you are worried about the existing data on the hard drive you plan to sell, remember that fdisk doesn't wipe the disk. It only changes, at most, 32 bytes on the disk (if it has one partition). Those bytes are very easy to reconstruct, allowing unrestricted access to everything on the drive.

You might, at least, consider obtaining the appropriate low-level format utility for the drive to prevent the next user from using your credit card numbers.

Just a thought....

Alt255@Vorpalcom.Intranets.com
​

"To run Visual Basic, you must have certain hardware and software installed on your computer.
• Any IBM-compatible machine with an 80286 processor or higher.
• One megabyte of memory."

Visual Basic Programmer's Guide