Not directly a bug report but a request to add this support in order to better control the synaptics driver, f.e. to disable completely the touch pad._________________Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

EDIT - Ignore - that doesn't seem to be what fixed it after all..._________________Classic Puppy quotes
-
root: n. the superuser or administrator account that has complete control over everything in the machine. Running as root is a taonga of Puppy Linux users.

- However using Puppy 2.17 it works like a clock and connects without anyproblem.

My access point is a Proxim Ap-2500M. Standard product when building large wireless networks (mesh).

Best regards,
Johan

Yes this IS already known but it is hardware dependent, and is why Barry is abandonning the latest kernel which has "retired" certain Modules and replaced them. For example IPW3945 was replaced by IPL3945 which has WEP but not WPA encryption.

I don't know about your specific hardware (forum member Tempestuous will be able to help with that if you get really stuck), but you could try one of the "Retro kernel" versions of Dingo and see if that cures your problem.

I believe that the first Beta is due over the weekend and will be on the retro kernel, so you could try that out when it is launched.

What level of hardware is Puppy compiled for now?
I copied my main (non-Dingo) setup onto an older PC with a 350Mhz Pentium 2 processor. This setup has the Dingo Mplayer and ffmpeg packages installed. Mplayer crashes with

Code:

MPlayer interrupted by signal 4 in module: unknown
- MPlayer crashed by an 'Illegal Instruction'.
It usually happens when you run it on a CPU different than the one it was
compiled/optimized for.
Verify this!
- MPlayer crashed by bad usage of CPU/FPU/RAM.
Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
gcc version. If you think it's MPlayer's fault, please read
DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
won't help unless you provide this information when reporting a possible bug.

I hope xine/gxine in Dingo doesn't have the same problem!
Also, I could have sworn I saw a page on puppylinux.com where Barry explained how he compiled Mplayer with shared ffmpeg, but I can't for the life of me find it now. Maybe it was on the forum and was someone else, but all I can find now is one little part on the puppy-from-scratch page. Does anyone know where to find this information?... because I could never find it anywhere else. If I remember correctly, using shared ffmpeg isn't "supported" anymore, but it's worked perfectly for everything on my other machine for months now._________________Classic Puppy quotes
-
root: n. the superuser or administrator account that has complete control over everything in the machine. Running as root is a taonga of Puppy Linux users.

A week ago (bit of a time lag here!) I used to Petget package manager to download and install the GIMP 2.4.0-rc3 package. It was supposed to be a 16MB download, but only 6MB downloaded. I let it install, but got a list of missing dependencies that went off the bottom of the screen- presumably the missing 10MB?

So I suppose Dingo is ok- the bug must be in the PET package? Or is it fixed already?

Not sure if this counts as a real bug, but I have problem with Xorg locking up on hardware probing, while running Puppy in QEMU. Xvesa works correctly. Any way to debug it? Tried using loglevel=7, but as far as I see it worked only until video selection.

Keyboard oddity:
keys do not "repeat" & I have to press a key repeatedly to get repeated characters.

Esoteric keyboard oddity:
When running x11vnc from an Acer 5610 laptop to the HD dingo, the keymapping is incorrect as I cannot obtain a "pipe" sign or a "Pound sterling" sign (latter produces just "3" , former produces backslash -- i.e. they aren't "shifted") ; Key repeats however work fine.

With alpha7, when saving or loading a file from an application, sometimes all file entries appear twice in the file selector window. This gets back to normal by going to the "parent" directory then re-entering the "child".

Found no other report of this, and it seems odd. Is it happening only to me?

Also, I could have sworn I saw a page on puppylinux.com where Barry explained how he compiled Mplayer with shared ffmpeg, but I can't for the life of me find it now. Maybe it was on the forum and was someone else, but all I can find now is one little part on the puppy-from-scratch page. Does anyone know where to find this information?... because I could never find it anywhere else. If I remember correctly, using shared ffmpeg isn't "supported" anymore, but it's worked perfectly for everything on my other machine for months now.

Yes, I remember posting it somewhere. It isn't in my blog, so it must have been the forum.
I got it to compile in the T2 project, and if you download the package that I placed on ibiblio ...somewhere... its about 600MB I think, open that up and look in the there you will find the information, but it does need a bit of familiarity with T2 to be able to extract the info you need.

Hmm, I should be a bit more helpful than that. I have looked in the T2, got out the relevant file, mplayer.conf. Some of the relevant stuff in it:

If I recall right, those options in bold are the key. They disable mplayer's inbuilt libs and cause to use the system ffmpeg libs, which must already be installed._________________http://bkhome.org/news/

I have been trying to make a replacement for gxset. This time I may have made enough headway for it to be at least a working start. There is one problem, with gxset still installed it will reset the xsetting on each reboot. But I have been able to reset most of the setting untill I reboot. I had it to where it would reopen the main window but the same line of code all at once stopped working. I will try and find out why.

Berry I hope this will work as a replacement for gxset and mite make it into puppylinux.

I just did both Full and Frugal installs on a
1997 Gateway 2000, Pentium MMX 200 MHz, 64 MB, 2 GB.
(The local 12 MAR 2008 ad said: FREE GATEWAY COMPUTER
with monitor and keyboard. As is.)
I'm using the Full installation ATM to compose this.

1. Please: Could NEWGRUBTEXT be put in the
Frugal install directory?

2. When unused, but running, Puppy seems to be accessing the HD
every few seconds. This is very bad for HD longevity.

Could the HD be left alone, not accessed,
and Powered Down, please,
when Puppy is unused, but running,
for minutes/hours/days at a time?

The screen blanks after the 12 minutes I selected in the BIOS Setup,
but the HD stays active.

3. Very much need a way to access WebDAV directories/"Folders".
I do not know what options you have, but providing an
Official PET of "cadaver" might help for now:
http://webdav.org/cadaver/

Mr. Barry
Not only are ALL ports open on your home (personal) system but you have left everybody running Puppy WIDE open.

I missed this post earlier, prehistoric has communicated with wingruntled and it seems that that issue is I was running the Ayttm IRC client without a firewall. My apologies, it wasn't for very long. In future I'll be extra careful to put up the firewall first before going online.
I'm always building new Puppy systems, so it's an extra step I'll have to discipline myself to do.
To others reading this, having visible ports does not mean that I can be compromised. But it is better to be hidden._________________http://bkhome.org/news/

Does anybody know if there is a good reason for the userChrome.css hack that prevents the Seamonkey gui from obeying GTK font settings? Because if I remove it, then Seamonkey still appears to work fine, and it actually matches everything else (except JWM - I changed the font preferences in every config file I could find, and it still doesn't work:cry: )

Now if only I could fix a couple of the other annoying things about seamonkey..._________________Classic Puppy quotes
-
root: n. the superuser or administrator account that has complete control over everything in the machine. Running as root is a taonga of Puppy Linux users.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum