02-02-2009 03:11 AM - edited 02-02-2009 03:12 AM
Hi mathan,
if you have two different dll's, then you should write your application, that it can work with both. There should be a function which gives information about the dll. You can read it and react on it. I think the result should be that XP works with the XP driver and Vista with the Vista driver.
Mike
02-02-2009 03:46 AM
Dear Mike,
Am sorry i didn't get your point.
I will tell the whole thing. Actually, the USB smart card reader am using is having support for 32 bit as well as 64 bit. All the .cat files, .inf files and .sys files are in a single folder named "Release" and when we plugin the smart card reader in our 32 bit system, during the found new hardware wizard, when pointing to the "Release" folder will automatically install the corresponding driver to the device. Same case when reader was plugged into a 64 bit machine, it will take appropriate 64 bit driver when pointing to that folder.
That was not at all a problem.
Actually, i have one dll named "MCSCM.dll" which communicates with the smartcardreader and the smartcard (memory card).
This MCSCM.dll has some more than 10 functions and am using card connect and card disconnect functions and some others. Before that, for establishing communication with the resource manager context, i have to use scardestablishcontext and scardlistreaders function from winscard.dll (called from c:\windows\system32 path using CLN).
The problem is, in WinXP in which my application was developed, the winscard.dll works fine even it was loaded from 'data' folder.
But when using the same application in WinVista, the winscard.dll instead of locating from the windows system32 folder, LabVIEW, by default points to the 'data' folder and takes it from there. In that case winscard.dll from VISTA is different from winscard.dll in XP.
What i did in VISTA was, i copied the winscard.dll from system32 folder and replaced it in 'data' folder. Then the application works fine.
Am asking, without doing such copying, is there any way to load the dll from the system path when the application was launched.
Please ask me more questions if i was not clear this time.
Thanks,
Mathan
02-28-2009 06:48 AM
02-28-2009 10:59 AM
Don't hijack an unrelated thread. Post a new question. You might want to try the Lego board.