Comm port access ?

[sggaunt]

Hello
We provide a customer with a program which connects to a handset via the comm ports on a PC.

Recently we had to change a third part module in the code because the orginal did not work with NT/W2000

Now we find that if the program has not been installed on a NT/W2000 m/c previously everything is OK,

But if the Old version of the code was previouly on the M/C then the communications do not work.

We are removing all registry refernces we can find and using the uninstall program supplied with our installer (Install Shield), but the problem persists.

As mentioned before there is no problem with clean installs or replacements on Win9X machines.

Can anyone Help.

Steve.

 

[TestNode]

Have you done any testing beyond the uninstall program? I will suggest that you build a fresh install of W2k and use windiff to map the winnt directory*, install your program and remap using windiff, then compare the results. Next step would be to run the uninstall program and run windiff again.

You should see what is changed, then what is missed.

My suspicion is that the system is writing a GUID that references your .dll, and is not removed from the dllcache directory during the uninstall. Hence, when you reload, the same GUID is used with a reference to the same .dll file. And when I write "same" this means version and/or date. Could be that W2k is not accepting your new .dll for some reason.

*The registry files also include some user information in winnt\profiles, otherwise, just running windiff on the winnt\system32 directory would suffice. You could run separate windiffs on each dir and would probably save some time.

Good luck,

Mike