Maybe me but using the command
gunzip --stdout beaver64-8.7.1-8gb.img.gz | dd of=/dev/sdb bs=1M
does not work because the image I downloaded was xz not gz.
Is this a typo and should I just correct it? If I am confused I guess others might be as well.

The compressed .img file has been further compressed into a .gz file. Right click and 'extract here' to provide the compressed .img file. Suggest you ignore that 'dd-' stuff the gurus use and install USB Image Writer, which contrary to some commentary, IS available for Linux, is graphical and is (fool?)proof even for YT; it runs well out of Mint, MX and other majors, but would avoid Arch-based stuff like Manjy if you're not too confident.

I was using Fatdog to write the image to the USB and it obviously failed. I have used xz instead of gunzip in the command and that does something to the USB but does not write a good image and you need to reformat the USB afterwards. I will look at Image Writer and see if I can install it in a Puppy. Barry has a utility to make writing the USB easy but that also refers to gz nor xz.

Hopefully, Barry reads this post and corrects me or the instructions. Quirky is to good for potential users to be put off because of queries such as this.

I was using Fatdog to write the image to the USB and it obviously failed. I have used xz instead of gunzip in the command and that does something to the USB but does not write a good image and you need to reformat the USB afterwards. I will look at Image Writer and see if I can install it in a Puppy. Barry has a utility to make writing the USB easy but that also refers to gz nor xz.

Hopefully, Barry reads this post and corrects me or the instructions. Quirky is to good for potential users to be put off because of queries such as this.

peterw,
Yes, you are correct, I uploaded the usb flash stick image file with xz compression, it should have been gz compression, for compatibility with the instructions.

Actually, easydd can handle either, however, the various Windows image writer apps only understand zip or gz compression.

So, I have recompressed the file, now *.img.gz, it is uploading right now.

A much bigger file, 601MB, but have to pay that price for it to work with the Windows apps. Watching it upload...

I must be doing things wrong. In Fatdog easydd could not run on the xz image. I will try that again in xenialpup since Billtoo has had success?

I used the "gunzip --stdout beaver64-8.7.1-8gb.img.gz | dd of=/dev/sdb bs=1M" command on the new gz image and that wrote out the system in two partitions. However, it would not boot on two machines. The boot flag had been set. Tried grugdos boot loader and it recognised Quirky and install bootloader but that stopped with "kernel panic".

Still too much misunderstanding!
First: decompress/extract the required .img file with almost any other major Linux distro, i.e.most of them, just right click and "extract here" -exactly as I stated. I did NOT say to extract using Windows. Just follow what I said - you end up with the uncompressed .img file. Then, with almost any major[LINUX] distro, install the Linux version of USB Image Writer and use that to install your .img file to your USB stick. Do not use the Windows USB Writer utility, use the Linux one. For simplicity do not use one of the Puppy distros, which are excellent, but different to the majors in many respects, as they are 'compact' distros and written for folks a lot more competent with the coding, CLI & co. than the average user, including YT.

sharing your fondness for running Quirkies and Puppies totally in RAM, I'm astonished at your dd-phobia which I, of course, partially can understand, in view of the command's potential effects.

It's absolutely not my intention to give you unwelcome advice, but a simple workaround could provide you with the option to exactly follow Barry's instructions for preparing flash sticks.

If you boot a recent Quirky live-CD, on a 'HD-free' PC, you can download any .img-file and write it onto a flash stick using dd (easydd) without risking to play havoc since everything happens in RAM (and on the flash stick). As far as I can see from your posts, the required hardware ('HD-free' PC) is easily available to you.

Sage
Thanks for your help. I do understand your instructions and using them I have installed Quirky to a USB stick. It basically works on a Acer C720 Chromebook apart from (what I expected) the touchpad and its buttons - peculiarity of Chromebooks. Also, I have not got the sound working yet.

I need to experiment more with the Quirky recommended ways of installing. Perhaps, I will try dd'ing the decompressed image and not do it all in one.

I have a 2 year old HP laptop to which I can't install Quirky 8.7.1. It can see all the partitions on the disk, but on choosing a specific partition to install to, the installer keeps issuing an error message saying that the partitions are unreadable and to maybe try another one instead.

This Quirky 8.7.1 version installed to an older HP PC with no issues. Quirky Xerus 8.6 also installed with no problems to this laptop.

Is there perhaps a firmware package missing that is required so that the installer can see the disk partitions partitions on this specific HP laptop? It's a bog-standard HP cheapo that in the past has always ran Quirky/Puppy/ as well as many other distros with zero problems._________________Life is too short to spend it in front of a computer

I'm trying to install Beaver-8.7.1 onto my box. Yeah, it's the one with dual core and only 2 GB of ram.
I've tried the 'sync' in line 133 and 115 in /usr/local/install-quirky/install-quirky-to-frugal without luck.
The script will stop at ..writing inodes.. at 84% (there is less than 1.5 GB of compressed ram left).

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