Puppy Linux Discussion Forum

[nooby]

[rcrsn51]

[nooby]

thanks I got into this dreaded Error 60 the file need to be
contiguous and I have no wine so does not puppy has
some program or a trick that can make a file contiguous
on fat32 if one move it to and fro or something?

[rcrsn51]

@nooby: I tested ISObooter from here on a fresh NTFS-formatted flash drive and it worked with both Slacko and Xubuntu. So it should work on a hard drive, assuming that there are no issues with discontiguity..

If you want to look more at this, please post a message here.

[nooby]

Here is what I remember but I fail to get what Puppyluvr writes

http://www.murga-linux.com/puppy/viewtopic.php?p=510041#510041

[der-schutzhund]

Hello to all!
First a brief explanation of "the protection dog":
My hobby is working with dogs. I train dogs for security. Not for the police action but for sporting events!

What about the participation here shows this threat has raised an interesting question: How can be booted Puppyisos of different stores, formats?
Since my English is not really good, I must say that now I'm a little confused about the various solutions, approaches, and options Listing however. Maybe we can create a summary if everything works so far?
For me, it would be important that the iso can be booted even if it was pushed by a modified version! Since I work with have the Lazy sfs be found!

@nooby,

i tested it and it works sometimes!
Actually it is a nice solution but I could not understand why an iso worked sometimes and sometimes not if I copied it again in auto. Even though I previously all isos and put it back in did not copy all ran. It would be important for my application that I write about the same isos sometimes with a modified version! Meanwhile, I have resigned myself that it's probably not possible to boot puppyisos sure if they are overwritten several times with modified versions. Even if that would work would have started the so-Lazy-iso still find LP2_ .. sfs. That did not work even with a different approach since the start of the Isos a new virtual disk has been created in the budget were not the sfs.

regards

Wolfgang

[nooby]

Wolfgang,

seems they need the contiguous for to work and when one
load a new version the nit corrupt? That is why people suggest
ext2 or ext3 so it works better. I have gone over to the one that
rcrsn51 do based on the Scooby way to set it up
and if one format it each time one do a change then it seems to work

[der-schutzhund]

do you know if Windows programs in wine under ext2 work just as well as under FAT32 or NTFS?
Perhaps you should then not be limited to grub4dos but describe each combination is a safe solution?
It would be important, as I said, iso that can be overridden and sfs be found!
For example, the possible combinations (if it works):
- USB flash drive, Fat32, grub4dos
- USB flash drive, Fat32, Grub2
- USB flash drive, NTFS, grub4dos
- USB flash drive, NTFS, Grub2
- USB flash drive, ext2, grub4dos
- USB flash drive, ext2, Grub2

- HD, FAT32, grub4dos
- HD, FAT32, Grub2
- HD, NTFS, grub4dos
- HD, NTFS, Grub2
- HD, ext2, grub4dos
- HD ext2, Grub2

etc.

regards

Wolfgang

[nooby]

Hopefully rcrsn51 and others good at such can help you decide
which combinations works best. I am only a curious user
I know almost nothing sorry.

[JMX]

I have successfully used rcrsn51's excellent streamlined procedure to boot iso files on my Asus EEE SDHC card.

Here is how I have been able to boot directly to .iso files on my internal harddrive.

First, no changes were needed to my existing grub4dos installation. (I had previously installed grub4dos by creating a bootable DOS partition with its appropriate config.sys file). This way, nothing is ever written to the MBR.

I then created a folder on partition 2 of my harddrive (sda2) and named it "isos", and then I put all of the desired .iso files into that folder.

Then, for testing, (before running the isobooter script) I simply added this entry to my already existing menu.lst:

title wary-5.4.90 ISObooter
partnew (hd0,3) 0x00 (hd0,1)/isos/wary-5.4.90.iso
map --heads=0 --sectors-per-track=0 (hd0,1)/isos/wary-5.4.90.iso (0xff)
map --hook
root (0xff)
kernel /vmlinuz pmedia=ataflash pfix=fsck
initrd /initrd.gz

It worked. And the creation of the save file on the harddrive worked exactly as expected. By default, the save file goes at the root (or in a folder) on the partition of the device that grub4dos does its initial bootup (in my example, grub4dos is initially booted on sda2 which is (hd0,1)).

I then simply edit the path statements in the isobooter file (which in this example is located at the root of sda2) to create a new accessible file named isomenu.lst to harmonize with my overall mapping.

It is no longer necessary to extract any iso files!

If the bootup harddrive has no more that 3 primary partitions on it, and if the iso files are not fragmented, then the "partnew" feature of grub4dos can do its magic.

[cinclus_cinclus]

There are situations were the fourth of the four possible positions for primary partitions is already in use (e.g. after removing a primary partition) - though another one is free for being used by the partnew command .