>On my son's computer (WinME), if you queue up more than 2 things to print, you get some weird virtual call error and the printer ist kaput until you reboot. I have also seen some older software that ran happily on Win95 and Win98 die ugly deaths on WinME. Maybe the ME = Miserable Experience.
>
>>Windows ME has a config.sys file but if you write into it whatever you write disappears and has no effect. Windows ME does not seem to share printers at least as far as we are able to find out. My FoxPro 2.6 program requires a files setting of 80 in order to work. I and several coworkers have spend 3 hours trying to figure out how to JUST SET FILES!!! Why have a config.sys file when the #@!!! thing doesn't work! Any help greatly appreciated. ME is not for me.

This may not help in your situation, but a few years ago when Win 3.1 went to Win 95. We decided here to advance our app along the way. We did not trust MS to ensure that its OS would be backward compatible. So when IT budget was announced it always included money for forward moving of our app to the newest version of FoxPro. We were proven right when MS dropped support of 2.6. I would recommend to you to keep moving your app forward.