I have been keeping up with the changes. AFAIK, F96_4-CE_radky6.iso from the link peebee last mentioned is the latest version. This being a development thread rather than that of a final release, the practice of having the current version available from the first post of the thread was not used. The '6' in the title of the ISO is, AFAIK, the only way to distinguish it from earlier publications, e.g. F96_4-CE_radky5.iso
It is not less stable than the 'original' just structured differently and containing changes in response to issues raised previously on this thread.
@ peebee, you mentioned that it has a ydrv but no adrv. That's probably a result of my recommendation to name of the 'included' 'additional' sfs to ydrv rather than adrv. That recommendation was made because of the 'stacking/priority' order and the way nicOS-Utility-Suite's Save2SFS module used to work. An adrv used to be copied into RAM last or, at any event, have 3rd highest priority in the 'merge-file-system' [only lower than changes currently in RAM not Saved, and changes Saved]. Amethyst's Save2SFS module used to be able to create or update an adrv.sfs without having it include the contents of the ydrv.sfs, but not vice-versa.. With the publisher issuing an adrv.sfs, the user either had to manually change its name to ydrv.sfs, or modify the adrv.sfs in order to have the user's preferences prevail.
@ Amethyst. Amethyst has since modified the Save2SFS module. But I'm confused by the change. TBA, I've been too busy to test the result of the change. When the Save2SFS module is called the following GUI appears:
- Save2SFS.png (24.78 KiB) Viewed 1646 times
As you can see it offers to Save either to a ydrv or an adrv and also to 'Exclude existing adrv and ydrv'. I read that to be 'BOTH' without an option of Exclude one but not the other. But I could be wrong: there might be subsequent GUI that enables a User to select to exclude one but not the other. I created and have a ydrv which includes settings, customizations, and all applications I know will never be changed or need to be updated. My adrv, on the other hand, contains applications I frequently will need to update, e.g. web-browsers. In updating adrv I want to exclude ydrv, but not adrv. Perhaps, amethyst could post to the Utilities thread how to do that.
Frankly, it doesn’t matter what, if any, ‘additional drive’ is included, nor how the Save2SFS module works. The only thing which is important is understanding the system and how to work with it.
I can't find MochiMoppel's post specifying the issues he raised. But, MikeWalsh, you may not want to spend time addressing them if they weren't continued into the F96_4-CE_radky6.iso. Unless someone knows otherwise, that ISO will be the base for future changes, fixes.
I do have an issue. But I’m not sure it only relates to F-96. It has to do with the interplay between F-96, its employment of Pulse-Audio and perhaps only MikeWalsh’s portable web-browsers. So I’ll post it to the User Section. After I do I’ll provide link on this thread.
The only thing specifically worth mentioning here is that the scripts relating to the Multi-soundcare-wizard, mscw and mscw2, will be found in F-96 at /usr/sbin. But if you attempt to invoke either you’ll receive a notice to the effect that sound is controlled by pulse-audio. Selecting ‘off’ from the Taskbar audio-config launcher has no effect. Pulse-Audio is dependent on alsa. All alsa’s components are present, as is retrovol. But as far as I can tell, there is no way to ‘turn pulse-audio off’: no way to use the components other than via pulse-audio. This wouldn’t be a problem except that pulse-audio’s tools for selecting the proper sound card do not appear to me to be either as efficient or effective as the Multiple-Sound-card-wizard. MSCW operates under the principal ‘set it once and it is the default for all Sound applications’ until reset.
