Jump to content











- - - - -

USB Grub4dos install windows 8


  • Please log in to reply
32 replies to this topic

#26 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15540 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 14 October 2013 - 10:49 AM

##ISO file must be contiguous on disk in this case, use Sysinternals contig.exe

 OR Wincontig.exe (freeware AND redistributable) and with GUI (though it also has command line support) :):

http://wincontig.mdtzone.it/en/

 

:cheers:

Wonko



#27 xinyifly

xinyifly
  • Members
  • 2 posts
  •  
    China

Posted 14 October 2013 - 12:06 PM

The function of "WinVBlock" is to allow your booted Windows Installer to detect the RAM CD-ROM or RAM HardDisk.

So that you won't get a blue screen error when you booted Windows Installer from RAM CD-ROM

 

You should Download the Windows image yourself.

My Windows image is named like "*.iso"

Use Grub4Dos or Grub2 to load the "*.iso" into RAM and boot, then you can install your Windows normally.

 

Unfortunately, I met problems when I tried to load the "*.iso" to RAM 

although I known the correct steps and I have successfully booted another Windows PE.

Maybe the Windows image is too big...

Maybe WinVBlock can solve this problem or maybe not.

 

I am trying...



#28 Guest_ErikUSB_*

Guest_ErikUSB_*
  • Guests

Posted 14 October 2013 - 07:04 PM

What about: 

To map the disk image win98.ima on device (hd0,0) as a virtual floppy disk drive (fd0), then boot the virtual device -

title Boot Disk Image 
map (hd0,0)/win98.ima (fd0) 
map --hook 
chainloader (fd0)+1 
rootnoverify (fd0) 
map --floppies=1

cant we make iso into a ima ?



#29 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15540 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 14 October 2013 - 07:34 PM

What about: 



To map the disk image win98.ima on device (hd0,0) as a virtual floppy disk drive (fd0), then boot the virtual device -

title Boot Disk Image 
map (hd0,0)/win98.ima (fd0) 
map --hook 
chainloader (fd0)+1 
rootnoverify (fd0) 
map --floppies=1

cant we make iso into a ima ?

No. :frusty:

 

A floppy image is completely different from a .iso image (FAT 12, 512 bytes sectors vs. CDFS, 2048 bytes sectors) but you are still completely failing to grasp a basic concept :ph34r:.

 

DOS and Win9x/Me (and grub4dos) boot in "real mode" and NOT in "protected mode", and additionally, once booted they "trust" the info form the BIOS (which is modified by grub4dos).

Any Windows NT system starts to boot in "real mode" (NTLDR+NTDETECT.COM+BOOT.INI or BOOTMGR+\boot\BCD) but soon after the very initial start of booting  they "switch" to "protected mode".

Anything that is present in "real mode" (i.e. anything grub4dos can do like mapping images) is LOST when the switch happens UNLESS a driver "hooks" this mapping.

 

A Windows 7/8 "install disk" is slightly different because it has built-in (what actually boots is a minimal PE) support for "itself" (i.e. the boot.wim file) but since later the PE needs to access the "outer" container (i.e. the mapped .iso file) there is nonetheless the need for a driver that mounts the .iso inside the running PE.

 

I hope that the above helps clearing the point without getting too technical.

Check also:

http://reboot.pro/to...all-iso-images/

http://reboot.pro/to...about-grub4dos/

AND, please, RE-READ the already linked to thread:

http://reboot.pro/to...required-cddvd/

 

:cheers:
Wonko


  • xinyifly likes this

#30 Guest_ErikUSB_*

Guest_ErikUSB_*
  • Guests

Posted 14 October 2013 - 10:36 PM

indeed i get it now.

i think  :loleverybody:

 

 

i have chosen to

extract whole ISO to USB drive

title Win8 Setup
chainloader /bootmgr

and then i have removed these files from the extracted iso file:

/autorun.inf
/bootmgr.efi
/setup.exe
the whole efi folder
and the whole support folder

now, the only files i have left are:

the boot folder
and the sources folder
/bootmgr

and the install was a succes. :1st:

 

do you think that this will work on every computer or laptop, if all these folders and files are removed?

do i need those files, will i get a error from windows in the future, becoase some files are missing/could not be installed because of this?



#31 cdob

cdob

    Gold Member

  • Expert
  • 1463 posts

Posted 15 October 2013 - 04:10 AM

do you think that this will work on every computer or laptop


What about a machine with UEFI?
Does any machine offers BIOS compatible mode in future?

#32 Guest_ErikUSB_*

Guest_ErikUSB_*
  • Guests

Posted 15 October 2013 - 07:30 AM

my laptop uses uefi, but i have disabled it in order to boot with grub4dos.



#33 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15540 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 15 October 2013 - 08:37 AM

do you think that this will work on every computer or laptop, if all these folders and files are removed?

do i need those files, will i get a error from windows in the future, becoase some files are missing/could not be installed because of this?

On BIOS (or UEFI set to BIOS compatible mode) no, as cdob hinted "pure" UEFI boards  won't (obviously) work.

Stiil the approach f a "flat" install is simple and effective :) BUT "below" current standards, the other suggested approach of having a "monolithic" .iso is far more convenient iMHO.

 

:cheers:

Wonko






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users