COM1 not behaving...

  • Thread starter Thread starter Erik
  • Start date Start date
That would be nice, but I'm afraid we might never find out...

Bob I, if you're still reading, I have an even stranger reply for you (told
you I'd keep you updated): COM1 is now "behaving"; meaning that it works just
fine, after reboots and cold starts.

Don't ask me how; it just started working one day, before I ever got a start
to completely reinstall the system.

Once again, it seems that XP has cured itself...

> The question is: If the activity that takes place during this
> reallocation or scan or whatever Device Manager is doing is something
> that can be forced automatically on boot, how can that be accomplished
> to remove the need for this manual change?
 
Yes, still here, I guess the saying "All's well that ends well" is
appropriate. ;-) Glad to hear it resolved itself.

Erik wrote:

> That would be nice, but I'm afraid we might never find out...
>
> Bob I, if you're still reading, I have an even stranger reply for you (told
> you I'd keep you updated): COM1 is now "behaving"; meaning that it works just
> fine, after reboots and cold starts.
>
> Don't ask me how; it just started working one day, before I ever got a start
> to completely reinstall the system.
>
> Once again, it seems that XP has cured itself...
>
>
>>The question is: If the activity that takes place during this
>>reallocation or scan or whatever Device Manager is doing is something
>>that can be forced automatically on boot, how can that be accomplished
>>to remove the need for this manual change?

>
>
 
Back
Top