Image deploy gives bsod. Did i misunderstand the procedure.

  • Thread starter Thread starter Jan Mikkelsen
  • Start date Start date
J

Jan Mikkelsen

Hello. im unsure if i have misunderstood something about deploying an image.

I created an image.
I created an iso using hd2iso.exe
I burned the iso
I booted the target machine up from the newly created cd... and bsod right
after it displays the WinXP Embedded Logo.

It looks like its just loading itself from the cd and that might be what its
supposed to do. But I wanted to create an image that was unpacked onto the
harddrive, like Norton Ghost or PQDI would do it.

Did I misunderstand ?

thanks

/Jan
 
KM,

The problem that the target drive is a 2.5" HD and the Development Drive is
a 3.5" Not sure how i would go about x-copying from one to another there.

The BSOD was : STOP: 0x0000007B (0xF7C1E640, 0xC0000034, 0x00000000,
0x00000000)

I did look at the guide, but step4 did not go as planed. will try it again
later.


/Jan
 
Jan,
The problem that the target drive is a 2.5" HD and the Development Drive is a 3.5" Not sure how i would go about x-copying from
one to another there.

What problems you expect from x-copying just files from one disk to another? (some problems could be only if you use some security
attributes on files on NTFS partition)
We are talking about preFBA image, right? And you built your image with Target Settings for the target drive?
The BSOD was : STOP: 0x0000007B (0xF7C1E640, 0xC0000034, 0x00000000, 0x00000000)
http://msdn.microsoft.com/embedded/community/community/tips/xp/stoperr7b/default.aspx

I did look at the guide, but step4 did not go as planed. will try it again later.

KM
 
What problems you expect from x-copying just files from one disk to
another? (some problems could be only if you use some security attributes
on files on NTFS partition)

Since the to drives has diffrent connections, im unsure how i would connect
the two in the same system, so that i could xcopy.
We are talking about preFBA image, right? And you built your image with
Target Settings for the target drive?

yes. i ran tap.exe on the target machine, inserted a new harddrive (same
model and type) and wanted to deploy the preFBA image on to that machine.

thanks, but the common causes it describes isnt the problem.
I did use tap.exe and the were no errors or anything from missing hardware
components before i build the image.


/ Jan
 
Jan,
Since the to drives has diffrent connections, im unsure how i would connect the two in the same system, so that i could xcopy.

Well.. You don't necessarily need to do a direct copy. Just use some temporary storage that is available from the systems with each
drive connected. Or use network is you have two computers.
thanks, but the common causes it describes isnt the problem.
I did use tap.exe and the were no errors or anything from missing hardware components before i build the image.

Running TAP does not promise you got all the required critical components.
First add all three Generic disk components. Make sure you've got IDE Channel components and PCI Bus.

Also, does you target have hardware RAID support? If so, you will need a driver for that.

If you happened to have XP Pro installed on the target, open Device Manager and check what drivers are installed there.

7B is very common error, so you will likely find more answers by searching the NG archive:
http://groups-beta.google.com/group...crosoft.public.windowsxp.embedded&q=7B&qt_g=1

KM
 
I managed to connect the 2.5" target drive to my pc and xcopy teh runtime
image to that drive.

now i get no BSOD on FBA. :)


/Jan
 
i think i got it solved now, thanks.

/jan

KM said:
Jan,


Well.. You don't necessarily need to do a direct copy. Just use some
temporary storage that is available from the systems with each drive
connected. Or use network is you have two computers.


Running TAP does not promise you got all the required critical components.
First add all three Generic disk components. Make sure you've got IDE
Channel components and PCI Bus.

Also, does you target have hardware RAID support? If so, you will need a
driver for that.

If you happened to have XP Pro installed on the target, open Device
Manager and check what drivers are installed there.

7B is very common error, so you will likely find more answers by searching
the NG archive:
http://groups-beta.google.com/group...crosoft.public.windowsxp.embedded&q=7B&qt_g=1

KM
 
Back
Top