Hope you've been well, Fred, with good health and summertime spirits. Have a question, and I wasn't sure where to post it. It is related to DebianDob (in a way), so here goes (am posting this from DD32, it's still going strong and impervious to my shenanigans and knack for crashing OSes ):

I've got two small partitions where one is Debian Jessie Live 8.7 installed, and another is Debian Stretch 9.0 (both 64-bit) on an external hard drive. Both are full-installs. There's probably ~15 other pups there too in another partition, all frugal installed. Grub4dos governs everything (all partitions).

These two small partitions of full-install Jessie & Stretch I use just to keep up with Debian overall, and also to test stuff every once in awhile. One thing that has always bugged me about official Debian installs is the tedious CLI entries just to mount any ISO you have. So to remedy that, I long ago copied Terry's/ your & Toni's "mnt-img" script in /usr/local/bin and put it inside both Jessie & Stretch. Works great, one click from any file manager, and all ISOs open (have no need any ISO editing, just copying stuff inside it)..

But I'd like to be able to do the same with any ".sfs" files inside the ISO. You know, like easily happens in the Puppys, where one click on any SFS (no matter where it is) mounts it and lets you look inside (and thus copy anything you might want). Is that possible for SFS files in Debian full installs using some of your scripts out of DebianDog32?? If so, can I ask how would I do that?

So far, I've tried (copying into Jessie & Stretch) the DD32 scripts of "portable-sfs, loadsfs, loadsfs-fuse, loadsfs-fuse-writeoffs" (and also made sure that unionfs-fuse is in /usr/bin of both Jessie & Stretch) since it is a dependency. But I still can't get a SFS, no matter where it is, to just load/ mount and thus let me look inside to copy a few things from it.

But I'd like to be able to do the same with any ".sfs" files inside the ISO.

I'm not sure which mnt-img version and file manager is included in the iso you use for this but it should be a simple sfs file association problem. Try to right click on sfs file and "open with" mnt-img. Then set as default run action in the file manager.

But I'd like to be able to do the same with any ".sfs" files inside the ISO.

I'm not sure which mnt-img version and file manager is included in the iso you use for this but it should be a simple sfs file association problem. Try to right click on sfs file and "open with" mnt-img. Then set as default run action in the file manager.

Tried all three of your links, none work for opening a SFS file (in either Stretch and/or Jessie) in my Debian Live installs. I was also using the "mnt-img" from Fred's last DebianDog32 release. All 4 open any ISO great, but that's it.

I just realized that possibly the reason none of them work is that both my Debian installs (Jessie & Stretch), on their own partitions, are not "full-installs" per se. I used their Debian Live Minimal install ISOs (respectively) for each when setting them up. On Jessie, I'm running LXDE/PCManFM. On Stretch, it's XFCE/Thunar, though I did install the full offering from XFCE. So maybe something is missing from Debian overall since I only did minimal installs, I don't know??? (I honestly thought XFCE in Stretch with the "mnt-img" script would work, but sadly no.)

If it makes any difference, the Jessie minimal install has PCManFM as its file manager. I just now, from Synaptic Package Manager, also installed "xfe" (alongside PCManFM) and then opened xfe & right-clicked on a "SFS" and told xfe to use the script (put "mnt-img" in .config/xfe/script folder) to open the SFS. Still, nothing happens. So I must have something missing, as compared to "full" debian installs, in my minimal installs.

Just wish I knew what was missing. It's frustrating not being able to peek inside SFS files (and copy stuff) whenever I want and/or is needed.

If it makes any difference, the Jessie minimal install has PCManFM as its file manager. I just also installed "xfe" and put the script you mentioned (#2) in your message in the ./config/xfe/script folder, and then right-clicked on an "SFS" and told xfe to use the script to open the SFS, and still nothing. So i must have something missing, as compared to "full" debian installs, in my minimal installs.

Just wish I knew what was missing. It's frustrating not being able to peek inside SFS files (and copy stuff) whenever I want and copy stuff.

Have you tried a simple

mkdir mountpoint
mount some.sfs mountpoint
cd mountpoint
ls

Also, you are running with union=aufs kernel boot parameter? Try df -h and make sure there's a "aufs" being shown in there somewhere. If its overlay then you'll have to install aufs-dkms and add that union=aufs to your kernel boot parameters.

As Toni already said my first thought was also that file association for .sfs should do it.
On Debiandog it's done that way, with on DD32 openbox version as Thunar default filemanager.
Try install this package maybe (if you have Thunar installed):
https://debiandog.github.io/Jessie/i386/Packages/Included/filemnt-thunar_1.0.1_i386.deb
The command used in DD32 is: filemnt (which is symlink to mnt-img, so in fact shouldn't make any difference)
You should get some error message maybe by running in terminal e.g:

G'day Fred & Any Other Able Helpers, 1stly Thanx Fred 4 Your Modified isobooter-mod it Does Work Booting Your Original XenialDog_32bit-OpenBox_jwm-2017-01-22-firmware-all (casper-Boot).iso ( Number 18 on Me menu.lst File, Just Under M$ Windows 7 Virus Bait! that Does also Boot

Thanx Toni 4 your reply, that didn't work, Still the same Error 15, File not found, that Modification that yoU suggested was the same as Answering No 2 the Splash Screen Question, which Curiously is Wot Works 4 XenialDog 32bit OpenBox...

But Here's Another Clue, When Booting the PC it Doesn't Display the same as the menu.lst File, in Fact it Splits XenialDog 32bit OpenBox.... into 2 Choices Casper Boot or Porteous Boot, it's All Too Magic Trickery 4 Me 2 Understand!?

Maybe the problem you have is because the ISO name contains spaces.
Try to rename to e.g. Angel_Student_Eco-Educational_XX-E17_PC_KloneOS.iso and see if it works then.
EDIT: you can run isobooter-mod again then, maybe there's risk of fragmentation because of renaming, don't know, better to check it, or just edit the entry in menu.lst according to the new name.

Remember that the advantage of "not booting from it's splash screen" is that you can edit menu.lst entry for changes as you like, so just for example, if you create a folder on some ext2/3/4 formatted partition named "Angel_Student" the menu.lst entry (porteus-boot) can be this:

Or use a savefile (e.g. Angel_Student.dat) if you'd like to keep the changes on the same FAT32 formatted USB stick and edit menu.lst according to that. (I didn't test actually if that works with ISO booting, btw)

When or While I was eXecuting the isobooter-mod & it was asking the Question about the Splash Screen, I Answered n as I'm Supposed to for Most Puppies or Puplets, But then it Returns isoinfo: Unable to find Joliet SVD, Twice after FATGamespup-216, g_pup-1.2, grub & lxde-pup411-k2.6.28.5-dillo-v01.1, All from 1 jpeg snapshot that I took w/ Me Mobile Ph Camera ( that once again I can't get 2 upload as an attachment 2 this website! ), Nun of these isos work!

So I'm Convinced that the Problem is Related 2 that isoinfo Message, But I don't Understand wot it Means or How 2 Fix it!

Of Course I've already Done a Search on the Forum, Used the Puppy Search Tool & Done a General i'Net Search, I Do Hope there's a Simple Solution 2 this isoinfo issue since it'll address @ Least 4 of the 9 remaining that aRen't working...

Joliet is an extension to ISO 9660, the specification for the file system (including file names) for the content on a compact disc (CD); it allows file names up to 64 characters in length (including spaces) and the use of Unicode characters in file names (sometimes needed for internationalization). Written by Microsoft, Joliet is fully supported in Windows 95 and later Windows operating systems (except Windows NT prior to its version 4). In operating systems (such as Windows 3.1) that support only eight-character file names, a longer file name on the CD is truncated into an eight-character name using a tilde (~) followed by a unique number as the last characters in the name.

That's the technical definition but probably doesn't help much for your problem.
Why some ISO's got this "Unable to find Joliet SVD" error, I don't know.
I tried with lxde-pup411-k2.6.28.5-dillo-v01.1.iso and got the same message and although I couldn't see anything wrong at the menu.lst entry that was created I got "file not found" error when trying to boot.
Then I ran again isobooter-mod and when question appeared "Do you want to boot ..... from its splash screen?" I typed y and lxde-pup411-k2.6.28.5-dillo-v01.1 booted fine.

The isoinfo command is used to "look" which files are inside the ISO, that way it can check if it's a 'Puppy' or a 'Dog' (simply said) The error "Unable to find Joliet SVD" means also: not being able to do the checking for files inside and "thinks": "this cannot be a 'Dog' so it must be a 'Puppy'" then, which seems right in most cases.

Not much I can help more, I'm afraid.

EDIT: BTW...

Earlier... Max wrote:

The Bulk of the isos Work 42 / 52 in Fact

I think that's not bad at all, the ISO's not working you can probably make work by choosing y for "Do you want to boot ..... from its splash screen?"

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum