Jump to content











Photo
* * * * * 5 votes

Easy2Boot Development Discussion

grub4dos multiboot multipass usb boot iso

  • Please log in to reply
1338 replies to this topic

#651 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 22 June 2014 - 05:08 PM

@steve: thx for the hint ... 

 

I do not have any x24 modes listed on the machines I can test here, but eg 800x600x16 and 800x600x32, so I will give it a try to set the gmode to 800 600 32 (or 16)



#652 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 22 June 2014 - 05:12 PM

x32 should work the same as x24.

Have you a 'bad' system???  There is not much point on running vbeprobe on a good system - we know it works.



#653 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 477 posts
  •  
    India

Posted 22 June 2014 - 05:17 PM

I have not tested it, but in theory yes, but I think you must UEFI boot to prepare the WinToGo image because you need to run bcdboot under a UEFI-booted environment to make it place the EFI folder and BCD folders and files on the WinToGo volume.

 

Can I UEFI boot to 'Win8.1U1_x64_boot.wim' in order to prepare the WinToGo image so that I can run bcdboot under a UEFI-booted environment to make it place the EFI folder and BCD folders and files on the WinToGo volume ?

 

 

Thanks..............



#654 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 22 June 2014 - 05:19 PM

Yes, I think so. use the /f all switch for bcdboot to put both MBR and EFI BCDs and boot files on.



#655 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 22 June 2014 - 05:28 PM

P.S. Is it possible the 'bad' system is booting from the USB Helper drive? What if you don't connect it, but just connect the E2B HDD drive? Is there an old version of grldr on the Helper drive???



#656 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 22 June 2014 - 07:49 PM

ok, think I had a wrong start (change of version of e2b)

 

but I think there is a problem in the color pattern

 

description of MyE2B.cfg:


# Colour pairs are Text/Background

in my cfg it is the other way round, Background/Text

 


###color normal=black/white

or


### color normal=0x777700

does not work for me, I have to write it that way (for black text on white background):

color normal=0x%white%%%black%



#657 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 22 June 2014 - 08:15 PM

When using graphics mode (hi-colour resolutions), the background colour is ignored except for standard (console text) and highlight.

 

e.g. color standard=white/black    will give white text on a black background on the grub4dos console

       color normal=white/black       will give white text on top of the bitmap (i.e. transparent background)

 

color normal=0x%white%%%black%  translates to   color normal=0x0F  white text on black background (or transparent background if using graphics mode)

 

color normal=0x777700  makes the menu text a sort of dark yellow colour  (red=77hex green=77hex blue=00hex)

 

For black text, you would need to specify a value over 0xFF hex, so you can use a very weak colour value for green or red to make it over 0xff - e,g,  

 

color normal=0x000100   - or  0x010000

 

or even 

 

color normal=black/black  (which is same as black/red  or black/green etc as the background colour is transparent)

 

 

(you are removing the ###  comment markers???)



#658 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 22 June 2014 - 08:27 PM

color normal=0x%white%%%black% translates to color normal=0x0F white text on black background (or transparent background if using graphics mode)


nope, as I mentioned above
and yes I could also use black in the first place for transparent background
the entry gives me black text on white background (or transparent if I use black as color)

as another example of me MyE2B.cfg:
highlight=0x%red%%%yellow%
gives me yellow text on red background in case of a highlight

and as mentioned before: I cannot use for example highlight=red/yellow , that does not work, I have to use highlight=0x%red%%%yellow%


(you are removing the ### comment markers???)


I have only 1 syntax active, all other are commented out



#659 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 22 June 2014 - 08:44 PM

sorry - my bad

color normal=0x%white%%%black% translates to color normal=0x0F white text on black background (or transparent background if using graphics mode)


I should have said

color normal=0x%white%%%black% translates to color normal=0xF0 black text on white background (or transparent background if using graphics mode)
 


If using colour pairs e.g. black/white then 1st = text and 2nd = background

if using 0x%AAA%%%BBB% then AAA is background and BBB is text colour.


The description in SampleMyE2B.cfg shows pairs like black/white it does not mention the 0x%AAA%%%BBB% format (in that section of the file)


I actually removed the descriptions about using the 0x%AAA%%%BBB% format because we can now use the black/white type of parameters in the newer grub4dos.

So using 0x%AAA%%%BBB% is deprecated and should not be used. I should have removed the example line near the top of the file as well.



#660 patsch

patsch

    Silver Member

  • Advanced user
  • 785 posts
  •  
    Germany

Posted 22 June 2014 - 08:54 PM

I use rmprepusb 2.1.722, Easy2Boot 1.41 ... and I also tried latest chenall from here: https://code.google..../downloads/list

 

but only 0x%AAA%%%BBB% is working for me, not the color pairs like black/white



#661 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 22 June 2014 - 08:57 PM

Try in console.

 

In grub4dos menu, press p  then enter password then c

 

then type

 

color normal=black/white

 

then press ESC key to get back to the menu

 

I get black text for menu entries



#662 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 22 June 2014 - 09:00 PM

To use the console with keyboard you need to change the MyE2B.cfg to load the german keyboard patch file P.S. What is the grub4dos version at the top of the console window???



#663 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 477 posts
  •  
    India

Posted 23 June 2014 - 05:24 AM

I have not tested it, but in theory yes, but I think you must UEFI boot to prepare the WinToGo image because you need to run bcdboot under a UEFI-booted environment to make it place the EFI folder and BCD folders and files on the WinToGo volume.




Yes, I think so. use the /f all switch for bcdboot to put both MBR and EFI BCDs and boot files on.


Hi 'Steve'......

Greeting of the Day............

GOAL- Create 'Win 8.1 to GO' using Partition images (.imgPTNLBAa) so that it boot in both BIOS and UEFI machines through 'Easy2Boot ?

According to Steve " If you want to enable UEFI booting as well as MBR booting, you will need to reformat the USB disk with a GPT partition structure and use the 64-bit version of Windows 8 as the ISO source."


Comment from William (USA) who tried the above EFI install: 'I managed to get windows to boot using MBR with an EFI partition using the method you listed and adding the boot files to the main windows partition (marked as active) as well as the ALL command on the EFI to create a bootable flash drive for both BIOS and UEFI machines. '

----------------------------------------------------------------------------------------

create partition EFI size=100 offset=1024
format quick fs=fat32 label=EFI
assign letter=S
set id="C12A7328-F81F-11D2-BA4B-00A0C93EC93B"

create partition MSR size=128

create partition primary size=15360
format quick fs=ntfs label=System
assign letter=U
set id="EBD0A0A2-B9E5-4433-87C0-68B6B72699C7"
------------------------------------------------------------------------------------------


Hello 'Steve' - Is it possible to create more Partition Image formats so that we can also adjust MSR Partition in USB Drive if required ?

Will following Partition Image Pattern be work ? If not then what should we have to do ?

------------------------------------------------------------------------------------------------------------------------------
Win81toGO.imgEFILBAa23 -> 100MB -> S: EFI Partition -> BCDBOOT U:\Windows /s S: /f ALL /v
Win81toGO.imgMSR            -> 128MB ->
Win81toGO                            -> 15GB   -> U: Data Partition -> Imagex /Apply K:\Sources\Install.wim 1 U: /norpfix
------------------------------------------------------------------------------------------------------------------------------

1- Once partitioned, We can install Windows files using ImageX to the Data Partition. .


Imagex /Apply K:\Sources\Install.wim 1 U: /norpfix

2- When the image has been successfully applied to the Data Partition, and then run the BCDBoot command on the 100MB EFI Partition.

BCDBOOT U:\Windows /s S: /f ALL /v

(where S: is the EFI partition and U is the OS partition)


Actually I could not properly understand how and what Steps I have to follow in order to fulfill desired Goal. So please provide us a Step by Step Tutorial for doing the same if possible.............

Thanks in Advance.......................

:cheers:

Edited by devdevadev, 23 June 2014 - 05:41 AM.


#664 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 23 June 2014 - 08:14 AM

I am not sure that you must have GPT in order to UEFI boot - it should be possible with just FAT32 since you can UEFI boot from FAT32 from \efi\boot files??  :confused1:



#665 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 477 posts
  •  
    India

Posted 23 June 2014 - 08:24 AM

You mean addition of \efi\boot files into 'WintoGO.imgPTNLBAa' is sufficient in order to UEFI boot of 'Win to GO'?

Can I boot 'VHD' AND 'WIM' files form 'E2B' ?

Thanks

Edited by devdevadev, 23 June 2014 - 08:25 AM.


#666 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 23 June 2014 - 08:26 AM

You would need to run bcdboot /f all to make the bcd correct.

 

grub4dos can boot from a fixed vhd as long as the vhd loads windows into RAM from boot.wim  (i.e. not a Wintogo vhd).

 

grub4dos cannot boot from wim files.



#667 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 477 posts
  •  
    India

Posted 23 June 2014 - 08:32 AM

You mean 'Win8.1U1_x64.vhd' is a 'WintoGO.vhd' (i.e. not a fixed vhd) ?


Thanks

Edited by devdevadev, 23 June 2014 - 08:33 AM.


#668 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 477 posts
  •  
    India

Posted 23 June 2014 - 08:54 AM

AFAIU,

'grldr' can only boot 'Win8.1U1_x64.iso' while I have to use Boot Manager in order to boot 'Win8.1U1_x64.vhd' and 'Win8.1U1_x64_boot.wim' ?

Am I right ? or not ?


'Win8.1_x64.vhd' size = 3.5 GB

'Win8.1toGO.vhd' size = 15 GB

Then what is the difference between 'Win8.1_x64.vhd' and 'Win8.1toGO.vhd' ?

Thanks

Edited by devdevadev, 23 June 2014 - 08:57 AM.


#669 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 477 posts
  •  
    India

Posted 23 June 2014 - 10:59 AM

Hi 'Steve'.......

 

Can you please add a 'Boot Manager' entry in 'Easy2Boot Menu' so that we can boot 'VHD' and 'WIM' with
the help of 'Boot Manager Menu' ?

 

1- BIOS-
" We will use BCD edit function inside bootice to edit S:\Boot\BCD for creating boot entries for my 'Win8.1U1SE_x64_boot.wim' and 'Win8.1U1SE_x64.vhd' in BIOS mode (winload.exe to be put as loader). "

2-UEFI-
" We will use BCD edit function inside bootice to edit S:\efi\Microsoft\Boot\BCD for creating boot entries for my 'Win8.1U1SE_x64_boot.wim' and 'Win8.1U1SE_x64.vhd' in UEFI mode (winload.efi to be put as loader). "

 

 

Thanks



#670 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 23 June 2014 - 11:01 AM

Boot Windows direct from USB.mnu  is present in the \_ISO\docs\Sample menu files - just copy it to \_ISO\MAINMENU or wherever you want it.



#671 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 477 posts
  •  
    India

Posted 23 June 2014 - 11:15 AM

Thanks a lot 'Steve'..............

 

Can you please provide some information regarding 'MBR BootCode' boot sequence ?

 

http://reboot.pro/to...iew=getlastpost

 

:cheers: 



#672 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 23 June 2014 - 12:32 PM

I am not sure that you must have GPT in order to UEFI boot - it should be possible with just FAT32 since you can UEFI boot from FAT32 from \efi\boot files?? :confused1:

Using Dism to apply a Win 8.1 64-bit install.wim to a FAT32 USB drive fails...

[4396] [0x80070001] EnableShortnamesOnApplyTarget:(801): Incorrect function.
[4396] [0x80070001] WIMSetFileShortName:(891): Incorrect function.
[4396] [0x80070052] WimCreateDirectory:(4590): The directory or file cannot be created.
[4396] [0xc144012e]
2014-06-23 14:22:56, Error DISM DISM WIM Provider: PID=4396 e:\Windows\WinSxS\msil_microsoft.virtualization.client.common_31bf3856ad364e35_6.3.9600.16384_none_72d188163865428b (HRESULT=0x80070052) - CWimManager::WimProviderMsgLogCallback
[4396] [0x80070052] RestoreDirTree:(4885): The directory or file cannot be created.
[4396] [0x80070052] WIMApplyImageInternal:(1189): The directory or file cannot be created.

Error: 82

 


So it seems it needs to be NTFS and therefore we need GPT and multiple partitions for UEFI booting. E2B has no mechanism for GPT partitions so we cant UEFI boot from a partition image using E2B :-(



#673 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 23 June 2014 - 12:51 PM

steve6375, on 23 Jun 2014 - 2:32 PM, said:
Using Dism to apply a Win 8.1 64-bit install.wim to a FAT32 USB drive fails...

I am failing to see why you would want to apply an install.wim to a FAT32 volume :unsure:, however the issue is "common" with Vista :ph34r: and 7 and it is connected to the stupid WINSXS directory and the stupid length of the stupid names of the stupid files in it.
Is it clear how I find the whole WinSXS stuff stupid? :dubbio:

It seems like a part of the files can be removed, however, see:
http://reboot.pro/to...rdlinked-files/
I have no idea how (and if) this could/will apply to Windows 8 and to 64 bit.

:duff:
Wonko

#674 steve6375

steve6375

    Platinum Member

  • Developer
  • 7071 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 23 June 2014 - 12:59 PM

For Info: The object was to UEFI boot WindowsToGo from  a USB removable drive (and therefore a single FAT32 partition).

 

This is the reason why MS insisted that 'Certified' USB Flash drives are of the 'Fixed-disk' type - you can't UEFI boot WinToGo from a Removable-type Flash drive!



#675 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 23 June 2014 - 01:58 PM

steve6375, on 23 Jun 2014 - 2:59 PM, said:
For Info: The object was to UEFI boot WindowsToGo from a USB removable drive (and therefore a single FAT32 partition).

I see. :)

steve6375, on 23 Jun 2014 - 2:59 PM, said:
This is the reason why MS insisted that 'Certified' USB Flash drives are of the 'Fixed-disk' type - you can't UEFI boot WinToGo from a Removable-type Flash drive!

Though there may be also other very good reasons to flip the bit on those ;), independently from Windows8togo.

:duff:
Wonko





Also tagged with one or more of these keywords: grub4dos, multiboot, multipass, usb boot, iso

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users