PCI bus and BSOD

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm older to computers but new to the XP Embedded and I'm not sure where to
start with this problem. I'm testing an image on an old PII PC and I keep
getting one of two errors. When I originally built the image I put in
everything for the PCI bridge chipset (all Intel) but when I booted it gave
me an error that it couple not find pci.sys. Not a big deal since it wasn't
there. I added the PCI Bus component, which added the pci.sys driver, but
when I boot I get the dreaded Blue Screen Of Death.

Any ideas, the pci.sys driver is the same version that is on all my other XP
machines, including ones with the same hardware but running a full version
of XP Pro.

Thanks
RC
 
Hi,

You should give us BSOD stop code and more hardware infos.

Also use TAP.exe to detect hardware on your target device.

BTW:
Don't you think that PII is little outdated for XPe?

What type of image are you making?

Regards,
Slobodan
 
Hi a thought... Hope you have checked the dependencies check for the
PCI .component....and yes if havent used tap then please go for it.
Probably it is pulling in some unwanted dependencies .. could be !!

Kesavan ..
 
Slobodan Brcin (eMVP) said:
Hi,

You should give us BSOD stop code and more hardware infos.
Click to expand...

STOP: 0x0000007B (0xFAF72640, 0xC0000034, 0x00000000, 0x00000000)

Also use TAP.exe to detect hardware on your target device.
Click to expand...

I gave it a try with the DOS version. Same problem.
One thing though, when I check for and resolve dependencies I have to select
a Disk Drive and it lists 3 with the same name. Based on the properties and
the actual filenames it looks like two of them are for specific hardware and
one is for a generic disk. I go with the generic but maybe I sould be using
one of the others.
BTW:
Don't you think that PII is little outdated for XPe?
Click to expand...
Not really, but in this case it's just for development and working out the
software issues. In the end it will be an 800MHz Celeron on a very small
form factor SBC.
What type of image are you making?
Click to expand...
It will be running a .NET based Web app.
 
RC,
STOP: 0x0000007B (0xFAF72640, 0xC0000034, 0x00000000, 0x00000000)
http://msdn.microsoft.com/embedded/community/tips/xp/stoperr7b/default.aspx

I gave it a try with the DOS version. Same problem.
Click to expand...

TAP will produce more extansive output than TA. From my experience, TA often can't pick up IDE Channel Controllers.
One thing though, when I check for and resolve dependencies I have to select
a Disk Drive and it lists 3 with the same name. Based on the properties and
the actual filenames it looks like two of them are for specific hardware and
one is for a generic disk. I go with the generic but maybe I sould be using one of the others.
Click to expand...

Try the one which cmiConcordanceID (extended property) contains "Disk drive:GenDisk"
Not really, but in this case it's just for development and working out the
software issues. In the end it will be an 800MHz Celeron on a very small form factor SBC.
Click to expand...

FBA may run pretty slow on your target. You will definitely speed up your development process if you have fast target (even for
development&testing purposes).
It will be running a .NET based Web app.
Click to expand...

Especially if you run .Net, you may consider faster target CPU.

KM
 
Use all three disk driver components. (No image size increase)
Also make sure that you have all required drivers for chipset, etc.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Well using TAP.exe instead of TA.exe did the job, it boots now. I am a bit
disappointed since I really didn't want to install 2k or XP manually each
time there is a hardware change. Anyone heard is MS plans on fixing TA.exe?

I do have another problem now, but that's another question and another post.
Thanks for you help.

KM said:
RC,

http://msdn.microsoft.com/embedded/community/tips/xp/stoperr7b/default.aspx

TAP will produce more extansive output than TA. From my experience, TA
Click to expand...
often can't pick up IDE Channel Controllers.
using one of the others.

Try the one which cmiConcordanceID (extended property) contains "Disk drive:GenDisk" form factor SBC.

FBA may run pretty slow on your target. You will definitely speed up your
Click to expand...
development process if you have fast target (even for
 
RC,

If you happened to have a CD-ROM on your target, you could run TAP from
WinPE Environment (bootable XPe/SP1 1-st CD).

KM
 
RC,

After some time and understanding how TA, TAP, and how all hardware drivers
works you will probably stop using TA or TAP.

You can find one recent long thread between Konstantin and me that describe
how you can make universal image that will work on different hardware.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Thanks, I tried doing it without but I guess I need a bit more practice
first. I'm going to go back and compare the TAP the TA and my original try
to see what was missed and where.

I went looking for you thread, but no luck. It might not be on the server
anymore. Do you have any idea on the date it started? Were you, or
Konstantin, the original poster?

Thanks for all you help.
RC
 
Konstantin,
I got to admit I was mostly a listener in that thread to the Slobodan's
Click to expand...
ideas :-)

No, you asked the right questions so we put great deal of useful info is in
that thread.

Best regards,
Slobodan
 
Back
Top