BootSDI

whats the easiest way to roll the files created by bootsdi into an iso for virtual testing or maybe
a better question is how to virtually test the files created by the bootsdi script with vmware?

whats the easiest way to roll the files created by bootsdi into an iso for virtual testing or maybe
a better question is how to virtually test the files created by the bootsdi script with vmware?

Maybe that is a lack of my English knowledge (For you it is native, I've had only one year at school, and some knowledge increases by business trips to US):
Can you explain a bit simplier what you need?

BootSDI only creates one file, an image which can be read by the W2003 ramdisk driver.

Peter

Maybe that is a lack of my English knowledge (For you it is native, I've had only one year at school, and some knowledge increases by business trips to US):
Can you explain a bit simplier what you need?

BootSDI only creates one file, an image which can be read by the W2003 ramdisk driver.

Peter

peter, sorry, sometimes i dont ask clear questions. from what i understand bootsdi writes files to be transferred to an usb device for booting a pc. what i am asking is there anyway to test the sdi files - img
virtually in vmware. can the sdi build be converted to an .iso?

-c

BootSDI works the way as you've said, but you don't have to use the 'usb' option (I don't). You also have the option of building an .iso image which contains the image to be loaded into ram at boot. This .iso may be easily tested in a virtual machine.

Regards,
Galapo.

peter, sorry, sometimes i dont ask clear questions. from what i understand bootsdi writes files to be transferred to an usb device for booting a pc. what i am asking is there anyway to test the sdi files - img
virtually in vmware. can the sdi build be converted to an .iso?

-c

This question I cannot answer. But there are truely many members who can. The question can be changed to:

'I have a vdk disk image. How to see in VMWare or other emulators?'

Peter

BootSDI works the way as you've said, but you don't have to use the 'usb' option (I don't). You also have the option of building an .iso image which contains the image to be loaded into ram at boot. This .iso may be easily tested in a virtual machine.

Regards,
Galapo.

G'day Galapo:


thats what i'm looking for but i must not have something set right. i build the ram folder but no iso. what do you have checked on your gui?

-c

Here you go:


Hope this helps!

Regards,
Galapo.

Here you go:


Hope this helps!

Regards,
Galapo.

thanks galapo. hey by the way, is %globaltemplates% the same as - %ProjectDir%\workbench\common?

oops, almost forgot. do you use ramdisk with temp=b: or what?

-c

Yes, %GlobalTemplates%=%GlobalSupport%\Common. %GlobalSupport%=%BaseDir%\Workbench.

Yes, I still use ramdrive at b: but this is not essential as %SystemDrive% is writable with BootSDI so %temp% etc can be located there.

Regards,
Galapo.

Yes, %GlobalTemplates%=%GlobalSupport%\Common. %GlobalSupport%=%BaseDir%\Workbench.

Yes, I still use ramdrive at b: but this is not essential as %SystemDrive% is writable with BootSDI so %temp% etc can be located there.

Regards,
Galapo.

ive tried this before but ive had cant find browseui and other errors on boot. do i need filebasedwritefilter
enabled???

-c

ive tried this before but ive had cant find browseui and other errors on boot. do i need filebasedwritefilter
enabled???

No, fbwf will do nothing as %SystemDrive% is not non-writable.

I'm sorry, but I do not know what to do about your errors.

Regards,
Galapo.

@carfan
Cannot say if this answer your question (or one of them), but the image file made by BootSDI, as the name completely fails to imply, is not a .sdi image, but rather a RAW image, see here:
http://www.boot-land...?...=1580&st=59
http://www.boot-land...?...=1580&st=80

With the proper offset it can be mounted with IMDISK, for example or (if it is a "proper" RAW "DISK" image with VDK) so that you can add/delete/modify files in it.

jaclaz