Problem with booting Slimpup LiveCD[Solved]

[ubume2]

I was attempting to try out Slimpup 2.4. I booted from Live CD and noticed -- searching for Puppy Files on HD. I chose 0 (not to use files) and it still booted into my Puppy 525.

I had tried Puppy Lite earlier and did not have that problem.

I tried F2 key and tried some of the options there, but it still booted into 525.
Is there a solution to this? I just wanted to try it out live.

Thanks

[Ian]

I am not familiar with Slimpup but did you try 'puppy pfix=ram'
at bootup.

[ubume2]

I am not familiar with Slimpup but did you try 'puppy pfix=ram'
at bootup.

Hi, I tried that and several other options, but a no go.

I did install it frugally on a 2gig partition I had left over on my HD. Playing with it now.

Puppy Likes to use existing Puppy files on the hard drive when booting. I think I had to delete one of them after Slimpup installation to make it look like Slimpup, and not Lupu.

Thanks.

[ICPUG]

If Slimpup uses the same filename as lupu for its sfs file I can understand the problem.

A solution would be to specify on bootup the device, partition and folder where the sfs file is stored.

PMEDIA boot parameter is used to specify the device
PDEV1 boot parameter is used to specify the partition
PSUBDIR boot parameter is used to specify the folder

Any puplet based on a woof from this year will then only look at the specific folder identified.

In this way any number of puplets can be frugally installed.

with a live CD I would suggest just specifying PMEDIA to identify the cd device, i.e
pmedia=cd

Any files on the hard drive should now be ignored.

[ubume2]

Hi thanks for the response.

As it turned out, when I booted from CD, Slimpup came up with the same wallpaper and apps as my lupu525.

When I installed SlimPup, I changed the folder name to /Puppy. It booted up fine and looked like it was supposed to.

Having fun with another neat Puppy derivative:)

I do have SlimPup in a different partition than my Puppy Lucid.