Yes, it definitely appears that the TSX driver might have that issue. Our issue last night was that PhD was unable to get guide commands to the mount, the logs indicate it was getting no response to guide commands from PhD under DirectGuide.
If I understand what you are saying then only those com drivers that are written with that “flaw” (see below, it may not be a “flaw” as such) have the issue (which explains why not all drivers and functions have died)?
Sounds like those developers that wrote the drivers with the issue will need to fix and reissue the drivers unless MS can (or even will) come up with a way around that. If the drivers in question are truly wrong, then MS may not feel that it is their problem and will not deal with it.
We have rolled our system back and it is working but it sounds like the developers have (35?) days to fix their drivers before their users are totally dead in the water.
UPDATE: According to a post by Bob Denny on the ACP forum:
“And the whole thing is a result of some junk DCOM info needing to be present in COM registration just (and only) for TheSky 6 ten years ago! I was around for all of that. Thanks for alerting me to this. I will get onto the SGP forum and fill in the blanks.”
So if I am understanding this, it is all about old code for making the TSX driver compatible with TS V6 so it is less a matter of fixing code but of removing that requirement and it’s code? Probably well past time that TS V6 users ungraded to TSX anyway!
Am I still correct that we will need an updated TSX driver?