![]() ![]() |
Jul 24 2007, 03:43 AM
Post
#1
|
|
|
Follow the rules please :-) Group: Patrons Posts: 6783 Joined: 14-November 03 From: Bangalore, India Member No.: 9470
|
Sometimes, programs take quite long to startup (or process something for a long time).
Vista interprets this as an application crash, and asks whether you want to close the errant program. The problem is, the program hasn't crashed actually, and if only the dialog-box asking you to close didn't appear, the program would continue running peacefully. There's no option for you to tell Windows to ignore the program & allow you to resume using the program. I have tried disabling some relevant services (diagnostic ones that monitor the system), and looked for registry-policies that might control this dialog, and looked through gpedit.msc too. A screenshot is attached below, error dialog is on left side, and program is running but "inactivated" by vista on the right side. There has got to be a setting to disable this action, whether unattended or manually. HOW CAN I DISABLE THE DIALOG BOX SHOWN BELOW?
Capture.JPG ( 62.66K )
Number of downloads: 28 |
|
|
|
Jul 24 2007, 04:11 AM
Post
#2
|
|
|
The Guy from Aus ![]() ![]() ![]() ![]() ![]() ![]() ![]() Group: Members Posts: 1546 Joined: 14-November 03 From: DownUnder Member No.: 9474
|
@Prath
Pretty sure Sig is working on it but the Integrator is not compatible with Vista atm? Not working for me here either. |
|
|
|
Jul 24 2007, 04:28 AM
Post
#3
|
|
|
Follow the rules please :-) Group: Patrons Posts: 6783 Joined: 14-November 03 From: Bangalore, India Member No.: 9470
|
Well, this might not be a fault of the Integrator, because for all practical purposes its still running fine (and many other apps too).
This is actually seeming like an over-enthusiastic system diagnostic tool, monitoring for crashes but not quite identifying the status correctly, which can (and should) be disabled. |
|
|
|
Jul 28 2007, 03:04 PM
Post
#4
|
|
|
Windows XP PowerPacker Creator Group: Supreme Sponsors Posts: 709 Joined: 22-January 05 Member No.: 41734 OS: none
|
This issue is fixed in v1.5 of the integrator... which I will hopefully be releasing soon. v1.5 has been completly re-written to take advantage of the latest benefits of autoit development.
Basically that error was caused by the way I was doing md5 hash checking. I don't know if it had to do with some sort of memory leak in vista or what. but I completly changed the method of md5 hash checking and now it works smoothly. There have been so many changes in the code for v1.5 that it has been going through extensive beta testing. I want to try my best to work out any bugs before releasing it to the public. Anyone who wants to beta test is welcome to sign up at http://siginetsoftware/forums and request to be added to the beta testers forum. It would be an honor to have you there prathapml. Thanks for everything you have done for me in the past as well. |
|
|
|
Jul 30 2007, 02:08 PM
Post
#5
|
|
|
Follow the rules please :-) Group: Patrons Posts: 6783 Joined: 14-November 03 From: Bangalore, India Member No.: 9470
|
Am glad to hear that the problem is (almost? coz its still beta) solved
Waiting for final release! |
|
|
|
Aug 2 2007, 02:20 PM
Post
#6
|
|
|
Group: Members Posts: 1 Joined: 1-August 07 Member No.: 148990 OS: Vista Business x86
|
I am having this problem as well with winamp, I am excited to see if the fix works for it... I really don't want to do a clean re-install of winamp again.
|
|
|
|
![]() ![]() |
| Lo-Fi Version | Time is now: 9th February 2010 - 09:43 AM |