• cryomancer20x6@lemmy.sdf.org
      link
      fedilink
      arrow-up
      4
      ·
      3 years ago

      Discovering that game as a child is how I learned to code BASIC. I would change all kinds of values to make the game act crazy, colors, etc.

    • DosDude@retrolemmy.com
      link
      fedilink
      arrow-up
      0
      ·
      3 years ago

      I agree, but Windows 3.x was more a shell on top of MSDOS and had a more niche market, and windows 95 didn’t get most popular OS until late 1998. So for a lot of people that was way before windows. Also tech went a lot faster back then. Updates to an old system isn’t as important if it’s not connected to the world of online hackers.

        • DavidGA@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          3 years ago

          This is a common misconception, and it’s funny that people still believe it all these years later.

          While it’s true that Windows 95 relied on MS-DOS for bootstrapping and provided a DOS-like interface for running legacy applications, it wasn’t “just a shell” on top of DOS. Windows 95 introduced a 32-bit multitasking environment, a completely new user interface, and a separate set of APIs for software development (Win32). It had its own kernel that provided services like memory management and hardware abstraction, separate from DOS.

          The integration with DOS was mainly for backward compatibility, allowing users to run older software. But once you were in the Windows 95 environment, DOS was essentially sidelined, and Windows 95’s own features and architecture took over.

          • Karl Baron@bitbang.social
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            3 years ago

            Exactly, here’s the canonical The Old New Thing post on the topic. https://devblogs.microsoft.com/oldnewthing/20071224-00/?p=24063

            tldr:
            “MS-DOS served two purposes in Windows 95: It served as the boot loader. It acted as the 16-bit legacy device driver layer.”

            “Among other things those drivers did was “suck the brains out of MS-DOS,” transfer all that state to the 32-bit file system manager, and then shut off MS-DOS.”

  • vettnerk@lemmy.ml
    link
    fedilink
    arrow-up
    23
    ·
    edit-2
    3 years ago

    Drivespace was what enabled me to play Baldurs Gate 1 back in the day. My specs back then:

    • 32MB RAM
    • Pentium166 MMX
    • 500ish MB drive (My 2GB went bust, so I used an old spare drive for quite a while)
    • 16X CDROM
    • 2X CD Burner… yarr, that made me a lot of money
    • 3dFX Voodoo2 8MB coupled with an ATI Rage Pro
    • Soundblaster Live
  • Piranha Phish@lemmy.world
    link
    fedilink
    arrow-up
    14
    ·
    edit-2
    3 years ago

    I used the proprietary predecessor, Stacker.

    It was pretty magical. It turned my 40 MB hard drive into a (seemingly) 80 MB hard drive.

    I don’t remember there being a significant performance penalty, because it was presumably overshadowed by the relatively (compared to processor speed) slow disk speeds.

  • th_in_gs@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    7
    ·
    3 years ago

    The idea is still around! Apple’s APFS file system (and HFS+in its later days) support sort-of transparent compression, and on all its platforms most system files - the ones that don’t change much - are compressed to save space for user files. There’s surprisingly little documentation about this.

    There’s a third party tool you can use to compress files yourself: https://github.com/RJVB/afsctool

    It looks like the technical details are in this pdf: https://developer.apple.com/support/downloads/Apple-File-System-Reference.pdf

    • cmnybo@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      8
      ·
      3 years ago

      Btrfs has compression as well. It compressed my root partition to a third of it’s size. It helps out with some games as well, but they usually are not as compressible. The performance impact is pretty minimal as long as you don’t set the compression level excessively high.

  • Decipher0771@lemmy.ca
    link
    fedilink
    arrow-up
    4
    ·
    3 years ago

    Stacker, then MS ripped off Stacker and made Doublespace, got sued and changed the compression algorithm and renamed it DriveSpace.

    Couldn’t use DoubleSpace or Stacker with Windows 3.X, there was no 32bit driver so disk access was horrendously slow. Windows95 was needed to use DriveSpace with full driver support, but it was still slow and by that time hard drives had caught up with the growing size of the OS and applications somewhat and live disk compression lost popularity, particularly with the way DriveSpace did it. Storing your entire drive as a single giant file backed by FAT32 was a terrible idea and prone to corruption.

    When NTFS came around and introduced transparent file compression, that pretty much ended DriveSpace style compression. All modern FS now include some kind of compression, NTFS, APFS, BTRFS, ZFS. Even HFS+ had some ability to compress similar to APFS, but wasn’t very well known.

  • CanadaPlus@lemmy.sdf.org
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    3 years ago

    But look at that estimation screen! Again, rant all you wish, Microsoft knew how to handle a long running task even back in MS-DOS days. In this case, it’s estimated at 46 minutes. Great!

    Meanwhile, today it’s often just “beachball!”. It’s become a bit of a lost art.

  • Die4Ever@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    3 years ago

    on my old Windows 95 laptop I used the drive compression to create a partition to put some games on it, worked pretty well