As a followup to my recent post “Comspec Corruption”, I’m happy to report that the culprit has been found.

The installer for the client drivers for accessing a Sybase database.

What on earth they were thinking, I’ll never know … but at least I know that I’ll need to fix COMSPEC after any reinstall of that driver.


blog comments powered by Disqus
Next Post
Handling UAT if users constantly miss things  28 Jul 2012
Prior Post
Comspec corruption  10 Jul 2012
Related Posts
Browsers and WSL  31 Mar 2024
Factory methods and functions  05 Mar 2023
Using Constructors  27 Feb 2023
An Inconvenient API  18 Feb 2023
Method Archetypes  11 Sep 2022
A bash puzzle, solved  02 Jul 2022
A bash puzzle  25 Jun 2022
Improve your troubleshooting by aggregating errors  11 Jun 2022
Improve your troubleshooting by wrapping errors  28 May 2022
Keep your promises  14 May 2022
July 2012