• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
cdob

Install XP from a ISO file

136 posts in this topic

as usual no way to repair the unknown device (winvblock) in device manager into XP.

If you look carrefully, I think the device is working absolutely fine, there is no exclamation mark on the device icon.

It is just an unknown device, and it comes with a question mark; XP does not know in which correct category it should put it (SCSI and RAID controllers). But it is really working fine and does not need repairing.

0

Share this post


Link to post
Share on other sites
I am using AMD Athlon 64 X2 Dual Core 4800+ and ASUS M2A-VM HDMI mobo

and Windows XP SP3 Professional (with and without UpdatePack)

I found that if the WinVBlock virtual floppy is defined in RAM using --mem option,

then the virtual CD on USB will survive install of devices in GUI mode and XP Setup is OK.

At a ASrock N68C-S UCC (AMIBIOS) map --mem fails still. CD-ROM disappear at PNP.

Idea: Open a handle to virtual CD-ROM drive.

Compare

Press shift F10 to open command console at a default install ISO.

Change directory to virtual CD ROM drive.

This opens a handle CD ROM drive. Keep this windows open. PNP dosn't truncate access.

At DriverPacks edit presetup.cmd

:DPsFound
start /b "Open handle to virtual CD-ROM drive." pushd "%CDDRIVE%"

Another cmd.exe is launched in context to running hidden presetup.cmd.

Hence this cmd.exe is hidden too.

At driver February 14 I don't use virtual floppy at first reboot anymore.

Driver and txtsetup.oem was updated. Add file winvblk.cat to virtual floppy too.

title 2 Continue Windows XP setup

map /Inst/XP_RAM.ISO (0xff)

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

map --hook

chainloader (hd0)+1

0

Share this post


Link to post
Share on other sites

You need the MassSorage as boot driver.

I would advise to use DPsBase.exe and MassStorage + TXT-mode enabled (gives boot driver)

and use method 2 (as always).

Thanks, that worked just fine and I passed the point of blue screen now on newer machines.

I didn't tried to finish the installation on that PC thou.

I'll try on older PC today at work... (I reedited my post if you saw it few minutes ago because

I have to try it again... I made mistake in menu.lst)

Edited by tonyzg
0

Share this post


Link to post
Share on other sites

I had similar issue to Wimb. See my tutorial on RMprepUSB website at http://sites.google.com/site/rmprepusb/tutorials/install-xp-from-an-iso

Step 1 works fine when directly mapped to the ISO

Step 2 GUI stage crashes unless iso is mapped using --mem :-(

@tonyzg - re. RMPrepUSb and flashing cursor. Did you try latest version of RMPrepUSB = v2.1.617. This should be fixed. If not can you send me the contents of the MBR of your working USB drive as it seems that the systems that give a flashing cursor do not like the RMPrepUSB MBR??? The latest version has a modified version of grub4dos too so you can install to MBR or PBR. I would be interested to know if they both worked on all your systems?

0

Share this post


Link to post
Share on other sites

Step 1 works fine when directly mapped to the ISO

Step 2 GUI stage crashes unless iso is mapped using --mem :-(

Have you tried cdob's trick ?

Presumably this applies to a vanilla XP ISO:

Press shift F10 to open command console at a default install ISO.

Change directory to virtual CD ROM drive.

This opens a handle CD ROM drive. Keep this windows open. PNP dosn't truncate access.

and this to a modified ISO with DriverPacks integrated:

At DriverPacks edit presetup.cmd

:DPsFound
start /b "Open handle to virtual CD-ROM drive." pushd "%CDDRIVE%"

Another cmd.exe is launched in context to running hidden presetup.cmd.

Hence this cmd.exe is hidden too.

It would be very useful to know if this trick solves the problem in your case.

0

Share this post


Link to post
Share on other sites

At DriverPacks edit presetup.cmd

:DPsFound
start /b "Open handle to virtual CD-ROM drive." pushd "%CDDRIVE%"

Another cmd.exe is launched in context to running hidden presetup.cmd.

Hence this cmd.exe is hidden too.

This modification of presetup.cmd works for me.

The WinVBlock virtual floppy is NOT needed anymore at reboot for GUI-mode.

The XP Setup source in virtual CD on USB is found and survives install of devices.

GUI-mode of XP Setup continues without error. Install of XP is OK. :thumbup

The proposed title 2 of grub4dos menu did NOT work for me.

On selecting title 2 I returned to grub4dos menu on USB-stick.

I did modify and used original mapping of title 2 and then everything worked for me:


title 1 Start Windows XP setup - XP3_11_2.iso
map --mem /winvblock.ima (fd0)
map --mem /winvblock.ima (fd1)
map /XP3_11_2.iso (0xff)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
chainloader (0xff)

title 2 Continue Windows XP setup
map /XP3_11_2.iso (0xff)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
chainloader (hd0)+1

Boot twice from USB (using title 1 and 2) - and then Reboot from drive where XP is installed.

Congratulations with the NEW method for Install of XP from USB

I think it is the most simple way to Install XP from USB :thumbup

The same method can also be used to Install XP in HDD Image file

as described by Doodoo and sara - pmedia and wimb

http://reboot.pro/13856/page__p__122385#entry122385

http://reboot.pro/13731/

http://www.911cd.net/forums//index.php?showtopic=23553

cheers.gif

post-132150-0-52536700-1298618620_thumb.

Edited by wimb
0

Share this post


Link to post
Share on other sites

The WinVBlock virtual floppy at reboot for GUI-mode is NOT needed anymore.

Except maybe if you want to use an answer file ? Or do you include it in the ISO itself (but I find that a little less flexible... Just a matter of personal taste really)

0

Share this post


Link to post
Share on other sites

Except maybe if you want to use an answer file ?

The winnt.sif file is only needed in TXT-mode.

The GUI-mode will use the created WINDOWS\system32\$winnt$.inf file which contains the info of winnt.sif

Edited by wimb
0

Share this post


Link to post
Share on other sites

Topic pinned. :)

jaclaz

0

Share this post


Link to post
Share on other sites
I've tested it and works, setup goes on in text mode but after reboot I needed to build the MBR before step 2.

But I seriously suppose there must be a bug into the bios of my old test machine (mobo foxconn cpu intel p4).

as usual no way to repair the unknown device (winvblock) in device manager into XP.

@Davlak

Did you delete the partitions and reformat using XP Setup or did you leave the existing partition and just reformat. If you have off-track partitions (such as made by WinPE v2 and v3 DISKPART) then it may well fail to boot from HDD.

Always create a new partition for your tests.

I have to use DISKPART with the CRE PRI ALIGN 1065 command in WinPE v2/v3 before running winnt32 to ensure the partition is on a cylinder boundary. It may be the same with Setup?

Edited by steve6375
0

Share this post


Link to post
Share on other sites

If you tell ISO file name to WinVBlock in step 2, it should keep ISO file opened without having to use cmd trick.

Or you may try FiraDisk 0.0.1.30 with ISO file name in its parameter in small mem drive.

I tried to tell ISO filename to WinVBlock in step 2,

but unfortunately the virtual CD drive on USB-stick did NOT survive Install of devices in GUI-mode of XP Setup.

XP Setup FAILED as described earlier .... :(

It means that the cmd trick as proposed by cdob will remain as working solution. :thumbup

This is the Grub4dos menu title 2 that I used and where XP Setup FAILED


title 2 Continue Windows XP setup
map /XP3_1102.iso (0xff)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --rd-size=2048
map --mem (rd)+4 (0x55)
map --hook
write (0x55) #GRUB4DOS\x00v=1\x00XP3_1102.iso\x00\xff\x00
chainloader (hd0)+1

Edited by wimb
0

Share this post


Link to post
Share on other sites

I was attempting to run this type of setup but ran into a small snag...

If I go into presetup.cmd and add the line below "DPsFound" (as suggested).

:DPsFound

start /b "Open handle to virtual CD-ROM drive." pushd "%CDDRIVE%"

Then when it goes into TXT-mode setup, it will say that it "cannot copy presetup.cmd". If I go back to an ISO where this is unchanged, it will copy the file fine (but then loses the ISO mapping in GUI setup). If I manually copy the changed presetup.cmd then GUI setup will work fine.

Any ideas why modifying presetup.cmd would make it fail to copy in TXT setup?

If I look in TXTSETUP.SIF, I see setuporg.exe and presetup.cmd listed properly under sourcedisk files (as people on other message boards suggested checking this)

Thanks

~Fizz

Edited by daddy_fizz
0

Share this post


Link to post
Share on other sites
Or you may try FiraDisk 0.0.1.30 with ISO file name in its parameter in small mem drive.
Thanks, virtual CD-ROM survive PNP.

Install Windows XP from ISO on UFD to SATA hard disk by karyonix http://reboot.pro/13967/

I'm using

title 1 Start Windows XP setup - firadisk.img - /XP.iso
map --mem (md)0x800+4 (99)
map /firadisk.img (fd0)
map /firadisk.img (fd1)
map /XP.iso (0xff)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP.iso;floppy,vmem=find:/firadisk.img;\n\0
chainloader (0xff)

title 2 Continue Windows XP setup - firadisk.img /XP.iso
map --mem (md)0x800+4 (99)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP.iso;\n\0
chainloader (hd0)+1

0

Share this post


Link to post
Share on other sites

Installing from iso always skip the part with licence agreament (where we need to pres F8 to accept)

and doesn't recognize previously installed Windows XP. What about you guys?

0

Share this post


Link to post
Share on other sites

@tonyzg

Yes, a existing a:\txtsetup.oem turns setupldr.bin to this internal defaults: a kind of unattended installation.

0

Share this post


Link to post
Share on other sites

@tonyzg

Yes, a existing a:\txtsetup.oem turns setupldr.bin to this internal defaults: a kind of unattended installation.

Hmmmm, so I can't use this method to repair Windows installation...

Is there a way to enable this? Changing txtsetup.oem maybe?

0

Share this post


Link to post
Share on other sites
so I can't use this method to repair Windows installation...

Adapt this method:

don't use a (virtual) floppy

integrate the mass storage driver into the ISO file

0

Share this post


Link to post
Share on other sites

Hi, I am just dropping in to report that the installation of XP from an ISO, where both the mass storage drivers needed by the mobo and firadisk have been integrated using nlite, works fine. I built a XP ISO with drivers for all types of Intels ICH7(x) to ICH10(x) controller ( both raid and ahci drivers ), NVidias Nforce7 chipset ( raid and ahci ) and firadisk itself. Then I used the following configuration ( winsetup.lst ) for grub4dos:


title First part of Windows XP setup from ISO
map --mem (md)0x800+4 (99)
map /XP.iso (0xff)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP.iso;\n\0
chainloader (0xff)

title Second part of XP setup from ISO / Boot first internal hard drive
map --mem (md)0x800+4 (99)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP.iso;\n\0
chainloader (hd0)+1

The HDD for the installation was NOT connected via USB, because my mobo ( GA-P35DS3R rev. 1.0 ) only boots from USB in 1.1 mode and "Plops" USB driver did not work for me. Instead, the installation HDD was connected to the 4. S-ATA Port of the ICH9R, and the target HDD was on the 1. S-ATA port. Then I booted the installation HDD via the boot menu of the bios, which explains the mappings I needed in the winsetup.lst . I never installed a Windows XP so fast, even it could have been faster, since the installation HDD was only a 2,5" drive with 5400 rpm, which normally belongs into an external USB enclosure. Of course this method should work the same way if the installation HDD would have been booted through USB, but I did not test this since it would have been painfully slow with my mobo.

C.U. Picobot

Edited by PicoBot
0

Share this post


Link to post
Share on other sites

Hello!

Has everyone tryed to install the way described here with winnt.sif inside?

If i put winnt.sif in i386, just after format, when it starts to copy files, i get copy error for all files in winvblock.ima.

Without winnt.sif, everything is ok.

Any ideas?

0

Share this post


Link to post
Share on other sites

OemPreinstall=Yes in Unattended section of winnt.sif was the problem.

Set it to No or delete the entry.

Thank you for this topic! :thumbup

0

Share this post


Link to post
Share on other sites

OemPreinstall=Yes in Unattended section of winnt.sif was the problem.

Set it to No or delete the entry.

Thank you for this topic! :thumbup

And thank you for this hint. :thumbup You just solved the problem I had with one of my ISO installation.

0

Share this post


Link to post
Share on other sites

Little late to the game. XP only has two years left which in a way is kinda still a long time. I have been installing XP one way that I like from DVD for years until I realized how much we spend on DVD every year, anyway I have been trying all the old (new methods to me) methods to install XP. Winsetupfromusb which is great(my personal favorite), loading ISO into ram which works but not so good on low ram machines. I have a method that I worked out with Firadisk that works perfect even on low ram machines and only requires booting to USB once (my second favorite) so I though I would give this method a try. I am losing the WinVBlock driver at GUI and I know this is covered allot on here but let me tell you what I got

Using XP Home as example

XP Home SP3....updates slipstream with RyanVM tool

DriverPacks...all the latest

Using Winnt.sif

I added this to my presetup.cmd as described by, cdob

:DPsFound

start /b "Open handle to virtual CD-ROM drive." pushd "%CDDRIVE%"

and I am using what I assume to be the newest WinVBlock from ilko_t post here

This is my menu.lst (test purpose only)

title XP SP3 Home install 
find --set-root /laddsbootusb.tag
map --unmap=0:0xff
map --unhook
map --mem /XP/Floppy/winvblk.ima (fd0)
map --mem /XP/Floppy/winvblk.ima (fd1)
map /XP/ISO/HOME.ISO (0xFF)
pause
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
chainloader (0xFF)/I386/SETUPLDR.BIN

Everything seems to load fine in TextSetup Mode, if I hit f6, WinVBlock is there in the choices(I just hit f6 the one time to make sure my menu.lst mapped the ima file) I get pass the normal BSOD and I am able to format and copy files...computer reboots and DriverPacks start and when DP is done...get the error about the Path and can't find CD drive

The editing of the presetup.cmd seems to be the trick for, wimb

I am not booting to USB but once because I thought the presetup.cmd trick would eliminate the second part of install as listed below?

title 2 Continue Windows XP setup
map /winvblock.IMA (fd0)
map /winvblock.ima (fd1)
map /Inst/XP_RAM.ISO (0xff)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
chainloader (hd0)+1

Edited by laddanator
0

Share this post


Link to post
Share on other sites
Winsetupfromusb which is great
I like this too.
loading ISO into ram which works but not so good on low ram machines.
Did you tried the sorted ISO file? Haven't used this in conjunction with RyanVM updates.
I am losing the WinVBlock driver at GUI
Technically you don't loose the WinVBlock driver.

Underling USB connection is installed. The existing USB connection is lost and a new one builded.

This part kills connection to WinVBlock driver.

I am not booting to USB but once because I thought the presetup.cmd trick would eliminate the second part of install as listed below?
No, second USB boot is required still.
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.