Omega Owners Forum
Chat Area => General Discussion Area => Topic started by: LouisCorney on 01 April 2008, 19:44:29
-
... and probably very basic.
I've installed a fresh XP install on a hard drive, then put it in another. It doesn't work, keep getting:
"NTLDR is missing
Press Ctrl Alt Del to Restart"
or, when using a bootable repair CD this:
"Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware. Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information."
What have I done wrong?
I also keep getting an occasional BSOD :(
(Additional info: I installed XP onto H:\ drive of a computer, then using it as C:\ in the new one. Don't have XP CD,its on a DVD hence reason for doing it this way)
-
... and probably very basic.
I've installed a fresh XP install on a hard drive, then put it in another. It doesn't work, keep getting:
"NTLDR is missing
Press Ctrl Alt Del to Restart"
or, when using a bootable repair CD this:
"Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware. Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information."
What have I done wrong?
I also keep getting an occasional BSOD :(
(Additional info: I installed XP onto H:\ drive of a computer, then using it as C:\ in the new one. Don't have XP CD,its on a DVD hence reason for doing it this way)
Basically it wont work the way you are trying to do it..........
And by the sounds of it.......you are trying to illegaly install XP....... :-X
-
Basically it wont work the way you are trying to do it..........
Is there a way that would work?
-
have i got this right, you installed windows then removed the hdd an placed in another base unit, check the jumpers are either set to master if its on its own on the ide cable or master or slave if its with another drive like dvdrw, othey must be opposits, and in the correct place on the ide
-
... and probably very basic.
I've installed a fresh XP install on a hard drive, then put it in another. It doesn't work, keep getting:
"NTLDR is missing
Press Ctrl Alt Del to Restart"
or, when using a bootable repair CD this:
"Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware. Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information."
What have I done wrong?
I also keep getting an occasional BSOD :(
(Additional info: I installed XP onto H:\ drive of a computer, then using it as C:\ in the new one. Don't have XP CD,its on a DVD hence reason for doing it this way)
Basically it wont work the way you are trying to do it..........
And by the sounds of it.......you are trying to illegaly install XP....... :-X
As millions of others have done, we are all guilty of something like that, cannot tell me different..........just dont broadcast it.
-
... and probably very basic.
I've installed a fresh XP install on a hard drive, then put it in another. It doesn't work, keep getting:
"NTLDR is missing
Press Ctrl Alt Del to Restart"
or, when using a bootable repair CD this:
"Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware. Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information."
What have I done wrong?
I also keep getting an occasional BSOD :(
(Additional info: I installed XP onto H:\ drive of a computer, then using it as C:\ in the new one. Don't have XP CD,its on a DVD hence reason for doing it this way)
Won't work unless machines are near identical. Easier to swap the DVD drive, then install.
Not that XP was ever available (legally) on a DVD.
-
But as a clue, your issue is boot.ini and the way the differnt computers determine disks.
-
... and probably very basic.
I've installed a fresh XP install on a hard drive, then put it in another. It doesn't work, keep getting:
"NTLDR is missing
Press Ctrl Alt Del to Restart"
or, when using a bootable repair CD this:
"Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware. Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information."
What have I done wrong?
I also keep getting an occasional BSOD :(
(Additional info: I installed XP onto H:\ drive of a computer, then using it as C:\ in the new one. Don't have XP CD,its on a DVD hence reason for doing it this way)
Basically it wont work the way you are trying to do it..........
And by the sounds of it.......you are trying to illegaly install XP....... :-X
As millions of others have done, we are all guilty of something like that, cannot tell me different..........just dont broadcast it.
Agreed :y
Perhaps an admin could lock this thread.......until its been proved that origanal poster is trying to instal XP legally :y
-
But as a clue, your issue is boot.ini and the way the differnt computers determine disks.
Yeah I thought that might be it.
Thanks for the advice and pointing me in the right direction guys.
Don't mind this thread being removed if it hints at anything illegal (I've still got XP serial, just lost the original CD, this isn't illegal is it?)
-
But as a clue, your issue is boot.ini and the way the differnt computers determine disks.
Yeah I thought that might be it.
Thanks for the advice and pointing me in the right direction guys.
Don't mind this thread being removed if it hints at anything illegal (I've still got XP serial, just lost the original CD, this isn't illegal is it?)
If your got a gen serial no for XP.....then prob not........sorry but the way the question was asked.....and as TB said XP want released on DVD.....i thought the same.....the thread sounded dodgey......
-
No probs... though you did have me worried :y
As you can probably tell, I'm a beginner when it comes to PCs
-
Good luck, but swap the dvd drive over with CD, and build XP on the PC that the HDD belongs to is best option ;)
-
If you haven't fixed the problem is a quick solution (By the way this is a common problem even on genuine versions normally happens when transfering everything onto a new hard drive.
First of all put your xp disk into your cdrom drive and let computer boot off it. When you get option to repair computer (Press R) hit R
Once on DOS screen type
copy e:/i386/ntldr c:/
copy e:/i386/ntdetect c:/
(Where e:/ is the drive letter of your cd drive. It might be d:/ depends on how many drives you have)
Once both these files have copied remove the XP cd and reboot the system.
Hope this helps at least somebody
-
If you haven't fixed the problem is a quick solution (By the way this is a common problem even on genuine versions normally happens when transfering everything onto a new hard drive.
First of all put your xp disk into your cdrom drive and let computer boot off it. When you get option to repair computer (Press R) hit R
Once on DOS screen type
copy e:/i386/ntldr c:/
copy e:/i386/ntdetect c:/
(Where e:/ is the drive letter of your cd drive. It might be d:/ depends on how many drives you have)
Once both these files have copied remove the XP cd and reboot the system.
Hope this helps at least somebody
Very unlikeyl these 2 files are missing. Or even corrupt. ntldr missing is 99% normally the boot.ini. ntdestect errors haven't been an issue since NT4 RTM!
-
Had the same problem few weeks ago. believe me it works. Also this is the solution as published in the MCP 70-720 examination guide.
If you oot from the XP disk as you would when you do a fresh install if there is already a version on the harddrive it will give you a repair option.
-
Also shown here (see method 2)
http://support.microsoft.com/kb/318728
-
Had the same problem few weeks ago. believe me it works. Also this is the solution as published in the MCP 70-720 examination guide.
If you oot from the XP disk as you would when you do a fresh install if there is already a version on the harddrive it will give you a repair option.
Yup, fully aware of the repair processes. Should be after working with NT since 3.5, and using it since the initial 3.1 ;)
I would suggest if that fixed it, then a user with admin rights had deleted them.
Oh, and don't pay too much attention to the knowledge you gained to pass your MCP - MS training (except the infrastructure design courses) and reality are miles apart (hence why when I sit in on recruiting interviews, I pay no regard to MCSE).
-
Also shown here (see method 2)
http://support.microsoft.com/kb/318728
Which confirms what I said - boot.ini. ntdlr missing is aways a fault in boot.ini. Esp if you read the circumstances of the OP moving the HDD between machines. It will be the boot.ini
Oh, and did I mention boot.ini? Coz it will be the rather boot.ini!
-
I know what you are saying but didn't want to go too deep into the whole process. Was just posting a possible solution. As to infrastructure Thats going to be my next exam which I'm not looking forward to.
-
Hope they ask you how not to do a link.!!!!!!!!!!!!!!!1 :(
-
Hope they ask you how not to do a link.!!!!!!!!!!!!!!!1 :(
Funny ;D
-
I know what you are saying but didn't want to go too deep into the whole process. Was just posting a possible solution. As to infrastructure Thats going to be my next exam which I'm not looking forward to.
The clue was in the post - moving HDD. The disk numbering will be screwed, hence making boot.ini invalid. Wouldn't be the ntldr/ntdetect files missing, as it boots in one machine.
Obviously, shouldn't move disks like that, as all the wrong drivers, and if done properly (unlikely given the circumstances we know) the chipset drivers will cause a boot failure later in the boot sequence, once the kernel mode driver loads.
Infratsructure is pretty easy if you understand TCP/IP and assocaited technologies, esp DNS (which is dead easy, esp with Microsoft's half baked implementation). Just the AD part to worry about. IIRC, FSMOs aren't part of it, but GCs are, as is replication/ntfrs/sites and service/rdns. Not sure if WINs is in the 2003 one - it was in 2000 one. DHCP/DNS/Kerberos/PKI etc are all standard Internet stuff, and should be easy for anyone working in the industry.
Good luck with exam :)
-
To be honest guys I have no idea what you are talking about :-[ Sounds very impresive though. ;D ;D ;D
-
Cheers for that. Have just rebooked 70-290 (windows server 2003) after failing by 2% so gonna have another crack at that then onto windows server 2003 Network Infrastructure.
-
Cheers for that. Have just rebooked 70-290 (windows server 2003) after failing by 2% so gonna have another crack at that then onto windows server 2003 Network Infrastructure.
Ah, thats not good.
Its been a while, but IIRC, Server MCP covers Server and XP Pro? Which bit were your week on?
-
I know what you are saying but didn't want to go too deep into the whole process. Was just posting a possible solution. As to infrastructure Thats going to be my next exam which I'm not looking forward to.
The clue was in the post - moving HDD. The disk numbering will be screwed, hence making boot.ini invalid. Wouldn't be the ntldr/ntdetect files missing, as it boots in one machine.
Obviously, shouldn't move disks like that, as all the wrong drivers, and if done properly (unlikely given the circumstances we know) the chipset drivers will cause a boot failure later in the boot sequence, once the kernel mode driver loads.
Infratsructure is pretty easy if you understand TCP/IP and assocaited technologies, esp DNS (which is dead easy, esp with Microsoft's half baked implementation). Just the AD part to worry about. IIRC, FSMOs aren't part of it, but GCs are, as is replication/ntfrs/sites and service/rdns. Not sure if WINs is in the 2003 one - it was in 2000 one. DHCP/DNS/Kerberos/PKI etc are all standard Internet stuff, and should be easy for anyone working in the industry.
Good luck with exam :)
Totally agree, however a "fix" that sometimes works - about 75% - is to boot to the windows CD, work to the install screen where it says it has found a previous windows install, the choose "R" for "repair install" [note : this is different to the repair consol screen that goes to DOS]
Windows will delete and reinstall many files from this point on AND rewrite boot.ini .. it works very well most of the time. Takes about 40 minutes. Then install the drivers for the new motherboard etc etc
as I said .. not gauranteed but about a 75% success rate, and keeps all loaded programs intact .. :)
-
Had a few problems with Terminal Security Services
-
Good luck, but swap the dvd drive over with CD, and build XP on the PC that the HDD belongs to is best option ;)
This sorted it, and some other niggling problems :y
-
I know what you are saying but didn't want to go too deep into the whole process. Was just posting a possible solution. As to infrastructure Thats going to be my next exam which I'm not looking forward to.
The clue was in the post - moving HDD. The disk numbering will be screwed, hence making boot.ini invalid. Wouldn't be the ntldr/ntdetect files missing, as it boots in one machine.
Obviously, shouldn't move disks like that, as all the wrong drivers, and if done properly (unlikely given the circumstances we know) the chipset drivers will cause a boot failure later in the boot sequence, once the kernel mode driver loads.
Infratsructure is pretty easy if you understand TCP/IP and assocaited technologies, esp DNS (which is dead easy, esp with Microsoft's half baked implementation). Just the AD part to worry about. IIRC, FSMOs aren't part of it, but GCs are, as is replication/ntfrs/sites and service/rdns. Not sure if WINs is in the 2003 one - it was in 2000 one. DHCP/DNS/Kerberos/PKI etc are all standard Internet stuff, and should be easy for anyone working in the industry.
Good luck with exam :)
Totally agree, however a "fix" that sometimes works - about 75% - is to boot to the windows CD, work to the install screen where it says it has found a previous windows install, the choose "R" for "repair install" [note : this is different to the repair consol screen that goes to DOS]
Windows will delete and reinstall many files from this point on AND rewrite boot.ini .. it works very well most of the time. Takes about 40 minutes. Then install the drivers for the new motherboard etc etc
as I said .. not gauranteed but about a 75% success rate, and keeps all loaded programs intact .. :)
And quicker to rebuild from scratch ;)