That particular error is irritating me. Windows appears to send a "remove device" signal to the WinVBlock "bus" device, but sometimes does not follow that with an "attach" signal. Sending both signals is normal for when it properly installs the bus device using the .INF file. But there seems to be a race condition of some sort which is causing this problem. I have to figure it out and fix it. You might have luck with simply trying again, as my testing demonstrates about a 50% success rate.
...But I have one problem: a floppy was needed for me because using a folder containing winvblock generates an error "file not found" when attaching the iso.
Well, if you are mapping (fd0) using GRUB4DOS, then you would need for WinVBlock to be working in order to get an A: drive for that GRUB4DOS disk. If it's not working, you won't get the A: drive. But really, if you try again, you might not get the "file not found" when attaching the .ISO.
I did try mapping winvblock.img as fd0 but there's no a: unit (or other letter) into the prompt to explore and finding drivers from.
You can use either GRUB4DOS or winvblk.exe to attach the disk/disc image files. If you use one, you shouldn't need to use the other. The important bits are:
I'd like to do so, but need help for menu.lst.
- Disable Driver Signature Enforcement.
- That the bus device is properly functioning once the service has been started.
winvblk.exe -cmd detach -d 12should give "Parameter is incorrect" instead of "The system cannot find the specified file". What this command attempts to do is detach the 12th virtual disk (which doesn't exist). The former error means that there is no 12th virtual disk. The latter error means that winvblk.exe couldn't talk to the WinVBlock bus at all.
But really, whatever this problem is needs to be fixed.