Hi.
Sorry for the late reply. I'm currently busy with other things, so I'm online just once a week - or at the weekend.
When you say boot directory, are you talking about the root of the flash drive? I think I fingured it out. I right clicked on an SFS I put there and choose the LP2 load which threw up a big warning. Backed out and tried the SFS load which gave the same warning. Went back to the first one some hours later and threw caution to the wind and selected the LP2 load. After install it gave me more warnings about possibly not installing all files.
Man! I sure wish there was a less stressful way to do this.
---> There is always a less stressful way to do things. Usually by knowing how do things work. And, really, it's really easy and smart to do this in LazY Puppy.
Ok.
Boot directory is: directory on HD or USB Flash, that contains the LazY Puppy files (like StArtLPx2_202.sfs, initrd.gz, vmlinuz and all the LP2_xxx.sfs files)
In sdb1 I see:
Folders:
dev
etc
initrd
lib
root
usr
var
Yes, and that's the clue!
Having these directories in sdb1 (I assume sdb1 is the USB flash drive or HD drive where LazY Puppy is installed), means to use the LazY Puppy by a full install. This is NOT RECOMMENDED and LazY Puppy is not designed for the use from CD (like every else other puppy) and/or by full install.
LazY Puppy running from CD is possible, but without the comfort of automated download and load of SFS files. So, running from CD is recommended only for first run and then installing either to HD drive or to USB flash drive ---> by the installers, presented at the desktop.
Note: CD drive has to be mounted first (just left click it)!
I do recommend to install to USB flash drive, because this gives option to use a personal storage file (save file) and to shutdown/reboot without to save the current session.
LazY Puppy is different to other puppies, but it is very smart if you do use it frugal installed onto USB flash drive.
The USB installer does everything as needed (formatting the USB flash drive, installing the files etc.pp).
So, if frugal installed -let's say installed to /mnt/sdb1/LazY- do copy all your SFS files you want to use with LazY Puppy into this directory. The LazY Puppy SFS files do download automatically into this directory and executed from there.
If new SFS file added (don't do this on the LazY Puppy SFS files - it's already done!), just do a right-click and choose 'Convert to LazY Puppy'. This will prepare the SFS file for the use with LazY Puppy SFS P.L.U.S.. If your action is needed, you'll be informed (don't fear anything, it's really easy!). If process is finished, do again a right-click onto the SFS file and choose 'Create RunScript' (or similar, not simple Version). A GUI appears offering some options (self explaining (hopefully)). At the beginning it could be useful to activate option to copy a RunScript to the SFS location.
Now the mean thing:
If you do use a personal storage file (if you want to, do create this at first reboot from installed (not CD) version), then every thing is done and you should be able to run the application from it s menu entry (if option activated).
If you don't use a save file, you should do a remaster with the LazY Remaster Suite (also really comfortable and easy to handle) to keep the new added RunScript permanently in your OS.
But beware, there might be SFS files that won't work.
If I want to add new SFS files to my OS, I usually do a test first, which means preparing the SFS for LazY Puppy SFS P.L.U.S., creating RunScript, trying to execute the application, unloading the SFS - for each SFS I want to add.
If all went fine, I do a reboot to have a fresh and clean OS (no save file is used then), creating the RunScripts once again and do immediately a new Remaster (usually without to use any other application except the RunScript Creator - but it doesn't really matter, when the used SFS is unloaded before remastering).
If I can get the Android SDK and APK-Multi-Multi-Tool, and eclipse working then I'm headed in the right directions. These will at least let me Port ROM's from any phone with the same DPI as mine, and work on applications.
After having no succes with APK-Multi-Multi-Tool, I did not try the Android SDK. It's of course needed to use a newer puppy for this project (particular or fully).
I really like LazYPuppy, especially now that I understand it's concept better. I will keep it and see what I can install.
Yes, I really like LazY Puppy too!
It's my daily OS and I do own several derivatives of LazY Puppy (for example a 300 MB Audiostudio Version with all the audio applications installed). It works very well on all computers I do own or I'm able to use. In fact: I don't want to miss the comfort of LazY Puppy anymore but I'm afraid of the day it could never be used because of owning computers with newer hardware.
To be able to have a good and quite sleep at night, I did create the V.S.P.-LazY-Puppy Builder which lets me build a new LazY Puppy from every Puppy OS I want to within less than a single hour by entering 95 % of LazY Puppy's comfort into the new OS!
So: I'm prepared as well!