Puppy Linux Discussion Forum

[musher0]

Hi Glen.

Thanks for the logging code.

As to your 256 G Sandisk "locked" problem, I'd post it on its own thread in
the forum. You have a much greater chance of drawing attention from
people if it has its own title in the threads list -- than buried here.

As for me, I am pretty much clueless (with a couple of exceptions)
concerning hardware. So... no, I won't give you a bash one-liner for this,
I'm not that sure of myself!!!

However, my initial instinct would be to answer: have you tried to change
the properties of the partition through the ROX-Filer ? Please see attached
capture.

That panel can be obtained by typing Ctrl-P in /mnt; then a crosshair
appears, and then you click on the desired partition with this crosshair.

You should be able to change (tick / un-tick) any of the boxes. But don't
mess with it. The example presented allows read-write-and-execute for
anything on this ram1 partition (in other words: it is the default, as it
should be for regular use partitions).

Perhaps you need to do this from the Puppy or OS the crash occurred on.
(Note the "perhaps".)

I'd also suggest a poweroff and reboot of your Pup with the drive connected.
Sometimes, this by itself is enough to reset the normal partition defaults.

Poweroff, not just reboot. As in:
-- poweroff everything, including turning off the monitor, the speakers, and
any outside drive;
-- wait a couple of minutes;
-- turn everything on again, and then reboot as you normally do.

IHTH.

[glene77is]

Musher
Thanks for the tips.
Have tried most, and will go through all again.

Always a possibility,
I may have mounted it away from the fan,
and the 256 GB flashdrive got hot with mass copying.
Normally, I keep the large flashdrives by the fan,
hanging on a USB multiport. Otherwise, they get hot on mass copying.
When I say 'mass copying',
I refer to a mass copy of my 'backup' 256 GB
onto a new 256 GB.

Have gone back to the Hard-Drive and installed puppy distros for :
Lupu 525, Slacko 57, Slacko 632, Tahr 605, Xenial 708.
Have set up Directory version and/or the 4fs version
and plan to have both versions available from menu.lst.
Most function OK now.

I have found I like developing/mucking/tinkering in the Directory version.
I like the security made available by skipping the save2flash function.
When I make a mistake in codework, I just break-out and "reboot"
which reloads the prior version and I can start again.

Since I do frequent save2flash and then xarchive the savefiles
( which include a date-time-stamp in their name )
I noticed that the 256 GB flashdrives can get hot.
So, I hang then from a USB multiport, over the computer fan.



For developing a 4fs version,
to include custom display tracking and logging functions,
I use this technique :
(1) I have been able to load the 4fs version into Geany
( all relevant programs like rc.sysinit, rc.shutdown, sfs_load, fixmenus)
(2) then import (via Geany ) from the Directory version.

It is basically a Careful "copy/paste all" method.
WHEN I do a
(1) Geany "save"
(2) "save2flash"
THEN the 4fs file updates all index and file lengths.

I found an un-suspected feature
when setting pmode = ataflash or atahd or usbflash.
In general :
(1) "ataflash" or 'usbflash' requires a Linux ( ext2,3,4 partition) Directory ,
and allows the 'asktosave' to control saves.
(2) "atahd" can use the current hard-drive NTFS partitiion,
in a 4fs savefile, with 'auto save' .

This little discovery allows me to run Xenial ( both 4fs and Directory)
on my hard-drive system computer.
Prior to this, I had to always run the 4fs version on the hard-drives.



#==============================================================================
#&&& Xenial 7.0.8 GAE sample Log Method
#==============================================================================

### Assume that in rc.sysinit, you echo a little string > to clear/init the LogFile.

### Insert this "sample Library Subroutine"
in the first lines of each file to be logged.
### Each running script file will call itw 'own' logfunk???"
which inserts the script name.
### This example is for "sfs_load", and it titled "logfunksfs" .

### Script for "fixmenus", and all other files is similar ,
### just ID each program: "sfs_load","fixmenus", "rc.sysUP", "rc.sysDN", etc.
### Each of these programs makes many calls to its own "logfunk???"
### This example is for "sfs_load", and it titled "logfunksfs" .

#~ logfunksfs() {

### (1) name of current running script ;
ie, rc.sysUP, rc.sysDN, sfs_load, fixmenus .
#~ lcNameStr="sfs_load"

### (2) incoming parameter message,
#~ lcMsgStr="'$1'"

### (3) date-time-stamp
#~ lcDtsStr="`date -R | cut -f 2-5 -d ' ' | cut -f 1 -d '.' | tr '[a-z]' '[A-Z]'` z"

### (4) logging target file
#~ GaeLogFunkUp="/GAE-log-funk-up.tmp"
### filename copied from /etc/rc.d/GAE/GAE-SPEC
#~ lcFileStr="${GaeLogFunkUp}"

### build final string to write
#~ lcMsgStr="$lcNameStr : $lcMsgStr : $lcDtsStr "

### ( ) echo out to logging file.
#~ echo -e "$lcMsgStr" >> ${lcFileStr}

#~ } ### end logfunksample
###...........................................................................




I don't think I am presenting anything really 'new' for you,
just a 'sharing' exercise.
As always, YMMV ( your milage may vary ) .

[glene77is]

Guys,
I have resolved "my" problems with HardDrive Xenial 7.0.8
not reading a Directory SaveFile.

My old eyes did not see the difference between "," or "."
and sometimes I just imagined that there was a "," or "." written in place
--- yuk!.

So, Xenial frugal alongside M$XP :
(1) The SaveFile.4fs are installed on sda1 ( format NTFS )
(2) The SaveFile Directory are installed on sda5 ( format EXT2 )

I find that Xenial is the more tolerant of errors,
compared to Slacko 632.
YMMV !

Thanks for a place to write my little adventures.

[musher0]

Hi glen!

Thanks for the infos.

And thanks for the thanks about the writing space! (Although those should
actually be directed to forum moderator Flash and forum owner John Murga.)

BFN.

[musher0]

Hello all.

I recompiled the Sound eXchange (aka sox or SoX) version 14.4.2 (2015;
latest v. as of this writing) for xenialPup-706. It is available at:
https://augras.eu/puppy_linux/musher0/xenialPup-706-k41/Multim%C3%A9dias/SoX-14.4.2.pet

Those of you who do not know SoX, please head for:
http://sox.sourceforge.net

In short, SoX is a sound suite in CLI that can generate sounds, play a wide
range of music formats, and process tags of music pieces. But please go
read the docs? No summary can do it justice.

Enjoy!