Puppy Linux Discussion Forum

shelezyaka · Joined: 14 Feb 2012 Posts: 37 Location: Ukrainian

A small request.
Along with the new ISO you can please upload the file and the delta to the previous ISO.
For example the delta file "luki-014.iso___luki-015.iso.delta" size of 19 MB.
I find it easier to download this volume, the Internet service provider offers little traffic - 400 MB per month.

jemimah · Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL

jemimah · Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL

Pete22 · Joined: 08 May 2009 Posts: 212 Location: Utah, USA

Marv;

Thanks so much. Leafpad did the trick.
My machine's high number was 15125.
Leafpad is wonderful.

Pete

aarf · Joined: 30 Aug 2007 Posts: 3620 Location: around the bend

got this keyboard: can't emulate rawmode for keycode 240 multiple times in dmesg. dont know what it is. it is in racy5290 too.

tony · Joined: 14 Jan 2006 Posts: 265 Location: Montreal.ca

Hi Jemima,

By Google I found that a list of drivers could be found by "xine --help | more"

Drivers were present in saluki 10 but not in 14.

So copied /usr/lib/xine/plugins/1.26 from saluki 10 to 14 alongside of existing file 2.1

xine now starts OK.

Regards Tony

Dromeno · Joined: 12 Sep 2008 Posts: 469

Dromeno · Joined: 12 Sep 2008 Posts: 469

Dromeno · Joined: 12 Sep 2008 Posts: 469

Dromeno · Joined: 12 Sep 2008 Posts: 469

Dromeno · Joined: 12 Sep 2008 Posts: 469

aarf · Joined: 30 Aug 2007 Posts: 3620 Location: around the bend

tlcstat · Joined: 28 Oct 2007 Posts: 79

delete

jemimah · Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL

mikeslr

Hi jemimah & all,

I may just be having a bad day, but custom_builder15 doesn't work for me.
Since I explore various Puplets and use Grub4Dos, my usual procedure is to create a folder, download an iso, mount it, and move only the necessary files into that folder, and add the new Pup to Grub4dos' Menu.lst. The new Pup's folder, therefore, would not include either isolinux.bin or isolinux.cfg. That was the condition of the Saluki1 folder when I first tried to run custom_builder15. After pointing it to the Saluki1 folder and clicking "open" I received a report that the above two mentioned files were missing. So I mounted Saluki15's ISO and copied them to the Saluki1 folder. Now, clicking "open" dropped me out of the builder. I tried again, with the same result. I also tried after adding all the other files --i.e., boot.cat, etc.-- to Saluki1. Again, custom_builder shut down. Trying again, this time pointing to the mounted Saluki15.iso had the same result.
See attached screenshots for further understanding.
Even if it's just me, may I suggest that the requirement that isolinux.bin and isolinux.cfg be present should be reconsidered. If only a new adrive is being built, they aren't necessary. If, like me, Saluki is being run from a folder via Grub4dos, they won't be located in that folder [but could be included in the custom_builder application]. And in any event, builder should be able to use a mounted ISO which is just as likely to be available as a burned CD.

While taking the screenshots I discovered the delay feature did not work. But perhaps this was because I had checked "selection" rather than "full screen." The foregoing words in quotes may not be those used by the dialog. I'm not currently in Saluki. Hopefully, you'll get the gist.

Last note: When Saluki boots, it looks for an adrive specific to its version. That is Saluki15 will look for adrv_luki_015.sfs. It will ignore --not load-- adrv_luki_014.sfs, etc. If, like me, the user is going to use the same applications in the new version that were used in the old, there should (a) be some way to simply upgrade an old adrive, perhaps with appropriate warnings regarding compatibility; or (b) boot without an adrive with an application in core to simply rename an old adrive, perhaps with appropriate warnings; or (c) the loading mechanism should be less specific.

mikesLr