Problem about deploy .sdi image remotely

[Guest]

Hi. My target device has one 250M HD and 256M RAM. My final purpose is to deploy remotely the image file --final.sdi to the hard disk, and then boot from the hard disk. The size of final.sdi is about 200M.

Now I can use a smaller image about 100M with network support to remote boot the target system.
The next step, I want to get the final.sdi from tftp server, and extract it to the hard disk
My problem is that:
The spaces of hard disk and RAM are limited, where can I store final.sdi

 

[KM]

Arlin,

You can remotely boot from your sdi image and at the run time (running the
remotely booted image) you can
1) prepare the HDD (partition with diskpart or etc., format)
2) copy over network an image (could be the same sdi file, or just xcopy the
image files)
3) if it is sdi, use sdimgr or sdi2hd tools to expand the sdi file to the
HDD
4) setup boot.ini on the HDD
5) reboot in to OS image from HDD (hopefully you can setup BIOS priorities
to boot from HDD first and then from LAN)

KM

Hi. My target device has one 250M HD and 256M RAM. My final purpose is to

deploy remotely the image file --final.sdi to the hard disk, and then boot
from the hard disk. The size of final.sdi is about 200M.

 

[Guest]

KM, if I remotely boot from the sdi image and copy the final.sdi over network, what is the details that I can expand the final.sdi? The XPE help document does not mention the means or the options about extract a sdi file. SDI2HD.exe is a DOS tool just only run on MS-DOS 6.22 or later. When I run SDI2HD.exe in cmd.exe, the error message reportted: "This Program cannot be run from windows, only MS-DOS(v6 or higher) is supported". How can I resolve it?

----- KM wrote: -----

Arlin,

You can remotely boot from your sdi image and at the run time (running the
remotely booted image) you can
1) prepare the HDD (partition with diskpart or etc., format)
2) copy over network an image (could be the same sdi file, or just xcopy the
image files)
3) if it is sdi, use sdimgr or sdi2hd tools to expand the sdi file to the
HDD
4) setup boot.ini on the HDD
5) reboot in to OS image from HDD (hopefully you can setup BIOS priorities
to boot from HDD first and then from LAN)

KM

 

[KM]

Arlin,

Sorry, I shouldn't mentioned sdi2hd tool since you are playing with XPe image (not DOS). You can remotely deploy a DOS image (using
e.g. 3Com utility) and then use sdi2hd but you don't need that as you got working XPe image that you're able to remotely boot.
Basically you will need to use SDIMgr at run time to expand an SDI image to HDD partition (or disk). Look for /writepart: and
/writedisk: command switches of the SDI Manager.
If you partition your HDD (e.g., with diskpart) and have PART blob in the SDI file, you will need to use /writepart switch.
If you want to expand the entire disk (may not be wise if you want big data partitions on HDD) and have DISK blob, use /writedisk
switch.

To make SDIMgr working at your runtime, include WScript support and "\Program Files\Windows Embedded\bin\sdiaut.dll" library (needs
to be registred) into your image.

--
KM,
BSquare Corporation

KM, if I remotely boot from the sdi image and copy the final.sdi over network, what is the details that I can expand the

final.sdi? The XPE help document does not mention the means or the options about extract a sdi file. SDI2HD.exe is a DOS tool just
only run on MS-DOS 6.22 or later. When I run SDI2HD.exe in cmd.exe, the error message reportted: "This Program cannot be run from
windows, only MS-DOS(v6 or higher) is supported". How can I resolve it?

 

[Guest]

Thanks to KM, now I can expand a SDI image to my HD
I still have questions need help
You have suggested me

2) copy over network an image (could be the same sdi file, or just xcopy th

image files
To use xcopy or copy , I have to mapping a net disk at first which need a username and the password. But I do not want to input the username and password. I need the download process can run from un-unique tftp server with the file folder which includes the SDI file is not in shared. So I choose to use tftp .
There is a tftpd on the server device. When I use tftp at my target device, it will interrupt with the message "timeout occurred" after download about 32M. The total size of the file is about 110M
What is problem? If it's Net Card's problem, but I can remote boot the 110M SDI image using it, how to explain it

 

[KM]

Arlin,

Read this thread:
http://groups.google.com/groups?hl=...220521534%40newssvr12.news.prodigy.com&rnum=6

You may try another tftp client. Or better switch to more realible and less
restricted protocol.

Btw, you can always automate (e.g., a batch file) copy'ing your image from
the server. You will just have to use a command like "net use /USER
password".

KM

PS. I am not an export in tftp. Maybe someone who have tried what you are
trying to accomplish may jump in here and reply you.

Thanks to KM, now I can expand a SDI image to my HD.
I still have questions need help:
You have suggested me: the
image files)
To use xcopy or copy , I have to mapping a net disk at first which need a

username and the password. But I do not want to input the username and
password. I need the download process can run from un-unique tftp server
with the file folder which includes the SDI file is not in shared. So I
choose to use tftp .

There is a tftpd on the server device. When I use tftp at my target

device, it will interrupt with the message "timeout occurred" after download
about 32M. The total size of the file is about 110M.

What is problem? If it's Net Card's problem, but I can remote boot the

110M SDI image using it, how to explain it?

 

[Guest]

KM, in order to to support SDIMgr, I had completed those tasks
1. Add the register keys to the image as a component which is relative to sdiaut.dll
2.Boot the image on target device
3.Copy the file sdimgr.wsf and sdiaut.dll to the respective file folder "c:\program files\windows embedded\utilities" and "c:\program files\windows embedded\bin" in target device
4.Install wscript in target device
5.Then, run "c:\program files\windows embedded\utilities\sdimgr"
An error occured:"can't find the file c:\program files\windows embedded\utilities\sdimgr.wsf". But in truth, there is the file sdimgr.wsf. What can I do?

 

[KM]

Arlin,

There is a known bug in WScript component that does not install proper registry keys for WScript to run scripts.
Try simply run "wscript <you script path>" instead. Or search NG for the registry fix for WScript component.

Also, I would suggest you to grab registry keys for sdiaut.dll. Instead you better use FBA DLL Registration resource. This would be
more appropriate. Your component (or TD Extra Resources) could also copy the necessary files to the image.

--
KM,
BSquare Corporation

KM, in order to to support SDIMgr, I had completed those tasks:
1. Add the register keys to the image as a component which is relative to sdiaut.dll
2.Boot the image on target device
3.Copy the file sdimgr.wsf and sdiaut.dll to the respective file folder "c:\program files\windows embedded\utilities" and

"c:\program files\windows embedded\bin" in target device.

4.Install wscript in target device.
5.Then, run "c:\program files\windows embedded\utilities\sdimgr".
An error occured:"can't find the file c:\program files\windows embedded\utilities\sdimgr.wsf". But in truth, there is the file

sdimgr.wsf. What can I do?