Xp Pro Boot up problem

[Guest]

Hi,
my computer 2.4 GH had D: Xp Pro and G: windows 2003.
For some stupid reason i changed the drive letter of my Xp Pro partition to
C: with the help of third party software. That sowtware asked me to reboot my
computer in order to make changes. But after i reboot i could never boot in
again in my xp pro. It shows black Xp Pro screen and then it changed to blue
windows Xp Pro screen and then it goes no where from there.
But i can boot with my W2K3. And over there in My computer it shows my Xp
Pro partition is still D: drive and W2K3 is G:

what do u guys suggest? can fix this problem. I tried to boot in with safe
mode in Xp Pro but no luck.

 

[Pegasus \(MVP\)]

Hi,
my computer 2.4 GH had D: Xp Pro and G: windows 2003.
For some stupid reason i changed the drive letter of my Xp Pro partition to
C: with the help of third party software. That sowtware asked me to reboot my
computer in order to make changes. But after i reboot i could never boot in
again in my xp pro. It shows black Xp Pro screen and then it changed to blue
windows Xp Pro screen and then it goes no where from there.
But i can boot with my W2K3. And over there in My computer it shows my Xp
Pro partition is still D: drive and W2K3 is G:

what do u guys suggest? can fix this problem. I tried to boot in with safe
mode in Xp Pro but no luck.

You write "It shows black Xp Pro screen and then it changed to blue
windows Xp Pro screen and then it goes no where from there." Can
you be a little more specific? What do you mean with "nowhere"?

Also: Is this machine networked? If it is, can you ping it while it
goes "nowhere"?

 

[Guest]

You write "It shows black Xp Pro screen and then it changed to blue
windows Xp Pro screen and then it goes no where from there." Can
you be a little more specific? What do you mean with "nowhere"?

Also: Is this machine networked? If it is, can you ping it while it
goes "nowhere"?


No it's not network. It's all on my hard driver.

No where mean, my machine is dual boot if i select XP Pro to boot it shows
black with big logo of Windows Xp Pro. Then the black screen changed to blue
screeen with small logo on the screen shows Microfsoft Windows Xp, and then
it looks like it is ready to go to my desktop any time but it never make it,
just stay there on blue screen. does nothing. i have to reboot manually back
to get OS selection window.

 

[Guest]

if u read my Question care fully, as i mentioned i have two OS running in my
computer D: drive Xp Pro and G: drive windows 2003.
And for some stupid reason i changed my Xp Pro partition drive letter from
D: to C:.
And after that i'm unable to boot back in my Xp Pro partition.

 

[Pegasus \(MVP\)]

No where mean, my machine is dual boot if i select XP Pro to boot it shows
black with big logo of Windows Xp Pro. Then the black screen changed to blue
screeen with small logo on the screen shows Microfsoft Windows Xp, and then
it looks like it is ready to go to my desktop any time but it never make it,
just stay there on blue screen. does nothing. i have to reboot manually back
to get OS selection window.

Not having the machine networked makes things much harder.
You have to edit the registry in order to restore the original
drive letter of your WinXP installation. Here is how you can
do it from within Win2003:

1. Run regedit.exe.
2. Single-click HKLM.
3. Click File / Load Hive
4. Type x:\Windows\System32\config\system {OK}
(or whatever the exact location of the WinXP SYSTEM file is)
5. Type MountedDevices {OK}.
6. You will get a new key called "Mounted Devices". Single click it.
7. Click File. The item "Unload Hive" must NOT be greyed out. If it is
then you're in the wrong spot.
8. Navigate to the key "MountedDevices" inside the current key.
9. Identify the value that refers to the bad WinXP drive letter. It
looks like so: \DosDevices\C:.
10. Rename this value back to \DosDevices\D:.

Your underlying problem is, of course, that you are using the
extremely basic boot manager that is native to WinXP/2003.
You would be far better off by using a proper boot manager
such as XOSL (which is free!). It lets you run numerous OSs,
each in its own partition which is visible as drive C:, and each
completely independent from the others. Unfortunately you
cannot easily use XOSL now unless you have a small empty
or a small FAT partition on any of your disks.

 

[Pegasus \(MVP\)]

if u read my Question care fully, as i mentioned i have two OS running in my
computer D: drive Xp Pro and G: drive windows 2003.
And for some stupid reason i changed my Xp Pro partition drive letter from
D: to C:.
And after that i'm unable to boot back in my Xp Pro partition.

I am quite aware of that!

 

[Guest]

the easiest way to resolve the problem get your xp instilation cd and go
through reinstalling the windowsxp chose new instalation the it will try to
discourage you but continue the a screen will come do you want to repair
thats when u click the oproprait key the process should take about 35 mints
depending upon your speed good luck


"

 

[Pegasus \(MVP\)]

the easiest way to resolve the problem get your xp instilation cd and go
through reinstalling the windowsxp chose new instalation the it will try to
discourage you but continue the a screen will come do you want to repair
thats when u click the oproprait key the process should take about 35 mints
depending upon your speed good luck

That may be so but you should point out to the OP that
he will not only have to re-install WinXP but also all his
applications. BTW, have you considered adding some
punctuation to your replies? It would make them much
easier to read.

 

[Guest]

Thanks a alot as u said i did and it fixed my xp pro boot up problem. right
now i'm using xp pro the one i had problem.
thanx again.
I 've one more question, lets say if i had no W2K3 installed on my computer
than what was the other way to fix this problem.

 

[Z]

Thanks a alot as u said i did and it fixed my xp pro boot up problem. right
now i'm using xp pro the one i had problem.
thanx again.
I 've one more question, lets say if i had no W2K3 installed on my computer
than what was the other way to fix this problem.

If you take the time now to make yourself an Ultimate Boot CD for
Windows, you'll have what you need should the PC in trouble not have
another Windows installation on it.

http://www.ubcd4win.com

The process is a bit involved, but if you print out and follow the
directions, and take your time, you'll end up with a valuable tool.
UBCD4WIN has a registry editor and many other tools (eg: Password Renew).


A brief explanation from ubcd4win.com:

UBCD4Win is a bootable CD which contains software that allows you to
repair/restore/diagnostic almost any computer problem. All software
included in UBCD4Win are freeware utilities for Windows®. UBCD4Win uses
Bart's PE© to boot into a Windows® "pre-install" environment, basically
Windows® booted from CD. With network support, the ability to modify
NTFS volumes, recover deleted files, create new NTFS volumes, scanning
hard drives for viruses, etc. this project is almost everything you need
to repair your system problems.

There are many other types of utilities included to allow you to recover
and/or repair a damaged system. Additional applications included are CD
Burning, Backup/cloning, Defragmenters, Password recovery, the list goes
on!! Please visit the "List of Tools" page for a complete list of what
is included in the latest version of the project.

 

[Pegasus \(MVP\)]

Congratulations!

If you don't have a dual-boot installation then still have several
options to fix this problem, some of which are obvious:
a) Temporarily install the problem disk as a slave disk in some
other WinXP/2000 PC, then edit the registry hive as you did.
b) Boot the machine with a Bart PE boot CD (www.bootdisk.com),
then do the same thing again.
c) Boot the machine with a Nordahl boot diskette
(http://home.eunet.no/~pnordahl/ntpasswd/bootdisk.html), then
do the same thing again, this time from a Command Prompt.
It works but it's pretty tough going.

 

[Z]

b) Boot the machine with a Bart PE boot CD (www.bootdisk.com),
then do the same thing again.

Have you tried the UBCD4Win? Its built on Bart's PE.

 

[Pegasus \(MVP\)]

Have you tried the UBCD4Win? Its built on Bart's PE.

No, I haven't. What can UBCD4Win do that the Bart PE cannot do? How much
does it cost?

 

[Z]

No, I haven't. What can UBCD4Win do that the Bart PE cannot do? How much
does it cost?

It comes with a lot of extras on the CD. Its free.

http://www.UBCD4win.com

 

[Guest]

you know what i tried to install XOSL but i couldn't install. Do u know any
other free multi boot software that can let me boot 2-3 windows OS and 2-3
Linux OS.

 

[Guest]

Congratulations!

If you don't have a dual-boot installation then still have several
options to fix this problem, some of which are obvious:
a) Temporarily install the problem disk as a slave disk in some
other WinXP/2000 PC, then edit the registry hive as you did.
b) Boot the machine with a Bart PE boot CD (www.bootdisk.com),
then do the same thing again.
c) Boot the machine with a Nordahl boot diskette
(http://home.eunet.no/~pnordahl/ntpasswd/bootdisk.html), then
do the same thing again, this time from a Command Prompt.
It works but it's pretty tough going.

 

[Pegasus \(MVP\)]

I don't but I'm sure there are others. What seems to be the
problem with the XOSL installation? What brand PC is it?

 

[Guest]

Well i tried to install on my XP Pro NTFS active partition and i also tried
to install on fresh partition Fat32 200 MB and through floppy diskett as
well, every time it gives me same error.
"16 bit MS-DOS Subystem
c:\xosl\Install.exe
The system cannot open COM2 port COM3 port requested by the application.
Choose 'Close' to terminate the application."
My system is 2.4GHz,
Motherboard Name: Intel
Memory Slots
DRAM Slot #1 512 MB (PC2100 DDR SDRAM)
DRAM Slot #2 512 MB (PC2100 DDR SDRAM)

 

[Timothy Daniels]

I don't but I'm sure there are others. What seems to be the
problem with the XOSL installation? What brand PC is it?

Is XOSL still being developed/maintained/supported?
Lots of Google references to XOSL seem to have
petered out a few years ago.

*TimDaniels*

 

[Guest]

Is XOSL still being developed/maintained/supported?
Lots of Google references to XOSL seem to have
petered out a few years ago.

*TimDaniels*

So what are u using for multibooting?