>>I'm sorry to say, that after 1 week with the setting of BLASTER=A0 in the autoexec.nt file, it still locked up :(. It lasted 5 days before it locked up, though, and that is an improvement.
>>
>>This is going to be a real problem, as one of my office clients is expanding to a 2nd office and putting in 4 XP Pro machines... don't know how I'm going to prevent the application from locking up... Windows 2000 works fine, but the people they are getting the computers from say Win2K is not available on their new machines.
>>
>>I've been coding like crazy to get the app switched over to Visual Foxpro, but it is a massive application and will take many more months to make a complete switch (complete with debugging).
>>
>Hi Mike,
>
>Unfortunatelly, I haven't seen any real resolution to this problem. Your choises are:
>

Rewrite app
>

Run it under Win2K
>

Rin it on slower PC but it hard to tell how slower it has to be

Sergey,

What about TameDOS? I'm not sure, but it might be a possible solution. I just downloaded their trial version and will let you know how that works. It's a $20 program, so if it works, well worth the $20! It certainly slows down the CPU usage.

Mike

Let's see, how will the User misinterpret this Yes-No Question...