In fact, if you don't care about AoE, you needn't copy AoE32.sys. WVBlk32.sys handles all non-AoE logic, and is the "core" of WinVBlock. You can use just the sc command found in the ReadMe.txt file for this driver to install it, yes.
...I read with a lot of interest your post about WinVBlock. However there is a tremendous amount of very technical information, which makes it quite difficult...to extract the useful bits. May I ask a few simple questions:
1/ In order to install WinVBlock on a running XP, do I only need to copy wvblk32.sys and aoe32.sys in c:\windows\system32\drivers\ and execute the commands found in the ReadMe file ?
If I've read wimb's thread well enough, I do believe that you wind up with an HDD image file. These are indeed currently bootable with the currently released WinVBlock (0.0.1.8 as of this writing). You could boot such an image either as a RAM disk, or directly from the disk on which it resides.
2/ Is an .IMG file (as created by IMG_XP_Create) bootable with GRUB4DOS, not from RAM but as a HDD image file ?
Assuming your HDD image file is called foo.img and is in the root directory of the first partition of your USB disk, you'd do:
3/ If the answer in 2/ is yes, which commands do I need in GRUB4DOS menu.lst in order to do so ? The example in the WinVBlock thread only deal with the "boot from RAM" case.
title foo map (hd0,0)/foo.img (hd0) map --hook root (hd0,0) chainloader /ntldr
Hope it helps. Just be sure that if you are indeed booting from a USB disk, be sure that the USB drivers are all set to boot-start in your HDD image. By the way, .ISOs are so-named because of the ISO9660 filesystem, also called CDFS in Windows, I believe.
Sorry to keep you busy, and many thanks for your any information you can provide !