In Puppy 301 I found that when I used the Fast Boot setting my mixer started as MUTE; when I dont use Fast Boot it starts out unmuted
Frankly I did not see a noticeable difference in the startup times on my system using the Fast Boot so I dont use it as I prefer to have my mixer start unmuted

I have been using the slackware wine packages since 9.22 and have always found them to work well. (.47 and 0.48 I tested and then dropped back to 9.46 whicbecause of problems with 3D and NTLM security which were related to bugs introduced in Wine and which were in the buglist to correct. I hadnt see...

I use wine and always have done. I started with v911 and am now on 947 I too got frustrated with the install so since the beginning I have always used the slackware version since I found that pulling down its gzip and simply copying in the "usr" frolder from there has invariably worked The...

pkay even when I started with pfix=ram and built a new pup_save I got the inode errors trapping them they appear to start with 2 inode which state deleted inode 6283 has zero dtime fix - yes deleted inode 6284 has zero dtime fix - yes which fixes that and breaks then in Pass5 I get Inode bitmap diff...

Okay following up on that I decided to see what woukd happen if I used the same file that was in the fugal install on a USB drive boot I did it the sam eway that i used before I have a 2fs blank that i created I take this and copy in everything from the initrd\pup_rw then saved it to the usb drive a...

Barry picked this up as well - as did I he is rolling cpio back from 2.6 to 2.5 as apparantly it is a known issue Slackware 12 uses 2.5 probbaly for this reason v2.6 apparantly has problems with the interpretation of symlinks and instead copies the busybox file instead See Barry's Blog for a better ...

Okay its got nothing to do with changing the desktop. How I am doing this is that I have a 2fs blank that i created I take this and copy in everything from the initrd\pup_rw then give it a discrete Pup_save name 2 things are consistnet The first time i Boot with this new file as a choice it does not...

I am getting exactly the same Lobster - - even using a completely new pup_save. On the first reboot everything was fine - just got 8 lines or so that showed that it was doing its checks. then I changed the wm to icewm and removed icons from the desktop and the error messages appeared on reboot and k...

xvesa - who uses it - I do for one Without it I would not be able to use Puppy It has ALWAYS proved to allow linux to boot on ANY machine, with xorg there have been at least 5 test machines that would not have even started up and frankly I wouldnt have been using Puppy for as long as I have stating ...

if you want a good treatment opf Kernels and how they differ (such as the mpnplithic vs hybrid -- linux vs ms) wikipedia has an excellent st - search on kernel when you get there - my son is taok a similar task last year

I normally just wait for the slackware package and use that to create my own sfs - but hey why look a gift horse in the mouth - thanks

no - its just that there are a couple of pictures up on it now which take along time to render - if you cant wait for thelength of time or have a slow connection try disabling images in your browser before hitting it

The opictures are worth the wait though

Nice job Barry simply copied it onto the usb I use for testing, replacing the vmlinuz, initrd, pup_221 and zdrv_221 with the new files It updated the pup_save very cleanly and read in my prefs.sfs and wine945.sfs boot files with no issues All the custom apps I use - esp those that run under wine per...

okay - I think I have fixed my problem with the errors regarding GLIBC I was getting I had a wine939.sfs that i put together with an earlier distro. So i redid that sfs file by removing the lib folder that I had in there, then re-running the ldconfig so that I now use the updated libs That also fixe...

2 problems so far > First During boot up I get a switch_root failed message and then a 60 second pause after which puppy continued with the boot. Second the eth0 setup has to be reset on every boot I see the following errors in the log dhcpcd: relocation error: /lib/libpthread.so.0: symbol errno, ve...

yes I have exactly the same problem, and also when trying to boot from a cf card on a lenovo diskless woworkstation - which is the main reason I have stuck with the initrd from the alpha of 2.16

vanchutr I run as a frugal install off of a cf card that presents as an ide drive formatted in fat and in fact thats what i am on writing this one change in 216 is with how it loads sfs files and it is an enhancement not a bug there is a new program called bootmanager under system i think and you ha...

for sfs files in 216 you need to use the bootmanager to specify which sfs files you want to load - it works a bit differently than the previous versions and just adding the version number in will not help the bootmananger is found in the system sub-menu and is pretty self explanatory after choosing ...

I would vote not to have it at all - or if you have to have it get it to flash an icon in the taskbar

George

216 which is in the experimental stage at the moment has a great feature for handling sfs files on load - I use sfs files a lot to hold my customizations and programs like wine which are tailored to my individual needs and I have found that the bootmanager included in 216exp2 is sinmple to use and a...