Thank you. I will try again.ETP wrote:Please note that the stick needs to have been made bootable with syslinux 4.04 as stated in my original post. Vesamenu.c32 must also be from that version (as supplied) It will not work with 3.73.
How to Dual boot Puppy&XP from USB using syslinux & grub4dos
Re: How to Dual boot Puppy XP from USB using syslinux & grub4dos
Hi ETP
Thanks for suggestion of holding shift key on powerup to revert to hard drive os startup (instead of from cd). I tried twice without success so I'm thinking even if i can figure out the timing, my wife can't/ wont. I'm still hoping that there's a way to add a choice to revert to hard drive startup. I guess this has to happen before puppy gets installed so maybe what i'm asking is in a file that needs compilation or otherwise involving steps way beyond my noobish capabilities!? There are several boot and message files that are editable but the rest aren't. Hmm.
tia
Thanks for suggestion of holding shift key on powerup to revert to hard drive os startup (instead of from cd). I tried twice without success so I'm thinking even if i can figure out the timing, my wife can't/ wont. I'm still hoping that there's a way to add a choice to revert to hard drive startup. I guess this has to happen before puppy gets installed so maybe what i'm asking is in a file that needs compilation or otherwise involving steps way beyond my noobish capabilities!? There are several boot and message files that are editable but the rest aren't. Hmm.
tia
[color=orange]1. Dell Dimension E521, AMD Athln 64, 2 GHz 1.93GB ram,
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Dual boot from cd
Hi canbyte,canbyte wrote:Hi ETP
Thanks for suggestion of holding shift key on powerup to revert to hard drive os startup (instead of from cd). I tried twice without success so I'm thinking even if i can figure out the timing, my wife can't/ wont. I'm still hoping that there's a way to add a choice to revert to hard drive startup. I guess this has to happen before puppy gets installed so maybe what i'm asking is in a file that needs compilation or otherwise involving steps way beyond my noobish capabilities!? There are several boot and message files that are editable but the rest aren't. Hmm.
tia
Sorry that did not work for you - it was worth a try.
Any choice of OS needs to be offered by the bootloader menu. Once you see the choice between save-files it is too late
as the puppy linux kernel will already have loaded.
We each need to find a (dual) boot method that we are comfortable with. Also there is the question of what level of risk we can each tolerate if
things go wrong. Finally there is the matter of complexity. Simple but robust is better.
May I suggest that you study linuxcbon's thread which also mentions two other methods.
http://www.murga-linux.com/puppy/viewtopic.php?t=75257
The method mentioned there by shinobar is the simplest but you have the least control over the install procedure.
linuxcbon's method is next up in the simplicity stakes and you do have manual control.
Lastly another of my methods which is low risk from XP's point of view but intimate knowlege of syslinux/vesamenu.c32/their menu structures/ is desireable
Should you decide to go down any of these routes make sure that you first have good backups/clones of your XP drive(s) and are adept at restoring them.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
How to Dual boot Puppy XP from USB using syslinux & grub4dos
Hi greengeek,
It is far easier to do it in XP. The bootloader and vesamenu.c32 must be > v3.82
First if need be using XP format the stick as FAT32.
Syslinux (4.04 zip) can be downloaded from here:
http://www.kernel.org/pub/linux/utils/boot/syslinux/
How to Create a Bootable USB: Windows XP
STEP 0: Your motherboard (BIOS) has to support boot from usb (usb-key or usb-hdd).
You don't need to know which of these types your media is though, your BIOS recognizes
the usb controller in the device, and this determines usb-key or usb-hdd type.
STEP 1: Download the latest copy of syslinux and extract it. Download.
STEP 2: Open a command prompt and cd to your 'syslinux\win32' folder. Run syslinux.exe -m -a X:
replacing X with the drive letter of your media. This will install suitable MBR code into your flash drive and mark the partition on it as active.
It is far easier to do it in XP. The bootloader and vesamenu.c32 must be > v3.82
First if need be using XP format the stick as FAT32.
Syslinux (4.04 zip) can be downloaded from here:
http://www.kernel.org/pub/linux/utils/boot/syslinux/
How to Create a Bootable USB: Windows XP
STEP 0: Your motherboard (BIOS) has to support boot from usb (usb-key or usb-hdd).
You don't need to know which of these types your media is though, your BIOS recognizes
the usb controller in the device, and this determines usb-key or usb-hdd type.
STEP 1: Download the latest copy of syslinux and extract it. Download.
STEP 2: Open a command prompt and cd to your 'syslinux\win32' folder. Run syslinux.exe -m -a X:
replacing X with the drive letter of your media. This will install suitable MBR code into your flash drive and mark the partition on it as active.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
Hi ETP
Thanks for looking into that. Now i feel that i've highjacked your thread not hitchhiked on it as you have put up so much info that it should be flagged / titled as a dual boot from USB / CD for whoever else might be interested. sorry bout that.
Your last sentence stopped me in my tracks. I'm even worse grubbing at windoz than with Puppy - all worry and no fun! But what you said made me wonder if there might be a solution - to intercept the process at the first or second messages that appear. First is boot.msg which calls up the slacko screen and says
Which is the kernel anyway? The bin files on the cd are boot.cat initrd.gz vmlinuz and the .sfs file. Are these difficult to modify? Well, I guess that's a silly question for a noob to ask!
Thanks for looking into that. Now i feel that i've highjacked your thread not hitchhiked on it as you have put up so much info that it should be flagged / titled as a dual boot from USB / CD for whoever else might be interested. sorry bout that.
Your last sentence stopped me in my tracks. I'm even worse grubbing at windoz than with Puppy - all worry and no fun! But what you said made me wonder if there might be a solution - to intercept the process at the first or second messages that appear. First is boot.msg which calls up the slacko screen and says
Could a choice be added - 'hit F0 to abort Puppy and revert to hard drive'? with a little code to do the deed? Or is this message called up by the kernel? In which case could the cd be remastered to include a separate file to be called first with a new 5 second choice?Just wait 5 seconds for normal startup!07
For basic help press the <F2> key, for advanced help press <F3> key.
Which is the kernel anyway? The bin files on the cd are boot.cat initrd.gz vmlinuz and the .sfs file. Are these difficult to modify? Well, I guess that's a silly question for a noob to ask!
[color=orange]1. Dell Dimension E521, AMD Athln 64, 2 GHz 1.93GB ram,
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Dual boot from cd
Hi canbyte,
Don’t worry about jacking the thread. It was hardly active. From your reply I see that you have grasped the issue and it is evident that you prefer low risk.
Your current method of working with 533 (boot from CD with multiple save-files on USB) is very safe, versatile and sensible.
When one burns a Puppy ISO to CD/DVD, isolinux (a fork of syslinux) is used to boot the disc, isolinux.cfg being the configuration file. A very simple cfg is used in Puppy.
Yes, it would be possible to add a boot option to that file but doing so is fraught with pitfalls in that what would and would not work would be very hardware dependant. It would also have to cater for all O/Ss (Win 98/Win2000/XP/Win7 etc). In addition some O/S may not be on the first hard disc and some not even on the first partition of a particular disc.
The script that generates the cfg is a matter for BK, who wisely in my view, has kept it simple. It would not be good if at best an option only worked on some hardware and at worst locked a box up with possible corruption of the file system.
Having said that there is nothing to prevent an individual, using an ISO editor, from
changing the cfg and re-mastering it. We are back to risk.
Given what you have told me you may like to give the method described in this thread a try using another stick. Once formatted (if need be) and made bootable with syslinux as I have now described, it is simply a matter of creating the directories and copying your files over. You can keep your existing stick as it is. If you copy over multiple save files you will get your usual choice.
Reproduced below is a directory/file shot of such a stick for any readers benefit.
N/B
The hidden file in the root ldlinux.sys does not show up in this view.
Ps the kernel is the file vmlinuz.
Don’t worry about jacking the thread. It was hardly active. From your reply I see that you have grasped the issue and it is evident that you prefer low risk.
Your current method of working with 533 (boot from CD with multiple save-files on USB) is very safe, versatile and sensible.
When one burns a Puppy ISO to CD/DVD, isolinux (a fork of syslinux) is used to boot the disc, isolinux.cfg being the configuration file. A very simple cfg is used in Puppy.
Yes, it would be possible to add a boot option to that file but doing so is fraught with pitfalls in that what would and would not work would be very hardware dependant. It would also have to cater for all O/Ss (Win 98/Win2000/XP/Win7 etc). In addition some O/S may not be on the first hard disc and some not even on the first partition of a particular disc.
The script that generates the cfg is a matter for BK, who wisely in my view, has kept it simple. It would not be good if at best an option only worked on some hardware and at worst locked a box up with possible corruption of the file system.
Having said that there is nothing to prevent an individual, using an ISO editor, from
changing the cfg and re-mastering it. We are back to risk.
Given what you have told me you may like to give the method described in this thread a try using another stick. Once formatted (if need be) and made bootable with syslinux as I have now described, it is simply a matter of creating the directories and copying your files over. You can keep your existing stick as it is. If you copy over multiple save files you will get your usual choice.
Reproduced below is a directory/file shot of such a stick for any readers benefit.
N/B
The hidden file in the root ldlinux.sys does not show up in this view.
Ps the kernel is the file vmlinuz.
- Attachments
-
- screenshot.19.jpg
- (54.62 KiB) Downloaded 1132 times
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
ETP, Thanks for your patience in letting me continue chewing on this bone. I'll recheck later but I don't think my PC is bootable from USB. It occurred to me that what we are dealing with is the bios, which I suppose is what instructed the pc to boot from cd or usb. Is it possible to reverse the bios instruction without having to think about what OS is on the HD? Or can the bios be told that 'sorry but there is no boot os here so you'll have to try the HD or whatever is next on the list'? The same as if there were no puppy cd in the drive. Or are my ruminations on the wrong track?
[color=orange]1. Dell Dimension E521, AMD Athln 64, 2 GHz 1.93GB ram,
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Puppy 533 on CD, accesses flash drive only,
FFox Nightly12.0
2. Compaq P3 733Hz 375RAM
Printer: Oki C3400 > LAN [/color]
Hello ETP
This is a very nice guide and it got me thinking a bit about the power of syslinux.
It actually can be a full replacement bootloader. It can boot and chainload windows os and other loaders.
Here is a snapshot of my current syslinux.cfg on my laptop usb stick (based on your work):
As you can see I put my slacko install in a subfolder as this is an 8 gig stick so I will likely add other os (pups or whatever) to the stick.
Notice the windows entry, this boots straight into windows 7, only the chain.c32 module is added from syslinux. It's not even necessary really as the 1st HD entry boots straight from BIOS. It sends a failed message apparently and the machine starts from scratch without unplugging the usb, yet ignoring it, and as such on this machine boots straight to grub (legacy).
Here is the reference where I stumbled upon the magic: http://reboot.pro/11640/#entry102110
Thanks and cheers.
This is a very nice guide and it got me thinking a bit about the power of syslinux.
It actually can be a full replacement bootloader. It can boot and chainload windows os and other loaders.
Here is a snapshot of my current syslinux.cfg on my laptop usb stick (based on your work):
Code: Select all
PROMPT 0
TIMEOUT 80
DEFAULT /vesamenu.c32
MENU RESOLUTION 1024 768
MENU BACKGROUND /splash/bart9splash.jpg
MENU TITLE Puppy Linux
MENU WIDTH 30
MENU MARGIN 2
MENU ROWS 15
MENU HELPMSGROW 19
MENU TIMEOUTROW 20
MENU TABMSGROW 21
MENU CMDLINEROW 23
MENU HSHIFT 50
MENU VSHIFT 5
menu color screen 37;40 #00000000 #00000000 none
menu color border 30;44 #00000000 #00000000 none
menu color title 1;36;44 #00000000 #00000000 none
menu color unsel 37;44 #ff6a6a6a #00000000 none
menu color hotkey 1;37;44 #ff6a6a6a #00000000 none
menu color sel 7;37;40 #ffffffff #ff6a6a6a none
menu color hotsel 1;7;37;40 #ff808080 #ff6a6a6a none
menu color scrollbar 30;44 #00000000 #00000000 none
menu color tabmsg 31;40 #aaaaaaaa #00000000 none
menu color cmdmark 1;36;40 #ffff0000 #00000000 none
menu color cmdline 37;40 #aaaaaaaa #00000000 none
menu color pwdborder 30;47 #ffff0000 #00000000 std
menu color pwdheader 31;47 #ffff0000 #00000000 std
menu color pwdentry 30;47 #ffff0000 #00000000 std
menu color timeout_msg 37;40 #aaaaaaaa #00000000 none
menu color timeout 1;37;40 #ffaaaaff #00000000 none
menu color help 37;40 #aaaaaa00 #00000000 none
menu color msg07 37;40 #90ffffff #00000000 std
LABEL 5365
MENU LABEL Slacko 5.3.6.5
KERNEL /slacko-beta2PAE/vmlinuz
APPEND initrd=/slacko-beta2PAE/initrd.gz pmedia=usbflash
MENU SEPARATOR
LABEL 5365n
MENU LABEL Slacko 5.3.6.5 RAM
KERNEL /slacko-beta2PAE/vmlinuz
APPEND initrd=/slacko-beta2PAE/initrd.gz pmedia=usbflash pfix=ram
MENU SEPARATOR
LABEL windows
MENU LABEL Windows 7
COM32 chain.c32
APPEND hd1 1 swap
MENU SEPARATOR
LABEL hd
MENU LABEL Boot from 1st HD
localboot -1
Notice the windows entry, this boots straight into windows 7, only the chain.c32 module is added from syslinux. It's not even necessary really as the 1st HD entry boots straight from BIOS. It sends a failed message apparently and the machine starts from scratch without unplugging the usb, yet ignoring it, and as such on this machine boots straight to grub (legacy).
Here is the reference where I stumbled upon the magic: http://reboot.pro/11640/#entry102110
Thanks and cheers.
Puppy Linux Blog - contact me for access
canbyte:
I had to fix an asus laptop the other day.
Dead cd-dvd drive.
Do you think that piece of Vista crap would boot
any of my USB drives.
And I have a heap of them.
Put them in different ports...
selected the drive to boot from....ggggrrrrrrhhhh!!!
Then I thought....why not
Hit >>> F10 after I select the usb >>> in the hard drive to boot
and the monster booted.
Might be worth revisiting it.
Chris.
I had to fix an asus laptop the other day.
Dead cd-dvd drive.
Do you think that piece of Vista crap would boot
any of my USB drives.
And I have a heap of them.
Put them in different ports...
selected the drive to boot from....ggggrrrrrrhhhh!!!
Then I thought....why not
Hit >>> F10 after I select the usb >>> in the hard drive to boot
and the monster booted.
Might be worth revisiting it.
Chris.
You mentioned a wiki tutorial re making the stick bootable with syslinux:
http://www.syslinux.org/wiki/index.php/HowTos and that tutorial mentions (under the section to make bootable usb via Linux) the line:
dd conv=notrunc bs=440 count=1 if=mbr.bin of=/dev/sdX
However, that line specifies bs=440 which seems contrary to other tutorials I have found which specify 446. Do you think 440 is a typo?
http://www.syslinux.org/wiki/index.php/HowTos and that tutorial mentions (under the section to make bootable usb via Linux) the line:
dd conv=notrunc bs=440 count=1 if=mbr.bin of=/dev/sdX
However, that line specifies bs=440 which seems contrary to other tutorials I have found which specify 446. Do you think 440 is a typo?
I think you missed my relevant post: The syslinux wiki leaves a lot to be desired. It is generally out of date and sometimes incorrect.greengeek wrote:You mentioned a wiki tutorial re making the stick bootable with syslinux:
http://www.syslinux.org/wiki/index.php/HowTos and that tutorial mentions (under the section to make bootable usb via Linux) the line:
dd conv=notrunc bs=440 count=1 if=mbr.bin of=/dev/sdX
However, that line specifies bs=440 which seems contrary to other tutorials I have found which specify 446. Do you think 440 is a typo?
Hi greengeek,
It is far easier to do it in XP. The bootloader and vesamenu.c32 must be > v3.82
First if need be using XP format the stick as FAT32.
Syslinux (4.04 zip) can be downloaded from here:
http://www.kernel.org/pub/linux/utils/boot/syslinux/
How to Create a Bootable USB: Windows XP
STEP 0: Your motherboard (BIOS) has to support boot from usb (usb-key or usb-hdd).
You don't need to know which of these types your media is though, your BIOS recognizes
the usb controller in the device, and this determines usb-key or usb-hdd type.
STEP 1: Download the latest copy of syslinux and extract it. Download.
STEP 2: Open a command prompt and cd to your 'syslinux\win32' folder. Run syslinux.exe -m -a X:
replacing X with the drive letter of your media. This will install suitable MBR code into your flash drive and mark the partition on it as active.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
How to Dual boot Puppy XP from USB using syslinux & grub4dos
Hi 01micko,
Thanks for your kind words. I did actually investigate an option for booting Win 7 but not possessing it could not validate it.
The thing that put me off using the syslinux chain.c32 module was this warning on the wiki. (not good for laptops/netbooks)
Windows Vista/Windows 7 chainloading
Windows Vista and Windows 7 refuse to hibernate if it is chainloaded. Instead, you have to chainload Syslinux from Windows BCD. There is no known workaround for this.
Ref: http://www.syslinux.org/wiki/index.php/Common_Problems
Another page http://www.syslinux.org/wiki/index.php/ ... /chain.c32
Gives the following example however:
LABEL boot_part_win7fs
MENU LABEL Boot ntld from GPT partition labelled "win7fs"
COM32 chain.c32
APPEND label=win7fs ntldr=/bootmgr
I concluded therefore that chainloading gub4dos might be the better option for Win7. Not being able to validate such a boot (from USB without installing or changing anything on the C: drive) I proceeded no further.
Given that you liked this method of dual booting you may wish to have a look at this thread:
How to Dual boot Puppy & XP from ANY removable media.
(A simplified Lin`N`Win type method using syslinux & grub4dos)
http://www.murga-linux.com/puppy/viewtopic.php?t=80181
That is my current preferred method but using a 2GB SD card which remains permanently plugged in. Reproduced below is a cfg from a USB stick which combines both methods.
There is also a hidden treat in the SD card method in that if you plug a stick in and reboot the stick becomes the next drive to boot and by selecting XP on either menu you can switch between the menu on the stick and the menu on the card. To revert to normal behaviour i.e. booting off the SD simply dismount the stick, extract it and reboot.
Thanks for your kind words. I did actually investigate an option for booting Win 7 but not possessing it could not validate it.
The thing that put me off using the syslinux chain.c32 module was this warning on the wiki. (not good for laptops/netbooks)
Windows Vista/Windows 7 chainloading
Windows Vista and Windows 7 refuse to hibernate if it is chainloaded. Instead, you have to chainload Syslinux from Windows BCD. There is no known workaround for this.
Ref: http://www.syslinux.org/wiki/index.php/Common_Problems
Another page http://www.syslinux.org/wiki/index.php/ ... /chain.c32
Gives the following example however:
LABEL boot_part_win7fs
MENU LABEL Boot ntld from GPT partition labelled "win7fs"
COM32 chain.c32
APPEND label=win7fs ntldr=/bootmgr
I concluded therefore that chainloading gub4dos might be the better option for Win7. Not being able to validate such a boot (from USB without installing or changing anything on the C: drive) I proceeded no further.
Given that you liked this method of dual booting you may wish to have a look at this thread:
How to Dual boot Puppy & XP from ANY removable media.
(A simplified Lin`N`Win type method using syslinux & grub4dos)
http://www.murga-linux.com/puppy/viewtopic.php?t=80181
That is my current preferred method but using a 2GB SD card which remains permanently plugged in. Reproduced below is a cfg from a USB stick which combines both methods.
There is also a hidden treat in the SD card method in that if you plug a stick in and reboot the stick becomes the next drive to boot and by selecting XP on either menu you can switch between the menu on the stick and the menu on the card. To revert to normal behaviour i.e. booting off the SD simply dismount the stick, extract it and reboot.
Code: Select all
DEFAULT /vesamenu.c32
PROMPT 0
TIMEOUT 120
MENU RESOLUTION 1024 768
MENU BACKGROUND /beaker2.jpg
# MENU BACKGROUND /bart9splash.jpg
# MENU BACKGROUND /puppy.jpg
MENU WIDTH 30
MENU MARGIN 0
MENU ROWS 28
MENU HELPMSGROW 22
MENU TIMEOUTROW 24
MENU TABMSGROW 26
MENU CMDLINEROW 28
MENU HSHIFT 46
MENU VSHIFT 5
menu color screen 37;40 #00000000 #00000000 none
menu color border 30;44 #00000000 #00000000 none
menu color title 1;36;44 #00000000 #00000000 none
# menu color unsel 37;44 #ff6a6a6a #00000000 none
menu color unsel 1;36;44 #fc0000 #00000000 std
menu color hotkey 1;37;44 #ff6a6a6a #00000000 none
menu color sel 7;37;40 #ffffffff #ff6a6a6a none
menu color hotsel 1;7;37;40 #ff808080 #ff6a6a6a none
menu color scrollbar 30;44 #00000000 #00000000 none
menu color tabmsg 31;40 #aaaaaaaa #00000000 none
menu color cmdmark 1;36;40 #ffff0000 #00000000 none
menu color cmdline 37;40 #aaaaaaaa #00000000 none
menu color pwdborder 30;47 #ffff0000 #00000000 std
menu color pwdheader 31;47 #ffff0000 #00000000 std
menu color pwdentry 30;47 #ffff0000 #00000000 std
# menu color timeout_msg 37;40 #aaaaaaaa #00000000 none
menu color timeout_msg 37;40 #fc0000 #00000000 none
menu color timeout 1;37;40 #ffaaaaff #00000000 std
menu color help 37;40 #aaaaaa00 #00000000 none
menu color msg07 37;40 #90ffffff #00000000 std
LABEL 5365USB
MENU LABEL Slacko 5365 USB 17/10/12
KERNEL /p5365/vmlinuz
APPEND initrd=/p5365/initrd.gz pmedia=usbflash pupsfs=sdb1:/p5365/puppy_slacko_5.3.6.5.sfs psubdir=p5365
MENU SEPARATOR
LABEL 5332USB
MENU LABEL Slacko 5332 USB 05/07/12
KERNEL /p5332/vmlinuz
APPEND initrd=/p5332/initrd.gz pmedia=usbflash pupsfs=sdb1:/p5332/puppy_slacko_5.3.3.2.sfs psubdir=p5332
MENU SEPARATOR
LABEL 533USB
MENU LABEL Slacko 533 USB 05/05/12
KERNEL /p533/vmlinuz
APPEND initrd=/p533/initrd.gz pmedia=usbflash pupsfs=sdb1:/p533/puppy_slacko_5.3.3.sfs psubdir=p533
MENU SEPARATOR
LABEL 5332SSD
MENU LABEL Slacko 5332 SSD 07/08/12
KERNEL /p5332/vmlinuz
APPEND initrd=/p5332/initrd.gz pmedia=atahd pupsfs=sda1:/p5332/puppy_slacko_5.3.3.2.sfs pdev1=sda1
MENU SEPARATOR
LABEL 533SSD
MENU LABEL Slacko 533 SSD 14/09/12
KERNEL /p533/vmlinuz
APPEND initrd=/p533/initrd.gz pmedia=atahd pupsfs=sda1:/p533/puppy_slacko_5.3.3.sfs pdev1=sda1
MENU SEPARATOR
LABEL grub
MENU LABEL XP Pro 28/07/12
KERNEL /boot/grub/grub.exe --config-file="map (hd1) (hd0);map (hd0) (hd1);map --hook;chainloader (hd0)+1"
MENU SEPARATOR
LABEL reboot
MENU LABEL Reboot
KERNEL /boot/grub/grub.exe --config-file="reboot"
MENU SEPARATOR
LABEL off
MENU LABEL Power Off
KERNEL /boot/grub/grub.exe --config-file="halt"
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
Re: How to Dual boot Puppy XP from USB using syslinux & grub4dos
Do you think it may be possible to change the "pupsfs=sdx" portion of this syntax to compensate for the drive designation varying from system to system or varying because of other usb devices plugged in at boot time? Is there some other way to define the sfs location that is not fixed in this way?ETP wrote:[You will then need to change the following line in syslinux.cfg to match your set up:
From:
APPEND initrd=/p533/initrd.gz pmedia=usbflash pupsfs=sdb1:/p533/puppy_slacko_5.3.3.sfs psubdir=/p533
To:NOTES:Code: Select all
APPEND initrd=/p533/initrd.gz pmedia=usbflash pupsfs=sdc1:/p533/puppy_slacko_5.3.3t.sfs psubdir=/p533
Your stick is seen as sdc1
How to Dual boot Puppy XP from USB using syslinux & grub4dos
Hi greengeek,
Off the top of my head, if that is causing you a problem, there are 3 things that you
can try.
1. Reduce it to just
2.Reduce it to just
3. Make multiple entries with different append lines (choices on the menu)
Off the top of my head, if that is causing you a problem, there are 3 things that you
can try.
1. Reduce it to just
Code: Select all
APPEND initrd=/p533/initrd.gz pmedia=usbflash
2.Reduce it to just
Code: Select all
APPEND initrd=/p533/initrd.gz pmedia=usbflash psubdir=/p533
3. Make multiple entries with different append lines (choices on the menu)
Code: Select all
APPEND initrd=/p533/initrd.gz pmedia=usbflash pupsfs=sdb1:/p533/puppy_slacko_5.3.3t.sfs psubdir=/p533
APPEND initrd=/p533/initrd.gz pmedia=usbflash pupsfs=sdc1:/p533/puppy_slacko_5.3.3t.sfs psubdir=/p533
APPEND initrd=/p533/initrd.gz pmedia=usbflash pupsfs=sdd1:/p533/puppy_slacko_5.3.3t.sfs psubdir=/p533
APPEND initrd=/p533/initrd.gz pmedia=usbflash pupsfs=sde1:/p533/puppy_slacko_5.3.3t.sfs psubdir=/p533
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
Re: How to Dual boot Puppy XP from USB using syslinux & grub4dos
Thanks ETP, thats all working really well now. I'm using this on an Acer netbook which has an XP install that is purely for work use and must not be fiddled with, so this is a good method to let me switch between XP and puppy. I will see if I can afford to get a really low profile usb stick like a Sandisk Fit or a Lexar Echo ZX - they sit really close to the body and I will be able to leave one in permanently to do the dual booting. (Previously I was plugging in a usb stick only when I was wanting to boot puppy but it is annoying to have to keep taking it on and off my keyring...).ETP wrote: 2.Reduce it to just
Code: Select all
APPEND initrd=/p533/initrd.gz pmedia=usbflash psubdir=/p533
Initially I found that the netbook would not display the background image as the resolution needs to be 1024x600 so I used mtPaint to scale the bartsplash to the right size, then changed the resolution in the syslinux.cfg. All good now.
Thanks for your patience.
(The screen image actually looks way better resolution in real life than this pic suggests...)
- Attachments
-
- Booting on Acer netbook_.JPG
- (29.99 KiB) Downloaded 1485 times
Hi ETP, I noted your comments above about limitations and cautions regarding using such a method with Win 7, and I wondered if you had since experimented with a version for Win7 or seen a similar thread covering that topic elsewhere?
I'm still using the stick I created with your XP/Puppy method daily on my work netbook but have now also had to purchase a Win7 device so wanted to try the same approach. I saw 01mickos post above so might give that a go - but I just wanted to check first if you have further advice in case of any recent update to the method.
I'm still using the stick I created with your XP/Puppy method daily on my work netbook but have now also had to purchase a Win7 device so wanted to try the same approach. I saw 01mickos post above so might give that a go - but I just wanted to check first if you have further advice in case of any recent update to the method.