yes it does make difference , i used DriveGuard to boot the usb img on completely new hardware before learning process/
Interesting.... But difficult to really make any conclusions.
On top of some possibly unadvertised effects, the obvious effect of activation is that DriveGuard makes removable media appear as fixed (which it does not, when not activated).
I have been speculating that this may have important consequences... So I decided to persist with trying to use dummy.sys...
For months I've been using the historical install procedure by Dietmar
, which worked for me when booting flat files, but I always got a BSOD when installed in an IMG (not 7B, but I can't remember the specific error code at the moment). And then I found this very useful post by wimb
, which explains that the ENUM part of the registry tweak should not be used !! So simple, so obvious... and that makes the difference !
In other words, I have now this XP IMG on USB, with dummy.sys installed. i can boot on my NC10 laptop and all removable media appear as fixed
But I still get the same BSOD 7B on the Dell laptop, and the timing of events is still exactly the same as in my first experiment
So it seems making removable media appear as fixed is not key to our problem...
On a different note I haven't verified a claimed consequence:http://reboot.pro/7466/
Particularly, "dummydisk.sys" has been able to filter ON-THE-FLY the install of all NEW (so never previously recognized) and pre-partitioned USB Flash Drives without the need to PRE-RECOGNIZE them
but if true, that's something really useful indeed !
Still I would really like to understand why.....The USB device needs to be driven properly, i.e. there has to be a corresponding CDDB entry. Why making the removable media appear as fixed would relax this requirement ?