(OLD) (ARCHIVED) Puppy Linux Discussion Forum Forum Index (OLD) (ARCHIVED) Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

This forum can also be accessed as http://oldforum.puppylinux.com
It is now read-only and serves only as archives.

Please register over the NEW forum
and continue your work there. Thank you.

 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups    
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 21 Jan 2021, 00:30
All times are UTC - 4
 Forum index » House Training » Beginners Help ( Start Here)
Windows 8, 8.1 and 10: How to Boot Puppy
Moderators: Flash, Ian, JohnMurga
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
Page 4 of 5 [69 Posts]   Goto page: Previous 1, 2, 3, 4, 5 Next
Author Message

Joined: 16 Jun 2008
Posts: 3913
Location: 500 seconds from Sol

PostPosted: Tue 10 Jan 2017, 12:36    Post subject: Booting Puppy from a CD/DVD?  

Hi All,

If I understand his post correctly, mistfire has packaged an efi boot image you can use in constructing a CD/DVD of your remastered Puppy so that it will boot from that media. http://www.murga-linux.com/puppy/viewtopic.php?p=938720#938720.

It is based on the work of Fatdog (kirk and jamesbond).

Back to top
View user's profile Send private message 

Joined: 16 Jun 2008
Posts: 3913
Location: 500 seconds from Sol

PostPosted: Thu 16 Feb 2017, 20:48    Post subject: Recommendation as of February 16, 2016  

Hi All,

If you've skipped to here from the first post, this link will take you back after you've read this: http://www.murga-linux.com/puppy/viewtopic.php?p=858159#858159

Having skipped here, you've missed the instructions that you have to turn off Fast Boot, AKA Fast Startup which is Windows misleading term for what, Linux refers to "hibernate". Using either hibernate under Linux or Fast Boot under Windows, you really haven't turned off your computer. Consequently, when you Start it again, you're really not booting it and there's no way to boot into any other system. In Linux, hibernate is something the user must consciously choose. In Windows, it's automatic, part of the boot instructions.

You may also have to turn off Intel Smart Response Technology (ISRT).

Links to instructions are on the first post.

You also may not be aware that I do not have an UEFI computer; so this thread primarily serves to provide links to the efforts and discoveries of those who do. However, since my first post I have acquired a Windows 7 computer which --AFAIK-- is structurally the same as a Windows 8/8.5/10 computer. That is, the factory installation of Windows created 3 partitions of the Hard-drive. Each is formatted NTFS. The First, and smallest, is labeled "System". The Third is labeled "Recovery". You don't want to mess with either of those.. The Second and largest is labeled "Windows". Assuming you haven't filled it up with Windows junk, you can safely resize it with gparted to create a FOURTH partition, formatted as Linux to house any Linux Distro. And, as a Frugal install of Puppy does not require an entire partition --it can be located in a folder-- you can place one "Big Linux Distro" and as may Puppy Linux variants there as you like.

Doing a Wellminded Search, http://wellminded.net63.net/ on the term "gparted" will turn up instructions on how to use it safely. But, remember what I said about the 3 partitions already on your computer.

Limbomusic has recently posted regarding an easy way to setup ANY puppy linux to run from a USB-Key, http://www.murga-linux.com/puppy/viewtopic.php?p=943608#943608, primarily by following Jamesb’s instructions found here: http://blog.puppylinux.com/?viewDetailed=00009.

There's nothing wrong with running Puppies from a USB-Key, It's the preferred method used by many experienced Puppy fans, I frequently explore a Puppy using that method if I'm not familiar with it, or --being familiar with it-- want to try something without jeopardizing a well-functioning system. But running any Puppy from a USB-Key will always be slower, at least to bootup, than running the same Puppy from a hard-drive. And a Terabyte hard-drive affords more possibilities than even a 64 Gb USB-Key.

The one unmentioned first step in both Limbomusic's and Jamesb’s posts is that either (a) each and every time to you want to boot the computer from the USB-Key you have to hold down some key to get a "Boot Menu" so that it doesn't automatically boot from your hard-drive; or (b) change your computer's settings so that it will give boot-priority to your USB-Key over your Hard-drive. I chose (b) for my new-to-me Windows 7 computer; setting it up to (1) boot from a bootable CD/DVD if one was in the optical drive, if not (2) boot from a bootable USB-Key if one was plugged in, and (3) only if both a bootable CD/DVD AND a bootable USB-Key are absent, boot from the Hard-Drive.

I haven't had, and rarely expect to have, a bootable CD/DVD in the optical drive. It takes my computer about 1 second to check. So under normal circumstances if I've plugged in a bootable USB-Key, my computer will follow its instructions; and if I haven't, my computer will boot Windows 7. And I haven't had to mess with the boot-system Windows wrote.

With your USB-Key’s grub.cfg providing your computer with instruction as to which operating system to boot, you are not limited to only booting those systems on your USB-Key. Grub.cfg can also be written to boot any (or many) Puppies you’ve frugally installed to folders on your computer’s hard-drive.

Jamesb provided this example of a grub.cfg:

menuentry "Start Slacko" {
linux /vmlinuz
initrd /initrd.gz

Supposed you resized your second partition and from the now available space created a fourth partition. Puppy would recognize it as sda4 –drive a, partition 4. But grub2 begins numbering with “0” =Zero. So sda4 in “grub2-speak” is hd0,3. If, for example, you placed tahrpup64’s necessary files* in a folder named tahrpup64 on sda4, the following menuentry would boot it (assuming you’ve followed jamesb’s instructions to setup your USB-Key):

menuentry "tahrpup64" {
set root='(hd0,3)' #### Note the single-quote marks, don’t include this comment
linux /tahrpup64/vmlinuz
initrd /tahrpup64/initrd.gz

There are other techniques for specifying on which partition a desired folder is to be found, and other "boot arguments" --e.g. don't load the SaveFile/Folder; don't automatically SAVE changes-- which can be included. But I’ll leave explaining them to those Puppy users who actually use “grub2”. [Not having an UEFI computer, I can use grub4dos]. In fact, if I’ve gotten the above wrong, please post a correction.

* If you are already running any Puppy –for example from a CD/DVD or USB-Key-- to obtain the necessary files to boot any Puppy [excluding maybe Series 1 and 2?] browse to that Puppy’s ISO and Left-Click it, mounting it. A window will open revealing its contents. Place your mouse-cursor on each of the following files: vmlinuz(x), initrd.(x), xxx.xfs. Left-Press-Hold and drag in into your folder; release and select “copy”. Left-Click the ISO again to unmount it.

The “x”s will vary with your Puppy. Vmlinuz may have an ending number. Initrd usually ends with a .gz or a .xz but may have no suffix at all. The files referred to as .xfs will usually be sfs, but sometimes a number followed by fs. Fs stands for file-system. Sfs stands for squashed=compressed file-system. A number just identifies the format used in “squashing”. Tahrpup64’s ISO has two: puppy_tahr64_version-number.sfs –which contains tahrpup64’s operating system and builtin applications; and zdrv_tahrp64_version-number.sfs which contains firmware and drives. The ISO’s of other Puppies may not have a zdrv, but may include other SFSes having special purposes. It’s best to check a specific Puppy’s thread before leaving any sfs out. Note, how the vmlinuz and initrd are named in the ISO, your menuentry must use that name.

Edit: Re-reading this post, I'm not sure that I clearly spelled out how I boot Puppies and DebianDogs. While all my Puppies and DebianDogs are in folders on the 4th partition, I did not install Grub4dos to the hard-drive. Rather, I purchased the smallest (least expensive but quality) USB-Key I could find and, (having booted into a Puppy on a 2nd USB-Key) and copying the first Puppy's necessary files to a folder on the 4th partition I ran Grub4Dos and instructed it to install itself on the 1st (small) USB-Key. Grub4dos, of course, created a menu-entry for that Puppy.

The functioning Windows or Linux Grub2 boot-loader continued to exist, neither overwritten nor interfered with. Plug in the Key and boot Puppy. Don't plug in the Key and boot Windows and/or one of the "Big Distros".

After being able to boot into a Puppy on the hard-drive via the USB-Key, its a simple matter to add more Puppies/Dogs (in folders on the 4th partition) and to edit Grub4dos' menu.lst on the USB-Key to boot into them. Or, re-run Grub4dos, again installing it to the USB-Key.


Last edited by mikeslr on Sat 27 May 2017, 08:48; edited 2 times in total
Back to top
View user's profile Send private message 

Joined: 10 Sep 2011
Posts: 12591
Location: Mer méditerrannée (1 kms°)

PostPosted: Mon 27 Feb 2017, 07:15    Post subject: the menu is not as pretty as others  

mikeslr, i fully agree with you. Why some devs still continue using old boots ? grub4Dos is perfect, excepted that the menu is not as pretty as others.
Nevertheless see Pupjibaro's starting scripts, they ave been colorized nicely
(sorry for my english Wink )

Passenger Pelo ! don't ask him to repair the aircraft. Don't use him as a demining dog .... pleeease.
Back to top
View user's profile Send private message Yahoo Messenger 

Joined: 19 Apr 2009
Posts: 424

PostPosted: Sun 14 May 2017, 22:05    Post subject: Success dual-booting HP 14-an013nr laptop
Subject description: Another Windows 10 laptop

HP 14-an013nr "streambook"
This laptop boots without issue from a Fatdog flash drive, but after installing FD on a SSD I could not get Linux to #1 in the boot order using BIOS settings. I had to esc/F9 and manually choose boot device. After applying jamesbond's method of editing the EFI partition (sda1 on this machine), it now boots to grub menu. Very Happy
--Secure boot on, legacy boot off, hibernate off
--Can start Windows directly from reFind, or add grub entry
menuentry "Windows 10 " {
set root=(hd0,1)
chainloader /EFI-win/Microsoft/Boot/bootmgfw.efi
Back to top
View user's profile Send private message 

Joined: 16 Jun 2008
Posts: 3913
Location: 500 seconds from Sol

PostPosted: Thu 17 Aug 2017, 11:27    Post subject: BOOT FROM GPT HARD DISK IN LEGACY BIOS MODE  

Information and links provided by d4p . http://murga-linux.com/puppy/viewtopic.php?p=964610#964610

Back to top
View user's profile Send private message 

Joined: 16 Jun 2008
Posts: 3913
Location: 500 seconds from Sol

PostPosted: Thu 17 Aug 2017, 17:41    Post subject: Boot from USB-Key, Puppy Files on hard-drive  

See, http://murga-linux.com/puppy/viewtopic.php?p=964636#964636

Although I don't have a UEFI computer, having Puppy's necessary files on the computer (each in their own folder) setting the computer to give boot priority to the USB-Key and plugging in the USB-Key (well, actually its always plugged in) when I want to boot into a Puppy means I haven't had to make any changes to the default boot-loader my computer came with.

Back to top
View user's profile Send private message 

Joined: 16 Jun 2008
Posts: 3913
Location: 500 seconds from Sol

PostPosted: Fri 10 Nov 2017, 12:46    Post subject: Boot from USB-Key on Really Problematic Computer
Subject description: Asus zenbook ASUSTeK model: UX305FA v: 1.0

Hi All,

Thanks to the hard work of bigpup and peterw, and especially the perseverance of overkill22, overkill22 was finally able to boot a Puppy from his ASUSTeK model: UX305FA v: 1.0 by:

disabling secure boot,
disabling fast boot,
Enabling LAUNCH CSM,


For those who, like myself, had never heard of CSM,

"CSM booting[edit]
To ensure backward compatibility, most UEFI firmware implementations on PC-class machines also support booting in legacy BIOS mode from MBR-partitioned disks, through the Compatibility Support Module (CSM) that provides legacy BIOS compatibility. In this scenario, booting is performed in the same way as on legacy BIOS-based systems, by ignoring the partition table and relying on the content of a boot sector.[36]
BIOS-style booting from MBR-partitioned disks is commonly called BIOS-MBR, regardless of it being performed on UEFI or legacy BIOS-based systems. Furthermore, booting legacy BIOS-based systems from GPT disks is also possible, and such a boot scheme is commonly called BIOS-GPT." https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#CSM_booting

"Once you know that, you should understand that UEFI-CSM means "NON-pure UEFI boot mode" (i.e. BIOS compatility mode), and that UEFI means "pure UEFI" mode, and this is what Rufus tells you.
Therefore, if you see UEFI-CSM, then you should know that the drive will NOT boot in pure UEFI mode, but will need the CSM (a.k.a. BIOS compability) mode activated to be bootable on an UEFI platform.
If on the other hand you see UEFI, then it means your drive is bootable in pure UEFI, i.e. even if CSM is disabled on the target computer." by pbatard, https://github.com/pbatard/rufus/issues/731

Back to top
View user's profile Send private message 

Joined: 17 Apr 2014
Posts: 106

PostPosted: Mon 12 Feb 2018, 07:36    Post subject: mikeslr explanations are clear.  

mikeslr explanations are clear. what works, what does not. that is perfect.
Back to top
View user's profile Send private message 

Joined: 16 Jun 2008
Posts: 3913
Location: 500 seconds from Sol

PostPosted: Mon 02 Jul 2018, 10:32    Post subject: Learning from the "Dogs"  

Hi All,

Although, concerning "DebianDogs" in general, and Debian-Stretch-Live in particular, rcrsn51's instructions for dealing with an UEFI computer --especially with the additional obstacles that have appeared since July 2015-- are clear, sound. His post appears here: http://murga-linux.com/puppy/viewtopic.php?p=997643#997643

Edited: See rcrsn51's post next following explains why it won't work for Puppies. Thanks rcrsn51.


Last edited by mikeslr on Thu 05 Jul 2018, 16:00; edited 1 time in total
Back to top
View user's profile Send private message 

Joined: 05 Sep 2006
Posts: 13129
Location: Stratford, Ontario

PostPosted: Mon 02 Jul 2018, 11:27    Post subject:  

There is an ongoing problem for Windows users who want to install a Puppy for the first time.

If you download, then click-mount a Puppy ISO from Windows, it will show the files using their old DOS 8.3 filenames.

This is NOT the fault of Windows!
Windows is NOT renaming the files!

This is a consequence of the old-fashioned way that Puppy builds its ISOs. Dog ISOs don't have this problem.

So you cannot copy the files out of the mounted ISO into a frugal install. Instead you need a tool like 7-zip that can extract an ISO with the original names.

Now you can build your Puppy flash drive setup as usual, but with UEFI and a GRUB2 menu. Read here. For example:
menuentry "Puppy on USB" {
   search --no-floppy --set=root --file /usbmarker
   linux /puppy/vmlinuz pmedia=usbflash psubdir=puppy pfix=fsck
   initrd /puppy/initrd.gz

The simplest approach to this situation is to start building Puppy ISOs with Joliet extensions enabled. Then Windows can read them correctly.
Back to top
View user's profile Send private message 

Joined: 19 Dec 2017
Posts: 17

PostPosted: Fri 01 Mar 2019, 22:49    Post subject:  

Yeah, hi. So just to set things straight in short, simple terms, just as long as I disable hibernation/Fast Boot in Windows 10, and launch Puppy fully from USB only (UEFI/Syslinux), I can then safely dual boot Puppy and Win 10 on the same machine WITHOUT hosing the Win 10 partition into unusable state? Please confirm.

It has been my standard practice since time immemorial that I NEVER mess with the Windows partition while dual booting. I always keep Linux on its own physical disk, to avoid all the traps that Microsoft loves to lay to the paths of us Linux users.

I ask, because circumstances have forced my very 1st Win 10 unit into my hands recently, and I need the Win 10 installation to remain functional, because of reasons. But at the same time, I wouldn't want said machine to be exclusively Microsoft's domain. So, just as long as I use Puppy from its own physical device, I should be allright, right?
Back to top
View user's profile Send private message 

Joined: 12 Aug 2006
Posts: 3702
Location: Tamworth UK

PostPosted: Sat 02 Mar 2019, 09:25    Post subject:  

Confirmed in that as long as you always make sure Windows is fully closed down and not expecting ANY fast start up tricks, you will be OK.
"Just think of it as leaving early to avoid the rush" - T Pratchett
Back to top
View user's profile Send private message 

Joined: 19 Apr 2014
Posts: 42

PostPosted: Sat 13 Apr 2019, 19:45    Post subject:  

Hello everyone,

Sorry but I'm still a newbie. So my pc came with Windows 10 preinstalled. It's been totally locked by the manifacturer. i tried everything. I can't boot in dual boot. I can, however, boot on a UEFI usb stick. So I can enjoy Puppy Linux, which is almost the only Linux distro I can use on this pc. So my question is this. If I partition my hard drive and use, let's say, 5 Gb for instance, is it possible to use this partition to install Puppy on my hard drive and use a usb stick as a bootloader that would allow me to boot into the Puppy installed on my hard drive. Am I clear?

If so, how would I have to create my partiton table and install Puppy?

Thanks in advance
Back to top
View user's profile Send private message 

Joined: 29 Jan 2006
Posts: 4499
Location: Sydney Australia

PostPosted: Sat 13 Apr 2019, 22:32    Post subject:  

" is it possible to use this partition to install Puppy on my hard drive and use a usb stick as a bootloader that would allow me to boot into the Puppy installed on my hard drive.

Am I clear? "


I always advocate running Puppy from usb.
Cheap..cheerful...quick and absolutely won't stuff up your hard drive.

Never would I Puppy from a hard drive.

Don't delete windows for the one time you want to use it.
Ther are plenty of small programs that can defeat Windows 10 spying on you, and keep it lean and clean

2 quickies for a start.

O&O ShutUp10: Free antispy tool for Windows 10


Winaero Tweaker
universal tweaker software which supports Windows 7, Windows 8,
Windows 8.1 and Windows 10.


It always pays to read up the how to pages.

O& O gets a good rap.


Always...always give the computer specs.
The brand...HP, Acer etc, and the model number.

If it's a generic...built by a computer shop,
supply the motherboard brand and m/b number.

Because I'm sure in another post you failed to do that.

Good answers come from good questions.



We remind you that this is a modified version of Windows 10.
Install Windows 10 by following our guide on how to perform a clean installation of Windows 10 .


How to install windows 10 lean (CloudE) Download ISO


Windows 10 lean is the lightweight version of the windows 10, stripped all the way down, and it’s really fascinating.

" Unlike Windows 10 S, which wasn’t really lightweight at all.
You can get an idea a standard windows 10 ISO is about 4gb while the windows 10 lean (64-bit) is just approximately 2Gb, exciting?
Yeah "


Back to top
View user's profile Send private message 

Joined: 11 Oct 2009
Posts: 13981
Location: S.C. USA

PostPosted: Sun 14 Apr 2019, 02:06    Post subject:  

how would I have to create my partiton table and install Puppy?

That will delete everything on the hard drive.
To make a new partition all you do is make a big partition smaller and use the new unallocated space to make the new partition.
You still use the partition table already there.
Windows 10 uses several partitions, so you have to be careful about which one you make smaller.
Should be one very large data partition that you could change the size.

If you do not want to stick with just using Puppy from a USB.
The Lick installer is the easiest thing to use to get Puppy on the hard drive along side Windows.

LICK is a Puppy Linux installer for Windows.
With Lick no changing of partitions required. It will use what is already there.
It configures Windows and Puppy Linux to dual-boot environment in just a few clicks.
This makes it perfect if you want to try out Linux without the hassle of installing.

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 Shocked
YaPI(any iso installer)
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 4 of 5 [69 Posts]   Goto page: Previous 1, 2, 3, 4, 5 Next
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
 Forum index » House Training » Beginners Help ( Start Here)
Jump to:  

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

Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0783s ][ Queries: 13 (0.0112s) ][ GZIP on ]