3 replies to this topic

[pscEx]

In multiPE there is an option to boot a PE1 (XP based) across Grub4Dos FiraDisk or WinVBlock reading a RAM image.
 ramdisk.gif   24.91KB   16 downloads
Currently default setting is WinVBlock, but that is arbitrary, because I have had no criteria to decide.

@all, especially Karyonix and Sha0
(There exists a poll initiated by MedEvil, but I do not see there for me usable objective answers to my question.)
Please tell me technical reasons (speed, ressource use, etc.) to decide for the "optimum" driver.
Maybe the "optimum" depends on some project settings. Then please tell me also the "when" - "then"

Peter

[Sha0]

In multiPE there is an option to boot a PE1 (XP based) across Grub4Dos FiraDisk or WinVBlock reading a RAM image.
...
Currently default setting is WinVBlock, but that is arbitrary, because I have had no criteria to decide.

@all, especially Karyonix and Sha0
(There exists a poll initiated by MedEvil, but I do not see there for me usable objective answers to my question.)
Please tell me technical reasons (speed, ressource use, etc.) to decide for the "optimum" driver.
Maybe the "optimum" depends on some project settings. Then please tell me also the "when" - "then"

I don't know. You could flip a coin, perhaps. WinVBlock still needs some work, but right now I'm working on adding to Syslinux' NTFS support.

[pscEx]

Thanks, Sha0!

Your answer confirms my opinion, that the two ways technically are nearly equivalent.

It brings me the good feeling, that my previous "coin flip" was reasonable.

But let's wait for your "competitor" and eventually some users.

Peter

[dog]

I had a preference for winvblock because it would map an image from HD without needing to hard code the file name anywhere else.