Could not host the putty windows when using Putty 0.6 about superputty

[GoogleCodeExporter]

I tried changing window title in a saved session from within PuTTY but that did 
not
reproduce the issue you describe. SuperPuTTY captures the window based on the 
PuTTY
process it launches not on the window title. Under File->Settings->PuTTY/Scp 
location
verify putty.exe is the full path to your putty.exe file (Although it should be
asking you if this is invalid during start).

Original comment by [email protected] on 31 Mar 2010 at 4:15

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I have a similar problem SOMETIMES. Doesn't always happen. Also used to happen 
with Putty Connection Manager, hence me looking for an alternative and finding 
SuperPutty.

I haven't tested to prove this, but I think it might have something to do with 
Bullguard Internet Security, as it was after installing this that I started 
having problems with Putty Connection Manager. I haven't tried uninstalling 
Bullguard since I installed SuperPutty as I REALLY don't want to have to go 
through setting up all my firewall exceptions etc again.

If need be I could get a test machine up and running if you want me to try 
anything. 

If you want to do any testing of your own, Bullguard can be used for 60 days 
without a license.

Original comment by [email protected] on 29 Jun 2010 at 12:08

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Hi,
I have the same issue using Windows 7 Professional 32bits.
The putty windows is opened like a regular putty windows and the tabs are empty.
Attached screenshot

Original comment by [email protected] on 27 Apr 2011 at 10:15

• Added labels: ****
• Removed labels: ****

Attachments:

• NoTab.png

[GoogleCodeExporter]

This issue is driving me (and many others from what I've read) nuts.... At some 
point, on only one of my many machines, my PuTTY Connection Manager started 
showing the same issue described in this bug. i.e. PCM stopped swallowing the 
PuTTY windows exactly as was described in the bug here. I switched to using 
SuperPutty hoping it would fix the problem. After using SuperPutty's File -> 
Copy PuTTY Sessions menu option, I saw the exact same issue described in the 
bug. The import worked fine however all my putty sessions have the two window 
issue. HOWEVER if I connect using the Quick Connect, the very first time I use 
after starting SuperPutty, it will swallow the Window properly. Every 
subsequent Quick Connect, even to a different host, will have the same two 
window issue. Closing putty and superputty and restarting superputty gets me a 
single quick connection swallowed properly, then all subsequent sessions revert 
to the erroneous two window behaviour. I would love debugging suggestions.

Original comment by [email protected] on 9 Jul 2011 at 6:38

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

OMG I fixed it! Something in the Putty registry settings was causing the two 
window issue. I did the following. In a cmd.exe I saved my existing putty 
sessions to a putty_borked.reg file using: regedit /ea putty_borked.reg 
HKEY_CURRENT_USER\Software\SimonTatham\PuTTY

Then I made sure Putty and friends where closed and used regedit to delete the 
whole HKEY_CURRENT_USER\Software\SimonTatham\PuTTY key. Launching Putty 
recreated the defaults and now both PCM and SuperPutty swallow sessions 
properly.

Original comment by [email protected] on 9 Jul 2011 at 7:01

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Unfortunately my registry fix isn't a 100% fix as the problem returns. On 
another machine which was working 100% of the time, I upgraded PuTTY from 
development version 2010-11-12:r9020 to PuTTY 0.61 and this two window failure 
mode started happening with every connection. Reverting PuTTY to 
2010-11-12:r9020 made it go away on that machine.

Original comment by [email protected] on 13 Jul 2011 at 5:26

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Maybe you all have a look at this:
http://superputty.vanillaforums.com/discussion/28/putty-windows-are-not-attached
#Item_24

Original comment by [email protected] on 12 Sep 2011 at 8:46

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

If others are seeing this behaviour in Win7 then please try running in WinXP 
SP3 compatibility mode as this certainly solves the problem for me.

Original comment by [email protected] on 16 Nov 2011 at 1:03

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I tried  whippyhu... solution and it worked thanks. My issue happened in both 
connection manager and super putty after some updates.

Original comment by [email protected] on 6 Mar 2012 at 6:07

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

If this is of any use for future research I compiled the code and it returned 
the following error message SetWindowLong(m_AppWin, GWL_STYLE, lStyle); "A call 
to PInvoke function 'SuperPutty!SuperPutty.ApplicationPanel::SetWindowLong' has 
unbalanced the stack. This is likely because the managed PInvoke signature does 
not match the unmanaged target signature. Check that the calling convention and 
parameters of the PInvoke signature match the target unmanaged signature."

Original comment by [email protected] on 6 Mar 2012 at 6:20

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Quote:
"Comment 8 by [email protected], Nov 16, 2011
If others are seeing this behaviour in Win7 then please try running in WinXP 
SP3 compatibility mode as this certainly solves the problem for me."

On Win7 this resolved my issue with the terminal session not attaching to the 
SuperPutty window.

Thank you OP!

+1 - Comment 8 by [email protected], Nov 16, 2011

Original comment by [email protected] on 25 Apr 2012 at 1:34

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Fix in issue 92 seems to resolve these problems.  

Original comment by [email protected] on 28 May 2012 at 9:46

• Changed state: Duplicate
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Thanks whippyhu. Changing the compatibility mode to Windows XP SP3 on my 
Windows 7 (64bit) computer worked for me too. However I would like to add that 
this was working for me without setting the compatibility mode until today. My 
SuperPutty version: 1.3.0.1

Original comment by [email protected] on 20 Aug 2012 at 7:16

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Issue was fixed for as soon as I set up both Putty executable and PuttyCM in 
compatibility mode to Windows XP SP3 on Windows 7.

Original comment by [email protected] on 29 Sep 2012 at 4:04

• Added labels: ****
• Removed labels: ****