mitsukai, on Dec 3 2008, 06:28 PM, said:
excuse me? what makes u say EWF is unstable? give me thee link with the facts
and unsupoorted? i tihnk not! maybe u search more on EWF.
you dont even need to boot EVER after installing EWF!
Wtf? Why are you defending EWF? I don't need to link to explain my experiences with EWF, but whatever.
http://www.mp3car.com/vbulletin/winnt-base...m-whats-up.html
craptree said:
Hey there, I had exactly the same problem as you. EWF is very inefficient, and eats up RAM faster then fire to petrol. Try FBWF, does a smiler thing,but much much much more efficient (for various reasons). I have a guide up on installing this if your interested.
tl;dr: EWF locks up (and corrupts all your data, sometimes even Windows!) if it goes over 512mb of uncommitted data for no apparent reason. EWF takes forever to sort the data and commit it to disk if you're near the max. EWF wasn't designed for any applications where writes would
intentionally be performed but caught and discarded (only inadvertant bootup and running writes on a thin client). EWF wants to reboot every time you change the most trivial of settings (you can't even commit the data in RAM, then let it continue to filter writes to RAM, you have to reboot between commit and continuing filtering).
Not very tl;dr since there are so many holes. But long story short, EWF isn't even suitable for use on an Eee PC, because it locks up if you happen to go over 512mb memory usage with uncommitted data. What do you think that'll do when trying to run nLite with it running?!