Re: sdi2hd works in cf?



Leandro,

Oh, I see. DOS image booted remotely is ok to use sdi2hd.

Obviously, to use SDIMgr you'd need to boot (over PXE?) an XP/XPe/PE based image with scripting enabled. Btw, this approach is
pretty well tested by many of us here - works fine. WinPE licensing here is obvious. You could also create a small hardware
dependent XPe image to boot with RBM (PXE) and you don't really have to buy additional licenses for this image since it is only used
in deployment/recovery scenarios.

But lets go back to your issue. I recall sdi approach had an issue while laying down the image with SDI tools.
First of all, how do you get your SDI file? You should only capture it on the target hardware (target storage - CF). Don't use SDI
loaded virtual disk for that or you will encounter some issues with not matching the target hardware configuration.
Also, after you expanded SDI file to the CF make sure MBR is boot sectors look good (easy to compare with original sector contents
when the CF was bootable).

--
=========
Regards,
KM

Km,

"How did you manage to run it under XP/XPe? Can you show us the exact steps
you performed?"
I boot with one PXE Image of dos. I copied the sdi2hd.exe to the server tftp
and used when i booted in PXE mode.

I tried to use SDIMgr tool too, but occurs the same problem

when i put the Cf in device the error is:

A disk read error occurred
Press Ctrl + Alt + Del to restart

Thanks


"KM" wrote:

Leandro,

sdi2hd is a DOS utility (16 bit) - http://msdn.microsoft.com/library/en-us/xpehelp/html/cdconSDIDataExtractionTool.asp.
How did you manage to run it under XP/XPe? Can you show us the exact steps you performed?

You can use SDIMgr tool to expand the SDI file on the local storage (search products docs and this NG archive on how to do that).

Also, when you say "WinXPE does not boot", what exactly happens there on the screen?

Btw, before going PXE way I'd recommend you to finish up with SDI extraction locally on the device. Otherwise you are going to be
mixing problems and confusing issues from PXE and SDI.

--
=========
Regards,
KM

Hi,

I'm trying to copy one sdi image to my device using a PXE boot and the
sdi2hd utility. But the storage of my device is a CF, when the process of
"extraction" is completed a try to boot with the CF and the WinXPE does not
boot!

In the company that i work we need one tool that works in this way, because
i build de xpe image, installs what i need and I liberate the image for the
homolagation team(in a single file, to they boot the device in pxe and upload
the image for the CF).

If its not possible with the sdi image, anyone knows other tool to do
this(in the past we uses the norton ghost, but for the reason of license, we
stop to use it).

Tnks

Ps: The image in CF will NOT be read-only!
PS?: Sorrry for the poor english!! ;)





.



Relevant Pages

  • Re: sdi2hd works in cf?
    ... I Tried to create the sdi file in two forms, ... to use SDIMgr you'd need to boot (over PXE?) an XP/XPe/PE based image with scripting enabled. ...
    (microsoft.public.windowsxp.embedded)
  • PXE boot from X4100 - Solaris 10 11/06
    ... I am having real problems getting Solaris 10 11/06 x64 booting from PXE ... # Start off by initialising DHCP ... enable PXE boot by creating ... This E-mail is from IPC Media Ltd, a company registered in England and ...
    (SunManagers)
  • (BlueBottle) Network Boot Thoughts
    ... I have booted a MS DOS 6.22 environment, FreeBSD, and a tiny "hello world" program of my own devising. ... So I am poised to take another small step toward a network boot diskless bluebottle system. ... It seems to be built on layers of other stuff, all of which seems to be more and more homework and firmly pre PXE epoch. ...
    (comp.lang.oberon)
  • Re: Booting a CE device over the network
    ... We boot DOS thru pxe but it is thru linux ... There's UDP support, DHCP support and TFTP server support (TFTP client ...
    (microsoft.public.windowsce.embedded)
  • pxeboot with IBM x335: failure
    ... I'm trying to boot an IMB x335 server via PXE. ... BIOS drive A: is disk0 ...
    (freebsd-stable)