Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Install XP from a RAM loaded ISO image


  • Please log in to reply
311 replies to this topic

#251
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

Firaidk and imdisk drver update in XP_INST_v05.7z at first post.


Will test today. Did you have to update the setup.cmd in anyway


I would add the chainloader line as below


title Setup Windows from ISO : \nBoot once from USB; with virtual CD+Floppy XP_INST.IMA
map /images/winsetup.iso (222)
map --mem /images/XP_INST.IMA (fd0)
map --mem /images/XP_INST.IMA (fd1)
map --mem (md)0x800+4 (99)
checkrange 0x80 read 0x8280 && geometry (hd1) && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && geometry (hd1) && map (hd1) (hd0)
map --hook
write --offset=0 (fd0)/setup/ISOimage.ini \\images\\winsetup.iso\n;\n;\n;
write --offset=0 (fd1)/setup/ISOimage.ini \\images\\winsetup.iso\n;\n;\n;
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/images/winsetup.iso;floppy,vmem=find:/images/firadisk.img;\n\0
chainloader (222)/I386/SETUPLDR.BIN

In my case if I don't add the line on bold, my ISO will prompt me to hit any key to boot but with the line...boots right into setup

Glad you posted this. Much simple menu.lst than mine. I actually was going to post a very simple version of my method later today but you beat me to it :realmad: :w00t:



Thanks, cdob

Edited by laddanator, 15 January 2012 - 08:18 AM.



How to remove advertisement from MSFN

#252
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

if required, USB drivers loaded at a addional reboot



When does the addition reboot take place if needed?


If I could get this registry entry to work, could be wrote on the fly to the setup.cmd and imdisk mount would not be needed


reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "StartOptions"="cdrom,vmem=find:/images/winsetup.iso"


What is the?

Run setup CMDline: setup -newsetup-


Does this new setup.cmd run cleanup automatically?

Edited by laddanator, 15 January 2012 - 08:43 AM.


#253
jaclaz

jaclaz

    The Finder

  • Developer
  • 13,985 posts
  • OS:none specified
  • Country: Country Flag

If I could get this registry entry to work, could be wrote on the fly to the setup.cmd and imdisk mount would not be needed

What do you mean?

What is the problem with that?

jaclaz

#254
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

What do you mean?

What is the problem with that?



I was saying since you can actually load XP with nothing but firadisk (but has to be done in two boots to USB and using grub4dos) and Imdisk is never used. I like Imdisk but if it all can be done with one driver (firadisk) would be great also. I have successfully installed XP with nothing but two firadisk commands but I don't like having to boot to USB to run a second g4d command


This being in the first command

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP/ISO/HOME.ISO;floppy,vmem=find:/XP/Floppy/firadisk.img;\n\0

and this in the second boot to USB and g4d command

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

I was reading you can add this command to registry (can't remember the link..will find and post)

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

and this would eliminate a second boot to USB for a second g4d command and the need for Imdisk mount for GUI

My problem is I added the registry command to my presetup.cmd and added a reboot command shutdown /r and when computer reboots, the command is not run and I get that global can't find CD error thing. So not exactly sure if the command is wrong. At this point I am not using, cdob XP_INST_v05 for this test but just the plain firadisk.ima.

@cdob, I just finished a XP Home install on my Asus M4A88TD-M/USB3 with you new XP_INST_v05.7z and all went well.

Edited by laddanator, 15 January 2012 - 09:29 AM.


#255
jaclaz

jaclaz

    The Finder

  • Developer
  • 13,985 posts
  • OS:none specified
  • Country: Country Flag
Yes, the question was because the snippet you posted seems like a "badly" formed one (bad copy/paste, typo, random attempt?:w00t:).

If you run that you get in Registry:
a key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FiraDisk
with in it a REG_SZ named "StartOptions" CONTAINING "StartOptions=cdrom,vmem=find:/images/winsetup.iso"

What you want INSTEAD is more probably:
a key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FiraDisk
with in it a REG_SZ named "StartOptions" CONTAINING ONLY "cdrom,vmem=find:/images/winsetup.iso"

jaclaz

#256
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

Yes, the question was because the snippet you posted seems like a "badly" formed one (bad copy/paste, typo, random attempt?:w00t:).


Wasn't entirely random. We are also talking about it here


http://www.msfn.org/...post__p__987670

and I knew cdob would know what I was talking about but I guess that doesn't help anyone else much. :ph34r:


so that's why it seems random here. :wacko:


If you run that you get in Registry:
a key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FiraDisk
with in it a REG_SZ named "StartOptions" CONTAINING "StartOptions=cdrom,vmem=find:/images/winsetup.iso"

What you want INSTEAD is more probably:
a key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FiraDisk
with in it a REG_SZ named "StartOptions" CONTAINING ONLY "cdrom,vmem=find:/images/winsetup.iso"


Will give this a whirl. Thanks, jaclaz

Edited by laddanator, 15 January 2012 - 09:44 AM.


#257
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

Posted Image

What you want INSTEAD is more probably:
a key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FiraDisk
with in it a REG_SZ named "StartOptions" CONTAINING ONLY "cdrom,vmem=find:/images/winsetup.iso"



I added the above as you suggested (this is just a test inside a running machine)

Just doesn't look right to me. Should there be more in the registry for firadisk to find the ISO after reboot on an install?

Edited by laddanator, 15 January 2012 - 10:09 AM.


#258
jaclaz

jaclaz

    The Finder

  • Developer
  • 13,985 posts
  • OS:none specified
  • Country: Country Flag

Just doesn't look right to me. Should there be more in the registry for firadisk to find the ISO after reboot on an install?

Well, it does look BETTER to me. :angel

I have NO idea whether it will help you :ph34r: , or will ever do what you are trying to do :w00t: , or of if the contents are "right" or if anything else is needed, it is simply (now) compliant with existing examples, compare with:
http://diddy.boot-la...files/disk4.htm
http://reboot.pro/8804/page__st__401

BTW, please notice what karyonix himself says in the above:

"file=find:\xxx" does not work, use drive letter.


jaclaz

#259
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

Well, it does look BETTER to me.


Sorry, didn't mean to say what you suggested was wrong...just figured it would be a bigger add


BTW, please notice what karyonix himself says in the above:

Quote
"file=find:\xxx" does not work, use drive letter.


Yes but the reboot pro link you gave (will have to find exact post) some examples do not have the drive letter. Since DP sets drive letter as %CDDRIVE%, I also tried this

in the presetup.cmd

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

but didn't accomplish my goal.

Edited by laddanator, 15 January 2012 - 01:31 PM.


#260
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

Just notice my slashes are the wrong way

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

g4d uses the slashes that way. Should be

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

#261
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

maanu, post 250 sums it up. Just have to expand your setup.exe and add it to the new IMA as described on the first page and use, cdob menu.lst from post 250

#262
cdob

cdob

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 962 posts

I would add the chainloader line as below
chainloader (222)/I386/SETUPLDR.BIN

Thanks, this is a good idea at a default image.
What about a multi boot iso image without /I386/SETUPLDR.BIN ?
What about
ls (222)BOOTFIX.BIN && chainloader (222)/I386/SETUPLDR.BIN
ls (222)/I386/BOOTFIX.BIN || chainloader (222)

map --mem /images/XP_INST.IMA (fd0)
map --mem /images/XP_INST.IMA (fd1)
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/images/winsetup.iso;floppy,vmem=find:/images/firadisk.img;\n\0

At second glance this is broken: firadisk search firadisk.img at a disk, but there is RAM loaded floppy used too.

Should be:
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/images/winsetup.iso;\n\0
Can you test this at real hardware?

Much simple menu.lst than mine.
But you have more testing hardware.
I'm used to one hard disk (read: BIOS maps target hard disk as hd1 at USB boot) and one usb drive. Any map (hd?) real experince is highly welcome.

FiraDisk StartOptions is in investigation.
Remember the name: a start option is valid at start: at firadisk driver start.
Firadisk is running after reboot already. A simple registry add won't work after driver is started.
And firadisk is marked as a boot driver: a net stop is rejected.
At a addional reboot there is a drive load order and drive intialization.
USB drivers has to be loaded, initialized, USB drive available. Next firadisk could find a file.
Unfortunately different hardware may gives different timing results. A solution may work at known hardware, but fail at other hardware.
At second glance: a driver pair firadisk/imdisk gives predictable timing. Should work at more machines.

Edited by cdob, 15 January 2012 - 05:11 PM.


#263
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

Thanks, this is a good idea at a default image.
What about a multi boot iso image without /I386/SETUPLDR.BIN ?
What about

ls (222)BOOTFIX.BIN && chainloader (222)/I386/SETUPLDR.BIN
ls (222)/I386/BOOTFIX.BIN || chainloader (222)


That will work. I do my multiboot ISO a little different (don't use BOOTFIX.BIN). I hex edit my setupldr.bin to change the path of the boot folder(can only use 4 letters or number). I use the same mod setupldr.bin over and over..only has to be hexed once...I could do a whole write up on this but I will try not to go off-topic


Much simple menu.lst than mine.

But you have more testing hardware.
I'm used to one hard disk (read: BIOS maps target hard disk as hd1 at USB boot) and one usb drive. Any map (hd?) real experince is highly welcome.


Didn't mean to say your was simple as in lame :lol: but for someone who is new to this, meant its easier to understand. I use a mod BOOTWS folder with the firadisk ISO loads.

Firadisk is running after reboot already. A simple registry add won't work after driver is started.



Been testing all day and I am going to put this registry thing on the back burner (given me a headache) since the 1 boot to USB method is working with your IMA stuff, all is good...besides I still have winsetupfromusb which I hear may be getting a newer release.

Should be:

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/images/winsetup.iso;\n\0

Can you test this at real hardware?


Tried this before but didn't have any luck but that was before your IMA file with setup.cmd. Will try now.

Been testing the new XP_INST.IMA today on my Asus M4A88TD-M/USB3 with three internal HD. The BOOTWS mod has come in nicely. All three XP (Home-Pro-MCE) have installed fine. Will test on Dells tomorrow at work.

Also I use variables so that I can use one XP_INST.IMA and much easier to write ISO name on the fly. Under each menu title I have this

set XPISO=HOME.ISO
set Image=XP.IMA

set XPISO=PRO.ISO
set Image=XP.IMA

set XPISO=MCE.ISO
set Image=XP.IMA

So end result looks like this

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;
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP/ISO/%XPISO%;floppy,vmem=find:/XP/Floppy/%Image%;\n\0

UPDATE


@cdob, just finished an install with PRO and only used this line

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP/ISO/%XPISO%;\n\0

so now this line is not needed

floppy,vmem=find:/images/firadisk.img;\n\0

Also I guess it would be a good idea to remove the firadisk driver and imdisk. I saw in the setup.cmd you have a line to remove Imdisk but not firadisk. Did I miss something? If not might not be a bad idea to add it to the cleanup section.

Something like this

devcon remove *\firadisk
del %WinDir%\system32\drivers\firadi*.sys

Edited by laddanator, 15 January 2012 - 06:55 PM.


#264
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

Text setup mode runs really slow on a older computer with this method as would if loaded from the actually CD. Wonder if the small ISO trick could be map to mem to say (0xFF) and after reboot to start GUI , cdob's, new setup command would run and mount the big ISO and finish install? Just to speed up text setup mode?


If the path to the big ISO has been written to the ISOimage.ini...don't see why not

Edited by laddanator, 17 January 2012 - 02:53 PM.


#265
cdob

cdob

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 962 posts

Text setup mode runs really slow on a older computer with this method

Which old hardware do you use?
Is a USB 2.0 controller available?
Does BIOS enable USB 2.0 speed at USB boot?

Loading a file to RAM may take some time.

Actually there are two textmode parts.
First: boot to user selectable target drive.
Second: Copy files to hard disk

Which part(s) refers to slow on a old computer?
Which time does it take? Name minutes and seconds.

Wonder if the small ISO trick could be map to mem

Which files are inside this ISO image?
A tiny ISO trick will fail.
If a small ISO contains first boot files to user selectable target drive, then first boot can be faster.
Following parts may work or fail.

It's possible to RAM load recovery console and install from flat file at same ISO file.
Compare recovery console part http://www.msfn.org/...post__p__890654

If the path to the big ISO has been written to the ISOimage.ini...don't see why not

There is a missing gap between tiny ISO file and ISOimage.ini.
Firadisk may map small ISO file and big ISO file.
And windows setup may boot from small ISO.
Next search files inside small ISO to copy to hard disk. However there are no files inside
How to satisfy setup?

#266
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

Which old hardware do you use?
Is a USB 2.0 controller available?
Does BIOS enable USB 2.0 speed at USB boot?


Old P3 with gig of ram. CD install of text mode setup doesn't go any faster (I timed it) No USB 2. USB 1.0 so of course this will be slower. I must like making more work for myself :blink:

Which files are inside this ISO image?


Haven't got that far. I will stick with what's working and leave the small ISO out of the mix for now.

Actually there are two textmode parts.
First: boot to user selectable target drive.
Second: Copy files to hard disk

Which part(s) refers to slow on a old computer?
Which time does it take? Name minutes and seconds.


About 3 min or so to run first txt setup part (same as CD on this machine) . Coping the files is faster (didn't time that part)


Next search files inside small ISO to copy to hard disk. However there are no files inside
How to satisfy setup?



Some how after the small iso being mapped to (oxff) and when text setup part1 finishes..loads files from the mapped big ISO (222). Sounds crazy but I have done crazier! :sneaky:

#267
mexus

mexus
  • Member
  • 1 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Can you please tell me how to use mkISO_RAMload_sort.cmd.

Never mind found it on a previous page, moderator please delete this post.

Edited by mexus, 26 January 2012 - 06:55 PM.


#268
Oct

Oct
  • Member
  • 1 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Hi

PLEASE HELP

I have an error at the Beginning of the text base setup. I get the blue windows setup screen, I get the "Press F6 ....", then the "Press F2 ....." but then it fails with the message below, i.e the full iso is loaded into the RAM then XP text based setup starts to loads but stops before loading any of the files.

I then get the error:



Please insert the disk labelled

Windows XP Professional Service Pack 3 CD

Into Drive A

Press enter when ready



Have i missed a step or something obvious ??

Is it a setting I need to modify to point to the ISO loaded into RAM ?


Please help, and thanks ...

Attached Files


Edited by Oct, 02 February 2012 - 10:02 AM.


#269
cdob

cdob

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 962 posts
v06 major redesign

One driver only - firadisk
no need to include setup.exe in floppy image
Driver firadisk is used within installation. And disabled at end of installation.

A sample menu.lst is included.

Usage examples:

1: simple case, friendly BIOS - try this first
ISO contents read from USB disk, not loaded to RAM.

2: strange USB BIOS or hardware - adds a reboot if necessary
ISO contents read from USB disk, not loaded to RAM.

3.map : small map RAM loaded boot files
ISO image created by mkISO_RAMload_sort.cmd
Loads textmode boot part to RAM, about 10-20mb data. This includes recovery console.
Other files are read by windows drivers at USB 2.0 speed
Prefer at USB1.x BIOS speed

3.dd: small dd RAM loaded boot files
Uses dd to copy data.
Lower speed, a fargmented ISO image possible.

4: RAM loaded install files
ISO image created by mkISO_RAMload_sort.cmd
Loads textmode boot and copy part to RAM
Fastest approach at USB 2.0 BIOS speed

5: RAM load ISO image
simple approach, use a existing ISO image

#270
laddanator

laddanator

    Member

  • Member
  • PipPip
  • 126 posts
  • OS:Windows 7 x86
  • Country: Country Flag

Donator

Cool beans! Testing now

#271
lucidanime

lucidanime
  • Member
  • 4 posts
  • OS:none specified
  • Country: Country Flag

v06 major redesign

One driver only - firadisk
no need to include setup.exe in floppy image
Driver firadisk is used within installation. And disabled at end of installation.

A sample menu.lst is included.

Usage examples:

1: simple case, friendly BIOS - try this first
ISO contents read from USB disk, not loaded to RAM.

2: strange USB BIOS or hardware - adds a reboot if necessary
ISO contents read from USB disk, not loaded to RAM.

3.map : small map RAM loaded boot files
ISO image created by mkISO_RAMload_sort.cmd
Loads textmode boot part to RAM, about 10-20mb data. This includes recovery console.
Other files are read by windows drivers at USB 2.0 speed
Prefer at USB1.x BIOS speed

3.dd: small dd RAM loaded boot files
Uses dd to copy data.
Lower speed, a fargmented ISO image possible.

4: RAM loaded install files
ISO image created by mkISO_RAMload_sort.cmd
Loads textmode boot and copy part to RAM
Fastest approach at USB 2.0 BIOS speed

5: RAM load ISO image
simple approach, use a existing ISO image


Tried out this method, I get to the textmode partition screen, I can select the device to install to, it get's formatted, and then setup pops up an error saying it can't find firadisk.sys, and various other files from the XP_INST.gz file. Am I doing something wrong?

#272
cdob

cdob

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 962 posts

it get's formatted, and then setup pops up an error saying it can't find firadisk.sys

Remembers to a BIOS issue.

Which hardware do you use?
Which windows files do you use? Do you use a original or a edited version? Any parts removed? Do you use a file winnt.sif?

Try double virtual floppy disk.

title Setup Windows XP from ISO \n1: simple case, unfriendly BIOS \ntry this 2nd
set dir=/images
set myISO=%dir%/XP_RAM.ISO
echo %myISO%
set fdIMA=%dir%/XP_INST.ima
cat --length=0 %myISO% > nul || find --set-root --devices=hf %myISO%
map %myISO% (222)
map --mem %fdIMA% (fd1)
map --mem %fdIMA% (fd0)
map --hook > nul
#use original firadisk.inf
#cat --number=1 --locatei="firaedit.inf" --replace="firadisk.inf" (fd1)/TXTSETUP.OEM > nul
#chenall's ntboot
cat --locate=###### --number=1 (fd1)/TXTSETUP.OEM > nul || call :error %fdIMA% file error..
set offset=%?%
set fira.opt=cdrom,vmem=find:%myISO%;
write --offset=%offset% (fd1)/TXTSETUP.OEM value=Parameters,StartOptions,REG_SZ,"%fira.opt%"\r\n;
cat --skip=%offset% --locate=/ --replace=\\ (fd1)/TXTSETUP.OEM
dd if=(fd1) of=(fd0)
command (fd1)/grub4dos/shifthd.bat
root (222)
chainloader /I386/SETUPLDR.BIN


#273
lucidanime

lucidanime
  • Member
  • 4 posts
  • OS:none specified
  • Country: Country Flag

it get's formatted, and then setup pops up an error saying it can't find firadisk.sys

Remembers to a BIOS issue.

Which hardware do you use?
Which windows files do you use? Do you use a original or a edited version? Any parts removed? Do you use a file winnt.sif?

Try double virtual floppy disk.

title Setup Windows XP from ISO \n1: simple case, unfriendly BIOS \ntry this 2nd
set dir=/images
set myISO=%dir%/XP_RAM.ISO
echo %myISO%
set fdIMA=%dir%/XP_INST.ima
cat --length=0 %myISO% > nul || find --set-root --devices=hf %myISO%
map %myISO% (222)
map --mem %fdIMA% (fd1)
map --mem %fdIMA% (fd0)
map --hook > nul
#use original firadisk.inf
#cat --number=1 --locatei="firaedit.inf" --replace="firadisk.inf" (fd1)/TXTSETUP.OEM > nul
#chenall's ntboot
cat --locate=###### --number=1 (fd1)/TXTSETUP.OEM > nul || call :error %fdIMA% file error..
set offset=%?%
set fira.opt=cdrom,vmem=find:%myISO%;
write --offset=%offset% (fd1)/TXTSETUP.OEM value=Parameters,StartOptions,REG_SZ,"%fira.opt%"\r\n;
cat --skip=%offset% --locate=/ --replace=\\ (fd1)/TXTSETUP.OEM
dd if=(fd1) of=(fd0)
command (fd1)/grub4dos/shifthd.bat
root (222)
chainloader /I386/SETUPLDR.BIN



Because I used BTS's DriverPacks, I had OEMPreinstall =YES in my winnt.sif. I set that to no, and loaded the firadisk driver using F6, and it worked like a charm!! Is there anyway to either intergrate Firadisk into textmode, or force the system to load it from the virtual floppy without needing to press F6?

#274
cdob

cdob

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 962 posts

Is there anyway to either intergrate Firadisk into textmode

Post #104 http://www.msfn.org/...post__p__988506

jIf ISO image is not found after first reboot, then add hivesys.inf settings from Post #58 http://www.msfn.org/...post__p__987629

or force the system to load it from the virtual floppy without needing to press F6?

Can be a BIOS issue still. Do you use a secret hardware?

#275
lucidanime

lucidanime
  • Member
  • 4 posts
  • OS:none specified
  • Country: Country Flag

Is there anyway to either intergrate Firadisk into textmode

Post #104 http://www.msfn.org/...post__p__988506

jIf ISO image is not found after first reboot, then add hivesys.inf settings from Post #58 http://www.msfn.org/...post__p__987629

or force the system to load it from the virtual floppy without needing to press F6?

Can be a BIOS issue still. Do you use a secret hardware?



It's not secret hardware, it's a LENOVO THINKCENTER 1578N9G. Everything worked perfectly when I pressed F6 to load firadisk, I tried integrating it, and it just gave me an error to insert Windows XP Professional SP3 disk into Drive A, so I think i'll stick with the F6 method for now




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN