14 replies to this topic

[LopoTRI]

On my usb i tried the iso of windows 7. i named it Win7.iso in the folder /isos. Then i edit the menu.lst

title Windows 7
find --set-root /isos/Win7.iso
map /isos/Win7.iso (hd32) ----> or (0xff)
map --hook
chainloader (hd32) ----> or (0xff)
boot

or this

title Windows 7
map (hd0,0)/isos/win7.iso (hd32)
map --hook
chainloader (hd32)

when i select it in grub4dos it comes "press any key to start from cd/dvd"
when i press a key the message comes again.
When i press a key again it hangs and do nothing
When i dont press any key it goes back to my main menue.
Some help???

I have got to say that i make my usb to boot first the ntldr for the xp-text-setup.
When i boot to usb my menue is:

1. Text-setup Win XP (never unplug the usb until you see the desktop)
2. Continue Text-setup Win XP (never unplug the usb until you see the desktop)
3. Attended Install Win XP ......
4. Grub4Dos

in Grub4Dos i have some isos and images, they work perfect.

Knows anybody why the Win7.iso makes me angry??

[steve6375]

http://www.boot-land...?showtopic=7916

does this help?

title 1 FIXED DISK EMULATION
find --set-root /winpe.iso
map /winpe.iso (hd32)
map --hook
chainloader /BOOTMGR

title 2 FLOPPY EMULATION - RAMDISK
find --set-root /winpe.iso
map --mem /winpe.iso (fd0)
map --hook
chainloader (fd0)/BOOTMGR
rootnoverify (fd0)

title 3 FLOPPY EMULATION - No ramdisk
find --set-root /winpe.iso
map /winpe.iso (fd0)
map --hook
chainloader (fd0)/BOOTMGR
rootnoverify (fd0)

[LopoTRI]

no.
And i dont mean the winpe. i mean the win7 installer iso.
I have formated my stick and install it again. Now its booting.....

Can anybody tell me how i can manage grub4dos to load the imdisk-fix (setupimdisk.cmd + setupcdrom.cmd) and then autostart the win7-install.iso???

[Wonko the Sane]

@LopoTRI

It doesn't work like this , you should be more explicit, describing accurately what you are trying to do (and unfortunately failing to) if you want to get help in a productive way.

You failed to describe how the thingy was originally partitioned/formatted and then to describe HOW you re-partitioned/re-formatted it:

I have formated my stick and install it again. Now its booting.....

This way, noone knows what was the cause, noone knows what was the fix.

Maybe you solved your problem, but this thread has no prectical use for anyone else.

This:

Can anybody tell me how i can manage grub4dos to load the imdisk-fix (setupimdisk.cmd + setupcdrom.cmd) and then autostart the win7-install.iso???

Of course allows for a simple answer:
YES.
http://homepages.tes...no-answers.html

Now, you evidently read somewhere about "the imdisk-fix (setupimdisk.cmd + setupcdrom.cmd)", why don't you post a link to where you read about it?

Take a few minutes and try describing the environment where you want to use it, like the USB stick, a .iso, etc., etc., this way once someone will hopefully help you in finding the solution to your current problme, the thread will be useful to other people that may have your same problem.



Wonko

[LopoTRI]

sorry, but on my first topic i wrote this....

I have got to say that i make my usb to boot first the ntldr for the xp-text-setup.
When i boot to usb my menue is:

1. Text-setup Win XP (never unplug the usb until you see the desktop)
2. Continue Text-setup Win XP (never unplug the usb until you see the desktop)
3. Attended Install Win XP ......
4. Grub4Dos

Also i had format my usb in ntfs (with paragon v10 in my XP-system)
Then i make it bootable with bootsect /nt52 X: (with my windows 7-system)
I installed Windows XP-setup-cd with USB_MultiBoot_10 (with my XP-system)
I copied the grldr + menu.lst on the root of my usb and manage the boot.ini with the entry for grub4dos (c:\grldr="4. Start GRUB4DOS Menu - DOS FPY IMAGES + Linux + XP Rec Cons + Vista")
I copied the win7-installer-cd to /isos/win7.iso and make a entry in menu.lst

title Windows 7
find --set-root /isos/Win7.iso
map /isos/Win7.iso (hd32) ----> or (0xff)
map --hook
chainloader (hd32) ----> or (0xff)
boot

or this

title Windows 7
map (hd0,0)/isos/win7.iso (hd32)
map --hook
chainloader (hd32)

The problem when i maped the win7-install.iso was.....

when i select it in grub4dos it comes "press any key to start from cd/dvd"
when i press a key the message comes again.
When i press a key again it hangs and do nothing
When i dont press any key it goes back to my main menue.
Some help???

Also i low-level-formated my usb with LLFsetup.2.36.1181, cause i have tried too many times with too many bootloaders, make a new partition in ntfs with paragon v10 and install grubload with "grubinst-1.1-bin-w32-2008-01-01"
Then i copied the win7.iso to my usb and make an entry in menu.lst

find --set-root /isos/Win7.iso
map /isos/Win7.iso (hd32)
map --hook
chainloader (hd32)
boot

And now my problem with "press any key to boot...." is gone. It boots the windows 7 installer with the other problem "(missing cd/dvd-rom driver)".

I found on this forum links for the imdisk (but now i cant find it again ) but i have a link in translated version, cause its from a chinese site.....
http://translate.goo...history_state0=

So my question was can anybody help me, i want to manage this imdisk-fix to boot automaticly when i select the windows7 installation from my grub4dos?

[Icecube]

@ Wonko

Now, you evidently read somewhere about "the imdisk-fix (setupimdisk.cmd + setupcdrom.cmd)", why don't you post a link to where you read about it?

If its not too late, i found a topic in chinese site how you can fix this problem with CD/DVD drivers with ImDisk....

Here is the Link in translated version. Go to step 4.
http://translate.goo...history_state0=

Windows 7 installation problem (missing cd/dvd-rom driver): http://www.boot-land...art=#entry91631

[Wonko the Sane]

sorry, but on my first topic i wrote this....

Yes, and that doesn't describe much of what I listed as missing details.

Not a problem, but maybe a short check of the "common sense advice" attached to Rules, might be of use:
http://www.boot-land...?showtopic=9101
expecially points #f.

Basically it is you that are having a problems, and you can contribute to:

• be helped faster/better
• let the topic you started (and hopefully the solutions found) to be helpful for other members

Rather obviously, you have no obligation to try and fulfill #2 above, you are perfectly free to post unreferenced items, but in doing so you will probably fail in #1 too, which from your subjective view point may not be the smartest thing to do.

On the other hand, I was willing to try and help you, but freedom is double face, and entitles me to declare your problem an S.E.P.:
http://en.wikipedia.org/wiki/Somebody_Else's_Problem
and as thus I cannot see it anymore.

Good luck for your problem, whatever it is.



Wonko

[Obelisk]

Mine is a quite similar problem to LopoTRI. Though the error is different.
Here 's my stuff:

+ USB 4 GB Transcend. Folder tree is:
1. grldr
2. menu.lst
3. Win7_pro.iso
4. OS (folder)
4.1. Ubuntu (folder)
4.1.1. Ubuntu_11_10.iso
4.2. Windows (folder)

The Live-Ubuntu iso was booted perfectly so I won't talk about it.
The problem is booting Win7_pro.iso. I created it by PowerISO, just by adding all files from the installation DVD (included bootmgr, setup.exe and some folders) then save it as Win7_pro.iso. In my menu.lst I've try these "tricks":

title Windows 7 (iso) - 1

find --set-root /Win7_pro.iso

map (hd0,0)/Win7_pro.iso (0xff)

map --hook

root (0xff)

chainloader (0xff)



title Windows 7 (iso) - 2

find --set-root /Win7_pro.iso

map (hd0,0)/Win7_pro.iso (0xff)

map --hook

root (0xff)

chainloader /bootmgr



title Windows 7 (iso) - 3

find --set-root /Win7_pro.iso

map (hd0,0)/Win7_pro.iso (0xff)

map --hook

root (0xff)

chainloader (0xff) /bootmgr

But all of them seem to be stucked by this error (occured after I enter each title in booting time):

  (hd0,0)

map (hd0,0)/Win7_pro.iso (0xff)



Error 60: File for drive emulation must be in one contiguous disk area



Press any key to continue...

I thought it was an error raised by grub4dos but don't know how to solve it ?
Is there a way to organize the disk space, helping the boot loader know which of its OS-part is being in which disk-part ?

Edited by Obelisk, 25 March 2012 - 07:41 PM.

[steve6375]

Run WinContig on the iso file on the USB drive (or use latest RMPrepUSB Ctrl+F2)

[Obelisk]

I mean... I don't want to mess up with many software-supports solution.
Actually a solution of mine now is copy all those win-7-stuffs to the root of the USB, then have grldr boot the bootmgr from (hd0,0). That way've worked perfectly...
I just care about organizing my files in the future, and for my sake, each time I want to install/re-install an OS I can simply:

1. Copy the .iso to a well-organized folder in my USB.
2. Edit menu.lst to deal with the new-come .iso.

And done.

Thank you steve6375... but can you explain more about the error, and the usage of that RMPrepUSB ?
And... if any of you have a non-software-related solution, that would be great too... ^^

Edited by Obelisk, 26 March 2012 - 05:17 AM.

[Wonko the Sane]

Obelisk
A file needs not to be contiguous if memory mapped.
A file needs to be contiguous if directly mapped.
The error you get plainly states that:

Error 60: File for drive emulation must be in one contiguous disk area

You can stamp your feet all the time you want, but until you make that .iso file contiguous in the filesystem it won't boot.

You can use a "wide" approach (defrag the whole disk/device hosting the .iso) or a "targeted" one, i.e. running Wincontig or Contig only on the file that needs to be made contiguous.

For the record your issue has NOTHING in common with the the OP and you just senselessly hijacked a thread instead of starting a new one with your issue (and clearly avoided to SEARCH the board before posting):
http://www.google.co...guous+disk+area


Wonko

[steve6375]

Thank you steve6375... but can you explain more about the error, and the usage of that RMPrepUSB ?
And... if any of you have a non-software-related solution, that would be great too... ^^

If you click on the RMPrepUSb link in my signature, it will take you to my website where a lot of tutorials can be found.
As well as 43 and 63, check out 61.
All you have to do is use your eyes and click!

[Obelisk]

Thank you all. Maybe I've too scared to fully read a document >"<.
My problem is gone by re-formatting the USB stick and recopy the file.

With the stuff mapping: I knew it too. But after times try to map a 2.54-GB-win-7-installer and get some RAM-dumping, I got the point ^^... Besides, not all PC has 3GB RAM as mine, what happen if I try to install Win7 for my friends... ?

Btw... Wincontig was alway tell me that "You should delete temporary files to make your disk cleaner blah blah blah"... Though at that time I had more than 22GB.

RMPrepUSB was another story though... A little confuse with its GUI, but I'll try it later ^^

Edited by Obelisk, 27 March 2012 - 02:18 AM.

[GGGBrightGGG]

!!!Solved!!!

http://www.rmprepusb.com/tutorials/firawiniso --->

 

=========================================================== =========================================================== =========================================================== Method (for USB Hard Drives)

1. Create a new folder on your hard drive called C:\WINFira

 

2. Download the zip file Tut43_FiraIso.zip from the Beta Downloads - Tutorials page and extract the contents to the C:\WINFira folder

Contents of Tut43_FiraIso.zip:

                 AutoUnattend.xml

                 Menu.lst

                 \FiraDisk folder

                          au.xml

                          firadi64.cat

                          iradi64.sys

                          firadisk.cat

                          firadisk.inf

                          firadisk.sys

                          LOADISO.CMD

                          slp.exe

                          spaces.txt

                          wenv                (not used in this tutorial)

                          \i386\devcon.exe

                          \ia64\devcon64.exe

                          mysetup.cmd   (not actually used - see Addendum below)

                          winpeshl.ini      (not actually used - see Addendum below)

                 \ISO folder

                          Choose_an_iso

                          <<<<<<<    (your iso files go here)

 

Note: these instructions also apply if you already have a bootable grub4dos disk, just extract the Tut43_FiraISO.zip contents onto it (note that it will overwrite your menu.lst though!) and copy all your ISO files to the USB drive and overwrite your grldr file with the recent one included in the latest version of RMPrepUSB v2.1.623 or later.

 

3. Now copy your Windows install ISO files to the C:\WinFira\ISO folder - Note: the iso filenames must NOT contain spaces!

 

You can download some Windows 7 ISOs from here. The Windows 8 Release Preview ISOs can be found here.

 

4. The sample menu.lst contains 5 (0-4) menu entries. The first menu entry is set to boot a fixed iso name. Just copy the first menu entry to make as many more as you like for all your ISO files. The second menu entry is merely to allow you to reboot to your hard disk after Windows has been installed onto it. The 3rd menu entry allows the user to choose which iso to boot to, by getting the user to type in the name of the iso that they want to use (note: does not work with Win8 ISOs). The last two menu entries are for Win 8 RP. You can delete any menu entries that you do not require.

 

New: Note that menu number 5 is not included in the download of menu.lst - this is a new menu which prompts the user for a Windows 8 Product Key before Windows Setup is run.

 

Edit the menu.lst and change the first line (title) and 3rd line (ISO filename) in each menu

 

5. Now prepare a USB Flash drive using RMPrepUSB (if you already have a bootable USB drive with grub4dos installed you do not need to do this - but you do the newish version of grldr)

 

    Run RMPrepUSB (use v2.1.622 or later)
        To wipe and format the USB drive (optional) - set the following options in RMPrepUSB:
        1. MAX
        2. (any volume name you like!)
        3. WinPE v2/v3 (or DOS or FreeDOS or XP)
        4. FAT32 or NTFS (or FAT16 but it has a 2GB limit)  and also select the Boot as HDD option ('Boot as HDD' adds a small 2nd partition and makes the BIOS to boot it as a hard disk instead of a ZIP or Floppy drive and thus you don't get 'flashing cursor' on boot on some BIOSes - e.g. EeePCs!)
        5. Tick Copy OS Files box and set the Copy Folder to C:\WINFIRA

        6. Click Prepare Drive to format the drive and copy the files over

 

NOTE: Whether you already have an existing grub4dos USB drive or have just formatted one as detailed above, you need to install the latest version of grub4dos as follows:

 

6. Now click on Install grub4dos and choose Yes forMBR and hit Enter to copy across the grldr file. You need the correct grub4dos grldr file as this supports some newer grub4dos commands.

 

Contents of bootable grub4dos drive should now be:

 

           AutoUnattend.xml

           grldr   (new 'chenall build' version as used by latest RMPrepUSB)

           Menu.lst

           \FiraDisk folder

                 au.xml

                 firadi64.cat

                 firadi64.sys

                 firadisk.cat

                 firadisk.inf

                 firadisk.sys

                 LOADISO.CMD

                 slp.exe

                 spaces.txt

                 wenv

                 \i386\devcon.exe

                 \ia64\devcon64.exe

           \ISO folder

                 Choose_an_iso

                 (your iso files go here)

                 <<<<<<<<<<<<<<<<<<<<<<<<<<<<< (use short names if possible to avoid typing!)

                                                                             ***Name must have NOT space***

 

You may have problems using an emulator

>>> You Should Test Boot With Real System

 

Fig. 43.6.4 IMPORTANT: you should see the blue Windows Command Shell window which installs the FiraDisk driver and then load the ISO file when Windows Setup starts. If you don't see this then it won't work!

 

Method (for USB Flash drives)

The auto-detection of \AutoUnattend.xml will not work if you use a hard drive (neither USB nor IDE/SATA) as a hard drive is not a 'removable' disk, we need to patch the ISO files themselves so that they will automatically run the LOADISO.CMD from the boot drive. To do this we need to copy the contents of the ISO file to an empty folder, modify the ISO file contents and then create a new version of the ISO file.

 

The guide below is for advanced users. I assume you already know how to mount images using ImageX (or DISM or GImageX) or can use similar tools. It is easiest to download and install theWindows 7 WAIK (over 1.3GB!). However, you can use Tutorial #83 to just download ImageX in about 30 seconds!

Please refer to my other tutorials (e.g. for WAIK and Virtual CloneDrive  see Tutorial #1) for details on installing and using the WAIK.

 

1. Using your Windows 'office' system, Mount the ISO that you want to modify using ImDisk or Virtual CloneDrive or any suitable tool and extract all the contents to an empty folder on your hard drive (e.g. C:\TESTISO)

 

2. If you want to be able to install any edition of Windows (e.g. all Vista/Win 7 SKUs rather than just Professional), then delete the C:\TESTISO\SOURCES\EI.CFG file.

 

If you have Win8, you will need to change the ei.cfg file contents to:

 

 

          [Channel]

          _Default

          

          [VL]

          0

 

3. Run a WAIK command prompt as Administrator (found in the Start Menu after installing WAIK) and mount the C:\TESTISO\Sources\boot.wim file (use Imagex /info to determine the correct image number that you need to mount, usually this is Index #2 - but not always!). e.g.

IMPORTANT: Make sure you use the correct wim image number - it is not always 2!

 

 

          imagex /info C:\TESTISO\SOURCES\boot.wim

          (check what images you have by looking at the output)

          mkdir c:\mount

          imagex /mountrw C:\TESTISO\SOURCES\boot.wim 2 c:\mount

 

 

4. Now we just need to copy the two files to theC:\mount\windows\system32 folder - winpeshl.ini andmysetup.cmd. Use the ones in the \FiraDisk folder inside thetutorial download. Their contents are shown below just for reference:

 

Although these two files are located in the \FiraDisk folder inside the Tutorial #43 Tut43_FiraIso.zip download for your convenience, they are not actually used in booting and can be deleted from the\FiraDisk folder after copying them to the mounted ISO folder - if you wish.

 

5. Commit the changes and unmount the mounted image - e.g.

 

         (close any Explorer windows which point at C:\mount first!)

         imagex /unmount /commit c:\mount

         imagex /cleanup

 

6. Create a new ISO file from the WAIK command prompt:

 

         oscdimg.exe -b"C:\Program Files\Windows AIK\Tools\PETools\x86\boot\etfsboot.com" -u1 -d -h -m -lWIN732SP1 C:\TESTISO\ C:\Win732SP1.iso

 

         (-l specifies the volume Label - note that the source path C:\TESTISO\ ends in a back-slash - however some versions of oscdimg may not like the final \ and you may get a 'usage' message - if so then remove the last backslash). The -u1(ISO9660) option ensures that the ISO is readable in both UDF and ISO 9660 (grub4dos readable) format - NOTE: when mounted by grubdos, all filenames will be uppercase - e.g. BOOTMGR not bootmgr. For maximum compatibility (e.g. with WinImage) you can also add -j1 for Joliet format (upper/lower case and long filenames).

 

6. Now follow the tutorial above but use this new ISO file. 

 

7. (optional) 

The Autounattend.xml file in the root of the USB drive is not required and can be deleted.

If you delete the AutoUnattend.xml file, you need also to change the menu.lst slightly and delete the lines that mention AutoUnattend.xml, otherwise the grub4dos menu will give an error as the file will no longer exist.

 

8. The new ISO should allow you to install any edition of Windows that is contained within the Install.wim file. You can also use the same files on a USB Flash drive if you wish.

 

Note: MySetup.cmd can run different versions of Setup.exe

X:\Setup.exe will run Setup and offer the Repair Operating System option.

%RAMDRIVE%\Setup.exe and \Sources\Setup.exe will go straight to the 'Install Windows' GUI and will not allow the user to Repair Windows.

 

If you do not want the Repair option offered, you should comment out the line shown in purple in MySetup.cmd (i.e. place a double colon :: in front of it - or delete the line).

To remove the Repair Y/N question, delete the following lines from the Firadisk\Loadiso.cmd file

 

          if not exist X:\sources\recovery\startrep.exe goto :SKIP_REPAIR

          echo.

          echo ********* REPAIR WINDOWS? **************

          echo.

          set /P ASK="Do you want to try to repair Windows (Y/N)? : "

          if /I "%ASK%"=="Y" start /w X:\sources\recovery\startrep.exe

 

[steve6375]

or just use Easy2Boot which is much easier!