Now, it WAS working. I don't know whether it's a problem calling a driver
function, or more likely, a problem calling another DLL like CTL3D or
COMMDLG. These are always getting screwed up. I run hundreds of
applications on my machine and they all have idiosyncracies with DLL's.
Anybody see this problem? Got any ideas? I've gotten as far as seeing what
DLL's CUSM calls but I can't see any way of seeing what entry points in the
DLL's it calls so I can compare it with the existing entry points in my
existing DLL's...
AARRGGHHH! This was working. I really want to use my color camera with
CUSM. It was working on their !@#$% last beta.
Help.
- JohnR
-- John R. Haggis haggis@cesium.com Millennium Research (408) 269-1814 vox (408) 269-9323 fax