Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 

The time now is Tue 11 Aug 2020, 06:54
All times are UTC - 4
 Forum index » House Training » HOWTO ( Solutions )
Install basic Puppy on a computer with 16 Mb RAM
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [27 Posts]   Goto page: 1, 2 Next
Author Message

Joined: 09 May 2008
Posts: 908
Location: Moorooka, Queensland

PostPosted: Mon 26 Oct 2009, 09:56    Post subject:  Install basic Puppy on a computer with 16 Mb RAM
Subject description: A case study with an old Toshiba 430CDS laptop. Low ram low-ram loram

Executive Summary:

Most current and emerging Linux versions require at least 64Mb RAM, or double that for satisfactory operation across a range of higher-end internet, gaming and and office applications. The process of "natural" succession tends to have older and still-functional computer hardware consigned straight to the junk heap, particularly those with a maximum capacity of less than 128Mb. Nonetheless, here I outline a procedure for successfully installing a Puppy 4.12 puplet (Pulp 0.03) on a laptop with 16Mb RAM, for its intended end-of-life role as a simple games computer for primary-school children. No previous experience with Linux is neccessary - I'm not a programmer, but a Windows refugee and end-user with just enough curiosity make trouble for myself.

1. Low RAM computers - General observations
It's important to highlight that the amount of RAM available is not the only factor in getting Puppy running happily on 'vintage' computers. CPU speed and health I won't mention further as defects in this department are often fatal as most CPU's can't be replaced on older motherboards without a soldering iron, and this can signal problems elsewhere on the board. Optical and hard drives can be easily replaced with newer components, and should be seriously considered for automatic replacement because:
a) The original 8x CD-ROM etc. drastically impacts on installation time and general operation. (Refer to the first sentence 'nutshell' in this post, and don't try this route.)
b) The symptoms of a dying CD drive are sometimes not easy to spot, and can 'hang' repeated installation attempts at random points, giving the impression that RAM or other hardware may be at fault. Persistent hangs at the "Booting to kernel..." message when installing Puppy and other versions of Linux is a sure indication that the CD drive needs replacing. (cf. nutshell)
c) The original hard drive (HDD) is likely to be a IDE/ATA/PATA vintage with a spindle speed of 5400 RPM, and possibly lacking DMA transfer rates. Drive speed is important - particularly when you require a sizeable linux-swap partition (256MB recommended - but see healthy debate regarding swap-partition size on the forum) to complement the low RAM. Exchanging the original with a faster ATA drive (i.e., 7200 RPM) will markedly improve installation and general operation speeds. Running noise is also reduced. Better still, replacing the old-style drive with a solid-state drive, that is, CF or SD cards in an internal IDE-adaptor will improve running speed, temperature and energy-efficiency.
d) Test the integrity of your HDD before committing it to the project. The "Ultimate Boot CD" (UBCD 4.1.1, with v. 4.1.2 arriving soon for official release) is an invaluable tool for any refurbishment project and is mentioned often in the Puppy forums. Plenty of tools are provided for diagnosing your CPU, motherboard and RAM. Make sure that you use Memtest86+ to assess the quality of your RAM - it is on UBCD, available alone for free download and is also provided stock-standard in many versions of Puppy, so there is no excuse to skip it's use. On UBCD I find MHDD32 particularly useful in diagnosing and "repairing" HDD problems with bad or degrading sectors (i.e., will provide operational workarounds but no HDD can be fully repaired). It's particularly useful when arranging the location of your linux-swap to avoid a swamp of slow sectors on areas of the drive - string-like patterns and well-defined areas of slow sectors are indications that the drive needs replacing.

I formatted my installation partitions in the Ext2 format as I had fatal halts whenever I attempted using Ext3.

2. BIOS, CD issues
Checking that you have the latest BIOS for your motherboard should be performed early in any recycling project. It's not hard to do, although it has moderate risk in that the 'flash' process should never be interrupted.
Regrettably, many early BIOS's - particularly in the Win95 and Win98 era - were designed to the MicroSoft script, including the inability to install straight from CD without the use of a boot floppy. WakePup2 is provided stock-standard in most versions of Puppy and enables detection of Puppy files on non-Linux hard-drive and USB partitions, for installation purposes. "Grubflop" from rcrsn51 is perfect for getting around the BIOS shortcoming and booting a Puppy installation CD - it will also boot the installation CD's of other Linux versions, and diagnostic discs like UBCD without any problem. Anyone who uses Puppy on older computers should have grubflop in their toolbox. http://www.murga-linux.com/puppy/viewtopic.php?t=16950
Older CD-drives require care in the preparation of installation CD's: avoid using RW CD's; multisession CD's; use 'finalized' ISO's burned at the slowest speed you have available on your main or 'everyday' computer. (but cf. nutshell and save trouble)

3. Choosing your OS
A good test of your hardware and the range (and sophistication) of applications available to it is to install operating systems that were more-or-less designed for low RAM environments. These include; Win95, Win98SE given the 'lite' treatment (Win98lite), ReactOS 0.3.10 (not at 16Mb RAM), DeLi 0.8.0, SliTaz 2.0 (loram), TinyCore 2.4.1, Luit Linux 0.4 and Kantonix 2005-04-lite. However, at 64Mb RAM and below, it is likely you will find such distributions too bulky in their attempts to provide all things for all people, and my inclination is to pick a lite Puplet that can be easily modified to perform a restricted range of functions...

4. Choosing and preparing your Puppy version
Understandably, not all hardware can be supported by the latest official version of Puppy Linux in the constant pursuit of support and compatibility for the latest technology (and software demands). “Retro” versions utilize earlier Linux kernels and generally provide better support for earlier hardware. Official “barebones” versions and "fat-free" puplets reduce the number of applications and overall pup_XXX.sfs size, hence improving running efficiency in low-ram machines. “Lite” or “ultra” puplets further reduce operational overheads by minimizing a range of processes concerned with running the X windows environment (e.g., freememapplet, xload, blinky etc). After choosing the specific role for your RAM-challenged computer (e.g., music jukebox, internet access and emailing, games etc.), similar results can be achieved by taking your preferred Puppy or puplet, removing those applications you won’t require manually or automatically with Pet-be-gone, and/or manually reducing your resource “overheads” in the X environment (e.g., see greyhound "puppy" http://www.murga-linux.com/puppy/viewtopic.php?search_id=976194388&t=33652) to "mould" your puppy to the hardware available.

5. Moulding Puppy for 16Mb RAM
I do not recommend installing any Puppy version from a finalized, slow-burned live-cd onto a 16Mb laptop, using its original hardware.
The testbed here was a Toshiba Satellite Pro 430CDS, 120MHz Pentium, 16Mb onboard EDO, 1.3GB -preDMA HDD, 10x CD-ROM, external floppy - no USB, PCMCIA ports unused, no networking features. EDIT: I USED A 256MB LINUX-SWAP PARTITION
While I wouldn't do this again with less than 64Mb RAM, the boot parameters I found most successful were:

puppy pfix=noramsfs,nox,nopcmcia ide=nodma acpi=off apm=on loglevel=7
Instead of noramsfs I used "noram" for earlier versions of puppy where the argument "noramsfs" wasn't provided as an example on the bootup screen. I don't know whether there are fundamental differences in their use, or whether they can be used interchangeably. "pfix=ram" is of course the default option for installations with plenty of RAM.
I used 'nox' to help dig around behind the Xorg chooser, before the startup of X11 to solve some issues with Toshiba Laptop LCD settings that I won't discuss further here. "ide=nodma" for the old hdd without DMA support, the laptop supports APM not ACPI, and the full verbosity provided by "loglevel=7" permits me to diagnose any faults to work around in future installation attempts.

From my experiments with over a dozen or so Pupplets from puppy1 to puppy4, it appeared that for those versions with ISO's larger than 75Mb, waiting time increased exponentially for the X-server to stop loading and the menu to be accessible. If I had to wait over 30 minutes I counted the installation as a failure, although at least once I waited over 24hours for menubar, background and icons to appear before I aborted. From instances where the X-server completed loading, initial attempts to improve response to the mouse actions and keyboard commands were highly, highly frustrating. These chiefly involved killing various background processes, removing the desktop icons and exchanging the background wallpaper for a plain black screen.

Long before this point I considered using a faster desktop machine to pre-load Puppy onto a USB caddy and transferring it straight into the laptop for re-initialization in its final environment, but delayed because I thought it was going to be more difficult than it actually was. I used a small hdd (<4GB, 3.5") recycled from other projects and used it to surrogate a full install of the puppy I wanted to try in the laptop. (I used full installations throughout, not frugal ones due to performance concerns at low RAM levels.) After creating a small 32MB pup_save, I then removed whatever applications not required and remastered the puplet for a live CD copy - as backup and re-installation via the faster desktop, not to the laptop. Then I essentially cloned the desktop drive onto the laptop drive, ensuring that the GRUB settings were correct before I installed it back into the laptop. THIS INSTALLATION ROUTE BYPASSES THE HEAVY DRAIN ON RAM NEEDED AT THE INSTALLATION STAGE, OFTEN RESULTING IN FATAL CRASHES.

To my astonishment, Pulp 0.03 - a derivative based on Puppy 4.12 barebones - not 'retro' - works "out of the box" on a Pentium laptop with only 16Mb RAM. It uses no wallpaper or desktop icons by default, and together with a series of performance 'tweaks' and careful selection of blingless and bloatless applications for improving overall speed in contemporary machines works well in low RAM. I removed the Siag office suite and the typing tutor, and installed some games pets (e.g., XArchon - thanks for that one, MU). I have no need for any graphics-intensive programs here, though will attempt downloaded flash games played via ttuuxx's FirePup 0.4 which is pre-installed in Pulp. It may be best to have any additional games pre-installed while the laptop HDD is still caddied to the faster computer.

NOTE: I used a recycled, 7200 RPM HDD to replace the original drive which struggled badly and actually deteriorated noticeably over one week of installation attempts - as gauged using the MHDD32 software mentioned earlier.

Using the drive transfer method I anticipate similar success using performance optimized, bare-desktop versions of Puppy4, including TurboPup Xtreme (Beta2). It is likely that ChoicePup412RminV2 will also work well in low RAM conditions if given the bare-desktop and "greyhound" treatment in pre-installation. It remains to be seen whether the hardware will tolerate the educational games SFS's posted by sidders on his HSB project. A barescreen, barebones 412 puppy with the suite of HSB sfs' may well provide the best overall solution but gCompris may well be too resource-hungry. http://www.murga-linux.com/puppy/viewtopic.php?t=41454

- As I still have some 'tweaking' left to go regarding Xorg/Xvesa issues on older Toshiba Laptops, this may explain some jumpiness and slow running speed of arcade games such as X-soldier. Fine for everything else, and will also provide a good eBook reader, music player etc.
...I'll still be buying more RAM for it, however.

Many, many thanks to Barry Kauler again for his fabulous take on the Linux OS, and to all in the Puppy community asking questions and to the gurus responding to them - I've used your 'gear' here.
Special thanks also to those who contributed the puplets below -

Versions Tested:
Puppy-1.0.3-FF.2005; SimplePup (1.0.7); Puppy-1.0.8-Mozilla; MicroMuppyOpera, Puppy-109CE-KDE3.5.2, Sea-icepup 1.19.1, [Does anyone have copies of Todd Richardson's LitePup series, or know where I might download them from??] Puppy-214R Remaster, 214X15, GamePup216, Fat-free2.16-Dillo, Fat-free2.17, DCL2008 (301), Fat-free301Xorg, FH301RetroLiteV2, PizzaPup301, SkinnyPup4.0a, Puppy4.12Retro_bb, WolfPup2FF, ChoicePup412RminV2, TuboPup XtremeBeta, Pulp 0.03.
Back to top
View user's profile Send private message Visit poster's website 

Joined: 02 Oct 2007
Posts: 632

PostPosted: Tue 12 Jan 2010, 15:31    Post subject:  

@Puppyt: Have you tried the latest version of Turbopup Xtreme (v1.0 FINAL) ?

It's much lighter than the old Beta you've tried before.

Turbopup Tech Support
Back to top
View user's profile Send private message 

Joined: 18 May 2008
Posts: 4878
Location: Blue Springs, MO

PostPosted: Tue 12 Jan 2010, 18:22    Post subject:  

I have posted a bunch of jwm hacks that will make it a full desktop environment (without the moderately heavy Rox) here:

For browsing - netsurf or dillo2 or a console base browser (links...)

If you have a smaller spare hard drive put it on a SEPARATE ide channel and setup your swap partition on it (of course more RAM is better)

Many versions will work, but you'd need to comment out the auto-started daemons like CUPS, Rox, event manager,... and remove the <Swallow'd applets from /root/.jwmrc or /root/.jwmrc-tray (absvolume, blinky, asapm...) pprocess will tell the tale and pfind will find the culprit script (unless it is in the init script - maybe syslogd and klogd)

Recompiling some of the stuff statically and with unneeded options removed can also help (for instance maybe you don't need jpeg or xpm support in jwm if you convert all icons to png and use a single color background)

Maybe once finished it would be possible to share using something like:
dd -if=/dev/sda1 -of=/mnt/sda2/lite_pup.img  #not sure?

so others could install it using a boot floppy, CD and:
dd -if=/mnt/sda2/lite_pup.img -of=/dev/sda1 #not sure?

... or you could bypass X altogether and use many SDL games on the framebuffer - (DOS flashback method)

Check out my github repositories. I may eventually get around to updating my blogspot.
Back to top
View user's profile Send private message Visit poster's website 

Joined: 09 May 2008
Posts: 908
Location: Moorooka, Queensland

PostPosted: Wed 13 Jan 2010, 03:24    Post subject:
Subject description: Low ram puplets

Thanks for your replies panzerpuppy and technosaurus:-

panzerpuppy, I have been following synth's progress with Turbopup Xtreme and was kinda hoping to test version 1.1 out on the old Toshiba 430CDS. You seem to have inside info on that development - should I just stick to 1.0 instead for such a machine? (I've tested Xtreme 1.0 on my main desktop, and liked what I saw there very much, but haven't had the chance to trot it out on the 430CDS.)

technosaurus, many thanks indeed for the hacks for a ROXless puppy - that thread you started is brimming with tips on reducing running overheads - I hope to give some of those a running when I get a chance in the not-too-distant future..

To All, I acquired a 32MB RAM module secondhand from a Chinese supplier very helpfully suggested by a puppian responding to my post on another thread. However, I haven't had any puplet running on the 430CDS continuously due to improper shutdowns (e.g., my 4yo daughter just loves pressing those buttons), and running fsck on such a machine on a regular basis is, well, pretty fsckd. So given my level of expertise with Linux (where I just keep breaking stuff till it works) the project in on the backburner til I find a decent lump of time to work it through.
What I have found is that until I have found a puplet (native or suitably hacked) that will shutdown cleanly on such hardware, operational performance will tend to degrade on successive bootups - SilverPuppy's brilliant resource here on his "Make Puppy recover automatically from improper shutdowns" thread here http://www.murga-linux.com/puppy/viewtopic.php?t=47668 backgrounds the issue well.

Sorry that I haven't properly updated the project as quite a few people seem curious about running Puppy on such limited hardware resources, and the update is overdue. I was kinda hoping that ttuuxx might have put the blowtorch to his 214X series and had a version Big-bassified for a Fat-free release... such a beast might run sweet on sub-64 Mb RAM behemoths... Not to be (anytime soon) so a revisit of the versions listed earlier (plus Murga's MeanPuppy, TurboPup Xtreme 1.0) on 48 Ram, ext3 etc plus experiments outlined by SilverPuppy and technosaurus and their contributers is warranted. Could you wait a fortnight please?

Cheers All
Back to top
View user's profile Send private message Visit poster's website 

Joined: 24 Jun 2006
Posts: 140
Location: Imperial Warmongering Dystopia of Amerika

PostPosted: Sat 16 Jan 2010, 03:06    Post subject:  

The older cd drives can often be 'restored' to
normal operation by using a lens cleaning disk
to remove dust accumulation from the laser
optical unit. Insert it into the drive and let
it automatically do its chores.

Or, if the optical unit is accessible for manual
cleaning, a Q tip very slightly moistened with
isopropyl (rubbing) alcohol may be used to
very gently remove dust/debris from the lens.

As long as the cd drive is able to 'read' some
portion of a cd before cleaning, there is a good
possibility that it will come back to 'life.'

The optical unit is very delicate so very gentle
handling is a necessity.
Back to top
View user's profile Send private message 

Joined: 09 May 2008
Posts: 908
Location: Moorooka, Queensland

PostPosted: Sun 24 Jan 2010, 23:53    Post subject:  

Cheers Hugh - those are great tips. (And I hope you're over your 'flu)
I forgot to mention too that a loosely-fitted IDE cable between the motherboard and the CD can also run you into trouble at the "Booting the kernel" stage. (But more often than not your CD simply will not be picked up at boot.) The plastic connections tend to wear over time. Also check the cable itself - sharp creases, pinpricks in the cable can often be the cause of many mysterious ailments in ye-olde-worlde-charm computer.
Back to top
View user's profile Send private message Visit poster's website 

Joined: 04 Oct 2005
Posts: 5547
Location: GB

PostPosted: Sat 02 Oct 2010, 12:29    Post subject:  

We did the no-shutdown feature to death many times. For certain chipsets there is no answer just a work-around with acpi set to <force> or one of the alternative settings.
As for old CD drives, I've seen hundreds of DOA s and not a single one could ever be resurrected by cleaning the lens - it's an urban myth. Even cleaning the disc rarely works - it's usually a fault in the inter layer(s).
Also beware of 'rubbing alcohol' which is usually denatured plain old ethanol, but might contain lanolin as well! If you are contemplating chemical cleaners, you need to source them from a laboratory (supplier) in at least Analar grade or better and apply it with clinically clean swabs. There's clean & 'pure', then there's chemical clean & pure, and finally bacteriostatic reagents. If you don't understand these terms check in with your local university chemistry department or clean-room fab (which will be operated by chemists*)...

[*Brits take heed: a chemist is rarely a pharmacist; different breed in the UK.]
Back to top
View user's profile Send private message 

Joined: 18 May 2008
Posts: 4878
Location: Blue Springs, MO

PostPosted: Mon 04 Oct 2010, 17:20    Post subject:  

One thing I didn't mention was the size of the mandatory processes. To reduce the memory requirements I supplemented these binaries with minimal static uclibc versions... for instance - I compiled additional busybox implementations using the uclibc capable compilers at http://www.impactlinux.com/aboriginal
make allnoconfig
make menuconfig
>select only one applet (getty is a good example)
>>exit & save

(if you are only doing 1 applet you can just rename busybox to your applet name... NOTE that recent developments in busybox have complicated this a bit, because if the "full" busybox has the applet, then the internal one gets called - which can be an issue if busybox ash is the shell that execs the command - to prevent this behavior busybox-full must be either configured without the applet or the, enabled-by-default, "prefer applets" feature disabled)

Most of this is in the PupNgo thread already, so look there for pets, scripts and techniques. I have had jwm running in Xvesa with <16mb in pupngo but if you set up a swap file/partition and use a full install you should be able to still run other apps, however slowly

Check out my github repositories. I may eventually get around to updating my blogspot.
Back to top
View user's profile Send private message Visit poster's website 

Joined: 13 Sep 2006
Posts: 62
Location: New Hampshire USA

PostPosted: Sun 09 Jan 2011, 16:39    Post subject:  

Congrats to all you minimalists! I'll just mention that a 2011 HDD or CD drive may be wasted on old hardware. The CPU and drive controller may not be able to see the whole thing or keep up with the transfer rate anyway, and may even freak out at the new stuff. For really old machines you can often find giveaway drives that will boost performance to as high as it is ever going to go. 1998 drives can do wonders for a 1992 machine!-)
Back to top
View user's profile Send private message 

Joined: 09 May 2008
Posts: 908
Location: Moorooka, Queensland

PostPosted: Fri 21 Jan 2011, 13:31    Post subject:  

Alas - a confessional...

The nub is I have had to relent and leave Puppy for FreeDOS on the smaller of the two machines - many thanks to the suggestions of various other puppians (including hondasid, author of Uhuru Puppy).
With no real surprise I found that hardware of this vintage is perfectly geared for the mountains of DOS "abandonware" lurking on the 'net - providing acceptably challenging entertainment and educational value for my early Primary-school-aged kids. PERHAPS a DOSBox-dedicated pUPnGO would be OK on this machine - I tried goingnuts' latest version (pUPnGO_V412_200110.iso; see http://www.murga-linux.com/puppy/viewtopic.php?t=51478) and while I had fun - especially online with the text web-browser - household rioting nearly ensued. I didn't have the time or the nous to continue with that Puppy avenue further, but I really liked where pUPnGO was taking me on that old beast.

I had concentrated on getting the smaller Toshiba 430CDS Satellite Pro up and running (now 32MB RAM with original 1.2GB hdd formatted to Ext2, 128MB swap - unlike its bigger brother 'maxed out' at 48MB RAM). I was pleasantly surprised that pUPnGO booted and could install straight from the PCMCIA CD-ROM, but again rcrsn51's grub floppy was vital. For other puplets (as listed in the OP) it was still a case to best load Puppy onto the laptop's harddrive while it was connected to a newer computer. Most regrettably, I couldn't maintain a kid-friendly/foolproof Puppy working reliably on the smaller machine. That is, not a puplet that would also provide the range of resource-friendly entertainment as the old DOS software.
I used the drive diagnostic tool MHDD (from within UBCD) and it revealed the tragic 'track marks' of failing sectors in the last 15% of the hard drive - tell-tale signs of years of abuse from Windows disk-threshing. Even using Gparted to "cut off" the dodgy tail by leaving it unused as an unformatted partition didn't provide the consistency I was expecting, although complete crashes were less likely. I suspect very much to be able to remove a range of performance glitches by ditching the old drive for a solid-state hard-drive (SD or CF) with an IDE adapter - but I don't have one spare. However as hayden mentioned earlier, there is only so much that might be gained from mixing technologies from such disparate 'eras'. Nonetheless, even given the vintage motherboard and CPU, it may well benefit from an IDE adapter for two CF cards - with one dedicated for swap, as technosaurus suggested earlier.

After a VERY torturous journey, I eventually settled on the mix of FreeDOS 1.0 (with the latest JEMM memory expander), the child-friendly GUI of Ronald Blankendaal's "Access" arranged to open automatically from the boot-up http://surf.to/AccessDosMenu, and for occasional 'housekeeping' duties use the file manager provided in DosStart http://www.icdc.com/~dnice/dosstart.html - rather than use OpenGEM or SEAL2. I'm using the entire drive formatted to FAT16, and crashes are extremely rare.

For more advanced users on such hardware, an embedded Puppy like pUPnGO could meet a range of requirements although I think at present, it is possible but not probable for children's entertainment. And not perhaps with the economy of DOS - though goingnuts, technosaurus and other collaborators certainly are working to that end.

Apologies that I haven't responded sooner - apparently there's been a glitch with automated notifications regarding comments on this thread.

Search engines for Puppy
http://puppylinux.us/psearch.html; Google Custom Search; http://wellminded.net63.net/ others TBA...
Back to top
View user's profile Send private message Visit poster's website 

Joined: 07 Dec 2008
Posts: 927

PostPosted: Sat 22 Jan 2011, 15:13    Post subject:  

Puppyt: Thank you for a really impressive report on your trials! You mention that you did test pUPnGO version pUPnGO_V412_200110. You might have fun testing the latest version (pUPnGO_V412_041210.iso) as a lot happened: The CLI (and core part) is totally separated from the GUI part - and also everything in CLI is build as static bins. This means that you can load different GUI parts - one is included on the download iso-image but two other is offered: Xwoaf (very tiny using ulibc) and bl3. Especially the bl3-dress might be worth trying as it should be able to boot to GUI in 16Mb ram. It can use Slackware 4 packages so there are a lot of expansion possibilities. Attached a screen-shoot of pUPnGO running the bl3-dress loaded as sfs-file after boot to prompt. If you have the time to test some day I could do a pUPnGO-bl3-iso for you...
 Filesize   26.75 KB
 Viewed   4671 Time(s)


Back to top
View user's profile Send private message Visit poster's website 

Joined: 09 May 2008
Posts: 908
Location: Moorooka, Queensland

PostPosted: Sat 22 Jan 2011, 21:38    Post subject:  

Hi goingnuts,
I beg your pardon - it was actually pUPnGO_V412_041210.iso that I tested, but in the confusion of waterlogged days recently at my end and release dates I erred in haste. I enjoyed ivansampa's little youtube video and downloaded and installed about 5th Jan. I had a fab but limited time playing with it, but that is feedback best left on your thread...

I've actually run way overtime on my muddled-headed computer-testing for the time being, but thankyou very much indeed for your kind offer for a bl3 version of your puplet. Thanks too for pointing out the Slackware compatibility - if I was to stick to your pUPnGO ethos of a single-role, embedded system - would it be feasible to run a DosBox package (e.g., http://connie.slackware.com/~alien/slackbuilds/dosbox/pkg/) from within pUPnGO - what sort of advantages might you get over using a straight DOS version when running ye olde software? And if pUPnGo was to act as a DosBox 'server', perhaps via to the Dos 'flashback' method technosaurus hints at earlier in this thread, or busybox applet (I have only a rough sense of what he means in these respects), could a X-like gui be eliminated to reduce overheads further? Though on second thought a graphical file manager within Puppy would be preferable to the FreeDOS offerings I've butted my head against recently.
...And what I'm seeing very clearly now is the points I originally listed in the first post are really championed in your pUPnGO thread, and I really should be directing my questions there!

Many Thanks

P.S. I reckon I owe it to the Puppy Community to get a 44-pin (laptop) IDE CF or SD adapter (with ports for 2 cards to follow technosaurus' suggestion) and revisit the issue of Puppy4's and below on a sub 48MB machine...

Search engines for Puppy
http://puppylinux.us/psearch.html; Google Custom Search; http://wellminded.net63.net/ others TBA...
Back to top
View user's profile Send private message Visit poster's website 

Joined: 26 Nov 2010
Posts: 63

PostPosted: Tue 13 Sep 2011, 11:42    Post subject:  


The original Norton Commander (which has been cloned many times) might be a good choice for file management in FreeDOS. Let me know if you want a copy.


It's always easy when you know how!
Back to top
View user's profile Send private message 

Joined: 09 Nov 2011
Posts: 1

PostPosted: Fri 11 Nov 2011, 10:56    Post subject:    

I know I'm posting on here a tad late, but I had absolutely, positively NO IDEA that puppy linux could be posted on that slow of a computer. Am I reading this right? 16 MB (not GB's) of RAM? The reason I'm shocked is because I'm wanting to install a separate partition on an older computer. . .for no particular reason, actually. Honestly, I'm just wanting to experiment with other OS's and laptop platforms (old and new) and thought this might be interesting. I found an old Compaq Armada at a rummage sale. Now THAT'S old school. Although, when it comes to new laptops, I certainly wouldn't be going to rummage sales. . .more like a retail -- y'know, places like hhgregg or something.

Anyway...with any luck, these tips will work. Thanks for allowing me to chime in and thanks for the trips. Smile

I do not regret one moment of my life.
Lillie Langtry

Last edited by BeefyCat on Sat 12 Nov 2011, 04:33; edited 1 time in total
Back to top
View user's profile Send private message 

Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Fri 11 Nov 2011, 13:07    Post subject:  

Puppyt, thank you for the information about puppy running on low ram computer like that.
I have an old computer with 40 Mhz processor, 3 Mb RAM (three MB RAM) and 40 MB HDD. It has a network card.
It has only floppy drive but I can connect CD-Rom and I can put about 500 Mb HDD as well.
At the moment it works with MSDos 6.2 and Windows 3.1 and it takes about 30 MB from 40 MB hard drive.
Does anybody have any idea if there is a chance to make some puppy work on that computer? Rolling Eyes

Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
Display posts from previous:   Sort by:   
Page 1 of 2 [27 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » HOWTO ( Solutions )
Jump to:  

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

Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1320s ][ Queries: 12 (0.0443s) ][ GZIP on ]