So I have this old computer (no idea of the specs... but it runs win XP ok) and I want to play around with puppy so I decided to create a bootable puppy CD with tahrpup 6.0.2. In the past I've successfully created bootable USB drives with Fatdog for a laptop in order to remove a virus so I thought this would be a cinch.
Problem is, try as I might, I can't.
It seems that because I'm using windows to burn the ISO to disk, the operating system renames and forces uppercase on all the files such that I get a buggerized version. Puppy finds vmlinuz and initrd.gz ok but then puppy has kittens (pun? intended) when it then tries to find puppy_tahr_6.0.sfs because winblows has renamed it to PUPPY_TA.SFS. I get the dreaded "[can't find]... Dropping out to initial-ramdisk console..."
So, who out there in puppy land can tell me how to force windows to create an exact copy of the tahrpup ISO on disk as the makers intended it rather than the windozized one?
Bonus Quesion: Who can tell my why the creators of puppy didn't choose a file name that circumvented this obvious achilies heel?
I've tried Nero, Imgburn and the native windows 8 disk burner. Nero is no longer an option and neither is making a USB as the mobo has no way of booting from USB.
Everything I do either results in a .sfs not found or a disk that simply wont boot. I don't drink enough to use all the coasters I have.
How to create a live Puppy CD in WinXP?
-
L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: Help... Can't create a working puppy CD
Hope this helps: http://www.puppylinux.com/cd-puppy.htmSlyPhy wrote:I've tried Nero, Imgburn and the native windows 8 disk burner.
Murphy's Law
Hi SlyPhy,
In the nearly 8 years I've been around Puppy, yours is the first report that I recall in which BurnCDCC couldn't successfully burn a Puppy ISO to a CD/DVD. Which may be way no one has seen the necessity of fixing the 'Achilles heel': Achilles could wear stainless steel boots.
Windows screwing things up by capitalizing "names" while copying is common. The work-around is to edit the names back to what they were supposed to be after Windows was finished screwing up. But, other than BurnCDCC's dialog window to select the burner and the ISO, I thought BurnCDCC by-passed Windows; operating at a closer to bios-to-hardware level.
It seems that somehow your Windows 8 has managed to remove Achilles' footware. Murphy's Law.
Am I correct in assuming that you no longer have the computer for which you burned FatDog to a USB-Key in order to deal with its virus? Obviously, that computer was able to boot from a USB-port, otherwise you wouldn't have been able to boot the FatDog-USB-key. If that assumption isn't correct, than you should be able to boot into FatDog --or any Pup burned to a USB-key-- and use Puppy's tools to burn a CD.
The only other thing which comes to mind is Free ISO Burner, http://www.freeisoburner.com/, Probably won't work, but it's free.
Edit: or maybe try burning without calling up the Graphical User Interface: http://teamwindows8.com/2012/11/how-to- ... -software/
mikesLr
In the nearly 8 years I've been around Puppy, yours is the first report that I recall in which BurnCDCC couldn't successfully burn a Puppy ISO to a CD/DVD. Which may be way no one has seen the necessity of fixing the 'Achilles heel': Achilles could wear stainless steel boots.
Windows screwing things up by capitalizing "names" while copying is common. The work-around is to edit the names back to what they were supposed to be after Windows was finished screwing up. But, other than BurnCDCC's dialog window to select the burner and the ISO, I thought BurnCDCC by-passed Windows; operating at a closer to bios-to-hardware level.
It seems that somehow your Windows 8 has managed to remove Achilles' footware. Murphy's Law.
Am I correct in assuming that you no longer have the computer for which you burned FatDog to a USB-Key in order to deal with its virus? Obviously, that computer was able to boot from a USB-port, otherwise you wouldn't have been able to boot the FatDog-USB-key. If that assumption isn't correct, than you should be able to boot into FatDog --or any Pup burned to a USB-key-- and use Puppy's tools to burn a CD.
The only other thing which comes to mind is Free ISO Burner, http://www.freeisoburner.com/, Probably won't work, but it's free.
Edit: or maybe try burning without calling up the Graphical User Interface: http://teamwindows8.com/2012/11/how-to- ... -software/
mikesLr
-
unicorn316386
I like using the 8:3 naming scheme too. I wonder how hard it would be to rebuild tahr as tahr602.sfs and zdrvt602.sfs. It's interesting that the capitalization (all caps) did not affect things, the last person I heard from who had the same problem also said they had to change everything to lowercase. The README.HTM on the iso actually talks about your exact issue (in fact, that's the only thing README.HTM talks about) so it is already documented.
If your README.HTM is somehow missing, 01micko posted it's contents here:
http://www.murga-linux.com/puppy/viewtopic.php?p=674232#674232
If your README.HTM is somehow missing, 01micko posted it's contents here:
http://www.murga-linux.com/puppy/viewtopic.php?p=674232#674232
I used to believe the same about my computer until I found out it lists usb drives under hard drives.SlyPhy wrote:neither is making a USB as the mobo has no way of booting from USB
Last edited by theru on Thu 10 Dec 2015, 17:42, edited 1 time in total.
The Windows uppercase problem is documented; but the fact that BurnCDCC has done this writing to a CD is, as far as I know, very unusual. Did you get the program from here: http://www.terabyteunlimited.com/downlo ... ftware.htm
Do you have Grub 4 DOS installed as the boot loader agent? If so, it should be possible to unpack the ISO into it's own folder on the hard drive, then write the entry into the Menu.lst (that's a lower-case L-for-Leather - not a number one!). If Windblow's is being it's usual P-I-T-A ; just rename the Tahr files in lower case.
Footnote: Have a search under the terms, long filename truncation, and, enable disable long filenames. This possibly has something to do with the Registry.
Do you have Grub 4 DOS installed as the boot loader agent? If so, it should be possible to unpack the ISO into it's own folder on the hard drive, then write the entry into the Menu.lst (that's a lower-case L-for-Leather - not a number one!). If Windblow's is being it's usual P-I-T-A ; just rename the Tahr files in lower case.
Footnote: Have a search under the terms, long filename truncation, and, enable disable long filenames. This possibly has something to do with the Registry.
Yep. It was a laptop that is now landfill afaik.Am I correct in assuming that you no longer have the computer for which you burned FatDog to a USB-Key in order to deal with its virus?
Also, Since starting this process, my wife has upgraded her (this) laptop to win 10. Not sure that will make any difference though.
I will however try making another fatdog USB and see if I can get it to boot here and burn a puppy cd using fatdog though.
Are you looking at what is on the CD using a Puppy Linux file manager or a Windows file manager?Puppy finds vmlinuz and initrd.gz ok but then puppy has kittens (pun? intended) when it then tries to find puppy_tahr_6.0.sfs because winblows has renamed it to PUPPY_TA.SFS.
If using a Windows file manager.
The files names may be correct, but the file manager is just showing the names wrong.
You could be having some classic, Boot from CD issues, with some old computers.
Try this:
Boot with Puppy live CD
At boot screen select F2 key
Try using one of these boot options
1. puppy acpi=off
2. puppy acpi=on
3. puppy ide=nodma
4. puppy ide=nodma acpi=off
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)
Another Work-around
Hi SlyPhy,
The following "Rube Goldberg" technique may work:
1. Download LinuxLiveUSB Creator -- your choice, regular or portable. http://www.techspot.com/downloads/5488- ... eator.html
2, Run it, installing TahrPup to a USB-Key.
It doesn't matter whether or not your computer can boot via a USB-Port. One of the options you have in setting up the USB-Key with LinuxLiveUSB Creator, is to have it install portable virtualbox to the USB-Key along with the Linux Distro of your choice. http://www.howtogeek.com/65888/create-a ... with-lili/
Per the above Webpage, "Once everything is installed, open an explorer window and navigate to your USB drive. Double click VirtualBox\Virtualize_this_key.exe to launch portable Virtualbox running the OS installed on your drive. [Emphasis supplied for the sake of clarity].
...
Virtualbox will open and start your portable OS...
EDIT: Our wonderful readers pointed out that LiLi does not recommend using persistence with portable VirtualBox."
No matter. Puppies don't need "persistence". Their usual method of adding applications by creating SaveFiles still works. As does the use of SFSes.
Thereafter, you can either run Tahrpup that way --I'm not sure to what extent doing that will waste your computer's limited resources-- or while running Tahrpup use its builtin CD burning applications to burn a Tahrpup CD/DVD.
I'm posting from Tahrpup. Menu>Multimedia lists Burniso2CD, PBurn CD/DVD among its applications.
mikesLr
P.S. Disclaimor -- The above seems very logical. Never having had any reason to do it, I haven't. Consider it a theory. In theory, you should also be able to burn a CD/DVD using BurnCDCC.
The following "Rube Goldberg" technique may work:
1. Download LinuxLiveUSB Creator -- your choice, regular or portable. http://www.techspot.com/downloads/5488- ... eator.html
2, Run it, installing TahrPup to a USB-Key.
It doesn't matter whether or not your computer can boot via a USB-Port. One of the options you have in setting up the USB-Key with LinuxLiveUSB Creator, is to have it install portable virtualbox to the USB-Key along with the Linux Distro of your choice. http://www.howtogeek.com/65888/create-a ... with-lili/
Per the above Webpage, "Once everything is installed, open an explorer window and navigate to your USB drive. Double click VirtualBox\Virtualize_this_key.exe to launch portable Virtualbox running the OS installed on your drive. [Emphasis supplied for the sake of clarity].
...
Virtualbox will open and start your portable OS...
EDIT: Our wonderful readers pointed out that LiLi does not recommend using persistence with portable VirtualBox."
No matter. Puppies don't need "persistence". Their usual method of adding applications by creating SaveFiles still works. As does the use of SFSes.
Thereafter, you can either run Tahrpup that way --I'm not sure to what extent doing that will waste your computer's limited resources-- or while running Tahrpup use its builtin CD burning applications to burn a Tahrpup CD/DVD.
I'm posting from Tahrpup. Menu>Multimedia lists Burniso2CD, PBurn CD/DVD among its applications.
mikesLr
P.S. Disclaimor -- The above seems very logical. Never having had any reason to do it, I haven't. Consider it a theory. In theory, you should also be able to burn a CD/DVD using BurnCDCC.
Hmmmmm.....
Now I'm super confused.
After 2 days of trying... cold booting, warm booting, swearing, trying to resurect the old win xp (which failed), plugging in old drives, unplugging and re-plugging everything, using every puppy boot parameter I could find.. nothing worked - always the same 'dropping out to initial-ramdisk console..." error. I got jack of the whole process and so I turned everything off and went to work.
12 hours later I get home and turn the damn thing on again.
Now here's the thing - the bios is set to boot from ANYTHING other than the hard drive and the hard drive has it's hard switch set to slave yet when I turn it on, questionable puppy CD in CD drive it ignores the boot sequence and starts to boot windows from the HD (for the first time in probably years). Nothing was changed since attempting to boot puppy from liveCD 12 hours previously. Kind of stunned I watch until it reaches the log in screen for win xp... then all of a sudden for no reason the optical drive starts to spin up. I have a couple of stabs at the windows password but it's not what I think it is so I hit the reset button on the front of the box to reboot for the hell of it... and this time instead of windows, puppy starts to load (as was expected the first time). Expecting the familiar drop to console I am floored when instead it says "Loading the 'puppy_tahr_6.0.sfs' main file... copying to ram.
At this point it simply hangs - no # prompt or any cursor.. nothing. After about 2 minutes I start to mash the keyboard to discover that there is some kind of console running as my keystrokes are registered on the screen. I hit enter a couple of times..nothing.. then I type 'ls' and hit enter and it suddenly continues to load and puppy loads fully.
WTF?!
No.... seriously WTF?!
Now I'm super confused.
After 2 days of trying... cold booting, warm booting, swearing, trying to resurect the old win xp (which failed), plugging in old drives, unplugging and re-plugging everything, using every puppy boot parameter I could find.. nothing worked - always the same 'dropping out to initial-ramdisk console..." error. I got jack of the whole process and so I turned everything off and went to work.
12 hours later I get home and turn the damn thing on again.
Now here's the thing - the bios is set to boot from ANYTHING other than the hard drive and the hard drive has it's hard switch set to slave yet when I turn it on, questionable puppy CD in CD drive it ignores the boot sequence and starts to boot windows from the HD (for the first time in probably years). Nothing was changed since attempting to boot puppy from liveCD 12 hours previously. Kind of stunned I watch until it reaches the log in screen for win xp... then all of a sudden for no reason the optical drive starts to spin up. I have a couple of stabs at the windows password but it's not what I think it is so I hit the reset button on the front of the box to reboot for the hell of it... and this time instead of windows, puppy starts to load (as was expected the first time). Expecting the familiar drop to console I am floored when instead it says "Loading the 'puppy_tahr_6.0.sfs' main file... copying to ram.
At this point it simply hangs - no # prompt or any cursor.. nothing. After about 2 minutes I start to mash the keyboard to discover that there is some kind of console running as my keystrokes are registered on the screen. I hit enter a couple of times..nothing.. then I type 'ls' and hit enter and it suddenly continues to load and puppy loads fully.
WTF?!
No.... seriously WTF?!
If it's an old machine, perhaps, Tahrpup is much modern.
I'd try with something like Puppy Precise or Lucid Puppy.
I have a couple of old machines (P IV and Celeron D) and also have troubles booting modern Puppies. Something related with video, I guess.
Saludos.
I'd try with something like Puppy Precise or Lucid Puppy.
I have a couple of old machines (P IV and Celeron D) and also have troubles booting modern Puppies. Something related with video, I guess.
Saludos.
Remember: [b][i]"pecunia pecuniam parere non potest"[/i][/b]
It's a dual core pent IV running at 3.06 GHz and has 2 GB memory... but this is kind of beside the point... puppy is now running (I'm typing this from puppy).What you have failed to mention is: The usual suspects: Processor speed, Memory - how much is important; Hard drive and video. It all matters! Please state MEMORY.
I am really, really confused as to why though.
A little bit of extra information about my coasters if anyone is interested.
Burnt with windows 8 native disk burner resulted in 8.3 file names
Burnt with Nero from win 7 resulted in 8.3 file names. (this was the first disk I made on a friends machine before I had a chance to think about things.. I don't think I even made it a boot disk)
Burnt with Imgburn from win 8 resulted in one with 8.3 file names, one that was unreadable (probably my mistake) and one with long file names.
Burnt with BurnCDCC from win 10 resulted in long file names (it was one of these disks that eventually booted)
I still have no clue as to why the machine suddenly decided to co-operate.
Burnt with windows 8 native disk burner resulted in 8.3 file names
Burnt with Nero from win 7 resulted in 8.3 file names. (this was the first disk I made on a friends machine before I had a chance to think about things.. I don't think I even made it a boot disk)
Burnt with Imgburn from win 8 resulted in one with 8.3 file names, one that was unreadable (probably my mistake) and one with long file names.
Burnt with BurnCDCC from win 10 resulted in long file names (it was one of these disks that eventually booted)
I still have no clue as to why the machine suddenly decided to co-operate.
An old computer is a computer with used hardware.
The hardware can fail or act up at any time.
In troubleshooting do not overlook anything.
Common causes of problems:
Loose connections
Disconnect/reconnect any item including stuff plugged into motherboard.
Dust in computer.
Blocked cooling fan inlets and outlets.
Dust inside a CD player. (clean using cleaning disc)
Look for obvious damage on motherboard. (bulging capacitors) Bad capacitors will cause anything to happen.
Test memory. Run a memory test program like memtest86.
Run testing programs to test condition of storage devices.
Reset computer bios to default settings.
Graphics problems:
Check settings in computer bios dealing with graphics.
Try operating with a basic graphics driver like Vesa.
Component failure can happen at any time to any component.
Usually you can suspect failure in this order.
Power supply.
Hard drive
Graphics card.
motherboard. (older than 5 years suspect first)
Memory.
CPU
The hardware can fail or act up at any time.
In troubleshooting do not overlook anything.
Common causes of problems:
Loose connections
Disconnect/reconnect any item including stuff plugged into motherboard.
Dust in computer.
Blocked cooling fan inlets and outlets.
Dust inside a CD player. (clean using cleaning disc)
Look for obvious damage on motherboard. (bulging capacitors) Bad capacitors will cause anything to happen.
Test memory. Run a memory test program like memtest86.
Run testing programs to test condition of storage devices.
Reset computer bios to default settings.
Graphics problems:
Check settings in computer bios dealing with graphics.
Try operating with a basic graphics driver like Vesa.
Component failure can happen at any time to any component.
Usually you can suspect failure in this order.
Power supply.
Hard drive
Graphics card.
motherboard. (older than 5 years suspect first)
Memory.
CPU
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)
If memtest reports part of the ram is damaged you may be able to skip the damaged part
See this page for more info:
http://unix.stackexchange.com/questions ... r-indicati
See this page for more info:
http://unix.stackexchange.com/questions ... r-indicati
-
WB7ODYFred
- Posts: 169
- Joined: Sun 14 Dec 2008, 02:15
- Location: Oregon & Washington
Create Puppy CD or DVD in WinXP
I want to share some other tools for creating a Live Puppy CD in WINXP or a puppy USB Flash Drive. Your mileage may vary, (YMMV) Use the tool that makes you happy and is useful for your needs.
http://isorecorder.alexfeinman.com/isorecorder.htm a windows power utility to burn .ISO file images to disk from windows menu. You can find versions for WIN XP or WIN Vista or WIN 7.
http://isorecorder.alexfeinman.com/W7.htm Burn a CD or DVD with WIN 7.
I see Linuxliveusb.com was mentioned before to write .ISO file to a USB Flash Drive.
http://linuxliveusb.com/
I like rufus.exe http://rufus.akeo.ie a single .exe file for windows to burn a .ISO image file to a USB Flash disk drive and make it bootable.
I think PuppyLinux might have the Unetbootin utility, available to install from the Puppy Package Manager. http://unetbootin.github.io/
http://launchpad.net/unetbootinn/trunk/ ... ws-613.exe Specific Windows version 6.13 for Unetbootin
Happy Linuxing with Puppy.
Older computer? Use older puppy versions 4.12 or 4.3.1 or 5.7.1 http://distro.ibiblio.org/puppylinux/
Newer computer? try 6.3 Slacko either 32 bit or 64 bit. http://01micko.com/blog/ http://slacko.eezy.xyz/download.html Download Slacko 6.3 here
Older computer BIOS wont boot from USB Flash or CD drive? Use Plop Boot Manager or PlopKexec or Plpbt.bin.
https://www.plop.at/en/bootmanagers.html
https://www.plop.at/en/bootmanager/plpbt.bin.html
I used plopbt.bin to boot TinyCore Linux on a 64 megabyte DRAM computer. http://tinycorelinux.net/ http://distro.ibiblio.org/tinycorelinux ... 6/release/
Fred Finster
My Blog http://puppylinux-or-pcbsd.blogspot.com/
WIN XP to Puppy Linux: 10 minutes, 2 downloads, 1 usb flash drive
http://slacko.eezy.xyz/download.html
http://rufus.akeo.ie Rufus.exe programs writes a .ISO image file to a USB Flash drive and makes the USB Flash drive bootable from the BIOS.
http://isorecorder.alexfeinman.com/isorecorder.htm a windows power utility to burn .ISO file images to disk from windows menu. You can find versions for WIN XP or WIN Vista or WIN 7.
http://isorecorder.alexfeinman.com/W7.htm Burn a CD or DVD with WIN 7.
I see Linuxliveusb.com was mentioned before to write .ISO file to a USB Flash Drive.
http://linuxliveusb.com/
I like rufus.exe http://rufus.akeo.ie a single .exe file for windows to burn a .ISO image file to a USB Flash disk drive and make it bootable.
I think PuppyLinux might have the Unetbootin utility, available to install from the Puppy Package Manager. http://unetbootin.github.io/
http://launchpad.net/unetbootinn/trunk/ ... ws-613.exe Specific Windows version 6.13 for Unetbootin
Happy Linuxing with Puppy.
Older computer? Use older puppy versions 4.12 or 4.3.1 or 5.7.1 http://distro.ibiblio.org/puppylinux/
Newer computer? try 6.3 Slacko either 32 bit or 64 bit. http://01micko.com/blog/ http://slacko.eezy.xyz/download.html Download Slacko 6.3 here
Older computer BIOS wont boot from USB Flash or CD drive? Use Plop Boot Manager or PlopKexec or Plpbt.bin.
https://www.plop.at/en/bootmanagers.html
https://www.plop.at/en/bootmanager/plpbt.bin.html
I used plopbt.bin to boot TinyCore Linux on a 64 megabyte DRAM computer. http://tinycorelinux.net/ http://distro.ibiblio.org/tinycorelinux ... 6/release/
Fred Finster
My Blog http://puppylinux-or-pcbsd.blogspot.com/
WIN XP to Puppy Linux: 10 minutes, 2 downloads, 1 usb flash drive
http://slacko.eezy.xyz/download.html
http://rufus.akeo.ie Rufus.exe programs writes a .ISO image file to a USB Flash drive and makes the USB Flash drive bootable from the BIOS.