Tnx 666philb and peebee.
Maybe fixed in v1.9.4.

#2018-09-18 v1.9.4: merge woof, fix chain loading grub2, always install wee as for mbr, fix for full installed (mavrothal)
grub4dos-0.4.4.v1.9.4.pet (2018-09-18)
http://shinobar.server-on.net/puppy/opt/

baraka, thank you for your co-operation and the report.

Avoid GL libraries confliction with some Puppy's.
Tested on bionicpup64.
getnvidia-1.5.pet
http://shino.pos.to/party/bridge.cgi?puppy/opt/

Tnx baraka for the testing.
I realized and hope fixed the 64bit problem reading your report.
Try v1.4:
getnvidia-1.4.pet
http://shino.pos.to/party/bridge.cgi?puppy/opt/

getnvidia-1.3 is tested both on UPup-bb(32bit) and on Bionicpup64. It depends on the NVIDIA*.run you choose, whether 32 or 64bit. getnvidia-1.3.pet shows its version as '1.2'. Uploaded 1.3-1.pet which shows correct getnvidia version. getnvidia-1.3-1.pet http://shino.pos.to/party/bridge.cgi?puppy/opt/

Try v1.3:
getnvidia-1.3.pet (edit: replaced by getnvdia-1.3-1.pet)
http://shino.pos.to/party/bridge.cgi?puppy/opt/

baraka wrote:Again, imho I think that is something wrong with the GLX libraries or render mode.

Well, i think some optional packages need for some puppy.

Not fully tested but hope to be usable:
getnvidia-1.2.pet
http://shino.pos.to/party/bridge.cgi?puppy/opt/

Tnx peebee.

#2018-09-18 v1.9.4: merge woof, fix chain loading grub2, always install wee as for mbr, fix for full installed (mavrothal)
grub4dos-0.4.4.v1.9.4.pet (2018-09-18)
http://shinobar.server-on.net/puppy/opt/

Updated:
grub4dos-0.4.4.v1.9.3.pet (2018-08-03)
http://shinobar.server-on.net/puppy/opt/

#2018-08-03 v1.9.3: fix chain loading grub2, always install wee as for mbr, fix for full installed (mavrothal)

I hope 32bit PAE kernel with forcepae option available such as kernel 4.0.4-tahr_PAE.

puppyapps(Default Applications Chooser) fails hen you select category ALL button. Tow lines to be fixed: # diff -u puppyapps.old puppyapps --- puppyapps.old 2016-09-18 16:40:26.000000000 +0900 +++ puppyapps 2017-02-25 16:35:37.000000000 +0900 @@ -232,7 +232,7 @@ update_defaults () { LANG=C # change ...

gyro, thanks for your discussion, but I do not understand it.

You are talking which place the extra sfs'es to be searched.
I am just talking that '/mnt/home' is always a symlink points 'initrd/mnt/dev_save' under PUPMODE=12 or 13.

Uploaded sfs_load-3.0.3.pet, fixed subdir issue and LASTUNIONRECORD issue.
http://shinobar.server-on.net/puppy/opt ... -3.0.3.pet

Thanks mavrothal. It solves the problem. Besides, I think sfs_load is better to reform on the /mnt/home handling. Using '/mnt/home' is just for human interface. Internally, it can be treated as '/initrd/mnt/dev/save'. --- sfs_load-300 2016-09-11 07:30:18.000000000 +0900 +++ sfs_load 2017-02-26 12:14...

peebee wrote:you have to do it in the opposite order:

Make pupsave then
Install sfs

Then all is ok after reboot.

Right, for atahdd(PUPMODE=12).
But it doesn't solve the issue for usbflash/ataflash(PUPMODE=13).

That IS strange :? As i said I do not see that (anybody else?) Yes strange. But i got it :) You can reproduce the issue: (1) Furugal install in a subdir and some extra SFS in the same subdir. (2) Boot without pupsave. (3) Load the extra SFS in the subdir. (4) Save the session making a new pupsave. ...

using the latest puppy builds in a frugal install (in a subdir) SFS_load 3.0 detects the SFSs in the subdir, loads them fine and they load again correctly on reboot. I tried on the Slacko-6.9.6.4 and also on the LxPupSc-17.02.1T frugal install in a subdir. The SFS in the same subdir loads fine, yes...

By the way, sfs_load v3 in the Slacko-6.9.6.4 fails to load extra sfs's in the sub folder(psubdir) at boot. Fixed. http://shinobar.server-on.net/puppy/opt/pup5/sfs_load-3.0.2.pet --- sfs_load-300 2016-09-11 07:30:18.000000000 +0900 +++ sfs_load 2017-02-23 21:38:16.000000000 +0900 @@ -62,7 +62,7 @@ M...

Thanks mavrothal and gyro for your discussion. My lang_pack_ja-2.0.sfs uses the LASTUNIONRECORD record. Japanese forum members found it fails as for the recent puppies. My proposal above is one solution for this problem. I think I need to read threw the init and rc.sysinit script so that I can make ...