BionicPup32 (UPupBB) (27 June 2020)

[peebee]

3. HERE is where it goes wacky. I insert flash drive B into the same USB port. I click on its icon. A ROX window comes up, STILL showing the contents of flash drive A!

Hi 6502

Just tried this on a pristine frugal install of UPupBB.....

Afraid I don't see the problem you are seeing - have you changed Puppy Event Manager Settings in any way?

Can you try on a pristine frugal install and see if you still have the problem?

Thanks
peebee

[B.K. Johnson]

***D E L E T E D****

[B.K. Johnson]

I have been confounded for a while by the low setting of the volume control in the notification area (systray). I think I have found the reason. I now realize that it coincides with my switch from tahr-6.0.2 to 6.0.6. Like Mike Walsh, I had changed the boot sound. I had the systray volume display visible (unplanned) while playing with Mike's Startupsond when I saw the volume bars drop. I had the same result when I ran my script which sets amixer to -30db (Miks has -45db). So, it seems to me that the scripts need to reset amixer to its normal volume setting before exiting.
How do we do that?
This seems to work (percentage variable).

Code: Select all

amixer set Master 75%

Mike, please confirm that this observation occurs also in upupbb.

[6502coder]

@peebee

Sorry! False alarm on the ROX problem with swapping flash drives. After much investigation it turned out to be due to a flash drive that went bad.

[d_vineet]

I can see only 32bit iso's of UPupBB for download. I am aware that 32 bit versions can run happily on 64 bit m/c. Still, not having 64 bit iso is because there will not be any marked performance advantage of 64 bit over 32 bit version as far as UPupBB is concerned?

[peebee]

I can see only 32bit iso's of UPupBB for download.

Correct. There will never be a 64-bit UPup.

There is however Bionicpup64 7.9.8 CE RC by 666philb

[peebee]

Update to +26 on 02-feb-2019

1d6307e3c25a661d234b40043cd0e2df upupbb-18.05+26.iso

{delta}

Quite large ubuntu updates....surprising how much for an LTS version....

[tosim]

peebee-This morning I installed 1805+26 to newly formatted harddrive-ext4, flag set to boot. It's an older laptop, and with gparted, made the whole disk(75GB) into 1 partition. (I ran the CD first to ensure all was working, then did the format.) Started up with the cd in, and after upup was running, clicked the install button. Followed the instructions EXACTLY, but after the install was completed, shut down, removed the cd, and rebooted. Here is the only stuff that showed on screen:
wee 0> find --set-root /grldr
wee 15> /grldr
wee 17> _

I'm assuming it had something to do with booting. I did not choose grub4dos,and as I said earlier-I followed directions exactly. BTW- I've never had any problems dealing with the previous versions when running from multi-boot usb app. Would greatly appreciate any assistance. Thank you.

[6502coder]

Did a manual update from +25 to +26, which has been running just fine in several hours of use spread over 3-4 sessions over the past two days.

[peebee]

newly formatted harddrive-ext4, flag set to boot.

@tosim

I suspect you have used "64-bit ext4" which is a known problem - see:

http://www.murga-linux.com/puppy/viewtopic.php?t=111376
How to fix Grub4DOS Error 13, wee 13>, due to 64-bit Ext4

and this post from fredx181 shows how to fix the format:
http://www.murga-linux.com/puppy/viewto ... 51#1013051

[foxpup]

@tosim

There seem to be quite a few people that do a full install with a Puppy installer on hd ... and fail.

First: You better do a frugal install of Puppy. It is by far the preferred way for Puppy. Puppy is made to run this way.
It gives you more control and flexibility and it is safer.
You can even install frugal without installer, manually. It is easy and fast.

If you still want a full install, look on this topic:
Full installs not booting with Grub4dos generated menu entry

[tosim]

Thank you guys for your responses. Will get to it within a few days. BTW-This was a Frugal install.

[mikeslr]

Hi tosim,

Glad it's a frugal install. You posted "I installed 1805+26 to newly formatted harddrive-ext4". Emphasis supplied. If you formatted the drive using any Linux other than Puppy, it probably created a 64-bit Ext4 partition. Grub4dos can not write to 64-bit Ext4 partitions. This would result in 'wee' errors.

You can use the gparted in Puppies to format partitions as Ext4, as Puppies' gparted creates 32-bit Ext4 partitions to which grub4dos can write. But I suggest that you first install shinobar's recently released grub4dos-0.4.4.v1.9.4.pet. One of the things changed by this update is that it always installs 'wee' for mbr: http://www.murga-linux.com/puppy/viewto ... 43#1004943

[tosim]

Mikeslr:Thanks. However, if you go to the above link you posted(re shinobar...),the post right below that, from BarryK states,"
I looked into that "64bit ext4" problem, did not come up with a solution. However, Gparted creates 32bit ext4 filesystems, thus avoiding the problem. "

[mikeslr]

Hi tosim,

Clearing up a bit of confusion. Trying to install grub4dos to a 64-bit formatted partition is NOT the only reason one will receive notice of a "wee" error. Shinobar's update addressed the other reason.

[tosim]

OK,got it. Thanks again to y'all for the help. I'll mark this solved, if I can.

[peebee]

Update to +27 on 09-feb-2019

49e1c91e8c185963cd24ef2b5dd71f75 upupbb-18.05+27.iso

{delta}

Ubuntu updates....

[oui]

can we use a delta ON A ALREADY remastered ISO?

[peebee]

can we use a delta ON A ALREADY remastered ISO?

No...
post #2:

Delta updates are periodically issued and can be found here

They have to be applied to the original .iso

There is a utility to convert the delta to a pet which could then be loaded onto the remastered system.

[oui]

oh! ok, it was the main reason of that utility dotpet (I did understand it more generally as a change comparable with, in the past, the change between old dotpup's and modern dotpet's...)!