Fatdog64-600 Final and 601 (July 2012)
Fatdog64-600 Final and 601 (July 2012)
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.
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
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.
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.
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.
http://git.kernel.org/?p=linux/kernel/g ... rmware.git
Wicd depends on python, not really an option.
I thought the 5100 firmware was in there, you can try downloading the current firmware snapshot from 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.
http://git.kernel.org/?p=linux/kernel/g ... rmware.git
Wicd depends on python, not really an option.
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.
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
GRUB upgrade to FATDOG
I saw this. Thanks. But, I want to ask a question for understanding...Is there some known problems with GRUB4DOS?... 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. ...
ALSO Thanks to you who have contributed to "FATDOG600 ... Seamonkey". Reasons are pretty much known in this area.
Here to help.
FATDOG600 - Repo missing items
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.
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.
Booting FATDOG600 right from the ISO by a simple GRUB entry
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.In review, would someone explain the following, please.
Code: Select all
title fatdog64
kernel /memdisk iso
initrd /Fatdog64-600-firefox.iso
- 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")?
Speaking of booting Fatdog directly from an ISO, could someone please try this with a Grub4Dos bootable flash drive?
I don't have a machine whose BIOS will boot the big initrd from USB, but I think that this should work.
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
Fatdog directly from an ISO
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
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
This is what I got:rcrsn51 wrote:Speaking of booting Fatdog directly from an ISO, could someone please try this with a Grub4Dos bootable flash drive?
I don't have a machine whose BIOS will boot the big initrd from USB, but I think that this should work.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
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 also placed the ISO in the root of the flash drive.
I would like to see this work.
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.smokey01 wrote:Jamesbond I have just discovered that cpio does not work well in FadDog64-600.
Thanks for this. I'll upload them to the repo later.Billtoo wrote:made a pet of Links web browser version 2.7, the newest at this time.
Mmm ... need to test it again, the last time I tested it still worked.Jim1911 wrote:The problem was that the remaster.iso did not contain the vmlinuz file
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?WIllM wrote:This is a pet for lxterminal, with the dependency vte.
False alarm. The file (samba-3.6.5-fdx86_64.pet) never went missing.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/
From /usr/share/syslinuxWhere does the memdisk.iso come from?
Yes.What is the function of the memdisk.iso (is it the ISO the equivalent of FATDOG600's "vmlinuz")?
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.Error 60: File for drive emulation must be in one contiguous disk area
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]
Error 60: File for drive emulation must be in one contiguous disk area
Yes. The same thing happens occasionally when using Grub4Dos to boot *buntu ISOs off a flash drive.reformat the flash drive (mkdosfs /dev/flash-device)
I wonder if memdisk is less demanding. I believe that this is a fairly new feature in syslinux.
wine-1.5.9-i486_v1.pet
Green_dome's latest wine-1.5.9-i486_v1.pet works fine without any modifications in using new frugal installation of Fatdog64-601.
- Attachments
-
- image-1.jpg
- (48.17 KiB) Downloaded 1247 times
Re: wine-1.5.9-i486_v1.pet
Jim do you have a link please.Jim1911 wrote:Green_dome's latest wine-1.5.9-i486_v1.pet works fine without any modifications in using new frugal installation of Fatdog64-601.
Re: wine-1.5.9-i486_v1.pet
Latest Winesmokey01 wrote:Jim do you have a link please.Jim1911 wrote:Green_dome's latest wine-1.5.9-i486_v1.pet works fine without any modifications in using new frugal installation of Fatdog64-601.