As I wrote in the Slacko thread:
Puppy has a very aggressive mouse pointer. Its default acceleration is set to 2 with a threshold of 4. This will give me inflammation in my mouse arm, so in all these Puppy years I have set it to 1.2 (acceleration) and 13 (threshold). Well, I will not state what is correct, but how can a newbie find the setting? Is pupX set properties of X informative? - Doubt it. And I think it would be good with a link in the mouse/keyboard wizard. I wouldn't be surprised if that is the place a newbie would look.

Thanks so much for this! I have an old, sensitive mouse that is driving me crazy. Until I buy a new one, this and the Xorg keys will do.

zigbert wrote:

Talking about menu descriptions, it may be worth to rethink 'JWM configuration' as well.

I agree.
Or at least put a scrollbar in the JWM theme chooser, so that having many themes won't expand the GUI from roof to floor -- at times I think the Exit button will reach China. The same happens in the Icon Set Chooser GUI, a scrollbar for that one would be great, too.

Well, on the topic of adjusting mouse sensitivity, yes, good idea to add a button -- this is added in script 'input-wizard'.
Done in Woof, will be uploaded soon._________________http://bkhome.org/news/

Barry. 3.8 kernel. For enabling brcmsmac driver you need to add bcma support as module and also under wireless, the bcma support for broadcom, then you will see brcmsmac as tickable option.
Proprietary wl.ko though is the only supporting driver for many chips. brcmsmac and brcmfmac does not cover them all.

New wireless realtek driver rtl8723ae.ko was in your 3.8 rc kernel. It needs 2 supporting firmwares. I cant show modinfo for the driver (not in 3.8 kernel puppy now), but the attached firmwares should be the right ones.
They can be placed to the all-firmware/rtlwifi folder....if you wish. And according firmware.dep editing. There are already in linux world posts about need for that driver and questions how to get it to work with chips which needs it. So...seems reasonable to include the firmwares also.

Is the issue of the random allocation of index numbers at each boot now fixed?

I have several multiple sound card computers here and from my observations this wizard would change the default from index 0 to index 1, but this does not lock things down if the allocation of index numbers to the different detected devices at each boot is random.

Does MSCW now write anything to /ect/modprobe.d/alsa-base.conf because normally I have to edit that file manually to resolve this issue?_________________Oscar in England

When NASA is selected in pupTelly... the program 'bounces' back and forth between the pupTelly dialog-box and the video media... stays on NASA about 7-seconds... stays on pupTelly dialog box about 11-seconds, this continually repeats.

The pre-occupation with multiple sound cards seriously misdirects the valuable intellectual challenges facing our developers. Probably count the number of folks who need this facility on one finger (no, not that finger, madam!). Those confronting conflicts with onboard sound have merely to write out the onboard unit in BIOS, assuming they aren't using a cr*p proprietary BIOS on an even more cr*ppy Intel board. [But even these can be over-ridden using a serious BIOS interception utility.]
Those mounting two independent sound cards might try making one of them an old ISA card and using an earlier Puppy variant that has been extensively worked over such as those by TaZoc, ttuuxx and johnbiles.
Generations ago, and also on another Forum that I moderated, I advocated slicing the Vcc line of troublesome onboard sound chips with a scalpel - still and equally valid solution.
Once we can stop people buying Intel and put that worthless organisation into liquidation, many of the world's IT problems will cease. It might also achieve that other most desirable goal of closing down the devil's OS.

Sorry, but I don't agree with your assertion that resolving multiple sound card issues is not important.

I often see people on here reporting problems of loss of sound and I believe this may be one of the causes.

Other devices such as modems get detected as sound cards. Common hardware such as webcams plugged into USB ports also becomes detected as additional sound cards on the system in many cases. The percentage of computers which will have more than one is not as small as you suggest.

For those of us who do install additional PCI or USB sound cards because we want the functionality of more than one audio input and output (in order to be able to route audio to and from different places), it would defeat the object to disable one of those cards in the BIOS. The Operating System should be able to detect the sound cards and handle them properly and consistently and I thank those who work to ensure that this is the case in Puppy._________________Oscar in England

If modems, webcams & co. are detected as sound cards that's an error of detection suggesting an appropriate remedy.
Folks wanting to run two or more sound cards from one PC, and I disagree - it must be an infinitessimal number, would be better advised running two or more old boxes, especially to avoid routing even more cables to other rooms, presuming they're not listening to jazz in one ear and pop in the other. Messing with unnecessary complications in SW is, as I said, severely distracting. Sound, per se, is not intrinsically difficult to achieve on any old junk. Indeed, broken record, the best results can be had from a board with an ISA slot and a genuine SB128. There are also a plethora of modern digital sound devices available from discrete separates and, most probably, your own telly. Most municipal dumps harbour entirely adequate hi-fi boxes.
It is important to define clearly what objectives are required to be met. Suggesting that there are two separate and, implicitly, different sound generators running off one machine in the same room is just silly. Anyone so severely constrained can PM me and I'll send them an old board, gratis.

It's not very important but will report anyway. I've been translating report-video and noticed this thing. I have two videocards - one of them is built-in and this one shown in the report but the other one is in use and it's driver is shown:

If modems, webcams & co. are detected as sound cards that's an error of detection suggesting an appropriate remedy.
Folks wanting to run two or more sound cards from one PC,..... gratis.

I believe that you need to understand this issue much better, Sage. I've been stuck with Lupu 5.25, for quite awhile, specifically because of this issue. I am simply using a Dell Inspirion Mini NETBOOK; No PC sound card issues here. The detection of sound H/W is not a trivial issue. Apparently the group has always lacked the specific experience required to handle such an issue. If you could locate the appropriate sound h/w detection expert, out there, s/he will surely solve the problem; hopefully permanently.
Cheers,
ir_________________ir

My conclusion and report of frisbee's dependence on the wag_profiles package are incorrect. Because wag-profiles.sh was in the initial beta package from which frisbee is derived, I assumed it was needed. But it was there because it was modified to use dhcpcd-dropwait, which was also there. Therefore, the modified wag-profiles.sh can be restored into the net_setup package. One consideration, though, is that wag-profiles.sh gets updated to add entries for new wireless drivers; keeping it separate would avoid also updating the otherwise unchanged net_setup package. I have updated my frisbee-kit tarball with a recombined net_setup package, so there is one less package for users/testers/developers to install.

The newest network_tray package seems to work reliably. However, now that I have "integrated" the tray icon set, the "-eth" set is no longer needed. I would like to remove the -eth set from the code and perhaps experiment with an implementation that does not require the set of signals from the dhcpcd hooks. Now that I have completed frisbee integration, I feel I can consider some improvements.
Richard

I well understand that some folks have sound card issues, ilanrab. You do not seem to understand that it's not a good idea to be running laptops/Dell/Intel (perhaps with 'doze as well?). You cannot squeeze more than one sound card into any laptop I've ever seen. If the internal proprietary laptop components are telling there's more than one sound card - there isn't!. That is an OS issue. Laptops are not intended to be wired externally to multiple rooms - that's crazy. You can have an old box for free - find them in skips at the roadside/dump - chances are they'll all do sound. First rule for Linux - delete the devil's OS unless you're a hobbyist interested in pushing boundaries. HW is so cheap or cheaper that there is NO POINT, even for impecunious students and less fortunate nations to be running multiple sound cards. I've personally sent dozens of working boxes with sound to Africa via our local charities - if they want more so they can run sound in several rooms, they have only to ask. Of course, none of those machines have the ultimate rogue OS loaded, only Linux. Education is the answer, as Tony Blair pointed out. We've got a mission to re-educate uniformed and brainwashed folks from propping up the DWIntel cartel (as well as other evil capitalist crooks eg in banking, meat trading, fizzy drinks purveying, add-your-example-here).