Post by robmw on Nov 23, 2005 8:06:19 GMT -5
Hi Bill,
Congrats on your 'semi-retirement' - I can fully appreciate the time it must take to create all this stuff, it takes me far more time than I really have just to enjoy it
Hopefully though you are still checking the forums for some of your older creations so here goes with my question.
I was recently trying to fly the Grumman Goose which I purchased as payware, after a few weeks of doing other things on the PC and I've run into a problem.
Basically the plane will not load into FS9 and exits with an error saying that a debugger is installed. This immediately tipped me off to the likely source of the problem as I have recently installed debugging tools for Windows in order to use an application called Process Explorer from sysinternals - all this since last flying your plane without any problems. I therefore uninstalled the debugger using it's uninstall option, rebooted my machine and tried to load the plane again. Unfortunately the same error was reported.
It seems that at least part of the debugger is still installed such that it can still be detected as being present. This is confirmed by the fact that the other application, Process Explorer, still runs without error whereas it originally asked for the Windows debugger to be installed. This behavior is also exhibited on my PC at work (for Process Explorer) so I know it's independent of any software components your plane is using.
Despite a lengthy search for information on how to manually uninstall the Windows debugger or what features it might expose that would enable it to be detected and a search for remaining files and disk, registry entries, environment variables etc, I've come up with a blank. I'm therefore stuck at the moment without being able to fly the Goose
, . I should say that I have many other payware planes from the likes of Flight1, FSD, Aerosoft and none of these are affected, nor is any aspect of FS9 impacted to the best of my knowledge.
As I originally purchased these before they became freeware, is there any help you could give me in identifying what is being detected regarding the debugger such that I can perhaps manually remove it? I realise that the check is probably there for a reason but I cannot see any other way of continuing to fly the Goose without re-installing Windows, which with the complexity of my flight sim setup is not an option I wish to even contemplate!
I realise that you might not wish to post a reply on the public forum but this was the only way I could find to contact you.
Yours hopefully,
Rob White
Congrats on your 'semi-retirement' - I can fully appreciate the time it must take to create all this stuff, it takes me far more time than I really have just to enjoy it
Hopefully though you are still checking the forums for some of your older creations so here goes with my question.
I was recently trying to fly the Grumman Goose which I purchased as payware, after a few weeks of doing other things on the PC and I've run into a problem.
Basically the plane will not load into FS9 and exits with an error saying that a debugger is installed. This immediately tipped me off to the likely source of the problem as I have recently installed debugging tools for Windows in order to use an application called Process Explorer from sysinternals - all this since last flying your plane without any problems. I therefore uninstalled the debugger using it's uninstall option, rebooted my machine and tried to load the plane again. Unfortunately the same error was reported.
It seems that at least part of the debugger is still installed such that it can still be detected as being present. This is confirmed by the fact that the other application, Process Explorer, still runs without error whereas it originally asked for the Windows debugger to be installed. This behavior is also exhibited on my PC at work (for Process Explorer) so I know it's independent of any software components your plane is using.
Despite a lengthy search for information on how to manually uninstall the Windows debugger or what features it might expose that would enable it to be detected and a search for remaining files and disk, registry entries, environment variables etc, I've come up with a blank. I'm therefore stuck at the moment without being able to fly the Goose
, . I should say that I have many other payware planes from the likes of Flight1, FSD, Aerosoft and none of these are affected, nor is any aspect of FS9 impacted to the best of my knowledge.As I originally purchased these before they became freeware, is there any help you could give me in identifying what is being detected regarding the debugger such that I can perhaps manually remove it? I realise that the check is probably there for a reason but I cannot see any other way of continuing to fly the Goose without re-installing Windows, which with the complexity of my flight sim setup is not an option I wish to even contemplate!
I realise that you might not wish to post a reply on the public forum but this was the only way I could find to contact you.
Yours hopefully,
Rob White
I now have some more troubleshooting experience on hand for the future!