Just reinstalled puppy using a frugal install of 2.16.1 of course one of the first things I did was to add Ezpup !

All went well, only a couple of things Im not sure of..'Xlock' Icon is visible but clicking on it nothing happens & 'Blinky' has a grey square around it instead of blending in with the black taskbar like it used to..

Not sure if this has anything to do with using a frugal install for the first time or perhaps something diff with Ezpup 2 ?

I removed .Xlock from root and Xlock again worked but after rebooting it comes back to stop Xlock working.

If you click on xlock to "test" that it's working, and you don't enter a password, you get a corrupt (null) encrypted password. Simply delete the /root/.xlock.rc file again and this time either don't click on xlock to test, or use a password you can remember and let xlock start.

ohyes wrote:

For Blinky looks like I do have whats required..though below is my startup just incase something is wrong with it

Yes, your line for Blinky in startup is ok. Blinky picks up (for transparency purposes) the first taskbar background after it is started with the transparency option.

I suggest you comment out the line containing Blinky and reboot into your preferred theme. Then uncomment Blinky in startup and use Ctrl+Alt+Backspace to exit to prompt. Restart IceWM with the full "xwin starticewm" commandline. Blinky "should" then pick up its transparent background from the current taskbar.

Hope that helps._________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

Also tried overwriting with installing Ezpup again didnt do anything for me.

Edit startup to give blinky a background color - format as -bg "#ffffff" - shutdown and restart with the new color to ensure that blinky is reading the -bg switch. Then repeat process removing color data and leaving -bg "", shutdown and restart. Blinky should pick up the correct background info.

Also, double check that you have ColorNetIdle="" in either your /root/.icewm/preferences file or the default.theme file for the theme you are using. If that doesn't work, then I don't know what else to tell you, ohyes._________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

.. when I fire blinky up it shows the colour of the chosen theme every time ignoring any colour parameter I put in the bg switch

Hmmmm...which Gtk Themechooser did you use ... the old default or the one titled MU-Gtk-Themechooser? Using the old one at some time since installing EZpup may have overwritten something on your system.

Try reinstalling the MU-Gtk-Themechooser from PSI and rebooting. Then select Aero as the default theme. Then reboot to restart X and reload any libraries and see what happens when you reset blinky to transparent as suggested in a previous post.

Hope that helps._________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

it's working now ..not sure why...though Im not game to try and break it

Edit:Played with Mu Theme chooser...if i pick another theme blinky ends up with the theme colour border .. the inner is still black.. so to get around that I m using Aero Clone theme..which blends black
So almost fixed..

I had played with the default GTK Theme and also MU GTK theme chooser so maybe something is wrong there but the problem started before touching either theme choosers.

One thing I noticed when running/starting Blinky from the console is that you get the application messages echoed ..in this case 'blinky'
though I couldnt make sense of what it was telling me.

it's working now ..not sure why...though Im not game to try and break it

Hey, if it aint broke don't fix it!

Blinky was meant to run under JWM, not Icewm. It was patched for IceWM by MU using eggtrayicon or something like that. I happen to like blinky, but Icewm has its own Net monitoring on the task bar. I guess it's one of those not so important issues.

Glad you've got it back to where it was._________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

Blinky was meant to run under JWM, not Icewm. It was patched for IceWM by MU using eggtrayicon or something like that. I happen to like blinky, but Icewm has its own Net monitoring on the task bar. I guess it's one of those not so important issues.

I commented out blinky so it's not anymore on the taskbar, but where is icewm's net monitoring?
How is it activated for the task bar?

Also volume and wmpower now creates a little sepate window and not a task bar item.

Freemamapplet has improved and it's a little blue block, but not large enough to display the value. Only two digits are displayed.

Also volume and wmpower now creates a little sepate window and not a task bar item.

wmpower is an icedock applet, and needs icedock enabled in /root/.icewm/startup.

There is also a volume applet for icedock, but I prefer to use Pvolume from the menu. It will start as a full app window, but minimising the window puts on the taskbar as an icon. You could also start it from an icon on the taskbar. See the EZpup Help wiki page for links to the manuals for Icewm and Rox and for tips and tricks for customising EZpup.

Béèm wrote:

Freemamapplet has improved and it's a little blue block, but not large enough to display the value. Only two digits are displayed.

This one is beyond me to resolve. The version of Freememapplet I provided in EZpup-2 was patched for IceWM by MU. Instead I prefer to use the Disk Free icon on the desktop which calls Partview to display free space on the mounted partitions. Alternatively you could run conky on the desktop and have all the stats you could ever want.

Hope that helps._________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com