| Author |
Message |
josejp2424
Joined: 01 Aug 2010
Posts: 462
|
 Posted: Tue 30 Jul 2019, 20:02 Post subject:
kodi-18.3-leia
Subject description: For tests |
|
Kodi 18.3 Leia For tests
kodi-18.3-Leia.
# MD5
# 5191fd3e062645bd606009024d0bf1fd
_________________
Shiba Inu | Pupjibaro jessie | My Blog
|
|
Back to top
|
|
 |
alextome930
Joined: 01 Mar 2013
Posts: 3
|
| Posted: Tue 30 Jul 2019, 22:08 Post subject:
Re: why the system don't use my savefile? |
|
| blgs wrote: | | alextome930 wrote: | why the system can't find my savefile?
I did a frugal install on a USB-stick which had 2 partitions .I created a folder named dpupbuster64, and copyed initrd.gz vmlinuz puppy_dpupbuster64_8.0.0.sfs zdrv_dpupbuster64_8.0.0.sfs into it. Then I installed grub4dos on partition 1 with the following scripts:
| Code: |
title DpupBuster64 (sdd1)
find --set-root /dpupbuster64/vmlinuz
kernel /dpupbuster64/vmlinuz pfix=fsck pmedia=usbflash PSUBDIR=dpupbuster64
initrd /dpupbuster64/initrd.gz
|
it worked, the system boot well, audio graphic network are good .I can do anything . when i run shutdown or reboot , system asked me to create a savefile , i created a savefile (dpupbuster64save-0731.2fs) on partition 2 . Here is the problem: when I reboot the system, it couldn't find my savefile which just created. All the things I changed before reboot are gone.
What's the problem? Can anybody help me?
By the way, please forgive my pore English. |
I assume sdd1 is your boot partition (FAT or ext4) and sdd2 is the partition (ext4) where your save file is located.
Replace "PSUBDIR=dpupbuster64" by "psave=sdd2". During bootup the system while search dpupbuster64 at sdd2. |
Thanks for your answer. I tried replace "PSUBDIR=dpupbuster64" by "psave=sdd2" as your said. But I got this error, it couldn't find puppy_dpupbuster64_8.0.0.sfs. the system couldn't boot up.
There is an another puppy in my usb-stick, it is bionicpup64 8.0, and the menu.lst can be seen below.
| Code: |
title Puppy bionicpup64 8.0 (sdd1)
kernel /bionicpup8/vmlinuz pmedia=usbflash pfix=fsck
initrd /bionicpup8/initrd.gz
|
It works well, all the things are good. And the save file is in the sdd2/dpupbuster64.
But this pup can't , I don't know why.
|
|
Back to top
|
|
|
alextome930
Joined: 01 Mar 2013
Posts: 3
|
| Posted: Tue 30 Jul 2019, 22:12 Post subject:
Re: why the system don't use my savefile? |
|
| josejp2424 wrote: | | alextome930 wrote: | why the system can't find my savefile?
I did a frugal install on a USB-stick which had 2 partitions .I created a folder named dpupbuster64, and copyed initrd.gz vmlinuz puppy_dpupbuster64_8.0.0.sfs zdrv_dpupbuster64_8.0.0.sfs into it. Then I installed grub4dos on partition 1 with the following scripts:
| Code: |
title DpupBuster64 (sdd1)
find --set-root /dpupbuster64/vmlinuz
kernel /dpupbuster64/vmlinuz pfix=fsck pmedia=usbflash PSUBDIR=dpupbuster64
initrd /dpupbuster64/initrd.gz
|
it worked, the system boot well, audio graphic network are good .I can do anything . when i run shutdown or reboot , system asked me to create a savefile , i created a savefile (dpupbuster64save-0731.2fs) on partition 2 . Here is the problem: when I reboot the system, it couldn't find my savefile which just created. All the things I changed before reboot are gone.
What's the problem? Can anybody help me?
By the way, please forgive my pore English. |
The menu.list is fine.
but are you sure you saved the dpupbuster64save-0731.2fs in the sdd1 partition? |
Thanks for your answer. I saved the savefile in the sdd2, because there is not enough space on sdd1. so I chosed sdd2. I try to change to sdd1, but when the save program run, it never give the chance to change to another partition, it just let me change the folder.
|
|
Back to top
|
|
|
blgs
Joined: 07 Dec 2018
Posts: 20
|
| Posted: Sat 03 Aug 2019, 06:16 Post subject:
Re: why the system don't use my savefile? |
|
| alextome930 wrote: | | blgs wrote: | | alextome930 wrote: | why the system can't find my savefile?
I did a frugal install on a USB-stick which had 2 partitions .I created a folder named dpupbuster64, and copyed initrd.gz vmlinuz puppy_dpupbuster64_8.0.0.sfs zdrv_dpupbuster64_8.0.0.sfs into it. Then I installed grub4dos on partition 1 with the following scripts:
| Code: |
title DpupBuster64 (sdd1)
find --set-root /dpupbuster64/vmlinuz
kernel /dpupbuster64/vmlinuz pfix=fsck pmedia=usbflash PSUBDIR=dpupbuster64
initrd /dpupbuster64/initrd.gz
|
it worked, the system boot well, audio graphic network are good .I can do anything . when i run shutdown or reboot , system asked me to create a savefile , i created a savefile (dpupbuster64save-0731.2fs) on partition 2 . Here is the problem: when I reboot the system, it couldn't find my savefile which just created. All the things I changed before reboot are gone.
What's the problem? Can anybody help me?
By the way, please forgive my pore English. |
I assume sdd1 is your boot partition (FAT or ext4) and sdd2 is the partition (ext4) where your save file is located.
Replace "PSUBDIR=dpupbuster64" by "psave=sdd2". During bootup the system while search dpupbuster64 at sdd2. |
Thanks for your answer. I tried replace "PSUBDIR=dpupbuster64" by "psave=sdd2" as your said. But I got this error, it couldn't find puppy_dpupbuster64_8.0.0.sfs. the system couldn't boot up.
There is an another puppy in my usb-stick, it is bionicpup64 8.0, and the menu.lst can be seen below.
| Code: |
title Puppy bionicpup64 8.0 (sdd1)
kernel /bionicpup8/vmlinuz pmedia=usbflash pfix=fsck
initrd /bionicpup8/initrd.gz
|
It works well, all the things are good. And the save file is in the sdd2/dpupbuster64.
But this pup can't , I don't know why. |
I have installed Dpupbuster64 on a usb (uefi mode)
Partition one : sdb1 (FAT32) : all boot files including UEFI directory
Partion two : sdb2 (ext4) is containing the savefile in /
See below my grub.cfg file
Quote
insmod png
background_image /splash.png
set timeout=10
menuentry "Start dpupbuster64 8.0.0" {
linux /vmlinuz pfix=copy,fsck pmedia=cd pkeys=us plang=nl_NL psave=sdb2
initrd /initrd.gz
}
menuentry "Start dpupbuster64 8.0.0 - Don't copy SFS files to RAM" {
linux /vmlinuz pfix=nocopy,fsck pmedia=cd pkeys=us plang=nl_NL psave=sdb2
initrd /initrd.gz
}
menuentry "Start dpupbuster64 8.0.0 - RAM only" {
linux /vmlinuz pfix=ram,fsck pmedia=cd pkeys=us plang=nl_NL
initrd /initrd.gz
}
menuentry "Start dpupbuster64 8.0.0 - No X" {
linux /vmlinuz pfix=nox,fsck pmedia=cd pkeys=us plang=nl_NL psave=sdb2
initrd /initrd.gz
}
menuentry "Start dpupbuster64 8.0.0 - No KMS (Kernel mode setting)" {
linux /vmlinuz nomodeset pfix=fsck pmedia=cd pkeys=us plang=nl_NL psave=sdb2
initrd /initrd.gz
}
menuentry "Start dpupbuster64 8.0.0 - Ram Disk SHell" {
linux /vmlinuz pfix=rdsh pmedia=cd pkeys=us plang=nl_NL psave=sdb2
initrd /initrd.gz
}
menuentry "Shutdown" {
halt
}
menuentry "Reboot" {
reboot
}
Unquote
In my case Dpupbuster64 operates perfectly on usb stick. During boot-up the savefile on sdb2 is loaded.
I do not know what went wrong in your case. But it should work.
|
|
Back to top
|
|
|
josejp2424
Joined: 01 Aug 2010
Posts: 462
|
Posted: Sun 04 Aug 2019, 15:07 Post subject:
openbox plus 64
Subject description: openbox plus 64 |
|
for test
http://murga-linux.com/puppy/viewtopic.php?p=1033700#1033700
_________________
Shiba Inu | Pupjibaro jessie | My Blog
|
|
Back to top
|
|
|
ETP
Joined: 19 Oct 2010
Posts: 1163
Location: UK
|
| Posted: Mon 12 Aug 2019, 15:31 Post subject:
Testing: - dpupbuster64-8.0.0-uefi-beta3 issued 28/07/2019 |
|
Hi josejp2424,
Thanks for this beta. I did encounter some minor issues including the need to deviate
from my normal boot codes using syslinux. Other members also seem to have had problems
with different boot loaders and I wonder whether there have been recent WoofCE changes to
Puppy's standard boot codes such as psavemark= ?????
I will report in detail on the other minor issues in a separate post but wanted first to test
PulseAudio with SSR which I installed via PPM.
A link to a video held on Google Photos follows and SSR was a joy to use with PA.
The video may optionally be downloaded (142 MB)
https://photos.app.goo.gl/spuoAuu5bXgEZzXp9
.
_________________
Regards ETP
Kennels
|
|
Back to top
|
|
|
josejp2424
Joined: 01 Aug 2010
Posts: 462
|
Posted: Tue 13 Aug 2019, 07:17 Post subject:
Re: Testing: - dpupbuster64-8.0.0-uefi-beta3 issued 28/07/2019
Subject description: woof-ce |
|
| ETP wrote: | Hi josejp2424,
Thanks for this beta. I did encounter some minor issues including the need to deviate
from my normal boot codes using syslinux. Other members also seem to have had problems
with different boot loaders and I wonder whether there have been recent WoofCE changes to
Puppy's standard boot codes such as psavemark= ?????
I will report in detail on the other minor issues in a separate post but wanted first to test
PulseAudio with SSR which I installed via PPM.
A link to a video held on Google Photos follows and SSR was a joy to use with PA.
The video may optionally be downloaded (142 MB)
https://photos.app.goo.gl/spuoAuu5bXgEZzXp9
. |
hi ETP .
woof-ce has had changes, and very good changes.
I liked the videos, 
_________________
Shiba Inu | Pupjibaro jessie | My Blog
|
|
Back to top
|
|
|
ETP
Joined: 19 Oct 2010
Posts: 1163
Location: UK
|
Posted: Tue 13 Aug 2019, 16:30 Post subject:
Testing: - dpupbuster64-8.0.0-uefi-beta3 issued 28/07/2019
Subject description: More detail |
|
Hi josejp2424,
I agree that woof-CE has made great advances but sometimes fundamental changes are not communicated to our users.
The problem seems to be a lack of a readily viewable mechanism where new or changed behaviour can be detailed.
The obvious place for such announcements is the blog at puppylinux.com.
Forum member peebee I think, took it upon himself to post on 28/08/18 about important
changes to ROX-Filer in the testing branch of woof-CE.
http://blog.puppylinux.com/puppy-specific-version-of-rox-filer-in-woof-ce-testing-branch
Install was a manual frugal from the ISO to the 3rd f2fs partition (sdb3) on a 16GB USB2 stick.
Boot was provided by a vesamenu entry on the fat32 boot partition (sdb1) using syslinux 4.04.
The working entry was as follows:
| Code: | LABEL dpupbuster64
MENU LABEL Dpup Buster64 Beta3 11/08/19
KERNEL /dpupbuster64/vmlinuz intel_pstate=disable
APPEND initrd=/dpupbuster64/initrd.gz pmedia=usbflash pupsfs=sdb3:/puppy_dpupbuster64_8.0.0.sfs pdev1=sdb3
|
My initial attempt with
| Code: | | APPEND initrd=/dpupbuster64/initrd.gz pmedia=usbflash psavemark=3 |
booted but failed to find the save folder which had been created and populated.
Strange, as that has been working earlier this year when testing a variety of Pups
Items installed:
libdouble-conversion1_3.1.0-3|routines to convert IEEE floats to and from strings
libpcre2-16-0_10.32-5|New Perl Compatible Regular Expression Library - 16 bit runtime files
libqt5core5a_5.11.3+dfsg1-1|Qt 5 core module
libqt5dbus5_5.11.3+dfsg1-1|Qt 5 D-Bus module
libqt5gui5_5.11.3+dfsg1-1|Qt 5 GUI module
libqt5network5_5.11.3+dfsg1-1|Qt 5 network module
libqt5widgets5_5.11.3+dfsg1-1|Qt 5 widgets module
libqt5x11extras5_5.11.3-2|Qt 5 X11 extras
libxcb-keysyms1_0.4.0-1+b2|utility libraries for X C Binding -- keysyms
libxcb-xinerama0_1.13.1-2|X C Binding xinerama extension
simplescreenrecorder_0.3.11-1+b1|Feature-rich screen recorder for X11 and OpenGL
opera-stable_62.0.3331.99_amd64|Fast and secure web browser
ListDD-2.1|List dynamic dependencies
Pup-SysInfo-2.8.6|System information utility
startup_welcome_alert-mk2|Provides multilingual verbal Startup welcome plus Internet connection alarm
translate-shell_0.9.6.9-1|Command-line translator using Google Translate etc.
libfribidi-bin_1.0.5-3.1|Free Implementation of the Unicode BiDi algorithm utility
speechify|Add multilingual speech to system splash screens
cursor_themes-1-1|themes for mouse cursor
Notes:
In the above opera was a manual install of the official deb with a custom desktop file and suitable libffmpeg.so file in a
created directory - /usr/lib/x86_64-linix-gnu/opera/lib_extra
The cursor themes pack was installed over the top of the existing pack as I was unable to select any cursor. That did the trick.
A list of minor issues revealed by a ListDD system scan & examination of various logs is attached.
The bottom line is that IMHO, this is a great Pup with the potential to become an "official" Pup.
It is a pleasure to use with many novel features.
|
| Description |
Please remove false .gz
|
Download |
| Filename |
minor_issues.txt.gz |
| Filesize |
4.83 KB |
| Downloaded |
8 Time(s) |
| Description |
|
| Filesize |
12.82 KB |
| Viewed |
341 Time(s) |
|
_________________
Regards ETP
Kennels
|
|
Back to top
|
|
|
josejp2424
Joined: 01 Aug 2010
Posts: 462
|
Posted: Tue 13 Aug 2019, 22:22 Post subject:
Re: Testing: - dpupbuster64-8.0.0-uefi-beta3 issued 28/07/2019
Subject description: More detail |
|
| ETP wrote: | Hi josejp2424,
I agree that woof-CE has made great advances but sometimes fundamental changes are not communicated to our users.
The problem seems to be a lack of a readily viewable mechanism where new or changed behaviour can be detailed.
The obvious place for such announcements is the blog at puppylinux.com.
Forum member peebee I think, took it upon himself to post on 28/08/18 about important
changes to ROX-Filer in the testing branch of woof-CE.
http://blog.puppylinux.com/puppy-specific-version-of-rox-filer-in-woof-ce-testing-branch
Install was a manual frugal from the ISO to the 3rd f2fs partition (sdb3) on a 16GB USB2 stick.
Boot was provided by a vesamenu entry on the fat32 boot partition (sdb1) using syslinux 4.04.
The working entry was as follows:
| Code: | LABEL dpupbuster64
MENU LABEL Dpup Buster64 Beta3 11/08/19
KERNEL /dpupbuster64/vmlinuz intel_pstate=disable
APPEND initrd=/dpupbuster64/initrd.gz pmedia=usbflash pupsfs=sdb3:/puppy_dpupbuster64_8.0.0.sfs pdev1=sdb3
|
My initial attempt with
| Code: | | APPEND initrd=/dpupbuster64/initrd.gz pmedia=usbflash psavemark=3 |
booted but failed to find the save folder which had been created and populated.
Strange, as that has been working earlier this year when testing a variety of Pups
Items installed:
libdouble-conversion1_3.1.0-3|routines to convert IEEE floats to and from strings
libpcre2-16-0_10.32-5|New Perl Compatible Regular Expression Library - 16 bit runtime files
libqt5core5a_5.11.3+dfsg1-1|Qt 5 core module
libqt5dbus5_5.11.3+dfsg1-1|Qt 5 D-Bus module
libqt5gui5_5.11.3+dfsg1-1|Qt 5 GUI module
libqt5network5_5.11.3+dfsg1-1|Qt 5 network module
libqt5widgets5_5.11.3+dfsg1-1|Qt 5 widgets module
libqt5x11extras5_5.11.3-2|Qt 5 X11 extras
libxcb-keysyms1_0.4.0-1+b2|utility libraries for X C Binding -- keysyms
libxcb-xinerama0_1.13.1-2|X C Binding xinerama extension
simplescreenrecorder_0.3.11-1+b1|Feature-rich screen recorder for X11 and OpenGL
opera-stable_62.0.3331.99_amd64|Fast and secure web browser
ListDD-2.1|List dynamic dependencies
Pup-SysInfo-2.8.6|System information utility
startup_welcome_alert-mk2|Provides multilingual verbal Startup welcome plus Internet connection alarm
translate-shell_0.9.6.9-1|Command-line translator using Google Translate etc.
libfribidi-bin_1.0.5-3.1|Free Implementation of the Unicode BiDi algorithm utility
speechify|Add multilingual speech to system splash screens
cursor_themes-1-1|themes for mouse cursor
Notes:
In the above opera was a manual install of the official deb with a custom desktop file and suitable libffmpeg.so file in a
created directory - /usr/lib/x86_64-linix-gnu/opera/lib_extra
The cursor themes pack was installed over the top of the existing pack as I was unable to select any cursor. That did the trick.
A list of minor issues revealed by a ListDD system scan & examination of various logs is attached.
The bottom line is that IMHO, this is a great Pup with the potential to become an "official" Pup.
It is a pleasure to use with many novel features. |
hi ETP .
Thanks for the tests, and the details offered. .
and hopefully in the next iso, the errors will be fixed.
_________________
Shiba Inu | Pupjibaro jessie | My Blog
|
|
Back to top
|
|
|
josejp2424
Joined: 01 Aug 2010
Posts: 462
|
Posted: Tue 13 Aug 2019, 22:41 Post subject:
virtualbox 6
Subject description: virtualbox 6 |
|
VirtualBox 6.0
Download VirtualBox 6.0
MD5
# 7d447d7c990e9b624bebfa4b139d47bd
_________________
Shiba Inu | Pupjibaro jessie | My Blog
|
|
Back to top
|
|
|
blgs
Joined: 07 Dec 2018
Posts: 20
|
| Posted: Wed 14 Aug 2019, 02:40 Post subject:
dependency check in Dbuserpup64 |
|
Please include a program to verify the dependecies of the installed programs.
Some .deb programs can be installed but won't work e.g. megasync.
By checking the dependency of a program, the missing files can be installed afterwards.
|
|
Back to top
|
|
|
foxpup
Joined: 29 Jul 2016
Posts: 913
Location: europa near northsea
|
| Posted: Wed 14 Aug 2019, 04:28 Post subject:
|
|
I think josejp2424 has installed pkg from sc0ttman. You can use that.
You can use it from the terminal!
http://murga-linux.com/puppy/viewtopic.php?t=112927
|
|
Back to top
|
|
|
josejp2424
Joined: 01 Aug 2010
Posts: 462
|
| Posted: Wed 14 Aug 2019, 08:20 Post subject:
Re: dependency check in Dbuserpup64 |
|
| blgs wrote: | Please include a program to verify the dependecies of the installed programs.
Some .deb programs can be installed but won't work e.g. megasync.
By checking the dependency of a program, the missing files can be installed afterwards. |
if it's true,
ListDD should be installed
_________________
Shiba Inu | Pupjibaro jessie | My Blog
|
|
Back to top
|
|
|
josejp2424
Joined: 01 Aug 2010
Posts: 462
|
Posted: Thu 15 Aug 2019, 14:15 Post subject:
wine 4.13
Subject description: for test wine |
|
for test Wine 4.13 Multilib.
Wine 32 bits 4.12.1
Wine 64 bits 4.13
Download Wine 4.13
MD5
# 672d061cbb96c0342b0856298daa51f4
_________________
Shiba Inu | Pupjibaro jessie | My Blog
|
|
Back to top
|
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index » Advanced Topics » Puppy Projects
