This thread describes how to install a complete Operating System (FatDog), nVidia drivers and GPUGRID on to a 1GB or larger USB memory stick. The procedure is much easier than you might think.

Advantages:

Saves the cost of a hard drive.
Saves the cost of an operating system.
Saves the energy to run a hard drive.
Allows you to try Linux/Puppy/FatDog with no hard drive commitment what so ever.
It is fast, easy and fun.

FatDog64 is a complete 64 bit operating system that is under 200MB. Being so small it can run completely in RAM which makes it very fast. Best of all it is completely free.

Why not give it a go? No commitment is required. Nothing needs to be installed to your hard drive, in fact once you make a bootable disk you could unplug your hard drive and the system would still run just perfect.

FatDog64 running BOINC/GPUGRID: http://yfrog.com/7gfatdog64boinchardinfop



Summery of the process:

Download and burn the FatDog64 ISO to a CD or DVD.
Boot from the optical disk, install the OS to a stick and save your settings.
Download nVidia drivers.
Set up the drivers first, reboot, and then download and run BOINC.




Steps in more detail:

Note: An nVidia GPU is required to run GPUGRID. 1GB of RAM or more should be available as well.

1) Download the FatDog64-511 iso from: http://distro.ibiblio.org/pub/linux/distributions/fatdog/iso/

2) Burn iso file to a CD or DVD (as an iso disk image, not as data)*

3) If your computer is not set to boot from CD/DVD select "boot from CD/DVD" in BIOS or boot menu (at f2 or f12 typically).

4) Boot from the FatDog64 CD/DVD (you can unplug your hard drive if you are worried about it, FatDog64 will not be needing it)

Note: FatDog64 should come to a GUI screen automatically. If you are left at a command prompt with no GUI see **

5) Go to the "setup" menu , select "Puppy universal installer"

6) Select "USB Flash drive" and hit "OK"

7) Follow the instructions. Note GParted is similar to "Partition Magic". Make sure the bootable flag is set with Gparted.

8) Shutdown the system (all the way down this time).

9) You will be asked if you want to create a permanent storage. Answer yes.

10) Remove the CD/DVD, reboot(make sure your bios/boot menu is set to boot from USB). Your USB stick will now remember settings between restarts. Redo steps 4a- if necessary.

11) Set up networking by left clicking "Net-Wizard" and follow the directions.

12) Open an internet browser by left clicking "Firefox".

13) At the default home page single left click "click here for pet packages". Single left click the folder "500".

or follow this link: http://distro.ibiblio.org/pub/linux/distributions/fatdog/pets/500/


UPDATE

A new pet package is available with the new nVidia 260 series driver.

14) Download the nvidia driver pet by right clicking on "nvidia-260.19.21-for-510-only.pet" and then left clicking on "Save Link As" and then clicking on "Save". Pay attention to where it puts the file (defaults to "Downloads").***

NOTE: "for-510-only" means version 510 or newer (works fine with 511).


15) On your local computer go to "nvidia-260.19.21-for-510-only.pet" which should most likely in the "Downloads" folder on the desktop and left click it. It will install automatically.

16)You might actually need to restart the entire computer rather than just the X-server GUI. Older versions (RC3) worked by just restarting the X-server but I don't think this works any longer.

NOTE: The nVidia driver must be installed and working before you go any farther, this might require you to install to a USB stick or HD before proceeding.

17) Use Firefox to download BOINC for 64 bit Linux from the BOINC download site. The BOINC site should auto detect the correct version automatically. Pay attention to where it puts the file.
http://boinc.berkeley.edu/download.php


18) Right click on the BOINC file, go to properties and make the file executable by putting check marks in the "exec" boxes (left click in the box to make a check mark).

19) Left click on the .sh file, BOINC installs itself.

NOTE: Fatdog makes all downloaded files the property of the user, rather than the ROOT account. Errors may occur if a program owned by a regular user tries to modify a file belonging to ROOT. If this is an issue running BOINC from the downloads folder do the following:

19a) Move the BOINC folder from downloads to another folder, like "my-applications"

19b) Change the ownership of the folder my-applications and all sub folders and files using the console command "chown -R root:root /root/my-applications". The -R is for "recursive".

20) In the same folder you found the original install file there should now be a new folder named BOINC. Open the folder by left clicking and left click on "boincmgr".

That is it. The rest should be familiar to BOINC users (set up BOINC preferences and attach to GPUGRID).


*
If you don't have an ISO burner check out:

http://www.imgburn.com/ or

http://www.ntfs.com/iso-burning.htm

**
(Thank you Toni)
4a. You will be left at the console. Enter the command "mp"
4b. An editor appears. Type ctrl-o and, when requested a file, enter /etc/X11/xorg.conf (respect capitals)
4c. In the "Device" section, add the following line
Driver "vesa"
4d. Save and exit (ctrl-q)
4e. Type "startx".
4f. This should put you on a low-res GUI from which you can resume with the following steps. After you install the proprietary nvidia drivers, the resolution will be fine.

***
These files may change names as they are updated. If you can't find the exact file look for a similar file name.

EDIT: Changed "CD" to "CD or DVD". FatDog is less than 200MB so it can easily fit on a CD but a blank DVD will also work just fine.

Hi bigtuna,

maybe you should team up with Dotsch, he seems to do the same with his
Dotsch/UK distri.

Michael

---

Team Linux Users Everywhere

I saw Dotch a few weeks ago and though it looked interesting but never got around to checking it out.

Puppy Linux has been a favorite of mine for years now so it was natural to attempt to get Puppy working with BOINC/GPUGRID.

When my good friend BikerMatt sent me a 6 core CPU I built a system around the 1055T right away. I didn't have an empty spare hard drive laying around so I tried the normal 32 bit version of Puppy Linux which requires no hard drive. 32 bit Puppy worked for BOINC and Rosetta but it had several limitations:

1) The 32 bit version could not see all the system memory.
2) The 32 bit version was evidently compiled to use a max of 4 cores and the 1055T has 6 cores.
3) The 32 bit version could not run GPUGRID.

After some searching I found FatDog64 and I was very excited because FatDog had the potential to overcome all of the 32 bit version's deficiencies. When I saw that the nVidia driver was available as an easy to install "PET" package I knew I had to give it a try. I was thrilled to discover that FatDog64 did not have any of the 32 bit version's deficiencies.

I'm about to check out Dotch. At this point I'm wondering why Dotch needs to be roughly 3 times the size of FatDog?

BTW I'm not responsible for FatDog, I'm just the guy who got FatDog working with GPUGRID (which is easy/nothing). Kirk is the genius who took Barry's already awesome Puppy software and got it working on a 64 bit kernel.

Evidently the nVidia driver in the "PET" is a bit dated. It works fine with my GT240 but not with Fermi cards. Looks like I'm missing step 4f:

(thanks to skgiven for pointing out the omission)

4f) This should put you on a low-res GUI from which you can resume with the following steps. After you install the proprietary nvidia drivers, the resolution will be fine.

At this point I don't actually know how to install newer drivers than are contained in the PET so I'll need some help with this one. I'm more of a Puppy Linux fan than a Puppy Linux expert.

PET packages have me spoiled since they install with one easy click...

Uhm.. we can't edit it, either :( How strange!

Can we start a new thread with all the updated info/corrections and erase the old one?

I took the liberty to edit your post, but please PM me at your convenience so we can try to debug the unable-to-edit condition. I prefer not to start a new thread so the links pointing here will stay valid.

Update:

"PuppyPC" is now a completely different computer. The old system was an AMD 4000+ with a single GT240. The new system is diskless and is running an AMD Athlon(tm) II X2 250 (3.0GHz dual core) CPU and twin XFX GT240 video cards (thanks to BikerMatt for some of the hardware).

FatDog64 had no trouble at all with the dual video card setup.

One thing did give me a bit of a headache, the AZIO AWU354 wireless USB network adapter is evidently not directly supported. The AZIO AWU354's chipset is the Ralink RT2070. After a few failed attempts to get it working I gave up and installed a wireless PCI card and all is well.

Not sure why but it really gives me a thrill to see the system running so well with no hard drive...

Hi bigtuna,

I've been curious, but also hesitant. My PC's are very picky, after very many failed WU's while experimenting with Mint 8 Gnome/Kde, Ubuntu 10.04 Gnome/Kde/Xfce, Mint 9. I went back to Mint 8 Gnome & Kde.

Since Fatdog is still rc3, I didn't dare. Would there be any point in starting with Puppy 5, & follow the steps for Puppy 4 upgrade to Fatdog: http://www.murga-linux.com/puppy/viewtopic.php?t=28068

Only problem is, I don't know if there is a fatdog-5.sfs needed to upgrade. Would doing this, if possible, be more bloated, but stable?

---

We mirrored the ISO here http://www.gpugrid.net/pub/Fatdog64-500.iso

Hi bigtuna,

I've been curious, but also hesitant. My PC's are very picky, after very many failed WU's while experimenting with Mint 8 Gnome/Kde, Ubuntu 10.04 Gnome/Kde/Xfce, Mint 9. I went back to Mint 8 Gnome & Kde.

Since Fatdog is still rc3, I didn't dare. Would there be any point in starting with Puppy 5, & follow the steps for Puppy 4 upgrade to Fatdog: http://www.murga-linux.com/puppy/viewtopic.php?t=28068

Only problem is, I don't know if there is a fatdog-5.sfs needed to upgrade. Would doing this, if possible, be more bloated, but stable?

I assume you are thinking of upgrading with the idea of running GPUGRID? And that you need a 64-bit OS? I believe that the original versions of FatDog were 32-bit. The name FatDog by itself only indicates the addition of some larger popular applications that are common in full size distros but absent in Puppy (because Puppy is designed to be small). I suspect that the thread you linked to is talking about 32-bit software...

What you need to run GPUGRID is 64 bit software which is where FatDog-64 comes in. When I talk about FatDog I'm generally referring to the 64 bit version but there are earlier non-64 bit versions of FatDog. Sorry for the confusion.

Since FatDog64 will run from the CD in RAM there is no hard drive commitment what-so-ever. I can download FD-64, burn it, boot it, set it up, and have it running GPUGRID in less than half an hour. If you are running Fermi it might take a bit more effort and certainly your first time might take a bit longer but it is really simple to just try it, just to get an idea of what is possible on such a small OS.

Hi Bigtuna,

does this mean that puppy/fatdog64 has a rival or a friend? http://distrowatch.com/?newsid=06185

They point out to their new 64-bit kernel available in distribution files area http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/release_candidates/distribution_files/ if I'm not mistaken.

---

Since Fatdog is still rc3, I didn't dare.

Updates:

Fatdog64-500 is now considered to be "final".

Announcement:

http://www.murga-linux.com/puppy/viewtopic.php?t=57389&sid=8f7699339436705fd70457da2cc2bf54

ISO:

http://distro.ibiblio.org/pub/linux/distributions/fatdog/iso/


Kirk was nice enough to update the nvidia driver "pet" so installing the 256 series driver only takes one click.

http://distro.ibiblio.org/pub/linux/distributions/fatdog/pets/500/

The OP has been edited to reflect the new version and the new driver pet.

I've not had a chance to test the final version or the new driver but I will in just a day or two.

Santa is bringing me a GTX 460 very soon so I'll be able to test FatDog with Fermi based cards...

Thanks bigtuna, I get the hint. I'll try within a week, I might want to get a USB flash drive first, just to be on the safe side. Things have been so nice & stable lately.

---

Hi Bigtuna,

I installed after getting a USB pendrive. It works & I was really looking forward, but as you can see here http://www.gpugrid.net/results.php?hostid=75696 it doesn't like my PC. Not this one at least http://www.gpugrid.net/show_host_detail.php?hostid=75696. Such a shame, it was supposedly 50-100% faster than Mint Linux8 64bit. It's not only GPUGRID it fails on, but also Rosetta@home, freehal@home, ibercivis, & WCG says it has no work for my unsupported i686 machine.

EDIT:

I will try to lower my slightly OC'ed RAM that's set to 1066Mhz from an original 900Mhz, down to 800Mhz & see if that helps.

It's way too soon to say, but the longest a GPUGRID WU survived before changing from 1066Mhz to 800Mhz was under 4 minutes, now I'm past 13 minutes. One single "suggestion" or "request" if I may, is a PET for nvclock & BOINC when there's time for that ;-)

rosetta@home failed after 30min so did GPUGRID, Freehal@home still ticks. Maybe it's just the heat & rosetta@home fails on other PC's too, but I can't figure out how to install nvclock :-(

---

For WCG (which only have x86 apps) you need to create a cc_config.xml file in the Boinc directory, open it as a text file and save it after adding the following lines,

<cc_config>
<options>
<alt_platform>i686-pc-linux-gnu</alt_platform>
</options>
</cc_config>

For WCG (which only have x86 apps) you need to create a cc_config.xml file in the Boinc directory, open it as a text file and save it after adding the following lines,

<cc_config>
<options>
<alt_platform>i686-pc-linux-gnu</alt_platform>
</options>
</cc_config>

I did this & got this message from WCG
Wed 14 Jul 2010 11:41:05 PM GMT+5 World Community Grid [error] App version has unsupported platform i686-pc-linux-gnu
Wed 14 Jul 2010 11:41:05 PM GMT+5 World Community Grid [error] No application found for task: i686-pc-linux-gnu 614 ; discarding

But downclocking the RAM did help a lot, & so did using Option "Coolbits" "4" I'd use "5" but my GPU is already OC'ed

---

I should have also said you need to exit Boinc and then open it up again (leave it a few seconds in between).
It's fine, you won't lose all the tasks - they are in RAM.

We had a power outage which killed my RAM only machine. Normally it only takes a few minutes to boot, load the driver, install Boinc and get up and running again.

I took the power outage as an opportunity to try out FatDog 64 final (I was running rc3) and the new 256 series drivers (I was running the older 195 series drivers)and I couldn't get it to work. Curiously reverting back to rc3 and the 195 series drivers did the trick and the computer started like normal??

Anyhow for some reason the newer stuff does not install the same way and when you restart x (after loading the driver) it never comes back, not even with the xorgwizard command.

Any help would be appreciated.

TIA

Im from CZech Rep...my comp is PDC (core2duoWith2MB_L2chace@3.45Ghz-stable) n fermi 456...but, your server dont send my any work...n my credit is still ZERO !!! I need torture my GForce....where iz my problem? cuda installed, boinc installed...how much can i do ?pls help me...thX haski@email.cz

---

Hi Senna,

try a higher (newer) version of BOINC 6.10.58 & newest NVIDIA WHQL DriverGeForce/ION Driver Release 256 I see you're downloading WU's but getting instant errors. Hope this helps

---