(old)Puppy Linux Discussion Forum

There seems to be a ""bug"" in the `pup_event_frontend_d` script.

Especially when booted from USB-Flash :

After ignoring the warning and unmounting the Boot-USB-Drive via terminal `umount /dev/sdb1`
and running `pup_event_frontend_d` via terminal the
/dev/sdUSB file(s)
are getting deleted.

Needed to
Code:
mknod /dev/sdb b 8 16
mknod /dev/sdb1 b 8 17
mknod /dev/sdb2 b 8 18

manually
( params via `ls -l /dev/sd*` )

Checking whether this happens is Quirky 1.4 and reporting in the Quirky development forum is the most efficient way to bring this to Barry's attention. http://murga-linux.com/puppy/viewtopic.php?t=62359

.

The three main problems with the Z-drive system are:-

1. Nobody seems to have explained what it's for in the first post in this thread, where new testers are likely to be downloading Luci from.

2. It has a very obscure name - unless you know what the numbers mean there's no way of knowing what it's supposed to be from the filename itself and when Puppy /is/ working properly clicking on it doesn't say anything useful either.

3. If it /isn't/ in the same location as the luci_nnn.sfs file wierd stuff like non-working networking happens but there are no error messages generated at all (that I've seen) that would indicate that the missing z<whatever>.sfs file is the problem. I only found it out by looking at the LiveCD and noticing the extra sfs file - even then that required me to know that additional SFS files are loaded at boot.

The zdrive contains the kernel modules, about 22MB of them! Once they are loaded the really don't need to take up any ram--so using the zdrive loads them from the disk. That makes the main sfs file smaller--around 110MB, which is a reliable size for loading into ram on a computer with 256MB ram We had not been using the zdrive until Puppy 237 (I think) or maybe even later.

I wouldn't be surprised if it is causing problems, however Quirky and Wary are both using zdrives also. We should keep watch and if worse comes to worst and no fix appears, we can delete a package or two from the iso and return to *not* using a zdrive. Thanks.

Burn_IT wrote:I've cut a CD and tried on two machines:
Dell Lattitude C840 & ThinkPad T42
Neither loaded ANY network drivers yet BOTH work under 511 and earlier.
When I say they didn't load network I also mean there are NO driver modules in the (none existent) list to load either.
Both recognise the hardware correctly.

Also on the C840, the PS2 mouse is not recognised and there is no Alps drivers.

I would do more testing, but not being able to get to a network kind of ruins any chance.

Did you use Burniso2cd to make a live CD?
This is what should be on the live CD.

A frugal install made with the Puppy universal installer should look like this

I did burn the ISO to CD using infrarecorder and it does indeed contain those files. I also installed to a USB stick. Neither loaded the sfs when run.

I have resolved my problem by copying the files to my hard disk and manually setting up Grub4Dos entries for it, BUT - and I think this is an OLD problem yet to be agreed and resolved, they were all upper case names on the CD and I had to change them to lower case for it to work.
I will recreate the CD from Lucid itself and see what happens.

Bigpup what function does that atahd icon do? I only do manual installs so I never see that one?

Hope it is okay to ask

playdayz wrote:My plan has been to 1) make shinobar's language packs available in PPM. That will be a big step forward IMHO. They are not a perfect fit, but we might be able to do a little customizing to add the packages that are unique to Lucid 5.2. 2) Another thing we have started (but there is so much to do) is to place the NLS packs into PPM for individual programs--the one for mtpaint is there now for instance. 3) Finally, the locales are often included with packages such as Chromium 7. I have noticed that users really like it when the browser automatically speaks their language.

Evey thing what has to be installed as a pet will grow my save file, something what I would like to avoid.
Therefor ttuuxxx'x idea to have that in a separate sfs looks a nicer solution to me.

NLS support is pretty complex and isn't all about having the messages in ones own language. This only part of it.
It is important that the application can render the accented characters, like filenames etc..

In fact, personally, I like to have system messages, application messages etc.. in English, but my filenames with accented characters, date and number format in nl.

National Language Support Guide and Reference is good reading material.

The ATAHD or IDEHD tells Puppy it is on a hard drive. It is similar to the PMEDIA= parameter.

It is beginning to look as though the burning program is changing the case of the names.

Quick update: with some tests with the RAM monitor open, I've observed it crashes for me with as low as 100MB of RAM in use. I thought this was a RAM problem so I ran mtestx86 4.10+ for a day, no errors. I tried Puppy 2.14X and it worked without a single crash, recognized and used the swap perfectly, and so on. Also, the theme managers all worked.

Unfortunately, 2.14X requires a CD to boot (the installer is so old it doesn't recognize my partitions like 5.x does).

I think the solution is a "legacy" kernel for these old computers.

playdayz wrote:

I would (and I do) adding my locals to my system...

Here are shinobar's language packs. Can anyone interested please test. Download the pet and install--and of course change the language with Personalize Settings or Chooselocale. Thanks http://219.75.239.224/puppy/lupq/opt/languages/.

I downloaded the nl pet and looked inside it.
To me it seems that it only gives the translation of some application messages.

To me it is still not clear how to handle the accented characters f.e. in file names, so they can be used in programs like ROX (or any file manager) in the open with dialogs, the save/save as and other similar dialogs.

I don't remember if I reported it, that recently I discovered that a lot of my file names had changed. The accented characters had been change at a certain moment and replaced by a strange character sequence. The content of the file was ok and I could change the file name to it's original name. aan IPI (01) BEGT financiÙle situatie en jaar afsluiting 2002 is an example from such a corruption. It should read aan IPI (01) BEGT financiële situatie en jaar afsluiting 2002
I have seen that in Lucid 511 the filename was in red and a message when hovering over said: the file name is not a correct UTF one (or something similar)

I hope I will not have such corruptions, whichever solution is implemented.

Burn_IT wrote:The ATAHD or IDEHD tells Puppy it is on a hard drive. It is similar to the PMEDIA= parameter.

Those dummy files are created by the Puppy Universal Installer to work with the Wakepup boot diskette.

For a regular hard drive boot, they serve no purpose and can be deleted.

playdayz wrote:All of the browsers btw are the full package, but not all include locales--for Firefox there are individual language versions that you can add. Edit -> Preferences -> Content and you can add a language.

I don't think that will give the user a localized Firefox. I have no Firefox installed atm, but I think the function you refer to is about content, website content, not the browser itself. (Unless things changed very recently in FF)

Only Chromium based browsers and Opera come with all locales included and are able to "see" the user's locale and install the right language. Firefox, afaik, is a different download for every language version. Seamonkey is unique, as it allows to add a language pack to an English version easily. ( Which is ideal for Puppy's goal to keep things small.)

The browser is probably the most important part of the OS for the average user. If the browser is localized, the OS 'feels' already localized for 75%..

Altho I downloaded SeaMonkey from the Mozilla site, I see to my surprise, that I have a selection of German also to have the application messages in German.

And this hasn't anything to do with the content.

Hi Béèm,

And do you get a German interface, when German is clicked?
Never saw that before.

My reburned CD with lower case names seems to work OK.

Now to find out why Windows got it wrong!!

Burn_IT wrote:My reburned CD with lower case names seems to work OK.

Now to find out why Windows got it wrong!!

It is a known problem when using windows to move and look at files in Puppy Linux.
Read the warning posted here:
http://www.puppylinux.com/install.htm

Bert wrote:Hi Béèm,

And do you get a German interface, when German is clicked?
Never saw that before.

Yes indeed. I was very surprised.
Close was Schließen.

playdayz wrote: The zdrive contains the kernel modules, about 22MB of them! Once they are loaded the really don't need to take up any ram--so using the zdrive loads them from the disk. That makes the main sfs file smaller--around 110MB, which is a reliable size for loading into ram on a computer with 256MB ram We had not been using the zdrive until Puppy 237 (I think) or maybe even later.

Came in with Luci-239, according to the bottom of your post at the top of the thread. You should probably include the file name too, remembering to update it with each version. Perhaps a name such as 242drivers.sfs would make its purpose more obvious?

I wouldn't be surprised if it is causing problems, however Quirky and Wary are both using zdrives also. We should keep watch and if worse comes to worst and no fix appears, we can delete a package or two from the iso and return to *not* using a zdrive. Thanks.

Don't get me wrong, I understand the reasoning behind having it, and when the zdrive and the main SFS /are/ in the same place the system seems to work fine on the tests I've done. It's just that there are a few scenarios where they might not be. In that case, there should be an error pop up rather than leave the user to wonder why it's not working.

When I had the problem with a missing zdrive I'd moved the luci-239.sfs file to my Puppy directory on C (sda1) and possibly also deleted the zdrive as I was short of space and didn't know what it was for. Another user on this thread had done a manual install but not copied the zdrive file.

TBH, moving some of the larger apps to the zdrive rather than essential system files may be a better solution.

Béèm wrote:Close was Schließen.

Scheiße

Maybe you can retrace the download url at mozilla, maybe it accidentily chose German for you?

Traditionally, Puppy has almost always had Seamonkey as the built-in browser. Also Insidious Puppy has it. In that situation, the language packs at the Seamonkey site, are a great help.

playdayz wrote:It is our Feature Freeze--only debugging from now on.

nooooo . I had some more yum yum for you. Oh well.