(no title)
sockbot | 27 days ago
The two main problems I ran into were 1) software support at the application layer, and 2) video driver support. There is a herculean effort on the part of package maintainers to build software for distros, and no one has been building 32 bit version of software for years, even if it is possible to build from source. There is only a very limited set of software you can use, even CLI software because so many things are built with 64 bit dependencies. Secondly, old video card drivers are being dropped from the kernel. This means all you have is basic VGA "safe-mode" level support, which isn't even fast enough to play an MPEG2. My final try was to install Debian 5, which was period correct and had support for my hardware, but the live CDs of the the time were not hybrid so the ISO could not boot from USB. I didn't have a burner so I finally gave up.
So I think these types of projects are fun for a proof of concept, but unfortunately are never going to give life to old computers.
tombert|27 days ago
It baffles me how usable Office 97 still. I was playing with it recently in a VM to see if it worked as well as I remembered, and it was amazing how packed with features it is considering it's nearing on thirty. There's no accounting for taste but I prefer the old Office UI to the ribbon, there's a boatload of formatting options for Word, there's 3D Word Art that hits me right in the nostalgia, Excel 97 is still very powerful and supports pretty much every feature I use regularly. It's obviously snappy on modern hardware, but I think it was snappy even in 1998.
I'm sure people can enumerate here on the newer features that have come in later editions, and I certainly do not want to diminish your experience if you find all the new stuff useful, but I was just remarkably impressed how much cool stuff was in packed into the software.
flomo|27 days ago
(edit to say I'm obviously ignoring i8n etc.)
MrGilbert|27 days ago
With memory prices skyrocketing, I wonder if we will see a freeze in computer hardware requirements for software. Maybe it's time to optimize again.
blackhaz|27 days ago
justapassenger|27 days ago
mikepurvis|27 days ago
It's really astonishing how full-featured it all was, and it was running on those Pentium machines that had a "turbo" button to switch between 33 and 66 MHz and just a few MBs of RAM.
lproven|26 days ago
With the small caveat that I only use Word, it runs perfectly in WINE and has done for over a decade. I use it on 64-bit Ubuntu, and it runs very well: it's also possible to install the 3 service releases that MS put out, and the app runs very quickly even on hardware that is 15+ years old.
The service packs are a good idea. They improve stability, and make export to legacy formats work.
WINE works better than a VM: it takes less memory, there's no VM startup/shutdown time, and host integration is better: e.g. host filesystem access and bidirectional cut and paste.
deafpolygon|27 days ago
goalieca|27 days ago
It definitely was snappy. I used it on school computers that were Pentium (1?) with about as much RAM as my current L2 cache (16MB). Dirty rectangles and win32 primitives. Very responsive. It also came with VB6 where you could write your own interpreted code very easily to do all kinds of stuff.
rkagerer|27 days ago
nunobrito|24 days ago
Still remember it was possible to perfectly mimick existing documents that had long stopped being printed with such a quality in replication.
The introduction of ribbons was a cruel mistake. It gets harder and harder to know where anything is located nowadays because ribbons hide options too often.
dfex|27 days ago
I am now starting to wonder how much of it has to do with network access to Sharepoint and telemetry data that most likely didn't exist in the Office 97 dial-up era.
Features-wise - I doubt there is a single feature I use (deliberately) today in Excel or Word that wasn't available in Office 97.
I'd happily suffer Clippy over Co-Pilot.
pjmlp|27 days ago
boznz|26 days ago
jama211|26 days ago
nxobject|27 days ago
Truly, I do not miss the swamp of toolbar icons without any labels. I don't weep for the old interface.
jsdevrulethewr|27 days ago
Nope, that’s a modern problem. That’s what happens when the js-inmates run the asylum. We get shitty bloated software and 8300 copies of a browser running garage applications written by garbage developers.
I can’t wait to see what LLMs do with that being the bulk of their training.
Exciting!
dariosalvi78|27 days ago
zokier|27 days ago
That seems odd? Debian 12 Bullseye (oldstable) has fully supported i386 port. I would expect it to run reasonably well on late 32 bit era systems (Pentium4/AthlonXP)
jabl|27 days ago
But otherwise, yes, Debian 12 should work fine as you say. Not so long ago I installed it on an old Pentium M laptop I had lying around. Did take some tweaking, turned out that the wifi card didn't support WPA2/3 mixed mode which I had configured on my AP, so I had to downgrade security for the experiment. But video was hopeless, it couldn't even play 144p videos on youtube without stuttering. Maybe the video card (some Intel thing, used the i915 driver) didn't have HW decoding for whatever video encoder youtube uses nowadays (AV1?), or whatever.
amne|27 days ago
genewitch|24 days ago
[1] My first broadband connection was in 1998 at 768/768 kbit symmetrical. My first megabit speed connection was in 2006 or 2007. in 2010 or 2011 we got VDSL and it was 16 whole megabits. Now i have 300mbit on a good day, and 150mbit on a bad day.
I literally wrote the guide on how to use old hardware with VM tech to route your house, first with ipcop[2], then generically[3], and just this week i wrote a guide on how to get ipv6 working with starlink and dd-wrt[4].
i've been in this a long time.
[2]https://web.archive.org/web/20220323223325/https://www.dslre...
[3]https://web.archive.org/web/20131214075417/https://www.dslre...
and the dd-wrt starlink one from this week:
[4]https://nextcloud.projectftm.com/index.php/s/4iScqZbrfYiNcKy
ETA: it is hilarious how much pushback i got about doing all of this in a VM, just scant years before "you should just use a VM for that" became the default answer, and a decade before "just put it in a k8s cluster and pay someone a quarter million a year to babysit it" became a thing...
also ipcop booted and installed off a single floppy forever
1313ed01|27 days ago
Alternatively you may have accidently built a great machine for installing FreeDOS to run old DOS games/applications. It does install from USB, but needs BIOS so can't run it on modern PC hardware.
iberator|27 days ago
littlecranky67|27 days ago
anthk|27 days ago
leidenfrost|27 days ago
It can boot from a floppy or from a CD drive, and it lets you chainload into a live usb even on old computers.
I used it to boot from CD from a floppy in an old Pentium MMX and it worked great (although slow, of course)
endgame|27 days ago
2b3a51|27 days ago
My first thought: How about using a current computer to run qemu then mounting the Lenny iso as an image and installing to a qemu hard drive? Then dd the hard drive image to your 32bit target. (That might need access to a hard drive caddy depending on how you can boot the 32bit target machine, so a 'hardware regress' I suppose).
My second thought: If target machine is bootable from a more recent live linux, try a debootstrap install of a minimal Lenny with networking (assuming you can connect target machine to a network, I'm guessing with a cable rather than wifi). Reboot and install more software as required.
wink|27 days ago
forinti|27 days ago
My biggest obstacles are that it doesn't have an ethernet port and that it doesn't have BIOS USB support (although it does have a card with two USB ports).
I've managed to run some small Linux distros on it (I'll definitely try this one), but, you're right, I haven't really found anything useful to run on it.
dosk|24 days ago
I have P1 90mhz P2 500mhz and typing from P4 just now :P
I think biggest limit will be missing SSE2 PAE POPCNT modern distros need this
unknown|24 days ago
[deleted]
fuzzfactor|24 days ago
Start with a conventional MBR and active FAT32 partition, and make sure it will boot to MS-DOS, this only requires the 3 DOS OS files to be present when the bootsector is a DOS bootsector (which seeks IO.SYS).
Once that's done, then (optionally) copy the DOS bootsector to a file on that FAT32 volume, name the (512 byte) file BOOTSECT.DOS. A disk editor can do this, or carefully use dd in Linux.
I then boot to Windows and use its CLI to run SYSLINUX.EXE (v6.03 on virgin media), to "Syslinux" (verb) the FAT32 volume. You can alternatively do this from Linux. This replaces the DOS bootsector with a Syslinux bootsector that will seek a Syslinux folder instead of seeking IO.SYS. Also writes ldlinux.sys and ldlinux.c32 to the FAT volume.
You do have to be consistent with your Syslinux version, the .C32 files in use must be from the same version of Syslinux that you use to "Syslinux" the FAT volume. And must match the version of Isolinux used to make the ISO. To find out which version of Isolinux was originally used on the ISO, open the ISO in a disk editor and these have big sectors but about the third sector down will be some readable text with the Isolinux version number.
Then copy all the files & folders from the mounted ISO to the FAT volume, change the name of the isolinux folder to syslinux, in the syslinux folder change the name of isolinux.cfg to syslinux.cfg.
A properly prepared distro distributed in ISO form should then boot normally the way it is intended when stored on a FAT filesystem instead.
Show-stoppers can still arise when some live distros have .CFG bootstrings within their Isolinux folder that specify CDROM or other hardcoded deficiencies, for USB you can sometimes specify REMOVABLE after you change the foldername to Syslinux. You can also specify a chosen volume in case it's not picked up by default.
You may need to look at every .CFG file in the Syslinux folder, they are all usually linked, ideally there is only syslinux.cfg but some people make it more complicated than that. Back them up before editing but they are just text files.
mrighele|27 days ago
I expect at least the base system (including X) to work without big issues (if your hardware is supported), for extra packages you may need a bit of luck.
[1] https://www.openbsd.org/plat.html
[2] https://wiki.netbsd.org/ports/
[3] https://wiki.netbsd.org/ports/i386/
1vuio0pswjnm7|26 days ago
This statement must be Linux-only
Pre-compiled packages for i386 are still available for all versions of NetBSD including the current one
I still compile software for i386 from pkgsrc
https://ftp.netbsd.org/pub/pkgsrc/current/
NB. I'm not interested in graphical software, I prefer VGA textmode
svilen_dobrev|27 days ago
iberator|27 days ago
Don't lose hope. You can boot it one way or other :)
M95D|27 days ago
https://youpibouh.thefreecat.org/loadlin/
anthk|27 days ago
b00ty4breakfast|26 days ago
Little known fact; before 2006 all we did was play Pong and make beep-boop noises on our computers.