Stop code 7B

[Dean Macinskas]

I ran TAP on my target board (Epox EP-8KMM3I) and imported the pmq file into
TD. The import reported:

Could not find a driver for Multimedia Audio Controller
(PCI\VEN_1106&DEV_3059&SUBSYS_30051695&REV_60).
Could not find a driver for Video Controller (VGA Compatible)
(PCI\VEN_1106&DEV_7205&SUBSYS_90231695&REV_01).
Import succeeded with 43 drivers for 45 devices.

Not knowing what to do with this, I added FAT and NTFS, built an image and
got stop code 7B when I booted it.

Would the failure to resolve the "not found" driver reported be the problem?
Is there an easy way to take the video drivers supplied by Epox and add them
as components?

As always, thanks for your help.
--
Regards,
Dean P. Macinskas
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Digital Devices, Inc. Phone: (215) 258-3593 x105
118 South Second Street Fax: (215) 258-3579
Perkasie, PA 18944
USA
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
"The major difference between a thing that might go wrong
and a thing that cannot possibly go wrong
is that when a thing that cannot possibly go wrong goes wrong
it usually turns out to be impossible to get at and repair."
- Douglas Adams

 

[Gordon Smith \(eMVP\)]

I ran TAP on my target board (Epox EP-8KMM3I) and imported the pmq
file into TD. The import reported:

Could not find a driver for Multimedia Audio Controller
(PCI\VEN_1106&DEV_3059&SUBSYS_30051695&REV_60).
Could not find a driver for Video Controller (VGA Compatible)
(PCI\VEN_1106&DEV_7205&SUBSYS_90231695&REV_01).
Import succeeded with 43 drivers for 45 devices.

Not knowing what to do with this, I added FAT and NTFS, built an
image and got stop code 7B when I booted it.

Would the failure to resolve the "not found" driver reported be the
problem? Is there an easy way to take the video drivers supplied by
Epox and add them as components?

As always, thanks for your help.

1. You'll be happy later if you import the TAP into Component Designer and
create a component for your hardware instead of importing directly into TD.
It's more flexible. Remember to base your new component off of the
"Selector Prototype Component".
2. Have you double checked the target path settings? (like d: instead of
c: depending on your device)
3. "It depends". Some drivers are incredibly simple - import the INF into
Component Designer, create a repository to hold the files, import the new
component and use it in your build. If that doesn't work, come back and ask
for more advise.

 

[Dean Macinskas]

Comments inline...

1. You'll be happy later if you import the TAP into Component Designer and
create a component for your hardware instead of importing directly into TD.
It's more flexible. Remember to base your new component off of the
"Selector Prototype Component".

I'll take your suggestion. But my real question is: if the stop code 0x7B
indicates a missing critical driver, how do I know what driver is missing?

2. Have you double checked the target path settings? (like d: instead of
c: depending on your device)

Yes - appears to be OK.

3. "It depends". Some drivers are incredibly simple - import the INF into
Component Designer, create a repository to hold the files, import the new
component and use it in your build. If that doesn't work, come back and ask
for more advise.

According to the MSDN article
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/ht
ml/cdtskImportingDataFromINFFileIntoSLDFile.asp) one first has to install
the driver. Well, the driver I want to import is for hardware that does not
exist on my development platform. Aren't I going to seriously muck up my
dev platform if I start installing drivers that have nothing to do with its
hardware?

 

[Brad Combs]

Hi Dean,

If you have drivers for your systems hardware, and there are no components
already in the DB for them then you'll want to componentize the drivers
first, then import the PMQ into Component Designer as Gordon suggested. This
will allow the import to find all the devices that TAP found and add them to
the configuration. As for the 7B check out...

http://www.seanliming.com/Docs/XPE Stop 0x0000007B Error.pdf

or search this group on google.
http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded

This error is from a missing driver for the controller that the boot disk is
attached to. Try some of the suggestions in Sean's article.

HTH,
Brad

 

[Dean Macinskas]

Hi Dean,

If you have drivers for your systems hardware, and there are no components
already in the DB for them then you'll want to componentize the drivers
first, then import the PMQ into Component Designer as Gordon suggested. This
will allow the import to find all the devices that TAP found and add them to
the configuration.

Right. But the article on doing this in MSDN says the first thing you do is
install the driver on your PC. But the driver I want to componentize is NOT
a driver for my dev PC, it's for my target. I really don't want to install
a completely unrelated driver on my dev PC - I wanted to componentize it
directly from the CD it came on. Is this possible?

Regards,
Dean

 

[KM]

Dean,

Right. But the article on doing this in MSDN says the first thing you do is
install the driver on your PC. But the driver I want to componentize is NOT
a driver for my dev PC, it's for my target. I really don't want to install
a completely unrelated driver on my dev PC - I wanted to componentize it
directly from the CD it came on. Is this possible?

It certainly is.
http://msdn.microsoft.com/embedded/community/community/tips/xp/thrdprty/default.aspx

Although it is all x86 world you don't really need to mix things up and install target device drivers on dev machine.
You sometimes even cannot install a driver on your dev PC due to lack of particular hadrware support there for which the driver is
needed.

 

[Dean Macinskas]

It certainly is.
http://msdn.microsoft.com/embedded/community/community/tips/xp/thrdprty/default.aspx

Although it is all x86 world you don't really need to mix things up and

install target device drivers on dev machine.

You sometimes even cannot install a driver on your dev PC due to lack of

particular hadrware support there for which the driver is

needed.

I followed the Component Designer procedure (or thought I did) to import a
driver from an INF file, and specified a repository directory. I then
imported it into the component database with Component Database Manager (no
errors were reported). But I don't see my named repository in the target
directory, and when I try to add my component in TD it complains that it
can't find specified files in the repository:

Info 101: Initializing new component: "VIA/S3G UniChrome IGP [Version
6.14.10.0123, R2]"
Warning 1116: Adding unreleased component to configuration: "VIA/S3G
UniChrome IGP [Version 6.14.10.0123, R2]"
Warning 1121: Can not find the resource viagfx.cat for VIA/S3G UniChrome
IGP
Warning 1121: in the following search path:
\\XP-EMBED\Repositories\\{CB5844E6-6C94-425F-8277-D0B740DBCC02},
\\XP-EMBED\Repositories\{022716D8-0CF0-4779-B94C-8E52EB36709C},
\\XP-EMBED\Repositories\{347677C8-8935-4d30-8DDA-FB6D701ACF47},
\\XP-EMBED\Repositories\{484C9D34-846E-40E2-A2E6-FF2771A303D5}
Warning 1121: The estimated configuration size may not be accurate.
Warning 1121: Can not find the resource kmviagi.inf for VIA/S3G UniChrome
IGP
Warning 1121: in the following search path:
\\XP-EMBED\Repositories\\{CB5844E6-6C94-425F-8277-D0B740DBCC02},
\\XP-EMBED\Repositories\{022716D8-0CF0-4779-B94C-8E52EB36709C},
\\XP-EMBED\Repositories\{347677C8-8935-4d30-8DDA-FB6D701ACF47},
\\XP-EMBED\Repositories\{484C9D34-846E-40E2-A2E6-FF2771A303D5}
Warning 1121: The estimated configuration size may not be accurate.
Warning 1121: Can not find the resource vtmini.sys for VIA/S3G UniChrome
IGP
Warning 1121: in the following search path:
\\XP-EMBED\Repositories\\{CB5844E6-6C94-425F-8277-D0B740DBCC02},
\\XP-EMBED\Repositories\{022716D8-0CF0-4779-B94C-8E52EB36709C},
\\XP-EMBED\Repositories\{347677C8-8935-4d30-8DDA-FB6D701ACF47},
\\XP-EMBED\Repositories\{484C9D34-846E-40E2-A2E6-FF2771A303D5}
Warning 1121: The estimated configuration size may not be accurate.
....

Did I do something wrong during the import phase in CD or the database
update phase in CDM? How do I diagnose and fix this?

Thanks for any pointers and help.

Regards,
Dean

 

[Guest]

I think you are overcomplicating things. You have two
separate issues. One is if the missing files are causoing
the 7b and the other is componentizing the driver.
First componentize the target hardware device.
--Run TAP.EXE. Open the component designer and import
that PMQ. Open up the component, and in component
properties, just change the PROTOTYPE FIELD to selector
prototype component (Software > Test and Development).
Check the "Component instances are editable". Leave the
repository at unknown. Save it, close the component and
then open the database manager and import it.
In Target designer, create a build with your component,
then under settings, uncheck the audio so that it isn't
going to use it. Assuming the system will use a VGA
driver, if it can't find the proper video driver, it will
load the VGASAVE. Do your normal dependency check and
build and see if you get the same error. I don't think
you will.

The other issue is the driver comonentization. It sounds
as though all the files where not imported by the
database manager, or all the needed files are not picked
up by the importation process. I have found it easier to
comment out the .INF and get it pared down to just the
actual driver you are looking for. If it is installed on
your target system already, you can get the PIC/VEN
DEVICE ID and SUBSYS# from poking around in the driver
under (XP PRO) device manager and details it will list
all the info for the proper driver.

Steve Worcester - Avnet Applied Computing

I followed the Component Designer procedure (or thought I did) to import a
driver from an INF file, and specified a repository directory. I then
imported it into the component database with Component Database Manager (no
errors were reported). But I don't see my named repository in the target
directory, and when I try to add my component in TD it complains that it
can't find specified files in the repository:

Info 101: Initializing new component: "VIA/S3G UniChrome IGP [Version
6.14.10.0123, R2]"
Warning 1116: Adding unreleased component to configuration: "VIA/S3G
UniChrome IGP [Version 6.14.10.0123, R2]"
Warning 1121: Can not find the resource viagfx.cat for VIA/S3G UniChrome
IGP
Warning 1121: in the following search path:
\\XP-EMBED\Repositories\\{CB5844E6-6C94-425F-8277- D0B740DBCC02},

\\XP-EMBED\Repositories\{022716D8-0CF0-4779-B94C- 8E52EB36709C},
\\XP-EMBED\Repositories\{347677C8-8935-4d30-8DDA- FB6D701ACF47},
\\XP-EMBED\Repositories\{484C9D34-846E-40E2-A2E6-

FF2771A303D5}
Warning 1121: The estimated configuration size may not be accurate.
Warning 1121: Can not find the resource kmviagi.inf for VIA/S3G UniChrome
IGP
Warning 1121: in the following search path:
\\XP-EMBED\Repositories\\{CB5844E6-6C94-425F-8277- D0B740DBCC02},

\\XP-EMBED\Repositories\{022716D8-0CF0-4779-B94C- 8E52EB36709C},
\\XP-EMBED\Repositories\{347677C8-8935-4d30-8DDA- FB6D701ACF47},
\\XP-EMBED\Repositories\{484C9D34-846E-40E2-A2E6-

FF2771A303D5}
Warning 1121: The estimated configuration size may not be accurate.
Warning 1121: Can not find the resource vtmini.sys for VIA/S3G UniChrome
IGP
Warning 1121: in the following search path:
\\XP-EMBED\Repositories\\{CB5844E6-6C94-425F-8277- D0B740DBCC02},

\\XP-EMBED\Repositories\{022716D8-0CF0-4779-B94C- 8E52EB36709C},
\\XP-EMBED\Repositories\{347677C8-8935-4d30-8DDA- FB6D701ACF47},
\\XP-EMBED\Repositories\{484C9D34-846E-40E2-A2E6-

FF2771A303D5}
Warning 1121: The estimated configuration size may not be accurate.
....

Did I do something wrong during the import phase in CD or the database
update phase in CDM? How do I diagnose and fix this?

Thanks for any pointers and help.

Regards,
Dean


.

 

[KM]

Dean,

To fix the repository problem, make sure that you set "Copy repository files to repository root" checkbox on the CDM Import dialog
when you are trying to import the component once again.

--
Regards,
KM, BSquare Corp.

It certainly is.
http://msdn.microsoft.com/embedded/community/community/tips/xp/thrdprty/default.aspx

Although it is all x86 world you don't really need to mix things up and

install target device drivers on dev machine.

You sometimes even cannot install a driver on your dev PC due to lack of

particular hadrware support there for which the driver is

needed.

I followed the Component Designer procedure (or thought I did) to import a
driver from an INF file, and specified a repository directory. I then
imported it into the component database with Component Database Manager (no
errors were reported). But I don't see my named repository in the target
directory, and when I try to add my component in TD it complains that it
can't find specified files in the repository:

Info 101: Initializing new component: "VIA/S3G UniChrome IGP [Version
6.14.10.0123, R2]"
Warning 1116: Adding unreleased component to configuration: "VIA/S3G
UniChrome IGP [Version 6.14.10.0123, R2]"
Warning 1121: Can not find the resource viagfx.cat for VIA/S3G UniChrome
IGP
Warning 1121: in the following search path:
\\XP-EMBED\Repositories\\{CB5844E6-6C94-425F-8277-D0B740DBCC02},
\\XP-EMBED\Repositories\{022716D8-0CF0-4779-B94C-8E52EB36709C},
\\XP-EMBED\Repositories\{347677C8-8935-4d30-8DDA-FB6D701ACF47},
\\XP-EMBED\Repositories\{484C9D34-846E-40E2-A2E6-FF2771A303D5}
Warning 1121: The estimated configuration size may not be accurate.
Warning 1121: Can not find the resource kmviagi.inf for VIA/S3G UniChrome
IGP
Warning 1121: in the following search path:
\\XP-EMBED\Repositories\\{CB5844E6-6C94-425F-8277-D0B740DBCC02},
\\XP-EMBED\Repositories\{022716D8-0CF0-4779-B94C-8E52EB36709C},
\\XP-EMBED\Repositories\{347677C8-8935-4d30-8DDA-FB6D701ACF47},
\\XP-EMBED\Repositories\{484C9D34-846E-40E2-A2E6-FF2771A303D5}
Warning 1121: The estimated configuration size may not be accurate.
Warning 1121: Can not find the resource vtmini.sys for VIA/S3G UniChrome
IGP
Warning 1121: in the following search path:
\\XP-EMBED\Repositories\\{CB5844E6-6C94-425F-8277-D0B740DBCC02},
\\XP-EMBED\Repositories\{022716D8-0CF0-4779-B94C-8E52EB36709C},
\\XP-EMBED\Repositories\{347677C8-8935-4d30-8DDA-FB6D701ACF47},
\\XP-EMBED\Repositories\{484C9D34-846E-40E2-A2E6-FF2771A303D5}
Warning 1121: The estimated configuration size may not be accurate.
...

Did I do something wrong during the import phase in CD or the database
update phase in CDM? How do I diagnose and fix this?

Thanks for any pointers and help.

Regards,
Dean

 

[Dean Macinskas]

I think you are overcomplicating things. You have two
separate issues. One is if the missing files are causoing
the 7b and the other is componentizing the driver.
First componentize the target hardware device.
--Run TAP.EXE. Open the component designer and import
that PMQ. Open up the component, and in component
properties, just change the PROTOTYPE FIELD to selector
prototype component (Software > Test and Development).
Check the "Component instances are editable". Leave the
repository at unknown. Save it, close the component and
then open the database manager and import it.
In Target designer, create a build with your component,
then under settings, uncheck the audio so that it isn't
going to use it. Assuming the system will use a VGA
driver, if it can't find the proper video driver, it will
load the VGASAVE. Do your normal dependency check and
build and see if you get the same error. I don't think
you will.

Steve,

I followed your procedure exactly and I still got a 7B stop code. If I
import the pmq directly into TD, a lot of other stuff is also pulled in, and
if I specify the generic video driver I get an image that boots. I admit
that converting my pmq to a component seems cleaner, but apparently things
are missed. Any idea why?

I'm not sure I understand "Assuming the system will use a VGA driver, if it
can't find the proper video driver, it will load the VGASAVE" - I searched
the database for "VGASAVE" and it doesn't appear.

The video driver on CD has cabs in it that apparently CompDesigner does not
expand, so the important stuff in them never gets imported. WinZip declares
that the cabs themselves do not conform to the post-1998 definitions, so I
can't extract the relevant stuff and point CD to it. I'm not sure at this
point how to import the video drivers supplied by Epox.

Regards,
Dean

 

[KM]

Dean,

Until the new driver, which is currently NOT in your XPe database, gets to the database, the PMQ import won't help you to include
the driver to the build.
Before the import you have to create (componentize) the driver first.

The "VGA Save" (Visibility=200) is the component you were looking for. Although I don't know how it can help you if the driver you
are fighting with is not the display one (7B is unlikely caused by a missing Display driver but rather a disk driver or related).


To extract the files from the install package just launch the installation and before clicking Next...Finish button, go and find the
extracted files from the install packages under a Temp directory. To be sure where they will be extracted to, launch the
installation with FileMon running in background.

Also, to extract a CAB file you should use EXPAND.EXE (run EXPAND.EXE /? to see the command line help).