You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 19, 2024. It is now read-only.
The original Putty 0.63 displays a window telling you that COMx is currently in use when you have another program or session using that port.
The currenty t020 build of Putty Tray just crashes if you use the same port "A problem caused the program to stop working correctly. Please close the program" with the option to Close or Debug.
If I select to debug with VStudio then I get "Unhandled exception at 0x00B38C8E in putty.exe: 0xC0000005: Access violation reading location 0xE8ED6472."
This issue happens all the time on Win8.1-x64 with a USB FTDI chipset device.
The text was updated successfully, but these errors were encountered:
I knew that would go wrong. Dammit.
Re-review that code for possible horrors. I'm still not happy with
backhandle possibly being junk, but nothing should really get far enough
to notice (famous last words). Still going with it being better to run
stuff, than to not run it.
The original Putty 0.63 displays a window telling you that COMx is currently in use when you have another program or session using that port.
The currenty t020 build of Putty Tray just crashes if you use the same port "A problem caused the program to stop working correctly. Please close the program" with the option to Close or Debug.
If I select to debug with VStudio then I get "Unhandled exception at 0x00B38C8E in putty.exe: 0xC0000005: Access violation reading location 0xE8ED6472."
This issue happens all the time on Win8.1-x64 with a USB FTDI chipset device.
The text was updated successfully, but these errors were encountered: