Even Puppy's Grub4DOS (essentially the old 'legacy' GRUB, from before GRUB2) will do this.
Even if you run only Puppy (like I do), Grub4DOS still makes an entry for Windoze by default; the path is there for the Windoze NTLDR, should it ever be wanted. Before going 'all-Puppy', I ran XP alongside 4 or 5 Puppies for nearly 2 years. And Linux bootloaders are more versatile than their Windoze counterparts; you don't have to run 'em from the MBR.....you can even run them from any partition's 'volume boot record' (more commonly known as the 'partition boot sector', or PBR.). So long as you point the relevant lines of your bootloader in the right direction, it honestly doesn't matter where on the drive it is physically situated.
It is only a set of directions, when all's said & done.....although the Master Boot Record is normally utilised for the simple reason that most industry-standard BIOS programs are set-up to look there first, in the initial 512K of the first sector, before looking anywhere else.
Anyway, Chris is right. Most of us are lazy; why arse around with the BIOS every time, when the Boot Menu will give you the choice? And to my mind, using a properly set-up Boot Menu is a far more technically satisfying solution.
Currently, I have 10 Pups on a 500 GB WD Caviar 'Blue'.....and Anti-X 16.1 on a 32GB KingSpec SSD. Anti-X boots via the Puppy Grub4DOS bootloader; I have an entry in Grub4DOS which 'chains' into Anti-X's GRUB2. Like this:-
# Full installed Linux
title AntiX 16.1 (sdb1/boot)
When I installed Anti-X, I disconnected the main drive, so the LiveCD only 'saw' the smaller SSD. Hence, it installed GRUB2 to that drive. I did things this way, knowing that it was extremely easy to 'chain' into other boot-loaders, even on other drives, from Grub4DOS itself.....and also because I firmly believe, and maintain, that GRUB2 is a bloated, excessively over-complicated monstrosity of a thing which, to my mind, has no real place in the elegantly simple set-up of your average Linux distro (compared to Windoze, that is). Why construct a simple, robust OS, then burden it down with summat like that?
I still maintain Grub4DOS is one of the most versatile boot-loaders I've ever come across.....and Pup's version is specially 'tweaked' to search 'two-deep' inside a partition's top-level directories for kernels as well. Why on earth the Linux community abandoned it in favour of its offspring I shall never, ever understand.
(I know this doesn't directly answer the OP's original query.....but it does serve to illustrate how versatile most boot-loaders really are. They usually have many more options than your average Joe will ever be aware of. All it takes is a wee bit of research; as with so much 'tech' stuff, the answers are out there on the 'net; you just have to 'dig' a little!)
That's what a 'search engine' is for...
Edited by Mike_Walsh, 10 March 2018 - 08:37 PM.
Distros:- Multiple 'Puppies'..... and Anti-X 16.1
My Puppy BLOG ~~~ My Puppy PACKAGES
Compaq Presario SR1916UK; Athlon64 X2 3800+, 3 GB RAM, WD 500GB Caviar 'Blue', 32GB Kingspec PATA SSD, Seagate 'Expansion' 3 TB USB 3.0 external HDD, ATI Radeon Xpress 200 graphics, Dell 15.1" pNp monitor (1024 x 768), TP-Link PCI-e USB 3.0 card, Belkin PCI USB 2.0 4-port card, self-powered 7-port USB 2.0 hub
Dell Inspiron 1100; 2.6 GHz P4, 1.5 GB DDR1, 64GB KingSpec IDE SSD, Intel 'Extreme' graphics, 1 TB Seagate 'Expansion' external storage, HP HD2300 webcam.