I wish that I were both smart enough to understand what is going on with Foxstart and smart enough not to be curious. But I am neither. I did try to read the stuff about timing loops and overflow errors and counting up instead of down to eliminate divide errors (or was it down instead of up?) in the DZpatch.prg file that UFT Engineering may have used in UFT 3.0 Foxw2600.esl.
I then wondered if Blue and company tried to disable it on exit, and if that was perhaps causing a certain ATI video card to go bonkers. I also read a little bit about that ATI card and found that the company basically admits that it too has problems staying in synch and randomly swithes back and forth from TV output frequency to Monitor output frequency. Throw in a wheelmouse or two, and some substandard PC 100 memory chips and and some video buses clocked at 83 mhz and you wonder how UFT runs at all.
Then I went back to my big MS Win 95 (beta copy=1?)resourse manual and tried to understand read what it said about 16 bit programs in Win 95 in 1995.
Frankly, I don't understand any of it, but it seemed that if we all throw enough BS in the mixture the people with the problems might go "aha".
I still think I would get a cheapy non-tv non accelearated video card if I were more into UFT than vector graphic games.