ok, I'm finally done with the legacy x86 version of the system as you can see on the attached screens. it took me a bit more time than expected, at least testing/putting everything together, but now this should complete full system support for all the pc compatible (x86) architectures along with the previous image. the target audience for this and overall idea with this image remains the same as on the initial post (i.e. a recovery/backup live system oriented toward skilled/seasoned techs) so basically refer there for more info and without further redo for those interested this is how to roll out this from a working Linux machine.
Code: Select all
curl -4s ftp://ftp.fpsclasico.de/livesys86.img.xz|xz -dc|dd of=/dev/mmcblk0 ibs=8192 count=483840 obs=1048576 status=progress
essentially just the same as before only with a different (download) filename. for the rest this time the image is a 4 GB combo legacy bios 16/32 bits system including as well a solid community memory testing tool which was incompatible with UEFI (secure boot) to ensure your (legacy) hardware is still functional.
the 16 bit system is just a good old fashioned dos compatible system (FreeDOS 1.3) which should basically just run on anything since the 8086 provided you have some way to feed the 4 GB image to it. in reality I believe that should just run on pretty much anything. that system can be very handy (required) for legacy pc low level maintenance task like bios/firmware updates/flashes or disks recoveries (norton tools etc) and additionally I also included with it (and tested) the original shareware episodes of doom, heretic and (the original) quake as well as a entire freebie doom clone (boom). being a dos system means that it only require 1 MiB of memory to run (although it can be expanded/extended beyond the 1 MiB limit) and it has 256+ MiB of free space in dos just in case you need to work with some files (bioses/firmwares etc) there.
the 32 bit system is as well a good old fashioned legacy CentOS 7.9.2009 full size KDE 4 desktop Linux live system. I could probably have deployed another more recent fedora build or a custom one but finally I thought that this was probably the most solid option considering that there's already a 64 bit installment and the hardware where this would really run. anyways the setup is the same as on the 64 image and basically just as you can see on the attached screens. the only difference is that this time the desktop is not really (pre)configured as it was a bit messy to deliver it that way. notice that to show up the (classic) desktop you need to enable the "folder view" by entering the desktop configuration (Atl+D, Alt+S) and that due storage constrains you better run your browser in private mode (or get rid of any local internet files storing). the rest of the desktop customizations are probably more of a personal choice (i.e. theme, fonts, shortcuts etc) so just with that you should be good to go. the bare desktop runs bellow 256 MiB of memory use and even while writing this on a full stack browser (firefox) under 512 MiB of memory use. essentially I believe this should run (to some extend) on any 1+ GHz Pemtium/Athlon with at least 1 GiB of memory or compatible/better hardware although obviously finally the in-game performance in such a lowend configuration unless coupled with a solid gpu it might not always be enough for the standard high quality hd provided settings. for the rest needless to say the system comes with the good old fashioned UnFreeZe client pre-installed (besides the pak0.pk3 that you need to put yourself there "somehow") that still requires to setup oss sound before (although this time I included a basic script for that). finally once all setup the one-time free storage space for your work in the system is of around 1 GiB which for a dual live 4 GB system image it was about the maximum attainable.
and that should be it as usual I think that it's not worth to write a "book" about it if somebody do finally try it and have some question/feedback or anything just drop it here. overall I think it turned out pretty good and a very handy addition to have around in case of need. I mean, I've been using this for about the last week in one way or another and it literally turned a 15+ years old hd broken laptop that was just a monitor stand into a fully 2020+ functional system. of course as noted the hd game struggled to even hit 60 fps most of the time, let alone try to "play"/run any multimedia file/project. however for basic recovery/maintenance tasks the system was totally comparable to the rest of the 2015+ stuff I have around so I believe that this is probably one of the last chances for such similar legacy system to be functional and productive by 2020+ standards.
overall I'd say that probably unless you have more than 4 GiB of memory this system is a better option over the 64 bits one so I'd say that basically this should be the recommended (32 bit) image for the Windows XP-7 generation of pc/hardware (i.e. 20-10 years old computers). machines older than XP (i.e. +20 years) would probably do better staying with the provided 16 bit system (FreeDOS) and the shareware games/communities there (which are huge, to be honest, I really got hooked trying those) and machines newer than 7 (i.e. -10 years) are clearly much better suited for the 64 bit image. matter of facts, as noted, trying to run this on such UEFI machines would probably require some tuning (ex. disabling secure boot and enabling legacy support, typically the UEFI compatibility support module, I mean, if that's a option and if that doesn't break anything else. basically not recommended at all) and even so the 32 bit kernel included is not even PAE capable meaning that even on such instances you would be limited to the classic 4 GiB 32 bits memory limit. in few words, I tested it in one such instance and the +4 GiB 64 bit system did really make a difference so this image is probably more intended for such systems bellow that limit.
as a last note remark again that this only cover x86 pc compatible hardware (so far 16, 32 and 64 bit between both images), these images won't run on other kind of computer architectures like arm or ppc for example. hopefully I'll setup at least a arm version which seems to be a lot more mainstream and trendy nowadays (i.e. Chromebooks and similar devices) but that will obviously take quite a few more time. other than that as a hint for Windows user in case somebody wanna try this as well there, it seems you can probably easily get this going there by manually downloading the images link on the commands (ex. livesys64.img.xz
) and then simply uncompress them with 7-zip
and writing the resulting raw images (4/8 GB) into a usb with the Win32 Disk Imager
tool for example and then booting your computer from there.
You do not have the required permissions to view the files attached to this post.