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.

If I mount a disk which has write protect set and delete some files using Rox filer, they disappear from the window and there is no error message, but the files have not been deleted.

I just have to make sure I know what state the disk is in before I do anything.

I don't need an update to Fatdog64 at the moment but I look forward to one with kernel 3.11 with Radeon power management. But only when it suits you.

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?

FATDOG is so fast now, this seemingly would be hard to measure, but, yet, worthwhile.

Interested._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engineor use DogPile

Very interested - although my understanding of the many new features and updates is limited, what I do know, is that Fatdog64 in its latest guise boots faster and runs much better than any other OS that’s been on the E732 laptop.

(A short while ago my grand daughter cracked the laptop screen, (huge fester) so I was using an older LCD monitor, which a few days ago just stopped working (mutter). Fortunately, I’ve acquired a slightly newer Asus moniter, so back using the E732/FD64 again).

So an improved FD64 is of much interest to me and I suspect many other happy users. Many thanks to you and kirk for all that you do - much appreciated. Best regards - Ray_________________Asus 701SD. 2gig ram. 8gb SSD. IBM A21m laptop. 192mb ram. PIII Coppermine proc. X60 T2400 1.8Ghz proc. 2gig ram. 80gb hdd. T41 Pentium M 1400Mhz. 512mb ram.Edited_time_total

I inserted an SD card, non-bootable, formatted FAT32 in my laptop and booted into Fatdog. Everything worked fine, until it came to un-mounting. Clicking the little green box to unmount failed to unmount the card. Instead a Rox window for the root of the card opened. This occurred several times. Selecting "Un-mount" from the right-click menu worked fine. I can't find any previous discussion of this.

Possibly because it was inserted before booting, the SD card icon (A very nice icon it is too), is located first. There is not enough space for the lengthy name, mmc etc etc, so it runs into and is possibly overwritten by the first HD name, sda1.

For noobish questions, is there a more appropriate part of the forum to post into? I don't want to clutter this one up.

Snail have you tried moving the drive icon to another location on the desktop then click on the green dot. I assume you clicked on the drive icon earlier to mount it._________________Puppy Software <-> Distros <-> Puppy Linux Tips

You are right. The problem of the green box on the SD card icon failing to unmount the card, opening a Rox window instead, only seems to occur when the icon is loaded in the left bottom corner of the desktop. It is placed there when the card (VFAT 8G) is inserted before bootup. It will also go there when it is reinserted after boot, since there is a gap for it to go into. In both cases unmount fails. So it's not the booting causing the problem. It also happens with a couple of 2G VFAT Cards. Otherwise, everything seems to work OK and the drive mounter can unmount them.

I notice that there is a "Safely remove" option for USB sticks in the drive mounter. Why is this needed? It is not there for SD cards.

A strange problem. One out of 5 USB sticks I inserted does not produce a desktop icon at all when inserted. It can be seen in /mnt and the drive mounter can see it and safely remove, mount and unmount it. It's behaviour is normal in Win7 (Slow as heck) and it also seems to work entirely normally in Fatdog, except for this one quirk! It's a 4G Lexar. The others are 2G and 0.5G. All are VFAT.

By the way, I think that the drive icons are a terrific user aid. Are they unique to Puppies? The only other distros I've used didn't have anything like them but that's about 4 years ago.

I recall an older USB (Sandisk) stick I was using to boot other puppies not having the icon displayed with Fatdog even after manually mounting with pmount. The Sandisk would not mount automatically. I could get to the files with a file manager after manually mounting the stick.

The format was vFat and when I changed it to Ext4, the icon appeared along with the others like normal after booting or inserting the stick afterward.

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:

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:

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?

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.