(old)Puppy Linux Discussion Forum

L18L wrote:Never got any new puppy or fatdog or quirky run on my computer before.

Archlinux gave me a solution.

No xorg driver modesetting needed
Only disadvantage: resolution cannot be changed without reboot.

Other operation systems which I could get running are slacko64 and remixOS (matter of kernel configuration).

stemsee wrote: I had trouble with screencaster; when changing directory for recordings to ~/Downloads, the recordings were being deleted. on examing the script I commented out one line and now its fine.

Back in early Jan 20167, dr. Dan wrote:Hello all, I decided to try to improve the fatdog-battery-meter.sh script myself. It was a poor use of my time, but I know a little bit about the language now. Anyway, I added a rudimentary time left estimate which works on two different laptops so far.

Compared with 702, my battery life seems diminished. I don't know whether it is from using Seamonkey, but it seems to use a lot of memory.

Thanks for letting me play the home version of Fatdog64, it's a lot of fun. I keep finding additional features!

jamesbond wrote: I'm going to take your latest momanager and push it to the official repo, thanks!

CACHE=$WD/cache ;  mkdir -p $CACHE #130505
cd $WD #170224-2

L18L wrote:Made and used in Fatdog64 (and latest slacko64)
Not intended to run in arm architectures.

## jamesbond - check arch
case $(uname -m) in
	x86_64|i*86) ;; # good to go
	*) Xdialog --title "MoManager" --infobox "Unsupported architecture: $(uname -m)" 0 0 10000 
	   exit 1;;
esac

jamesbond wrote: If small size is really what you're after, you can always run the splitter like this:

Code: Select all

BASESFS_COMPRESSION="-comp xz" fatdog-split-initrd.sh ...

dr. Dan wrote:@jamesbond: Thanks for looking, and I am only intending to be helpful to someone.

Just for curiosity, since I really do not know that much about system stuff, what files are in your laptop's path "/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/" (AKA the location of "$POWER_PATH/*/charge_now" on my systems? I had success on a Dell and a HP. I could try an Acer and an Asus, just to learn something.

I might be able to try running 702 and then 710 as a test, but it would be fairly inconvenient just now, so I'll ask for low expectations.

By the way, I installed FD710 on this HP using the Windows bootloader option, but it required a fair amount of research to learn how to configure the Windows 7 boot system to work. It was far from automatic!

Thanks as always.

jamesbond wrote:

dr. Dan wrote:I might be able to try running 702 and then 710 as a test, but it would be fairly inconvenient just now, so I'll ask for low expectations.

By the way, I installed FD710 on this HP using the Windows bootloader option, but it required a fair amount of research to learn how to configure the Windows 7 boot system to work. It was far from automatic!

When you have installed it, the installer will create a file that you can run to automate the process; but it is highly recommended that you read the file before doing anything. There are several modes of Win7 installation, but I remember if you follow the common cases, you should be able to find that file in your C: drive when you boot to Windows. Did you see this file? What exactly did the problem you encounter?

Thanks as always.

Much welcome.

dr. Dan wrote:This was in regard to your suggestion that I compare idle state between the two for battery consumption.

Thanks, it is working fine. I read the instructions repeatedly, ran the .exe file, but it did not accomplish the install successfully, so I modified the necessary files myself. I don't have enough understanding to help with diagnostics.