> On the other hand, I understood no-one spotted the problems during the > FC2 development cycle, either. > > James. I think it was somehow related to 2.6 kernel. It was reported repeatedly during the test cycle but the actual fix/workaround came after the release of core 2 if memory serves. I have not seen the issue persist in the Core 3 Test* cycle on hardware where I did experience that issue in core 2, both XP & win2K dual boot quite happily w/o any incantations required at install time. YMMV :). -- Bests, Jon
