LateAdopter wrote:The ISO 9660 filenames are garbled in fd600a2 and fd600b1. They were OK in the fd520 and fd521 ISOs.
It's usually because the mastering software is set to enforce ISO 9660 level 1. It is better to set level 3 or turn the checking off completely. Then any software can read the filenames correctly without any extensions.
Yes, I used level 1 and only enabled Rockridge extension. I've changed the build scripts, remasters and shutdown to enable ISO level 3, Joliet and Rockridge to make it more "compatible".
Setting up the country specific settings, the first time, is more complicated because you have to use three separate tools to do it.
The first two ask you to restart X and you have to say no, and the third one doesn't ask you and you have to remember to do it!
I know what you refer by first two; I don't get the third one.
The reason they are separate is that depending on your circumstances, you only need to use one or both of them.
Billtoo wrote:Sound quit working, I think it was caused when I opened the terminal
and ran alsa mixer and set the levels, then used the alsactl store
command.
I never use alsactl before ... anyway the initscripts will store the current volume settings using alsactl as follows: "alsactl -f /etc/asound.state store" (you can see this in /etc/init.d/20-alsa
tronkel wrote:Another awesome FATDOG. Running very well on my hardware.
Thank you for the compliment
Is it on Distrowatch yet? If not, it ought to be.
I don't think kirk registered Fatdog to distrowatch ...
As an example, my .fonts.conf file for anti-aliased fonts did not work at all when saved to the normal Puppy root home folder. Only after creating a new user using the FATDOG Control Panel did this function OK.
Didn't it? I thought the .confs.conf if placed in /root should work for root (but not other users), vice versa if you put it under /home/fido then it should work for fido (but not for other users).
Is there an sfs file available yet for FATDOG 600b1 for 32-bit libs? Or can I use the 32-bit sfs libs file from the 500 series?
The new 32-bit libs is in progress, for the time being you can use the old one. Note the old 32-bit libs is based on the earliest Quirky so it is really ancient ... but it works
shinobar wrote:Grub4DosConfig 1.8 now supports Fatdog64.
Thank you shinobar, I'll get in for the next release
Note: Failed format floppy, tested on Fatdog64 alpha2 and beta1.
I only have one machine with floppy drive and I have not formatted a floppy for years ...
I'm not even sure whether the
drive is still working
Thank you for the report though, I think devtmpfs doesn't automatically create this "special" floppy device
nodes. The floppy formatter program needs to be upgraded to create them on the fly.
Billtoo wrote:t takes 30 seconds to get to the prompt if I boot the fatdog 521 dvd with
fatdog pfix=nox,ram
On the same pc it takes 4 minutes to get to the desktop if I boot the fatdog 600b1 dvd with fatdog savefile=direct:local
It's not a big problem but when you have to do reboots to install the proprietary Nvidia driver etc., it takes some time.
EDIT: I tried again and just hit enter to start the fatdog 600b1 dvd and it still took 4 minutes but it did load my savefile, guess I didn't need the fatdog savefile=direct:local part.
The equivalent of 521's "pfix=ram,nox" in 600 is "savefile=none pfix=nox".
As kirk said, the "direct:local" isn't needed - that is the default options, which means:
- direct = directly access the savefile (no RAM layer in between)
- local = search all local drives (harddisk, dvd, usb ...) for the savefile and use the first one found
I can guess where the slowness come from. It is probably because of the humongous initrd. 600 is optimised for operation from harddisk frugal install - humongous initrd is faster in this case. For dvd, the split-initrd (initrd + main sfs, the way standard puppy and 521 works) is probably faster. I've included support for split-initrd for flash drives, but I forgot about dvd, sorry
I'll see whether I can whack the remaster script to include support for split initrd too.