been awhile since I've been around puppy, and was interested in something to run on an ibm laptop.
got this laptpop on Saturday 04/12/2010 and started to test today 06/12/2010.
SPECS: (i dont know all of them sorry)
brand: IBM A21M
Video card: 8 meg ATI 2x agp
CPU: Xeon/Celeron 800MHZ
RAM: 128 meg (however only 127 megs register in bios load-out suggesting a 1meg cache or something)
did it
Boot = yes
run off CD = yes
use Xorg = yes
use swap drive = no
boot time to me seemed to be the equivalent of original puppy's 2.14 through to 4.0 ... which even on my faster units in vm or direct was around 1-3 minutes not including network setup times.
hope that helps
John Biles
see other feedback page for other info
Legacy OS (TEENpup) Feedback is it booting?
- john biles
- Posts: 1458
- Joined: Sun 17 Sep 2006, 14:05
- Location: Australia
- Contact:
Hi guys,
I successfully tried Legacy OS on a Compaq Evo, and I was amazed how fast it could run SuperTux !
However, I think it does not shutdown properly...
I'll post the specs later when I'm back home, just for the record.
EDIT :
Here are the specs :
Compaq Evo N1015v
Processor : Mobile AMD Athlon XP 1500+
Memory : 190MB
Graphic card : ATI Radeon Mobility U1
Display : 1024x768x24
Multimedia audio controller : ALi M5451 PCI AC-Link Controller Audio Device
Ethernet controller : Realtek RTL-8139/8139C/8139C+
It boots, runs off CD, use Xorg, and shuts down properly (contrarily to what I said earlier).
I successfully tried Legacy OS on a Compaq Evo, and I was amazed how fast it could run SuperTux !
However, I think it does not shutdown properly...
I'll post the specs later when I'm back home, just for the record.
EDIT :
Here are the specs :
Compaq Evo N1015v
Processor : Mobile AMD Athlon XP 1500+
Memory : 190MB
Graphic card : ATI Radeon Mobility U1
Display : 1024x768x24
Multimedia audio controller : ALi M5451 PCI AC-Link Controller Audio Device
Ethernet controller : Realtek RTL-8139/8139C/8139C+
It boots, runs off CD, use Xorg, and shuts down properly (contrarily to what I said earlier).
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.
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
#
- john biles
- Posts: 1458
- Joined: Sun 17 Sep 2006, 14:05
- Location: Australia
- Contact:
Hello nitehawk,
Always good to hear that someone is getting good use out of it. I'm currently working on improving it more and will release Legacy OS 2 late January early February all going well. If the current Legacy OS runs on yur PC then the new one will to.
I've created a new look for it that's a bit lighter that should hopefully go down well with users.
Always good to hear that someone is getting good use out of it. I'm currently working on improving it more and will release Legacy OS 2 late January early February all going well. If the current Legacy OS runs on yur PC then the new one will to.
I've created a new look for it that's a bit lighter that should hopefully go down well with users.
Legacy OS 2017 has been released.
I installed it to the hard drive and shut down the PC, then It asked me to save the state file and I chose a place to save it.
Then when i rebooted my PC it said grub error 15 and wont go into grub, so effectively the PC is bricked.
When I was installing I choose not to alter the MBR, was that the reason?
Also it complained of a missing file so I dont think it installed properly
Then when i rebooted my PC it said grub error 15 and wont go into grub, so effectively the PC is bricked.
When I was installing I choose not to alter the MBR, was that the reason?
Also it complained of a missing file so I dont think it installed properly
- john biles
- Posts: 1458
- Joined: Sun 17 Sep 2006, 14:05
- Location: Australia
- Contact:
Hello slenkar,
All you should need to do is reboot Legacy OS again running from the Live CD, partition your Hard Drive again with ext2 and 500 Mb's of Swap, run the installer and select install MBR when asked. On shutdown after install do not save any state file or anything else. Upon restart you will be asked to set the screen size etc and your done.
Good Luck!
All you should need to do is reboot Legacy OS again running from the Live CD, partition your Hard Drive again with ext2 and 500 Mb's of Swap, run the installer and select install MBR when asked. On shutdown after install do not save any state file or anything else. Upon restart you will be asked to set the screen size etc and your done.
Good Luck!
Legacy OS 2017 has been released.