1106 replies to this topic

[davlak]

I wonder why I have again (as said earlier too) an unknown device in device manager, whose driver is WVBlk32.sys.
have I a fake winvblock.img???

[L A M A]

=
*** IMG_XP package Version 2.0 - Boot XP from Image file on USB ***

all right! So far this month is cool kewl with updates...





downloading downloading downloading...

[Sha0]

I wonder why I have again (as said earlier too) an unknown device in device manager, whose driver is WVBlk32.sys.
have I a fake winvblock.img???

It depends on how you install WinVBlock. I've said this before, but if you install with sc.exe or winvblk.exe, then as soon as you net start winvblock, you will get a new device in Device Manager which you should update using the .INF file. If you use Add Hardware Wizard, you will get two devices in Device Manager. You can uninstall one of them; whichever one you don't like. See the difference between them by observing their Device Instance Id on their Details tab.

[wimb]

It depends on how you install WinVBlock. I've said this before, but if you install with sc.exe or winvblk.exe, then as soon as you net start winvblock, you will get a new device in Device Manager which you should update using the .INF file. If you use Add Hardware Wizard, you will get two devices in Device Manager. You can uninstall one of them; whichever one you don't like. See the difference between them by observing their Device Instance Id on their Details tab.

The above description corresponds to install of WinVBlock driver in XP OS booted from partition.

In case of direct install of XP in XP-1.img file and using winvblock.ima virtual floppy,
then WinVBlock installs quite differently as compared to what you described above.

Just like davlak I have Unknown device in device manager and have no SCSI device.

The WinVBlock Service does NOT exist.
Instead I have now wvblk32 Service.

In this case using the command in an attempt to get rid of Unknown device

sc create WinVBlock binPath= c:\windows\system32\drivers\wvblk32.sys type= kernel start= boot group= "SCSI miniport"

then WinBlock Service is created but in CONFLICT since

net start winvblock

command or simply reboot results in system crash.

When I just do nothing and keep the unknown device as is, then everything is functioning normally.
So what I would like to say is that install via winvblock.ima virtual floppy during install of XP,
results in a completely different way of install of WinVBlock driver.

It is confusing but I hope it helps you to draw conclusions.

[davlak]

When I just do nothing and keep the unknown device as is, then everything is functioning normally.
So what I would like to say is that install via winvblock.ima virtual floppy during install of XP,
results in a completely different way of install of WinVBlock driver.

that's exactly what I did too!

[davlak]

hey...
does WinVBlock have any problem with IE8?

I ask you because after upgrading IE6 > IE8 on the next reboot I've a BSOD 7b but I could not read anything more...now I'm gonna reinstalling xp on IMG and verifying if really automatic restart is disabled, after that I'll report.
the above happened 3 times, and always after IE8 upgrading.

[wimb]

I have IE8 integrated in XP Setup source (including also all Windows Updates)
and in that case no problem with WinVBlock.

So IE8 is no problem for WinVBlock. Something else is going on I suppose ....

[karyonix]

#104
I think "wvblk32" service name comes from the line 'driver=diskid,filename,servicename' in txtsetup.oem in your floppy image.

[wimb]

The txtsetup.oem has WinVBlock at that position, but on install of XP using winvblock.ima virtual floppy
then the installed service is named wvblk32

txtsetup.oem

[Disks] 

disk = "WINVBLOCK DISK",\winvblk.inf,\ 

 

[Defaults] 

scsi = WINVBLOCK 

 

[scsi] 

WINVBLOCK = "WinVBlock Driver" 

 

[Files.scsi.WINVBLOCK] 

driver = disk,wvblk32.sys,WinVBlock 

inf = disk,winvblk.inf 

[davlak]

well correction...
I must confirm: IE8 <--> WinVBlock have non problems.
the simple fact is that at the 2nd or 3rd reboot (random) I have a BSOD 4E PFN_LIST_CORRUPT and this happened on my netbook Acer Aspire One, while on other 3 pcs of mine all works fine for several restart.
I suppose it's something driver-related. my 2Gb RAM (1+1) are OK and all other HW components too, I know for sure.
on that netbook I have installed win7 ultimate and xp pro sp3, ubuntu 10.10 on real HD and virtual hd.
furthermore win 2003 runs fine on the same machine even booted from vhd on usb, in 2 version: vboot and wimvblock

[davlak]

The txtsetup.oem has WinVBlock at that position, but on install of XP using winvblock.ima virtual floppy
then the installed service is named wvblk32

txtsetup.oem

[Disks] 

disk = "WINVBLOCK DISK",\winvblk.inf,\ 

 

[Defaults] 

scsi = WINVBLOCK 

 

[scsi] 

WINVBLOCK = "WinVBlock Driver" 

 

[Files.scsi.WINVBLOCK] 

driver = disk,wvblk32.sys,WinVBlock 

inf = disk,winvblk.inf 

that's exactly what happens to me.
I've related about it some days ago.

[davlak]

well correction...
I must confirm: IE8 <--> WinVBlock have non problems.
the simple fact is that at the 2nd or 3rd reboot (random) I have a BSOD 4E PFN_LIST_CORRUPT and this happened on my netbook Acer Aspire One, while on other 3 pcs of mine all works fine for several restart.
I suppose it's something driver-related. my 2Gb RAM (1+1) are OK and all other HW components too, I know for sure.
on that netbook I have installed win7 ultimate and xp pro sp3, ubuntu 10.10 on real HD and virtual hd.
furthermore win 2003 runs fine on the same machine even booted from vhd on usb, in 2 version: vboot and wimvblock

[SOLVED]

for some reason that I ignore, something strange happens in my winxp vhd hosted on my netbook hd or usb-hd.
at every reboot changes are made into registry key regarding iastor and msahci.
never knowed this till today
so I've put a reg file (the ones from folder registry_key in IMG_XP) in %WINDIR% and then gpedit.msc to make regedit executing this registry at every shutdown-restart.
now it works, and I'm happy but... I don't like it

EDIT: even stranger is the fact that 2003 (on VHD on the same netbook) doesn't seem to be affected by the misteriously self-deleting registry value, as for win7 vhd and ubuntu.vhd ...

ok ok...ubu hasn't registry...ok

[Sha0]

...
the simple fact is that at the 2nd or 3rd reboot (random) I have a BSOD 4E PFN_LIST_CORRUPT and this happened on my netbook Acer Aspire One, while on other 3 pcs of mine all works fine for several restart.
...

Which WinVBlock version?

[davlak]

Which WinVBlock version?

Hi Sha0, it's 0.0.1.8-DEV (Feb-6-2011)

in meantime, I've made an experiment on my netbook: installed xp on internal sata hd, installed winvblock inside xp and this way I have no issue regarding the unknown device and the bsod after net start winblock (mentioned by wimb too) though there's another issue, two winblock scsi device whereof one has the yellow !...anyway: after that I've applied the usb and other registry tweaks and cloned the whole installation on a vhd, put the vhd on the internal hd of my netbook...and all seems go right since now....therefore I agree with wimb regardind some issue with the winvblock.img.

[wimb]

=
*** IMG_XP package Version 2.1 - Boot XP from Image file on USB ***

You can use IMG_XP_Create.exe and USB_XP_Fix.exe to make Universal XP Image file bootable from USB

Download - IMG_XP

Update of USB_XP_Fix.exe

• Added - Option to Make Grub4dos Boot Menu for XP Image file on USB-drive
• Added - Support in boot.ini menu for Multiple Hal and Kernel - Option useful for old hardware
• Changed - Program Version - latest version is 2.1 for USB_XP_Fix.exe

More Info - http://www.911cd.net...showtopic=23553

[Doodoo]

The above description corresponds to install of WinVBlock driver in XP OS booted from partition.

In case of direct install of XP in XP-1.img file and using winvblock.ima virtual floppy,
then WinVBlock installs quite differently as compared to what you described above.

I can only concur with that. When installing Xp direct to an image file with a virtual floppy containing the WinVBlock driver, I have seen various behaviours, including those two:



and

the simple fact is that at the 2nd or 3rd reboot (random) I have a BSOD 4E PFN_LIST_CORRUPT

Have seen exactly the same thing on my samsung NC10 notebook, where the above screen captures have also been taken.

for some reason that I ignore, something strange happens in my winxp vhd hosted on my netbook hd or usb-hd.
at every reboot changes are made into registry key regarding iastor and msahci.

Haven't had the time yet to check if the same occurs, and if your fix also works for me... But I'll certainly give it a go !

[L A M A]

DOWNLOADING... dot dot dot...

[wimb]

I can only concur with that. When installing Xp direct to an image file with a virtual floppy containing the WinVBlock driver, I have seen various behaviours, including those two:

You are mixing things up - WinVBlock Disk is NOT WinVBlock Driver

WinVBlock Disk is present for me too - there is no problem about it.

WinVBlock Driver will normally occur as SCSI Controller, but for direct install of XP in Image file,
then this fails and you get Unknown Device instead

[Doodoo]

You are mixing things up

Yes absolutely.... Forgive my ignorance !

WinVBlock Driver will normally occur as SCSI Controller, but for direct install of XP in Image file,
then this fails and you get Unknown Device instead

That's what I should have shown :



But then what is this WinVBlock Disk ?? Can it be removed from the device list ?

[Sha0]

...
But then what is this WinVBlock Disk ?? Can it be removed from the device list ?

Please try using View -> Devices by connection. This non-default view has helped me to better understand how Windows works with devices. Perhaps it could help you, too.

Using the "by connection" view, everything with a + "plus sign" is a bus device that has children. You will quickly see that WinVBlock Disks are children of the WinVBlock Driver (the bus). Such disks are the virtual disks. If you established a virtual disk from GRUB4DOS or MEMDISK, then no, you cannot remove it. Otherwise, use winvblk.exe -cmd attach and winvblk.exe -cmd detach to attach and detach such disks.

Why do you wish to remove the devices, anyway? They cause no harm. You should be able to Update Driver... the "question-mark" Unknown device as long as its Details tab shows that it really is the WinVBlock bus.

[maanu]

@ wimb

i have encountered a strange issue regarding booting my HDD img
on a AMD notebook ,
it is how it happened ,

when i start booting img file from AMD notebook ) (i was booting from usb)
i got BSOD 0x00000007E after windows logo

i copied the img to the hdd , boot from usb , and MAPPED THE IMG ON HDD in RAM,
booted it , same BSOD happened .


is it the famous inteppm.sys issue ?

http://www.runpcrun.com/0x0000007E

??

if i am not wrong , i have read somewhere in 911 cd forums, about
renaming the above driver , in order to boot it on AMD.

( by the way , i have already booted the same img on one of the old
AMD desktop systems without any issue . )


any hints ?

( using winvblock 30th jan driver )

[wimb]

=
*** IMG_XP package Version 2.2 - Boot XP from Image file on USB ***

You can use IMG_XP_Create.exe and USB_XP_Fix.exe to make Universal XP Image file bootable from USB

Download - IMG_XP

• Added - Created Image Size selectable from 0.4 GB in small steps until 7 GB
• Added - Option to Add EWF Write Filter to protect the XP Image file for unwanted changes
• Changed - WinVBlock updated to latest version 0.0.1.8-DEV (Feb-14-2011)
• Changed - Program Version - latest version is 2.2 for USB_XP_Fix.exe

More Info - http://www.911cd.net...showtopic=23553

[Aye Htay]

Hi Wimb,

Just want to tell you Thanks for your tool and working fine my mini7.
Installed on IntelPentium 4, tested on AMD, working well.
As you know, for Win7 no need to install any drivers, as installed itself.
Running on Ram disk. Tried with VHD in USB Flash. No way to load because loading too slow.


Regards,

ah

Edited by Aye Htay, 14 February 2011 - 11:15 PM.

[maanu]

@ wimb

cant we just DISABLE the loading of INTELPPM.SYS from registry ./?

will it effect on INTEL based systems then >??

during googling , i have read some posts ,where users were asked to DELETE the INTELPPM.SYS file from drivers folder , when they were having same issue (post 121) while booting XP from AMD,.


but i guess since we are talking about GENERIC xp , we CANT delete intelppm.sys ?

[karyonix]

@maanu
Normally intelppm service has Start=1 (system). It crashes on some AMD based machines.

You can just disable it by set Start=4 (disabled).
I think the effect on Intel based system is probably the processor will not sleep.

What I think is best value is Start=3 (load on demand).