Page 2 of 5

Posted: Thu 18 Jan 2007, 16:55
by polux
Im running Muppy 007 from CD in 2 laptops. One is a Compaq Presario, AMD Athlon XP2000, 500 RAM, no Hard Disk and with a US Keyboard, the other is a IBM T41 with German keyboard.

No problems with the keyboard layouts in both. Everything works Ok. :)

I love my Muppy :twisted:

Muppy007 Service Packs

Posted: Thu 18 Jan 2007, 18:23
by jam
Mark,

Can't see Muppy007 service packs when using the PSI installer. I can install manually so it's no big deal, but I'm spoiled using PSI! :)

Posted: Thu 18 Jan 2007, 18:58
by Sage
Apart from laptops, which I tend to avoid, there's a simple answer to using the full version of Mark's masterpiece. Fit one older CD drive to read and boot from and fit a more modern DVD/CD-RW/DVD-RW for running, saving, watching, burning stuff. Ideally, choose an older drive made after ~1997 with a speed >x20 if you want to boot to a CD-RW/DVD-RW image, but almost anything will boot to a CD-R. Nobody wants old CD drives any more so they can be canabilised from the local skip/tip/dumpster; around 50% are likely to be still working!!

VESA / Xorg Auto-Detect

Posted: Thu 18 Jan 2007, 20:32
by jam
Mark,

Would it be possible to auto-detect whether to use Xvesa or Xorg depending on the graphics card? There are problems using Xvesa with Intel chipsets, yet Xorg works just fine so I was wondering if it would be possible to revert to Xorg if an Xvesa functionality probe fails.

Muppy 007 trayicons

Posted: Fri 19 Jan 2007, 09:51
by tronkel
Hi Mark,

Congratulations again on a great version of puppy. It is running very fast on my 400MHz processor with 192MB RAM and 500MB swapfile. Faster than Puppy 2.13. and also KDE is extremely usable for the first time ever on this PC

I wonder what I am doing wrong here with the icewin trayicons. Even if I associate an application-specific icon with the shortcuts contained in the /root/trayicons folder, they do not appear in the icewin tray even after having been refreshed using the >> and << buttons. Not an urgent problem. Have a good day! :D

Best regards

tronkel (Jack)

Posted: Fri 19 Jan 2007, 17:03
by MU
you must right-click the ">>" button.
This opens a drag-area (right-click to close it).
Drag programs on it, then left-click on ">>" and then "<<".
Mark

Posted: Fri 19 Jan 2007, 19:46
by primalphunk
Looks good but like Sage I have been unable to get the correct keyboard map(US in my case) to load.

peace,
James

Posted: Fri 19 Jan 2007, 20:08
by MU
ah I see, I think it the keyboard-wizard has a bug with UTF-settings.

Please type in a consolewindow:

export LANG=C
input-wizard


If it works then, I'll add it to the servicepack.
Mark

Icewin trayicons

Posted: Fri 19 Jan 2007, 20:46
by tronkel
you must right-click the ">>" button.
This opens a drag-area (right-click to close it).
Drag programs on it, then left-click on ">>" and then "<<".
Mark
I tried what you suggested Mark, but the only application icon that appears after using the drag area and the >> and << buttons, is the generic puppy cog-wheel icon.

Is there any linux command I could use that would refresh the configuration relating to associated program icons for the traybuttons perhaps?

I wonder if anyone else has experienced this problem.

Thanks

tronkel (Jack)

Posted: Fri 19 Jan 2007, 21:07
by MU
ah I see, it uses the globicons from rox 1.2.

Workaround: edit:
/usr/local/MU-rox-traybuttons/resource/run-mu_rox_traybuttons

replace line 14:

Code: Select all

globicons = readfiletolist("/root/Choices/ROX-Filer/globicons")
with:

Code: Select all

globicons = readfiletolist("/root/.config/rox.sourceforge.net/ROX-Filer/globicons")
I will have to add a check, that finds out if rox1 or rox2 is activated.
Mark

Icewin trayicons

Posted: Fri 19 Jan 2007, 21:50
by tronkel
Thanks Mark, that has fixed it. Would you please upload a revised script with the revisions for checking the ROX version when you have a spare moment. I know you are busy with work and Muppy - so anytime will do - not urgent :D

tronkel (Jack)

Posted: Sat 20 Jan 2007, 02:26
by primalphunk
MU wrote:ah I see, I think it the keyboard-wizard has a bug with UTF-settings.

Please type in a consolewindow:

export LANG=C
input-wizard


If it works then, I'll add it to the servicepack.
Mark
It was a little bit of a challenge finding the correct keys to type this at the console...maybe I should have just pasted each line...We all get a little smarter in retrospect... heheh

Muppy did not complain about the first line but when I typed the second one here is what was returned.

sh: input -wizard command not found

So that didn't appear to fix it for me. Do I need to be in a different directory or something? Remember...I'm still a stupid newbie so I am often oblivious to the obvious.

peace,
James

Posted: Sat 20 Jan 2007, 04:44
by MU
input-wizard
not
input -wizard
Note the space you have typed before the "-".
Mark

Posted: Sat 20 Jan 2007, 13:15
by primalphunk
MU wrote:input-wizard
not
input -wizard
Note the space you have typed before the "-".
Mark
Actually I have tried it multiple times without the space. It's just when the error is returned to me that the shell inserts a space in it's output...

peace,
James

Posted: Sat 20 Jan 2007, 14:47
by primalphunk
This is my best effort to be helpful and give you a lot of feedback about my keymap issue.

I'm not familiar with azerty keyboard maps...so I previously used quite a bit of trial and error in the vain hope of finding the right keys.

Thinking that perhaps I used a -(minus in mathematics) when I should have used a -(hyphen) I decided to try your suggestion again but this time I used konsole and just did a cut and paste of your text. My results were different this time. The second command launched the kb selector gui and I was able to select us keymap. There were no Gdk errors as I experienced when simply fishing around for a solution on my own. It even seemed to have worked for a time.

I decided to logout to the command line and try xwin starticewm just to see if the changes had stuck.(Maybe I sabotaged my best efforts right there?) The keymap was unfortunately for me set back to an azerty one. I retried the commands and the dialog boxes that popped up in the kb selector gui seemed to indicate success but when the real test came...trying to type w, z, a and whatnot in a text editor it was again back to azerty.

I kept messing about with things and at times when I selected the keyboard and mouse setup tool I produced an error message like below.
(process:3466) Gdk warning **: locale not supported by Xlib
(process:3466) Gdk warning **: cannot set locale modifiers us.map" keyboard map

There were even times after rebooting that the system would pause 60 seconds with similar warnings about the keymap failing to load.

I took a look at the /etc/keymap file and it did indicate a us keymap was loaded. Later, after producing some of the Gdk error messages I listed I found something of the error messages themselves in the same text file.

peace,
James

Posted: Sat 20 Jan 2007, 15:57
by MU
ok, as a workaround:

edit /etc/profile

replace
LANG=en_US.UTF-8
with
LANG=en_US

Then reboot.

Then this locale error should be gone.
I will try to check more carefully, what programs are affected by that error.

Mark

***edit*** note for me: bugreport: kppp from menu does not work:
http://murga-linux.com/puppy/viewtopic. ... 1913#91913

**edit2**
chooselocale-bugfix:
http://www.murga-linux.com/puppy/viewto ... 2187#92187
**edit3**
colorselect-bugfix:
http://www.murga-linux.com/puppy/viewto ... 2056#92056

Posted: Wed 31 Jan 2007, 08:13
by MU
updated the servicepack for 007.

Fixed:
added "grey" to icedock-colors
fixed rox-traybuttons to detect what rox is active
kppp now launches from Icewm-menu
chooselocale and input-wizard now work with UTF-8 locales.

Mark

Does the Nvidia drivers in 007-212 fix NForce2 issues?

Posted: Thu 08 Feb 2007, 15:41
by puppyfan12
Mark said there's new Nvidia drivers (in 3DCC) in this version of muppy. Does this version fix these problems I've been having with Asus A7N8X-E (nforce2 chipset) motherboard? Or possibly it's unrelated...if so could you post suggestions there?

*edit* as an after thought I moved the content for the ethernet problem I had with 006 into it's own thread so I don't clutter this one. I'd just like to know here if the 007 nvidia driver updates fix those problems.

*update Feb 12, 2007 5:44pm EST* Ignore problem mentioned above. The issue was zdrv_212.sfs was corrupt and had a 0 (zero) byte size. After copying that file from the iso, everything works as it should.

Posted: Sun 11 Feb 2007, 10:54
by drongo
Are the links at the top of this thread still working? I downloaded eight Linux ISOs on Friday night. Two didn't produce bootable disks. One of these was Muppy. I used a different link and attempted to download Muppy again last night but the MD5 does not match (it didn't match the first time - but I assumed the iso had been updated without changing the MD5).

I'm desperate to try Muppy - it looks lovely.

Posted: Sun 11 Feb 2007, 14:52
by MU
I did not change the links.
As many people use muppy, they still should work.
Cannot test myself at moment, as I'm not on ADSL any more.
Mark