I tried the setextradata command to try and test the VM with an ISO, instead of USB but it didn't help.

Then I read that Vbox has to be restarted after using that command, so I tried that and got:

"Callee RC: CO_E_SERVER_EXEC_FAILURE"

and when I relaunched it still wouldn't boot from the ISO. So then I closed Vbox and ran the setextradata command again. I stil got that error when relaunching Vbox but the Win8 ISO actually boots now

The USB doesn't give the C4 error anymore but just goes black after the loading circle animation shows up but that's not surprising as it doesn't work on baremetal either, so I'll have to experiment with some ways of building the USB.

Having tested some more, it seems I can boot from the ISO (and other ISOs) but not if the USB VMDK is connected to the VM as then, whether I'm booting from the ISO or the USB, it just gets stuck with the spinning circle animation forever.

Thanks for this!

Have a question. I notice "[EMS Enabled]" beside the Windows 7 option in Windows Boot Manager setup screen. How do I remove EMS or disable?

Edited August 10, 201412 yr by seires

I wouldn't touch it, it is exactly as in the original bcd store. The only reason you see it is that there is a menu displayed, in the original configuration the same entry is no displayed, but booted right away. If it bothers you and you know what you are doing, you can use bcdedit, BootIce, or VisualBCD and edit bcd stores in \boot and \efi\microsoft\boot.

 

http://msdn.microsoft.com/en-us/library/windows/hardware/ff542193(v=vs.85).aspx

You'd need to use the /store parameter as well and point to the target bcd store, for both BIOS and EFI stores.

Ok I'll leave it as is. This is the best multiboot!

I've tried a few prior like Yumi but wouldn't work with slipstreamed 7 and no multiple Windows. The only minor inconvenience is it seems you have to rebuild if you want to update a source like antivirus rescue cd? 
 

For such ISOs you could simply replace the ISO file with the new one in folder ISO and make sure it's not fragmented, say with the included WinContig in \files\tools\rmprepusb\wincontig.

Same applies for Windows Vista/7/8 sources, given that boot.wim is the same. No need to defragment here.

You may also need to edit menu.lst in root and correct the title and file names if they are changed.

Hi

 

This fantastic tool only came to my knowledge just few days ago.I should say that i am very impressed.  Keep up the good work mate   .

Ohh, come on mate, you are an agent, should know stuff

Hi

 

Pardon me if these questions are already asked and answered. I am a little lazy to walk-through the 84 pages  .

 

1. What is the exact purpose of files "default" and "windefault" at the root of USB ?. Why there is a warning "The file size is 2048 bytes. Don't change the file size !!!!!!!" on it ?. While i understands that "usbdrive.tag" is just a tag file used to find the root of USB, i failed to understand the purpose of "default" file.

 

2. Can i change the path of "DPMS" folder ?. If i move this folder to inside of "WINSETUP" folder and modify the path references in menu file to reflect the new path ( /DPMS to /WINSETUP/DPMS), is it will work ?.  

#1

Get a recent grub4dos (or even a non-recent one) and read it's Readme, or check here:

http://diddy.boot-land.net/grub4dos/files/menu.htm#default

 

The actual reason why the file has been chosen with a fixed size of 2048 bytes is that this way it is surely accessible by grub4dos on a NTFS filesystem.

Small files, full details here:

http://www.forensicfocus.com/Forums/viewtopic/t=10403/

are "embedded" in the $MFT entry on NTFS and grub4dos cannot see/access them.

 

 

#2

WHY?

Please provide a good reason for this change.

However the DPMS are taken (without modifications) from:

http://driverpacks.net/

so maybe you will have a better answer if you ask that question there:

http://forum.driverpacks.net/

 

jaclaz

Default files are used to auto move between the menus making default one the appropriate one.

I.e. afer first part of XP setup is completed/booted, make the second one default boot menu, thus allowing unattended setup. Default file is for the main menu, windefault is for the NT5 (xp, 2000,2003) boot menu. I wouldn't play with those file unless you have a good reason to do so.

DPMS.iso location can be changed, given that you ammend all file locations accordingly.

@Jaclaz

DPMS is Chennal's dpms.bat modified by Steve wrapped in an ISO file, only making use of driver pack mass storage, and I doubt their forum would be able to offer much help, unless it's a specific driver issue.

@Jaclaz

DPMS is Chennal's dpms.bat modified by Steve wrapped in an ISO file, only making use of driver pack mass storage, and I doubt their forum would be able to offer much help, unless it's a specific driver issue.

I know , the main point was, as someone else said

 

I wouldn't play with those file unless you have a good reason to do so.

particularly because the OP talked of a DPMS folder....and the readme.txt in it contains:

 

To update the driver pack, modify DPMS.ISO and replace "D" and all subfolders with the new ones.

Then rename to DriverPack_MassStorage_wnt5_x86-32.ini to DriverPack.ini and replace the existing one.

To obtain the latest BTS mass storage driver pack visit:

http://www.driverpacks.net/driverpacks/windows/xp/x86/mass-storage/

 

OT , the DPMS.ISO could be a very good target for the COSMIAS approach .

(which would allow easier "moving" it)

 

Reboot.pro is down  right now , but when it comes back it may interest you.

http://reboot.pro/topic/17807-release-cosmias-a-new-approach-to-g4d-images/

in the meantime (JFYI):

https://web.archive.org/web/20130507103634/http://reboot.pro/topic/17807-release-cosmias-a-new-approach-to-g4d-images/

 

jaclaz

Edited November 28, 201411 yr by jaclaz

I think OP asked about the DPMS folder on the USB disk root, which folder contains DPMS.iso. You are talking abou the DPMS folder inside the ISO.

I am aware of Cosmias, nice stuff!

Currently I am reading as before, just not writing much, as spare time is very limited.

 

#2

WHY? 

Please provide a good reason for this change.

 

I like to organize the folder structure of my USB boot drive. All XP stuff in one folder, 7 related stuff on another folder etc. Other than that, there is no real need to do that.

 

Thanks for the links - it will surely help me to understand Grub4DOS better.

 

@ilko_t

 

Thanks for the explanation. I can only assume about the amount of time you spent to polish this tool.  

New version 1.5 was released.

Updated to detect and support Windows 10 and Server 2012 and a few little bugs fixed when run on non-english locales.