Was reading about this and wondering if someone has used it and what their impressions are?
http://puppylinux.org/wikka/Pup4DOS
Pup4DOS
I went as far as downloading it, and I don't see why it shouldn't work.
(I can't test it at the moment though, because I have a SATA/NTFS/WinXP machine and you don't get more puppy-hostile then that
)
However this reminded me of how I used to multi-boot slackware from the native DOS boot menu (which is not the same thing as the Win98 boot menu that you get by pressing F8 at boot). To activate the DOS menu you just edit config.sys and autoexec.bat (better save a copy first, just in case).
The same technique should work with Puppy (I didn't try it yet because of SATA, blah, blah, whine, whine
), and the advantage is that you can set puppy as the default OS, and don't have to boot Win first and then restart in DOS mode - just reboot the machine and choose from the menu, or wait for the default choice. Basically it is like having a poor man's Lilo or Grub.
my CONFIG.SYS:
----------------------------------------------------------------------------
rem multiple boot menu
rem config.sys
[menu]
menuitem=puppy, boot Puppy Linux with tiny
menuitem=slack, boot Slackware with loadlin
menuitem=win98, boot Win98
menudefault=puppy, 20
[common]
rem this is the stuff that gets executed anyway
rem it could be moved in the win98 section
files=60
buffers=60
[puppy]
rem we don't need anything special here
rem autoexec wil kick in and call the boot loader.
[slack]
rem ditto
[win98]
rem old config.sys commands here
device=C:\CDROMDRV.SYS /D:CD001
...
my AUTOEXEC.BAT:
----------------------------------------------------------------------------
rem AUTOEXEC.BAT
rem the labels must be named like the menuitem entries
rem common commands go here
goto %config%
:puppy
tiny.exe c:\vmlinuz c:\image.gz @puppy.cfg
goto END
:slack
c:\loadlin\linux.bat
goto END
:win98
rem all the commands in the old autoexec.bat should go here
keyb it
mscdex /d:cd001
....
goto END
:END
---------------------------------------------------------------------------
Now, if I only could find the code of the "installer" I wrote for zipslack...
(I can't test it at the moment though, because I have a SATA/NTFS/WinXP machine and you don't get more puppy-hostile then that
)However this reminded me of how I used to multi-boot slackware from the native DOS boot menu (which is not the same thing as the Win98 boot menu that you get by pressing F8 at boot). To activate the DOS menu you just edit config.sys and autoexec.bat (better save a copy first, just in case).
The same technique should work with Puppy (I didn't try it yet because of SATA, blah, blah, whine, whine
), and the advantage is that you can set puppy as the default OS, and don't have to boot Win first and then restart in DOS mode - just reboot the machine and choose from the menu, or wait for the default choice. Basically it is like having a poor man's Lilo or Grub.my CONFIG.SYS:
----------------------------------------------------------------------------
rem multiple boot menu
rem config.sys
[menu]
menuitem=puppy, boot Puppy Linux with tiny
menuitem=slack, boot Slackware with loadlin
menuitem=win98, boot Win98
menudefault=puppy, 20
[common]
rem this is the stuff that gets executed anyway
rem it could be moved in the win98 section
files=60
buffers=60
[puppy]
rem we don't need anything special here
rem autoexec wil kick in and call the boot loader.
[slack]
rem ditto
[win98]
rem old config.sys commands here
device=C:\CDROMDRV.SYS /D:CD001
...
my AUTOEXEC.BAT:
----------------------------------------------------------------------------
rem AUTOEXEC.BAT
rem the labels must be named like the menuitem entries
rem common commands go here
goto %config%
:puppy
tiny.exe c:\vmlinuz c:\image.gz @puppy.cfg
goto END
:slack
c:\loadlin\linux.bat
goto END
:win98
rem all the commands in the old autoexec.bat should go here
keyb it
mscdex /d:cd001
....
goto END
:END
---------------------------------------------------------------------------
Now, if I only could find the code of the "installer" I wrote for zipslack...
OK. I found the answer for you. After looking at Barry's page on how Puppy works, I added the following to the Puppy boot parameters wiki page:
ramdisk_size:
This may be needed by people who have remastered Puppy 1.x. The kernel is configured with a 12288K maximum ramdisk, and image.gz once expanded has to fit into this. If bigger, the boot parameter "ramdisk_size=" has to be used to specify a suitable size to hold all of image.gz (uncompressed) plus some spare space. For example: ramdisk_size=15360 would result in a 15360K maximum ramdisk.
ramdisk_size:
This may be needed by people who have remastered Puppy 1.x. The kernel is configured with a 12288K maximum ramdisk, and image.gz once expanded has to fit into this. If bigger, the boot parameter "ramdisk_size=" has to be used to specify a suitable size to hold all of image.gz (uncompressed) plus some spare space. For example: ramdisk_size=15360 would result in a 15360K maximum ramdisk.