WinVBlock

But my version files .inf and .oem is better because have some fixes:

Well, but (unless I am missing something) nothing prevents from mixing the best of both, if someone really wants to use nlite or fix the other minor issues.

The (nice ) betterings you did to those two files do NOT anyway allow you to insist (again) on advising the use of a less-featured version of the driver, but much more than that deceive a new user with incorrect statements related only to the specific version of the driver you use as if they were an universal truth.

 

Of course you are perfectly free to consider yourself the ultimate expert of Winvblock, and propagate whatever (possibly inaccurate) information you believe into, but you have to be prepared to the possibility of receiving some critics by other members when this information is considered to be actually inaccurate.

 

Wonko

Of course you are perfectly free to consider yourself the ultimate expert of Winvblock, and propagate whatever (possibly inaccurate) information you believe into, but you have to be prepared to the possibility of receiving some critics by other members when this information is considered to be actually inaccurate.

Yes, but believe me, WinVBlock testing is difficult and time consuming. I use the method of trial and error, and I think that each of my information is precious. Today I tested the new driver WinVBlock 0.0.1.8-DEV (Feb-14-2011) and during the installation of WinXP system lost access to a virtual optical drive (xp.iso (0xff)):
 loss_access_ISO.png   111.42KB   0 downloads
The old version I tested many times in virtual machines, and in real computers. I think that the old version (0.0.1.8 (June-1-2010)), which was officially released by Sha0 at this topic on page 9 is more stable than later and my information about this version are very accurate.
Only a test gives the best information about operation of driver, and not heard opinions and inserting links to guides.

Well, you are then again in the stance that what wim_b and Steve6375 (besides other much respected and experienced people) wrote (and that countless people have used with success, obviously with a few cases of failure) is false.

Of course this is perfectly possible, but improbable.

There may be a zillion reasons why your attempt failed, including the particular hardware (real or virtual) you were using, the source CD/.iso, the settings you used and what not.

There is a simple way to verify, since you are into experimenting, try replicating what is in here:
http://reboot.pro/to...tall-xp-in-vhd/
WITHOUT introducing ANY change of ANY kind.
Then try replicating this (the FOR LOW RAM SYSTEMS (FASTER)):
http://www.rmprepusb...-xp-from-an-iso
again WITHOUT introducing ANY change of ANY kind.
(I am proposing these as examples to replicate because they are very detailed and comprehensive, and as such easier to replicate without making any assumption or unwanted changes, which may well happen when following less detailed tutorials)

Since we are going into this:

Only a test gives the best information about operation of driver, and not heard opinions and inserting links to guides.

allow me to change it into:
Only properly carried and documented  tests with results reproduced by many people on many different hardware gives  the best information about operation of a driver.

 

Anyway, this is essentially a S.E.P.:

https://en.wikipedia..._Else's_Problem

 

Wonko


 

Well, you are then again in the stance that what wim_b and Steve6375 (besides other much respected and experienced people) wrote (and that countless people have used with success, obviously with a few cases of failure) is false.

I do not think so! Just each of us prefer a different way of using WinVBlock:
wimb mainly prefer VHD, USB
steve6375 mainly prefer USB
I prefer mainly HDD, RAW image, PXE, AoE, iSCSI, Tiny PXE Server

I'm interested mainly speed of installation on computers without any drive except a hard drive using the network.

Preferences are fine, of course , but capabilities of a driver are a different thing.

 

Statement:

Winvblock, at least in some version can, when loaded through a properly configured menu.lst entry or set of grub4dos commands, map directly a .iso and this specifically has been reported to work in order to install a Windows XP from the directly mapped .iso to a number of different devices.

 

The last character in the above sentence is a "dot" or "full stop" or "period".

 

Obviously on some hardware (read as the note by Steve6375 about Atom based devices) or in some configuration or in some variations of source device and target device this may not work.

 

Wonko

I have prepared a package with drivers WinVBlock as x86_x64 F6 floppy image and a text-mode drivers ready for integration with nLite. I also added GRUB4DOS menus for PXE use :-):
FIX_INF_WinVBlock_0.0.1.8-DEV_(Feb-14-2011)_direct_map.zip
FIX_INF_WinVBlock_0.0.1.8_(June-1-2010)_no_direct_map.zip

Changelog txtsetup.oem:

• change name driver to "WinVBlock x86" for x86 and "WinVBlock x64" for x64

Changelog winvblk.inf:

• change Provider name to reboot12
• change date and driver version
• change name install section from [wvblkxx] to [install]
• change name dispalyed in Device Manager to "WinVBlock x86" for x86 and "WinVBlock x64" for x64
• delete unnecessary Compatible ID's in section [WinVBlockDriver]
• rename section [DisablePrefetcher] to [Registry]
• move AddReg=Registry to section [Service]
• delete addreg HKLM...AutoReboot (this is unnecessary)

Now the files are clear and understandable :-)

--> Driver's source code has not been changed <--
 drv.png   21.74KB   2 downloads
Note: By using the ISO image with integrated WinVBlock in real optical drive appears twice in Device Manager but when mapping ISO vanilla + F6 floppy or ISO nLite integrated WinVBlock occurs only once in the device manager :-)

Edited by kievigreen, 13 July 2015 - 07:32 PM.

Why BSoD when I change a display resolution with 800x600 for standard vga graphics adapter windows xp on
1024x768 ?

At what point does it happen?

At what point does it happen?

How do you know that this fault WinVBlock?

How do you know that this wine WinVBlock?

I transferred that XP to real HDD and everything worked.
And on WinVBlock BsoD 0x000000F4

 

And it occurs only when I try not only to change the Display resolution. Even at input of the DXDIAG team there is BsoD

And it always on the standard VGA controler...

 

Edited by kievigreen, 14 July 2015 - 10:29 PM.

Which versions GRUB4DOS and WinVBlock are using? You use VHD from USB or HDD? Please attach your menu.lst

Which versions GRUB4DOS and WinVBlock are using? You use VHD from USB or HDD? Please attach your menu.lst

Edited by kievigreen, 14 July 2015 - 11:24 PM.

Look as it occurs

https://youtu.be/9Vn0MvoFE7I

 

Edited by kievigreen, 14 July 2015 - 11:54 PM.

I tried all versions WinVBlock
winvblock-3bcb138

Try my versions - direct or no_direct map: Link

Try my versions - direct or no_direct map: Link

Edited by kievigreen, 15 July 2015 - 11:01 AM.

I have prepared a package with drivers WinVBlock as x86_x64 F6 floppy image and a text-mode drivers ready for integration with nLite. I also added GRUB4DOS menus for PXE use :-):
FIX_INF_WinVBlock_0.0.1.8-DEV_(Feb-14-2011)_direct_map.zip
FIX_INF_WinVBlock_0.0.1.8_(June-1-2010)_no_direct_map.zip

Changelog txtsetup.oem:

• change name driver to "WinVBlock x86" for x86 and "WinVBlock x64" for x64

Changelog winvblk.inf:

• change Provider name to reboot12
• change date and driver version
• change name install section from [wvblkxx] to [install]
• change name dispalyed in Device Manager to "WinVBlock x86" for x86 and "WinVBlock x64" for x64
• delete unnecessary Compatible ID's in section [WinVBlockDriver]
• rename section [DisablePrefetcher] to [Registry]
• move AddReg=Registry to section [Service]
• delete addreg HKLM...AutoReboot (this is unnecessary)

Now the files are clear and understandable :-)

--> Driver's source code has not been changed <--
drv.png
Note: By using the ISO image with integrated WinVBlock in real optical drive appears twice in Device Manager but when mapping ISO vanilla + F6 floppy or ISO nLite integrated WinVBlock occurs only once in the device manager :-)

hi reboot12, can you please provide upload mirror on reboot.pro for this?

dropbox wants me to jump through hoops and sign in for it.

thanks

Mirror on reboot.pro:
 FIX_INF_WinVBlock_0.0.1.8_(June-1-2010)_no_direct_map.zip   738.54KB   53 downloads
 FIX_INF_WinVBlock_0.0.1.8-DEV_(Feb-14-2011)_direct_map.zip   765.38KB   30 downloads

So nobody knows in what there can be a problem in WinVBlock  BsoD 0x000000F4 ?

Edited by kievigreen, 15 July 2015 - 05:59 PM.

thanks for that mirror reboot12!

So nobody knows in what there can be a problem in WinVBlock BsoD 0x000000F4 ?

I recall having the same problem you describe but it was long ago and I can not recall what I did do correct it, sorry. I do recall getting it to work finally though. just wanted to have reboot12's issue handy should I run into it again since I cant recall how I resolved it before.

thanks

So nobody knows in what there can be a problem in WinVBlock BsoD 0x000000F4?

Does your computer have a dual-core processor? Read this:
Windows XP stops responding when you click or resize a window, or in Windows Server 2003, when you run many console applications, you receive a Stop error message: "0x000000F4"

Does your computer have a dual-core processor? Read this:
Windows XP stops responding when you click or resize a window, or in Windows Server 2003, when you run many console applications, you receive a Stop error message: "0x000000F4"

No, it didn't help

 

Edited by kievigreen, 15 July 2015 - 07:13 PM.

I have no experience with USB and VHD. Does it have to be necessarily using VHD? Maybe try with the RAW disk image.
I use WinVBlock only with RAW images disks or drives (HDD, FDD, ISO)

hi kievigreen 

you my need to analysis with rigtht way to get right soulstion

 

  are you sure BsoD 0x000000F4 because of WinVBlock or FiraDisk

 try to boot your vhd using vboot without both of WinVBlock and FiraDisk

download vboot 

 

http://www.vmlite.co...d=51&Itemid=148

 

instructions can be found here:

 

http://www.vmlite.co...structions.html

 

 or install norma xp to hdd  without WinVBlock and FiraDisk and vga driver

 

are the  BsoD 0x000000F4  stell happen 

Edited by memoarfaa, 15 July 2015 - 08:57 PM.

 or install norma xp to hdd  without WinVBlock and FiraDisk and vga driver

 

are the  BsoD 0x000000F4  stell happen 

 

Edited by kievigreen, 15 July 2015 - 11:19 PM.