Oh, I am running an AMD Athlon 1400 with 1 GB memory. Running 4.00 from a CD in RAM. The computer is about 9 years old now - all previous Puppy versions up until 4.00 alphas worked ok, beta 1 was "so so" and beta 2 and "SC" had similar problems.

using a frugal install of 4.00 final I noticed that the password that I enter when mounting a personal save file (with heavy encryption created with Puppy 3.01 or 3.00) is being shown as plain text, while it was not shown at all with 3.01.
I confirmed this behavior by choosing "none" when booting 4.00, creating a small h.e. save file when shutting down, then choosing this save file when rebooting - password was again shown in plain text.
I have not yet tried with light or no encryption.
Am I doing something wrong, is this a bug or a feature ?
(Or have I missed an already existing posting about this ? A search did not turn up anything for me ...)

In general, though, the new release looks good to me and I look forward to giving it a more detailed try.

Joined: 05 Mar 2008Posts: 276Location: "Killing a nerd is not as much fun as ist sounds" B.Simpson

Posted: Mon 05 May 2008, 16:18 Post_subject:

I just found out that some of my private wireless profiles made it into the default config file for Puppy 4.00! Wow!

The problem is not that if you happen to be at Berlin, Alexanderplatz every Puppy-Linux-User can surf the internet (profile: "alex") . No - - - the problem is, that one of these profiles has a wrong line count. This will prevent the network wizard from working correctly. So please replace your file /etc/WAG/profile-conf with the version provided as a attachment.

Posted: Mon 05 May 2008, 16:46 Post_subject:
acpi=force will give you a full shutdownSub_title: has strange side effects for me though

paulh177,

I get exactly the behavior you describe - always - on 3.01 and all the
Dingos. A full shutdown except for the final power off.

paulh177 wrote:

full hard disk install on dell gx240

using 2.6.21.7 kernel selecting poweroff, the machine powers off fully

using 2.6.25 kernel selecting poweroff, the system halts and the disk(s) seems to powerdown but the whole machine keeps running

If I use acpi=force boot parameter, I get a full shutdown.

However, for me, on all the older pups acpi=force causes strange
side effects. It causes intermittent boot lockups at a variety of points
in the boot process; and sometimes I get a strangely twisted mouse
where I expect the mouse to go up the screen and it goes to the
right instead. The twisted mouse can survive several bootups - even
cold off/on cycles.

Both sage and Dougal assure me that these are hardware problems,
but the fact remains that I never see them unless I use acpi=force.

So, I press the power button after I see the Power Down message.

Try acpi=force - it will most likely give you a full shutdown and may
not have any side effects for you.

The new ALSA wizard doesn't detect my PCI SoundBlaster Live! card while previous versions did. Of course everything is so intermittant with my computer running Puppy 4.00 that this might be just peculiar to me.

I followed Tempestuous advice and look at the readme file for RT73usb driver. The information is available from http://rt2x00.serialmonkey.com, one needs to search the site for "rt73usb". Only information on iwconfig is given to configure the device. Unfortunately, "iwconfig" can only be used to setup WEP for security. I checked Dingo Kernel 2.6.25 if the rt73usb module supported "iwpriv" commands, which would allow one to setup a WPA connection. However, there is no iwpriv functions supported. The use of WPA with this driver is a future development.

I also checked the ralink website. There is a driver for the rt73 hardware, which supports kernel versions 2.4 and 2.6. The driver was released in Januray 2008 so it should support the latest 2.6 kernel. It does need the Wireless Extensions V18. It supports iwpriv commands and the use of wpa_supplicant. I have attached the January 2008 ralink driver for anyone's use. For the newbies, package needs to compiled before one can use it. Hopefully, this will help with Dingo Kernel 2.6.25 development.

using a frugal install of 4.00 final I noticed that the password that I enter when mounting a personal save file (with heavy encryption created with Puppy 3.01 or 3.00) is being shown as plain text, while it was not shown at all with 3.01.

The same behavior that I noted in one of the Dingo betas; apparently it never got fixed.

Posted: Tue 06 May 2008, 04:38 Post_subject:
First Impressions of Puppy Linux 4.00Sub_title: Only some small clouds detected

To all Puppy Developers

Congratulations first for the new Puppy 4.00 which has several improvements compared to 3.01 that I used before. It runs quite smoothly in a frugal installation on my PC.

Bugs
I found the following bugs:

1. Epdfview crashes with a "Segmentation fault" if the UP/DOWN/PAGEUP/PAGEDOWN-key is pressed within the loaded document.

2. SeaMonkey: The item Language has disappeared in Edit/Preferences/Appearance Menu. Though even if it is still possible to download a language package for Seamonkey it is not possible to localize to your preferred language.

3. Mtpaint has only been compiled in the English version by using "configure" instead of "configure intl". So it can not be used in localized Puppy Distribution. The resulting localized binary is only slightly bigger than the English one (462216 to 451784). So Mtpaint should be localized by default.

5. xfdiff-cut from ftp://ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4 installs without adding a .files-file in /root/.packages. So it is not seen by the packet manager and can not be uninstalled any more.