Randy C
May 12th, 1999, 03:12 PM
On Some machines running Win 95 (notably some laptops), you can issue a CreateFile() call to the "COM2" (or whatever port) and open it with no problem, leaving the user with no mouse control... even if your application test opens and then re-closes the port, the mouse will be gone till the user re-boots. This is bogus! Is there any sure fire method (reading .ini files? registry entries? System calls?) that will definetly tell me with certainty what port (if any) is being used by the mouse, so I can block the user from trying to access it?
--Randy C
* * * Second star to the Right!
--Randy C
* * * Second star to the Right!