best puppy for very old computer

Booting, installing, newbie
Message
Author
Dewbie

#21 Post by Dewbie »


User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

Re: looking for driver

#22 Post by greengeek »

rkonrad wrote:The journey now begins to find any an appropriate driver
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

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#23 Post by greengeek »

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 ... rt-425836/

ubuntu cyberblade issue with sample working xorg
http://ubuntuforums.org/showthread.php?t=1698729

Linux forum that mentions a solution for a similar card and offers an xorg.conf
http://www.linuxformat.com/forums/viewtopic.php?p=93917

Debian forum with major bitching session, but some good indepth comments about xorg etc
http://forums.debian.net/viewtopic.php?f=10&t=51558

Tip re copying a working xorg.conf (on Tecra 8200 with diff Trident, but still useful background and a sample grafted xorg.conf)
http://208.109.22.214/puppy/viewtopic.php?
p=34944&sid=16d38df046f91bd007bf36b186086464

Older murga post re 3D centre and cyberblade:
http://www.murga-linux.com/puppy/viewtopic.php?t=10757

Forum member “Tempestuous

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#24 Post by greengeek »

.
Any chance of posting the contents of your xorg.conf file that is in the /etc/x11 folder?

It will give us a starting point to see if you are using vesa fallback or the Trident driver at the moment.

eskimo
Posts: 3
Joined: Sun 08 Apr 2012, 16:58

Installing Puppy via floppy-boot

#25 Post by eskimo »

Hi,

I apologize if I'm adding my question to a wrong thread but I haven't found anything more suitable (was looking for a topic named "best puppy for very very very old computer" without success :-)

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).

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 :-(

Could somebody please help me with this? Thanks in advance!

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

Re: Installing Puppy via floppy-boot

#26 Post by greengeek »

eskimo wrote: 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)

I’d recommend downloading the 4.3.1 iso available here:
http://ftp.nluug.nl/ftp/pub/os/Linux/di ... ppy-4.3.1/

and also downloading fatfree pup 2.17 here:
http://www.fileswap.com/dl/PBz6SgIf6J/p ... p-2.17.iso

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

Keen to hear how it goes.

sfeeley
Posts: 812
Joined: Sun 14 Feb 2010, 16:34

#27 Post by sfeeley »

@eskimo
To make a long story short, I'm looking for a way to boot Wary Puppy installer from a floppy drive
If you can boot the CD on another computer (that has a floppy drive), you can go to
menu --> setup --> wakepup

which creates a boot floppy that will convince your other older computer to read the CD drive.
http://www.puppylinux.com/hard-puppy.htm
(scroll down for the description of wakepup)

You might also look up the lin-n-win installation method, which uses windows to install puppy.
http://www.icpug.org.uk/national/linnwin/contents.htm

There are also programs that do the lin-n-win automatically (I've not used but here's the thread)
http://208.109.22.214/puppy/viewtopic.p ... efc6d0c503

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.

User avatar
Monsie
Posts: 631
Joined: Thu 01 Dec 2011, 07:37
Location: Kamloops BC Canada

best puppy for a very old computer

#28 Post by Monsie »

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 [u]username[/u] is pronounced: "mun-see". Derived from my surname, it was my nickname throughout high school.

Dewbie

#29 Post by Dewbie »

Monsie wrote:
The reason is that newer Puppies especially Wary Puppy require 256 mb of ram.
For frugal installation, that is:
http://puppylinux.org/main/Manual-English.htm#Manual05

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

Re: Installing Puppy via floppy-boot

#30 Post by greengeek »

eskimo wrote: ...(browsing today's web with IE 4.0 preinstalled in Win95 is not funny).
...at the time when the motherboard was born USB 1.1 was not yet standardized, not sure about USB 1.0)
Yes, these are the biggest limitations. It will be interesting to see what benefits Puppy gives you on this hardware.

Another Puppy that is worth trying on hardware like this is MeanPuppy (developed by John Murga, who runs this forum), available here:

http://www.my-plan.org/storage/puppyLinux/
(The iso will be titled puppy-2.02-opera)

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...)

eskimo
Posts: 3
Joined: Sun 08 Apr 2012, 16:58

#31 Post by eskimo »

Hi again,

thanks to everybody for their help and advice... I read through all of them and tried some of them and I was (partly) successful in the end.

First I burnt a new bootable CD with WaryPuppy 5.3 at 16x (got a good-quality Verbatim CD-RW medium for that - previously I had used a cheap noname CD-R) and tried booting the old machine from it - without success. The only difference when compared with the previous CD was a different message preceding the "Starting Windows 95" one - now it was "Boot from ATAPI CD-ROM: Failure..." whereas before it said "Boot from ATAPI CD-ROM: 1.FD (some unreadable characters) SystemType-00".

Then, as a second step, I attempted to boot my newer machine (AMD Athlon 2500XP) from the Wary Puppy 5.3 CD-RW - the OS launched without any problems so I could put aside the option that something's wrong with the CD - the problem was clearly caused by the fact that the old machine was incapable of booting from a CD-ROM (although its BIOS claims that it should be able to do it). Therefore I tried to create a WakePup2 bootable floppy - and here I came upon something which might be a bug in WaryPuppy 5.3 (but it can as well be just that I did something wrongly) - after choosing Menu/Setup/WakePup I got a message saying that WakePup was not installed and that I should install it via PET install (or what was the name of the installation tool). So I downloaded and installed a package named "wakepup2-20070919" (there were no other wakepups available), the installer said that all was OK but when I chose Menu/Setup/WakePup nothing at all happened. I tried uninstalling the WakePup, downloading it again from a different mirror, but the result was the same...

Since I suspected that the problem with wakepup2 could be that - being built in 2007 - it was no longer compatible with the recent WaryPuppy 5.3, I erased the CD-RW and re-burnt it with pup-431.iso. And it turned out that my suspicion might be right because this time after installing wakepup2-20070919 I was finally able to create a bootable floppy. And the floppy boot worked with my old PC. Moreover, it worked for both 4.3.1 Puppy and WaryPuppy 5.3 (I still kept the first cheap CD-R with Wary).

Yet I can't quite say that I'm too satisfied with the result because the full boot took 5-10 minutes (I hope, though, that after I'll properly install some Puppy to the HDD the startup won't take so long anymore) and I came across other difficulties - e.g. serial mouse didn't work (fortunately I found working the PS/2 mouse socket in the old PC that I had always thought had never worked) and Puppy couldn't find the sound card installed in the PC (I would think that this is a result of the card being ISA some manual configuration/tweaking could be needed). I also found strange that the Puppy launched in console and I had to manually type "startx" to get to the GUI (could be that the installer wanted to indicate to me that way that X wouldn't work with such old machine - it worked, though). But what surprised me most was that I didn't find 4.3.1 Puppy any quicker than its 5.3 Wary brother. So perhaps I should look for something older than 4.3.1 ? Maybe I'll try the fatfree 2.17 next(?) Or the MeanPuppy?

Now I think I'm gonna put this Puppy experiment of mine aside for a while and I'll return to it sometime later... but of course, if any ideas that you think might be useful for me come to your mind in the meantime, please write them down here for me... Thanks!

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#32 Post by greengeek »

eskimo wrote: Now I think I'm gonna put this Puppy experiment of mine aside for a while and I'll return to it sometime later... but of course, if any ideas that you think might be useful for me come to your mind in the meantime, please write them down here for me... Thanks!
Hey, nice work. Very detailed feedback. I think you are right that an install would greatly improve speed. If you come back to the project I'd probably still give the MeanPup a try. Some of the older, more lightweight stuff was optimised for lower memory machines.

Dewbie

#33 Post by Dewbie »

eskimo wrote:
(got a good-quality Verbatim CD-RW medium for that - previously I had used a cheap noname CD-R)
Don't pay too much attention to the brand name on the package.
If you use Puppy's built-in Pburn, it shows who actually manufactured it.
Yet I can't quite say that I'm too satisfied with the result because the full boot took 5-10 minutes
Wary 5.1.1 k2.6.30.5 (the 4.3.1 kernel) boots quickly on my old Compaq Deskpro P2 / 350 / 320 MB RAM.
I tried it today on a Dell Dimension P4 / 2.2 / 1.5G RAM, and booting is unbelievably slow.
(Edit: It might be because the Dell has a CD-ROM and the Compaq has a CD burner, which apparently operates at a higher speed.)
Last edited by Dewbie on Wed 13 Jun 2012, 20:34, edited 1 time in total.

Dewbie

#34 Post by Dewbie »

greengeek wrote:
Some of the older, more lightweight stuff was optimised for lower memory machines.
http://www.murga-linux.com/puppy/viewtopic.php?t=65544

sfeeley
Posts: 812
Joined: Sun 14 Feb 2010, 16:34

#35 Post by sfeeley »

I hope, though, that after I'll properly install some Puppy to the HDD the startup won't take so long anymore
definitely will. Puppy tries to load as much from the CD into ram at boot. On a slow CD Rom on a slow computer this can take a lot of time. But will be much faster from HD.

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#36 Post by Burn_IT »

That 5-10 minutes is a very long time.
My guess would be that it was struggling to read the CD. Either the CD is "dirty" or, more likely, the reader in that machine is iffy. There could be dust/dirt on the lenses or it may be so old it is struggling to read the narrower tracks on a new CD.
Often, if an old machine won't read a CD, you can get round it by WRITING another CD at just 4x rather than at a higher speed.
"Just think of it as leaving early to avoid the rush" - T Pratchett

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#37 Post by greengeek »

eskimo wrote:First I burnt a new bootable CD with WaryPuppy 5.3 at 16x
Burn_IT wrote:...or it may be so old it is struggling to read the narrower tracks on a new CD. if an old machine won't read a CD, you can get round it by WRITING another CD at just 4x rather than at a higher speed
I had a lot of problems with reading CDRs on older machines till I dropped to 4x burning. Burning at 16x does seem too fast and if your burner supports 4x that is definitely the way to go. Any drive that reads it still has the option of reading at high speed if it can manage it without errors. Didn't know about the narrower tracks. I wonder when they started doing that?

I also think faster burns can increase the number of "buffer underrun glitches" that get written to a CDR when the system speed can't keep up with the rate of date transfer during burning. Old drives don't seem to like what the underrun technology does to the CD track.

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#38 Post by Burn_IT »

The narrower tracks are a result of using higher speed lasers to write the disk. In order to be able to read/write at higher speeds the laser has to be focussed more tightly so that the errors caused by "leakage" from the adjacent track is minimised.
"Just think of it as leaving early to avoid the rush" - T Pratchett

eskimo
Posts: 3
Joined: Sun 08 Apr 2012, 16:58

the story continues...

#39 Post by eskimo »

Hi,

yesterday I found some time to play with my very old PC and Puppy again. First I tried downloading the MeanPup iso recommended by greengeek - burnt it to a mini-CD-RW at 4x (I found it rather difficult to get a CD-R that would accept as low a burning speed as 4x) and tried booting from the CD in the old PC. No luck - I'm beginning to think that booting from any CD is simply impossible with that machine.

So my next step was of course the WakePup floppy. Unfortunately, this didn't work either - the wakepup floppy I had created with Puppy 4.3.1 the previous week couldn't find MeanPup on the CD and boot it :-( I had hoped that it was enough to have a single WakePup floppy that can then be used to boot any Puppy from the CD (I thought so since I was able to boot WaryPuppy 5.3 with WakePup floppy created by Puppy 4.3.1). Do you think creating another WakePup floppy directly in MeanPup could help me to get over this?

Anyway, finding the floppy boot incompatible with MeanPup, I returned to WaryPuppy 5.3 and tried experimenting with that. I partitioned my HDD following the manual in puppylinux.org (I found "GParted" a very nice tool, btw.) and then performed a full installation of Wary Puppy to the HDD (/dev/sda2). I also installed the GRUB boot manager to be able to boot either Win95 or WaryPuppy (btw. I wondered - what is the difference between GRUB and GRUBDOS and which one is better?)

I was anxious to see how quick the HDD-boot of WaryPuppy would be when compared with the 5-10 mins long WakePup+CD live boot... and I found out that it was definitely quicker, although the boot behaviour was pretty strange - after choosing "Puppy Linux" from the GRUB boot menu, "Starting up..." was displayed for almost exactly 1.5 mins and during that time the computer seemed to be waiting for something (but there was no HDD activity or anything like that). Then, suddenly, the booting resumed (or started) pretty quickly and it took no more than another 1.5 mins until WaryPuppy was completely booted. Well, now I don't know what causes the 1.5 mins lag - should I blame GRUB or WaryPuppy for it? I would think that something might be wrong with GRUB config but I've no idea what it could be (and then, Windows 95 boot without any delay when selected from GRUB).

The performance of WaryPuppy itself was not as slow as I had been afraid of, however, when I tried to launch the SeaMonkey browser, the whole system hanged and only hard reboot helped (well, here I blame myself for this because I answered Yes to the question whether to install Adobe Flash Player - perhaps I shouldn't have done that - unfortunately, now I don't know how to get rid of it to see whether it causes the hang or if it is the SeaMonkey browser itself)...

The thing, which upset me most, was that WaryPuppy somehow couldn't cope with my ES1868 sound card - immediately after installation it didn't discover any sound cards. So I tried the ALSA Sound Wizard, which discovered the card - in the list there was the item "es18xx: ESS ES 1868 Plug and Play AudioDrive" (which is exactly the sound card I have) three times, then there was "legacy: Probe: legacy ISA (non-PnP) chips" once and two more items that were irrelevant (something with USB and with Apple). I tried selecting and installing the driver for each of the three "es18xx" items one after another but none of them worked (the wizard always said that the driver was successfully installed and that I can play sample.wav but in the end no sound could be heard). Then I tried choosing the "legacy ISA (non-PnP)" option - although the card is declared as PnP - selecting all compatible options offered - two ESS's, SoundBlaster and SoundBlaster Pro (the documentation of the sound card says it's 100% compatible with both SB and SBPro) - and choosing "Yes" to the question of trying all possible combinations of IRQ/DMA - the wizard ended with "Not Found" message. The sound card itself can't be broken because in Win95 it plays OK. Searching this forum I've found a description of a similar problem here: http://murga-linux.com/puppy/viewtopic. ... 43&t=32774 - it's not exactly the same thing because the sound card there is ES1888 whereas I have ES1868 but indicates that ESS sound cards are something that Puppy is not a good friend of. According to the post, the only solution seems to be hacking "modprob.conf" - only I don't know how I should hack it. Any good advice on this, please?

I'm happy at least with the fact that I managed to get a serial mouse working with Puppy, because the old motherboard in the PC appears to be fighting with a PS2 mouse (every now and then it stops working). But I've been wondering - is there a way how to set the mouse to serial _before_ the X-Window starts? It is not easy to start the mouse wizard in X-Window just with keyboard (tried navigating with Tab-key like in MS Windows but wasn't successful).

OK, I see I've written too much already... I think I'll get back to Puppy again the next weekend - looking fwd to your comments in the meantime :-)

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#40 Post by jemimah »

The hang was almost certainly because you ran out of RAM. Have you created a swap partition? You're probably going to want a much lighter browser like dillo.

Post Reply