I have a custom built AMD Duron 900+ processor, with Windows 2000 built in on a 3.4GHz HDD, but I wanted to put Windows XP Pro on a new HDD(20gig), but everytime I go to install XP on the computer I get all the way to the screen where you see the installtion happen, but then I get to crash(blue) screen with error message saying that Windows has shut it's self down to prvent problems, if you know any information on helping me, please let me know, thank you.
2000 to XP help....
- Thread starter irkorn18
- Start date
How did you setup the second drive? Did you set it as master with the end connector on the cable plugged into it? Or did you set it as the slave drive using the middle connector on the cable? If neither of those were done the dirve isn't being seen by the installer itself. In some cases you may have to set the added drive to the cable select position to be seen by the bios which provides the needed drive information to the XP installer.
Well, I put the 2000 one with matser, and XP with slave, then I set XP to master, when I completely disconnected the 2000 drive, and it still would go through set up either way, and I set the 2000 to master, with the middle connector, and XP with the end connector, I guess I will try them opposite of that, but I still don't understand if I set it to master and it's the only drive on there, with an end or middle connection that it doesn't let me completely set up XP with it.
it was my dad's boss's old computer, they got new Dell P4's there, so they gave me this, and they had a computer company make this awhile ago, but they did stick a 3.4gig HDD in there, but it has 684(?) close to that RAm, and it has a VIA(from what I see) motherboard in it, not sure of the model# or anything, but they BIOS you can tweak....what other info do you need?
The way you connected the drives answers the problems with the installer seeing the drive. Unless you have an ide drive set to the cable select position a master is always seen with the end connector. That's the master position on the cable. With it set to master on the middle one you're not going to get anywhere!
First you will have to decide which OS and drive you want as the primary there. With both drives connected the installer will ask whether you want to install XP onto drive #1 or #2. The installer will also ask if you want XP installed onto the 20gb drive where it will show the total amount of drive available. Since no partitioning and formatting has been done the installer will proceed to create the new primary on the drive as you follow the onscreen instructions.
If everything goes well and you have both drives connected during the installation XP will take over at bootup showing a screen where you let XP load after some 30 seconds or use one the arrow keys to select 2000 and press the enter key. This will due to the boot loader file in XP having added the 2000 option in the boot.ini file.
First you will have to decide which OS and drive you want as the primary there. With both drives connected the installer will ask whether you want to install XP onto drive #1 or #2. The installer will also ask if you want XP installed onto the 20gb drive where it will show the total amount of drive available. Since no partitioning and formatting has been done the installer will proceed to create the new primary on the drive as you follow the onscreen instructions.
If everything goes well and you have both drives connected during the installation XP will take over at bootup showing a screen where you let XP load after some 30 seconds or use one the arrow keys to select 2000 and press the enter key. This will due to the boot loader file in XP having added the 2000 option in the boot.ini file.
Well, I took my original HDD out of the computer, installed 2000 pro onto a new HDD and the only HDD that will work in the computer is the original HDD, what does this mean? I've used every jumper setting and inside BIOS I've done everything to try to get it to load correctly, but I keep getting the blue screen when another HDD tries loading on the computer....
Your initial problem was setting the jumpers incorrectly since the position on the cable determines which drive is master or slave. For a dual drive - dual OS setup there you had the master(2K HD) set as slave and slave(XP HD) set as the master. Setting the one on the middle connector or both to the cable select position could see them both run. You have 2000 on the 3.5gb drive already.
Unless the 20gb is defective which I doubt you forgot that XP was partially installed to that drive. The 2000 installer is bound to crash trying to overwrite the files copied already by a newer version of Windows! The question now is why you are trying to install 2K on the drive you wanted XP on?
Unless the 20gb is defective which I doubt you forgot that XP was partially installed to that drive. The 2000 installer is bound to crash trying to overwrite the files copied already by a newer version of Windows! The question now is why you are trying to install 2K on the drive you wanted XP on?
Well, I wanted 2000 on my 20 gig, but I couldn't find my cd, so I already had XP, in which I thought I could just plug it in, and it'd recognise it and I'd be fine, and go run XP on the computer, but then it didn't work, so I just wanted to get 2000 to work on the computer for now, so I decided to just clear the HDD and put 2000(I have my XP HDD, so it's not loss) but now that I have done that, I'm just getting the blue screen displaying INACCESSIBLE_BOOT_DEVICE, in which I can't really find much feedback on how to solve this problem. I have just the new 2000 HDD hooked up, and I've had it on cable select, and master, but it doesn't change anything...
The error message there points at one of two things. 1) improper hookup 2) bad hard drive or bad cable If you have been running the old drive on the same cable but the cable is an older 40/40 not an 80/40 that would explain a lot of things right off.(40wire/40pin - 80wire/40pin)
That would mean that the smaller drive was an ATA66 drive while the larger 20gb model is an ATA100. Normally this would be covered by the backward compatibility to older boards newer drives have. That must have been one of the first boards running a Duron cpu if that is an ATA66 drive being run there. 95 systems saw 500mb, 1, 1.2, 1.4, 1.5, 2, and 2.5gb hard drives as well as some larger 3.5, 4, and even 5gb drives.
That would mean that the smaller drive was an ATA66 drive while the larger 20gb model is an ATA100. Normally this would be covered by the backward compatibility to older boards newer drives have. That must have been one of the first boards running a Duron cpu if that is an ATA66 drive being run there. 95 systems saw 500mb, 1, 1.2, 1.4, 1.5, 2, and 2.5gb hard drives as well as some larger 3.5, 4, and even 5gb drives.