Main Area and Open Discussion > General Software Discussion

How to detect parent .EXE from tray icon?

<< < (2/2)

rjbull:
The app will still be running in the background (which is why Ath's KeepUpApp probably won't help) but there just won't be a tray icon for you to be able to access the app from.-app103 (March 17, 2013, 07:24 AM)
--- End quote ---
Yes, that sounds about right; I haven't investigated fully, but suspect the apps are all there, I just can't see them.  Many thanks!

I wrote an app to try to simulate the process of waiting, clicking shortcuts, and waiting some more.-app103 (March 17, 2013, 07:24 AM)
--- End quote ---
I already run WinPatrol Plus with some programs run Delayed, and should have thought of that  :-[  It's nice to see your free delayed-startup program; who better than that scary taskbar girl  :)  As you point out, it may be tedious to figure out and organise the correct amount of delays.

@anandcoral:
I don't see that particular feature in Pitaschio's Features list, but I'll take a look.  Thanks for the pointer!

anandcoral:
Hi rjbull,

In case you have problem in finding the required feature, I am giving below the screen shots from my machine.

The below window comes after you right click on the tray icon and select 'Settings'.






Hope it helps you.

Regards,

Anand

Tinman57:
  This has been a problem that MS has refused to fix since XP.  I found a hack that reverses this problem, though I'm not sure if there's a Vista version or not.  Here's a snippet that I copied for future reference:

SpoilerSystray icons missing problem
-----------------------------

Some Windows XP installations show a peculiar defect in that some systray icons do not appear when the system is booted and the user logs on. The problem seems even more noticeable on systems with autologon and/or with many applications (with systray icons) running at startup.

According to the excellent analysis in the "Problem analysis and proposed solution" comment by "tasmanian" user at http://winhlp.com/node/16?page=1&cs=2231#comment-406 this is caused by a timing defect in the Windows function Shell_NotifyIcon in shell32.dll, which has a timeout fixed at 4 seconds. Combined with an unfavorable Windows API message this causes the problem, which befalls many heavily loaded computers that don't have ultra-fast hard disks. Changing the timeout to one minute and removing the unwanted message solves the problem.

This Patch Tool
---------------
Tired of manually applying the patch each time MS updates shell32.dll or on new Windows installs I decided to create this patch tool, it will easily patch shell32.dll file according "tasmanian" purposed solution, it should work with any version of shell32.dll as it will automatically find the correct offset for the bytes to patch.

Thanks
------
tasmanian - for the excellent analysis and proposed solution
WinHlp.com - for supporting all the discussion about this problem

rjbull:
In case you have problem in finding the required feature, I am giving below the screen shots from my machine.-anandcoral (March 18, 2013, 03:23 AM)
--- End quote ---
Many thanks!  :)  I wouldn't have found that, even though I know perfectly well that my sticky notes program makes all its notes hidden windows.  Pistachio is an interesting utility; pity it doesn't show icons as well in that list.

@Tinman57: thanks - did a quick check on the original pages, but they don't seem to have a known solution for Vista.

Tinman57:
In case you have problem in finding the required feature, I am giving below the screen shots from my machine.-anandcoral (March 18, 2013, 03:23 AM)
--- End quote ---
Many thanks!  :)  I wouldn't have found that, even though I know perfectly well that my sticky notes program makes all its notes hidden windows.  Pistachio is an interesting utility; pity it doesn't show icons as well in that list.

@Tinman57: thanks - did a quick check on the original pages, but they don't seem to have a known solution for Vista.
-rjbull (March 19, 2013, 04:03 PM)
--- End quote ---

  Darn rjbull, sorry to hear that.  You would think that someone would have done the same for Vista.  I haven't had this problem since I did this hack until MS released a new version of shell32.dll last year.  I just re-ran the patch and back to happiness again....

EDIT: I got to reading some more on this problem and the patch.  From what I can see, the patch works for any version of the shell32.  Give it a try and see.
  NOTE:  Backup your original shell32.dll just in case.  I'm not familiar with Vista and how it may (or may not) automatically restore the original .dll.  You may have to copy the patched .dll to your cache, and possibly to other "Backup" locations in the OS.

  If you don't feel comfortable running this patch, you can get the offset information from the website, and using a hex editor make the changes manually.  Good luck....

Navigation

[0] Message Index

[*] Previous page