I have tryed a few times to understand, what the difference between Firadisk and WinVBlock is, but i always fail.
Can anyone explain the difference to me or at least tell me which driver should be used for what?
Firadisk vs. WinVBlock
Started by
MedEvil
, Feb 02 2011 07:40 PM
4 replies to this topic
#1
Posted 02 February 2011 - 07:40 PM
#2
Posted 02 February 2011 - 08:24 PM
You are not the only one, rest assured.I have tryed a few times to understand, what the difference between Firadisk and WinVBlock is, but i always fail.
Psss, come nearer, the SECRET is: There is NO secret
There is none (in practice).Can anyone explain the difference to me or at least tell me which driver should be used for what?
The same ideas are constantly exchanged between the respective developers karyonix and Sha0, and though they are two separate projects and codes, they tend to sport exactly the same features.
Until we don't have mature, stable releases of both, it's just a matter of difference between releases, meaning that today's experimental release of one may have an added feature, and the release of tomorrow of the other may have that same feature added + another one.
More or less currently BOTH:
- can be installed via F6 or SC
- show devices in disk management
- can be RAM based or file/sector based
- can "catch" images loaded by BOTH grub4dos mapping and Memdisk
- can mount RAW images and .vhd and .iso
- are compatible with XP and (possibly) 2K
Latest work is to make them running with 2003 and (Vista , 2008 and) 7. (driver signing, 64 bit, etc.)
Once both will be "stable", it is likely that they will "fork" more with one more focused to network connections (like AoE et similia, already present in WinVblock) and the other one to other things, but we'll have to wait and see.
Wonko
#3
Posted 02 February 2011 - 10:18 PM
Thanks for clearing this up. It was bugging me for some time.
#4
Posted 02 February 2011 - 11:19 PM
Or, may be the developers would agree to take the best from both drivers and create a single project & product... Its typical for open source. So that each of them can concentrate on a different project. Competition is wonderful thing, but given critical shortage of qualified Reboot developers in this complex field, taking care of updating G4D & transition to Burg and polishing this wonderful driver in parallel may be better handled in separate "cores". Especially keeping in mind that MS is coming with Win8 soon, so the existing product support gap may widen. Would be nice to add "G4D Style Menu" support to Burg or an easy to use Burg Config Generator.
#5
Posted 03 February 2011 - 12:36 PM
hehe, I would obviously want all cool dudes to become one
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users