Jump to content











Photo
- - - - -

Install WinXP from ISO image using WinVBlock


  • Please log in to reply
20 replies to this topic

#1 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 12 May 2014 - 06:57 AM

I recently tried to install WinXP from ISO image to RAW disk image -> link and there were no problems. Now I'm trying install WinXP from ISO image D:\xp.iso to real HDD partition primary NTFS C:. The system is installed but without last stage Window Welcome (network settings, user account, Firewall etc.). Installation of doing in this way:

  • on HDD have 2 partition NTFS C: and D:
  • on D: (hd0,4) have xp.iso copied
  • in first and second phase run GRUB4DOS over network (boot PC with BIOS boot agent (e.g. gPXE) to PXELINUX -> grldr + menu.lst/default)
    default 0
    timeout 5
    
    title TXT-Setup WinXP - phase 1
    map --mem (hd0,4)/xp.iso (0xff)
    map --hook
    chainloader (0xff)/I386/SETUPLDR.BIN
    
    title GUI-Setup WinXP - phase 2
    map --mem (hd0,4)/xp.iso (0xff)
    map --hook
    root (hd0,0)
    chainloader /ntldr
  • WinXP install very fast :-) but without last stage Window Welcome :-( and after normal boot from HDD lacks many components e.g. Luna style, no LAN connection in Control Panel !!!

Why Windows is installed in this way? I use the same image xp.iso (WinVBlock nLite integrated) that I use when installing to RAW image.

P.S. In Device Manager have WinVBlock RAID controller twice :dubbio:


Edited by reboot12, 12 May 2014 - 06:59 AM.


#2 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 17 May 2014 - 08:45 AM

Integrated driver WinVBlock to xp.iso manually but the WinXP is still installed without the "Welcome" screen :-(. The driver added in the manner described in this tutorial -> Windows XP - Installing to SATA _WITHOUT_ a Floppy Disk <- Integration done without .CAT file, and thus the installer display window "WinVBlock Bus WVBlk32 - has not passed Windows Logo testing...).

5447357m.png

The window is displayed in two different moments of the second phase (GUI-Setup) of the installation. This means that the WinVBlock driver is installed 2 times. After the first installation everything is OK but after second installer displays a message box to insert the installation CD :confused1: . After boot GUI-Setup installer xp.iso mapped with GRUB4DOS have E: letter but after second install driver WinVBlock something is wrong and E: location is not available. In setupact.log have this:

Volume: E:\

Device Path: \\?\winvblock#ramopticaldisc#1&c0ac9c8&0&ram_at_5b54e000#{53f56308-b6bf-11d0-94f2-00a0c91efb8b}

1. WinVBlock Disk - \Device\0000002b
   HardwareId:
     WinVBlock\RAMOpticalDisc
     GenCdRomWinVBlock\RAMOpticalDisc
   Location: RAM_at_5B54E000
PhysicalDeviceObjectName: \Device\0000000b
   HardwareId:

and after second driver install:

Zewnętrzny program RUNDLL32 shell32,Control_RunDLL intl.cpl,,/R /s:"E:\I386" zwrócił kod błędu równy 0.
NetSetup: Stan funkcji InitFromAnswerFile: 0x0

5504700m.png 5492412m.png

After Cancel installation some files cmprops, IEXPLORE WinXP Setup ends but without window "Welcome" because some components is missing. In Device Manager have WinVBlock driver twice:

5497535m.png


How to disable the driver installation for the second time?

 


Edited by reboot12, 17 May 2014 - 09:03 AM.


#3 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 17 May 2014 - 09:27 AM

Try NOT integrating the Winvblock driver and use the floppy image.

I.e. read and follow this:
http://www.msfn.org/...rom-a-iso-file/

You may want to try opening a handle to the (virtual) CDROM to avoid the second install:

http://www.msfn.org/...-file/?p=956987

Or try (alternatively) Firadisk.

If I get this right you are using a non-local (via PXE) iso image, it is possible that this introduces a variation that needs a specific change.

 

:duff:

Wonko



#4 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 17 May 2014 - 11:17 AM

Try NOT integrating the Winvblock driver and use the floppy image.

I do not want to use the floppy image, I want to use an ISO image of the integrated WinVBlock driver such as SATA.
 

Or try (alternatively) Firadisk.
If I get this right you are using a non-local (via PXE) iso image, it is possible that this introduces a variation that needs a specific change.

I do not want to use the firadisk driver. Via PXE boot use only GRUB4DOS (boot file grldr in TFTP server), xp.iso is located on local harddisk, partition NTFS D:. Yes my xp.iso have file WINNT.SIF with some settings for semi-automatic installation but this xp.iso work OK if try install from RAM-ISO to mapped RAW disk image.
 
In summary:
  • For install WinXP from RAM-ISO to dummy.img need WinVBlock driver for xp.iso and for dummy.img - no any problems with installation
  • For install WinXP from RAM-ISO to HDD need WinVBlock driver only for xp.iso - have problem with installation
I do not understand why access to E: is lost 29 minutes into of installation:
5448391m.png

Edited by reboot12, 17 May 2014 - 11:53 AM.


#5 cdob

cdob

    Gold Member

  • Expert
  • 1342 posts

Posted 17 May 2014 - 12:04 PM

For install WinXP from RAM-ISO to HDD need WinVBlock driver only for xp.iso - have problem with installation

Why do you PNP the winvblk driver? The driver is active already.

Either do not PNP the winvblk driver at GUI mode:
press shift F10 and delete the winvblk inf file.

Or open a handle at GUI modefirst:
press shift F10 and change directory to winvblock CD drive letter.

#6 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 17 May 2014 - 12:25 PM

I do not want to .... 

....
I do not want to ....

....

 

 

Good :).

The character in literature for today is ....

Bartleby, the Scrivener :w00t:, by Herman Melville :thumbsup::

http://en.wikipedia....,_the_Scrivener

I would prefer not to ...

 

 

 

 

Go try helping people .....  :(

 

:duff:

Wonko



#7 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 17 May 2014 - 01:45 PM

Why do you PNP the winvblk driver? The driver is active already.

Yes, right, winvblk driver is active already.
 

Either do not PNP the winvblk driver at GUI mode:
press shift F10 and delete the winvblk inf file.

I did a test with an ISO image from MSDN - only add some lines to TXTSETUP.SIF (like this) & WVBLK32.SY_ (CAB compressed) to I386 folder. ISO file does not contain any WinVBlock.INF file.

Lost connection to E: drive still occurs.
 

Or open a handle at GUI modefirst:
press shift F10 and change directory to winvblock CD drive letter.

If try select drive E: then have error: "E: is not available"



#8 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 17 May 2014 - 07:28 PM

OK,  I found how to get around the problem :-). For testing I use a MS VPC 2007 virtual machine but this machine have no possible remove CD-ROM drive in settings. Now I tried VMware Workstation 8 - this one allows remove CD-ROM drive in settings :-)

If no CD-ROM drive present then WinXP install from RAM-ISO to HDD working OK :good:  :happy_dance3:

5471746.png

P.S. If CD-ROM is present in VMware have also the same problem. This means that here is some problem CD-ROM drive with xp.iso mapped to RAM with GRUB4DOS.

 

Interesting that when installing WinXP to dummy.img problem does not occur even in the presence of the CD-ROM drive.


Edited by reboot12, 17 May 2014 - 07:39 PM.


#9 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 18 May 2014 - 05:15 AM

This is a known problem -> Disappearing memory mapped ISO drive with winvblock - XP setup
 
Probably has to do with GRUB4DOS. I found also this:

So the BIOS is not a problem because it works with correct hardware and it manages to work with inconsistent hardware. Windows, same answer. Linux, same answer. Grub4dos gets confused when the PC's wiring says master and the drive's wiring says slave.



#10 memoarfaa

memoarfaa

    Member

  • Members
  • 81 posts
  •  
    Egypt

Posted 18 May 2014 - 08:44 AM

OK,  I found how to get around the problem :-). For testing I use a MS VPC 2007 virtual machine but this machine have no possible remove CD-ROM drive in settings. Now I tried VMware Workstation 8 - this one allows remove CD-ROM drive in settings :-)

If no CD-ROM drive present then WinXP install from RAM-ISO to HDD working OK :good:  :happy_dance3:

5471746.png

P.S. If CD-ROM is present in VMware have also the same problem. This means that here is some problem CD-ROM drive with xp.iso mapped to RAM with GRUB4DOS.

 

Interesting that when installing WinXP to dummy.img problem does not occur even in the presence of the CD-ROM drive.

 

 

Hi reboot 12 

At first Thanks to 

1- grub4dos developers

2- MSFN and reboot.pro Members and developers

to speed there time and effort to developing setup windows from grub4dos ramdisk

 

I have good experience of integrated grub4dos driver in to xp iso 

I believe that is not bug in grub4dos but the wrong way to integrate WinVBlock in to XP.iso

You are appear going to the wrong way 

As the image you uploaded in firast of this topic for the problem 

the installation stop of coping Cmprops.dll

Cmprops.dll may stop the installation because of security point via PXE or setup from hdd 

 

show microsoft description here

http://support.microsoft.com/kb/818464

http://support.microsoft.com/kb/816119

 

you must specify security description of unsigned digital signature  of WinVBlock catalog to the installation

 

1- add security to offline installation hive SETUPREG.HIV

 

show method of fiaradisk here 

 

http://reboot.pro/to...130/#entry75640

 

Injected driver to offline Windows install loaded SETUPREG.HIV as SYSTEM.SAV

 

path to 

HKEY_LOCAL_MACHINE\SYSTEM.SAV\ControlSet001\Services\WinVBlock\Security

and hex to WinVBlock catalog

2- you are already use UnattendMode mode with winnt.sif 

 

add this to avoid  unsigned digital signatures

DriverSigningPolicy=Ignore

NonDriverSigningPolicy=Ignore 

3- give me the result 

if you want to stop install of WinVBlock in gui mod I will give you the solution 



#11 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 18 May 2014 - 01:17 PM

As the image you uploaded in firast of this topic for the problem 

the installation stop of coping Cmprops.dll

Cmprops.dll may stop the installation because of security point via PXE or setup from hdd

Yes, but only when use ISO with drivers integrated like in this tutorial: Windows XP - Installing to SATA _WITHOUT_ a Floppy Disk

1. TXTSETUP.SIF + WVBLK32.SY_

2. $OEM$/$1/Drivers (.sys, .inf, .exe, .cat, .oem)

 

Now i test xp.iso with only TXTSETUP.SIF + WVBLK32.SY_ with disabled CD-ROM drive in VMware settings. This driver is need for WinXP Setup for use RAM-ISO mapped. No need any other way integrated additional drivers. After WinXP end install in Device Manager is Unknown Device but this can resolved with Update Driver manually (ROOT\WVBLK32\0000) and Uninstall Unknown Device (ROOT\WVBLK32\0001):

5496417m.png

WinXP is now installed on HDD and not need use WinVBlock driver for work.


Edited by reboot12, 18 May 2014 - 01:18 PM.


#12 cdob

cdob

    Gold Member

  • Expert
  • 1342 posts

Posted 19 May 2014 - 03:18 PM

I use the same image xp.iso (WinVBlock nLite integrated) that I use when installing to RAW image.
P.S. In Device Manager have WinVBlock RAID controller twice :dubbio:

Nlitea and existing files get strange results.
Try intetrage winvblock drivers yourself.

txtsetup.sif
[SourceDisksFiles.x86]
WVBlk32.sys = 1,,,,,,,,3,3
WinVBlk.INF = 1,,,,,,,20,0,0

[HardwareIdsDatabase]
;same name
ROOT\WVBlk32 = "WVBlk32"
Detected\WVBlk32 = "WVBlk32"

;ROOT\WINVBLOCK = "WVBlk32"
;Detected\WinVBlock = "WVBlk32"

[SCSI.Load]
WVBlk32 = WVBlk32.sys,4

[SCSI]
WVBlk32  = "WinVBlock"
WinVBlk.INF
[Version]
Signature="$Windows NT$"
Class=SCSIAdapter
ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
Provider=WinVBlock
DriverVer=05/16/2010,0.0.0.8

;winvblock driver included to txtsetup.sif
;--> no copy driver files
 
[Manufacturer]
WinVBlock=WinVBlockDriver,,NTamd64
  
[WinVBlockDriver]
"WinVBlock Driver"=WinVBlock,Root\WinVBlock, Detected\WinVBlock
"WinVBlock Bus WVBlk32"=WVBlk32,DETECTEDInternal\WVBlk32, Detected\WVBlk32
 
[WinVBlockDriver.NTamd64]
"WinVBlock Driver"=WinVBlock.NTamd64,Root\WinVBlock, Detected\WinVBlock
 
[WVBlk32]
AddReg=DisablePrefetcher

[DisablePrefetcher]
HKLM,"System\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters",EnablePrefetcher,0x00010001,0x1
HKLM,"System\CurrentControlSet\Control\CrashControl",AutoReboot,0x00010001,0x0

[WVBlk32.Services]
AddService=WVBlk32,0x00000002,Service

[WinVBlock]
CopyFiles=Files.Driver,Files.Tools
 
[WinVBlock.NTamd64]
CopyFiles=Files.Driver.NTamd64,Files.Tools
 
[WinVBlock.Services]
AddService=WinVBlock,0x00000002,Service
 
[WinVBlock.NTamd64.Services]
AddService=WinVBlock,0x00000002,Service.NTamd64
 
[Service]
ServiceType=0x00000001
StartType=0x00000000
ErrorControl=0x00000001
ServiceBinary=%12%\wvblk32.sys
 
[Service.NTamd64]
ServiceType=0x00000001
StartType=0x00000000
ErrorControl=0x00000001
ServiceBinary=%12%\wvblk64.sys
RAM ISO installation works at VMware Player here, additional CD drive is available.
Device Manager have WinVBlock RAID controller once.

#13 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 19 May 2014 - 05:46 PM

I tried your files but in 29 min. still E: drive not available. WinVBlock driver install twice at 35 min & 33 min

5557553m.png 5552433m.png 5539121m.png

I copied WVBLK32.SY_ and WINVBLK.IN_ to I386 folder.

 

I think that it is not a matter of settings in the INF file because the WinVBlock driver is not required to operate the system. This is only need for install from RAM-ISO.

 

I remind that I want to install WinXP on disk, not in the image IMG on the disk, when driver is required for ISO mapped to RAM and for dummy.img mapped.


Edited by reboot12, 19 May 2014 - 06:03 PM.


#14 cdob

cdob

    Gold Member

  • Expert
  • 1342 posts

Posted 19 May 2014 - 06:12 PM

Add winnt.sif and disable driver signing requirement.
http://www.msfn.org/...signed-drivers/

Which file is seeked at third picture?
 

I remind that I want to install WinXP on disk, not in the image IMG on the disk, when driver is required for ISO mapped to RAM and for dummy.img mapped

What about one XP ISO to use at both cases?
ISO mapped to RAM and for dummy.img mapped
  • memoarfaa likes this

#15 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 24 May 2014 - 11:24 AM

I make new test with the same xp.iso on MS VirtualPC 2007 (real CD-ROM + FDD emulation). To install WinXP with the ISO image to disk i need map any virtual floppy disk image e.g. Win95boot (fdd.img) to RAM in both Windows Setup phases. This is my menu.lst for install OS from D: to C:
title TXT-Setup WinXP - phase 1\n RAM-ISO to HDD
map --mem (hd0,4)/fdd.img (fd0)
map --mem (hd0,4)/xp.iso (0xff)
map --hook
chainloader (0xff)/I386/SETUPLDR.BIN

title GUI-Setup WinXP - phase 2\n RAM-ISO to HDD
map --mem (hd0,4)/fdd.img (fd0)
map --mem (hd0,4)/xp.iso (0xff)
map --hook
root (hd0,0)
chainloader /ntldr

Edited by reboot12, 14 July 2015 - 08:31 PM.


#16 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 29 May 2014 - 08:09 PM

Because I run GRUB4DOS from a PXE server on which I have a floppy image and memdisk just one menu to install the system:

title Install WinXP from RAM-ISO
# map floppy image to RAM over PXE
map --mem (pd)/images/fddwin95.ima (fd0)
# map ISO image to RAM from partition D:
kernel /memdisk raw iso
initrd (hd0,4)/xp.iso
boot

MEMDISK is better for use because Windows Setup displays Press any key to boot from CD.. and to install WinXP SP2 need boot PC twice from the same menu GRUB4DOS. During first boot PC need press any key to boot from CD and during the second boot time, do not press any key to boot from HDD :-)

 

No need for separate menu (phase I & II) for install WinXP SP2 (of course if in BIOS is set boot order 1. CDROM 2. HardDisk)

 

P.S. How Press any key to boot from CD work please read this thread.


Edited by reboot12, 29 May 2014 - 08:40 PM.


#17 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 30 May 2014 - 08:48 AM

 

MEMDISK is better for use because Windows Setup displays Press any key to boot from CD..

Well, no.

I mean, if instead of directly chainloading the loader bypassing the .iso bootsector:



chainloader (0xff)/I386/SETUPLDR.BIN

you chainload the bootsector (which is what memdisk does)



chainloader (0xff)

you should have the Press any key to boot from CD..  alright.

 

:duff:

Wonko



#18 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 30 May 2014 - 05:17 PM

chainloader (0xff)

you should have the Press any key to boot from CD..  alright.

Yes, you right. Instead memdisk you can use Grub4dos and chainloader (0xff)

title Install WinXP from RAM-ISO
# map floppy image to RAM over PXE
map --mem (pd)/images/fddwin95.ima (fd0)
# map ISO image to RAM from partition D:
map --mem (hd0,4)/xp.iso (0xff)
map --hook
chainloader (0xff)

Edited by reboot12, 30 May 2014 - 05:17 PM.


#19 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 24 June 2014 - 01:49 PM

I try new test with GRUB4DOS 0.4.5c (pd) device + WinVBlock + Tiny PXE Server + iPXE. To install WinXP one can use (pd) device instead (hd) - xp_winvblock.iso maps within about 1 minute on MS VPC 2007 :-). This is menu on PXELINUX server:
title TXT-Setup WinXP - phase 1\n (pd) RAM-ISO to HDD
map --mem (pd)/images/fddwin95.ima (fd0)
map --mem (pd)/images/xp_winvblock.iso (0xff)
map --hook
chainloader (0xff)/I386/SETUPLDR.BIN

title GUI-Setup WinXP - phase 2\n (pd) RAM-ISO to HDD
map --mem (pd)/images/fddwin95.ima (fd0)
map --mem (pd)/images/xp_winvblock.iso (0xff)
map --hook
root (hd0,0)
chainloader /ntldr
Demo video - WinVBlock_XP
Note1: You can also use gPXE instead iPXE ;-)
Note2: The built-in MS VPC 2007 Argon PXE boot agent work but very, very slow.

Edited by reboot12, 14 July 2015 - 08:32 PM.


#20 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 25 June 2014 - 02:06 AM

Yay!

#21 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 26 June 2014 - 11:01 AM

Mapping ISO image over (pd) device with GRUB4DOS uses TFTP protocol. Unfortunately on real machines this is very slow and not stable. The best way to load ISO is use HTTP protocol over PXELINUX while PC boot from iPXE with script to set 210 & 209 DHCP options. To use this installation method, you must first map a floppy image using GRUB4DOS.

script.ipxe to set HTTP protocol for PXELINUX:

#!ipxe

dhcp
set 209:string pxelinux.cfg/default
set 210:string http://${dhcp-server}/
prompt --key 0x02 --timeout 2000 Press Ctrl-B for the iPXE command line... && shell ||
chain ${210:string}pxelinux.0

To install WinXP from ISO mapped over HTTP with memdisk you need:

  • boot PC from iPXE with script.ipxe
  • run GRUB4DOS from PXE server, map any floppy image to RAM, keep pxe and back to PXELINUX

    menu PXELINUX 1:
    LABEL g4d
    MENU LABEL GRUB4DOS over PXELINUX
    boot grldr pxe detect
    menu GRUB4DOS:
    title Map floppy image and back to PXELINUX\n This is for use memdisk xp_winvblock.iso over HTTP from PXELINUX
    map --mem (pd)/images/fddwin95.ima (fd0)
    map --hook
    pxe keep
    chainloader --force --raw (pd)/pxelinux.0
    
    menu PXELINUX 2:
    LABEL xpmem
    MENU LABEL Map xp_winvblock.iso with memdisk and boot
    TEXT HELP
          !!! Map the first with GRUB4DOS any floppy image !!!
          Please use this menu for TXT & GUI WinXP Setup phases
          Phase I - autoboot or press any key to boot from CD
          Phase II - no press any key to boot from HDD
    ENDTEXT
    kernel memdisk iso raw
    initrd /images/xp_winvblock.iso
  • boot PC twice from the all menus for TXT & GUI WinXP Setup

Note1: MEMDISK display error Failed to free base memory but WinXP Setup works OK :-)

Note2: MEMDISK maps the ISO image in about 1:20 min over Ethernet 100 with HTTP protocol

 

WinXP see both images: GRUB4DOS mapped floppy image and memdisk mapped ISO image:

5841853m.png

 

Demo video - memdisk xp


Edited by reboot12, 26 June 2014 - 11:05 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users