Thanks for your time. I think I can rule out the "failure to sacrifice an end-user to the WinME gods" since that person is a highly qualified tech. :) Then again, he has a tendency to find out bugs faster than anyone else in this world! :)

Thanks again!

>No; I have WinME systems running FPW2.6a (patched for speed fix) today, so it's not that ME inherently dislikes FPW2.6 - it could be CPU speed issues, driver issues, interference with another app like NAV, a need to restrict the memory or disk space available to the app, or your failure to sacrifice an end-user to the WinME gods every day at noon causing the problem. Video has been one issue we ran into - FPW does not like any number of high-performance video cards, and exhaustion of the GDI by Win16 apps is a frequent problem; running at high res/high color depth with lots of desktop icons and fonts will exhaust the GDI for the Win16 subsystem quickly. Try dropping down to 640x480 @ 16 color mode with the standard VGA driver to test this. You may want to drop all the way back to running in Safe Mode and then readd drivers and startup apps until you see things break by playing with MSCONFIG and Selective enabling of drivers and startup apps.