[laddanator]

Quote

Don't you edit the ISO image anyway?

I do but you don't have to. I don't do anything major with the ISO but slipstream updates and add driver packs.

Quote

Read more sites and combine another approach.

Do you not like the method I listed above? Been getting allot of personal mail as to the how to of my method. I am thinking about making a YouTube video

Quote

so to sum it up , (i doubt if i am right , because all above details are giving me headache )

Let me sum it up a little. My menus.lst and method seems confusing because context is lost sometimes online. Just follows this

http://www.msfn.org/...aded-iso-image/

You can leave the paths default and name your ISO default and use this

timeout 15
color white/blue
write 0x8274 0x2001

title Boot From Hard Drive (Windows Vista/7 or Xp)\nBoot Into Main OS Drive
checkrange 0x80 read 0x8280 && map () (hd1)
checkrange 0x80 read 0x8280 && map (hd1) ()
checkrange 0x80 read 0x8280 && map --hook
rootnoverify (hd0,0)
chainloader +1 || chainloader /ntldr

title
root

title XP Home Install From ISO With 1 USB Boot\nWorks With Low Ram also
find --set-root  /Inst/XP_RAM.ISO
map --mem (md)0x800+4 (99)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
map  /Inst/XP_RAM.ISO (222)
#map --mem  /Inst/XP_INST.IMA (fd0) 
#map--mem  /Inst/XP_INST.IMA  (fd1)
map  /Inst/XP_INST.IMA (fd0) 
map /Inst/XP_INST.IMA  (fd1)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/Inst/XP_RAM.ISO;floppy,vmem=find:/Inst/XP_INST.IMA ;\n\0
rootnoverify (222)
chainloader (222)/I386/SETUPLDR.BIN

Quote

New approach uses new firadisk feature to search and mount the ISO file. That's one driver for textmode and gui mode.

If you don't use Imdisk to mount ISO at GUI, you will have to boot a second time to USB and use the second firadisk command is which I was trying to get away from

checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP/HOME.ISO;\n\0
root (hd0,0)
chainloader /ntldr
chainloader (hd0)+1

How do you write the ISO name to ISOimage.ini on the fly? Like this?

This is almost working for me. The error I am getting is can't find ISO \\XP\ISO\HOME.ISO backslash in front of the XP part. If I remove the double backslash I get XXP\

write --offset=0 (fd0)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n;
write --offset=1 (fd1)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n;

Quote

Post #53 - dorked links. Please correct. Method interests me greatly

Fixed

This post has been edited by laddanator: 13 January 2012 - 11:30 PM

[laddanator]

Quote

moreover , does cdob's USB to USB still valid with this trick ? i guess all imdisk will do , is search the iso and mount it again for windows setup to use .

Not sure haven't tested this

Quote

just like the win7 iso install trick ?

Again, not sure

Quote

please attach your modded .IMA file

I will work on this but would like for, cdob, to give me the ok

[cdob]

laddanator, on 13 January 2012 - 05:33 PM, said:

Do you not like the method I listed above?

Don't you remember? I recommended this approach at reboot.pro. Yes, I like it.
I dislike the technical requirement of two different drivers. A one driver approach seems to be nicer.
I did this years ago to support a default ISO image.

It's a user personal choice:
Some users prefers default ISO file and a virtual floppy image.
Drawback, you can't use a USB floppy anymore to load F6 drivers.
Grub4dos and BIOS has to support this. The virtual floppy approach fails at some BIOS.

Other users prefers all drivers and addons inside the ISO file.
This can be done too.

There is no one size fit all solution.

Quote

If you don't use Imdisk to mount ISO at GUI, you will have to boot a second time to USB and use the second firadisk command is which I was trying to get away from

Firadisk read settings from registry too. The other approach uses hivesys.inf

Quote

;search ISO image
HKLM,"SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\images\winsetup.iso"

Firadisk read registry and search \images\winsetup.iso.
No need for a second boot to USB.

Quote

How do you write the ISO name to ISOimage.ini on the fly?

Seems to be a grub4dos error. Try remove %XPISO%, use a fixed name at menu.lst.

Quote

I will work on this but would like for, cdob, to give me the ok

Thanks for asking. Give me this weekend to validate the newer setup.cmd again.
Automatic usb drivers load is nice for the pubilic at troublesome BIOS.
And I dislike the requirement to edit setup.cmd. All user settings should be at menu.list or a ini file.
Of course you may setup.cmd in addition, but default should be to keep it.

Do you use a approach at work?
Do you remove firadisk and imdisk at end of installation?
Do you need default USB settings at end of installation?
The CriticalDeviceDatabase approach changes default behaviour. Do you restrict end users at USB usage, disallow USB storage?
If you set relating permissions, it may be a good idea to remove USB CriticalDeviceDatabase at end of installation.

[laddanator]

Quote

Seems to be a grub4dos error. Try remove %XPISO%, use a fixed name at menu.lst.

Actually got this to work. Had an invisible space before the first backslash (invisible script killer..as I like to call it)

write --offset=0 (fd0)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n;
write --offset=0 (fd1)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n;

Will work with variable but should both offset=0 for fd0 and fd1?

Both should be offset=0

Quote

Firadisk read registry and search \images\winsetup.iso.
No need for a second boot to USB.

I will give this a try.

Quote

And I dislike the requirement to edit setup.cmd. All user settings should be at menu.list or a ini file.

I agree. Did a new method last night that I just added your newer setup.cmd to the IMA and didn't change anything else and just wrote the ISO name and path on the fly in the ISOimage.ini and XP installed fine (if you don't map the IMA file to memory, the write change will be permanent) . So pretty much everything was done from the menu.lst. If folks are confused about editing the IMA, then I will not post a "write up" on the registry method but will post if it worked for me or not

Quote

Of course you may setup.cmd in addition, but default should be to keep it.

Again agree...will post my new findings later with no setup.cmd editing and all done on the fly

Quote

Do you use a approach at work?

I do but not testing on customer computer. We have crap tons of computer from HP to Dell and so on laying around I test on.

Quote

Do you remove firadisk and imdisk at end of installation?

Do you think it's a good idea too?

Quote

Do you need default USB settings at end of installation?

No, that I have found so far. I tested all USB ports with different USB HD and USB JumpDrive

Quote

The CriticalDeviceDatabase approach changes default behavior. Do you restrict end users at USB usage, disallow USB storage?

Like I said, not tested on customers computer as of yet. Wanted to make sure all is good before I do.

Quote

If you set relating permissions, it may be a good idea to remove USB CriticalDeviceDatabase at end of installation.

What would you suggest to do this?

Quote

Thanks for asking. Give me this weekend to validate the newer setup.cmd again.
Automatic usb drivers load is nice for the public at troublesome BIOS.

No problem. I installed an XP Home on my Asus M4A88TD-M/USB3 last night with the newer setup.cmd from your later post and on the fly write of the ISOimage.ini and all went well. Look forward to any new stuff and thanks, cdob

This post has been edited by laddanator: 14 January 2012 - 08:48 AM

[laddanator]

Quote

;search ISO image
HKLM,"SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\images\winsetup.iso"

Couldn't firadisk driver be added to the XP source and then add the registry stuff?

Also since firadisk is copied to the system from txtseup.oem maybe the

Quote

HKLM,"SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\images\winsetup.iso"

could be written to the setup.cmd on the fly?

This post has been edited by laddanator: 14 January 2012 - 12:25 PM

[cdob]

laddanator, on 14 January 2012 - 07:23 AM, said:

write --offset=0 (fd0)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n;
write --offset=0 (fd1)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n;

Will work with variable

That's nice.

Quote

I just added your newer setup.cmd to the IMA and didn't change anything else and just wrote the ISO name and path on the fly in the ISOimage.ini and XP installed fine (if you don't map the IMA file to memory, the write change will be permanent) . So pretty much everything was done from the menu.lst.

Thanks for report.
Yes, flat file mapped IMA writes to hardware. This require a friendly BIOS too. Don't rely on that.

Quote

I will not post a "write up" on the registry method but will post if it worked for me or not

Be aware, that's under construction still. Most likely I'll change the approach.

Quote

What would you suggest to do this?

Call "setup.cmd -cleanup" late at [GuiUnattended]. This restores default registry settings.

Can you accept one more reboot at setup.cmd approach?
Add registry setting inside setup.cmd and reboot. ImDisk is obsolete that way.

laddanator, on 14 January 2012 - 07:27 AM, said:

Couldn't firadisk driver be added to the XP source and then add the registry stuff?

Yes, that's possible.

cdob, on 13 January 2012 - 02:58 PM, said:

Next step would be include firadisk in ISO image.

However this would require to edit a ISO file. Do you like to edit a iso file?
There are different approaches to add registry settings.

[laddanator]

Quote

This require a friendly BIOS too. Don't rely on that.

Actually working on something or a different type of mapping that doesn't require mapping to virtual type floppy (fd0) or (fd1)

Quote

Call "setup.cmd -cleanup" late at [GuiUnattended]. This restores default registry settings.

Is the cleanup, the line below? (Already in the newer setup.cmd)

:cleanup ======================================================
set SYSTEM=HKLM\SYSTEM
set CriticalDeviceDatabase=%SYSTEM%\CurrentControlSet\Control\CriticalDeviceDatabase
set Services=%SYSTEM%\CurrentControlSet\Services

REM +=======================================================+
REM | restore default USB settings                          |
REM |-------------------------------------------------------|
reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0300" /f
reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0310" /f
reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0320" /f
reg.exe delete "%CriticalDeviceDatabase%\USB#CLASS_08" /f
reg.exe delete "%CriticalDeviceDatabase%\USB#CLASS_09" /f
reg.exe delete "%CriticalDeviceDatabase%\USB#ROOT_HUB" /f
reg.exe delete "%CriticalDeviceDatabase%\USB#ROOT_HUB20" /f
reg.exe add "%Services%\usbohci" /f /t REG_DWORD /v "Start" /d 3
reg.exe add "%Services%\usbuhci" /f /t REG_DWORD /v "Start" /d 3
reg.exe add "%Services%\usbehci" /f /t REG_DWORD /v "Start" /d 3
reg.exe add "%Services%\usbhub" /f /t REG_DWORD /v "Start" /d 3
reg.exe add "%Services%\usbstor" /f /t REG_DWORD /v "Start" /d 3

rem net.exe stop imdisk
rem sc.exe delete ImDisk
rem delete drivers\imdisk.sys
REM +=======================================================+
goto :eof  === cleanup ====================================== 

If so I run a ProgramInstaller.cmd in runonce at first login, I could just add the line to that cmd?

Quote

However this would require to edit a ISO file. Do you like to edit a iso file?
There are different approaches to add registry settings.

No, that's why I was wondering if writing the reg entries to the setup.cmd along with the other entries on the fly would work?

Quote

Add registry setting inside setup.cmd and reboot. ImDisk is obsolete that way

Are you referring to this?

Quote

HKLM,"SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\images\winsetup.iso"

and why would this cause another reboot

Quote

Can you accept one more reboot at setup.cmd approach?

And can the reg command be added like this

write --offset=251 (fd0)/setup/setup.cmd reg.exe add "HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\XP\ISO\HOME.ISO
write --offset=251 (fd1)/setup/setup.cmd reg.exe add "HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\XP\ISO\HOME.ISO


This was added to registry from setup.cmd and after DP finishes...Global cant find CD Rom error popped up

reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "cdrom,file=%CDDRIVE%\XP\ISO\HOME.ISO" 

And this failed also.

reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "StartOptions"="cdrom,vmem=find:/XP/ISO/HOME.ISO"

I know this was added because after load is finished (had to use part two of the firadisk method for this test to finish install)...the command is in the registry

Also added this to my ProgramInstaller.cmd that runs on first log in after install finishes (runonce)

:cleanup ======================================================
set SYSTEM=HKLM\SYSTEM
set CriticalDeviceDatabase=%SYSTEM%\CurrentControlSet\Control\CriticalDeviceDatabase
set Services=%SYSTEM%\CurrentControlSet\Services

REM +=======================================================+
REM | restore default USB settings                          |
REM |-------------------------------------------------------|
reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0300" /f
reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0310" /f
reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0320" /f
reg.exe delete "%CriticalDeviceDatabase%\USB#CLASS_08" /f
reg.exe delete "%CriticalDeviceDatabase%\USB#CLASS_09" /f
reg.exe delete "%CriticalDeviceDatabase%\USB#ROOT_HUB" /f
reg.exe delete "%CriticalDeviceDatabase%\USB#ROOT_HUB20" /f
reg.exe add "%Services%\usbohci" /f /t REG_DWORD /v "Start" /d 3
reg.exe add "%Services%\usbuhci" /f /t REG_DWORD /v "Start" /d 3
reg.exe add "%Services%\usbehci" /f /t REG_DWORD /v "Start" /d 3
reg.exe add "%Services%\usbhub" /f /t REG_DWORD /v "Start" /d 3
reg.exe add "%Services%\usbstor" /f /t REG_DWORD /v "Start" /d 3

rem net.exe stop imdisk
rem sc.exe delete ImDisk
rem delete drivers\imdisk.sys
REM +=======================================================+
goto :eof  === cleanup ====================================== 

The first 7 delete commands give can't find registry entry command

The 5 add complete successfully

By the way, the rebooting I don't mind,,,its the rebooting to grub4dos to run a second menu.lst command is what I try to avoid

This post has been edited by laddanator: 14 January 2012 - 10:43 PM

[laddanator]

cdob, should I be posting here about added firadisk to registry and skipping imdisk mount during install or would it be better to post in the XP from RAM post?

[jilaliotmane]

can you make a clear tutorial .. maybe with a vidéo..
because i didn't understand any think

[laddanator]

I would like to make a video tutorial (would be my first) for winsetupfromusb and this method. Just need to get permission from ilko_t and cdob

It's easy for me to say but this method is really simple. Sometimes I can't find the words to make since of the details but maybe in video would clear things up.

This post has been edited by laddanator: 15 January 2012 - 02:34 PM

[jaclaz]

laddanator, on 15 January 2012 - 01:24 PM, said:

I would like to make a video tutorial (would be my first) for winsetupfromusb and this method. Just need to get permission from ilko_t and cdob

It's easy for me to say but this method is really simple. Sometimes I can't find the works to make since of the details but maybe in video would clear things up.

Should you want my opinion (completely UNasked for ) there is nothing as UNuseful as a video tutorial for such complex things WITHOUT a proper, clear, textual tutorial (and the possibility to copy/paste, etc.).
A video may be a nice addition, not a replacement, IMNSHO.

jaclaz

[laddanator]

Quote

Should you want my opinion (completely UNasked for ) there is nothing as UNuseful as a video tutorial for such complex things WITHOUT a proper, clear, textual tutorial (and the possibility to copy/paste, etc.).
A video may be a nice addition, not a replacement, IMNSHO.

You been around here along time so your opinion is always welcome. I been doing this awhile but never really had to explain how I came to a point or my methods to others. I need to remember that instead of posted advance menu.lst and so on, that the simple basic will work also so people who are new to this can start with the basic and change things to fit their needs as they get more comfortable.

[laddanator]

Quote

setup.cmd -cleanup

is the -cleanup like a switch to the cmd file?

[maanu]

laddanator, on 15 January 2012 - 02:34 PM, said:

Quote

setup.cmd -cleanup

is the -cleanup like a switch to the cmd file?

it will simply call the cleanup part of the batch file.

try this floppy image of friadisk , made by my chinese friend Sratif (moderator of Wuyou forums )

http://db.tt/Bl77RtUG

study batch file included and inf file too.


@ cdob

did you face any error while testing server 2003 sp2 32bit using iso install method ?

after formatting partition, when windows start to copy files, it gives me error

" firadisk,sys not found , make sure cd is stil in cdrom and bla bla "

and all the other files which are in XP_RAM.IMA 0.5



title XP Home Install From ISO With 1 USB Boot\nWorks With Low Ram also
find --set-root /Inst/XP_RAM.ISO
map --mem (md)0x800+4 (99)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
map /Inst/XP_RAM.ISO (222)
#map --mem /Inst/XP_INST.IMA (fd0)
#map --mem /Inst/XP_INST.IMA (fd1)
map /Inst/XP_INST.IMA (fd0)
map /Inst/XP_INST.IMA (fd1)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/Inst/XP_RAM.ISO;floppy,vmem=find:/Inst/XP_INST.IMA ;\n\0
rootnoverify (222)
chainloader (222)/I386/SETUPLDR.BIN

title XP Home Install From ISO With 1 USB Boot\nWorks With Low Ram also
find --set-root /Inst/XP_RAM.ISO
map --mem (md)0x800+4 (99)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
map /Inst/XP_RAM.ISO (222)
map --mem /Inst/XP_INST.IMA (fd0)
map --mem /Inst/XP_INST.IMA (fd1)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/Inst/XP_RAM.ISO;floppy,vmem=find:/Inst/XP_INST.IMA ;\n\0
rootnoverify (222)
chainloader (222)/I386/SETUPLDR.BIN


mapping XP_INST.IMA to memory , and direct map , both result with same error , required files not found , after setup format partition .
just wondering why this is happening for server2003 only . ??
by the way , above entries work OK on xp iso.

This post has been edited by maanu: 15 January 2012 - 03:06 PM

[laddanator]

Quote

mapping XP_INST.IMA to memory , and direct map , both result with same error , required files not found , after setup format partition .
just wondering why this is happening for server2003 only . ??
by the way , above entries work OK on xp iso.

Cant answer for sure but I don't think Server2003 is supported by cdob can answer that better

Quote

it will simply call the cleanup part of the batch file.

Seems it is not set to run at default so thought maybe some kinda switch -cleanup

if /I %1.==-cleanup. (call :cleanup &goto :eof)
if /I %1.==-usb_boot. (
call :set_usb_boot_setting SYSTEM CurrentControlSet
bootcfg.exe /TIMEOUT 8
goto :eof

makes me think this is a switch.

Ok, is a switch. Just ran setup -cleanup from a test.cmd and the cleanup process ran only. Cool

Quote

try this floppy image of friadisk , made by my chinese friend Sratif (moderator of Wuyou forums )

http://db.tt/Bl77RtUG

study batch file included and inf file too.

Will do. What does this do exactly?

This post has been edited by laddanator: 15 January 2012 - 04:10 PM

[laddanator]

This part can be removed from the menu.lst

floppy,vmem=find:/Inst/XP_INST.IMA ;\n\0

and just use this part

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/Inst/XP_RAM.ISO;\n\0

The Find Floppy is not needed due to memory or direct map of IMA

[cdob]

maanu, on 15 January 2012 - 02:50 PM, said:

did you face any error while testing server 2003 sp2 32bit using iso install method ?

A default 2003 SP2 32bit trial does install fine here.
Did you edited the ISO file? Which file size do you use?

Quote

" firadisk,sys not found , make sure cd is stil in cdrom and bla bla "

Which hardware and grub4dos version do you use?

Try fd0 only

map --mem /images/XP_INST.IMA (fd0)
#map --mem /images/XP_INST.IMA (fd1)

And about false hdN machines: can you name a example?
Which disks are connected?
Boot grub4dos, press c to command line.
Which fd and hd devices are listed?
Which device match USB drive?
Which device match internal hard disks?

[maanu]

i use modded server 2003 ISO , it is actually DataCenter edition . size about 300 MB.

i will try with fd0 only.
and i use grub4dos 2012-12-30 . modded iso's of xp work fine on same hardware though.

i have an old branded DELL desktop . 1TB seagate + 80GB Samsung . booted with 8GB Kingsten . made bootable using fbinst.

[cdob]

maanu, on 17 January 2012 - 11:39 AM, said:

i use modded server 2003 ISO size about 300 MB.

That's havily modded. Try a vanilla 2003 image.

Quote

modded iso's of xp work fine on same hardware though.

I'm getting missing firadisk at XP size about 300 MB. It's size or nlited version?
Does your txtsetup.sif calls sfloppy.sys still?

Quote

i have an old branded DELL desktop .

Which Dell desktop do you use?

Quote

1TB seagate + 80GB Samsung . booted with 8GB Kingsten .

Which boot drive do you use by default?
Which XP/2003 target do you install to?

Edit menu.lst, replace two checkrange lines with

#checkrange 0x80 read 0x8280 && geometry (hd1) && map (hd0) (hd1)
#checkrange 0x80 read 0x8280 && geometry (hd1) && map (hd1) (hd0)

clear

echo existing hd:
echo
geometry (hd9) && echo
geometry (hd8) && echo
geometry (hd7) && echo
geometry (hd6) && echo
geometry (hd5) && echo
geometry (hd4) && echo
geometry (hd3) && echo
geometry (hd2) && echo
geometry (hd1) && echo
geometry (hd0) && echo

pause pause

clear
echo mapping hd

#calculate max HDD
set /a hdN=*0x475&0xff + 0x80 - 1
echo max HDD (%hdN%)

geometry (hd9) && map (hd9) (hd8) && echo map (hd9) (hd8) && echo
geometry (hd8) && map (hd8) (hd7) && echo map (hd8) (hd7) && echo
geometry (hd7) && map (hd7) (hd6) && echo map (hd7) (hd6) && echo
geometry (hd6) && map (hd6) (hd5) && echo map (hd6) (hd5) && echo
geometry (hd5) && map (hd5) (hd4) && echo map (hd5) (hd4) && echo
geometry (hd4) && map (hd4) (hd3) && echo map (hd4) (hd3) && echo
geometry (hd3) && map (hd3) (hd2) && echo map (hd3) (hd2) && echo
geometry (hd2) && map (hd2) (hd1) && echo map (hd2) (hd1) && echo
geometry (hd1) && map (hd1) (hd0) && echo map (hd1) (hd0) && echo
geometry (hd0) && map (hd0) (%hdN%) && echo map (hd0) (%hdN%) && echo

map --hook

pause pause

clear
echo mapped hd
echo 
geometry (hd9) && echo
geometry (hd8) && echo
geometry (hd7) && echo
geometry (hd6) && echo
geometry (hd5) && echo
geometry (hd4) && echo
geometry (hd3) && echo
geometry (hd2) && echo
geometry (hd1) && echo
geometry (hd0) && echo

pause pause

Post the output messages.

Does boot.ini work now?

[laddanator]

Quote

geometry (hd9) && map (hd9) (hd8) && echo map (hd9) (hd8) && echo
geometry (hd8) && map (hd8) (hd7) && echo map (hd8) (hd7) && echo
geometry (hd7) && map (hd7) (hd6) && echo map (hd7) (hd6) && echo
geometry (hd6) && map (hd6) (hd5) && echo map (hd6) (hd5) && echo
geometry (hd5) && map (hd5) (hd4) && echo map (hd5) (hd4) && echo
geometry (hd4) && map (hd4) (hd3) && echo map (hd4) (hd3) && echo
geometry (hd3) && map (hd3) (hd2) && echo map (hd3) (hd2) && echo
geometry (hd2) && map (hd2) (hd1) && echo map (hd2) (hd1) && echo
geometry (hd1) && map (hd1) (hd0) && echo map (hd1) (hd0) && echo
geometry (hd0) && map (hd0) (%hdN%) && echo map (hd0) (%hdN%) && echo

Can this be used in the everyday menu.lst to map the HD for more than one HD or is this for test purposes?