I failed to install 1.0.4 as well as 1.0.3 type 2 install on a P1 166 MHZ w/ 40 MB RAM, although I ad the partitions hda1 1,5 GB linux native and hda2 128 MB linux swap set up beforehand. this very machine is now running DSL 1.4 without probs. Any clues? Do I have to bypass the Ramdisk which is apparently too small? What am I doing wrong? Any help appreciated to wake up another unwakable _________________www.weiss-lampertheim.de
built and maintained with Puppy!

I failed to install 1.0.4 as well as 1.0.3 type 2 install on a P1 166 MHZ w/ 40 MB RAM, although I ad the partitions hda1 1,5 GB linux native and hda2 128 MB linux swap set up beforehand. this very machine is now running DSL 1.4 without probs. Any clues? Do I have to bypass the Ramdisk which is apparently too small? What am I doing wrong? Any help appreciated to wake up another unwakable

You say it failed to install a type 2? In order to get to the point where you were ready to install a type 2, this indicates to me that Puppy booted successfully and was running. Is this correct?

You didn't state with any specificity what happens when you run the hd installation script. What happens?

1. Press 2 (v.1.03) or 3 (v.1.04) at boot-time so puppy will not use your pre-existing partitions. If asked later about what home partition to use, press ENTER (no partition identified).

2. In console, manually format your swap partition "mkswap /dev/hda2" and turn it on "swapon /dev/hda2", then reboot the Puppy CD so you will have more memory the next time Puppy loads, and the entire usr_cram.fs will be loaded to memory. This will allow you to eject/reinsert the CD (as the install script expects you to do that - see below).

***If you did (2), this may not happen anymore: When the install script asks for the Puppy CD, it may want to eject the CD first, but you can't do that because of insufficient memory. Check the "install-hd2.sh" near the "ripfromcd" command about this possible problem. (The "ripfromcd" function itself is in "installfuncs" script.) remove any such line about ejecting the CD. (You may have to copy the scripts to /tmp to change them.)***

See the link below for more discussion and comments. Good luck._________________Puppy user since Oct 2004. Want FreeOffice? Get the sfs (English only).

thanks guys. yes, I wasn't even able to boot the cd, so I never got to the point of starting a type 2 install ...
thought puppy would use the swap partition hda2 automatically in case it exists and RAM's too low ..._________________www.weiss-lampertheim.de
built and maintained with Puppy!

thanks guys. yes, I wasn't even able to boot the cd, so I never got to the point of starting a type 2 install ...
thought puppy would use the swap partition hda2 automatically in case it exists and RAM's too low ...

You thought right. Puppy should recognize and use swap the partition automatically. This is irrregardless of amount of RAM you have.

I've observed Puppy's behavior as follows:

It automatically uses the swap partition on a boot from CD-ROM and an Option 1 HD install.

It needs to be told to use the swap partition after you made the Option 2 install. And it needs to be told every time you boot. You generally do this by putting the command in /etc/rc.d/rc.local

thanks again guys. the md5 were alright as i used these same cds successfully on other machines. bruce, i wasn't even able to boot from the cd ..._________________www.weiss-lampertheim.de
built and maintained with Puppy!

maybe i wasn't clear. i couldn't even boot the cd due what i thought of lack of RAM so i figured there might be a way to do a type 2 install without booting up the whole system._________________www.weiss-lampertheim.de
built and maintained with Puppy!

There is a way (in the possible future) to make an option 2 install without a bootable cdrom, without a cdrom and for that matter without puppy.

I've been working on this on and off for some days now. The problems I have has to do with working out documentation for others and distribution.

The documentation is the hardest part because I have to figure the person reading may not know much about computers. Truthfully, documentation is overwhelming for me, although the procedure is straight forward and easy for those adept and partitioning drives and working in DOS.

Here's a sketch of how it works.

I install Puppy on a 1gb ext2 partition. I make a compressed image of that partition using DOS based free software called savepart.

The size of the image is about 80 MB

Using SAVEPART and working in DOS this image file can then be installed on an existing partition of between about 150MB and 1GB in size

You use grub for dos to boot it and there you have it.

The entire install is done in DOS and is very fast and doesn't requre much RAM or processor power.

The chances are I will not complete the project because it would involve so many step-by-step instructions for the novice.

It might be feasible to make it availabe for those who know what they are doing and I can simply outline what to do, rather than explain it all in detail.

------------

Anyway, I understand a your situation a little better. I don't know why the CD-ROM disk doesn't boot. But, I will say that I've seen a lot more complaints of this nature with RW disks as opposed to write once disks.

I can take on that job, Bruce, just post the process and the file somewhere.

Germanpup, as Bruce said, a CD start uses the swap partition automatically, so you can in fact load the Puppy from CD. What may be preventing you is the CD drive. Old CD drives may not be able to read newly burned CDs, esp CD-RWs - try a slowly-burned CD-R, say 2X or 4X._________________Puppy user since Oct 2004. Want FreeOffice? Get the sfs (English only).

Bruce, that's interesting. I would too like to participate in that kind of work! The only thing that bugs me is the DOS workaround. Wouldn't it be easier to "backup" the whole puppy filesystem (may it reside in Ramdisk, pup001-Files or wherever) to an image then "restore" it to any ext2 or ext3 or whatever linux partition? In case you still want / have to use DOS why not integrate it into the bootdisk generated by puppy install? Should be enough space on it ...
anyhow I'm wondering if this could also be achieved using linux onboard tools maybe from within puppy ... do you see a way I could get a hold of this image file of yours?_________________www.weiss-lampertheim.de
built and maintained with Puppy!

Bruce, that's interesting. I would too like to participate in that kind of work! The only thing that bugs me is the DOS workaround. Wouldn't it be easier to "backup" the whole puppy filesystem (may it reside in Ramdisk, pup001-Files or wherever) to an image then "restore" it to any ext2 or ext3 or whatever linux partition? In case you still want / have to use DOS why not integrate it into the bootdisk generated by puppy install? Should be enough space on it ...
anyhow I'm wondering if this could also be achieved using linux onboard tools maybe from within puppy ... do you see a way I could get a hold of this image file of yours?

SAVEPART is DOS based, free and very good, therfore the need for DOS. It there is no DOS, SAVEPART can be put on a DOS bootable floppy and run from there. The main idea is here the software - not the OS.

Almost all low end and low ram computers can boot DOS and run SAVEPART. If you don't have DOS, it can be run from a DOS bootable floppy. If you don't have a floppy it can be run from a DOS bootable CD-ROM. If you don't have a floppy or a bootable CD-DRIVE, it can be run from DOS off the hardrive.

SAVEPART saves and restores partitions (among other things). In Puppy Option 2 the entire filesystem resides on a partiton. So you do save the entire filesystem by saving the partition.

As far as filesystem choice. Puppy formats an ext2 prior to the Option 2 install. I don't know if we have choice.

The problem is, after making the Puppy partition with SAVEPART the MBR does not necessarily have the GRUB or any other bootloader program except for the default of what was there. You probably won't be able to boot Puppy without a program designed for the job. You need something to boot it and that is where GRUB for DOS makes it easy.

Once booted, Puppy can be used to install GRUB on the MBR.

You want to make and restore the entire partiton from Linux? I think System Rescue CD has provisions for this. This could be tested.

The consideration I have is this: If you can boot System Rescue CD, you could probably boot Puppy from CD. If you can boot Puppy successfully, then use its hard drive installation program.

just checked out savepart, looks promising. Along come other tools as diskinfo, fileinfo and partinfo which all would fit easily on the DOS-based puppy bootdisk. Fine so far. Let's say you had an image of puppy on CDROM and that kind of bootdisk (modified with a menue of course for install purposes, that's the easy part) then the question remains how would you create an ext2 and a linux swap partition from DOS? Maybe it'll be necessary to create a minimalist console based puppy bootdisk with just sh and fdisk? Or are there any tools out there to create linux partitions from DOS? Anyway I'm eager to get that going. Another point of course is: if you can't boot the puppy cd how will you be able to create the image that savepart is going to use? As far as we got from here you would still need a running puppy type 2 install as well as at least the puppy cd and a cd writer in order to create that image. I have the slight feeling that a script to produce such an image from a(ny) puppy cd couldn't be that hard as all the filesystem is there ..._________________www.weiss-lampertheim.de
built and maintained with Puppy!

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum