G'day zigbert,
I think the default Temp-CPU widget was created by forum member Trio to watch for high temperatures in his EEE laptop. His widget was specific to only this computer.
For running on any other computer, the temp-cpu pwidget config needs editing to use the data from the temperature reporting module(s) of this other computer.
If the computer has no such module then the widget will not work.
My rough 'how to' maybe get Temp-CPU to work on a different computer:
1) find the module with which your computer can view its operating temperatures - Puppy's Boot Manager can test load modules to see if it's the one you need. There could be other ways to find if your CPU has such modules.
2) load on booting the temperature module - e.g. coretemp is a fairly common one - it's on my ~10-year old laptop; my ~15 year old HP desktops use an smsc47b397 module so you may need to hunt around if it is not an obvious one like 'coretemp!
3) run sensors in the terminal to see what and how the data are displayed - load lmsensors pet or sfs if the terminal replies it's not loaded.
4) in your text editor, open the existing Temp-CPU (temp-cpu) widget config file - in /usr/local/pwidgets/widgets/configs/
5) edit the TEXT lines at bottom of the default Temp-CPU widget to extract values from the lines of the terminal sensors output and display these in the Temp-CPU widget.
trial and error with grep, cut and sed commands eventually worked for me - I have no idea what 'grep', 'sed' and 'cut' do, but my guess is one says which program to get detail from ('sensors'?), one to choose which lines in the output to use, and the other how to choose which bits of those lines to cut for display.
5) colour the widget display and pick the font size and placement - pretty it up if you know how
6) save the new Temp-CPU config file
Examples
My desktop's config for its smsc47b397 module:
#this is a Pwidgets config file
#the actual building of the graphics is defined in bottom of this file, - after 'TEXT'.
#need cpu temp monitor module found and loaded
#lm-sensors loaded to show display of module output
#edit TEXT lines to display parts of output in widget with grep, cut and sed
#### PWIDGETS #####
HEIGHT=240
OFFSET_X_LEFT=1080
OFFSET_X_RIGHT=20
#### CONKY ####
#COLORS --- 0:headings 1:base-info 2:extra-info 3:markers 5:green 6:red
#Colors are defined in theme-files, - NOT here.
color0 A2914E
color1 666666
color2 bbbbbb
color3 ffab00
color5 499D3A
color6 red
background no
own_window yes
own_window_type roxdesktop
#own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
own_window_transparent yes
own_window_colour hotpink
double_buffer yes
total_run_times 0
update_interval 1
minimum_size 180 5
draw_shades yes
draw_outline no
draw_borders no
stippled_borders 2
border_margin 4
border_width 1
default_color white
default_shade_color 333333
default_outline_color red
no_buffers yes
uppercase no
use_spacer none
#font fixed
use_xft yes
xftfont dejavu:size=9
TEXT
${font pdingobats2:size=20}${color4}z${font :size=12}${color yellow} CPU Temps
${font :size=9}${color pink} ${execi 33 sensors | grep -A 9 'smsc' | cut -c1-25 | sed '/^$/d'}
${color green} Frequency core1: $alignr$color${freq freq(0)} Mhz
${color1} Frequency core2: $alignr$color${freq freq(1)} Mhz
My Samsung laptop config with its coretemp module is:
#this is a Pwidgets config file
#the actual building of the graphics is defined in bottom of this file, - after 'TEXT'.
#### PWIDGETS #####
HEIGHT=130
OFFSET_X_LEFT=1140
OFFSET_X_RIGHT=20
#### CONKY ####
#COLORS --- 0:headings 1:base-info 2:extra-info 3:markers 5:green 6:red
#Colors are defined in theme-files, - NOT here.
color0 A2914E
color1 666666
color2 bbbbbb
color3 ffab00
color5 499D3A
color6 red
background no
own_window yes
own_window_type roxdesktop
#own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
own_window_transparent yes
own_window_colour hotpink
double_buffer yes
total_run_times 0
update_interval 1
minimum_size 180 5
draw_shades yes
draw_outline no
draw_borders no
stippled_borders 2
border_margin 4
border_width 1
default_color white
default_shade_color 333333
default_outline_color red
no_buffers yes
uppercase no
use_spacer none
#font fixed
use_xft yes
xftfont dejavu:size=9
TEXT
${font pdingobats2:size=20}${color4}z${font :size=12}${color yellow} CPU Temps
${font :size=9}${color pink} ${execi 33 sensors | grep -A 9 'core' | cut -c1-20 | sed '/^$/d'}
${color green} Frequency core1: $alignr$color${freq freq(0)} Mhz
${color1} Frequency core2: $alignr$color${freq freq(1)} Mhz
The above coretemp config should/could/might work as-is if you have a coretemp-moduled CPU?
In both config examples, it's the 'TEXT' section at the end, and the second line of that in particular, that determines if this widget will display properly.
If it does work but looks tatty, then prettying it up and fitting to your monitor needs fiddling around with other lines of this config as well.
Unfortunately, not a "one-size-fits-all" widget as far as I can see
.
David S.