How to stop Bionicpup32 from booting with previous USB install?

[LarryP]

Greetings;

I have a full install of BionicPup32 8.0 on a HP Mini 210-2070NR. It works fine once booted up, but on initial boot it tries to go to a previous install on the USB. How do I delete the upupbb file that seems to be causing this?

[rockedge]

Delete the savefile/savefolder on the USB drive. Boot up in RAM only mode and go to the partition and just delete the save with the file manager or your prefered method. Then reboot, and the lack of any save file/folder will indicate to Bionic32 that it is a fresh start. If there are 2 or more save files/folders at boot the process will halt and prompt which one to use or none.

Describe what you have as a "full install". Since a true full install I think does not generate a save option since it writes directly to the file system

[bigpup]

How exactly did you do a full install?
I assume you installed to the computers internal drive?
What boot loader did you install to boot the full install?

What happens if the Bionicpup32 USB is not plugged in?

[LarryP]

I did the full install from the USB. Before I had the hard drive in hand I was running the whole thing from the USB that I created with unetbootin-windows-702, and when I got the hard drive installed I just followed the instructions I found on the 'net. If the USB is not installed I get an opening screen that has a GRUB4DOS window listing several boot options with "Puppy upupbb 19.03 (sdb1)" (which is what I named the file when it was created) at the top, then two of the same "BionicPup32 19.03 (sda1/boot)" followed by "Find Grub2", "Windows" and "Advanced menu" in that order. Selecting one of the two BionicPup32 entries boots it up like I want it to, except that if I don't select it right away I get a message saying it didn't shut down properly and to run the xorg utility or wait 30 seconds.

If I put the USB in, it comes up to the same GRUB4DOS window, but then boots up normally.

[LarryP]

Trying to delete the save folder on the USB brings up an error saying it is write only and can't be deleted.

[JASpup]

The USB boots the USB when plugged-in, but the full-install on HD makes you rush to choose an entry?

I have yet to attempt a full Puppy install, but I normally change G4D timeout times.

Example in G4D's menu.lst: timeout 90

That should give you a whole minute-and-a-half to make a choice.

It can be kind of confusing when you have the same os on both USB and internal. It's important to know which you're running.

My standard is to keep live sessions on the USB and pupsave/frugal internal.

[bigpup]

I think you may have configured Grub4dos menu, to have a entry for the install to the internal drive and also, a entry to boot the install, on the USB.
It will do that, unless you tell it to configure, only for a specific drive.

Do this, so the menu entry, when booting from the internal drive, is only for installs, on the internal drive.

Boot the computer and do not have the USB plugged in.
This for sure, makes the only thing running, is what is on the internal drive.

Look on the desktop, at the drive icons, showing lower left side.
All should be sda something.

Run the Grub4dos Bootloader Config
Select the sda drive as location, to install boot loader.
Select search within only this device
No other selections, need to be done.
Keep selecting OK, until program completes.

Now when you boot, from the internal drive.
The only boot menu entries, are for what is on the internal drive.

Note:
1st menu entry is usually the normal boot mode.