Moderator: Forum moderators
Can't confirm your shutdown issue on my system.
-Fossapup64 9.5 host, Virtualbox 6.1
-boot from F96-CE_2.iso
-savefile created on .vdi virtual hard drive
-shutdown & restart execute with no errors
Thanks
wizard
Note:
Headings for these posts are not going to match subject of topic.
They were split from another topic to make this topic.
Big pile of OLD computers
Gave another try with the F96-CE_2.iso in a different VM
Booted and save fine as wizard indicated.
However, there are some minor issues with savefile/folder process
Although there several disks and partition and I'm booting from the ISO, it only offers to save in the first disk and partition it finds.
When I reboot from the ISO with the savefolder in the first disk and partition, never looks for it or finds it.
I tried to specify 'psave' typing 'c' at the boot screen, but it dropped me in the grub command line instead.
There you have to specify the entire grub boot command. I could not. I think that not many ordinary users can do this from memory.
Finally, although I'm booting from the ISO the boot menu says "boot from USB".
Maybe this is contributing to the specific save/discovery behavior. However, given the inability to easily add kernel commands and specify different 'pmedia' I can not evaluate the validity of this hypothesis.
I'm not sure how many of these changes are woof-CE changes or F96_CE-specific but I do not remember original fossapup acting like that. These apparent restrictions may offer other advantages but would be nice if at least the user can easily add boot parameters when booting the first time (or from the ISO), as the help menu suggests.
Thank you
Look closely at your grub menu, the first line at the top should read "BOOT FROM CD/DVD. If you don't choose that, Puppy will not find your save file/folder.
@rockedge
The grub sub-menu for CD/DVD supplies the pmedia=cd that is required.
wizard
Big pile of OLD computers
I tried to specify 'psave' typing 'c' at the boot screen, but it dropped me in the grub command line instead
That was correct. You press "e" to edit the boot parameters.
wizard
Big pile of OLD computers
wizard wrote: Sun Mar 05, 2023 3:10 pm@retiredt00
Look closely at your grub menu, the first line at the top should read "BOOT FROM CD/DVD. If you don't choose that, Puppy will not find your save file/folder.
The "BOOT FROM CD/DVD" is obviously present but does nothing
Did you try it? Did it work for you?
retiredt00 wrote:Although there several disks and partition and I'm booting from the ISO, it only offers to save in the first disk and partition it finds.
When I reboot from the ISO with the savefolder in the first disk and partition, never looks for it or finds it.
Booting from just the ISO could be controlled by what is allowing you to do that.
Did it actually provide a usable place for the save to be stored.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
The "BOOT FROM CD/DVD" is obviously present but does nothing
Did you try it? Did it work for you?
Yes
When I choose "BOOT FROM CD/DVD" this menu appears
Then when I press enter and boot it finds my save file on the .vdi ext3 virtual drive.
wizard
Big pile of OLD computers
wizard wrote: Sun Mar 05, 2023 5:11 pmWhen I choose "BOOT FROM CD/DVD" this menu appears
Then when I press enter and boot it finds my save file on the .vdi ext3 virtual drive.
another linux voodoo!
In my case 'enter' just moves it to the next entry (boot form USB)
I guess I should get the original fossapup and see if my hardware goes nuts or me
@retiredt00
Are you still just booting using the ISO.
If yes.
Are you using Ventoy, Yumi, or this method viewtopic.php?t=3680?
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
As mentioned earlier, I'm booting the ISO image in a virtual machine.
I did try fossapup9.5 in the same setting and everything works as expected.
vanilla dpup 10.X also works OK in these conditions, so it may be something F96-C_2-specific, at least as regarding the ISO boot menu.
@retiredt00 I am going to try to replicate what you are experiencing. Does F96-CE_1 boot as ISO (CD-ROM) on a virtual machine on your system?
rockedge wrote: Mon Mar 06, 2023 6:51 pm@retiredt00 I am going to try to replicate what you are experiencing. Does F96-CE_1 boot as ISO (CD-ROM) on a virtual machine on your system?
As far as I remeber was OK
Unfortunattely I do not have the ISO anymore and could not find it in your site either.
If you have it somewhere, I could take another look.
@retiredt00 I have uploaded both the F96-CE and F96-CE_1 ISO files to the site.
https://rockedge.org/kernels Look in the directory Old_F96-CE_versions
I am experimenting with F96 in various types of QEMU virtual machines.
rockedge wrote: Mon Mar 06, 2023 9:13 pm@retiredt00 I have uploaded both the F96-CE and F96-CE_1 ISO files to the site.
https://rockedge.org/kernels Look in the directoryOld_F96-CE_versions
Thank you.
CE and CE_1 worked fine. CE_2 not.
From what I can see CE_2 grub menu redirects to /boot/grub/cdmedia.cfg for the CD booting.
This does not appear to work at least in my case
There is also a new /boot/grub/cdmedia.lst file in CE-2
Finally /boot/isolinux/boot.cat and isolinux.bin appear different in the 2 versions
Not sure where these changes came from but is likely the problem in my case.