DSL Embedded :: Save MyDSL installation

Quote

When closing DSL I get the warning that there are unsaved extensions and automatically the amsn files are showed as well as /mnt/hdb in the emelfm windows. The only thing to do to get pass the "unsaved extensions" warning is to move the amsn-files to /mnt/hdb, but I can understand this is not correct as they are no longer available after reboot. I can see that the prompt signals restore of backup files from hdb but I don't see any list.

Sounds like you don't have mydsl=hdb in the append section of the dsl-windows.bat file.

OK. I use the dsl-linux.sh, but think it's the same. I have changed:
-append "qemu frugal quiet modules=hdb mydsl=hdb". What stands before "mydsl" is as it came with the embedded.zip.

I start MyDSL, download amsn-package and save it to /home/dsl/optional, which also is in .filetool.lst. I turn off and get the warning that there are unsaved extenstions and the emelfm window comes up. I have tried
a) not to do anything i.e. to answer "no" to the question or
b) copy the newly added files in optional to /mnt/hdb
c) move the files to /mnt/hdb

The result is always:

After reboot the amsn-packages are in /home/dsl/optional (so I gather the backup worked in a way) but no icons on desktop and no "MyDSL" menu when rightclicking.

I don't want to give up on this, however clumsy I may be. With this solved I think even my most reluctant windowsfriends will be conquered.

@Roberts,

I have booted the 2.2b.iso (not tthe standard embedded) in Qemu, given the 'mydsl=hdb' from the boot command line and, et voila, Opera has been magically backed up and mounted on the fly. It even auto-configured the proxy server, cool!.
So, the problem was either with wrong append option in the standard dsl-embedded or the fact that I was using 2.0 embedded.

By the way, in my own experience, I notice that DSL embedded runs better with the -cdrom option than the -initrd option...

1. You will never get agreement on whether to use -iso or -kernel options for qemu. The -kernel option was chosen because the virtual machine can have a premade backup and thus eliminate many of the usual setup questions. Personally I don't care, the -iso is much easier for me to maintain.
2. If you boot from linux and wish to use the virtual harddisk it is called harddisk and not hdb because your linux system may already have a real hdb!
3. Mixing and matching, results in a totally confusing situation not only for those who try to offer support but also for others trying to learn the standard way of which things are presented.
4. While asking for support it is always best to fully disclose. My answer was for the typical running DSL insdide windows. I still would not be inclined to run Linux inside of Linux and tyring to use the virtual drive. But I can see the desire to access the virtual drive while booting from DSL natively and that requires the qemu boot option.
5. I don't know how many times, I have said not to store extensions in your home directory, because they are large and static. Yet, still I see this.

Bottom Line:

If you are running DSL embedded NATIVELY from a USB drive, then you need to edit your E:\syslinux.cfg file and add "mydsl=harddisk" to the APPEND statements, or maybe just type

dsl frugal mydsl=harddisk

at the prompt if you prefer to type it in manually every time. I don't remember if the "qemu" cheatcode is required or if it is already provided by default.

However, when running DSL in "Embedded" mode, either from dsl-linux.sh or DSL-Windows.bat, you need to add

mydsl=hdb

to the append statement where the other cheatcodes are listed.

Next Page...
original here.