Fatdog64-600 Final and 601 (July 2012)

[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

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

[Sage]

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

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

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]

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.

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

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]

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.

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

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

[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

[smokey01]

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]

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.

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.

The problem was that the remaster.iso did not contain the vmlinuz file

Mmm ... need to test it again, the last time I tested it still worked.

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?

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.

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

[Jim1911]

Green_dome's latest wine-1.5.9-i486_v1.pet works fine without any modifications in using new frugal installation of Fatdog64-601.

[rcrsn51]

[Edit] Go here for GTK-mpscan v1.1.

[smokey01]

Green_dome's latest wine-1.5.9-i486_v1.pet works fine without any modifications in using new frugal installation of Fatdog64-601.

Jim do you have a link please.

[Jim1911]

Green_dome's latest wine-1.5.9-i486_v1.pet works fine without any modifications in using new frugal installation of Fatdog64-601.

Jim do you have a link please.

Latest Wine

[smokey01]

Is there a Pet or SFS available for Skype 4.0.0.8?

Ta