Hi, Trying to install 210 (updated version) using 2 cd's and 2 cdrom drives on an old SONY VAIO PCG-C1VPK.
(1) Drive #1: PCMCIA PCGA-CD51/A
(2) Drive #2: USB Addonics DVD/CD-RW.
Since PCMCIA CDROM ability is turned off in the installer kernel, I'm using the 2nd drive via USB. I was able to get Fedora Core 5 to install using this method since it searches across the devices automagically.
--------------------------------------------------------------------
I'm able to get to the boot text and type:
puppy PMEDIA=usbcd
and my #2 USB drive spins up. Output Text follows:
---------------------------------------------------------------------
mount: /dev/scd0 is write-protected, mounting read-only
...
ERROR, cannot find Puppy on usbcd boot media.
PUPMODE=1 PDEV1=
Exited to initial ramdisk commandline...
/bin/sh: can't access tty; job control turned off
#puppy
---------------------------------------------------------------------
After being dropped out of the installer to the shell:
(1) Did a df and only see /dev/ram0
(2) I mounted & looked at the #2 USB drive:
mount -t auto /dev/scd0 /mnt/tmpfs
and I do see a "pup_210.sfs"
Any suggestions? Thanks! --Ron
210r install using 2 CDROM drives on VAIO PCG-C1VPK
try usb
Why don't you try PMEDIA=usb ?
(You can also open the universal installer script and see whether there is a usbcd entry prescribed there.)
(You can also open the universal installer script and see whether there is a usbcd entry prescribed there.)
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
Thanks, the USB option worked; I was able to get live-boot running.
Now to figure out why my harddrive installation failed. It kept complaining about bad entry inittab.
Because of that, I can't use the original posted dual cd's to work. Puppy seems to look for some saved files off the harddrive. Anybody know what the magical boot line is to *NOT* look for the (I'm guessing) puppy_save.xxx files? (Using fdisk I deleted my new partition and that brought back Puppy's live-boot back, but I don't want to keep doing this.)
Now to figure out why my harddrive installation failed. It kept complaining about bad entry inittab.
Because of that, I can't use the original posted dual cd's to work. Puppy seems to look for some saved files off the harddrive. Anybody know what the magical boot line is to *NOT* look for the (I'm guessing) puppy_save.xxx files? (Using fdisk I deleted my new partition and that brought back Puppy's live-boot back, but I don't want to keep doing this.)
pfix=ram
"puppy pfix=ram" at boot-up should tell Puppy not to look for pup_save.3fs.
When you install to hard disk, your next boot should start from hard disk.
If your hard disk has XP/NTFS, then you should use a frugal/coexist install. Visit http://ph-islands.net/pupinstall/winxp.php for tutorial to understand how it works (though the Universal Installer of Puppy does things for you automatically).
When you install to hard disk, your next boot should start from hard disk.
If your hard disk has XP/NTFS, then you should use a frugal/coexist install. Visit http://ph-islands.net/pupinstall/winxp.php for tutorial to understand how it works (though the Universal Installer of Puppy does things for you automatically).
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
Thanks, I'll give the RAM option a try.
I'm actually installing over an old RH (8.0 ?) install, so I had 3 partitions: boot, root, and swap. When I did the Puppy install, it said it completed. Not sure why it fails to startup correctly. I just kept getting bad entry inittab and it would lockup. My plan is to repartition/formatting the disk and try installing again.
Thanks again!
I'm actually installing over an old RH (8.0 ?) install, so I had 3 partitions: boot, root, and swap. When I did the Puppy install, it said it completed. Not sure why it fails to startup correctly. I just kept getting bad entry inittab and it would lockup. My plan is to repartition/formatting the disk and try installing again.
Thanks again!