(old)Puppy Linux Discussion Forum

When trying to mount FD64-devx_700.sfs in FatDog 64 700 frugal install a message prompts me stating: 'Failed to mount cannot find branch directory'. I thought the file might be corrupted and did a hash check but the hash checked out fine. I also mounted other '.sfs' files fine.

Is there something changed with FatDog v700 that I'm missing??

If there's another alternative I'd like to know because I'm wanting to put VirtualBox on my system..

Thanx to all in advance for your sage advice.

Odd problem, do you have 6X size of all sfs used as RAM. Try upping total RAM, also may be permission problems, move sfs out of spot and into tmp to mount. If in the downloaded area permissions are not high enough to mount correctly.

I have no problem with memory(24gig on harddrive + 4gig of system memory-dedicated to Fatdog) and I even created a swap file. I tried to unsquash the file on a different 64bit system and the same message. 'Unable to mount cannot find branch'. Other misc squash files have worked fine. I even downloaded from 'Smokey's' link(thinking I might of had a corrupted file--though I doubt this scenario highly). As far as permissions I'm doing them as root and the permissions on the '.sfs' files are all the same upon download. ----And as you stated Ted, I did move the file away from spot's download directory and into the /tmp and used the 'Load SFS' option upon boot up. When using the load upon boot-up option It finds it and claims it cannot mount it as well. And I'm selecting the bootup option from the Fatdog control panel and using the default directory it's pointing to.

Do you think it might be the fact I didn't choose the 'Save session to a single file' option upon rebooting the frugal version of Fatdog64?? Because when installing Fatdog64 I chose the 'Save to directory' option when doing my first save rebooting (after installing frugal Fatdog64).

This is different from past puppy derivatives as they only allow saving to a single save file(when saving a session upon shutdown or reboot). Which is the norm. In that you can up the RAM of the personal storage file as needed(but it used to be limited to 1.8gig of personal storage). But in this version of Fatdog64 it prompted me with the ability to save my session as a directory. And upon the next reboot allocates the directory's entire partition as the personal storage file. Which in my case turn out to be 19gigs.

I appreciate your response. I'll double check again perhaps I did do something wrong.

This problem has been solved. Thanx Ted for your input.