|
Update.
After doing many different tests and taking wide and varied approaches towards identifying what exactly is going on with my ports and fixing it (registry hacking, system driver renaming etc.) , I, having run out of plausible causes, shut down SETIatHome application that startu up automatically on boot and lo and behold, my serial ports sprang to life!
I think that SETIatHome has a memory leak problem that was disrupting the location that serial ports use for I/O.... bizzare, but all is well now.
Victor
|