I've been away from Puppy for a bit but got a new monitor. This was EXACTLY what I was looking for. I run puppy in a virtualbox session. In virtualbox, puppy runs only with the Xvesa driver. There are still some bugs for me in the extra modes when i configure it; but it might be a function of me run...

Hi there, My puppy 2.17 boots fine on my system from CD or HD install. In virtualbox - it is now broken (as of 2.16) and I don't know if it's related to the kernal update. The last tested working puppy in virtualbox for me was 2.12 (i didn't test the versions 2.13->2.15) My system Windows XP Pro Asu...

I cannot claim to have come up with this myself. Some 18yo on his blog discussed this regarding the MX3230 Gateway laptop. Seems like it's an issue with the Via sound chip (and yes, it runs a realtek chip for some reason). Anyways, you have to go into ALSAMIXER and disable the external amplifier opt...

The filename/uppercase bug is EXACTLY the issue that I've had with my 2.16 install of Puppy. I had upgraded from a frugal install; transferring the new Puppy files over to the computer via a memory key. I had used windows to extract the files onto the memory key for transfer. For the last 2 days, I ...

Although Puppy has a utility to easily resize the pup_save file; there is no easy way to shrink it. This may be useful; for example, if you have a very large pup_save file that has a lot of empty space and you wish to either "compact it" or transfer it to a usb flash drive that is smaller....

Sunburnt...

Thanks for this utility - I find it very useful.

I'm not sure if I'm right or not; but I've noticed the same thing. I've had the problem where the USB drive is mounted in pupstate 12 (direct access mode) when 1) I boot up from the hard disk 2) BUT the pup_save is on the usb drive. I'm not sure if it's just specific to my configuration or not; but ...

You are right that if you have more than 1 pupsave in a partition, it gives you a list to choose from BUT; I prefer that the load up process be automated. Anyways, I'll take a look at your init script or just hacking away at the init script so it works. For me, the importance is that I have an older...

UPDATED DEC 18, 2006 I hope this can help someone else save some time. There is already an excellent thread on CUPS printing; but it seems somewhat fragmented. You should read that thread here http://www.murga-linux.com/puppy/viewtopic.php?highlight=cups&t=8673 This message adds some additional ...

Well, just to revive the threat for this and maybe have Barry add back the pupsave variable to the bootup cheatcodes I often wish to specificy which copy of the pup_save I would like to use in testing and as it is right now, I have rename or move things which is a bit - awkward. Any help would be ap...

My understanding was that there WAS a boot parameter that specified where the save file was to be stored; however, as of Puppy2, I think that was taken out to simplify things.

HOWEVER, I think it might be an idea to put it back in

Thanks,

Kevin

Updated Dec. 18, 2006 *** I just reinstalled the driver and found that I missed a step in the write up. I had to install BOTH the brother cups wrapper driver and the puppy cups 0.3. I don't know if you NEED both, but that's how I got it working *** Hi there, just wanted to share my experience gettin...

Hi there, I just wanted to say that this thread helped me solve my problem as well. I have a sound blaster 64 AWE - PCI on an older P3 desktop running puppy 2.12 in Pupmode 2 (full hard drive install). The sound would not play even though I tried to adjust volume through puppy. The ALSA sound wizard...

All I can say is WOW.

I've been using puppy for about 3 weeks now and JUST found this beta program. It is awesome, really helps to simplify installs; especially with the debian package support.

Thanks,

Kevin

PS - I think this should DEFINITELY make it into the ISO; hopefully by the next revision

Hi there, great idea, I tried running it and although I THINK I did the right thing, my new INITRD.gz file would miss some directories/information. Don't really know why, can you just check that it works ok for other people. Eventually, I found these commands worked as well (somebody else posted it ...

The truth is, this method should allow you to force ANY pupmode. However, you should have a good understanding of how the pupmodes work first before you change things as you can break your puppy. Barry has posted a description of Puppy and pupmodes at http://www.puppyos.com/development/howpuppyworks...

The truth is, this method should allow you to force ANY pupmode. However, you should have a good understanding of how the pupmodes work first before you change things as you can break your puppy. Barry has posted a description of how puppy and pupmodes http://www.puppyos.com/development/howpuppywork...

Thanks for posting the script to edit initrd.gz

I was trying to use another program but that was giving me errors (edit-initrd.gz) as I found that I was losing chunks of initrd on recompression with it.

Now it seems to work beautifully.

THANKS A LOT.

Kevin

Don't know if it's a simple as setting the PUPMODE variable in the init script. Tried that and it gave me a failure message. Good suggestion though. I think it might be coded to run pupmode 13 off /dev/sda so I'll have to look at the other lines and see if I can figure it out - sigh :) Thanks, Kevin

Ok, update after 3 hours. 1) edit-initrd is great; it seems to be running fine... I haven't checked the filesize of initrd after modifications though to see if everything is making it back in. HOWEVER, I'm finding that it is more difficult to set PUPMODE=13 than just setting a variable. As such, I h...