Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 01 Oct 2014, 18:52
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Fatdog64-620 Final (17 April 2013) and 621 (9 May 2013)
Moderators: Flash, JohnMurga
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 24 of 29 Posts_count   Goto page: Previous 1, 2, 3, ..., 22, 23, 24, 25, 26, 27, 28, 29 Next
Author Message
LateAdopter

Joined: 27 May 2011
Posts: 155
Location: Reading UK

PostPosted: Wed 24 Jul 2013, 05:55    Post_subject:  

Hello jamesbond

Quote:
- Default dpi is now set to 96, font size reduced from 12 to 10 to maintain similar appearance to previous versions


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.

Currently I use FD 620 and Pemasu's UPUP Precise 3.7.2 which are both on the old system. So I haven't had to work out how to do it yet.

Quote:
- Important multisession and usb-flash fix for certain scenarios where deleted files re-appear or saved files appears missing.


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.

Thank you for your work on Fatdog
Back to top
View user's profile Send_private_message 
Jim1911

Joined: 19 May 2008
Posts: 2457
Location: Texas, USA

PostPosted: Wed 24 Jul 2013, 10:49    Post_subject: Request for update to Bibletime 2.9.2  

Hi kirk and jamesbond,

The recent update of Bibletime 2.9.2 has fixed numerous bugs. Please consider an update package to Bibletime 2.9.2 for Fatdog.

Thanks,
Jim
Back to top
View user's profile Send_private_message 
gcmartin

Joined: 14 Oct 2005
Posts: 4296
Location: Earth

PostPosted: Wed 24 Jul 2013, 16:23    Post_subject:  

JamesBond wrote:
... Let me know if anyone is interested.
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 Engine or use DogPile
Back to top
View user's profile Send_private_message 
Ray MK


Joined: 05 Feb 2008
Posts: 765
Location: UK

PostPosted: Fri 26 Jul 2013, 03:43    Post_subject:  

Hi jamesbond

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
Back to top
View user's profile Send_private_message 
smokey01


Joined: 30 Dec 2006
Posts: 1821
Location: South Australia

PostPosted: Fri 26 Jul 2013, 04:35    Post_subject:  

Always interested in Fatdog and it's still my preferred OS. I have been testing many distro's lately and I keep returning to FD.

None of the rest are anywhere near as responsive.

Thanks Kirk and James.

_________________
Puppy Software <-> Distros <-> Puppy Linux Tips
Back to top
View user's profile Send_private_message Visit_website 
irishrm


Joined: 14 Mar 2009
Posts: 218

PostPosted: Fri 26 Jul 2013, 05:47    Post_subject:  

Looking forward to Fatdog_next.

irishrm.
Back to top
View user's profile Send_private_message 
Snail

Joined: 18 Oct 2009
Posts: 238

PostPosted: Fri 26 Jul 2013, 08:56    Post_subject: Problem Unmounting SD Card
Sub_title: Seems to be a bug. easily worked around.
 

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.

Environment: Lenovo T400 with Fatdog621 installed to Win7 partition, sda2. SanDisk SDHC 8GB C4 Card.
Back to top
View user's profile Send_private_message 
smokey01


Joined: 30 Dec 2006
Posts: 1821
Location: South Australia

PostPosted: Fri 26 Jul 2013, 17:45    Post_subject:  

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
Back to top
View user's profile Send_private_message Visit_website 
Snail

Joined: 18 Oct 2009
Posts: 238

PostPosted: Thu 01 Aug 2013, 14:46    Post_subject: Desktop drive icon behaviour
Sub_title: Drive Icons: One down another to go
 

Hi Smokey,

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.
Back to top
View user's profile Send_private_message 
chapchap70

Joined: 18 Nov 2010
Posts: 129
Location: The Island Of Long (NY, USA)

PostPosted: Thu 01 Aug 2013, 18:17    Post_subject:  

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.
Back to top
View user's profile Send_private_message 
Snail

Joined: 18 Oct 2009
Posts: 238

PostPosted: Thu 01 Aug 2013, 20:58    Post_subject: Desktop drive icon behaviour
Sub_title: No icon
 

As in Chapchap's case, there is no icon for this particular USB stick regardless of whether it is mounted or not.

As all of my flash drives are formatted FAT, FAT32 for the 8G SD, VFAT for the rest, it is not a filesystem type issue, as far as I can tell anyway.
Back to top
View user's profile Send_private_message 
Hans

Joined: 16 Mar 2006
Posts: 45
Location: The Netherlands

PostPosted: Sat 03 Aug 2013, 08:08    Post_subject:  

Yes Jamesbond and Kirk I am as always interested in a new fatdog!

And thanx again for all the hard work
Back to top
View user's profile Send_private_message 
DrDeaf

Joined: 30 Dec 2006
Posts: 50

PostPosted: Sun 04 Aug 2013, 22:27    Post_subject:  

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
-------------------


Maybe not the interest you wanted, but I am interested in XFS support.
Would that be possible?
Back to top
View user's profile Send_private_message 
don922

Joined: 19 Jan 2008
Posts: 380
Location: The land of 14" monitors

PostPosted: Tue 06 Aug 2013, 05:32    Post_subject: frugal installation problems  

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:
    fatdog.png
    fix-usb.sh
    initrd
    vmlinuz

In a frugal installation the menulist is as follows:
    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

Initrd is shown as initrd.gz in Puppy 528.005 & Puppy 529. Fatdog 621 calls it just 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?

_________________
Don -- Thailand

Back to top
View user's profile Send_private_message 
Marv


Joined: 04 May 2005
Posts: 340
Location: SW Wisconsin

PostPosted: Tue 06 Aug 2013, 10:53    Post_subject: Re: frugal installation problems  

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:
    fatdog.png
    fix-usb.sh
    initrd
    vmlinuz

In a frugal installation the menulist is as follows:
    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

Initrd is shown as initrd.gz in Puppy 528.005 & Puppy 529. Fatdog 621 calls it just 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?


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.
Code:
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

_________________
tweaked 412 based boxpup, well honed 'lina-lite-005, alphaOS 321 Wink , X-slacko 2.1, Lxpup 14.07, and not to forget trusty Carolina/Carolite (now with 3.15 kernel). All lean and steady pups.
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 24 of 29 Posts_count   Goto page: Previous 1, 2, 3, ..., 22, 23, 24, 25, 26, 27, 28, 29 Next
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1049s ][ Queries: 13 (0.0114s) ][ GZIP on ]