Hi, for my first post, let me relate a familiar scenario..... P111 650, just move an Adaptec 2940UW SCSI and IBM high speed SCSI drive from another machine into this one. Windows REFUSES to install on the SCSI drive - just locks up half way through installing devices. All BIOS/HArdware configurations tried, so gave up and chalked one up to Bill Gates. So. I did a clean install on the 1st partition of the (only) IDE drive, installed partition magic and copied the partition to the SCSI drive, selecting the same drive letter and that it be hidden. This went OK, but Part magic screwed up on reassigning drive letters. Bah. I used the Windows 2000 install disk to put things right. Using the recovery console I renamed the /winnt directory, then I used the installer to delete the old IDE partition, rebooted - this time install presented the SCSI as Drive C: I went ahead with install, which let me set up an 8Mb partition on the IDE for the boot manager. The install was left to run until the first reboot. Then I used the recovery console to put /winnt back where it was and the system booted OK. But I can't log in. I've worked out that the system still has the drive identified as D: If anyone can help, I'd like to know how to change the drive letter from the recovery console? I reckon the win install route doesn't work because when asked to format the drive (SCSI) I chose leave intact. Coming from a UNIX background I really don't have the mindset of "It's broken - reinstall from scratch". I know Part Magic screwed up, but I can't face going through th entire procedure again with another piece of software instead - that is equally likely to screw up. I'm 99% of the way to getting this to work, surely there is a 1% that can let me change this drive letter. Microsoft support Article, Q249321 goes on to describe the symptoms of not being able to log and points to article Q223188 which describes exactly how to change the registry to effect a drive letter change. But It's solution is to use the registry editor, for which you have to be able to log in. (MS are soooooooooooo stupid). HELP!!! I've read a lot of posts on this forum and I realise there are some ways of achieving a result. I have a LAN, but the machine in question is not visible on the LAN, (and I can't log in to make it visible). Can anyone give advice on how to edit the registry from the recovery console? or to establish a LAN connection when I can't log in? PS. Had I thought of it earlier I would have got networking sorted on the machine before I did the drive copy, so I could administer remotely, but hey. will so if I MUST rebuild.

Right - fixed it meself. What I did was this - Isolate all machines on the network apart from the problem machine and one other. I then set the other machine to have IP address 192.168.0.170 - this was picked up by the other machine (Default IP on install is 192.168.0.169). Also, sounds obvious, but make sure that the machine names aren't the same - we were building a machine to replace one other on the network - and so fell into this trap. Then, follow the instructions in Microsoft article Q223188 on their support site. You don't need to be registered to get the article. This describes how to use regedit.exe to fix the problem remotely. Regedit.exe and regedt32.exe both have right click options which allow connection to a remote machine. Use this to change the registry and you can change drive letters easily to your hearts content!!!! I was well pleased with the result, just had to share it.