I don't think there is anyway to tell the difference, for certain, in code. The USB class/subclass/protocol seems to be rather unrespected by hardware makers. There is a place for them, but my drives don't seem to fall in line.

Thanks for your suggestion but I am not booting from the USB hard drive I am just using it to store my pup_save configuration file. If I use either of the pmedia commands the boot process expects the boot files to be on the selected device. I agree it would be difficult to determine if the USB attached device was a USB flash, compact flash or hard drive; therefore, if there were a boot command to tell puppy my pup_save files were being stored on a hard drive attached via USB would solve this problem. I know most people do not use a USB attached hard drives and if they do, they boot puppy from the USB attached hard drive. Puppy is by FAR the most flexible Linux distribution I have tried and adding this capability would put Puppy further out in front. NOTE: Puppy works fine thinking the pup_save file is stored on a flash device it just could work better if puppy could be told the pup_save file was on a hard drive.

- Sound works well, at least on my old test-PC; Zmixer had no mute buttons, the Puppy mixer has but mutes an input device by throwing its fader to zero. It would be best then if it could keep the fader setting when muted, giving the same volume as before when un-muted, as in hardware mixers;

- Pmount seems to work well, more intuitive GUI.

More to come as testing goes further.
Anyway fine job Barry, always wondering how you manage to do all this...

Above I wrote negatively about Gxine. I have just edited that out. Please disregard. I was not comparing Gxine with other players, just complaining that I couldn't get it to work. Well, I have finally got my installation fixed and it works. As usual Barry has shown good judgment in this selection.

But I like to run a tight ship, and have already dumped realplayer and the neat xfreecd I had used as bandaids. Sorry for any confusion caused.

1.
216 alpha is good when I take a full installation on ext2/swap partitions and on usb stick. But i was failed to make it run with the frugal install.
Is this a bug?
2.
216 alpha was not automount the my .sfs file with full installation?. How to?

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 have to use that the first time you boot to specify what sfs files you want to load - its a nice, simple program and allows for a lot of flexibility and granular control

The iso I downloaded might be corrupted, but I thought I'd report this to see if anyone else is having the same problem with 2.16a multisession.

burniso2cd has been problematical on my system for the last 2 or threee versions of Puppy. Does not seem able to burn a normal ISO far less deal with multisession. I tried Gcombust - was OK with ISO but not OK with multisession.

I now use Xcdroast. It seem to work OK. This is the debian dotpup from Mark Ulrich's puppyisos server. Other versions including the standard version installed via petGet are missing dependencies and do not run.

Wonder if burniso2cd needs some attention._________________Life is too short to spend it in front of a computer

Glad to have you back. I enjoyed your trip report and pix.
When I encountered the show-stopper with Gparted, I had booted from CD with pfix=ram so I could operate on the entire drive. No update/upgrade involved.
Richard