Having boot problems, seems obvious but doesnt want to work

My girlfriend's computer is getting the following error at startup:

"Windows could not start because the following file is missing or corrupt: System32\DRIVERS\pci.sys
You can attempt to repait this file by starting Windows Setup using the original Setup CD-ROM. Select 'r' at the first screen to start repair"

Well, I put in the Windows disk and at restart i pressed F12 to enter Windows setup, but no matter what i do it seems to simply drop me at a blank C:\> prompt. I know I am probably missing something obvious, but if you guys could help me out once again I'd certainly appreciate it. I was also wondering if anyone has any idea how this file may have gotten deleted in the first place as neither of us have any recollection of any changes to the system. Thanks in advance, I love you guys fo bailing me out repeatedly from my computer driven insanity.

 

Have a look her, detailed, with pictures , repair proceedure.
http://www.webtree.ca/windowsxp/rep... XP by Installing Over top of Existing Setup:

 

Hmmm well i read the faq you posted, but the only option this presents me with is reformatting her drives, which she only wants me to as an absolute last recourse as there are irreplaceable photos on the computer. As the problem simply apperas to be a missing or corrupt driver, isnt there a simpler solution?

 

Have you tried pressing f8, as the system starts up. and starting in safe mode, or, restoring to an earlier time (system restore)

 

pci.sys is not just any old driver it is a pretty important part of widows!

Nevertheless Microsoft have a fix for your problem, if you can follow it.

http://support.microsoft.com/kb/319136

It is a pity you condemmed BAKLOGIC's link out of hand. I've not seen it before and thought it was pretty comprehensive when I looked at it Thank you BAKLOGIC. It seems to have instructions on everything from asking a Hong Kong policeman for directions when your rickshaw breaks down to making the tea.

It also contains a long list of many useful proceedures, including help for your problem.


Studio T

 

If you went to the link that I GAVE YOU AGAIN, http://www.webtree.ca/windowsxp/repa...sting Setup:
AND SCROLL DOWN THE PAGE TO THE LAST SECTION
How to Repair Install: ***Also removes Service Packs***
Sometimes the only way to repair XP is to reinstall. You do not have to wipe your partition and start over. Just as with previous versions of Windows you can reinstall right over top of an existing setup. This has the advantage of retaining your installed applications, data and settings. You will lose previously saved System Restore Points but System Restore will begin creating new restore points again immediately following the Repair Install.
AND FOLLOW THAT ADVICE, YOU SHOULD KEEP ALL YOU DATA.
Whe done, ensure Windows firewall , at least is on, before going on-line.
To get Windows updated again, go to

http://www.majorgeeks.com/AutoPatche...ate_d5213.html
, and that shoul solve the updating, easier.

 

Thanks for the microsoft link Studiot, it could be a more simple fix. for Dallis Raines42

 

I certainly didn't intend to discredit Baklogic's link, it did look like a very good resource, I did however peruse all the different options and none of them seemed to suit/solve my exact issue... the computer will not start in safe mode or with a system restore point... both options give me the same load bar and then display an error message identical to the original. I also used the Microsoft page you linked, Studiot. While the first option seemed promising, upon entering the command line "expand drive:\i386\pci.sy_ c:\winnt\system32\drivers /y" (Entered as "expand D:\i386\pci.sy_ c:\winnt\system32\drivers /y" in every possible combination, it continued to tell me "access is denied" after a short pause. The second option, for in-place upgrade was one of the solutions described on Baklogic's link ( I suppose I should have explained that I had already explored this option), and did not work for me. The following error messge is displayed:
"Windows XP Home Edition Setup
The partition is either too full, damaged, not formatted, or formatted with an incompatible file system. To continue installing Windows, Setup must format this partition.

C: Partition2 [Unknown] 39158 MC ( 39158 MB free)
on 39206 MB Disk 0 at Id 0 on bus 0 on atapi [MBR].

Caution: Formatting will delete any files on the partition.

Use the UP and DOWN ARROW keys to select the file system you want, and then press ENTER to continue. If you want to select a different partition for Windows XP, press ESC to go back.

>Format the partition using the NTFS file system (Quick)
>Format the partition using the NTFS file system"

This is the same screen I got last night, and as I assume that this is due to the same issue, I figured you realized I would reach this message in working through the fix you posted. This is why I asked if there was a solution that would not require formatting, and it seems I have arrived at the same issue again, albiet with the additional question: why is access denied when trying to expand the pci file? Thanks for your patience with me guys, your help really is appreciated.

 

You can have a look at this little gem,
http://majorgeeks.com/Super_Fdisk_d4985.html

 

I'm sorry my eyes do deceive me, but when I go to the Microsoft link, I could have sworn it said to use the repair console to effect the repair you require. This proceedure will not affect your data.

THIS WAS WHY I POSTED THAT LINK

Your reply suggests to me that you have not accessed the WINDOWS REPAIR CONSOLE.


There are full instructions to do this on both the Microsoft link and the Baklogik link.

Studio T

 

If you need help or advice with the recovery console post again it is a scary beast.

Studio T

 

Studiot, I believe I am doing exactly that... my procedure is as follows:

1. Start the computer
2. hit F12 for the boot menu
3. From boot device menu, select option 4. IDE CD-ROM Device
4. Windows Setup loads next, giving me the option to repair a windows XP installation using the recovery console, by pressing "r". (The windows walk through says I should have to hit "c", but if i recall correctly this is simply a throwback to windows 2000, and XP is only meant to have one option)
5. I am then given the following prompt:
"Microsoft Windows XP (TM) Recovery Console.
The Recovery Console provides system repair and recovery functionality.
Type EXIT to quit the Recovery Console and restart the computer.
C:\>"
and that's it.
6. its at this point I entered the expand command from your FAQ
"expand D:\i386\pci.sy_ c:\winnt\system32\drivers /y"
7. to which I got an "access denied" reply. I also tried the command line using her other CD-ROM device, removing the space before /y (with both drives) as that was not explictly explained in the FAQ. I also tried changing the command prompt from C:\ to D:\ and entering the rest of the command directly from that prompt. None of these produced any different results, always giving me "access denied"

I believe I am doing this in the correct place and following the instructions provided. I am not an idiot and I can certainly read what the steps described. I would not have said I attempted the fix recommended if I had not followed all the steps in said FAQ. Is the problem perhaps due to the fact that the repair procedure is intended for Win2000? Is there perhaps a difference in the structure of the WinXP CD that would require a changed command? I will now give the FDisk program a try and see if I cant finagle my way into an operating OS, thanks again to both Baklogic and Studiot

 

Why are you hitting F12 for the boot menu?
this refers to files ON THE HARD DRIVE which is corrupted. Your objective is to boot from the CD.

First you need to make sure the pc will boot from the CD; Insert the CD and restart, keeping close watch on the screen.
If you see a message which says 'press any key to boot from CD' do so or the system will march on and try to boot from the problem drive.
If it doesn't boot from the cd or you don't see the message, you will need to change the boot order or priority in the pc BIOS or setup program.

To do this you need to tap a key several times as you power on the pc. Watch the screen it may be F2 or DEL.

When you are in setup you will need to look for Boot order or boot priority, probable the second screen you come to. Make sure that CD comes before hard drive.

Reboot

The pc should now be run entirely from the CD so any files required will be pure and pristine.
The first screen will offer the choice of return for install via setup or R for repair console. R is the option you want.
Once in the repair console it will ask for the drive to be looked at and the administrator password.
You can also run checkdsk from the repair console, not a bad idea.

Hope this helps

Studio T

 

Sorry I've just realised some BIOS have the F12 boot options so you may have been accessing the CD. But try it the other way anyway.

the repair console should present you with a numbered list of Windows installations to repair - 1 in your case.
you choose by entering the number - 1 just pressing enter cancals out of the console
You are then asked for the administrator password
enter this and pres return
you then get a normal dos type prompt > where you can follow the microsoft proceedure to copy the replacement files off the disk.

You are right in thinking that sometimes you hav eto interpret what msoft say compared to what you see on the screen, because they don't alway tell all.

Studio T

 

Okay, I changed the boot order (f2 for setup) to CD>HDD>Floppy, then restarted the system, and sure enough was given the "press any key to boot from cd" option. Back to the same XP setup screen again, hit r for the console, and once more dumped back to the
"Microsoft Windows XP (TM) Recovery Console.
The Recovery Console provides system repair and recovery functionality.
Type EXIT to quit the Recovery Console and restart the computer.
C:\>"

I am still not getting any listings for windows installations however. IIRC it should read something like this, correct?:

"Microsoft Windows XP (TM) Recovery Console.
The Recovery Console provides system repair and recovery functionality.
Type EXIT to quit the Recovery Console and restart the computer.
1: C:\WINNT

Which Windows XP installation would you like to onto
(to cancel press ENTER)?"

I am thinking this is a bad sign that the recovery console is not recognizing ANY windows installations...

 

It does look very much like the partition is not being recognised, or Windows would find it.
If neither Studiot's or, my other links helped, the last could be a boon.
http://majorgeeks.com/Super_Fdisk_d4985.html
Incidently,when using the R option, in the repair console,by default, the administrative password for Windows XP Home Edition is blank.
That is why you press 1 and not C , and not enter.

 

Ok, thanks for your help. I am running an indepth chkdsk now ("/chkdsk /p") which is taking an inordinatly long time to complete (been running about 30 minutes and only at 11%) when this is done i will post results and then try the fdisk option. thanks for your continued attention!

 

If you still have a problem, I have searched around for extra help for you.
If you have a look at this page, and scroll down it, you will see how to get over the original problem, explained with further a little download, even, for the corrupted file.- extracting , and replacing - We have to give links, when it is someone elses work.
Hope this will be of use. If not, it is worth the read.

http://www.computing.net/windowsxp/wwwboard/forum/133426.html

 

Well, CHKDSK returned less then optimal results. Heres the log:
"C:\>CHKDSK /p
CHKDSK is checking the volume...
CHKDSK is performing additional checking or recovery...
CHKDSK is performing additional checking or recovery...
CHKDSK is performing additional checking or recovery...
28% completed.
The volume appears to contain one or more unrecoverable problems."
any ideas?

 

Your hard drive is screwed...whether it's an actual physical failure, or the data somehow became corrupted to the point the OS can't recognize it, the end result is the same. It would be helpful to know if the BIOS recognizes the hard drive...if it does, that should mean the drive is physically ok, but you're gonna have to fdisk, format & reload from scratch. Times like these, it's great to have a back-up image with Ghost or True Image to restore from!

 

OK Dallas, the hard drive is sufficiently corrupt to need a full clean install as Wavetar suggests.
You are obviously using the internet on another pc. Can you connect the faulty drive as a slave to another pc to recover the data before you do this?

The alternative one computer solution is to carve out a second partition from the free space and install a second copy of windows into it. This would involve a program such as partition magic which can boot the pc, shrink the existing partition, then create and format a new one in the space freed up.

Studio T

 

I am a bit concerned if the recovery console is truly inacessible because it implies that you can't control the pc from an operating system not on the hard drive.
If this is so it would imply a hardware fault in memory or motherboard.

Did you try to run check disk from the recovery console?
If so this is good news. Can you run other recovery console commands such as bootcfg /scan ?

Studio T

 

Ok, I guess i will slave her drive to mine and see if i cant pull off the data she needs. And yes, i ran checkdisk from the console, but when i tried running "bootcfg /scan" only more bad news followed:
"Scanning all disks for Windows installations.

Please wait, since this may take a while...

Error: Failed to succcessfully scan disks for Windows installations. This error may be caused by a corrupt file system, which would prevent Bootcfg from successfully scanning. Use chkdsk to detect any disk errors."

speaking of which... why did windows spell "successfully" with three c's? that wasnt a typo on my part ><

obviously, chkdsk isnt going to help me out here....

 

You seem computer savvy so I assume you know about master/ slave jumpers on IDE hard drives, and finding the drive in bios and then windows. You may be unlucky in that your own pc will want to run check disk on the drive and may not succeed. You should get the option to press on regardless, and may be able to recover data nevertheless.

Post again if you need help with any of this.

As I said I think that the message from bootconfig is good news because it shows the pc is running as it should from another OS.

Before reinstallation I suggest you download and run a disk check utility from

http://www.majorgeeks.com/downloads8.html

There are several general checkers, plus manufacturer specific ones here. We have no information about the faulty drive is it getting old?

About the typo I've heard of this before, perhaps it has the same problem that affects my pc when I tipe perfectly good english into it for Major Geeks.

Studio T

 

Firstly, sorry taking so long on my reply, its been a busy week. I tried slaving her HDD to mine (and yes i set the jumpers first). I simply removed my secondary slaved drive and attached hers instead in the same position on the cables. The computer got as far as opening a boot menu when prompted, but would not boot to windows. I would get a black loading screen accompanied by some "working" sounds from the pc, which would then stop before to long leaving me with only a blank screen. Nothing I tried could get my computer to boot with the bad HDD attached. For reference, here is the information off of her hardware:
Brand: Maxtor
Model: DiamondMax Plus 8 (40GB) ATA / 133 HDD
Date: 12DEC2002
Serial Number: E142D9EE

I don't know if you need any further info but please let me know if you do, I will check this thread frequently in the next few days, as she is getting antsy to have her computer working. At this point I feel like I could probably get it going ok with a wipe and a clean install from the recovery console, but as I said she has photos stored (and not backed up) that are irreplaceable to her. Thanks again for all your great tips and attentive help

 

NFTS reader, is worth considering.
http://www.majorgeeks.com/NTFS_Reader_for_DOS_d2036.html

 

I expect you did not get the bios to recognise the new slave drive. you have to enter the bios and look for an entry that reads something like auto detect drives. Do it for each master and slave for each IDE channel. Then press save changes and exit.
If you have jumpered and cabled the drives correctly (as masster /slave not cs) the pc will then boot with the proper drive as master. The slave goes in the middle position on the cable.

If you can then boot but still have trouble with the slave drive, try downloading Maxtor's own tools or a data recovery utility.

http://www.majorgeeks.com/downloads8.html

http://www.asci-red.net/tools.htm#hmt


Studio T