About those 7b errors

[Eric S.]

After wasting countless hours reading forums and trying different things, I
thought I might just ask here for help: I was trying to deploy XPe on a
dual machine with SCSi and raids, after noticing that it's not as easy as it
looks, and getting loads of 7b errors, I thought I might try this down on a
lesser scale.

I popped an evaluation version of vmware, installed XP on it, then XPe
tools, did a TAP, added the SCSI component and the Video components, added
them to the database... now all I am missing is STORAGE\volume. Even if I
add the 3 disk drive components from the component lists, I am still
BSODing..I tried running off an ERD CD, ran TAP, built an image out of that,
32 of 33 drives found, missing only that STORAGE\volume component again.
Is there a way or a doc somewhere to fix the boot problem probably caused by
this? I am running out of ideas, I did check the Genericdevice key that a
document from microsoft is pointing to.... I am guessing the Storage\volume
thing is the key but maybe it's something else?

A lot of 7b postings on the net are about people with problems, once they
find the solutions, you don't hear back from them , please... if something
works, I'll confirm it

Eric.

 

[Slobodan Brcin \(eMVP\)]

Hi Eric,

Try these searches:
http://groups.google.com/groups?hl=...a=group=microsoft.public.windowsxp.embedded.*
http://groups.google.com/groups?hl=...a=group=microsoft.public.windowsxp.embedded.*
http://groups.google.com/groups?hl=...a=group=microsoft.public.windowsxp.embedded.*

Regards,
Slobodan

 

[Phil Smith]

I popped an evaluation version of vmware, installed XP on it, then XPe
tools, did a TAP, added the SCSI component and the Video components, added
them to the database... now all I am missing is STORAGE\volume. Even if I
add the 3 disk drive components from the component lists, I am still
BSODing..I tried running off an ERD CD, ran TAP, built an image out of that,
32 of 33 drives found, missing only that STORAGE\volume component again.

Eric,

I also ran TAP from within XP and also ended up with Storage\Volume
unresolved, but my image boots fine. I also did not add the video or
mouse; I add them later with "Install VMWare tools" from the VMWare
menu. VMWare 4.5.1 has std. VESA compatibility so you can get high res
even without the VMWare video driver.

I am not trying to use VMWare Buslogic SCSI yet; I tried to install it
after boot and it complains that the INF file is missing a required
section and fails. Yet the same driver installs fine in real XP and
W2K3. Given that std. XP has daily updates and my XPe is dated 9/2003,
I'm waiting for XPe + SP2 to come out.

I think you are being too ambitious initially to actually boot from a
VMWare SCSI hard disk.

Initially I was blowing up (7b) when deploying the image since I was not
copying all files (hidden, system) from the target build directory to
the boot image. The technique I now use is to create another virtual,
shared IDE drive that is the C: (boot) FAT16 drive of an Xpe VMWare
session and the F: drive (IDE 1:1) of the XP build system. Others have
used multi-boot and a single XP/XPe session to test XPe images but the
problem with that is that the XPe image is not on C: so you have to make
adjustments.

Phil

 

[Eric]

Initially I was blowing up (7b) when deploying the image since I was not

copying all files (hidden, system) from the target build directory to
the boot image. The technique I now use is to create another virtual,
shared IDE drive that is the C: (boot) FAT16 drive of an Xpe VMWare
session and the F: drive (IDE 1:1) of the XP build system. Others have
used multi-boot and a single XP/XPe session to test XPe images but the
problem with that is that the XPe image is not on C: so you have to make
adjustments.

The problem is I am not even getting there.

To make it clear, it's a standard VMWare install, when I was
mentionning SCSI it as just that I added every drivers I could find my
hands on, but it is running IDE.

With the demo on microsoft's website, what I saw was that the guy used
his laptop with 2 partitions, C:\ being system and let's say D:\ being
XPe.

You have to modify the boot.ini file in order to go boot from that
partition, this was done and it started booting, but it 7b after a
while, after running it in debug mode I noticed it crashed at
classpnp.sys.

I don't know if it's something related to the boot.ini file, I'd guess
not since it's finding the proper files. It's not something I done
with the TAPping process because I can tell that I've been doing it
over 100 times now in all kind of different ways (adding components,
removing, adding some of the built-in templates, etc).

The only thing I didn't try which you pointed is to make another drive
image and treat it as root and boot from it with another vmware
session (go to a drive instead of a partition). I don't think this is
related to the classpnp.sys crashing though.

Slobodan gave me links to check but I already went through them before
posting, didn't help or I missed something too obvious.

thanks

 

[KM]

Eric,

You are missing a critical boot driver.
Have you check if you got proper disk driver, IDE chnnel components, PCI
bus, etc?
Read this tip page:
http://msdn.microsoft.com/embedded/community/community/tips/xp/stoperr7b/default.aspx

Also, before going to VMWare environment on that machine, are you able to
create a working XPe image just on another partition of your dev machine?

Also, you can compare your project to Brad's Virtial PC slx from
www.xpefiles.com:
http://www.xpefiles.com/a_file.cfm?custid=Development Utilities&fileid=vpc.zip&groupName=Main.

KM