XP booting issue

  • Thread starter Thread starter John Putar
  • Start date Start date
J

John Putar

With lack of caution i installed win2000server onto same volume(HDD) where
winXP are, I fixed that, erasing the 'winNT'(win2000server) folder from HDD.
Then fixing XP installation again(fixmbr, bootcfg, fixboot)...
Now i have three booting options A B and C. Neither is working properly, it
says something about mising hal. file and something about win2000server in
the next two.
When changing fixboot and bootcfg then suddenly ther's two booting options B
and D. D(XP) is working fine. After restarting, then again three options.

Reinstall.isn't on my mind as an option. What to do?
 
John Putar said:
With lack of caution i installed win2000server onto same volume(HDD) where
winXP are, I fixed that, erasing the 'winNT'(win2000server) folder from
HDD. Then fixing XP installation again(fixmbr, bootcfg, fixboot)...
Now i have three booting options A B and C. Neither is working properly,
it says something about mising hal. file and something about win2000server
in the next two.
When changing fixboot and bootcfg then suddenly ther's two booting options
B and D. D(XP) is working fine. After restarting, then again three
options.

Reinstall.isn't on my mind as an option. What to do?
a mess. But is it solvable?
 
John said:
With lack of caution i installed win2000server onto same volume(HDD) where
winXP are, I fixed that, erasing the 'winNT'(win2000server) folder from HDD.
Then fixing XP installation again(fixmbr, bootcfg, fixboot)...
Now i have three booting options A B and C. Neither is working properly, it
says something about mising hal. file and something about win2000server in
the next two.
When changing fixboot and bootcfg then suddenly ther's two booting options B
and D. D(XP) is working fine. After restarting, then again three options.

Reinstall.isn't on my mind as an option. What to do?

Boot to the Windows XP installation and use the Msconfig utility to scan
and remove invalid paths in the boot.ini file.

John
 
solved! Thanks to mister in white ->>John John (MVP),
I used msconfig suggested and command prompt bootcfg options. I fixed it
manually over commnands, because didn't find any automatic problem
recognition actions.



wrote:
 
Back
Top