@BillToo, thanks. I was just looking at this site just before clicking into this BLUE thread where I find your post. XBMC would be an excellent native application for this distro it could be, OOTB.

What an idea._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engineor use DogPile

Blue V3 attempts to address two issues that emerged in testing by forum members. The first is that some sticks are in reality less than 8x1000x1000x1000 bytes. The second is that some BIOSs will not boot from a USB stick without using some trickery.

When I first issued Blue I failed to anticipate the first problem and although aware of the second, did not realise just how common that problem is.

The above observations have been added to the second (FAQ) post in this thread which now contains 9 items as opposed to the original 4._________________Regards ETP
Pups inmy kennels.

One success, one failure + question.
Success: blue pup runs from my SDD. Got a V3 blue pup working on 8GB USB key. Prepared f2fs partition on SSD. Copied files from USB key f2fs partition to SSD. Edited config file in USB key vfat partition to point to the SSD f2fs partition /dev/sda5.
Failure: I have an old HP usb 1.1 memory key, 30MB, and I thought I could use it instead of my other 8GB USB key to hold the vfat boot partition. So, formatted hp key vfat, cloned vfat partition from 8GB USB key to 30MB hp key using gnost option 6, http://www.murga-linux.com/puppy/viewtopic.php?t=54231, shut down, replaced 8GB key with 30MB key, reboot. I can see the progress indicator "vmlinuz....<ready>" but then my PC reboots followed by the progress indicator again in an endless loop.
Questions: Where did I go wrong? What should happen, technically, after the progress indicator says "<ready>"?

The problem, I think, is that the MBR does not contain the proper program to config file on the partition you formated on the USB1.1 stick. Changing the bootmanager to GRUB4DOS might help here.

I've never done the following with BLUE. But, its an idea.
While running your PUP

insert your USB1.1 stick.

blanks your stick

go to Menu>system>GRUB4DOS

Let GRUB4DOS setup stick

Try again.

You may have to set parms on the Blue entry in the config file to boot.
Here to help
Edited: to add problem thoughts_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engineor use DogPileLast edited by gcmartin on Tue 08 Apr 2014, 16:31; edited 1 time in total

The problem, I think, is that the MBR does not contain the proper program to config file on the partition you formated on the USB1.1 stick. Changing the bootmanager to GRUB4DOS might help here.

I'm not an expert, but I thought that the MBR is fine since the USB1.1 stick is going through a boot sequence and displaying "vlinuz.....<ready>" then the PC reboots. I used gnost to clone the source partition to the USB1.1 stick, gnost is a cloning script, I think it takes care of the MBR. But I could be wrong. Anyway, I used GRUB4DOS boot manager from puppy precise and set the USB1.1 menu.lst to boot from /dev/sda5 and also chainload linux on /dev/sda (in GRUB4DOS advanced menu). Neither option worked. Blank monitor with a blinking underline cursor. I might give up on this USB1.1 key and go back to using a full blue pup V3 stick to boot blue pup on my SSD - like I'm doing just now. It's a waste, but at least it works.

It sounds as though Gnost, which I have never used, was not up to the job. What you attempted was right in principle. To achieve your aim:

1. Return your 30MB key (The target boot device you wish to use.) to its virgin state as described below:

In Linux use Gparted to do that: (In Windows just format it.)

A. Start by clicking on “device” then select “Create Partition Table”

B. Create a single fat32 partition spanning the whole stick accepting all other defaults.
(Do not set any flags or change anything else)

2. Download the 16 Meg HDD/SSD boot image file (16MegBlueBoot.img) that I have now uploaded together with the Windows utility to flash that image on to the target boot device (win32diskimager-v0.7-binary.)

It is intended to be used when you have copied the files from the f2fs partition of a working 8GB stick over to a partition on a hard disc or SSD and prefer not to modify syslinux.cfg on that stick to boot from or want to use that stick elsewhere.

Hi ETP,
I got no success copying the sticks 2nd partition (using rox drag and drop the files from the stick 2nd partition).

ETP wrote:

Install to hard disc or SSD:

Having created a working Blue Pup install on a card or stick you have all the ingredients and simply need to copy over the complete contents of the 2nd partition on the card or stick to an empty f2fs partition that you “prepared earlier” on your disc. It should be at least 16GB in size to allow room for snapshots. (20GB is recommended)
N/BIf you elect to shrink an existing partition in order to create an f2fs partition it is strongly advised that you back up your whole hard disc before doing so.
To perform this copy you will have to have booted from an f2fs aware Pup such as QT, Precise 5.7.1 or Thin Slacko.

How can one
- copy the the sticks 2nd partition to a HDD partition ? (currently a logical partition, ext4 formatted - i noticed that Grub4dos cannot boot on f2fs partition ...it returns an error like "cannot find this partition")
- extract the bluepup-img.xz to that hdd partition?

Return your 30MB key (The target boot device you wish to use.) to its virgin state as described below:

In Linux use Gparted to do that: (In Windows just format it.)

I've had quite a few usb booting problems (not with Blue pup...) where I have used Gparted in the belief that it returns a stick to a pure, virgin state. However, it is now my belief that Gparted cannot be trusted to format a stick to an "ex Factory" condition - it leaves some mbr and filesystem structures intact, and if those structures have already been damaged, corrupted or badly configured then you can't count on Gparted to correct it. (I'm no expert on this so don't quote me...)

I just wanted to mention that in case some people find odd results after expecting that Gparted would 'virginise' the stick. There might be more thorough ways of getting a solid "ground zero" format including a perfectly configured mbr...

Hi Charlie,
Firstly UNDER NO circumstances should you attempt to target your HDD with the img.xz file. That could WIPE your hard drive.

Thanks !!!

Quote:

I am not clear from your post whether you are struggling to copy the files to your ext4 partition or whether you are struggling to boot having successfully copied the files.
Can you please clarify the problem?

Sorry being that unclear
the question is just to get the files copied to the ext4 partition.

Uuh...There might be some further boot question afterwards... If i've well understood, the BluePup stick is needed for booting (from the files into sdb1). BluePup is not aimed for starting from Grub, isn't...?

To copy the files from the second (f2fs) partition on the working stick that you have made, you must first boot from another Pup that is f2fs aware such as QT, Precise 5.7.1 or Thin Slacko.
Once you have booted that Pup, plug in your Blue stick and then open up two Rox filer windows.
The first window should be to the empty partition on the hard disc.
The second window should be to the f2fs partition on the stick.

Make sure that you display hidden files on the stick & then select everything.
Drag them across to the empty window and select copy. That process will take some time as there is about 1.6GB of directories and their contents to copy.

The syslinux.cfg on the Blue Pup stick then needs changing so that you can boot from that.

If the above is not working for you, please post any error messages._________________Regards ETP
Pups inmy kennels.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum