I wouldn't be so sure the order of sound cards matters. I'd suspect the driver for the first (or the config/handling thereof) to be the culprit.playdayz wrote:So how come it is doing things to the first audio card only?
Wow, excellent news. JWM is (I think?) the lightest and fastest window manager in the world that also has a modern look and feature set.01micko wrote:Some testing of jwm2-493-patched-q1.pet
- stellarium <-- fullscreen ok
gnome mplayer (using pupradio stream) <-- fullscreen ok
flashplayer <-- fullscreen ok
Suggestion: include this version of JWM with 5.2.
Bug/suggestion: The only remaining problem, it seems, is in updating the jwm configuration files. Too little is user configurable, and the scripts that write to the config file (and jwm tray config, etc) are a bit buggy (see the problem I reported earlier about applying a JWM theme).
Suggestion: I'm excited to hear about ogle. Its size and speed make it perfect for general inclusion in the distro.
Question: My computer (well, my mom's) has 256MB ram and the intel 8x845G chipset (similar to that of another user on here, but an 845 version instead of his 865 version). The computer is one of the most common "junkers" available, the Dell Inspiron 2400. I previously reported problems running 239 for any extended period of time (such as running firefox) for it would eventually crash to the prompt. I initially suspected memory issues, but later suspected booting with "noapic" would fix the issue as it did with xubuntu on the same system.
However, in case the latter is wrong, I'd like to revisit the "run out of ram" issue just in case. It will be some time (read: not until this weekend) before I'm able to test again, and I was wondering about how woof in 240 and above handle swap. I made a swap partition in gparted, but 239 did not use it at all. I heard there was a way to make a "swap.sfs" or something earlier, but could not figure it out.
Suggestion: I propose a tool for enabling swap (at least the pupswap.sfs or similar) to be created at install time (universal installer?) so that ram-limited computers could have less trouble. It would be great if I figure how to do it manually, but that wouldn't help other newbies, would it?
Suggestion: better tray configuration -- I'm in the US (and so is everyone I know personally), and everyone here hates the default "military" 24-hour clock. It would be great if the localization setup at first boot would take care of this, as having to search for the option to configure this may be found buried in Desktop settings. It would also be more convenient to implement more right-click power on the tray to easily change this and other tray settings.
Bug: I've learned USB installation is still quite glitchy (239 again) even when the syslinux.cfg file is manually updated with the boot source term "usbflash." Though it boots, the universal installer checks (again) for a CD rather than a USB stick. When the USB is mounted and the installer then directed to the root of the USB, it fails to detect the files until run again. When it is run again, it apparently recognizes the files and proceeds from the point it left off.
Suggestion: call bootloader (Grub or Grub4dos, depending on if the user specifies he has Windows or not) during/after installation. Not a single person I've given puppy to so far has managed to install it (frugal or otherwise) and then successfully boot into again.
Suggestion: It would be helpful for standard folders to be set up for newbies. For instance, when a USB drive is inserted, most people would not know to look under /mnt/sdb1, but expect either a link on the desktop or in a "my computer" type place.
Bug(?): full install won't use swap partition like normal distros.