handling IVI class driver simulation - need to call actual driver

[pblase]

Running LabWindows/CVI 8.1. I have written a device driver for a piece of equipment, and a class driver to sit on top of that (so as to hopefully allow the use of more than one type of controller in the future). Things run ok if the hardware is plugged in. However several of the parameters use dynamically calculated range tables, and if I try to operate in simulation mode (set "Simulating to '1' in the option string when calling "InitWithOptions()") none of the range table functions in the actual driver get called. I don't want the actual write or read callback called when simulationg, so checking the "use callback when simulating" flag for the attribute won't do what I want. I just want the range-table callback called. Any suggestions would be welcome.

[pblase]

Ah, found this one. Since this mechanism goes through the IVI Store and MAX, I had forgotten to tell it to use the debug version of the driver instead of the release version for one of the driver sessions (each controller is on a separate driver session, of course). Since the debug version is several months newer than the release version, no wonder I was getting wierd results.