Fatdog64-600 Final and 601 (July 2012)

A home for all kinds of Puppy related projects
Message
Author
capicoso
Posts: 172
Joined: Fri 13 Jan 2012, 23:38
Location: Argentina

#161 Post by capicoso »

Guys, how did you do the volume bar? I mean the green volume bar that appears when i use my multimedia keys for volume+/-/mute. There are some programs that i couldn't compile on Fatdog so i also use Precise Puppy, and i'd like to have that bar on precise. Thanks

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#162 Post by kirk »

capicoso,

That's Sven that does that. Sven is in the tray next to Wpa_gui.

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#163 Post by jamesbond »

Fatdog64 601 is released. Please see first post.
Full-install is still not supported but if you really need it please check http://murga-linux.com/puppy/viewtopic.php?t=79819.
It's hibernation time now 8)
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

Sage
Posts: 5536
Joined: Tue 04 Oct 2005, 08:34
Location: GB

#164 Post by Sage »

Nice one, jb, thanks.
But you can't slope off yet - get the matchsticks ready to watch Adam Scott whoop the world....

gnomic
Posts: 78
Joined: Sat 21 Aug 2010, 00:14

#165 Post by gnomic »

Fatdog64 600 firefox edition here. Running a Toshiba Satellite Pro S300 with Intel 5100 wifi. Alas it seems impossible to connect to a WPA2 access point. Appears the firmware is not being loaded. By the way is wpa_gui really up to the job? Have never found it of much use. Wicd by contrast usually seems to 'just work'. Likewise SNS etc.

Various other puppies and porteus 64bit editions can connect with this hardware. Haven't followed fatdog development blow by blow, is there a known problem here?

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#166 Post by smokey01 »

Jamesbond I have just discovered that cpio does not work well in FadDog64-600.

I have compiled a new one that can be downloaded here:

http://www.smokey01.com/software/utility/cpio2

You will need to make it executable and copy it to /bin

I discovered this when making graphical boot menus.

Cheers

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Fatdog64-600 Final and 601 (July 2012)

#167 Post by Billtoo »

I burned the fatdog64-601 iso to a dvd and then installed it to a 4 gb
flash drive.
It's working well.

I made a pet of Links web browser version 2.7, the newest at this time.
Attachments
links-2.7.jpg
(21.68 KiB) Downloaded 1191 times

Sage
Posts: 5536
Joined: Tue 04 Oct 2005, 08:34
Location: GB

#168 Post by Sage »

Sorry guys, but at least we kept it in the Commonwealth.

Jim1911
Posts: 2460
Joined: Mon 19 May 2008, 20:39
Location: Texas, USA

#169 Post by Jim1911 »

New frugal installation of Fatdog64-601. Using an existing save file, I first uninstalled the NVIDIA driver, then copied the save file to the new installation. It booted fine and the new NIVDIA driver works fine.

Everything appeared to be working fine so I did a remaster which seemed to remaster properly, however, it would not boot. The problem was that the remaster.iso did not contain the vmlinuz file. When I copied that over, the remaster appears to work fine. Also, note that the base sfs file is 600 rather than 601 in the initrd file.

Thanks for the 601 update.

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#170 Post by kirk »

I uploaded a pet package of Grub-legacy-.0.97 in case you have problems with Grub4dos. It's the same one that was in 521. It will work with ext2/ext3/ext4.

Running a Toshiba Satellite Pro S300 with Intel 5100 wifi. Alas it seems impossible to connect to a WPA2 access point. Appears the firmware is not being loaded.
I thought the 5100 firmware was in there, you can try downloading the current firmware snapshot from here:

http://git.kernel.org/?p=linux/kernel/g ... rmware.git

Wicd depends on python, not really an option.

WillM
Posts: 173
Joined: Wed 30 Dec 2009, 04:42
Location: Oakland, California

#171 Post by WillM »

This is a pet for lxterminal, with the dependency vte.
It has transparency, but if set to 0 it doesn't stick. About 5 is good.
Attachments
lxterminal_transparent.jpg
(27.71 KiB) Downloaded 1002 times

gcmartin

GRUB upgrade to FATDOG

#172 Post by gcmartin »

... I uploaded a pet package of Grub-legacy-.0.97 in case you have problems with Grub4dos. It's the same one that was in 521. It will work with ext2/ext3/ext4. ...
I saw this. Thanks. But, I want to ask a question for understanding...Is there some known problems with GRUB4DOS?

ALSO Thanks to you who have contributed to "FATDOG600 ... Seamonkey". Reasons are pretty much known in this area.

Here to help.

gcmartin

FATDOG600 - Repo missing items

#173 Post by gcmartin »

Thought you would want to know this.

I did review this download location for the FATDOG600 PETs. It seems that full SAMBA contributed by 01Micko has been removed from the REPO site ===> http://mirror.aarnet.edu.au/pub/fatdog/pets/600/
Could it be added back? Thanks in advance.

gcmartin

Booting FATDOG600 right from the ISO by a simple GRUB entry

#174 Post by gcmartin »

This was reported in an earlier post as a method to boot FATDOG (for test for example) without the need to create a Live media to boot FATDOG600.

Code: Select all

title fatdog64
kernel /memdisk iso
initrd /Fatdog64-600-firefox.iso
In review, would someone explain the following, please.
  • Where does the memdisk.iso come from?
  • What is the function of the memdisk.iso (is it the ISO the equivalent of FATDOG600's "vmlinuz")?
Thanks in advance for any explanation.

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#175 Post by smokey01 »

gcmartin Grub4Dos works fine in FatDog.

I have used it to create a number of USB flash drives, with graphical splash screens no less.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#176 Post by rcrsn51 »

Speaking of booting Fatdog directly from an ISO, could someone please try this with a Grub4Dos bootable flash drive?

Code: Select all

title Fatdog64-601 (Grub4Dos+ISO)
find --set-root /Fatdog64-601-Firefox.iso
map /Fatdog64-601-Firefox.iso (0xff)
map --hook
root (0xff)
kernel /vmlinuz
initrd /initrd
I don't have a machine whose BIOS will boot the big initrd from USB, but I think that this should work.

User avatar
escucha
Posts: 83
Joined: Sat 14 Mar 2009, 19:40
Location: Ainulindalë

Fatdog directly from an ISO

#177 Post by escucha »

to rcrsn51

Error 60: File for drive emulation must be in one contiguous disk area

This is ever the message, no matter if I put the ISO on root directory nor change hd(0,0) into hd(0,1).

but why load directly from iso?
simply put vmlinuz and initrd onto a directory and try this:

title Linux 'fatdog64-601-firefox' <-- the directory name at will
kernel /fatdog64-601-firefox/vmlinuz psubdir=fatdog64-601-firefox
initrd /fatdog64-601-firefox/initrd

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#178 Post by smokey01 »

rcrsn51 wrote:Speaking of booting Fatdog directly from an ISO, could someone please try this with a Grub4Dos bootable flash drive?

Code: Select all

title Fatdog64-601 (Grub4Dos+ISO)
find --set-root /Fatdog64-601-Firefox.iso
map /Fatdog64-601-Firefox.iso (0xff)
map --hook
root (0xff)
kernel /vmlinuz
initrd /initrd
I don't have a machine whose BIOS will boot the big initrd from USB, but I think that this should work.
This is what I got:

Code: Select all

Booting command list
(hd0,0)

map /Fatdog64-601-Seamonkey.iso

Error 60: File for drive emulation must be in one contiguous disk area

Press any key to continue...
I used the Fatdog64-601-Seamonkey.iso not the Firefox version.

I also placed the ISO in the root of the flash drive.

I would like to see this work.

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#179 Post by jamesbond »

smokey01 wrote:Jamesbond I have just discovered that cpio does not work well in FadDog64-600.
Thanks, cpio in Fatdog is busybox cpio, not the full cpio. Probably accidentally left out, because I saw kirk has one in his t2-packs collection.
Billtoo wrote:made a pet of Links web browser version 2.7, the newest at this time.
Thanks for this. I'll upload them to the repo later.
Jim1911 wrote:The problem was that the remaster.iso did not contain the vmlinuz file
Mmm :roll: ... need to test it again, the last time I tested it still worked.
WIllM wrote:This is a pet for lxterminal, with the dependency vte.
Thanks Will. I'll get this up to the repo as well. You know we have a package called x_misc_tools on the pet repo which (among others) contains "transset-df" to set true transparency, if xcompmgr is running?
gcmartin wrote:I did review this download location for the FATDOG600 PETs. It seems that full SAMBA contributed by 01Micko has been removed from the REPO site ===> http://mirror.aarnet.edu.au/pub/fatdog/pets/600/
False alarm. The file (samba-3.6.5-fdx86_64.pet) never went missing.
Where does the memdisk.iso come from?
From /usr/share/syslinux
What is the function of the memdisk.iso (is it the ISO the equivalent of FATDOG600's "vmlinuz")?
Yes.
Error 60: File for drive emulation must be in one contiguous disk area
According to http://diddy.boot-land.net/grub4dos/files/map.htm, you need to use contig or winconfig (both are Winblows programs) to make the file contiguous. I reckon you can get away without them if you format your flash drive and the copy the iso first. I'll give it a try myself shortly.

But --- if you have to format the flashdrive (and lose all data in the process), why don't we just "dd" the ISO straight to the flash drive? All Fatdog ISOs are hybrid isos, if one does "dd if=fatdog.iso of=/dev/your-flash-drive-device", the flashdrive would become bootable also.

EDIT: works. Posting from it now.
a) reformat the flash drive (mkdosfs /dev/flash-device)
b) mount the flash drive, then copy the iso
c) then "sync". wait until sync process is completed.
d) copy the grldr file to the flash drive (cp /usr/lib64/grub4dos/grldr /mnt/flash-device)
e) create the menu.lst file as described by rcrsn51.
f) lastly, run bootlace.com /dev/flash-device (this installs grub4dos boot-loader).
g) "sync", then unmount, then reboot.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#180 Post by rcrsn51 »

Error 60: File for drive emulation must be in one contiguous disk area
reformat the flash drive (mkdosfs /dev/flash-device)
Yes. The same thing happens occasionally when using Grub4Dos to boot *buntu ISOs off a flash drive.

I wonder if memdisk is less demanding. I believe that this is a fairly new feature in syslinux.

Post Reply