If you have a particular setup that you tried that works good, you don't have to remember it. Just type option 7 and it runs your last saved configuration.

You can copy the a:\linld directory to the target device and run it from there when you use option 8.

Ulterior motive: Option 8 works on a floppy image burned to a CD. I can experiment with the best configuration on floppy, copy it to the USB stick, and carry it around along with the boot CD for the poor souls who won't retrofit their computer with a floppy drive.

---

P.S. (Edited August 1):

Philh: Like you, one of the computers I tried would lock up on the USBASPI.SYS driver but work OK with aspiuhci.sys. Another computer that locked up on the USBASPI.SYS driver didn't work with aspiuhci.sys but worked OK with version 2.06 of USBASPI.SYS. Unfortunately, there doesn't seem to be a combination that works on all computers. I consider this a DOS USB support issue rather than a Puppy issue, but it is an issue none the less.

I attached my edits to the autoexec.bat file here since I don't know if my excerpts above are very clear.

---

(Edited August 3): The writeup and attachment was revised to reflect the current new Wakepup2 configuration.

Thought I might ask this question here. Have an ibm 380 ed lap P150 32 megs a ram that I'm playing with to run pup. 'Cording to the lenovo site it is non cd bootable.

Stumbled on that it booted a win 98 cd. Ended up trying out gparted that booted. Tried out a bunch a pup vers & no luck. Tried out a wake floppy with a buncha pup vers & no luck with that. Thought at first it wasn't recognizing the cd drive or something..

All of a sudden the wake floppy (outa 2.17) booted pup vers 2.01. So wonderin why it booted 2.01 & not the other 2x variants?

Also didn't boot micro muppy(based on 2.12 i think).Last edited by jonyo on Wed 08 Aug 2007, 06:15; edited 1 time in total

wake pup works for me. it's great for those times that my intermittant cd drive is down, or overheated....

works for 2.17, not sure wake pup version...@ work...

wondering how it works, and how come this is the only distro that can use a floppy to help boot.

others say that since kernel 2.6.... is over 1.44 mb it won't work on a boot floppy, but i think that even tho pup is using 2.4.... and is less than 1.44, am i right that the kernel isn't on the disk anyway?

the mbr on the floppy gets hit and the bios boots it.
config.sys is loaded and all DOS drivers are loaded in there.
autoexec.bat is next. it has the logic to find puppy and decide what is pasted to linld.
linld is a dos app that will boot a kernel image from DOS.
we use the menu system in order to write the config file for overcomeing the commandline limitations in freedos (we are using freedos not MS-DOS).

j-impossiblix wrote:

...and how come this is the only distro that can use a floppy to help boot.

is it really? i'm ignorant, so i must defer this back the group.

@all
is puppy really the only disto (or liveCD) that can use a floppy (GRUP floppy excluded, that wouldn't be any fun)?

I'm still curious why my supposed non bootable (mostly doesn't) from cd ibm 380 ED lap that I tried with a wake pup ended up booting only ver 2.01 this way.. Said there were no pup files found on the other 2x variants I tried ?

Philh: Like you, one of the computers I tried would lock up on the USBASPI.SYS driver but work OK with aspiuhci.sys. Another computer that locked up on the USBASPI.SYS driver didn't work with aspiuhci.sys but worked OK with version 2.06 of USBASPI.SYS. Unfortunately, there doesn't seem to be a combination that works on all computers. I consider this a DOS USB support issue rather than a Puppy issue, but it is an issue none the less.

I'm starting to see this also. My one test machine has both 1.1 and 2.0 and it used to work with either or and now 2.0 won't work at all.

I'll work in a menu for the drivers next.

we'll have all loaded by default for people that don't know what to pick and a "custom option" for advanced users.

I usually use grub to load a wakepup image so I can boot from usb rather than a floppy.

How do you load wakepup from usb flash drive? Do you have to clear the drive before moving the image there and can you store some additional files to the drive afterwards? What kind of line you need in menu.lst for grub?

I'm still curious why my supposed non bootable (mostly doesn't) from cd ibm 380 ED lap that I tried with a wake pup ended up booting only ver 2.01 this way.. Said there were no pup files found on the other 2x variants I tried ?

Any thoughts? Gotta be something diff about 2.01?

Thought it was something about the early 2x variants (few of 'em booted but even there..not all) that was diff & maybe there still is.. Had no luck with booting variants higher than 2.02..

Ended up trying 2.17 & it booted. Turns out that the ones that didn't boot were cos I was burning 'em at whatever (high) speed & on r/w type disks. They all booted & worked on newer gear. Re-burned 2.13-4-5-6 at slow speed (x2) on write type disks & they all booted with a wake floppy.

The upcoming pup 2.20 has improved handling of pup installed into a directory, but just one-deep. So you could have the pup in:
/puppy220/vmlinuz
/puppy220/initrd.gz
/puppy220/pup_220.sfs
/puppy220/zdrv_220.sfs

where the directory name 'puppy220' is your choice. Puppy will also support the 'psubdir=puppy220' boot param, to avoid Puppy searching elsewhere at bootup.
But, WakePup really needs to do its search one-deep through all the directories in dos/fat partitions.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum