Jump to content











Photo
* * * * - 3 votes

WinVBlock


  • Please log in to reply
609 replies to this topic

#601 reboot12

reboot12

    Frequent Member

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

Posted 17 March 2016 - 07:23 AM

I do not use driver aoe32.sys of Sha0 but I tested the driver AoE 0.97g from winaoe.org and this driver does not work with TXT WinXP Setup.
 
But I was able to integrate all drivers iSCSI, AoE and WinVBlock to ISO image so that after installation are all available in Device Manager - please read this post: WinXP AOE boot problem with new hardware
 
In addition, the more stable is old WinVBlock 0.0.1.8 without direct map support ISO images - fix_inf_winvblock_0.0.1.8_(june-1-2010)_no_direct_map.zip


  • wimb likes this

#602 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 17 March 2016 - 08:39 AM

reboot12, on 17 Mar 2016 - 08:23 AM, said:
In addition, the more stable is old WinVBlock 0.0.1.8 without direct map support ISO images - fix_inf_winvblock_0.0.1.8_(june-1-2010)_no_direct_map.zip

This one, right?
http://reboot.pro/to...block/?p=193676
http://reboot.pro/to...block/?p=193748

:duff:
Wonko

#603 mr_jrt

mr_jrt

    Member

  • Members
  • 32 posts
  •  
    United Kingdom

Posted 19 March 2016 - 04:45 PM

I do not use driver aoe32.sys of Sha0 but I tested the driver AoE 0.97g from winaoe.org and this driver does not work with TXT WinXP Setup.

 

Indeed, I tried that as well, and it didn't show up in text mode.



#604 mr_jrt

mr_jrt

    Member

  • Members
  • 32 posts
  •  
    United Kingdom

Posted 20 March 2016 - 03:08 AM

Well, good news. I've managed to get, tweak, and build the code and get a working driver using a newer version of the Windows Driver Devkit. I tried using the latest code but that fails to even handle the memdisk, let alone the AoE disk (or indeed, direct mapping), so as suspected I'll have to try cherry-picking changes from the unreleased work to see if I can get direct-mapped disks working without breaking everything else. :)


Edited by mr_jrt, 20 March 2016 - 03:08 AM.


#605 mr_jrt

mr_jrt

    Member

  • Members
  • 32 posts
  •  
    United Kingdom

Posted 21 March 2016 - 01:01 AM

Hmm. Still no joy.
 
I've got kernel logs of installing XP successfully with iSCSI: http://pastebin.com/SUETWpxP
..and unsuccessfully with AoE: http://pastebin.com/0sbDT27p
 
Just doesn't seem to contact the AoE target when booting from it in GUI mode...

Text mode:
Successfully identified aBFT NIC
No sBFT found
Attempting SAN boot; will wait for system disk
iBFT requested
No iBFT available!
Waiting for SAN system disk (attempt 1)
  System disk is <unknown>, boot disk is <unknown>
  MBR f9e4bcb6: "\??\WinVBlock#AoEHardDisk#1&c0ac9c8&0&AoE_at_Shelf_0.Slot_0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Found system disk at "\??\WinVBlock#AoEHardDisk#1&c0ac9c8&0&AoE_at_Shelf_0.Slot_0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"
Found SAN system disk; proceeding with boot
GUI mode:
Successfully identified aBFT NIC
No sBFT found
Attempting SAN boot; will wait for system disk
iBFT requested
No iBFT available!
Waiting for SAN system disk (attempt 1)
  System disk is <unknown>, boot disk is <unknown>
Waiting for SAN system disk (attempt 2)
  System disk is <unknown>, boot disk is <unknown>
Waiting for SAN system disk (attempt 3)
...etc
Comparing it against the successful text mode boot (and the successful GUI mode iSCSI boot) I can't see anything obvious, so I guess I'll have to add more logging in. :(

Edited by mr_jrt, 21 March 2016 - 01:03 AM.


#606 mr_jrt

mr_jrt

    Member

  • Members
  • 32 posts
  •  
    United Kingdom

Posted 22 March 2016 - 11:08 PM

Gaah! I was being stupid. The two reasons it wasn't even being loaded was:

i) Because I thoughtlessly inserted it into a non-sticky section ([CdRomDrivers.Load], incidentally) along with the iScsiPrt driver. The integratedrv utility does this to control load ordering, but adds in the required service keys manually for GUI mode to work:
HKLM,"SYSTEM\CurrentControlSet\Services\iScsiPrt\Parameters","BusType",0x00010001,9
HKLM,"SYSTEM\CurrentControlSet\Services\iScsiPrt","DisplayName",0x00000000,"iScsiPort Driver"
HKLM,"SYSTEM\CurrentControlSet\Services\iScsiPrt","ErrorControl",0x00010001,1
HKLM,"SYSTEM\CurrentControlSet\Services\iScsiPrt","Start",0x00010001,0
HKLM,"SYSTEM\CurrentControlSet\Services\iScsiPrt","Type",0x00010001,1
HKLM,"SYSTEM\CurrentControlSet\Services\iScsiPrt","ImagePath",0x00000000,"system32\drivers\msiscsi.sys"
and ii) ...even once moved into a "sticky" section, the proto-service entries in the proto-registry don't specify the driver filename, i.e. these entries: 
[SCSI.Load]
wvblk32 = wvblk32.sys,4
AoE     = aoe32.sys,4
...will create the following registry values:
HKLM,"SYSTEM\CurrentControlSet\Services\wvblk32","ErrorControl",0x00010001,1
HKLM,"SYSTEM\CurrentControlSet\Services\wvblk32","Group",0x00000000,"SCSI miniport"
HKLM,"SYSTEM\CurrentControlSet\Services\wvblk32","Start",0x00010001,0
HKLM,"SYSTEM\CurrentControlSet\Services\wvblk32","Type",0x00010001,1

HKLM,"SYSTEM\CurrentControlSet\Services\AoE","ErrorControl",0x00010001,1
HKLM,"SYSTEM\CurrentControlSet\Services\AoE","Group",0x00000000,"SCSI miniport"
HKLM,"SYSTEM\CurrentControlSet\Services\AoE","Start",0x00010001,0
HKLM,"SYSTEM\CurrentControlSet\Services\AoE","Type",0x00010001,1
You should note that there is no "image path" value to the .sys driver yet. Windows will look for a driver in system32\drivers with a filename that matches, meaning that the filenames would need to be "wvblk32.sys" and "aoe.sys". My next problem came from the fact the filename as built by the project's build is aoe32.sys, meaning the driver will not get loaded once GUI mode starts, but will load fine in text mode from txtsetup.sif. It's old information, but easily forgotten if you're not careful.

With those two issues resolved, it's actually loading, abet still crashing. But at least it's loading!

Finally, I also want to take a moment to congratulate Sha0 and the original author of WinAOE - the debug tracing in the code base is absolutely top-notch.

#607 mr_jrt

mr_jrt

    Member

  • Members
  • 32 posts
  •  
    United Kingdom

Posted 23 March 2016 - 01:25 AM

...and success, we have a winner. Just installed XP completely over WinVBlock's AoE from start to finish, both text and GUI modes.

Now to get direct mapping working with this older version... :)

#608 baselsayeh

baselsayeh
  • Members
  • 6 posts

Posted 09 August 2016 - 09:36 PM

Hello

@sha0

I think that i found a bug in your driver.

Tried to install windows vista in vhd using winvblock [56fb4f1438f0cdb2652de24ccff06737248dd942 from github] by wimb without any success.

Applied the vista wim file and rebooted from the vhd.

It would fail without any log file is written to disk.

Then i tried to install windows vista in virtual box and then install winvblock and boot the machines vhd in my real laptop

it worked but it doesn't want  to save any change to the vdh file

Each restart it would install my laptop drivers

but with firadisk everything works fine.



#609 tinybit

tinybit

    Gold Member

  • Developer
  • 1051 posts
  •  
    China

Posted 27 December 2016 - 03:41 AM

Some people encountered a problem(Blue STOP:07B) with WinVBlock(reported at somewhere in a Chinese site - bbs.wuyou.net). It seems the driver does not support memory blocks at above 4GB. Can anyone confirm it? Note that It is OK loading IMGs at blocks below 4GB. So I guess WinVBlock does not support blocks above memory address of 4GB.



#610 Biatu

Biatu

    Member

  • Members
  • 50 posts
  •  
    United Kingdom

Posted 14 January 2017 - 05:21 AM

This would be a very useful utility in linux. Create G4D ramdisk, Boot Linux, format ramdisk, do stuff, kexec into bootmgr/syslinux/grub, boot WinPE. Would work wonders for persay...PlopKexec. we could use LZMA/LZMS conpression in WIM, boot.


Edited by Biatu, 14 January 2017 - 05:22 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users