Newyearspup 02 Micro, Mini, Midi, and Maxi RC10

[Béèm]

But the real show-stopper is, that altho I selected the Belgian azerty keyboard, I am not in it, but have some qwerty keyboard.
How can this be solved?

Do the german/french one work for you?
You can activate them in the "settings" menu.
(keymap DE, keymap FR).
Mark

No the German doesn't work.
The french does work except the dead keys, which are proper to the Belgian keyboard.
I am typing in NYP now, so as long as I don't have to type some special characters, it's ok.

So the show-stopper remains.
I installed the mini and it's nice.

Hope the keymap for the Belgian keyboard can be available for selection on boot.

[Sage]

Accented characters occur in a wide range of languages. No surprise that there are companies wanting to sell font packs for the devil's OS. However, for those who understand these things (not me!) it really shouldn't be so difficult to work out a key combination once the ASCII look-up code is known. A useful list is given in :
http://tlt.its.psu.edu/suggestions/inte ... tml#winalt
In principal, any key can be (re)defined to show any symbol or character, then it just needs one of the universal drivers which were originally all based on Unix. It was so much easier in 8-bit. It always surprises me how few Brits know that CTRL-ALT-4 produces the euro symbol, even in W95 and even in the UK where the £sterling still reigns supreme! (Well almost, at least it did till ~1900).

[MU]

Bernard,
do you get an error when you type:
setxkbmap -layout be

That keymap is
/usr/X11R7/lib/X11/xkb/symbols/be

Your selected keymap is stored in the file:
/etc/keymap
It should be "be.map".

The keymap is loaded from /root/.xinitrc, with the command:

Code: Select all

#wow: (custom 4.11 puplet)fix keyboard layout (Xorg 7.4)
setxkbmap -layout `cat /etc/keymap | cut -f1 -d.`

So somewhere here must be the error.
Just to be sure: you use xorg, not xvesa?

Mark

[Sage]

OK, Mark - hopefully one problem solved for Béèm. Now some folks will be calling for the circumflexed 'y' and 'w' -ŷ and ŵ, which, of course can have vowel sounds in all languages, {apart from those pronouncing 'w' as 'v' (German(!) and others more directly linked to our mutual Sanskit heritage)}.
In this case, we are asking for ASCII 0373 & 0375.
How to do it?

Interestingly, these characters can be copied over from the above link, as well as accented Béèm from his posting.
Haven't czech-ed (sorry about that irresistible pun) the Czech hooked characters, but I guess the little circle-over ones work in Opera, at least.

[Béèm]

Bernard,
do you get an error when you type:
setxkbmap -layout be

That keymap is
/usr/X11R7/lib/X11/xkb/symbols/be

Your selected keymap is stored in the file:
/etc/keymap
It should be "be.map".

The keymap is loaded from /root/.xinitrc, with the command:

Code: Select all

#wow: (custom 4.11 puplet)fix keyboard layout (Xorg 7.4)
setxkbmap -layout `cat /etc/keymap | cut -f1 -d.`

So somewhere here must be the error.
Just to be sure: you use xorg, not xvesa?

Mark

Thank Mark for your attention.
I am in Xorg, sure of it.
keymap says: be-latin1.map (as selected on first boot)
But I am still in some qwerty layout
setxkbmap -layout be doesn't give an error.
Now I am in a Belgian layout but without dead-key support. So I can't make a o umlaut.
So it's more comfortable.

As the alpha6 be-latin1 works, I copied the be map to NYP but when doing the setxkbmap cmd I get a loading error.
In NYP pup_ro2 I found a be-latin1.map, but I am not sure where to put it.
I copied it to /usr/X11R7/lib/X11/xkb/symbols/be and issued the command setxkbmap -layout be-latin1, but got a load error also.

So the dead-key issue remains.

Other then that, after the session with NYP I powered down. But the PC doen't power off, probably due to the acpi=off parameter on boot.
Annoying, but workable.
However, I wonder what I will discover of other functionality not workin due to acpi=off.

Bernard

[tlchost]

I have a saved version of RC7....and the soundcard is detected, and alsa mixer works fine

I wanted to burn a new LiveCD, and the alsa wizard no longer works.

If I type alsamixer from the prompt I get. snd_ctl_open failed for default: no such file or directory


Was there a fix or work around for this? I can't seem to find it.

Thanks
Thom

[Béèm]

At intervals I have a gxmessage window popping up with no text and a black background.

Any reason for this?

[tlchost]

Apparently the alsa wizard doesn't work with some/all of the desktops in RC10.

I have it working on my home PC...and I'd appreciate some hints on how to detect the audio card on other systems.

Thanks
Thom

[wilson]

I have experienced an issue regarding heavily encrypted save files. While they work without error on Newyearspup 02 Midi RC10, I found that they do not _load_ with Wow's Unnamed puplet 1.1. I am hoping that maybe Mark or someone else may know why it works on one and not the other, as they are from my understanding similar puplets.

I tried saving from Unnamed 1.1 as a heavily encrypted save, but found it would not load completely after reboot. The system loads to the point of requesting the password, but after I enter the password it indicates "Can't mount file, press Enter key to try again, or any other char then Enter for f.s. check...". After a couple more tries I attempted the f.s. check and it indicates "The superblock could not be read or does not describe a correct ext2 filesystem." and then goes on to suggest using "e2fsck -b 8193 <device>".

I first tried this on a SD card as a USB install, but after reaching the error started using frugal installs on an IDE drive on another computer because they are easier to set up and test with. I got the same error trying a heavily encrypted save file with Unnamed 1.1 on a frugal IDE install.

I loaded a vanilla pup 4.1 frugal install and ran the e2fsck -b 8193 on the Unnamed pup_save_crypta.2fs save file. I got the response "Attept to read block from filesystem resulted in short read while trying to open pup_save_crypta-x1.2fs. Could this be a zero-length partition?"

I then tried saving from Newyearspup 02 Midi RC10 on a frugal IDE install as a heavily encrypted save, which loaded successfully after entering the password during reboot. I copied the Newyearspup 02 Midi RC10 pup_save_crypta.2fs file to the Unnamed 1.1 folder and rebooted to Unnamed, but got the same (original) error after entering the password.

I then tried taking the original pup_save_crypta.2fs file from Unnamed 1.1 and copied it to the Newyearspup 02 Midi RC10 folder, and rebooted to Newyearspup. The encrypted save file (all save files named differently) from Unnamed 1.1 loaded successfully to Newyearspup 02 Midi RC10 without error after entering the password.

This lead me to believe that Unnamed is saving the heavily encrypted save file successfully, but is having trouble when trying to load any heavily encrypted save files.

As a curiosity, I ran the e2fsck -b 8193 on the Newyearspup heavily encrypted save file. It also returned the "Attept to read block from filesystem resulted in short read while trying to open pup_save_crypta-x2.2fs. Could this be a zero-length partition?"

So my question is, does anyone know why Unnamed 1.1 would have an issue with loading a heavily encrypted save file, or do you think there was a problem with my testing? If the testing seems correct, is there anything I could do that would allow this functionality with Unnamed 1.1?

-thanks-

[MU]

wilson,
I am not certain - you could try to use initrd.gz from newyearspup, if you use a frugal installation. So you would overwrite that from ultrapup (backup first)..
I made some very slight changes, but do not remember, if I added one or two kernelmodules.
Maybe my changes to the startup script cause, that the drive, where your savefile is located, is found.

To check the filesystem of a encrypted file:
http://www.murga-linux.com/puppy/viewtopic.php?t=41918

Mark

[wilson]

Mark, copying the Initrd.gz file from NewYearsPup did the trick. I now have a functioning heavily encrypted save file on my SD card that loads with Ultrapup. Thanks for your help, and thanks for all the wonderful work you have done for the community.

Gary

[sailorbrand]

ich suche fürs nyp ein sfs oder so, von vbox.

Hab schon viel gesucht aber nix gefunden.

I search for a sfs-file of vbox for my new-year-pup.

help anyone?

[elraven]

hi sailorbrand. Try Dingo's site at http://dokupuppylinux.co.cc/programs:emulators
He has vbox 1.5.2 sfs listed there.
Hope it helps
elraven

[wow]

@sailorbrand: pet and sfs http://www.murga-linux.com/puppy/viewtopic.php?p=285289#285289

[vtpup]

Well, This may become my main pup on the Thinkpad T43.

It is basically the latest kernel Puppy that will run ATI Catalyst 9.3, which is the last driver set that ATI produced to cover legacy Radeon boards. Later kernels and later ATI Catalyst versions will not work with a large number of IBM Thinkpads, or probably a lot of other laptops as well.

In fact many earlier versions of the Catalyst driver ALSO don't work with these boards. Apparently some time around version 9.3, ATI decided to support legacy graphics chips, and then abandoned them again.

The T43 and many other Thinkpads used these boards as standard. The Thinkpads in the past therefore have had great difficulty with hardware graphics acceleration in Puppy Linux. This was an impossible problem when running Wine graphic intensive apps like CADs,, games, and simulations. Basically most graphic accelerated stuff crashed on these Thinkpads. Frustrating because that stuff all works on the same computer in Windows XP if you dual boot.

But I finally came across this ATI driver package this week, and MU's New Years Puppy which supports it very well. This puplet is a real life saver for this laptop, and I bet a lot of others using ATI boards. Though I bet most owners don't realize it and put up with a limited graphics capability.

Anyway this pup works great on the T43, and I can now run several CADs, and Google Sketchup (which see) in wine.

I happen to be a meat and potatoes Bary Kauler Puppy Linux user, with no interest in eye candy so I initially had a hard time with this admittedly good looking desktop. But for me everything worked differently, was in a different place than I was used , etc, and that made it feel clumsy and frustrating. I probably wouldn't have felt that way if I'd come to it fresh. But 3 years of using standard puppies made for inflexible habits.

However once I discovered how to restore JWM through the shutdown dialog MU has created, and get drive icons back on the desktop, add Seamonkey, and get ROX back as the main file manager, etc. I started to feel right at home again, and my working speed picked back up. I did keep the wallpaper and a few things, so it still looks new to me.

I had slow download capabilities, and I wanted a pretty stripped down version to build back up with only the things I use. I've had good luck so far. But a couple thngs aren't working well.

I can't find a gtkam/gphoto .pet, and I haven't been able to get a couple different mplayers to work.

I'd appreciate any help in finding .pets for these that will work with this puplet on the Thinkpad.

Thanks again MU for this puplet. I think it should be better known. Looks like it is the best (and only) possible choice for a Thinkpad of this era.

[cthisbear]

MU...well missed and a terrific bloke.

Talented, no cockiness....but had the smarts.

Gracious and helpful.

""""""""""

vtpup...

seeing this was an old thread, can you post the recent links
for this Puplet, so that other IBM owners can test it.

Thanks mate.....Chris.

[Béèm]

The puppy google search (see puppysearch in my sig) will find it in seconds I suppose.

[vtpup]

MU...well missed and a terrific bloke.

Talented, no cockiness....but had the smarts.

Gracious and helpful.

""""""""""

vtpup...

seeing this was an old thread, can you post the recent links
for this Puplet, so that other IBM owners can test it.

Thanks mate.....Chris.

Mark is gone?!!!!
ohno!
He helped me so much, and so many others.
Thank you Mark for all you have done.

*******************************************************

Here's the link to the various sizes of NewYearsPuppy. I actually had a hard time finding it again through Google and well minded search, because there are so many other peripheral references to it.

http://puppyisos.org/isos/2009-01-to-06/Newyearspup02/

Note, the versions are called Micro, Mini, Midi, and Macro. Each one has more apps than the last.

The micro and mini versions don't have the ATI driver on-board but all the necessary stuff is there for adding it from the ati-catalyst-9-3K2.6.28.5.pet that MU also put together.

ati-catalyst-9-3K2.6.28.5.pet

The midi and macro versions already have the ATI driver in place.

(Note, when adding the drivers to micro or mini versions DON'T use the later kernel pet -- ati-catalyst-9.3-K2.6.29.6-puppy4.3beta1.pet -- that one won't work with NewYearsPuppy)

[vtpup]

Just an update. The Mplayers I tried all worked after all, I needed to change the video settings to x11/shm, direct rendering, double buffering. (They also worked with GL2 but the playback was choppy) They didn't work with xv, as originally configured.

Also gtkam, gphoto2 ffom a thread posted by Aragon for 4.3.1 were located and installed and they worked, even though not previously tested against 4.1.1 (NewYearsPuppy).

So now, I seem to have everything I generally used in 4.3.2 v3 test, and can switch over to NewYearsPuppy as my main distro, with full graphics acceleration on the Thinkpad T43. Great! Thank you Mark.

[vtpup]

Everything has been working great with Newyearspup, on the Thinkpad T43 including Google Sketchup, CADs and other graphics intensive programs that accelerated hardware render on this laptop, until an automatic upgrade to Seamonkey 2.4 caused that program to stop working. Earlier versions worked fine.

When I try to run Seamonkey from terminal I now get:

Code: Select all

# ./seamonkey

./seamonkey-bin: /usr/lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /initrd/mnt/dev_save/Seamonkey/seamonkey/libxul.so)

As you can see above, the Seamonkey directory is located in /mnt/home and is shared by other puplets. It does work from 4.3.2 test

Any help solving this would be appreciated.