Here are some of my TEENpup boot experiences.
Runs from CD very well.
Runs in VBox (Raw disc access) from within msWin. Also boots from grub4dos at machine startup.
Using swap drive in VBox (2GB) and a swapfile (100KB) for actual-box.
Running msWin in ntfs partiton and GNU/linux on ext3 partition.
I do love frugal installs. This puppy likes full better. I'd rather not switch back. Makes a mess of my partition
As for booting Puppy 431 and this simply put sda instead of hda in 321's stanza.
Worked on my (now dead) XP/Mint/Puppy431/TeenPup/NOP/TinyCore box.
Old things break down & die. I will too one day.
Maybe full install into a directory (co-exist mode) is worth trying after all?
Booting from HD using nooby's tip from MinHund root=/dev/ram0 along with with acpi=off.
This avoids kernel panic about VFS and the "ERROR, cannot find Puppy on..." errors.
I noyiced this...
There is a splitting, or forking, of the `path' during boot which depends on whether cd is in tray or nay. Odd behaviour.
===========================================
Without CD in tray:
Mounting /dev/hda2 on (/initrd)/mnt/dev_ro1...
Creating tmpfs for pup_214.sfs on (/initrd)/mnt/tmpfs...
Copying pup_214.sfs to tmpfs..._
Very slow in virtual machine. Three minutes and I can wait no longer!
Only a few seconds at this stage on actual machine (Dell Dimension 4500s; P4 1.79 GHz, 1.12 GB RAM).
===========================================
With CD in tray:
Mounting /dev/hda2 on (/initrd)/mnt/dev_save...
Mntg pup_214.sfs directly off /dev/hda2 onto (/initrd)/pup_ro2...
Mounting pup_save.2fs on pup_rw...
Creating unionfs on (/initrd)/pup_new (to become '/')...
Then rc.init runs. Very fast. VBox: 60 seconds from grub to theme music.
Its faster on actual system.
VM has only 512 MB RAM and a virtual swap drive (a file) and must share CPU cycles.
===========================================
Too bad window does not resize as Puppy 4.31 or lucid does in VM.
Must change to Xorg for physical machine and Xvesa for VBox. Otherwise screen resolution is bad. Odd.
The disc/no-disc boot differentiation occurs after kernel booted as removing disc at this time causes `no disc' behavior.
For safety boot.ini has GNU/linux as default boot option. We don't want msWin meeting itself!
The "Default Boot" option below passes control back to msWin's boot.ini.
Code: Select all
# Grub boot menu
#
color green/black yellow/black
timeout=13
default=1
#
title Default Boot (WinXP)
rootnoverify (hd0,0)
chainloader +1
boot
#
title TinyCore 3.3
rootnoverify (hd0,1)
kernel /TC/bzImage vga=771 xvesa=800x600x24 norestore home=hda2 tce=hda2
initrd /TC/tinycore.gz
#
title TEENpup
rootnoverify (hd0,1)
kernel /vmlinuz root=/dev/ram0 acpi=off pmedia=atahd
# kernel /vmlinuz root=/dev/hda2 ro acpi=off pmedia=atahd or idehd
initrd /initrd.gz
#