Jump to content











Photo
- - - - -

Install WinXP to dummy.img file with WinVBlock + Grub4dos


  • Please log in to reply
4 replies to this topic

#1 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 287 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, UEFI, Coreboot, MS VirtualPC, VMware
  •  
    Poland

Posted 13 April 2014 - 01:43 PM

Hi. I try install WinXP to dummy.img with WinVBlock F6 driver. I make tests in virtual machine MS VirtualPC 2007 on 5GB.vhd

 

Contents 5GB.vhd:

 

- grub4dos installed and files grldr + menu.lst

- dummy.img 1500MB (active, primary partition fat16 formated)

- xp.iso (SP2)

- winvblock.ima for F6 (http://www.rmprepusb...?attredirects=0)

 

Virtual Machine is run on host WinXP SP2 2.99GB RAM (RAM size vm is 2GB)

 

After first boot Windows Setup see both disk - real 5GB and dummy.img 1,5GB

5174842m.png

 

but after press F6 and select WinVBlock driver have error copy wvblk32.sys:

5160506m.png

 

menu.lst content:

#serial --unit=0 --speed=19200

#terminal --timeout=5 serial console

timeout 5

default 0



map /dummy.img (hd0)



map --mem /WinVBlock.IMG (fd0)



map --mem /xp.iso (0xff)



map --hook







chainloader (0xff)/I386/SETUPLDR.BIN

P.S. After next boot Windows Setup not see dummy.img :-( Until fresh copy dummy.img file to VHD disk this is identified while Windows Setup.


Edited by reboot12, 13 April 2014 - 01:54 PM.


#2 cdob

cdob

    Gold Member

  • Expert
  • 1469 posts

Posted 13 April 2014 - 07:31 PM

Compare
http://reboot.pro/to...-12#entry119816
http://reboot.pro/to...d-drive-letter/
http://reboot.pro/to...e-2#entry137793

Set Winvblock parameter relating you image file
write (0x55) #!GRUB4DOS\x00v=1\x00dummy.img\x00\x80\x00

Do not press F6, XP loads the driver anyway.

#3 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 287 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, UEFI, Coreboot, MS VirtualPC, VMware
  •  
    Poland

Posted 13 April 2014 - 09:18 PM

OK, thx. Now I found other solution :-)

  • integrate wvblk32.sys (compressed WVBLK32.SY_) to xp.iso image + modified txtsetup.sif http://cytaty.blogsp...stallation.html
  • boot from menu 1 - TXT Setup
  • boot from menu 2 - Continued GUI Setup
  • boot from menu 3 - normal boot WinXP from IMG (without mapped ISO image)

menu.lst content:

title Instalacja WinXP z ISO w obrazie IMG - Faza I TXT-Setup
map /dummy.img (hd0)
map --mem /xp.iso (0xff)
map --hook
chainloader (0xff)/I386/SETUPLDR.BIN

title Instalacja WinXP z ISO w obrazie IMG - Faza II GUI-Setup
map /dummy.img (hd0)
map --mem /xp.iso (0xff)
map --hook
root (hd0,0)
chainloader /ntldr

title Uruchom WinXP z obrazu IMG
find --set-root --ignore-floppies /dummy.img
map /dummy.img (hd0)
map --hook
root (hd0,0)
chainloader /ntldr

P.S. WinXP boot until second boot and possible make changes (write enable). Image location is HASH:

5213581.png

 

For next boot I need add --mem option for load dummy.img to RAM but this make image read only:

map --mem /dummy.img (hd0)

Now image location is RAM:

5224845.png


Edited by reboot12, 13 April 2014 - 09:38 PM.


#4 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 287 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, UEFI, Coreboot, MS VirtualPC, VMware
  •  
    Poland

Posted 15 April 2014 - 04:06 PM

While first tests I use 5GB VHD FAT32 formatted partition and after some restarts WinXP crash with BSOD PFN_LIST_CORRUPT To boot OS properly I had use --mem option.

 

Now I make new tests but use new smaller VHD 4GB NTFS formated and WinXP boot OK without --mem option :-). Probably NTFS is better to store IMG disk image for GRUB4DOS map.

P.S. WinXP file system in IMG file is FAT16 :-)

5205121m.png 5183617m.png


Edited by reboot12, 15 April 2014 - 04:11 PM.


#5 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 287 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, UEFI, Coreboot, MS VirtualPC, VMware
  •  
    Poland

Posted 02 November 2014 - 04:23 AM

Of course, > here < is the solution to the problem. ;)






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users