Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: j_75080 on December 31, 2010, 05:12:27 PM
-
Hello,
I have a old IBM ThinkPad 365XD with Tiny Core Linux 3.4 installed, but have no wbar starting. I tried to start wbar from the command line and received the message "Using /home/tc/.wbar config file. --> Image not found. Maybe using a relative path?"
In addition, wbar is missing when booting from the Tiny Core LiveCD on this laptop. It does not show up in the process list.
Using the LiveCD on a Dell Latitude PII laptop or on a P4 desktop yields a working wbar which shows up in the process list when giving the "ps -e" command.
Could someone lead me to a solution for my missing wbar?
Thank you,
j_75080
-
the wbar extension sometimes changes with new versions of tc - are you sure you have the latest version of the extension?
-
I used Tiny Core Linux v3.4 LIveCD which has wbar included. As I stated, the LiveCD worked on PII and P4 computers, but not on this PI.
To make sure wbar was the latest version installed in my PI laptop, I went to the Tiny Core's repository, downloaded the current v1.3.3-3 version, and loaded in the PI laptop using Apps Audit. It still would not work.
If the LiveCD will not load wbar in this PI 72MB RAM laptop, is their some requirement that is not being met?
-
Do you refer to the plain CD, or perhaps with restoring backup or use a PPR?
-
I used the tinycore-current.iso burnt to a plain CD. The CD was used to install Tiny Core Linux 3.4 on the PI laptop also.
-
I don't know if it'll help your problem, but a TC 3.4.1 version has been released which includes a change to wbar.
-
Wbar does not start when any of the icon images can't be found. Have a look to see if any are missing then we'll go from there.
-
I read this earlier and it was probably a post of yours. So, I went into wbarconf and excluded all applications believing wbar would appear with no icons since there are no applications. Also, it should not be a an icon image problem if the LiveCD will not display wbar - aren't these needed econ images also on the LiveCD.
-
Well, a quick check of all the icon files could be achieved with sed -e '/^i:/!d' -e 's#^i:##' /usr/local/tce.icons | xargs ls -l, but I tend to agree that those should all be present as they are included in the initrd of the ISO.
Now, to undertake a bit of troubleshooting may I suggest:
(1) Make sure that really no 'wbar' process is running (e.g. via ps | grep wbar).
(2) Execute 'wbar' directly (without any "wrappers" and suppression of error messages):
wbar -bpress -config /usr/local/tce.icons
I'd expect that you get some error messages which might help a bit further ...
-
After working with my original tce.icons, I booted Tiny Core 3.4 on my P4 PC and saved the tce.icons file (511Bytes) on the LiveCD to a floppy. I copy the floppy's tce.icons file to my laptop's Tiny Core 3.4 /usr/local/directory replacing the original tce.icons file (103Bytes). Nothing changed.
Later, I have upgraded to Tiny Core Linux 3.4.1 and wbar still does not work.
Giving the sed -e '/^i:/!d' -e 's#^i:##' /usr/local/tce.icons | xargs ls -l command, now yields
-rw-r--r-- 1 root root 2591 Mar 28 2010 /usr/share/pixmaps/appbrowser.png
-rw-r--r-- 1 root root 2756 Apr 18 2010 /usr/share/pixmaps/aterm.png
-rw-r--r-- 1 root root 4293 Mar 28 2010 /usr/share/pixmaps/cpanel.png
-rw-r--r-- 1 root root 4340 Nov 19 2010 /usr/share/pixmaps/disk.png
-rw-r--r-- 1 root root 3119 Nov 19 2010 /usr/share/pixmaps/fluff.png
-rw-r--r-- 1 root root 3366 Nov 19 2010 /usr/share/pixmaps/gear.png
-rw-r--r-- 1 root root 3398 Nov 19 2010 /usr/share/pixmaps/power.png
-rw-r--r-- 1 root root 1184 Apr 18 2009 /usr/share/pixmaps/osxbarback.png
There is absolutely no wbar process on my PI laptop althought it shows on my P2 and P4 computers.
ps | grep wbar yields no process.
wbar -bpress -config /usr/local/tce.icons yields the following error as user and as root:
Using /usr/local/tce.icons config file.
Using a Super Bar.
Illegal instruction
Thank you for your help,
j_75080
-
My hunch is that the CPU on your "troubled" system is too old to cope with the '/usr/bin/wbar' executable.
Maybe it would need to be re-compiled to be compatible with your CPU. I'd suggest you try that yourself, as it might be difficult to convince the Core team to support a specific build for a system that might be more than 13 year old (if the page (http://www.thinkwiki.org/wiki/Category:365XD) is to be trusted).