226 replies to this topic

[steve6375]

I can add .vhd but I have not tested vhd from grub4dos

So you have a typical menu for grub4dos vhd booting?

[alacran]

Attached the menu I use for VHD booting, all VHD's do have bootmanager or boot.ini installed to avoid any problem when booting, as you may know Win8 can't be booted from Grub4Dos calling the \Windows\system32\winload.exe (bootmanager way when booting VHD's), so to be consistent I use same way for all.

 

Spoiler

#VHD located on Isos file
title Load XP-SP3 from VHD XP-SP3.vhd
find --set-root --ignore-floppies /Isos/XP-SP3.vhd
map /Isos/XP-SP3.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr

#VHD located on any partition root
title Load Windows 7 from VHD - Win7.vhd
find --set-root --ignore-floppies /Win7.vhd
map /Win7.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr

#VHD located on any partition root
title Load ThinPC from VHD - ThinPC.vhd
find --set-root --ignore-floppies /ThinPC.vhd
map /ThinPC.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr

#VHD located on any partition root
title Load Windows 8 from VHD - Win8.vhd
find --set-root --ignore-floppies /Win8.vhd
map /Win8.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr

 

All VHD's are active volumes NTFS formated with their corresponding 5.2 or 6.x MBR and boot code on partition

 

Best Regards

Edited by alacran, 08 May 2013 - 10:50 PM.

[steve6375]

Thanks! So this added to the \_ISO\E2B\grub\QRUN.g4b batch file should work...

:.vhd
map %1 (hd0)
map --hook
root (hd0,0) || rootnoverify (hd0,0)
chainloader /bootmgr || chainloader /ntldr || chainloader +1 || chainloader (hd0)+1
exit

Now in BETA27v2

[alacran]

Good I will test it and report back

[alacran]

It's working just perfect, I tested booting my XP-SP3.vhd on a USB 2.0 stick exFAT formated, a little slow as expected from USB 2.0 stick but it was just to test, on HDD it is going to boot faster.

[gbrao]

So it's possible to boot a Windows XP/7/8 VHD from grub4dos ?

[Wonko the Sane]

... as you may know Win8 can't be booted from Grub4Dos calling the \Windows\system32\winload.exe (bootmanager way when booting VHD's), so to be consistent I use same way for all.

Care to explain?
I am only familiar (with *any* Vista or later OS) with chainloading BOOTMGR.
Can you provide the "alternate" way with Grub4dos "calling" \Windows\system32\winload.exe that you use (or used) for Vista or later BUT pre-windows8 OS?


Wonko

[alacran]

@ Wonko

 

What I wanted to say is: AFAIK Win8 can be booted only from Windows loader. So even if could be alternative ways for Grub4Dos booting other NT6 systems, perhaps calling \Windows\system32\winload.exe as Windows loader does, it’s better to be consistent and use the proposed one, which is good for all NT6 systems.

 

I admit my message was confuse, I was writing during thinking, and I didn’t realize that it wasn’t clear.

 

So in short answer I don't know other way to boot NT6 systems from Grub4Dos.

Edited by alacran, 09 May 2013 - 09:05 PM.

[Wonko the Sane]

@ Wonko

 

What I wanted to say is: AFAIK Win8 can be booted only from Windows loader. So even if could be alternative ways for Grub4Dos booting other NT6 systems, perhaps calling \Windows\system32\winload.exe as Windows loader does, it’s better to be consistent and use the proposed one, which is good for all NT6 systems.

 

I admit my message was confuse, I was writing during thinking, and I didn’t realize that it wasn’t clear.

 

So in short answer I don't know other way to boot NT6 systems from Grub4Dos.

Yep, I suspected something like that (I am trying to avoid confusion).

 

There is not *any* other method (if not chainloading BOOTMGR or a bootsector invoking BOOTMGR) to boot any NT6 or later system from grub4dos.

 

Wonko

[alacran]

So it's possible to boot a Windows XP/7/8 VHD from grub4dos ?

 

Yes, but there are certain requirement you must comply, not all VHD’s can be booted from G4D.  If you are not familiar with XP or Win7 VHD creation, and preparation for later booting from Grub4Dos, you may use this tool from Wimb, but first read carefully all info on the first Post of that page.: http://reboot.pro/in...?showtopic=9830

 

Regards

Edited by alacran, 10 May 2013 - 05:08 AM.

[gbrao]

I have created a few vhds using the wimb IMG_XP tools. I always thought it was not possible to boot Win 7/8 vhd's from grub4dos.

See for eg : http://reboot.pro/to...-8/#entry171553

Or the guide from : http://reboot.pro/to...7-from-ramdisk/

 

Unless you mean a Win 7/8 vhd that does not have winvblock or firadisk installed.

 

I have booted Win XP VHDs from g4d with winvblock installed.

[wimb]

Portable Win7 VHD can be booted from Grub4dos Menu as FILEDISK or as RAMDISK 

when WinVBlock or FiraDisk driver have been installed in Source (x64 architecture requires FiraDisk).

http://reboot.pro/to...-16#entry128716

http://reboot.pro/to...-22#entry150248

http://reboot.pro/to...-22#entry149420

 

Win8 VHD can be booted from RAMDISK with Grub4dos Menu

http://reboot.pro/to...-8/#entry171552

[gbrao]

Oh, the vhds i created would only boot from memory from g4d menu.

For 'filedisk' I would boot the vhds from windows bootmgr.

Please confirm : the same W7/W8 vhd can be booted as RAMDISK or FILEDISK from a g4d menu ?

Edit : Does the Win 7/8 edition (Ultimate/Pro ...) used to make the vhd matter ?

[steve6375]

New BETA28 available - WIndows ISOs menu greatly changed!

[DarkPhoeniX]

Today i installed Windows Xp pro SP3

The OS seems to work fine except for some abnormality's

 

the following image shows WinVBlock as a unknown device

http://i43.tinypic.com/357opxd.jpg

The following image shows that windows is installed to the "H:\" drive

http://i43.tinypic.com/2yybgd4.jpg

 

and there is no option (on initialization) to input a user name(this can still be done via Users in control panel)

 

Is this normal?

 

If so will it cuse a problem if i Remove the winvblock driver(delete),after installation ?

And change the Main drive to C:\?

via a script run at post?

 

I will still have to test other OS's when i have my 64gb Flash drive 

[Wonko the Sane]

Oh, the vhds i created would only boot from memory from g4d menu.
For 'filedisk' I would boot the vhds from windows bootmgr.
Please confirm : the same W7/W8 vhd can be booted as RAMDISK or FILEDISK from a g4d menu ?
Edit : Does the Win 7/8 edition (Ultimate/Pro ...) used to make the vhd matter ?

gbrao,
you are mixing methods.

A .vhd, NO MATTER if "as filedisk" or "ramdisk" NEEDS to be mapped through grub4dos if you use the Winvblock or Firadisk drivers (both these drivers "hook" the grub4dos mapping).

Some "high end" editions of Windows 7 (and possibly of 8) have a built-in a DIFFERENT way to "natively" boot from .VHD, that need no grub4dos, nor firadisk, nor winvbloick.

It is not like this info is kept secret :
http://reboot.pro/to...tive-boot-vhds/
http://reboot.pro/to...-vhds/?p=138494


Wonko

[steve6375]

Today i installed Windows Xp pro SP3

The OS seems to work fine except for some abnormality's

 

the following image shows WinVBlock as a unknown device

http://i43.tinypic.com/357opxd.jpg

The following image shows that windows is installed to the "H:\" drive

http://i43.tinypic.com/2yybgd4.jpg

 

and there is no option (on initialization) to input a user name(this can still be done via Users in control panel)

 

Is this normal?

 

If so will it cuse a problem if i Remove the winvblock driver(delete),after installation ?

And change the Main drive to C:\?

via a script run at post?

 

I will still have to test other OS's when i have my 64gb Flash drive 

It is normal and expected.

No - you can just remove the drivers. It is a nuisance - you could try just adding the Firadisk drivers with F6 and see if it works - some systems it will and some will not - which is why I recommend both.

or use the WinPE method of install instead (but the ISO must contain the drivers).

 

Please update to latest BETA28V4 - major bug in v3 and previous - I did not update the Autounattend on the Easy2Boot drive for Vista+ installs!

[steve6375]

To all testers...

Please refresh to BETA28v4 to fix a bug with all installs of Vista and later OS's (Autounattend.xml was not written to Easy2Boot root!).

 

There are still a few things I am working on for Easy2Boot.

1. Keep the Main Menu in memory, so reloading the mainmenu can be done instantly rather than having to count all files again.

2. Change the Vista and later OS menus so that grub4dos lists the files in a menu rather than a console window. This would also mean that you could use a .txt file to specify a title for each ISO, rather than just use it's filename in the menu.

 

Maybe by the time it gets to BETA30 I can release it!  

[gbrao]

continued here : http://reboot.pro/to...-39#entry172280

gbrao,
you are mixing methods.

...

[llbranco]

is possible to make a Full Hibrid USB (install and live) with Linux an Windows and Mac?

is possible to make a Hibrid Legacy and (u)EFI Windows, Linux, Mac (Hackintosh and REAL MAC) bootable?

 

i found it:
http://www.insanelym...h-macosx-distr/

 

- Make Clover&Chameleon bootable USB Flash Disk for MAC OS X fast and easy under OS Windows. -

 

and it works fine on:
REAL MAC

LEGACY BIOS PC

Both EFI and uEFI PC

 

 

 

 

the question is simple:

 

how to mix Easy2boot with BDUTILITY to make a Hibrid BIOS/EFI and Windows/Linux/Mac bootable USB Device?

( or i'm crazy justo to think 'bout it? )

its possible Steve ?

 

( some EFI utilities can be "booted" on Fat32 even it has Grub(4dos, legacy or 2) installed... )

[llbranco]

as i promised ( i said the truth )

 

Bootmgr Missing:
is REALLY REAL!!!

( this NOTEBOOK isn't MINE )

Edited by llbranco, 22 May 2013 - 04:48 PM.

[llbranco]

FreeNAS LiveCD doesn't work (without any parameter) (x86/x64)

http://www.freenas.o...d-releases.html

 

NAS4FREE LiveCD works Fine (without any parameter)  (x86/x64)

http://sourceforge.n...nas4free/files/

 

OpenMediaVault LiveCD Crashs on Boot (loading ISOLINUX)

http://www.openmedia...g/download.html

[n1ghtnite]

Hello,

 

ich just bought a 128GB USB-Stick.

I already started the Stick w/ e2b on a pc but on my main-machine it says:

"... SOME FILES MAY BE UNACCESSIBLE, PLEASE CHECK YOUR BIOS" in red, when booting from the stick.

 

Now i tried to Run WinContig from PrepUSB to make all files contigous.

It finds fragmented files, but it says, it doesnt have enough free contigous block on the device, but i have 80GB free space on the Stick, which should be enough i guess.

Is there any other way to make my stick contigous?

or do i have to update my BIOS on the machine?

[steve6375]

Does it give that message when booting from QEMU or VBox? Are you usinh E2B v1.1

 

re. WinContig, not come across that issue - it won't be a BIOS problem. Did you format it as NTFS or FAT32, what size are the files you are trying to make contiguous?

[n1ghtnite]

Does it give that message when booting from QEMU or VBox? Are you usinh E2B v1.1

 

re. WinContig, not come across that issue - it won't be a BIOS problem. Did you format it as NTFS or FAT32, what size are the files you are trying to make contiguous?

 

No it doesnt give the messaage mit qemu.

The e2b.cfg says: set VER=v1.02

The Stick is NTFS-formatted, 1 big partition.

Heres a log of Auslogic Disk Defrag, so you can see the Files:

How do i upload a files to the forum?

Heres a uploaded.to-link anyways: http://ul.to/hq84nsl5