Robert in CA wrote:
On Friday, February 14, 2020 at 10:35:30 PM UTC-8, Paul wrote:
Robert in CA wrote:

snippage
I have a question involving the 8500. Whenever I click
the SuperantiSpyware icon on the 780 it comes up with no
problem but when I click the same icon on the 8500 I
have to do it twice before it comes up.

My question is; why do I have to click it twice on the 8500
and is there a way so that I only have to click it once?

Thanks,
Robert
It's unlikely that someone has "looked at the undercarriage
of every program out there", to answer this without doing some work.

I would use Process Monitor.

https://docs.microsoft.com/en-us/sys...nloads/procmon

1) Start the procmon.exe running.
2) Go back to the desktop, double click SuperantiSpyware.
The program fails etc.
3) Return to Process Monitor program window.
In the File menu, untick the tick mark to stop the trace.
4) In the filter menu, select

Program Name is procmon.exe Include

and apply that filter to the now-frozen trace.

This reduces the amount of junk to look through.

5) See if you can see any file it was accessing before it
quit or dropped dead.

That's about the best I can offer, in terms of a
"what approach could I use".

Even if I installed the program here, you just know
SAS isn't going to drop dead for me, and I won't
be able to reproduce it.

Paul

I tried to follow your instructions but it
didn't offer anything to untick and filters
and when I opened filters it didn't seem to
offer procmon.exe

Process Monitor

https://postimg.cc/3yhq8tZG

File Menu

https://postimg.cc/Xpwcj412

Filter menu

https://postimg.cc/K4TtfmbZ


Thanks,
Robert

In your picture, the ProcMon program window has a "File"
menu item. Click that and you should see a "tick mark".
That "tick mark" controls capturing. You untick the
tick mark under the File menu, to stop the tracing action.

You want Filter : Filter item to select the filters
desired for the output trace. Setting a filter reduces
the visual amount of output seen, hiding the irrelevant
stuff. The Filter menu and its subitem "Filter" exist,
because of the nature of hunting for a "needle in a haystack".

The trace runs at lightning speed, and you can end up with
100,000 entries in seconds. And then having to shovel through
those can be painful.

By setting the filter to just include SuperantiSpyware items,
the job of analysis will be a little easier. You would then
scroll to the bottom of the trace, and see where SAS is exiting.
Then look a little above that, to see "what file is it ****ed about".
Something happened to upset it. That's what you would be
looking for.

This isn't easy to do, this needle in the haystack stuff.

To give you an example, I got lucky once. I'd installed
two sound cards. After the installer for the second
sound card was installed, *both* sound cards would not
work. I was baffled as to how that could happen. I ran
a trace with ProcMon, and there were a hundred thousand
entries to go through. And just by accident, I saw a
registry entry. It was an entry the second card should
not have "clobbered". I returned the registry entry
to a "normal" value and *both* sound cards worked.
Then all you had to do, was select in the Windows control,
which sound card you wanted to use for your output.

Many times I use that tool and learn... nothing.

That's why it's a tool of last resort.

But in theory, it has a lot of information to offer.
It's a matter of human persistence, as to whether
anything can be learned from it.

What leaves me in awe, in those traces, is all the
bull**** the OS is doing underneath. Quite often in there,
I'm distracted by the stuff I'm seeing.

*******

In terms of program design, if the program discovers a copy
is already running, it may choose to terminate. You might
check Task Manager and see if a copy is running at the time
you try your first "click". A good program would print on
the screen, that it had discovered a copy already running.

Paul