Primary Disks thinks it E: not C:

[ericksot]

I have a user who has a problem on a hdd. He took the problem hdd out of the machine and placed it in another machine as a slave. When he booted the machine up the HDD he put in as a slave came up as C: and the Primary came up as E:. He fixed the problem with the HDD and took it out of the machine and put it back in its original CPU and booted it up and it works fine. When he tried to boot up the CPU he used to fix the drive it won't boot, and tells him he has no swap space. I am figurinng for what ever reason it still thinks it is E: not C: and W2k has C: listed for the swap space. Has anyone ran into this? If so any suggestions.

TIA

 

[chpicker]

The simplest answer I can come up with is that he hooked the drives up wrong, either to the wrong IDE channel or had the jumpers set incorrectly. The BIOS actually assigns the drive letters to the drives in the order it finds them...the drives themselves have no clue and don't care what letter they are assigned.

Otherwise, I'm a bit confused as to the last part of the problem with Win2k. Which machine is giving the swap space error?

 

[ericksot]

Thats what I thought, but I must walk softly he is our hardware tech and we don't see I to I on setting the jumpers. Both machines are running W2k. The machine he used to fix the problem HDD is the one giving the error. Before he put the problem hdd in the machine was working fine.

 

[chpicker]

What exactly does the swap space error say? When does it come up? Are you able to get into Windows in spite of the error, or does it halt the boot process?

 

[ericksot]

It halts the process

 

[butchrecon]

Can he boot into Safe Mode? Also is the partition marked as active (using FDISK). Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.


James Collins
Computer Hardware Engineer
A+, MCP

email: butchrecon@skyenet.net

 

[philanrandi]

either you are right or he is!!! i think it is the jumper settings on problem drive are master! on the other computer the other drive is set for "detect drive"