Cannot find PCI.SYS

  • Thread starter Thread starter Frank Natoli
  • Start date Start date
F

Frank Natoli

Built WinXPe SP1 image, no dependency errors, no errors of any kind.
Burned compact flash with image. Boot system. Complains of missing
PCI.SYS. File copy PCI.SYS onto compact flash from standard WinXP
installation. Reboot compact flash. Blue screen.

What component would contain PCI.SYS? Perhaps more importantly, how can
one research such a question? Thanks.
 
Frank said:
Built WinXPe SP1 image, no dependency errors, no errors of any kind.
Burned compact flash with image. Boot system. Complains of missing
PCI.SYS. File copy PCI.SYS onto compact flash from standard WinXP
installation. Reboot compact flash. Blue screen.

What component would contain PCI.SYS? Perhaps more importantly, how can
one research such a question? Thanks.
Click to expand...
Filters in target designer (the little funnel button) let you search the
database by a variety of criteria, including which components a
particular file is in.
pci.sys is in a large number of components. Did you use ta.exe or
tap.exe to create your .pmq and when you imported the PMQ did you get
any drivers which could not be found? It's unusual for everything to be
found, in my experience.
 
Good news, bad news.

Good news is your illumination of using the filters in the TA to search
for PCI.SYS produced as you predicted a gaggle of possible components.
I chose what appeared to be the most innocuous, i.e., PCI subsystem
itself. Added that component. Rechecked dependencies, no errors.
Rebuilt target image, no errors. Reformatted and setup compact flash.

Bad news is (after once running BOOTPREP.EXE) system immediately
crashes with:

*** STOP: 0x0000007B (0xF894E640, 0xC0000034, 0x00000000, 0x00000000)

Will attach kernel debugger to target system to encourage it to explain
the nature of the crash.

And yes, used TA.EXE to generate DEVICES.PMQ, which produced an
extremely modest list of devices. Upon import, there was no report of
missing drivers. This is a very modest single board computer with the
usual complement of peripherals: VGA, keyboard, mouse, LAN, compact
flash (used for WinXPe image) and hard drive (used for WinXPe Toolkit).

P.S. nice hoopskirt. I suppose the cardinal/clergyman behind you was
also in costume?
 
Hi Frank..
Have you used EWF Filter.
And if you are using than which mode are you using for the same.
 
Frank said:
Good news, bad news.

Good news is your illumination of using the filters in the TA to search
for PCI.SYS produced as you predicted a gaggle of possible components.
I chose what appeared to be the most innocuous, i.e., PCI subsystem
itself. Added that component. Rechecked dependencies, no errors.
Rebuilt target image, no errors. Reformatted and setup compact flash.

Bad news is (after once running BOOTPREP.EXE) system immediately
crashes with:

*** STOP: 0x0000007B (0xF894E640, 0xC0000034, 0x00000000, 0x00000000)

Will attach kernel debugger to target system to encourage it to explain
the nature of the crash.

And yes, used TA.EXE to generate DEVICES.PMQ, which produced an
extremely modest list of devices. Upon import, there was no report of
missing drivers. This is a very modest single board computer with the
usual complement of peripherals: VGA, keyboard, mouse, LAN, compact
flash (used for WinXPe image) and hard drive (used for WinXPe Toolkit).

P.S. nice hoopskirt. I suppose the cardinal/clergyman behind you was
also in costume?
Click to expand...
Bustle. :) And yes, Archchancellor Ridcully was indeed in costume.
I would suggest that you use tap.exe to get the list of devices - it's
much more reliable. However, a stop7b error is a very common one, and
usually down to missing or incorrect IDE-related stuff.
 
Back
Top