Thankyou that will solve itchapchap70 wrote:If you edit your syslinux.conf file, you should not have to type anything to load your savefile.
it is slow for me toochapchap70 wrote: I don't know why ibiblio is so slow.
My monitor is 100 dpi and the first thing I do, when installing a puppy, is to set 96 dpi because I want the larger fonts. So I would need to change the font size back to 12.- Default dpi is now set to 96, font size reduced from 12 to 10 to maintain similar appearance to previous versions
Just for info:- I have a similar, but probably unrelated, issue with DVD-RAM with write protection set. The write protection is enforced by the optical drive and operating systems do not seem to understand.- Important multisession and usb-flash fix for certain scenarios where deleted files re-appear or saved files appears missing.
Your "Base2RAM=expand" seem of great interest to me. Does this feature work in Live media mode AND does it mean that the running system will not need to expand modules from the SFS in system operation? Further, will the Remaster run faster with this feature enabled?JamesBond wrote: ... Let me know if anyone is interested.
Maybe not the interest you wanted, but I am interested in XFS support.jamesbond wrote:This is what we have in the Fatdog-Next as of today. Still using the 600 as the base. I have this running for quite a while now. Let me know if anyone is interested.
Fatdog64-Next Release Notes
Changes from 621:
Updates:
-------------------
- Linux 3.9.4 with lxc support but without XFS support
-------------------
Here is what I have in my Grub4Dos menulist. The directory fatdog_621, along with my other pup directories, menulist, grldr, common opera and sfs directories are in a bootable fat32 partition on my sata sdd. The data/working directory is an ext partition on that sdd. 64 bit core 2 duo laptop. Works, don't know if it helps. The fatdog bootstuff is explained pretty well in the fatdog FAQs, linked on the first post here. It does less searching for boot files than most pups so more explicit locations rqd.don922 wrote:I downloaded the Fatdog64-621.iso and the MD5sum is correct.
Using ISOMaster iso file editor I have extracted the following files from the Fatdog64-621.iso and put them in a new directory /mnt/home/puppy-fatdog-621:In a frugal installation the menulist is as follows:
- fatdog.png
fix-usb.sh
initrd
vmlinuzInitrd is shown as initrd.gz in Puppy 528.005 & Puppy 529. Fatdog 621 calls it just initrd.
- title Puppy 528.005
rootnoverify (hd0,0)
kernel /puppy528.005/vmlinuz pmedia=satahd psubdir=puppy528.005 pfix=fsck nosmp
initrd /puppy528.005/initrd.gz
title Puppy 529
rootnoverify (hd0,0)
kernel /puppy529/vmlinuz pmedia=satahd psubdir=puppy529 pfix=fsck nosmp
initrd /puppy529/initrd.gz
title Fatdog 621
rootnoverify (hd0,0)
kernel /puppy-fatdog-621/vmlinuz pmedia=satahd psubdir=puppy-fatdog-621 pfix=fsck nosmp
initrd /puppy-fatdog-621/initrd
The directories for Puppy 528.005 & Puppy 529 were prepared the same as Fatdog 621 and work fine.
What is wrong with what I've done with Fatdog 621? Why doesn't it boot?
Code: Select all
title fatdog_621 set up for humongous initrd
find --set-root --ignore-floppies --ignore-cd /fatdog_621/initrd
kernel /fatdog_621/vmlinuz savefile=ram:device:sda1:/fatdog_621/fd64save.ext2
initrd /fatdog_621/initrd