ToeCutter

I'm glad to see that others are having good experiences with WinFLP. It wasn't clear to me why DeadDude was railing so aggressively against it, WinFLP has solved quite a few problems for me. And, MS has been awfully generous with licenses. To your question regarding why MS insists on keeping WinFLP corporate: While I'm usually one to avoid cynicism, I'm convinced that offering WinFLP to the consumer market would seriously bite into that Vista revenue they're raking in right now. It's one thing limit the number of times a license may be used, but it's a completely different ball-of-wax when MS starts prescribing the type of hardware you can run their product on. This is bordering on ridiculous! http://www.engadget.com/2008/05/10/microso...ome-boundaries/

I regret the tone of my reply, but I'm not sure how you consider your post to be helpful to anyone, considering that it's riddled with inaccuracies. Much of what you've posted here simply isn't true, and the rest appears to be pure speculation. Have you used WinFLP in a production environment? I'm not sure why you're discouraging anyone from using WinFLP should it fit their needs.

WinFLP works just fine on older notebooks. I've even installed it on a fewer of the low spec new notebooks we've purchased and I've had only a few isolated issues. These issues were due primarily to the Windows Installer that ships with WinFLP. A quick trip to Windows Update fixed it pronto. Regarding you primary concern, Hibernation works just fine with all the notebooks we've installed WinFLP on. WinFLp goes into and comes out of Hibernation pretty quickly. Are you anticipating issues or have you experienced any with WinFLP specifically? I'd like to know if anyone else has had issues. I have noticed that driver support for WinFLP is essential. I've come to realize how much we've relied upon MS-provided drivers for power-management with our notebooks. Installing the vendor-provided ACPI drivers has worked fine though, as WinFLP relies on the WinXP x86 code base. I've yet to experience any driver issues related specifically to WinFLP. NOTE: WE install with both the "Driver Support" and "Local Mgmt" tools. All together, this represents a tiny 850MB install footprint. WinFLP screams on older notebooks when compared to WinXP. I've been very surprised with how well it works. We'll be deploying VMware ESX with VDI shortly, and I intend to use WinFLP on the majority of the virtual desktops we deploy. It's memory footprint is very low and it seems to offer performance similar to what we see with WinXP. I've yet to have a user notice any difference. We'll deploy using VMware and RIS tools, so our desktop management will automated to pretty high degree. Also, I've attached a JPG of one of our development VMs running WinFLP with Office 2007. Even with Word 2007 open and running, the memory consumption is ridiculously low.