I am running antiX linux on my laptop.
I want to create a Puppy live USB thumb drive.
I tried doing this with unetbootin but it would not boot.
What linux application can I use to create a USB drive from the Puppy ISO?
thanks
How to burn Puppy to a USB drive using Antix? (Solved)
How to burn Puppy to a USB drive using Antix? (Solved)
Last edited by greyowl on Tue 08 Oct 2019, 01:18, edited 1 time in total.
Unetbootin can be unreliable.
RUFUs runs in Windows and is great for creating LIVE USB drives.
It is a good idea to make a Puppy LIVE CD in any case.
Boot that and you can make a Live USB or better still, install a Puppy on the USB. The OOTB Puppy installer apps work well, especially the newer bootflash installer which can easily be configured for both UEFI and Legacy BIOS situations. The UEFI installer is also effective.
RUFUs runs in Windows and is great for creating LIVE USB drives.
It is a good idea to make a Puppy LIVE CD in any case.
Boot that and you can make a Live USB or better still, install a Puppy on the USB. The OOTB Puppy installer apps work well, especially the newer bootflash installer which can easily be configured for both UEFI and Legacy BIOS situations. The UEFI installer is also effective.
What is the computer make and model?
What Puppy version are you trying to put on a USB flash drive?
Are you sure this USB flash drive will work to boot a OS installed on it?
What is the make and model?
Some USB flash drives will just not work!
They do not seem to say on USB flash drive packaging anything about being a boot-able device.
It has to do with the USB drives internal controller and if they built it to be able to be used as a boot-able device.
What Puppy version are you trying to put on a USB flash drive?
Are you sure this USB flash drive will work to boot a OS installed on it?
What is the make and model?
Some USB flash drives will just not work!
They do not seem to say on USB flash drive packaging anything about being a boot-able device.
It has to do with the USB drives internal controller and if they built it to be able to be used as a boot-able device.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
The Problem: Puppy Linux USB-Stick from some other Linux
Hi greyowl,
While Flash and Geek3579's advice is correct, many computers no longer have CD/DVD burning hardware.
While what bigpup wrote is true, I'm surprised that he didn't ask you to provide details about the exact wording of the config files Unetbootin wrote to the USB-stick. He usually does. Sometimes the problem with Unetbootin is merely that it mistakenly identifies the device as a CD rather than a USB-Stick. If so, editing the config file can solve the problem.
You have, however, inquired about a 'forgotten' issue. Most of the people trying to do a USB-Key install for the first time have Windows as their operating system. They now have available Puppy's own LICK application, http://murga-linux.com/puppy/viewtopic. ... 720#462720 rufus and others. And once you have a running Puppy, there are several applications and an "easy" manual way to install Puppy to a Stick. But, to create a bootable Puppy on USB-Stick from a different Linux distro we've more or less expected Unetbootin to do the job. And sometimes it doesn't.
Someone who knows what he/she is doing should create a ".deb" version of "Lick" or "Yapi", http://www.murga-linux.com/puppy/viewto ... 260#914260. Until that happens, when Unetbootin fails, the following post discusses what may be your only two "easy" options: https://www.tecmint.com/create-an-iso-f ... -in-linux/
I don't know whether Gnome Disks --the second option above-- is available in Antix. Be very careful with the first option -- using the dd command. Accidentally choose your hard-drive rather than your USB-Stick and you'll wipe Antix off of it, replacing it with Puppy.
I can think of one other way, and one possibility. The possibility is EasyDD, http://www.murga-linux.com/puppy/viewto ... 61#1031161, an application created by BarryK, and packaged as a portable by Mike Walsh. As a portable it should run under any Linux. But I'm not certain that it works with ISOs. I think it only works with IMG files. If it does work with ISOs it will help to take the 'guess-work'/remembering which device to 'burn-to' out of the DD command.
The other way is to install your operating systems disk manipulation and ISO mounting tools. With them installed you can manually install Puppy to a USB-Stick: format the stick, mount the ISO, copy Puppy's files from the mounted ISO to the Stick, write Grub2 to the Stick and edit Grub2's config file.
While Flash and Geek3579's advice is correct, many computers no longer have CD/DVD burning hardware.
While what bigpup wrote is true, I'm surprised that he didn't ask you to provide details about the exact wording of the config files Unetbootin wrote to the USB-stick. He usually does. Sometimes the problem with Unetbootin is merely that it mistakenly identifies the device as a CD rather than a USB-Stick. If so, editing the config file can solve the problem.
You have, however, inquired about a 'forgotten' issue. Most of the people trying to do a USB-Key install for the first time have Windows as their operating system. They now have available Puppy's own LICK application, http://murga-linux.com/puppy/viewtopic. ... 720#462720 rufus and others. And once you have a running Puppy, there are several applications and an "easy" manual way to install Puppy to a Stick. But, to create a bootable Puppy on USB-Stick from a different Linux distro we've more or less expected Unetbootin to do the job. And sometimes it doesn't.
Someone who knows what he/she is doing should create a ".deb" version of "Lick" or "Yapi", http://www.murga-linux.com/puppy/viewto ... 260#914260. Until that happens, when Unetbootin fails, the following post discusses what may be your only two "easy" options: https://www.tecmint.com/create-an-iso-f ... -in-linux/
I don't know whether Gnome Disks --the second option above-- is available in Antix. Be very careful with the first option -- using the dd command. Accidentally choose your hard-drive rather than your USB-Stick and you'll wipe Antix off of it, replacing it with Puppy.
I can think of one other way, and one possibility. The possibility is EasyDD, http://www.murga-linux.com/puppy/viewto ... 61#1031161, an application created by BarryK, and packaged as a portable by Mike Walsh. As a portable it should run under any Linux. But I'm not certain that it works with ISOs. I think it only works with IMG files. If it does work with ISOs it will help to take the 'guess-work'/remembering which device to 'burn-to' out of the DD command.
The other way is to install your operating systems disk manipulation and ISO mounting tools. With them installed you can manually install Puppy to a USB-Stick: format the stick, mount the ISO, copy Puppy's files from the mounted ISO to the Stick, write Grub2 to the Stick and edit Grub2's config file.
I discovered that antiX Linux has a utility that can create a Live Puppy USB flash drive from the Puppy ISO. The only problem is that the USB flash drive will be "read only"
I could then boot up Puppy using the Live Puppy USB flash drive and use Puppy utilities (YaPl) to create another Live Puppy USB flash drive which I can "write" to and save my changes for persistence.
Would this work?
I could then boot up Puppy using the Live Puppy USB flash drive and use Puppy utilities (YaPl) to create another Live Puppy USB flash drive which I can "write" to and save my changes for persistence.
Would this work?
I wonder why the installer you used made the USB read only?
I am guessing it used a iso9660 format.
That would make it act like a live CD.
YaPI may not be the best installer program to use.
YaPI installs a boot loader that may not work for your computer. It does not support UEFI bios booting in normal mode.
I am not saying do not try it, just it may not work without changing some UEFI bios settings.
Puppy has other installers for making a live Puppy USB flash drive.
If you would tell use what exact Puppy version you are using.
We could tell you what installers it has for doing a live Puppy USB flash drive.
I am guessing it used a iso9660 format.
That would make it act like a live CD.
YaPI may not be the best installer program to use.
YaPI installs a boot loader that may not work for your computer. It does not support UEFI bios booting in normal mode.
I am not saying do not try it, just it may not work without changing some UEFI bios settings.
Puppy has other installers for making a live Puppy USB flash drive.
If you would tell use what exact Puppy version you are using.
We could tell you what installers it has for doing a live Puppy USB flash drive.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
bigpup and mikeslr,
As mentioned earlier, I used the Linux version of Unetbootin (version 608) to make a USB Flash Live BionicPuppy. When I tried to boot from it in the D620 laptop, I got a message that no Operation System was detected.
I understand from your posts that this is not surprising since Linux version of Unetbootin doesn't work well. However, you said that it is possible to change the config file so that it would work. Could you help me with this?
Below is the contents of the syslinux.cfg file:
default puppy
#display boot.msg
prompt 1
timeout 100
#F1 boot.msg
F2 help/help.msg
F3 help/help2.msg
ui /menu.c32
menu resolution 800 600
menu title bionicpup64 8.0 Live
menu background splash.png
menu tabmsg Press Tab to edit entry, F2 for help, Esc for boot prompt
menu color border 37;40 #80ffffff #00000000 std
menu color sel 7;37;40 #80ffffff #20ff8000 all
menu margin 1
menu rows 20
menu tabmsgrow 26
menu cmdlinerow -2
menu passwordrow 19
menu timeoutrow 28
menu helpmsgrow 30
label puppy
linux vmlinuz
initrd initrd.gz
append pmedia=cd
menu label bionicpup64 8.0
text help
Start bionicpup64 8.0 normally.
endtext
label puppy-fsck
linux vmlinuz
initrd initrd.gz
append pfix=fsck pmedia=cd
menu label bionicpup64 8.0 - filesystem check
text help
Start bionicpup64 8.0 normally with save filesystem check.
endtext
label puppy-ram
linux vmlinuz
initrd initrd.gz
append pfix=ram pmedia=cd
menu label bionicpup64 8.0 - RAM only (no pupsave)
text help
Start bionicpup64 8.0 with no pupsave - RAM only.
endtext
label puppy-nox
linux vmlinuz
initrd initrd.gz
append pfix=nox pmedia=cd
menu label bionicpup64 8.0 - without graphical desktop
text help
Start bionicpup64 8.0 in command-line mode (Linux console).
Graphical desktop later can be started by typing "xwin".
endtext
menu separator
label puppy-nokms
linux vmlinuz
initrd initrd.gz
append nomodeset pmedia=cd
menu label bionicpup64 8.0 - No KMS
text help
No Kernel mode setting
endtext
label puppy-safe
linux vmlinuz
initrd initrd.gz
append pfix=ram,nox pmedia=cd
menu label bionicpup64 8.0 - For machines with severe video problems
text help
Start bionicpup64 8.0 without savefile, without KMS, and run xorgwizard
to choose video resolutions before starting graphical desktop.
endtext
label puppy-rsdh
linux vmlinuz
initrd initrd.gz
append pfix=rdsh pmedia=cd
menu label bionicpup64 8.0 - Ram Disk SHell
text help
Execute 'init' then dropout to prompt in initramfs
endtext
As mentioned earlier, I used the Linux version of Unetbootin (version 608) to make a USB Flash Live BionicPuppy. When I tried to boot from it in the D620 laptop, I got a message that no Operation System was detected.
I understand from your posts that this is not surprising since Linux version of Unetbootin doesn't work well. However, you said that it is possible to change the config file so that it would work. Could you help me with this?
Below is the contents of the syslinux.cfg file:
default puppy
#display boot.msg
prompt 1
timeout 100
#F1 boot.msg
F2 help/help.msg
F3 help/help2.msg
ui /menu.c32
menu resolution 800 600
menu title bionicpup64 8.0 Live
menu background splash.png
menu tabmsg Press Tab to edit entry, F2 for help, Esc for boot prompt
menu color border 37;40 #80ffffff #00000000 std
menu color sel 7;37;40 #80ffffff #20ff8000 all
menu margin 1
menu rows 20
menu tabmsgrow 26
menu cmdlinerow -2
menu passwordrow 19
menu timeoutrow 28
menu helpmsgrow 30
label puppy
linux vmlinuz
initrd initrd.gz
append pmedia=cd
menu label bionicpup64 8.0
text help
Start bionicpup64 8.0 normally.
endtext
label puppy-fsck
linux vmlinuz
initrd initrd.gz
append pfix=fsck pmedia=cd
menu label bionicpup64 8.0 - filesystem check
text help
Start bionicpup64 8.0 normally with save filesystem check.
endtext
label puppy-ram
linux vmlinuz
initrd initrd.gz
append pfix=ram pmedia=cd
menu label bionicpup64 8.0 - RAM only (no pupsave)
text help
Start bionicpup64 8.0 with no pupsave - RAM only.
endtext
label puppy-nox
linux vmlinuz
initrd initrd.gz
append pfix=nox pmedia=cd
menu label bionicpup64 8.0 - without graphical desktop
text help
Start bionicpup64 8.0 in command-line mode (Linux console).
Graphical desktop later can be started by typing "xwin".
endtext
menu separator
label puppy-nokms
linux vmlinuz
initrd initrd.gz
append nomodeset pmedia=cd
menu label bionicpup64 8.0 - No KMS
text help
No Kernel mode setting
endtext
label puppy-safe
linux vmlinuz
initrd initrd.gz
append pfix=ram,nox pmedia=cd
menu label bionicpup64 8.0 - For machines with severe video problems
text help
Start bionicpup64 8.0 without savefile, without KMS, and run xorgwizard
to choose video resolutions before starting graphical desktop.
endtext
label puppy-rsdh
linux vmlinuz
initrd initrd.gz
append pfix=rdsh pmedia=cd
menu label bionicpup64 8.0 - Ram Disk SHell
text help
Execute 'init' then dropout to prompt in initramfs
endtext
Specs:
Dell Latitude D610
http://www.notebookreview.com/notebookr ... ics-specs/
Dell Latitude D620
http://www.notebookreview.com/notebookr ... ics-specs/
Laptops have a disposition to burn a cd...boot it
but when you save a session back to cd it won't boot.
This doesn't happen with some brands but because the hardware is so cut down it can occur.
Still worth exploring with the laptop with no hard drive.
Could get lucky.
Burn at no more than 32 speed with a burn that can do multisession.
Chris.
Dell Latitude D610
http://www.notebookreview.com/notebookr ... ics-specs/
Dell Latitude D620
http://www.notebookreview.com/notebookr ... ics-specs/
Laptops have a disposition to burn a cd...boot it
but when you save a session back to cd it won't boot.
This doesn't happen with some brands but because the hardware is so cut down it can occur.
Still worth exploring with the laptop with no hard drive.
Could get lucky.
Burn at no more than 32 speed with a burn that can do multisession.
Chris.
Which one?I have been trying to settup BionicPuppy.
Bionicpup64 8.0?
Bionicpup32 8.0?
Yes there is a difference!
I see by the syslinux.cfg you posted, it seems to be Bionicpup64 8.0
However, in the future, that specific info needs to be given in the beginning of a topic, first post!!
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Sorry, but I have to ask.The D620 does not have a HD so I have to use a USB Flash drive.
You are sure the bios is being setup to look for a USB device to boot from?
The USB device is being selected as the boot device?
Have you tried plugging the USB drive into a different USB port?
Is the USB drive partition formatted fat32?I got a message that no Operation System was detected.
Is the partition flagged boot.
That syslinux.cfg should at least let it try to boot but maybe give warning about finding Bionicpup files.
Editing the entries in the syslinux.cfg
Changing the
Code: Select all
pmedia=cdCode: Select all
pmedia=usbflashThe things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Yes, I am trying to setup BionicPup 64 8.0.
The Bios is set to boot from the usb drive and has been booting fine with a USB drive that has antiX on it.
I tried the USB drive in 3 different ports.
The USB drive partition is formated fat 32.
I don't know if the partition is "flagged boot"
Editted the entries in the syslinux.cfg from pmedia=cd to pmedia=usbflash
When I try to boot, I get the following message:
No bootable device
or
Read failure on USB device
The Bios is set to boot from the usb drive and has been booting fine with a USB drive that has antiX on it.
I tried the USB drive in 3 different ports.
The USB drive partition is formated fat 32.
I don't know if the partition is "flagged boot"
Editted the entries in the syslinux.cfg from pmedia=cd to pmedia=usbflash
When I try to boot, I get the following message:
No bootable device
or
Read failure on USB device
So you have now confirmed that USB bootability works.greyowl wrote:The Bios is set to boot from the usb drive and has been booting fine with a USB drive that has antiX on it.
So there are two possibilities .When I try to boot, I get the following message:
No bootable device
or
Read failure on USB device
1. Your USB installation method has failed to put a bootloader on the drive.
2. There is something wrong with your flash drive.
At this point, messing around with the syslinux.cfg is irrelevant.
You need a different way of setting up the flash drive. I gave you one above.