CompuServe Thread

Well, this isn't really too simple. I used a debuger. Periscope to be more exact. With this loaded in memory, I can halt the computer at any moment and do anything I want. I placed a "trap" at the Int 14h entry point and issued an Int 14h to see how the code would flow. Then I did what is called "single step". It means that I can walk through code (assembly) one instruction at a time to see what SERVER would do with the call. Before it let the call proceed to the original target (the Diaquest driver in this case) SERVER will process and check several things. Because the Diaquest utilities "talk" to the Diaquest driver through Int 14h, SERVER would get the call first and, because some of the calls were, in theory, illegal, it wouldn't handle it right and the Diaquest driver would never get it. Please note that I don't have Diaquest. I had to write a Diaquest emulator to test this. I wrote the emulator by watching what 3D Studio sends down when cofigured for Diaquest. This only gets worse… This is, of course, a lot more involved than this. I would be glad to explain what is an Int 14h, how it's normally used and so forth. But I would suggest creating a new thread for that so people wouldn't get sick reading it. I could call it "Nerds & Geeks Unlimited"…