You shouldn't have to do anything. Try booting with the savefile=none boot option. That will boot without using your save file. You should automatically connect. That's assuming that eth0 is plugged in before booting.

You shouldn't have to do anything. Try booting with the savefile=none boot option. That will boot without using your save file. You should automatically connect. That's assuming that eth0 is plugged in before booting.

That's weird. The dhcpcd call is in /etc/init.d/50-Wpagui. If you also have a wireless card, that could be a problem, if a open wireless network is found it will associate and try to get a address. That could cause problems. When you launch the network wizard, un-check the box "Run WPA_Gui at startup." if you have wireless. Could also be that your network card is slow coming to a ready state for some reason. Then you would need a delay before dhcpcd is run.

I have tried to install 601 on a USB hard drive. The installation seems to work and the save file creation is correct at shut down but on the next boot up the save file contents are not available and some functions report fatdog64 is 'not installed.'

The drive icon does not have the 'mounted' indicator present

If I manually mount the drive and use the control panel 'save file test' option the file content is reported as correct.

Any suggestions ?

Is there any way to save to the drive (like 521) rather than a frugal save file ?

Fatdog64-600 boots completely different from 521 or other puppies. Only savefiles named fd64save and located in the root of a partition are automatically loaded. Take a look at the FAQs/Boot Options. Here's some examples from that page:

savefile=direct:device:sda1 --- use savefile named fd64save.ext4 located in root directory of /dev/sda1, save directly to it
savefile=ram:device:sda2:/fd600/fd64save.3fs --- use savefile named fd64save.3fs located in /fd600 directory of /dev/sda2, use RAM layer
savefile=ram:usb --- use savefile named fd64save.ext4 located in root directory of the first found usb device, use RAM layer
savefile=direct:multi --- use multisession on device /dev/sr0

Posted: Sat 01 Sep 2012, 20:36 Post subject:
Fatdog64 Live DVD ModeSubject description: how to do it, and why it is not enough

Please excuse me in advance, I have just spent 2 days working on Fatdog64 with only limited success and am tired.

I have run various forms of Puppy all day every day for several years. I do this from DVD's on systems with no hard drive. I have ample reasons for using DVD's, but this is neither the time nor the place for that war.

Using the "Live DVD" mode in Fatdog64 is not like other Puppies. The working incantation was not obvious to me.

Instead, it is mainly from a comment in the Fatdog64-600rc topic by jamesbond on Tue 03 Jul 2012, 00:30

The trick seems to be to use the boot command: "fatdog64 savefile=direct:multi"

Unfortunately, that does not produce a Save icon.

That issue is addressed by jamesbond here at Fri 06 Jul 2012, 06:21

Quote:

You need to use the RAM-layer in order to enable manual save button. Use "savefile=ram:blahblahblah" instead of "savefile=direct:blahblahblah" to enable the RAM layer.

Unfortunately, that does not solve my problem.

To see that, we need to go back to the equipment:

DVD storage simply is not as reliable as hard drive storage. The main reason for that is that hard drives store small "sectors," which are easily read after writing, easily re-written, and even replaced without user involvement.

In contrast, DVD's store data in large streams on a single long helix on the DVD. If a dust speck causes a write error, we cannot know about it until we first write then read that whole "session." We can write the data again, of course, but the drive cannot do that itself, because it cannot store enough data in writer RAM.

To use optical storage reliably, something (at this point, the user) needs to verify that the write has occurred and can be recognized. Verification is necessary after every DVD write. Failure to verify writes risks all the data the user is trying to store, and sometimes, ALL of the data on that disc. On other Puppies, I can and do use the Save button, then mount the DVD and look for the saved directory. If it is not there, I can save it again. Worst case, I can scrounge up a flash drive and save the data, but this all depends upon the system staying alive for as long as it takes.

Unfortunately, we cannot do that with a Save button which queues for some unknown future action. I guess that would be shutdown, but I DO NOT SHUT DOWN! I just turn the power off. It is a glorious thing to be able to turn off the computer and walk out of the room without delay. DVD storage gives us that, provided there is no hard drive in the box. I love it!

Other DVD issues include properly checking each operation for failure, and then STAYING UP, issuing notice to the user, allowing repeats and alternate actions, and only giving up after the user specifically allows it.

When I was actually using Fatdog64, I loved it: it seems clean and responsive. I find the big initrd load irritating, but I love the video. I assume that since I do not have to set it up, I can take that same DVD and use it on different machines having different video systems, something most Puppies cannot do. When everybody gets their own secure virtual machine on a DVD, and can take it wherever, that is a big deal.

I found something wrong in the surround sound 5.1 channels on a working entertainment system which has correct sound on other Puppies. I have a Disney WOW calibration disc which jumps from channel to channel to identify which is which. Normally, each channel would be the same loudness, but here the center channel is much louder and also comes out both front sides. My guess is that the issue is the sound mixer, since that seems more likely than VLC, but who knows?

Fatdog64 has a noticeably better display on my systems than other Puppies, even though they use special drivers for my AMD video. We may never be able to stream HD Netflix or Amazon Prime on Linux, but we can hope for DVD's to look good, perhaps better than most players.

I recently tried to use Osmo in Fatdog64 and it didn't work properly. To be more specific the Task part didn't. When I created a task in the future it looked fine until the next time I started Fatdog and Osmo. I then noticed the task had been ticked as completed. This is not much use as it will never raise an alarm.

Because of this I went looking for a later version and I found two. The current version in Fatdog is 0.2.6. I found source code for 0.2.8 and 0.2.10 so I have compiled 0.2.10 and attached it as a pet. It now works as it should. Well I haven't noticed any problems so far.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum