I've stuck with Wary 5 though I"ve tried all the alternatives given by a very friendly commuity! It seems the video card is still the problem. It works but scrolls slowly to render any new text/image. When and if I find the correct driver, how will I incorporate this into the system? To the user who looked up my computer - thanks. I will be looking for the driver as time permitts.

Thanks again for the commands to help identify my video card.. It is a Trident Cyberblade /i1 rev 5d. The journey now begins to find any an appropriate driver. I've settled with the Wary 5. None of the other versions recommended helped with my card. So I thought I would start with this community if they know of any sources I could investigate. Video RAM is 8 megs by the way. I like the look of wary as well so I'll dispense with the macpup though I use it with my desktop (as well as Vector Linux)

I don't have a specific answer that will help, but I am in the middle of a similar issue myself so maybe my general info may be of use. There is an interaction between various modules in the video software so it is helpful to have some idea of the complexity before you can reduce it to simple steps.

In my experience it is not just as simple as clicking on the right driver and watching it install. Nor is it as simple as clicking a .pet that supposedly contains the correct driver (you might get lucky, but only if the person who made that .pet shares the identical video card hardware, firmware and linux kernel as you do)

Basically what you have to achieve is this:
1) Locate the manufacturers driver for your video card
2) Work out which kernel you have (type uname -r in a console)
3) Compile the manufacturers driver against your kernel (which may involve temporarily accessing the "devx" kernel that matches what you are using)
4) Load the driver correctly
5) Configure xorg.conf correctly

Apparently the compile steps are not difficult, but the xorg setup can be tricky.

It will become important to have an understanding of how the Xorg server decides which driver is active.

The video driver which is currently in use is specified by the xorg.conf file in the /etc/x11 folder. However, the behaviour of this file is rather problematic in my experience. The file does not always stay the same. There are circumstances under which Xorg will discard the changes you make to the file, and overwrite it.

This can cause endless problems with trying to figure out why your changes don't seem to work.

Also, it is important to remember that Xorg is able to "fallback" to basic settings if it detects that something in the xorg.conf file does not match your hardware. This means that there are at least two modes that will appear to work on your machine - firstly the fallback mode, and secondly the accelerated mode (...and there are various different levels of accleleration too. 2D and 3D accel are achieved by different methods)

There is also a .pet called something like xorg_high (which may be worth a try if you don't want to go the whole compile route just yet). The xorg_high driver is a step up from the fallback driver, but a step below true 3D acceleration based on the full (and correctly compiled) driver from the manufacturer.

The fact that only one Puppy has the correct fallback settings suggests that your video card may be a little "touchy" so it might be tricky to find the driver/xorg.conf combo that works well for you.

I recommend that you keep any important data off this machine until you have finished experimenting with the video as it is likely that you will have to work through a lot of config/reboot/reinstall.

Hopefully you will have time to do some research throughout this forum because there is a large patchwork of valuable info about how Xorg works - it's just that different people know different things depending on what happened with their particular hardware.

I recommend making a copy of the xorg.conf file that you can currently find in /etc/x11. This file will contain the fallback settings and driver name that currently work on your system. It may contain useful info, and in any case you may need to reinstall it at various times during the troubleshooting, or you may want to copy it over to any other puppy that has not succeeded in generating a working xorg.conf

I mentioned searching this forum for info - you may find the search function of this forum difficult to use (I don’t know why it doesn’t give the expected results...), and you may find that a normal google search gets you more specific results (and will also include similar topics from other distros forums...) Also, this modified google search page (specific to Puppy) is rather useful:
http://wellminded.com/puppy/pupsearch.html

At the risk of offering way too much blabber (but in the hope that some of it might help you avoid non-working shortcuts...) here is a bit more info:

I forgot to mention a couple of things:
1) As well as xorg and vesa, there was another option called xfree86. A debian forum post mentions your video card and xfree86 here:
http://www.galeon.com/arturofdezm/confpresario.html
and offers a sample config file here:
http://www.galeon.com/arturofdezm/XF86Config-4
I’m not suggesting that you should use xfree86, but the format of the sample file is very similar to xorg.conf and just might include some parameters that eventually help you.
2) As well as fallback graphics modes, and 2D/3D acceleration, there are other factors that can affect operation of the card: Mesa and DRI (direct rendering) seem to be mentioned quite a bit. I am still confused about whether these can co-exist alongside true acceleration, or are used instead of it, where a correct driver can not be found. (I am still working through similar driver problems on a couple of Toshiba laptops and struggling to unravel the relationship between all these factors)

One thing I know for sure (from lots of trial and error) is that someone elses .pet driver file may have worked well for them but still have a wrong parameter for your system or needs. This seems especially true for the early AGP cards, which came out at a time when there was a high rate of hardware development, and information and software development may not have matured fully. You may have to find a partial answer and finetune it. Anyway, here is a collection of info that might help build the picture.

This webpage is fairly specific about Trident support for your card. I don’t know how exactly this is applicable to Puppy (but someone else will..)
http://linux.die.net/man/4/trident

This post mentions DRI on a cyberblade card. No solution but possibly some config info of interest:
http://www.linuxquestions.org/questions/linux-hardware-18/trident-microsystems-cyberblade-i1-direct-rendering-support-425836/

Forum member “Tempestuous” summary of levels of 2D, 3D and DRI (older relevance but still valuable insight - His comment may sound as if there is no solution but that may not apply to your card, and things may have changed since 2006)
http://www.murga-linux.com/puppy/viewtopic.php?t=10757&start=26

Working cyberblade:
http://www.murga-linux.com/puppy/viewtopic.php?t=30467&sid=19c2c112ff79365b2166f82716f8c550

Sorry if none of this helps. Hopefully we will be able to help you hunt down the answer. There are some excellent techies in the Puppy forum who will be able to offer help in discarding what no longer applies. (Some things have changed since that video card was released - Xorg has changed, Puppy has changed, and newer accelerated cards use a different setup, so some of the older info will be relevant, but not all) . Even if full acceleration is impossible I think you will find an xorg.conf that gives you what you want, and can be ported to other puppies if you decide to change.

I am sure there are many more posts on the puppy forum and others. I suspect you will be able to patchwork a solution that helps. Best of luck!

The PC was completely unemployed for quite a long time - I didn't turn it on a single time during the last 3-4 years and other 3-4 years before that I was using it very rarely. At the time when it was still in active service (1996-2004) the PC was running Windows 95 SR2, which is still installed there but I would like to replace it with Puppy and see what I'll get - I'd like to try this as the last step before I throw the PC away as completely useless (browsing today's web with IE 4.0 preinstalled in Win95 is not funny).

Reading quickly through PuppyLinux websites I learnt that the puppy I should want to install and that could work with my old machine is Wary Puppy. So I downloaded the ISO image of the latest 5.3 WaryPuppy, burnt it to a CD, set the boot sequence in BIOS to "CDROM,C,A" and tried to boot... unfortunately it didn't work - although the BIOS made an attempt to boot from the CD-ROM (it displayed some 2 lines of something like "Booting from CD-ROM"), the attempt wasn't successful (the 3rd line was "Starting Windows 95")... since there is no USB support in the PC, I can't boot Puppy via USB either (actually, there are a few unused pins in the motherboard that its manual claims to be USB but they've never been connected to anything and I don't think they would work because at the time when the motherboard was born USB 1.1 was not yet standardized, not sure about USB 1.0)

To make a long story short, I'm looking for a way to boot Wary Puppy installer from a floppy drive or to use some Windows- or DOS-based installer of Wary Puppy that would allow me to install it to HDD and to use it first alongside and afterwards (if I'm happy with it) instead of current Windows 95. I searched and searched on the website, in forums but I didn't find any information related to booting from floppy

I would like to try some Puppy with my very old computer - Pentium 120, 64 MB RAM, 1.6 GB HDD, S3 Trio 64V+ PCI graphics, TEAC 24x CD-ROM drive, MissMelody-compatible ISA sound card, a PCI network card, Award BIOS (and no USB support).
I downloaded the ISO image of the latest 5.3 WaryPuppy, burnt it to a CD, set the boot sequence in BIOS to "CDROM,C,A" and tried to boot... unfortunately it didn't work - although the BIOS made an attempt to boot from the CD-ROM "Starting Windows 95")

I don't think you need to drop back to a floppy boot. It almost sounds as if the CD drive could not find a valid "image" on the CD. Did you do a "burn as image", rather than as a file? That is a common issue, especially if it the "burn as image" feature is not clearly defined within your burning programmes options. I think your machine only proceeded to boot the W95 because it saw no valid boot data on the CD.

Also, it could have been a bad burn. It is worth re-burning the CD at the lowest speed possible. (The laser gets better dye penetration at lower speeds.)

If you have no joy with Wary, it would probably be worth going back to some of the earlier versions of Puppy. (they were fine-tuned for machines without a lot of power)

Another one that gives good performance on low powered PCs is Gray’s Puppy NOP 431, available here:
http://puppylinuxstuff.meownplanet.net/NOP/puppy-431-NOP.iso (you may need a username of puppy and a password of linux)

you can also yank the harddrive, stick it into a better computer, install puppy there, and then move the harddrive back. Puppy can switch between computers like that. And on really old computers (like yours) sometimes, its better to use a faster CPU/more Ram to get it installed.

Also, look up the process for making a swap partition (or swap file). Both are ways of giving virtual memory to to Ram deficient computers by using your harddrive as virtual ram (its like a paging file in windows). If you can dig up some cheap ram somewhere, that would be best, since your computer is pretty near the bottom of what will run.
(You add a swap partition using the gparted program which is part of puppy linux-- again switching the drive to a faster machine might help to do this).

And take a look at some of the other puppy suggestions in this thread. Wary is a good place to start, but some of the others might have better luck.

Posted: Mon 09 Apr 2012, 03:31 Post subject:
best puppy for a very old computer

Hi eskimo,

I have a similar computer (1997 Windows 95 model) that is still in use today...
Therefore, I am quite certain that you will have to use WakePup as sfeeley suggested to boot Puppy from a floppy disk. Given the age of your computer, I would also suggest an older version of Puppy: Puppy 2.17 which you can get right here or fatfree pup 2.17 as greengeek suggested which is available over here. The reason is that newer Puppies especially Wary Puppy require 256 mb of ram. That said, I also recommend that you shop for some used ram: two sticks of 72 pin EDO ram @ 32 mb each, to hopefully bring you up to the maximum of 128 mb ram that your computer should take... assuming that you have four slots with 32 mb of ram in each slot. Lastly, I recommend that you partition your hard drive to include a swap file of 128 -256 mb of space.

Complete these requirements, and you should be able to resuscitate your old Pentium 1 such that it will perform reasonably well.

Monsie_________________My username is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.

It is the most fully featured tiny iso that I have found and includes a self-installer for the opera browser.

Although the Puppy OS is easily light enough to run on your hardware the main problem you are likely to see is that the internet today requires a lot from the browser, and browsers are memory hogs. Puppy has a wide choice of browsers, and you can go as light or as heavy as you want.

The version of Opera that comes within Meanpuppy is a good start.

As others suggested, the more memory you can fit, the better off you will be.

One of the main benefits puppy offers over W95 is full USB support, but as you have pointed out, that won't bring you any benefit on your motherboard. (Unless maybe you can find a header cable that is compatible with those pins you mentioned...)

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