Getting 7B BSOD

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

Guest

I'm VERY new to this and recently overcame an issue just getting booted to
DOS. Anyhow got that working and I ran Target Analyzer, loaded up the PNG
file it generated and made the most basic build I could. Effectively all I
did was load the PNG and then resolved dependencies. Chose standard loader,
FAT file system, explorer shell, chose all of the disk drives just to be
sure. The basics ... it came out to 100 meg. I load it up and I get the
white loading bar at the bottom of my screen and then instant BSOD .... 7B.
I'm not even sure where to go from here. I was using a compact flash card
initially but figured that might the problem so I got a laptop harddrive.
Both have the exact same end result, so the media doesn't seem to be the
issue.
 
Feral said:
I'm VERY new to this and recently overcame an issue just getting booted to
DOS. Anyhow got that working and I ran Target Analyzer,
Click to expand...

Right. First thing - ta.exe (as opposed to tap.exe, which runs under
XPPro or Win2k) is rubbish. It's highly unlikely to get you to a working
image.
You'll need to connect a hard drive of some sort to your hardware and
install XPPro. You say you had trouble getting DOS working, but if you
can't get XPPro to work, you'll never get XPe to.
 
If you boot the computer using CD #1 of the XP Embedded Tools
installation package you can run TAP.EXE that way, and then redirect
the output to a floppy disk, usb thumb drive or network connection.
That's the simplest way I know to run TAP. Boot from the CD, then type
TAP /?.

Also, when I first started I was very confused about the "Settings" at
the top of the configuration in the Target Designer, especially the
'arc path'. If you are trying to perform a mult-boot scenario you
probably have to adjust the drive letter settings and the Arc path.

The arc path specifies the partition # to boot (from 1 to 4), and is
usually multi(0)disk(0)rdisk(0)partition(1) to boot from the first
primary partition.

SteveS
 
Thank you guys so very much. Yeap all I had to do was load XP Pro, run
tap.exe, and then make the new build. Have over twice as many devices as
ta.exe, and it worked first try.

So it seems in order to install XPe, you need to own a copy of XP ... lol
.... that makes good business sense from microsoft's perspective I suppose :).
Sometimes I wish stuff like this just came with the manual. Ta.exe should
not even be distributed.
 
Feral said:
Thank you guys so very much. Yeap all I had to do was load XP Pro, run
tap.exe, and then make the new build. Have over twice as many devices as
ta.exe, and it worked first try.

So it seems in order to install XPe, you need to own a copy of XP ... lol
... that makes good business sense from microsoft's perspective I suppose :).
Sometimes I wish stuff like this just came with the manual. Ta.exe should
not even be distributed.
Click to expand...

ta.exe has its uses, for those who are already quite experienced at
finding what is missing in an image and who want to develop minimal images.
 
XP Embedded Advanced ... hmm ... will give it a look (need to learn how to
read I suppose). Thank you sir.
 
Back
Top