Problem with Dual Boot...

  • Thread starter Thread starter Bill Whitney
  • Start date Start date
B

Bill Whitney

We have a small problem.

Until now I have been succesfully been using an MS-DOS / WinXP dual boot
system. MS-DOS for my outdated version of AUTOCAD 12 and WinXP for the
usual stuff.

Recently I started recieving an error message after the dual boot "Windows
XP Professional" selection section, which told me a corrupted file existed
with "windows/system32/config/system".

I am still able to use my MS-DOS partition happily, however whenever I try
WinXP is bombs out and asks me to intert my WinXP disk and press 'R' for the
recovery section.

And so I do so, following the instructions I:
(a) insert the disk,
(b) press 'R',
(c) wait for the computer to reset,
(d) I then press the 'anykey' to boot from the CD,
(e) after waiting for the computer to read the disk I press 'R' to enter the
repair section,
(f) I do not press F2 to enter the automated system repair function
(g) when the prompt arrives asking me which volume I wish to boot from I
press '1' which is for d:\windows to boot from (whoch happens to be the
CD-ROM)
(h) after this is done I reset the computer and go through the same old dual
boot process for getting on to XP and do so.

After I am done with XP I shut the computer down, however when I boot the
computer up again, I am confronted with the problem of the error again...

PLEASE CAN ANYONE HELP...

Regards,

Thomas and Bill Whitney
(e-mail address removed)
 
Sorry folks, but there just isn't enuff info here. For example:

1) Is your XP partition NTFS or FAT(/32)?
2) Can you start in Safe Mode?,
3) Do you have NAV (or equivelent) recovery CD,
4) If you have NAV SYSworks (or something similar) can you boot from the CD
and run a Virus or Recovery check?
5) If you can, try to boot in Safe Mode and check the Even Logs. BIG note
here, if you can boot into Safe Mode, then the CORE OS is fine! It's a
Protected Mode App issue! Try restsarting using without the /FastDetect
Switch in Boot.ini, this will list all the Protected Mode APIs and DLLs that
load. The last one should be able to point you into the direction of which
App of service is hosed. Once you know this, reboot into SAFE mode, CP ->
Services and make the offending APP or Service a MANUAL startup,
6) In Safe Mode (assuming you can get there), try a CHKDSK (no switches -
just see if there are any corrupted files). If you have a corrupted system
file (indicated by the %winroot%\system32 etc error in your post), then try
to extract the file in question from the I386 dir on your XP CD,
7) If you can, boot into safe mode, run Adaware (Spybot or whatever) to see
if there is a highjacked file. Also in safe mode, check to see what programs
are installed. If anything is suspect, try removing the program (see #5
above - it may indicate a screwed up app),
8) What version of XP are you running. It would help to know,
9) This one may sound funny, but (temporarily) give the EVERYONE group FC
from %winroot% all the way down. I've seen a perms error cause this in the
past. Once you are finished make sure to remove the EVERYONE group.

Here's an example of something I ran into: Some time back one of my client
systems got hijacked (web bot installed from sosme site). Upon investigation
(Safe mode booting etc) I discovered that a file called bridge.dll was the
culprit causing the failure for the boot. I renamed (not deleted) the file
and after that I had several errors in the event log informing me of a
failing app (actually HUNG), BUT at least I got XP up and running. I cleaned
it from the Registsry and voila - all was well. In some cases, hijacker type
apps "Will not be registered" in the registry under it's real name, but
under an apprantly good name - like "Windows Security Monitor KB1324589". It
looks like a good MS KB article number and one would be inclined to ignore
it, see below.

FINAlLY, try rolling back the LAST MS update. The XP System Restore agent
will ask to recover the appropriate files from CD or DLLcache and perhaps
that will fix things up.

Sorry for all the questions, but a alot of info is needed to troubleshoot a
problem of this magnitude. If you have an error entry in the Event Log, post
that and perhaps someone could search MS KB and/or the web for you.

If you wish, send me more details directly and I'll see what I can find for
you.

RG
 
Richard Gutery said:
1) Is your XP partition NTFS or FAT(/32)?
Click to expand...

The system is Dual Boot
MS-DOS (Partition 1)
NTFS (Partition 2)
2) Can you start in Safe Mode?,
Click to expand...

We havent tried as this didnt seem necessary at the time.
3) Do you have NAV (or equivelent) recovery CD,
Click to expand...

We do not use Norton Anti-Virus and only use the WinXP CD as the recovery
device.
5) If you can, try to boot in Safe Mode and check the Even Logs. BIG note
here, if you can boot into Safe Mode, then the CORE OS is fine! It's a
Protected Mode App issue! Try restsarting using without the /FastDetect
Switch in Boot.ini, this will list all the Protected Mode APIs and DLLs
that load. The last one should be able to point you into the direction of
which App of service is hosed. Once you know this, reboot into SAFE mode,
CP -> Services and make the offending APP or Service a MANUAL startup,
Click to expand...

Sorry, this didnt work. When I went to safe mode with networking, it bombed
and gave the same response.
6) In Safe Mode (assuming you can get there), try a CHKDSK (no switches -
just see if there are any corrupted files). If you have a corrupted system
file (indicated by the %winroot%\system32 etc error in your post), then
try to extract the file in question from the I386 dir on your XP CD,
Click to expand...
7) If you can, boot into safe mode, run Adaware (Spybot or whatever) to
see if there is a highjacked file. Also in safe mode, check to see what
programs are installed. If anything is suspect, try removing the program
(see #5 above - it may indicate a screwed up app),
Click to expand...
8) What version of XP are you running. It would help to know,
Click to expand...

Standard 32bit version with SP2
9) This one may sound funny, but (temporarily) give the EVERYONE group FC
from %winroot% all the way down. I've seen a perms error cause this in the
past. Once you are finished make sure to remove the EVERYONE group.

Here's an example of something I ran into: Some time back one of my client
systems got hijacked (web bot installed from sosme site). Upon
investigation (Safe mode booting etc) I discovered that a file called
bridge.dll was the culprit causing the failure for the boot. I renamed
(not deleted) the file and after that I had several errors in the event
log informing me of a failing app (actually HUNG), BUT at least I got XP
up and running. I cleaned it from the Registsry and voila - all was well.
In some cases, hijacker type apps "Will not be registered" in the registry
under it's real name, but under an apprantly good name - like "Windows
Security Monitor KB1324589". It looks like a good MS KB article number and
one would be inclined to ignore it, see below.

FINAlLY, try rolling back the LAST MS update. The XP System Restore agent
will ask to recover the appropriate files from CD or DLLcache and perhaps
that will fix things up.
Click to expand...

EXCELLENT SUGGESTION.... just ran the restore and it seems to be working
fine now...

I ran though the restore log and notices three config/system files which
were the probable cause of the system failing in the past.

I am not sure if I am being clear... but it all seems to be working well....
thanks for the advice... A+ in my books you are...

Regards,

Tom and Bill Whitney
(e-mail address removed)
 
Your're quite welcome.

Regards,

Tom said:
The system is Dual Boot
MS-DOS (Partition 1)
NTFS (Partition 2)


We havent tried as this didnt seem necessary at the time.


We do not use Norton Anti-Virus and only use the WinXP CD as the recovery
device.


Sorry, this didnt work. When I went to safe mode with networking, it
bombed and gave the same response.




Standard 32bit version with SP2


EXCELLENT SUGGESTION.... just ran the restore and it seems to be working
fine now...

I ran though the restore log and notices three config/system files which
were the probable cause of the system failing in the past.

I am not sure if I am being clear... but it all seems to be working
well.... thanks for the advice... A+ in my books you are...

Regards,

Tom and Bill Whitney
(e-mail address removed)
Click to expand...
 
Back
Top