Baffled by application that works and then just dies.

  • Thread starter Thread starter Teflon
  • Start date Start date
T

Teflon

WinXP Pro SP2.

A recently installed application (App A) runs fine immediately after
a reboot. It can be closed, re-opened, multiple times, and continues
to work fine. However, after any other app launches, App A can not be
started again. Double clicking on App A's .exe gets the hourglass /
cursor for a bit, then nothing. App A is not listed in Task Manager's
Application window, but App A's .exe is listed in Task Manager's
Processes. Ending the AppA.exe process does not help, AppA will not
start. Have to reboot to get it to start again.

It seems to me that either some other process starts and blocks App
A's .exe from completely launching, or a process required by App
A's .exe becomes disabled.

I am at a loss as how to proceed to de-bug this problem, let alone fix
it.

As I said, if I reboot the machine, App A works fine until another app
starts, then, nothing, and this is the only application this is
happening to. Every other app on this machine is working.

App vendor is no help, says it is an OS problem, which is probably
correct. That's why I'm here.

Ideas, suggestions?
 
App A sounds like a top secret Piles remedy, Bill. It sure WOULD help
Click to expand...
if we knew more. :-)


It ALWAYS helps to know more. 'AppA' is Nova Development's Berlitz
Spanish Language Course - I just thought it was easier to shorten that
to 'AppA'.

Now that you have that 'missing' nugget of information, what's the
solution?

BTW, for those hemorrhoid problems, try Tronolane. Now you REALLY
know more.
 
Teflon said:
It ALWAYS helps to know more. 'AppA' is Nova Development's Berlitz
Spanish Language Course - I just thought it was easier to shorten that
to 'AppA'.

Now that you have that 'missing' nugget of information, what's the
solution?

BTW, for those hemorrhoid problems, try Tronolane. Now you REALLY
know more.
Click to expand...

Contrary to what you were told by the vendor, and given what you have
written in the original post, I still believe the problem lies with your
app, and not windows. Why? Because the problem is unique to running
their app, and only their app, from what you said. (The fact that they
"brushed it off" and said it's a operating system problem is not totally
surprising).
 
Back
Top