Edoc. I dont use grub, but insted grub4dos...so I cant comment all your definitions, but....

PMEDIA accepts and understands these parameters: pmedia= usbflash|usbhd|usbcd|ataflash|atahd|atacd|atazip|scsihd|scsicd|cda
Above is straight from Puppy init script so...you can count that above is correct. There is no idehd.
I suggest you to use PMEDIA=atahd parameter

I think I have that on one of the laptops here but I don't recall why.

pemasu wrote:

I suggest you to use PMEDIA=atahd parameter

I don't recall when it was along the way that I had to use "PMEDIA=idehd" and whether it was hardware-related (specific to the Toughbooks or a Netbook anomaly or what) and then just was copied from there.

I will try "PMEDIA=atahd" and see how that works.

pemasu wrote:

PDEV is wrong also, it should be PDEV1=

Oddly, I have the "1" in the menu.lst for the laptop but had cut and pasted from the file on this netbook where I do not. It has been working OK on the netbook - I wonder what is the purpose?

I have added the "1" to the netbook menu.lst and will see what happens when I reboot.

pemasu wrote:

You seem to have kernel and initrd.gz in different partitions ?

That was a typo, sorry.

pemasu wrote:

acpi=noirq nosmp vga=normal ----> are you sure you need these ?

Those are all recommendations from the past when chasing various hardware problems. I don't recall if they are BIOS or hardware specific. Most of the same hardware has been in use here for several years.

I have grub4dos grldr and menu.lst in ntfs partition and I boot windows 7 (when I need it) and all my Puppies from that ntfs partition.

It was easier for me and I also use Shinobar`s grub4dos bootloader config when I need. It has worked for me. It is just question of preferences. Use grub or grub4dos which ever you knows best. It is grub4dos for me.

First of all. This woof build is based on Iguleders work. He has single-handed done all the work for reviving dpup <snip snip>

ooooOOOOOOooo... I just noticed, multiple instances are working in this one !

pemasu... I think Iguleder fixed it while you werent looking : -)

The multiple instances were always a favorite feature of mine in the older dpup
series... so useful when experimenting with recent apps which might break the
good install... for other special uses too.

Thanks to both of you for getting dpup modernized and back together... for debian
people who use puppylinux, this is a real help. Ive been using it for over a month.

soundNICK, Exprimo is (IMHO) the strongest-going puplet I've seen and I think it has a very bright future ahead - it could be the next mainline Puppy.

But ... I believe it's just the beginning. It has endless potential! Before you give it the warm compliments it deserves, let's think of what the future holds for it.

I implemented Raspbian support in roar-ng (my distro building kit) while I'm waiting for Raspberry Pi to arrive. My next plan for the dpup world is to port it to ARM: Puppy for ARM exists and Debian for ARM exists, too. I just want to see how wonderful it could be if we fused the two together.

The first step is to build highly optimized ARMv6 packages - the rest will follow. That's the first thing I'm going to do when I get my Pi already. Using dpup as a platform for porting Puppy looks like a great idea to me - it could be any of Debian's supported architectures, you name it

By the way, today I got my distro to build for x86_64 against Slackware 14.0 packages - I don't see why it couldn't be Exprimo for ARMv6. _________________My homepageMy GitHub profile

soundNICK, Exprimo is (IMHO) the strongest-going puplet I've seen and I think it has a very bright future ahead - it could be the next mainline Puppy.

But ... I believe it's just the beginning. It has endless potential! Before you give it the warm compliments it deserves, let's think of what the future holds for it.

I implemented Raspbian support in roar-ng (my distro building kit) while I'm waiting for Raspberry Pi to arrive. My next plan for the dpup world is to port it to ARM: Puppy for ARM exists and Debian for ARM exists, too. I just want to see how wonderful it could be if we fused the two together.

The first step is to build highly optimized ARMv6 packages - the rest will follow. That's the first thing I'm going to do when I get my Pi already. Using dpup as a platform for porting Puppy looks like a great idea to me - it could be any of Debian's supported architectures, you name it

By the way, today I got my distro to build for x86_64 against Slackware 14.0 packages - I don't see why it couldn't be Exprimo for ARMv6.

Iguleder - I couldnt agree more about Exprimo being a strongest contender... part of this...
a lot of it... is the debian connection. However much slower the debian development
cycle [appears] to be, debian remains one of the best developed most refined and
consistently working distros_ adding puppylinux scalability / flexibility to this has to be
a total win.