SDImgr.wsf multi partitions

  • Thread starter Thread starter Jason
  • Start date Start date
J

Jason

If I use diskpart to create 4 partitions on one physical drive, can I use
sdimgr.wsf to install my sdi file onto physical disk 1 partition 2, physical
disk 1 partition 3

Any ideas?
 
These would be seperate command lines. One for each partition. sdimgr
command uses drive letters so if these are D and E drivers than the command
would be:

sdimgr <SDIfile.sdi> /writepart:d: /yes
sdimgr <SDIfile.sdi> /writepart:e: /yes

Otherwise you can pull the Hard drive out. Connect it to a USB to IDE cable,
plug the USB into the development machine, and copy the image directly to
the drive.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.
 
I've been using the cmd
sdimgr.wsf recovery.sdi /writedisk:0 /yes (which works)

can I just simply replace that line with the following and excpet it to work
(assuming I've already used diskpart to create the partitions)?
sdimgr.wsf recovery.sdi /writepart::c /yes
sdimgr.wsf recovery.sdi /writepart::d /yes
sdimgr.wsf recovery.sdi /writepart::e /yes
sdimgr.wsf recovery.sdi /writepart::f//yes

Also when the sdimgr gets done with the first one, it wont restart.... until
I tell it correct??
 
I don't know. Because SDIMGR is a script it might only do one at a time, but
it may try to do all 4. Try it and find out.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.
 
Sean

When I tried the cmd sdimgr.wsf recovery.sdi /writepart::c /yes I got a
error 9011 (0X2333) in "CmdWritePart": Partition blob not found

How do I create a partition blob? I've got my XPE machine up and running,
so how do I create a SDI file that is a parition blob?
 
You have to create a second SDI file using SDIMGR and use SDIMGR to copy the
contents from the mounted SDI file to the partition blob of the second SDI
file.Use the second SDI file for transfer to the target. My XPE Advanced
book covers these steps.

I recommend Winternal's Remote Recover because it simply mounts the remote
drive to my development machine. With the drive mounted, I can partition,
format, and copy the image(s) to the drive. It is pricy, but makes
development easier.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.
 
Sean

I've got XPe on two partitions and I've modified the boot.ini to read.....
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="XP Embeddd parition
1/fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="XP Embeddd parition
2/fastdetect
and the timeout is 20 seconds

When I reboot the boot I get the boot menu, but even if I select partition2
it appears as though I'm booting from the first parition. I'm assuming that
because I've got two local accounts, and I use different ones for the
different choices in the boot process. As I've populated the desktop
folder, the chanced are made to the user accounts on the C parition and the
D partition is never changed..

Basically the files on the C drive always stay on the C drive, and the files
on the D drive always stay on the D drive no matter what boot option I
select.

I'm using sdimgr.wsf testimg.sdi /readpart:c: /yes to create the sdi file
and then sdimgr.wsf testimg.sdi /readpart:d: /yes sdimgr.wsf testimg.sdi
/readpart:d: /yes to write to two partitions.
I've used diskpart to create partition primary size=3000
assign letter=x


Am I missing something as far as getting XPe to dual boot?
 
Jason said:
Sean

I've got XPe on two partitions and I've modified the boot.ini to read.....
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="XP Embeddd parition
1/fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="XP Embeddd parition
2/fastdetect
and the timeout is 20 seconds
Click to expand...
ANd is the same boot.ini on both partitions?
 
No, it's not. I left the boot.ini on the second partition alone.
Should I have changed the second one to reflect the changes?
 
I put the same boot.ini that is on the C drive onto the D drive and still no
luck. The C drive is always the same no matter what option I select in the
boot menu.
 
Jason said:
I put the same boot.ini that is on the C drive onto the D drive and still no
luck. The C drive is always the same no matter what option I select in the
boot menu.
Click to expand...
You mean that it boots from partition 1 no matter what, or that
whichever one it boots to is c:?
 
That is correct.
I've changed my boot.ini to multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="XP
Embeddd parition 2/fastdetect. When it boots and I'm looged in, I do a
Start | run C:\ and the files I see are from partition 1.

If I go into disk managment it shows D as (boot). When I created my SDI
image, it was from a single drive that was C and I'm using writepart to
write that blob to a partition I've precreated with diskpart
 
Jason said:
That is correct.
I've changed my boot.ini to multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="XP
Embeddd parition 2/fastdetect. When it boots and I'm looged in, I do a
Start | run C:\ and the files I see are from partition 1.

If I go into disk managment it shows D as (boot). When I created my SDI
image, it was from a single drive that was C and I'm using writepart to
write that blob to a partition I've precreated with diskpart
Click to expand...
So it's booting from d:?
 
I've got three partitions C D E
The first time I logged in, I log into the C drive (boot.ini has been
modified yet)
In the C drive I created a folder called "This is C"
Then from My Computer I went into the D drive and created afolder called
"This is D"
Then from My Computer I went into the E drive and created a folder called
"This is E"

Then I made in modifactions to the boot.ini arc paths partitions 1,2,3

When I reboot if I select the third option or the second I always see
c:\This is C
and when I look at diskmanagment the D or E drives have the word (boot) next
to them.

I really don't understand what is going on, this should e working. I've ran
fbreseal on all partitions thinkinf it was remembering the mount point, but
that didn't help me.
"

Any ideas?
 
Back
Top