Why can't I perform a repair installation from XP Pro Setup (upgrade version)?

[Frank]

Hi People,

I just upgraded my processor from a P2-400 to a P3-850, and now I get the
dreaded blue screen with this error
***Hardware Malfunction error
Call your hardware vendor for support.
***The system has halted

I'm using.......
XP Pro (Upgrade version)
Multi-boot setup (ala Partition Magic) W98 and XP Pro
Tyan S1846 ATX mother board

From a lot of back posts I read on this group it seems that I need to
perform a simple Repair Installation. The problem is I can't perform one
because I get no repair option from XP Setup.

First let me try to answer some questions in advance. The mother board and
BIOS do support the P3-850, the Intel Processor Utility shows all the right
data when I run it in W98. So I'm confident there isn't a hardware
problem, especially because the processor works fine in W98SE.

I have run the XP Pro Setup program by booting from the CD, but when I get
to the screen where Setup displays the partitions and asks to select one, I
was expecting to see a repair option, but there is none. It appears to be
the screen for a clean install, with options for "install here" and "create
a partition"...... but no option for repair. Before I get to that screen,
however, Setup tells me it can't find any Windows installations and prompts
me to insert a Windows CD. After inserting the W98SE CD, Setup proceeds
then gives me that partition list screen without the repair option. I exit
Setup at that point.

I'm stumped! I even tried booting from the XP CD with W98 as the active
partition, then tried again with XP as the active partition, hoping Setup
would recognize the XP installation and give me a screen with a repair
option, but I get the same behavior both ways.

I'm wondering if this missing repair option has anything to do with the
fact that I'm using an Upgrade CD version of XP Pro. Does anybody know if
there's something different about it? Has anybody out there used the
upgrade version and DID get a repair option?

Thanks,
Frank

 

[R. C. White]

Hi, Frank.

I assume you are using these instructions for your repair installation:
How to Perform an In-Place Upgrade (Reinstallation) of Windows XP
http://support.microsoft.com/default.aspx?scid=KB;en-us;q315341

Yes, those instructions can be confusing because there are TWO Repair
options. You must reject the first one and go for the Install choice. (The
first Repair option runs the Recovery Console, which lets you fix such
things as the MBR and boot record, which must be OK before WinXP will even
start to load.) The instructions for Method 2 must be read very carefully
and in sequence. When you see the screen in paragraph 2, press ENTER, as
instructed. When you get to paragraph 4, THEN you press R to Repair your
existing installation.

By the way, paragraph 5 is very short and sweet, but it will take a LONG
time to perform! As long as a new installation of WinXP. And then the
first few lines in "After You Perform and In-Place Upgrade" will also take a
long time, especially if your WinXP CD-ROM does not include SP1.

I did the in-place upgrade a couple of weeks ago. It took a couple of hours
for the basic upgrade, and then another couple of hours to download and
install all the fixes on Windows Update. I didn't lose any installed
applications or data, and most of my WinXP tweaks survived, too. But you'd
better clear a half-day for the entire project.

My WinXP CD-ROM is also the Upgrade version. The only difference between
Upgrade and Full is the price; the Upgrade CD checks to see that you have a
qualifying product. Other than that, they are identical.

RC

 

[Frank]

Hi, Frank.

I assume you are using these instructions for your repair installation:
How to Perform an In-Place Upgrade (Reinstallation) of Windows XP
http://support.microsoft.com/default.aspx?scid=KB;en-us;q315341

Hi RC,

I much appreciate your reply.

Yes, I'm using those instructions. I also reviewed this page
http://www.webtree.ca/windowsxp/repair_xp.htm because it shows some actual
screen shots encountered while Setup is running.

Yes, those instructions can be confusing because there are TWO Repair
options. You must reject the first one and go for the Install choice. (The
first Repair option runs the Recovery Console, which lets you fix such
things as the MBR and boot record, which must be OK before WinXP will even
start to load.)

Yes, I'm aware Recovery Console will not help with my situation. I avoided
that option by pressing Enter.

The instructions for Method 2 must be read very carefully
and in sequence. When you see the screen in paragraph 2, press ENTER, as
instructed.

Yes, I did that. Then I was presented with the licensing screen.

When you get to paragraph 4, THEN you press R to Repair your
existing installation.

And that's where I run into the problem. There is no "R" or Repair option
listed anywhere on the screen. In fact, it doesn't look like I'm getting
the same screen.

If you go to http://www.webtree.ca/windowsxp/repair_xp.htm and click on the
"How To Run a Repair Install" link, it'll take you to some screen shots
further down on the page. The third screen shot is the screen you just
mentioned (with the Repair option), I should be getting that but I'm not.
Here's what I'm getting instead.....

Windows XP Professional Setup
===========================
The following list shows the existing partitions and unpartitioned space on
this computer.

Use the UP and DOWN ARROW keys to select an item on the list.
- To set up Windows XP on the selected item, press ENTER.
- To create a partition in the unpartitioned space, press C.
- To delete the selected partition, press D.

ENTER=Install D=Delete partition F3=Quit


That appears to be the screen I got when I first installed XP. I can
understand why there wouldn't be a Repair option on a fresh install. But
it beats the hell out of me why I'm not getting that option now. XP worked
perfectly for months, until I replaced the processor the other day.

By the way, paragraph 5 is very short and sweet, but it will take a LONG
time to perform! As long as a new installation of WinXP. And then the
first few lines in "After You Perform and In-Place Upgrade" will also take a
long time, especially if your WinXP CD-ROM does not include SP1.

I did the in-place upgrade a couple of weeks ago. It took a couple of hours
for the basic upgrade, and then another couple of hours to download and
install all the fixes on Windows Update. I didn't lose any installed
applications or data, and most of my WinXP tweaks survived, too. But you'd
better clear a half-day for the entire project.

Thanks for the heads up. I have no problem with that, but do have a
problem if I need to perform a clean install again. I'd have to reinstall
more than 70 programs, and there's updates for many of them too. I'd
rather put the old processor back in than go through that.

My WinXP CD-ROM is also the Upgrade version. The only difference between
Upgrade and Full is the price; the Upgrade CD checks to see that you have a
qualifying product. Other than that, they are identical.

RC

Thanks again, it's good to know you could do a Repair Installation with the
Upgrade version. I was having doubts.

Let me ask you this. After the licensing screen I was presented with this
screen about the qualifying product.....

Setup cannot find a previous version of Windows installed on your computer.
To continue, Setup needs to verify the you qualify to use this upgrade
product.
Insert one of the following Windows product CDs.

I'm interested in knowing if you got the same text, especially the first
line where it says "cannot find a previous version of Windows installed on
your computer". I'm guessing it says that with all the Upgrade CDs, but
I'm curious if I'm not getting a Repair option because Setup doesn't see an
XP installation to repair. It should, it's listing both of my hard disks
and all the partitions on them. XP was activated, so everything's on the
up and up regarding licensing.

Needless to say, I did insert my Windows98 CD (as I did when I first
installed XP). Setup didn't ask me to remove the W98 CD, it immediately
presented me with the next Setup screen, the one mentioned above without
any Repair option.

Thanks,
Frank

 

[D.Currie]

Have you used any sort of drive overlay like ez-bios or anything like it?
That would cause what you're seeing.

 

[R. C. White]

Hi, Frank.

OK. I think I can guess at least part of the problem. I'll trim the good
parts from our thread so far so we can concentrate on the problem area:

If you go to http://www.webtree.ca/windowsxp/repair_xp.htm and click on the
"How To Run a Repair Install" link, it'll take you to some screen shots
further down on the page. The third screen shot is the screen you just
mentioned (with the Repair option), I should be getting that but I'm not.
Here's what I'm getting instead.....

Windows XP Professional Setup
===========================
The following list shows the existing partitions and unpartitioned space on
this computer.

Use the UP and DOWN ARROW keys to select an item on the list.
- To set up Windows XP on the selected item, press ENTER.
- To create a partition in the unpartitioned space, press C.
- To delete the selected partition, press D.

ENTER=Install D=Delete partition F3=Quit


That appears to be the screen I got when I first installed XP. I can
understand why there wouldn't be a Repair option on a fresh install. But
it beats the hell out of me why I'm not getting that option now. XP worked
perfectly for months, until I replaced the processor the other day.

I'm interested in knowing if you got the same text, especially the first
line where it says "cannot find a previous version of Windows installed on
your computer". I'm guessing it says that with all the Upgrade CDs, but
I'm curious if I'm not getting a Repair option because Setup doesn't see an
XP installation to repair. It should, it's listing both of my hard disks
and all the partitions on them. XP was activated, so everything's on the
up and up regarding licensing.

Thanks,
Frank

No, the missing "previous version" message is not because of the Upgrade
version. It relates back to that earlier screen that can't find ANY
previous Windows on your computer. You know and I know that Windows is
there, but Setup can't find it. So, let's figure out why.

In the link you provided, there are two contrasting screen shots. The
earlier shot - the second one under the heading, "How Partition using the
Recovery Console", and DISKPART - is the one I really expected you to see.
The later one, under "How to Repair Install", apparently is the one you
actually are seeing. I'm not sure why you are seeing NO existing Windows.
Perhaps you should try the Recovery Console route once just to see what it
shows you and be sure that you and Setup agree on which partition is which.
If RC does not see ANY existing Windows, then you need to figure out why;
probably either your HD cabling or your BIOS settings have changed since you
installed Windows. After seeing just where RC finds your existing Windows,
you can abort the RC and try the Repair Install again.

You probably noticed that Setup at this point is referencing locations on
your computer by HD # and partition #, and the "drive" letters may be
different from what you were expecting. Do YOU see a partition that Setup
can't see in the Repair Install mode? Check all the info in that screen:
the description of the disk and the IDE connection, the partition names and
formats, etc. Pay attention to the drive letters, but only so that you can
follow what Setup is calling them; they will not really relate to what you
see when actually booted into Windows.

IF your HD configuration is "plain vanilla", then this screen should conform
pretty closely to what you normally see. But, if you have any SCSI, RAID,
ATA133 or other non-mundane elements, the BIOS may disagree with Setup as to
which is Drive 0. Or when you changed the CMOS settings to boot from CD to
run Setup, you may also have confused the order of your HD numbers. None of
this causes a problem which is insurmountable, but it may require very
cautious navigation through this part of Setup.

I know that these screens get very tedious and boring, especially after
we've been through abortive Setups several times. But we MUST read the
screens very slowly and carefully and be sure we are not just getting into
the rhythm of hitting ENTER automatically to try to speed up the process.
(Been there; done that.)

If the answer does not appear obvious when you get this far again, post back
with details of your HD lineup, including controllers, host adapters,
partitions, etc. With enough details, we probably can help you navigate
through these tricky waters.

And if you DO figure it out, post back telling us how you did it. In a
newsgroup, we all learn from each other and it may be your turn to teach the
rest of us something. ;<)

RC

 

[Frank]

Have you used any sort of drive overlay like ez-bios or anything like it?
That would cause what you're seeing.

Thanks for the feedback. It made me retry some things I tried earlier.

No, I don't use an overlay, but I do use Partition Magic. While retrying
some of the things your post reminded me about, I did find out why XP Setup
wasn't recognizing the XP installation. If it had recognized the
installation I would have gotten the screen offering the Repair install
option.

The clue was in the screen I got asking me to choose a partition. In the
list of partitions, the XP boot partition wasn't the active partition.

Previously I had configured Boot Magic (Partition Magic's boot utility) to
use XP as the default OS, then I disabled Boot Magic so it wouldn't
interfere with XP Setup. I was thinking the XP boot partition would be
made active, but it wasn't enough. I had to also use Partition Magic to
change the active partition from W98 to XP. After doing that I was finally
presented with the screen that offered the Repair Installation option.

 

[Frank]

Hi, Frank.

OK. I think I can guess at least part of the problem. I'll trim the good
parts from our thread so far so we can concentrate on the problem area:

Hi RC, thanks again for the help.

No, the missing "previous version" message is not because of the Upgrade
version. It relates back to that earlier screen that can't find ANY
previous Windows on your computer. You know and I know that Windows is
there, but Setup can't find it. So, let's figure out why.

See my reply to D.Currie's post.

In the link you provided, there are two contrasting screen shots. The
earlier shot - the second one under the heading, "How Partition using the
Recovery Console", and DISKPART - is the one I really expected you to see.

Actually, that's the one I've been getting.

The later one, under "How to Repair Install", apparently is the one you
actually are seeing.

No, this is the one I wanted to see. I think you just got those two screen
shots backwards while composing your reply, so I feel that you're right on
the money (if they were reversed).

I'm not sure why you are seeing NO existing Windows.
Perhaps you should try the Recovery Console route once just to see what it
shows you and be sure that you and Setup agree on which partition is which.
If RC does not see ANY existing Windows, then you need to figure out why;
probably either your HD cabling or your BIOS settings have changed since you
installed Windows. After seeing just where RC finds your existing Windows,
you can abort the RC and try the Repair Install again.

As I said in my reply to D.Currie, the reason was that the XP boot
partition wasn't marked as the active partition as I was booting from the
XP CD. FWIW XP's boot partition is on my first hard disk, but the XP OS
files are on the second disk drive.

You probably noticed that Setup at this point is referencing locations on
your computer by HD # and partition #, and the "drive" letters may be
different from what you were expecting. Do YOU see a partition that Setup
can't see in the Repair Install mode?

What I saw were all my partitions, even ones with unallocated space.
However, XP's boot partition was marked "inactive" in Setup's list. It
needed to be marked active before Setup would recognize the XP
installation.

Check all the info in that screen:
the description of the disk and the IDE connection, the partition names and
formats, etc. Pay attention to the drive letters, but only so that you can
follow what Setup is calling them; they will not really relate to what you
see when actually booted into Windows.

IF your HD configuration is "plain vanilla", then this screen should conform
pretty closely to what you normally see.

hehehe, no plain vanilla for me Drive one is the drive that came with
my pc, it's only 8.4mb and UMDA/33. I added the second 30mb UMDA/100 disk
drive and a UMDA/100 controller card for it. I installed the XP boot
partition on drive one, but put the OS files on drive two becaue it's the
fastest drive. It works quite well.

But, if you have any SCSI, RAID,
ATA133 or other non-mundane elements, the BIOS may disagree with Setup as to
which is Drive 0. Or when you changed the CMOS settings to boot from CD to
run Setup, you may also have confused the order of your HD numbers. None of
this causes a problem which is insurmountable, but it may require very
cautious navigation through this part of Setup.

I know that these screens get very tedious and boring, especially after
we've been through abortive Setups several times. But we MUST read the
screens very slowly and carefully and be sure we are not just getting into
the rhythm of hitting ENTER automatically to try to speed up the process.
(Been there; done that.)

Yep, I've been there too. Nothing like that has occured here, I do read
the screens just to make sure my command matches the prompts for Enter, F8,
R, F3, yada yada......

If the answer does not appear obvious when you get this far again, post back
with details of your HD lineup, including controllers, host adapters,
partitions, etc. With enough details, we probably can help you navigate
through these tricky waters.

And if you DO figure it out, post back telling us how you did it. In a
newsgroup, we all learn from each other and it may be your turn to teach the
rest of us something. ;<)

RC

Well, things got better before they got worse.

As I said, I did manage to get the Repair Installation screen, and chose R
to repair XP. The furthest I got into the repair operation was just after
Setup said it was checking drive D (where XP's OS files are located), I
believe it started to copy some files at that point. I really thought I
had it licked, but unfortunately, during the operation I got that damn blue
screen again (*** Hardware Malfunction... The system has halted). I had no
choice but to reboot and try again. I tried about 26 times, but the
blue screen error kept appearing at unpredictable points during Setup. So
I gave up trying to repair XP, and put the old P2 processor back in.

After that I was able to boot into XP, but unfortunately I feel XP may be
damaged beyond repair now. It appeared to boot with a 640x480 screen
resolution. When I right clicked on the Desktop to inspect the settings I
had no resolution controls at all. All I had was a dialog for changing the
Theme, I didn't even have tabs on the dialog. Upon checking Device Mgr for
my Matrox G200AGP settings, I found it had the ! mark in a yellow circle.
The device status said "This device cannot start. (Code 10)". I followed
MS's Troubleshooting advice and uninstalled the driver, then scanned for
hardware changes. It did install the device, and the ! mark was gone, but
I still didn't have any controls, and upon rebooting the ! mark reappeared.

I had a System Restore checkpoint from the day before I changed the
processor. So I restored the system to that point. But still no joy, no
resolution control, and only the Theme dialog appears in Display Properties
again with no tabs. At this point I uninstalled the driver from
Add/Remove, and reinstalled it. But still no joy.

I also found that the XP Firewall wasn't enabled, where before it was.
Upon trying to enable it I got errors, they're at the bottom of this
message. I'm afraid that now I have a messy tangle of inoperable services
that might not be worth trying to untangle individually. I have no idea
where they came from, and because I don't have a firewall using a cable
broadband connection I didn't really feel safe using XP to click on the
links provided in Event Viewer. I did try to find more about them using
W98, but with W98 I coudn't find a page at MS's site that would explain
them.

At this point I really don't know what to do. I figure I have two options.

1-Leave the P2 processor in, and try running a Repair Install with Setup to
repair the current screwed up XP config.

Does anybody know if a Repair Install would even fix the problem with
Display properties and the service modules?

2-Failing that, put the P3 back in and try a complete fresh install using
the P3.

I do web design work, and have more than 60 programs installed. I dread
the thought of reinstalling them all, and the updates needed for them, not
to mention all the extensions I've installed for Dreamweaver programs. I
also have IIS installed and have many virtual directories configured. So
I'd gladly give up the P3 for stable operation with my current
installation. If you, or anybody else, can offer advice or other options
I'd sure be grateful.

Thanks again,
Frank



Event Type: Error
Event Source: Rasman
Event Category: None
Event ID: 20063
Date: 10/7/2003
Time: 5:26:00 PM
User: N/A
Computer: CC494569-A
Description:
Remote Access Connection Manager failed to start because the Point to Point
Protocol failed to initialize. The specified module could not be found.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7e 00 00 00 ~...


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 10/7/2003
Time: 5:26:51 PM
User: N/A
Computer: CC494569-A
Description:
The IPSEC Services service terminated with the following error:
The specified module could not be found.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 10/7/2003
Time: 5:26:51 PM
User: N/A
Computer: CC494569-A
Description:
The Remote Access Connection Manager service terminated with the following
error:
The specified module could not be found.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 10/7/2003
Time: 5:26:51 PM
User: N/A
Computer: CC494569-A
Description:
The Internet Connection Firewall (ICF) / Internet Connection Sharing (ICS)
service depends on the Remote Access Connection Manager service which
failed to start because of the following error:
The specified module could not be found.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Rasman
Event Category: None
Event ID: 20063
Date: 10/7/2003
Time: 5:27:22 PM
User: N/A
Computer: CC494569-A
Description:
Remote Access Connection Manager failed to start because the Point to Point
Protocol failed to initialize. The specified module could not be found.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7e 00 00 00 ~...


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 10/7/2003
Time: 5:27:22 PM
User: N/A
Computer: CC494569-A
Description:
The Remote Access Connection Manager service terminated with the following
error:
The specified module could not be found.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 10/7/2003
Time: 5:27:23 PM
User: N/A
Computer: CC494569-A
Description:
The Internet Connection Firewall (ICF) / Internet Connection Sharing (ICS)
service depends on the Remote Access Connection Manager service which
failed to start because of the following error:
The specified module could not be found.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 10/7/2003
Time: 5:29:23 PM
User: N/A
Computer: CC494569-A
Description:
The Telephony service entered the stopped state.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

 

[Frank]

For completeness, I reviewed older EV entries from when XP was working
normally, and compared them to the EV messages I'm getting now.

I don't know if it would simplify matters, but the below "error" is the
only one that appears in Event Viewer after XP boots. All the other
"error" messages shown in my last post were generated AFTER I tried to
enable XPs firewall.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 10/7/2003
Time: 5:26:51 PM
User: N/A
Computer: CC494569-A
Description:
The IPSEC Services service terminated with the following error:
The specified module could not be found.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

In addition to the above error message, I now have these four "info"
messages appearing, they didn't appear when XP was working ok. I'll just
paste the description of the events because they don't seem unusual, other
than the fact that I'm getting them now and didn't get them before.


The Network Connections service was successfully sent a start control.

The Network Connections service entered the running state.

The Network Location Awareness (NLA) service was successfully sent a start
control.

The Network Location Awareness (NLA) service entered the running state.



On some boots, however, two more "info" messages appear. But I "think"
these are a function of whether or nor my cable modem is turned on or off
during boot.

The IPSEC Services service was successfully sent a start control.

The IPSEC Services service entered the stopped state.


I went into Services and tried to manually Start the IPSEC service, but got
the "module cannot be found" error there too.

Thanks,
Frank

 

[Frank]

I believe I've straightened out the EV System error messages, for the most
part at least, and have XPs firewall working again. There are now no more
System Event errors at boot up, and the EV Information entries are the same
as I had before trying to upgrade the processor. Though I'm not completely
out of the woods yet, I do think I'm much closer to the edge of the
forest.<g>

While reviewing the EV Application log I came across the Information entry
shown at the bottom of this post. This is from the first time I
successfully booted into XP after giving up on the Repair Installation and
reinstalling the original P2 processor.

It seems the volume was dirty as a result of all the failed attempts at
running Repair Installations, especially the abrupt ***Hardware Malfunction
blue screens that halted the system. Two of those blue screens occured
while Setup was copying files (at appx the 5% mark on the progress bar), so
I would expect some corruption had occured.

If you look at the errors noted next to the paths shown on the below log,
they all say "first allocation unit is not valid. The entry will be
truncated." Can somebody please explain what that error means? The reason
I ask is that after checking the paths, 22 of the 24 files/folders don't
exist at the locations shown. Could it be that the error is telling me
that the FAT had a reference for a file that didn't exist, and that
truncating the entry means it was removed from the FAT?

14 of the 22 missing files/folders I was able to find elsewhere in Windows
(10 of them in the \windows\system32\dllcache folder). So what I did was
copy the 14 matching filenames from their alternate locations to the
locations shown in the paths from the log. After booting into XP I was
pleased to find the EV errors gone, services that couldn't start were now
running, and I was able to enable the firewall.

I still have two things (that I know of) that need to be addressed. The
total loss of Display Property control, and the 8 files/folders I coudn't
find anywhere in XP.

Since two of the lost files/folders have ".cpl." in their names I'm
focusing on the files/folders first, because I assume they have something
to do with the Control Panel and may relate to the Display Properties
problem. Does that sound right? Here's the 8 files/folders I couldn't
find anywhere in, or under, the \windows folder:

\WINDOWS\WindowsShell.Manifest
\WINDOWS\WinSxS\InstallTemp
\WINDOWS\system32\logonui.exe.manifest
\WINDOWS\system32\ncpa.cpl.manifest
\WINDOWS\system32\nwc.cpl.manifest
\WINDOWS\Help\ieeula.chm
\WINDOWS\Help\printing.chm
\WINDOWS\Driver Cache\i386

Can anybody offer any advice on the best way to go about finding or
recreating those files/folders? Which tools should I focus on? In other
words, would running a Repair Installation recreate them? I assume System
File Checker wouldn't help because I think it just copies backups, and
there aren't any that I can find. Or could I get some of them by
extracting them from the XP Pro CD? Any suggestions or pointers would be
appreciated.

And though I do have my Matrox graphic software drivers installed, they
aren't avialable to me with the display properties being the way they are.
You can see a screen shot of my Display Properties window at the following
url, it's worth a 1000 words.
http://shycatwebs.com/displayprops.jpg
So, before trying to recover any of the lost files, would I be best served
by removing the Matrox drivers via Add/Remove and let XP use its default
driver?

Thanks,
Frank




Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 10/7/2003
Time: 2:30:36 PM
User: N/A
Computer: CC494569-A
Description:
Checking file system on \Device\Harddisk1\Partition1
The type of the file system is FAT32.

The volume is dirty.
Volume Serial Number is 3E8F-0823
\WINDOWS\Prefetch first allocation unit is not valid. The entry will be
truncated.
\WINDOWS\WindowsShell.Manifest first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\WinSxS\InstallTemp first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\system32\asr_fmt.exe first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\d3dim700.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\diskperf.exe first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\dxdllreg.exe first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\logonui.exe.manifest first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\system32\ncpa.cpl.manifest first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\system32\ntdsbcli.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\nwc.cpl.manifest first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\oakley.dll first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\system32\odfox32.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\raschap.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\rasppp.dll first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\system32\spxcoins.dll first allocation unit is not valid. The
entry will be truncated.
\WINDOWS\system32\dllcache\SHLWAPI.DLL first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\system32\dllcache\URLMON.DLL first allocation unit is not valid.
The entry will be truncated.
\WINDOWS\inf\LAYOUT.PNF first allocation unit is not valid. The entry will
be truncated.
\WINDOWS\inf\netoc.inf first allocation unit is not valid. The entry will
be truncated.
\WINDOWS\Help\ieeula.chm first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\Help\printing.chm first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\Fonts\micross.ttf first allocation unit is not valid. The entry
will be truncated.
\WINDOWS\Driver Cache\i386 first allocation unit is not valid. The entry
will be truncated.
Bad links in lost chain at cluster 1118100 corrected.
Convert lost chains to files (Y/N)? 43896 KB in 70 recovered files.
Windows has made corrections to the file system.
8177128 KB total disk space.
103112 KB in 769 hidden files.
16068 KB in 3649 folders.
4463864 KB in 44211 files.
3594080 KB are available.

4096 bytes in each allocation unit.
2044282 total allocation units on disk.
898520 allocation units available on disk.
Checking file system on D:
The type of the file system is FAT32.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Volume Serial Number is 3E8F-0823
Windows has checked the file system and found no problems.
8177128 KB total disk space.
103116 KB in 770 hidden files.
16064 KB in 3648 folders.
4463872 KB in 44212 files.
3594072 KB are available.

4096 bytes in each allocation unit.
2044282 total allocation units on disk.
898518 allocation units available on disk.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.