This is only intended at present for anyone who has had problems producing a bootable stick.
The target device remains as an 8GB or greater USB2 or USB3 stick. I have however tested it with both cards and sticks.

I will edit this post with a detailed write-up of those changes should it give a better booting success rate. Blue Pup itself only has minor non-critical changes. If you are happy with V1 or V2 there is no vital need to change but you could test on another stick.

2. Use a port rather than a USB hub if possible as there is an underlying problem with QT.

3. Linux install terminal commands for V3:
(The target stick should not be mounted. In the directory that you downloaded the .img.xz file to, right click then /window/terminal here/ to access the terminal)
Only issue the sync command when the first command has completed which may take up to 20 minutes. If you wish you can monitor it running in HTOP.

The assumption here is that there is only one hard drive in the PC and at boot time only one USB stick (V3) plugged in and no SD cards. If you have a second hard disc you will need to change the sdb2 reference to sdc2. If you have another USB device plugged in such as a wireless or BT dongle this may also apply.
In summary try the default sdb2 then move up to sdc2 then sdd2 until you boot successfully without seeing a kernel panic message.If you first attempt to boot the stick on the same pc or laptop that you used to create it, make sure that before doing so, you shut down the device and remove all mains power from it for a couple of minutes.
This will ensure that your BIOS refreshes its view of the stick and sees it as bootable.

Downloading now, and will try if this V3 works.
It is a 4 Gbyte image ? Right ?
Just from my earlier post: there is actually only 7.21Gbyte (x1024x1024x1024) = 7.74 Gbyte in FAT32 on the stick.
Kingston (and La Cie) must reserve 8/7.74 - 100% = 3% on the USB stick to replace bad sectors.

Will try this tomorrow... as per your description, running UPUP Raring with 3.992 kernel.

Yes. It will expand to just less than 4 GB but is intended to go on an 8GB stick.
This was a bit of lateral thinking to get around the fact that many 8GB sticks are “not the full shilling”. It should circumvent that particular problem where their actual capacity is less than 7.45GB._________________Regards ETP

Observation
In appearance, this V3 will find home on 4GB stick, as well.

FutureI will test the "touch" ability for you later and report for disability usage.

Hope this helps
Edited: Clarity and additional item

1st 8GB drive before V3_2014-03-26.png

Description

Drive picture before xz command use

Filesize

28.07 KB

Viewed

707 Time(s)

1st 8GB drive after V3_2014-03-26.png

Description

Immediately after xz completion of downloaded file

Filesize

25.81 KB

Viewed

700 Time(s)

_________________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 Enginesor use DogPileLast edited by gcmartin on Wed 26 Mar 2014, 13:50; edited 2 times in total

I pose a question to everyone who has followed the 8GB problem discussion in this thread. It is here. Respond if you have any info you feel would be helpful._________________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 Enginesor use DogPile

I tried the linux method with 2 more 8gb flash drives on my 8+ year
old hp desktop pc. installing the V2 image.
--------------------------------------------------------------------------
8gb SanDisk cruzer U3 smart (some windows stuff on the drive shows up
as a cd drive on the desktop)
Gparted showed 7.65gb

This drive took about 15 minutes to install Blue Pup using the linux
method.

Booted to the prompt where I ran xorgwizard and chose the modesetting
driver then xwin to get to the desktop.
--------------------------------------------------------------------------
8gb kingston DT101 G2
Gparted showed the drive as 7.27gb.
After about 50 minutes the error popped up.

This drive booted up to the prompt where I ran xorgwizard and chose the
modesetting driver and then xwin to get to the desktop.

Posting from it now.

Images 1-3 are the kingston flashdrive in Gparted, images 4-5 are the
Sandisk Cruzer.
--------------------------------------------------------------------------
The 8gb V2 image works on these flashdrives.

I, too, last week with BluePUP-V2 got similar messages on 8GB USB. But, unlike him, those Version 2 attempts would NOT boot; until I used a 16GB and 32GB USB sticks. For any user who witnesses this error message, I would advise that your system may be compromised as lacking something, someware.

Hope this is helpful_________________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 Enginesor use DogPile

Believe it or not that is not an error message but the normal message dd gives when it has finished and can do no more. It does not indicate success or failure. In Billtoo's case he went on to boot from the stick.

With Blue Pup V3 you are not likely to run out of space when targeting an 8GB stick with a 4GB image unless you encounter a fake stick._________________Regards ETP

I downloaded version 3 of Blue and went to install it from Slacko 5.5.
When I opened a terminal and typed the command to install it, something strange happened. I had a window open up and proceed to display the data from the xz files progress along with PDF creator wanting to save the PDF.
I had to force a shutdown on that.
Next, I fired up Puppy Precise 5.7.1 and after editing my install script, I then use3d Gparted to restore the flash drive to one fat32 partition in preparation.
After that, I ran the install script with HTop also running so I would know for sure when the process was complete.
And... I did the install to a 4gig Sandisk flash drive!
When I went to boot it, it showed up in my computers boot menu. Good.
It loaded vmlinux, but I got a message of no init being found.
The install was to sdd. But that changed to sdc for some reason.
As to the missing init, I then mounted the fat32 partition and checked out /boot/syslinux/syslinx.cfg with gleany.
What I saw there suprised me in that what I saw was "default /vmlinuz root=/dev/sdb2 rootwait rw".
And the sdb2 partition on my desktop is the windows 7 partition.
So I edited syslinux.cfg to point root to /dev/sdc2 which is the f3fs partition on the flash drive.
I saved the file and believe it or not, it still showed up in my computer's boot menu and I was able to boot all the way to the desktop!! And remember this was with a 4gig flash drive! And I had 9 megs unallocated at the end of the flash drive too. So the flash drive had enough room.
So you are on the right track other than I do not know why the wrong partition was specified in the syslinux.cfg file.
I still have to try the 4gig flash drive on my laptop to see if the flash drive is recognized as a bootable device and will boot.

Man, I had 2 machines once: a good strong lenovo core 2 duo, and one 1GHz p3.
My lenovo he's dead, like this now only the p3 I can use it.
You would not know it the blue pup to do in the form of a CD?
Because he would interest me very much...
But a p3 can not booting from an USB- stick.

... It does not indicate success or failure. In Billtoo's case he went on to boot from the stick ...

Thanks @ETP. I have been a user of utilities for years that use "dd" and had never encountered that message, except, on the one time when a disk dump's geometry did not match the target HDD's even though the size matched. After this, I always checked that issue before going to a new target drive of the same size.

I should mention that in all cases where I get bootable sticks, I do NOT get such messages. But, if this is a "normal" error message, it may not be the reason that V2 does not work with my 2 different manufacturer's USB where failures occurred..

I am glad, though, that the suggestion to reduce the target partition size addresses this boot problem shown by your providing V3 for our evaluation. Additionally, it "appears" that a 4GB stick should work. I don't have one, but the math suggest it should.

Hope this helps_________________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 Enginesor use DogPile

Man, I had 2 machines once: a good strong lenovo core 2 duo, and one 1GHz p3.
My lenovo he's dead, like this now only the p3 I can use it.
You would not know it the blue pup to do in the form of a CD?
Because he would interest me very much...
But a p3 can not booting from an USB- stick.

Strange it is not too well known that you can usb-boot -any pc- with PLOP.

I am glad, though, that the suggestion to reduce the target partition size addresses this boot problem shown by your providing V3 for our evaluation. Additionally, it "appears" that a 4GB stick should work. I don't have one, but the math suggest it should.

Hope this helps

One can indeed create a 4gig bootable stick with version three. Evidently, the change you, ETP, made to get the flash stick to appear as a USB hard drive to the computer worked.
The only thing I am concerned with as per my earlier post is that the /boot/syslinux/syslinux.cfg file is showing an explicit drive address assigned to root. I do not know if this is hardwired into the writing of the file though and if one boots it on a computer that has a number of hard drives and partitions how the right one is chosen for the assignment of root.

I just fired up windows 7 on my laptop,edited the syslinux.cfg file to correspond to the number of drives on it making the root assignment to the next logical drive in line. I then used the laptop's boot menu to select the flash drive as my boot drive and after setting up my wireless network card, I am now editing this post from Blue version 3 booted from a 4gig flash drive!
And to me, the really fun part would be to have a Windows 8 user seeing the cromium desktop with the tiles.
The main thing here is that I am reporting some success with the arrangement!

I am glad, though, that the suggestion to reduce the target partition size addresses this boot problem shown by your providing V3 for our evaluation. Additionally, it "appears" that a 4GB stick should work. I don't have one, but the math suggest it should.

Hope this helps

One can indeed create a 4gig bootable stick with version three. Evidently, the change you, ETP, made to get the flash stick to appear as a USB hard drive to the computer worked.
The only thing I am concerned with as per my earlier post is that the /boot/syslinux/syslinux.cfg file is showing an explicit drive address assigned to root. I do not know if this is hardwired into the writing of the file though and if one boots it on a computer that has a number of hard drives and partitions how the right one is chosen for the assignment of root.

Harddrives and USB devices are numerated at power up (repower) or by any script that makes that call. When you install puppy to a pc with 2 USB stick plugged in, these can be enumerated as sdb and sdc. If you install to sdc, and reboot with the other stick removed, after reboot it is sdb. This is the reason I sometimes manually edit the "menu.lst" file from Grub4DOS.

The enumeration of USB devices is on devices it "recognizes" as USB. The algorythm has a fixed order in which is scans the USB ports.

So... you can probably avoid the issue you brought up by:
- keeping the devices plugged during the whole process.
- attach the USB stick you image to the last USB port. Keeping the chain prior to it intact. In that case your USB device will either be there (when recognized) or won't be there (when not). But a reboot will not re-rder the devices.

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