Is there an easy way to update a file in an SDI image in the field?

  • Thread starter Thread starter Mark K Vallevand
  • Start date Start date
M

Mark K Vallevand

I need to update a file that is in an SDI image.

I could send the SDI driver and SDI utility and walk though
mount/update/unmount. (Is is legal to send the SDI driver and utility to a
customer?)

Is there an easier way?

I could mount/update/unmount here and send the new SDI, but that doesn't
seem to be acceptable.
 
Hi Mark,
I could send the SDI driver and SDI utility and walk though
mount/update/unmount. (Is is legal to send the SDI driver and utility to a
customer?)
Click to expand...

Probably not. But you could tell them to download XPe demo :D. (Just kidding).
Is there an easier way?
Click to expand...
If you have same image that your customer have, then you can.
1. Make backup of that SDI image.
2. You should add files that you need.
3. Make a small tool that will store all differences between the two unmouted files in one file.
4. Make a small tool that will import all these changes from your small file to your customers SDI file.

Your file could be even compressed so it is easier to send and update.

What do you think?

Regards,
Slobodan
 
I thought of doing some sort of binary diff and patch.

I think I'm going to send them the whole image. Its not like they are using
a 19200 modem to load it.

--
Regards.
Mark K Vallevand
Slobodan Brcin (eMVP) said:
Hi Mark,


Probably not. But you could tell them to download XPe demo :D. (Just kidding).
If you have same image that your customer have, then you can.
1. Make backup of that SDI image.
2. You should add files that you need.
3. Make a small tool that will store all differences between the two unmouted files in one file.
4. Make a small tool that will import all these changes from your small
Click to expand...
file to your customers SDI file.
 
What I have is a USB bootable device that has a ramdisk sdi file on it. Its
used for backup and restore of the CF device. The XPe that runs from the
ramdisk does not use a fixed IP address. Some customers want a way to set
the IP address of the XPe that runs from the ramdisk. In fact, they insist
on it. I'm looking for a quick and simple way to implement that. Or,
generally, a way to implement network configuration with this ramdisk boot.

When the ramdisk image is booted, its C:, the USB device is D:, and the CF
device partitions are E: and F:. The customer can update the D: files, but
the C: files are in the SDI file.

I've thought of lots of things.
- Auto login that runs a batch file from D:. The customer updates the batch
file to set the IP address. Problems. Netsh, autologin, whatever else
needs to be added to a very tight image.
- Auto login that runs a user program which sets the IP address from a text
file on D:. Problems. Gotta right that program.
- A service that is started and sets the IP address from a text file on D:.
Problems. Gotta right that service.

Anyone solved this problem?
 
Mark,

I did not get exactly what is the problem?
You don't want to include Netsh and etc. to your mini image that is running off RAM (sdi)?
This makes sense. And yes, it has been done (I guess it has been done by many of us here).

E.g., for one of our customers I wrote a simple tool that was setting a static IP (some command line switches suported, etc.). I
implemented the tool working directly with registry network setting so the utility dependencies were minimal.
However, it would definitely be better for you to use IP Helper APIs to do the job.

Or use ready-to-go tools like ipchange.exe.
 
Back
Top