Slashdot Mirror


How (And Why) FreeDOS Keeps DOS Alive (computerworld.com.au)

FreeDOS was originally created in response to Microsoft's announcement that after Windows 95, DOS would no longer be developed as a standalone operating system, according to a new interview about how (and why) Jim Hall keeps FreeDOS alive. For its newest version, Hall originally imagined "what 'DOS' would be like in 2015 or 2016 if Microsoft hadn't stopped working on MS-DOS in favor of Windows" -- before he decided there's just no such thing as "modern DOS". An anonymous Slashdot reader writes: No major changes are planned in the next version. "The next version of FreeDOS won't be multitasking, it won't be 32-bit, it won't run on ARM," Hall said. "FreeDOS is still intended for Intel and Intel-compatible computers. You should still be able to run FreeDOS on your old 486 or old Pentium PC to play classic DOS games, run legacy business programs, and support embedded development."
By day, Hall is the CIO for a county in Minnesota, and he's also a member of the board of directors for GNOME (and contributes to other open source projects) -- but he still remembers using DOS's built-in BASIC system to write simple computer programs. "Many of us older computer nerds probably used DOS very early, on our first home computer..." he tells ComputerWorld. Even without John Romero's new Doom level, "The popularity of DOS games and DOS shareware applications probably contributes in a big way to FreeDOS's continued success." I'd be curious how many Slashdot readers have some fond memories about downloading DOS shareware applications.

211 comments

  1. DOS was terrible by Anonymous Coward · · Score: 0

    Single user and no security what-so-ever. IBM should have used the 68000 combined with a proper OS.

    1. Re:DOS was terrible by Anonymous Coward · · Score: 0

      Pray, tell what possible use "security" would be on a DOS system.

    2. Re:DOS was terrible by Anonymous Coward · · Score: 5, Informative

      Single user and no security what-so-ever. IBM should have used the 68000 combined with a proper OS.

      Single user single tasking was just fine for the day's hardware and the user needs. *nix would just slow the hardware down for no good reason, PCs weren't for remote time sharing use. Plus *nix, and its software "ecosystem" wasn't really a good match for a 16-bit architecture.

      Yes, the 68K was a much nicer processor. The segmented memory models of the x86 were a major source of bugs. 32-bit registers would have been nice.

      MS and IBM had a proper OS for the hardware of that era, it was 16-bit OS/2. The market said no thank you.

    3. Re:DOS was terrible by Anonymous Coward · · Score: 1

      Given the low footprint DOS would actually be a great cloud OS if it had security. Just think about it, in the cloud every CPU second and memory byte used counts so using an OS that is as small as possible would be the optimal solution. Instead we use Linux and Windows, two heavyweight operating systems that have had to be scaled down significantly.

    4. Re:DOS was terrible by AK+Marc · · Score: 4, Informative

      It has both no security and perfect security. Security isn't in the OS, but there are also few vulnerabilities. The applications own the security. So there's no reason DOS couldn't be used, it would just need appropriately secure applications to meet your requirements.

    5. Re: DOS was terrible by sce7mjm · · Score: 1

      This.
      No network stack if you don't load it. No problem.
      Even better for hardware hacking on a pc/104 board. Get a connector to matrix board solder components. And prototype with no complications. It's a win win.

    6. Re:DOS was terrible by Koen+Lefever · · Score: 2

      Single user and no security what-so-ever. IBM should have used the 68000 combined with a proper OS.

      Yeah, that's what I said when the IBM 5150 PC was announced in 1981 with an 8/16-bit 8088 CPU running a rebranded Quick & Dirty Operating System:

      "Too little, too late".

      I was not aware yet that a brand name may be worth a lot more than technical specifications.

      --
      /. refugees on Usenet: news:comp.misc
    7. Re:DOS was terrible by Anonymous Coward · · Score: 0

      > but there are also few vulnerabilities.

      Nonsense. You obviously never heard of boot sector viruses. Executables were also vulnerable to being contaminated.

      Merely inserting a diskette could infect your machine.

    8. Re: DOS was terrible by Anonymous Coward · · Score: 0

      Now, computers are UEFI, and FreeDOS can't hack UEFI. Bye bye FreeDOS unless it changes.

    9. Re:DOS was terrible by mlts · · Score: 1

      I have seen some add-on security products for both MS-DOS and early Macs (pre OS X) that were pretty good, and were more than just separating users.

      The most notable was a product by Casady & Greene called A. M. E., or Access Managed Environment. It allowed for hierarchal management of users where only the top admins could see peers of each other, and everyone else could only see who was lower in the hierarchy. Each permission had a setting of not just allowing or disallowing, but allowing the downstream user to allow their downstream users to set that. It also had very good encryption for its time (DES on the disk, folders, and individual files), as well as the ability to add code to copy-protect or otherwise restrict executing of applications (these were well before the days of signed applications, even applications that checked their own resources for integrity.) It even had features controlling lockout of a user, not just exponential timeouts, but for a very sensitive user, would go and erase files flagged as "sensitive", which ensured a brute force, even if successful, attack would not bring much. It even brought to the table 2FA by giving the option that a user must insert a floppy disk with a nonce file on it, as well as entering their password.

      Of course, there was logging, and virtually every action could be set to be placed in an audit log.

      Of course, today's user management has replaced the security programs that sat on top of single user, cooperative multi-tasking operating systems, but it is interesting to see how this was added on.

    10. Re: DOS was terrible by r00t_of_all_evils · · Score: 2

      As I remember, merely inserting the diskette would do absolutely nothing. You had to either run a program from the diskette, or forget to take it out of the drive when you (re)booted the machine in order to actually "catch" anything from it. Autorun didn't come along until Windows 95.

      --
      God is real, unless declared integer.
    11. Re: DOS was terrible by Eluan · · Score: 1

      And even on Windows 95 there was never autorun on diskettes anyway.

    12. Re:DOS was terrible by AK+Marc · · Score: 1

      Merely inserting a diskette could infect your machine.

      Inserting a disk into a running machine would do what? You don't even really mount the disk until you try to access it.

      There are lots of vulnerabilities if you run insecure programs on it. Trojans, worms, and viruses had different meanings back in the day. They'd all operate differently, but would all require use of an infected (insecure) file. Anti-Virus was all about scanning insecure files you were trying to run. Simply put, if you never ran anything insecure, you never had a problem.

    13. Re: DOS was terrible by Etcetera · · Score: 1

      As I remember, merely inserting the diskette would do absolutely nothing. You had to either run a program from the diskette, or forget to take it out of the drive when you (re)booted the machine in order to actually "catch" anything from it.

      Autorun didn't come along until Windows 95.

      Maybe they're thinking of the Mac's System software... There were several viruses on the Mac that could be spread just by insertion since the Finder (or System) would load the Desktop file on the disk insert event.

    14. Re:DOS was terrible by LWATCDR · · Score: 1

      At the time micros where almost exclusively single user machines. You booted up the machine and it was yours. IBM did not want to eat into the much more profitable mini computer market or heaven forbid the 360/370 market. They went after the Apple, TRS-80, PET, and CP/M market. They also did not try to touch the Commodore VIC-20 and Atari market. IBM actually was price competitive with the other machines in that segment plus had the name IBM on it. It was not a great computer but it was good enough.
      Yes using a 68000 would have been a much better choice but the 68008 was not yet available and the 68000 was seen as too expensive. That is why the PC used the 8088 instead of the 8086.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    15. Re: DOS was terrible by jaymemaurice · · Score: 1

      I think you are forgetting that DOS needs BIOS. UEFI is to get rid of all legacy DOS support...
      It shouldn't be FreeDOS to provide BIOS... but perhaps someone will provide BIOS boot UEFI module... like the hardware manufacturers maybe?

      --
      120 characters ought to be enough for anyone
    16. Re: DOS was terrible by jaymemaurice · · Score: 1

      See something similar to BAMBIOS

      --
      120 characters ought to be enough for anyone
    17. Re:DOS was terrible by lsatenstein · · Score: 1

      Single user and no security what-so-ever. IBM should have used the 68000 combined with a proper OS.

      Single user single tasking was just fine for the day's hardware and the user needs. *nix would just slow the hardware down for no good reason, PCs weren't for remote time sharing use. Plus *nix, and its software "ecosystem" wasn't really a good match for a 16-bit architecture.

      Yes, the 68K was a much nicer processor. The segmented memory models of the x86 were a major source of bugs. 32-bit registers would have been nice.

      MS and IBM had a proper OS for the hardware of that era, it was 16-bit OS/2. The market said no thank you.

      The market did not say No, It was MS that saw OS/2 as a serious competitor, and did everything to prevent it's deployment. They MS succeeded.
      ask the old timers about that failure of OS/2.

      --
      Leslie Satenstein Montreal Quebec Canada
  2. There was a modern MS DOS ... by perpenso · · Score: 4, Informative

    ... before he decided there's just no such thing as "modern DOS" ...

    Well, there was a "modern MS DOS", it was MS OS/2 1.x.

    1. Re:There was a modern MS DOS ... by Anonymous Coward · · Score: 0

      Well, there was a "modern MS DOS", it was MS OS/2 1.x.

      Except that OS/2 was a multitasking, protected mode operating system from IBM and MS-DOS wasn't any of those things. Sure, OS/2 1.0 came with a DOS-like text mode command interpreter, but that is no more MS-DOS than Windows NT minus its GUI is. OS/2 1.1, released just 11 months later, came with the promised Presentation Manager GUI, further extending its abilities beyond MS-DOS.

    2. Re:There was a modern MS DOS ... by perpenso · · Score: 4, Informative

      Well, there was a "modern MS DOS", it was MS OS/2 1.x.

      Except that OS/2 was a multitasking, protected mode operating system ...

      That was part of what made it "modern".

      ... from IBM ...

      And from Microsoft

      ... and MS-DOS wasn't any of those things.

      OS/2 1.x was described by Microsoft as a modern OS designed to replace DOS.

      OS/2 1.1, released just 11 months later, came with the promised Presentation Manager GUI, further extending its abilities beyond MS-DOS.

      Extending its abilities, also known as "modernizing". According to Microsoft OS/2 1.x with Presentation Manager was the "upgrade path" from DOS. For users stuck with legacy software they were going to add a comparable GUI to DOS called Windows. The Windows and Presentation Manager APIs were nearly identical, a convenience for developers as described by Microsoft. Windows was just temporary. Then the market ignored OS/2 1.x and stayed with DOS, Microsoft then reconsidered Windows and their partnership with IBM. I think we know how the story goes from there. The fact remains, for a little while, OS/2 1.x was the modern OS to replace DOS according to Microsoft.

    3. Re:There was a modern MS DOS ... by NormalVisual · · Score: 4, Interesting

      According to Microsoft OS/2 1.x with Presentation Manager was the "upgrade path" from DOS. For users stuck with legacy software they were going to add a comparable GUI to DOS called Windows.

      Windows had already been available for nearly three years before Presentation Manager was released with OS/2 1.1, and was introduced only three months after the OS/2 development agreement between MS and IBM was signed. At the time the agreement was signed, Windows had already been in development for about a year as a response to other PC-based UI products, and of course the Lisa/Macintosh. The PM API was designed to be similar to the Windows API, not the other way around, and still had some substantial differences. Interestingly, the original 1985 HELLO sample program that Charles Petzold based his famous "Hello World" example on will still compile and run almost unmodified under Windows 10, with the needed modifications mostly being limited to variable types that have since changed.

      Having similar APIs was helpful, but they were different enough to make a common code base impractical.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    4. Re:There was a modern MS DOS ... by Jim+Hall · · Score: 5, Informative

      (Jim Hall here, from the article.)

      This is exactly why we decided a "modern" DOS wasn't really DOS anymore. As you say, OS/2 was intended to be the "modern" DOS of the day, a multitasking, protected mode operating system. But to get all that, you have to break binary compatibility. So OS/2 wasn't really DOS anymore. But it wasn't meant to be, hence the new name.

      Ultimately, we decided that if you can't run classic DOS programs on a "modern" DOS, then it's not DOS anymore. So we decided to keep FreeDOS as just plain DOS. That's why FreeDOS 1.2 and later will still be essentially the same as FreeDOS 1.1 and earlier, with a few updates here and there. No fundamental changes. We won't be multitasking or multiuser or any other "modern" operating system functionality. That's not what it means to be DOS.

    5. Re:There was a modern MS DOS ... by Sooner+Boomer · · Score: 2

      Ultimately, we decided that if you can't run classic DOS programs on a "modern" DOS, then it's not DOS anymore.... We won't be multitasking or multiuser or any other "modern" operating system functionality. That's not what it means to be DOS.

      Keep the software functionality; it's perfect for specific circumstances. Please try to modernize the hardware interface as much as possible. A lot of contemporary computers lack what was considered basic hardware when DOS was new (and gained new stuff).

      --
      Chaos maximizes locally around me.
    6. Re:There was a modern MS DOS ... by perpenso · · Score: 4, Funny

      I'm perfectly happy with your decision. However even if multitasking and multithreading were added they would not have to break backwards compatibility, they could merely extend the API. Legacy apps would not know or care and just run with a single thread. But this is just hypothetical, not a suggestion. If you had an itch to go in that direction I'd say create a FreeOS2 based on 1.x. Hell, there may be some commercial viability to such a project too.

      Oh ... and damn you ;-) ... you are the main reason my better DOS and BIOS books, and the Pentium MMX 166, survive garage cleanings and take up valuable space.

    7. Re:There was a modern MS DOS ... by perpenso · · Score: 2

      According to Microsoft OS/2 1.x with Presentation Manager was the "upgrade path" from DOS. For users stuck with legacy software they were going to add a comparable GUI to DOS called Windows. Windows had already been available for nearly three years before Presentation Manager was released with OS/2 1.1, and was introduced only three months after the OS/2 development agreement between MS and IBM was signed.

      None of that changes the fact that Microsoft was telling developers, including me, that OS/2 was the upgrade path from DOS and the Windows was a temporary thing for people with legacy hardware/software and that migrating them to OS/2 with Presentation Manager would be easy since porting your apps would be easy, Windows and Presentation Manager having a nearly identical API. As I said there was a window of time where Microsoft was telling people OS/2 was the replacement for DOS, Presentation Manager the replacement for Windows.

      And I had seen Windows since v1 too. Prior to v3 I don't think it was used much beyond allowing multiple DOS sessions to run.

      The PM API was designed to be similar to the Windows API, not the other way around, and still had some substantial differences.

      Its not that simple. Windows v3 had a lot of changes and you can't measure these things by product announcements and release dates. OS/2 Presentation Manager may have been influencing Windows 3.0 behind the scenes.

      Having similar APIs was helpful, but they were different enough to make a common code base impractical.

      As someone who had common code bases for Windows and MacOS I'd say you are mistaken. I'm not sure what Microsoft was saying but it may have been more of a porting your app from DOS to OS/2 thing. Remember, DOS was the dead end, just maintenance, OS/2 was the future ... in that brief window of time.

    8. Re:There was a modern MS DOS ... by dryeo · · Score: 2

      Before OS/2, there was multitasking DOS v4, http://www.os2museum.com/wp/mu... which was the direction that MS was taking DOS before branching out to what eventually became OS/2, http://www.os2museum.com/wp/be...
      There was also the family mode programs that ran on simple DOS and OS/2 v1 (as well as NT up to Win2k using the OS/2 sub-system) where the program basically had a minimal OS/2 environment grafted on. The text mode Word v5 is a good example.

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    9. Re:There was a modern MS DOS ... by Anonymous Coward · · Score: 0

      > MS-DOS wasn't any of those things

      MS-DOS 4.0 and 4.1 (not to be confused with the much later 4.01) were multitasking. These are referred to as 'European DOS' because they were released by Siemens and ICL in Europe. I worked for ICL at the time. The intent was to have these running in protected mode on the 80286 but most MS-DOS software was broken because it used segment arithmetic which failed on the 286. OS/2 was originally MS-DOS 5.0 (not the be confused with the much later MS-DOS 5).

      https://en.wikipedia.org/wiki/MS-DOS_4.0_(multitasking)

    10. Re:There was a modern MS DOS ... by Anonymous Coward · · Score: 0

      > Windows and Presentation Manager having a nearly identical API.

      One major porting issue was that the screen co-ordinates were 'upside down'. Windows origin is upper-left corner. PM origin is lower-left. OS/2 PM had a much richer API but this was _later_ added to Windows.

      https://en.wikipedia.org/wiki/Presentation_Manager

      > OS/2 was the upgrade path from DOS and the Windows was a temporary thing for people with legacy hardware/software

      What kept people on Windows was Windows/386 which allowed multiple DOS-boxes to run the DOS software that they wanted to use. They could run WordPerfect 5.1 and Lotus123 at the same time along with the DOS accounting system.

      OS/2 at the time only had a single 'penalty box'.

    11. Re:There was a modern MS DOS ... by Jim+Hall · · Score: 3, Funny

      Oh ... and damn you ;-) ... you are the main reason my better DOS and BIOS books, and the Pentium MMX 166, survive garage cleanings and take up valuable space.

      Mwahahahaha! Victory is mine!

    12. Re:There was a modern MS DOS ... by evilviper · · Score: 1

      Ultimately, we decided that if you can't run classic DOS programs on a "modern" DOS, then it's not DOS anymore. So we decided [...] We won't be multitasking or multiuser or any other "modern" operating system functionality. That's not what it means to be DOS.

      If memory serves, it was DR-DOS which added multitasking in a somewhat "GNU Screen" style. All DOS program ran just fine, and they just didn't know other programs were running at the same time.

      I don't see how adding that would make it "not DOS" any more than would adding command history and completion to the shell, as FreeDOS did from the start.

      Not that I see much future for it, either way. Linux has better Windows file system support and more Windows support utilities, these days, and the need to emulate old DOS programs drops significantly every year.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    13. Re:There was a modern MS DOS ... by TangoMargarine · · Score: 1

      All DOS program ran just fine, and they just didn't know other programs were running at the same time.

      Were they really running at the same time, or using task switching or interruptive multitasking or some such thing?

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    14. Re:There was a modern MS DOS ... by RockDoctor · · Score: 2

      I loaned my Pink Shirt Book to a friend .. and never got it beck. [SOB, in both senses]

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
    15. Re:There was a modern MS DOS ... by RockDoctor · · Score: 1

      If memory serves, it was DR-DOS which added multitasking in a somewhat "GNU Screen" style.

      As did DESQview. And there were several others. The need for multiple interacting modules and increased memory space over 640k were pushing at the limits.

      --
      Birds are not dinosaur descendants;birds are dinosaurs, for all useful meanings of "birds", "are" and "dinosaurs"
    16. Re:There was a modern MS DOS ... by sjames · · Score: 1

      Agreed, FreeDOS serves it's purpose well. Speaking theoretically, if it was to become multi-tasking, a Free DESQview clone would be the way to do it.

    17. Re:There was a modern MS DOS ... by perpenso · · Score: 1

      > Windows and Presentation Manager having a nearly identical API.

      One major porting issue was that the screen co-ordinates were 'upside down'. Windows origin is upper-left corner. PM origin is lower-left.

      That is not a major porting issue. That is a very minor thing, well, unless one writes some terrible code.

      OS/2 PM had a much richer API but this was _later_ added to Windows.

      By the way, I'm referring to Windows 3 not Windows 2.

      > OS/2 was the upgrade path from DOS and the Windows was a temporary thing for people with legacy hardware/software

      What kept people on Windows was Windows/386 which allowed multiple DOS-boxes to run the DOS software that they wanted to use. They could run WordPerfect 5.1 and Lotus123 at the same time along with the DOS accounting system.

      OS/2 at the time only had a single 'penalty box'.

      No. Users doing such things were so rare they are statistically insignificant. It was a classic chicken-and-egg thing. People didn't want to change apps, developers didn't want to port apps without a user base. DOS had the network effect advantage over OS/2. The only way to migrate users would have been to phase out DOS and ship OS/2 as the installed OS. But Microsoft changed their minds about partnering with IBM and about OS/2. Well, sort of, OS/2 NT, aka OS/2 3.0, was renamed Windows NT. So in a way DOS/Win3/Win9x was phased out and replaced by (OS/2)Windows NT.

    18. Re:There was a modern MS DOS ... by Anonymous Coward · · Score: 0

      > MS-DOS wasn't any of those things

      MS-DOS 4.0 and 4.1 (not to be confused with the much later 4.01) were multitasking. These are referred to as 'European DOS' because they were released by Siemens and ICL in Europe. I worked for ICL at the time. The intent was to have these running in protected mode on the 80286 but most MS-DOS software was broken because it used segment arithmetic which failed on the 286. OS/2 was originally MS-DOS 5.0 (not the be confused with the much later MS-DOS 5).

      https://en.wikipedia.org/wiki/MS-DOS_4.0_(multitasking)

      And Windows NT was originally OS/2 NT, aka OS/2 3.0, the architecture portable OS/2 that Microsoft Worked on while IBM worked on OS/2 2.0 the 32-bit Intel specific OS/2.

    19. Re:There was a modern MS DOS ... by evilviper · · Score: 1

      According to WP, very real and full-featured multitasking.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    20. Re:There was a modern MS DOS ... by TangoMargarine · · Score: 1

      According to Wikipedia (?) where?

      In the mid-1980s Microsoft developed a multitasking version of DOS.[6][7] This version of DOS is generally referred to as "European MS-DOS 4" because it was developed for ICL and licensed to several European companies. This version of DOS supports preemptive multitasking, shared memory, device helper services and New Executable ("NE") format executables. None of these features were used in later versions of DOS, but they were used to form the basis of the OS/2 1.0 kernel. This version of DOS is distinct from the widely released PC DOS 4.0 which was developed by IBM and based upon DOS 3.3.

      https://en.wikipedia.org/wiki/...

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    21. Re:There was a modern MS DOS ... by TangoMargarine · · Score: 1

      DOS is not a multitasking operating system. DOS did however provide a Terminate and Stay Resident (TSR) function which allowed programs to remain resident in memory. These programs could hook the system timer and/or keyboard interrupts to allow themselves to run tasks in the background or to be invoked at any time preempting the current running program effectively implementing a simple form of multitasking on a program-specific basis.

      https://en.wikipedia.org/wiki/...

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    22. Re:There was a modern MS DOS ... by evilviper · · Score: 1

      No idea why you're looking-up MS-DOS...

      As my original comment said: "it was DR-DOS which added multitasking"

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    23. Re:There was a modern MS DOS ... by TangoMargarine · · Score: 1

      Ah. DR-DOS, the thing that Microsoft ensured that nobody ran.

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    24. Re:There was a modern MS DOS ... by TangoMargarine · · Score: 1

      Looks like preemptive multitasking came out in Novell DOS 7 in December 1993. So about 18 months before Windows 95 ate their lunch, I would guess.

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
  3. The problem with FreeDOS... by Anonymous Coward · · Score: 0

    The problem with projects like FreeDOS, is that just about all programs for DOS are closed-source and proprietary. Even though FreeDOS itself is free software, its development implicitly promotes old proprietary software.

    Microsoft's old operating system doesn't deserve to be continued to be developed and supported like this. It deserves to die a horrible death, so that people can move on to a better platform, such as GNU/Linux, where there is a culture of free and open-source software.

    Have an old legacy proprietary DOS program that you need for your business? Then throw it into /dev/null, and hire some talented programmers to write a modern free open-source replacement for GNU/Linux, that will get published on github.

    These days, you can buy a BeagleBone Black or similar system-on-chip computer for very cheap, it comes with a full-blown GNU/Linux development environment that beats the pants off DOS.

    1. Re:The problem with FreeDOS... by Anonymous Coward · · Score: 0

      >These days, you can buy a BeagleBone Black or similar system-on-chip computer for very cheap, it comes with a full-blown GNU/Linux development environment that beats the pants off DOS.

      These day, I can buy a Wintel laptop for very cheap, and run a full-blown development environment for free (Visual Studio Community Edition), that beats the pants off DOS.

      So what's *your* point?

    2. Re: The problem with FreeDOS... by Anonymous Coward · · Score: 0

      But DOS programming is fun. Really. The Linux community is cliquish and overzealous. Who wants to get into that?

    3. Re: The problem with FreeDOS... by Anonymous Coward · · Score: 1, Interesting

      The nightmares of all those TSR's is something that I don't want to visit ever again.
      as for config.sys

      just gives me the shivers just thinking about it.

    4. Re: The problem with FreeDOS... by Anonymous Coward · · Score: 0

      Different AC here ... but programming TSR's was fun. Seriously, it was. But yeah, it was tricky to get right and lots of them sucked.

    5. Re: The problem with FreeDOS... by Anonymous Coward · · Score: 0

      I don't think you get it. For many of us it's about playing old DOS classics yet. Games like Master of Orion 2 that I was recently able to play on an Android tablet pool side while on vacation. So fun!

    6. Re:The problem with FreeDOS... by PhunkySchtuff · · Score: 4, Insightful

      Have an old legacy proprietary DOS program that you need for your business? Then throw it into /dev/null, and hire some talented programmers to write a modern free open-source replacement for GNU/Linux, that will get published on github.

      Why, that just sounds like an absolutely wonderful idea. Why would anyone insist keeping on using some old software that has been paid for many moons ago, and we all by now know exactly where and when it does and doesn't work because it's been doing the same task for 20 years? Why not instead pay thousands and thousands of dollars for someone to attempt to write a replacement for it, possibly reverse-engineering a proprietary and undocumented hardware interface (costing thousands and thousands of dollars more more in time) only to give it all away to the handful of other people on the planet who also use the same version of WHATEVER.EXE that I'm using?

      Yep, what a smashing idea!

    7. Re:The problem with FreeDOS... by Blaskowicz · · Score: 1

      Hire some talented programmers to write a program, and then maintain it forever.
      You revile binary compatibility because it's an enabler of proprietary software (most of it freeware written by a single person), the flipside is your stuff stops working after a few years.

      Like many here I've eventually abandoned Windows but face it, then the fun is over. Not much to do except spend your time in firefox, bash and vlc.

    8. Re:The problem with FreeDOS... by NormalVisual · · Score: 2

      These days, you can buy a BeagleBone Black or similar system-on-chip computer for very cheap, it comes with a full-blown GNU/Linux development environment that beats the pants off DOS.

      For some things, yes. If you need a hard realtime system with sub-microsecond timing requirements and deterministic interrupt handling, Linux isn't going to do it, but DOS will. Even RTLinux couldn't meet those kinds of requirements.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    9. Re: The problem with FreeDOS... by NormalVisual · · Score: 1

      Agreed! TSRs were a blast to write, and back in ye olden days it was a really useful bit of functionality. I could have done without dealing with segmented memory, though.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    10. Re:The problem with FreeDOS... by johannesg · · Score: 1

      Agree completely. It's much better to wait until your hardware dies, and then let your company go bust as some vital business function cannot be replaced in time.

    11. Re:The problem with FreeDOS... by PhunkySchtuff · · Score: 4, Informative

      Or, you know, use FreeDOS to run it on modern hardware - which is kind-of the point of the article.

    12. Re:The problem with FreeDOS... by Gavagai80 · · Score: 4, Informative

      Or just run it in DOSBox on any OS. For most software that's the obvious thing to do.

      --
      This space intentionally left blank
    13. Re:The problem with FreeDOS... by Anonymous Coward · · Score: 0

      DOSBox is an HLE emulator intended only for running games. It lacks several key features needed to properly run mission critical software. Just ask the devs, they heavily discourage the use of DOSBox for non-gaming applications.

    14. Re:The problem with FreeDOS... by Jim+Hall · · Score: 4, Informative

      Or just run it in DOSBox on any OS. For most software that's the obvious thing to do.

      Actually, it's better to run legacy business applications on an actual DOS system like FreeDOS. DOSBox is meant only for games. They don't have great compatibility with business software.

      FreeDOS runs very well in PC emulators and virtual machines like QEMU, VirtualPC, VMWare, VirtualBox, and others. At home, I run QEMU and DOSemu to boot FreeDOS. (When I'm developing, I use DOSemu so I can share files easily between Linux and FreeDOS. When I want to test FreeDOS in a more traditional virtual machine, I run QEMU.) It runs great!

    15. Re:The problem with FreeDOS... by KiloByte · · Score: 1

      That'll work only until you actually invoke any feature of DOS. Ie, you're operating on bare metal rather than DOS.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    16. Re:The problem with FreeDOS... by sumdumass · · Score: 4, Insightful

      The biggest problem I have seen with old programs is data portability. Even several revisions out on the same programs can make it costly. In a lot of situations , more costly than keeping obsolete hardware running.

      I was involved in a project to resurrect an old NetWare 3.something system for an accounting program used in a division of a company that was purchased originally as a stand alone company. It was determined years ago that it would be too costly to port the data because it would all need to be input by hand requiring several people and about a year to do so it was never updated to a modern system.

      Even after getting it running again, it was still in use in parallel with a dormant version of the company wide system for several years while they had three people pulling and inputting data and validating it before going live.

      Once you get out of the update cycle with proprietary software, it can sometimes even become costly to move up. But to switch to another system altogether can be really costly.

    17. Re:The problem with FreeDOS... by NormalVisual · · Score: 2

      Well, more properly until you call something in DOS or the BIOS that turns interrupts off or masks off the one you're interested in - if interrupts are enabled and you're not already servicing one at a higher priority, the processor will yank you right out of whatever was executing and drop you into the handler no matter what either you or DOS was doing at the time. If DOS still manages to interfere with you, you can always change the offending interrupt vector to point to your own code.

      Practically speaking, DOS is so simple that there's not much that it could do that couldn't be easily worked around.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    18. Re:The problem with FreeDOS... by KiloByte · · Score: 3, Insightful

      Practically speaking, DOS is so simple that there's not much that it could do that couldn't be easily worked around.

      I'd rather say: DOS is so simple it provides nothing that can't be implemented from scratch in less time that it takes to work around its downsides.

      The only worthwhile thing it gives you is a filesystem. A filesystem that doesn't work on modern machines (disks above 2GB, GPT partition tables, UEFI, sectors bigger than 512 bytes), gets corrupted on a crash, suffers from a ridiculous level of fragmentation, has bizarre limitations on file names (8.3, all caps, half of ASCII banned), and so on.

      I'm not sure what's the modern equivalent of INT 13 (some EFI calls?), but otherwise, writing a simple but adequate filesystem without those flaws is something any half-decent programmer can do in less than a day. Writing filesystems is like writing a compiler: a good optimized one takes a team a decade, something that works can be done really quickly.

      I've done so myself (filesystem-in-a-file rather than filesystem-on-sectors, though), with crash resiliency, transactions and zlib compression, although with some other limitations that fit my particular use case. And if you don't want to reinvent the wheel, there should be plenty of code to reuse around.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    19. Re:The problem with FreeDOS... by NormalVisual · · Score: 2

      The only worthwhile thing it gives you is a filesystem. A filesystem that doesn't work on modern machines (disks above 2GB, GPT partition tables, UEFI, sectors bigger than 512 bytes), gets corrupted on a crash, suffers from a ridiculous level of fragmentation, has bizarre limitations on file names (8.3, all caps, half of ASCII banned), and so on.

      All of which are usually not necessary on an embedded system that needs to fly fast and likely doesn't even need a filesystem. The point of my original post wasn't to say that DOS was the do-all and end-all of operating systems. Rather, it was to highlight the fact that on severely time-constrained systems, DOS will often "beat the pants off" a full OS like Linux. All of the support for different filesystems, USB, etc. are useless if I'm burning holes in stuff because I can't maintain a consistent 750 ns update window for a pair of laser galvos. Even RTLinux couldn't come close to that kind of guaranteed latency.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    20. Re:The problem with FreeDOS... by i.r.id10t · · Score: 1

      And reality, what more do many computer users need to do? A good browser and a format-compatible office suite like OpenOffice or LibreOffice, and maybe a mail client. And quite a few can do without the office suite, or just use google docs.

      --
      Don't blame me, I voted for Kodos
    21. Re: The problem with FreeDOS... by Anonymous Coward · · Score: 0

      Last week I needed to flash some motherboards and I had my choice of dos or win95 flashing tool.

      Freedos worked great for running the dos flash utility.

    22. Re: The problem with FreeDOS... by chipschap · · Score: 2

      "Back in the day" things like WordStar, 1-2-3, Agenda, dBase, etc., were considered really great stuff and were used to get a lot of work done. The world has moved on but I believe those "oldies" still can be useful. (There's the famous example of George R R Martin using WordStar apparently to this day.) And nothing much has really replaced Agenda.

      FreeDOS (and DOSBox) allow playing the old games, which I think made up for in gameplay what they lacked in graphics (the citation above of MOO is a good example). And things like ZZT were just ultimately cool. There is a fun factor in that old stuff that isn't in everything today.

    23. Re:The problem with FreeDOS... by chipschap · · Score: 4, Interesting

      I don't disagree with most of what's posted in this subthread, but I can tell you that DOSBox runs many things well. I've used it to keep Lotus Agenda alive, and to run WordStar, etc., on my Linux systems.

      It does lack printing, which is an issue, but there are workarounds that can be automated.

      Sure, if you want everything to work pretty much as-is, use FreeDOS[1]. But DOSBox does much more than gaming.

      [1] I've found some things don't work on FreeDOS, usually those things that rely heavily on internals of memory or hardware management. For instance the task switcher Back & Forth doesn't work.

    24. Re:The problem with FreeDOS... by DNS-and-BIND · · Score: 1

      DOSbox itself states that you should never use it for non-gaming DOS applications. It can go wrong at any random time for any nondeterministic reason. This example from the official forums tells you why. DOSbox is for games, just use it for games. "We do not care one iota about your database app" is a direct quote from a developer.

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    25. Re: The problem with FreeDOS... by Anonymous Coward · · Score: 0

      It only appears that way to the easily offended.

    26. Re:The problem with FreeDOS... by epyT-R · · Score: 1

      An extended dosbox that contains serial and parallel support.

      http://ykhwong.x-y.net/

    27. Re:The problem with FreeDOS... by Anonymous Coward · · Score: 0

      > it comes with a full-blown GNU/Linux development environment that beats the pants off DOS.

      and includes dosemu and dosbox for running old MS-DOS software.

    28. Re:The problem with FreeDOS... by Anonymous Coward · · Score: 0

      > DOSBox is meant only for games. They don't have great compatibility with business software.

      Agree completely, but for that need there's vDos

      https://vdos.info/

    29. Re: The problem with FreeDOS... by ihtoit · · Score: 1

      I build gaming cabinets using DOS. They sell better than new-build systems!

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    30. Re:The problem with FreeDOS... by LWATCDR · · Score: 1

      "Have an old legacy proprietary DOS program that you need for your business? Then throw it into /dev/null, and hire some talented programmers to write a modern free open-source replacement for GNU/Linux, that will get published on github."

      Let me explain why this is not as easy as it sounds.
      Let's say you run a mobil tool truck business and have been using a POS and inventory control system that runs on DOS for 30 years or so. It does everything you need. It is paid for and it works.
      So you thing they should pay a talented programer to replace it.
      1. What do they know about hiring a programer?
      2. What do they know about writing specs.
      3. What do they know about documentation?
      4. What do they know about QA.
      5. What they have works so what do they get for paying a few thousand dollars to make a new system that does what the old system does?

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    31. Re:The problem with FreeDOS... by TangoMargarine · · Score: 1

      This example from the official forums tells you why. [vogons.org]

      No, it really doesn't. It says "don't do that," then links to a 2-post thread that, oddly, links back to the original, without giving a reason either.

      "It can go wrong at any random time for any nondeterministic reason."--what the hell? This is computers we're talking about. Unless we're talking random cosmic rays flipping bits, why should they be inherently nondeterministic? DOS doesn't even do threading, right? Which would be the main source of nondeterminism I would think.

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    32. Re:The problem with FreeDOS... by Perky_Goth · · Score: 1

      Maybe I'm just ignorant, but now I'm curious. You mentioned

      possibly reverse-engineering a proprietary and undocumented hardware interface

      Would that hardware even work on a modern PC? Hmmm, I forgot PCI still exists, would that be how you'd connect it?
      I'm just curious.

    33. Re:The problem with FreeDOS... by PhunkySchtuff · · Score: 1

      I was talking in broad hypothetical strokes there (in other words, making stuff up to illustrate a point), and you're right, an old ISA card will be trouble, you might be able to find a specialised board with regular PCI or PCI-X with a bit of looking.

  4. DOS shareware games by 93+Escort+Wagon · · Score: 4, Funny

    I remember some of the really early DOS games that were written to basically run correctly and be playable on (IIRC) a 4.77MHz 8086/8088.

    Then I remember trying to play those same games on a (again, IIRC) 12MHz 80286 system. That lunar lander would just immediately plummet into the ground or crash into the side of a mountain, and try as I might - there was nothing I could do about it.

    --
    #DeleteChrome
    1. Re:DOS shareware games by mrbester · · Score: 3, Informative

      There were TSR utilities that basically wasted CPU cycles so you could play games like that. Centipede was another unplayable game unless you slowed it down.

      --
      "Wait. Something's happening. It's opening up! My God, it's full of apricots!"
    2. Re:DOS shareware games by PhunkySchtuff · · Score: 3, Insightful

      Yep, I remember having to write a TSR myself that would count from 1 to 100,000 or something like that at every tick of an interrupt just so Prince of Persia would play at an acceptable speed on my 386 DX2 66 when it was optimised for a 286.

    3. Re:DOS shareware games by Anonymous Coward · · Score: 0

      I'm surprised your 286 didn't have a Turbo button, which slowed the clock rate down to run games such as that.

    4. Re:DOS shareware games by jm007 · · Score: 1

      I remember the Turbo button. Don't remember it affecting the games I was playing (much), though I tried.

      Why would something that slowed things down be called 'Turbo?'

    5. Re:DOS shareware games by Anonymous Coward · · Score: 1

      Generally it was "on" pressed in, hence "turbo". Last machine I had with it I think was 16MHz -> 33MHz.

    6. Re:DOS shareware games by 93+Escort+Wagon · · Score: 1

      Why would something that slowed things down be called 'Turbo?'

      Maybe games needed a "Torpid" button instead...

      I remember the Turbo button too; but, as you said, it didn't seem to slow things down enough.

      --
      #DeleteChrome
    7. Re:DOS shareware games by Eluan · · Score: 1

      That's weird, I last ran Prince of Persia without emulation on a K6-2 @350Mhz and there were no speed problems.

    8. Re:DOS shareware games by zwarte+piet · · Score: 1

      Ran it last week on a core-i3 at 2300Mhz. No problems.

    9. Re:DOS shareware games by nukenerd · · Score: 1

      Maybe games needed a "Torpid" button instead...

      The "turbo" button was a "torpid" button. Contrary to the name, it did slow things (on my 486 at least) down to 4.77 MHz, for games. I guess the marketing people had a sense of humour, or thought that "torpid" did not sound very cool.

    10. Re:DOS shareware games by Anonymous Coward · · Score: 0

      Haha I remember an 8088 game that I thought didn't work on my 486. The screen would change graphics modes, then come back to DOS. I was like, what is going on? So I tried it on an actual 8088, and the game worked fine. It was a game where you had to maneuver around a map, avoiding enemies and doing things to clear levels. But if you just didn't press the keyboard your character would, after several seconds, collide with the wall, and die. Then you would restart with a new life, and repeat that. After all three lives were gone, you'd go back to the DOS prompt, your game concluded. All that was happening before the graphics mode on the monitor had even caught up, on the 486.

      I didn't write a damned TSR or vector any interrupts though, I just played it on the 8088 briefly and then played real games, like Dune II. I suppose I'd have been willing to jump some hoops for Prince of Persia though.

  5. DOS's built-in BASIC system? by Anonymous Coward · · Score: 0

    DOS had a basic interpreter? I don't remember that. In fact I'm pretty sure it didn't. Apples and Commodores provided BASIC. Not Microsoft DOS.

    1. Re:DOS's built-in BASIC system? by sjames · · Score: 5, Informative

      Yes, GW-BASIC.

    2. Re:DOS's built-in BASIC system? by Anonymous Coward · · Score: 0

      DOS had a basic interpreter? I don't remember that. In fact I'm pretty sure it didn't. Apples and Commodores provided BASIC. Not Microsoft DOS.

      Every version of MS-DOS I've used had a BASIC interpreter of some sort.

      The IBM OEM versions of DOS would essentially call the BASIC that was in ROM, augmenting it with routines for disk access and enhanced graphics modes.

    3. Re:DOS's built-in BASIC system? by Anonymous Coward · · Score: 0

      DOS had a basic interpreter? I don't remember that. In fact I'm pretty sure it didn't. Apples and Commodores provided BASIC. Not Microsoft DOS.

      IBM PC DOS, which was MS-DOS, included Microsoft Basic.

    4. Re: DOS's built-in BASIC system? by Anonymous Coward · · Score: 0

      Early PCs and clones provided Microsoft BASIC in ROM.

    5. Re:DOS's built-in BASIC system? by Anonymous Coward · · Score: 0

      DOS had a basic interpreter? I don't remember that. In fact I'm pretty sure it didn't. Apples and Commodores provided BASIC. Not Microsoft DOS.

      I have some vague memories of QBASIC being included with at least MS-DOS 6, not sure if it was included before then.

    6. Re: DOS's built-in BASIC system? by Anonymous Coward · · Score: 0

      It was included before then. I used both BASICA and QBASIC and later QuickBasic because of the compiler. Fun times.

    7. Re:DOS's built-in BASIC system? by mrbester · · Score: 1

      BASIC-A, GW-BASIC and GW-BASIC were available depending on what version you were running and from whom.

      --
      "Wait. Something's happening. It's opening up! My God, it's full of apricots!"
    8. Re:DOS's built-in BASIC system? by dosius · · Score: 1

      QBASIC was in MS-DOS 5 and later, and PC DOS 5.0 throught 5.02.

      In MS-DOS, it replaced GW-BASIC; IBM continued to keep their BASICA (which GW-BASIC was functionally equivalent to but did not depend on the Cassette Basic in ROM) around to the end.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    9. Re:DOS's built-in BASIC system? by Rockoon · · Score: 1

      DOS had a basic interpreter? I don't remember that. In fact I'm pretty sure it didn't.

      Then things that you are pretty sure about are sometimes trivially and obviously wrong.

      Both the first shareware and one of the first mainstream open source software used it, that being PC-TALK.

      But hey... you arent old enough to know any of this, but somehow managed to think that you were knowledgeable.

      --
      "His name was James Damore."
    10. Re:DOS's built-in BASIC system? by Blaskowicz · · Score: 2

      Qbasic was included in Windows 9x and even NT4 apparently. Notably, "Microsoft Edit" was a shim that called qbasic.exe in editor-only mode (it's still better than vi and nano). Qbasic itself allows to play short high pitched tones through the PC speaker to startle people around you, or to annoy them much with a long duration 4KHz for instance.

      What's too bad is the keyboard input, unless there's some other way you couldn't really use continuous keyboard input for something like a space invader clone. Everyone used a loop like 10 A$=INKEY$ : IF A$="" THEN 10 which let you input a single key without needing to hit return, but you would just move single step by single step or trigger keyboard repeating and move wildly. Tweaking keyboard repeating in BIOS (or with a DOS program?) might have helped in some way.
      That alone prevented attempts at making "serious" games (and in mid to late 90s, Internet access was prohibitively expensive in Western Europe still so Qbasic and its detailed help files is what you got for free)

    11. Re:DOS's built-in BASIC system? by Anonymous Coward · · Score: 0

      QBasic came with Nibbles which scanned the keyboard. You could do this with peek/poke (or some built in function, can't remember). Getting smooth side scrolling/parralax and sprite engines going was a big deal though.

    12. Re:DOS's built-in BASIC system? by Anonymous Coward · · Score: 0

      Oh yeah? Then how come this gorilla just destroyed a city with bananas?
      https://www.youtube.com/watch?...

    13. Re:DOS's built-in BASIC system? by Blaskowicz · · Score: 1

      Oh crap, I had no idea to look for keyboard input there :)
      Availability of .BAS example files/games may have varied between DOS, Windows 95 and 98.
      So I should have looked for off-line help back then be it a book, people that knew about programming, getting someone to print nibbles.bas.
      Yes scrolling like a NES game wasn't something I even considered doable (doing something tiled-based, slow and naive in 40x25 text mode would have been fun already)

    14. Re:DOS's built-in BASIC system? by MobileTatsu-NJG · · Score: 1

      You could sort of do it in EGA mode if you used the PCopy command. My memory is fuzzy on the exact implementation of it but you could draw pictures into one of 8 'pages' of memory and use pcopy to dump that data into an invisible page, then make that page visible... double-buffering I think it was called.

      I did a few experiments where some scrolling and even a bit of sprite animation could be done. It didn't have the performance to be mistaken for an NES, but it could have been in the ballpark of Commander Keen.

      I apologize for not being able to get into grittier detail, but I did quite a bit of graphic experimentation with QBasic and was surprised about how far I got with it.

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    15. Re:DOS's built-in BASIC system? by Anonymous Coward · · Score: 0

      > DOS had a basic interpreter? I don't remember that.

      IBM-PCs (5150 and some others) had BASIC in ROM and a cassette port to load/save programs if you didn't have disks or MS-DOS. BASICA would load BASIC form PC-DOS. Many MS-DOS had GW-BASIC (Gee Wizz) included.

    16. Re:DOS's built-in BASIC system? by HBI · · Score: 1

      You'd write an event loop. It's pretty much how it is done elsewhere, too. True, it was nice to have something like the Turbo Pascal "keypressed" boolean to save cycles, rather than comparing INKEY$ to figure out if a character came in, but you'd be stuck writing an event loop regardless to handle multiple forms of input (mouse, joystick, etc)

      Failing that, you could CALL INTERRUPT 16h to get what you wanted, fairly easily, and wrap it in a SUB or FUNCTION. A copy of the old Peter Norton book would have been enough to do it.

      --
      HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
    17. Re:DOS's built-in BASIC system? by LiENUS · · Score: 1

      I thought commander keen was pretty close to nes in terms of smoothness. It did start life as a smb3 clone afterall.

    18. Re:DOS's built-in BASIC system? by MobileTatsu-NJG · · Score: 1

      It was playable, even on slow machines. Unfortunately I was nitpicky enough to see that it was operating at about half the frame rate of NES games. I never did know if that was because they put a limiter in there or if there really was some sort of bottleneck that kept it from running at 60fps.

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

  6. Heckle! by Anonymous Coward · · Score: 0

    > Hall originally imagined "what 'DOS' would be like in 2015 or 2016 if Microsoft hadn't stopped working on MS-DOS in favor of Windows" -- before he decided there's just no such thing as "modern DOS".

    Booooooo! Boooooo! But imagine if there were a modern DOS. So I am seizing Control of this article and asking Hey, Slashdot, if there were a modern DOS, what would it be like?

    1. Re:Heckle! by Z80a · · Score: 1

      Bloated as hell.

    2. Re:Heckle! by Anonymous Coward · · Score: 1

      > if there were a modern DOS, what would it be like?

      It would be like DRI's DR-Multiuser-DOS or later derivatives such as System Manager or IMS Real-32. Multiuser, multi-tasking, networking, multi-virtual screens. These would run Windows 3,11 in 386 mode on several screens.

      Single user cut down versions of Multiuser-DOS came out as DR-DOS 5, DR-DOS 6 with task-switching and DR-DOS 7 (NW-DOS 7 from Novell) with multi-tasking, multi-virtual screens.

      The origin of this was MP/M-86, Concurrent-CP/M-86 and Concurrent-DOS which were being demonstrated at the time that MS-DOS 2 was released (which was 'advanced' enough to support hard disks).

  7. You're not that old by phantomfive · · Score: 3, Informative

    "Many of us older computer nerds probably used DOS very early, on our first home computer..."

    And here I think of DOS as a 'newer' system

    --
    "First they came for the slanderers and i said nothing."
    1. Re:You're not that old by Nyder · · Score: 1

      "Many of us older computer nerds probably used DOS very early, on our first home computer..."

      And here I think of DOS as a 'newer' system

      Well, I was using TRS-80 DOS and L-DOS on TRS-80's in the very early 80's. But that was at school. My first home computer was a C64 with a cassette drive.

      --
      Be seeing you...
    2. Re:You're not that old by mvdwege · · Score: 1

      Yeah, the problem is that the Internet is dominated by the voices of the PC generation, who somehow never learned that there actually was a long history of computing before the PC and MS-DOS.

      Heck, most of them would be surprised if you told them DOS was a bad rip-off of an existing system to start with.

      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    3. Re: You're not that old by Lproven · · Score: 1

      Hear, hear!

      I came to work with MS-DOS after CP/M, which followed VAX-VMS at uni. :-)

      #greybeard

      --
      Liam P. ~ "Intelligence is a lethal mutation." (me)
    4. Re:You're not that old by Dutch+Gun · · Score: 5, Interesting

      Yeah, the problem is that the Internet is dominated by the voices of the PC generation, who somehow never learned that there actually was a long history of computing before the PC and MS-DOS.

      CP/M and other precursor OSes are really only of interest to historians and nostalgic geeks, but DOS actually has some real relevance to many people and projects even today, thanks to FreeDOS and the fact that we're still running x86-compatible machines... which is sort of astounding, actually.

      Sure, there was a long history of computing before the PC and MS-DOS, but it was constrained to very few people for the most part - specialists, hobbyists, professionals, academics, and so on. But it was really the PC, running MS-DOS for the most part, when the vast majority of people were introduced to computers for the first time. So, it's not all that surprising that DOS is seen - rightly, I think - as the OS most used at the beginning of the personal computer revolution.

      Even so, I don't think that many people mistake that for the beginning of computing in general. If nothing else, they saw computers on TV, with walls of reel-to-reel tapes and flashing lights.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    5. Re:You're not that old by NormalVisual · · Score: 2

      Yeah, the problem is that the Internet is dominated by the voices of the PC generation, who somehow never learned that there actually was a long history of computing before the PC and MS-DOS.

      Such as IBM offering VM functionality for almost 10 years prior to the PC's introduction. ;-)

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    6. Re:You're not that old by swb · · Score: 2

      I think you're right, but I think you have to label DOS generically as loads of people were first exposed to other DOS systems, like Apple ][ DOS 3.3 and the various other DOS-alike command line interpreters for home computers like the Radio Shack Color Computer, C64, and so on.

      The IBM PC was expensive and many schools had Apple ][s and a lot of home users used ColorComputer and Commodore 64s versus more expensive IBM branded PCs.

      I think part of the reason DOS may rightly be seen as "old school" computing is just the character-cell command line "look" which most people don't see unless their computer is doing something wrong, someone is fixing it for them, and it looks like every other CRT-based terminal running on any other system -- IBM 3270 sessions, VT-100 talking to a VAX, and so on.

    7. Re: You're not that old by Anonymous Coward · · Score: 1

      Very few people? There where more C64:s sold than pcs to date.

    8. Re:You're not that old by Jim+Hall · · Score: 4, Interesting

      Yeah, the problem is that the Internet is dominated by the voices of the PC generation, who somehow never learned that there actually was a long history of computing before the PC and MS-DOS.

      CP/M and other precursor OSes are really only of interest to historians and nostalgic geeks, but DOS actually has some real relevance to many people and projects even today, thanks to FreeDOS and the fact that we're still running x86-compatible machines... which is sort of astounding, actually.

      Sure, there was a long history of computing before the PC and MS-DOS, but it was constrained to very few people for the most part - specialists, hobbyists, professionals, academics, and so on. But it was really the PC, running MS-DOS for the most part, when the vast majority of people were introduced to computers for the first time. So, it's not all that surprising that DOS is seen - rightly, I think - as the OS most used at the beginning of the personal computer revolution.

      Even so, I don't think that many people mistake that for the beginning of computing in general. If nothing else, they saw computers on TV, with walls of reel-to-reel tapes and flashing lights.

      The interview was about DOS, so I didn't talk about the other stuff before DOS (and after).

      Our first "computer" was a mainframe acoustic coupler dial-up terminal my mom brought home for a week, so she could do some work at home. I wasn't very excited about it at the time; it was all business software and I was like eight years old.

      I seem to remember we had another computer in the house at one point. Not a TRS-80 but something along those lines.

      In 1982, my family bought an Apple clone (Franklin ACE 1000) and that was where my brother and I taught ourselves to write programs in AppleBASIC. I was fascinated by computer interfaces that we saw on TV and in the movies, so I wrote programs that emulated those, including the thermonuclear war simulator from the Wargames(1983) movie.

      Some time after that, we bought an IBM (I think the XT). And that's what got me started with MS-DOS.

      We used MS-DOS at home (upgrading to the '286 and '386 and '486) until I went to college with the family's old '386. During my university days, I had an account on the VAX and the Unix systems. I discovered Linux, and switched to that on my own computer (dual-boot with MS-DOS). I mostly avoided Windows at home, although I did run Windows 3.11 and Windows 95 for a short time - mostly for games. At work, I ran Apollo AEGIS/DomainOS, HP-UX, AIX, SunOS/Solaris, and Linux (RedHat 3.0.3 and later). Work also put me on a Windows NT4 desktop, which I ran for a while until they let me run Linux at work full-time. In the office, I've run either Windows (whatever was current) or Linux. At home, I just run Linux (I'm running Fedora Linux now) and use DOSemu or QEMU to run FreeDOS.

    9. Re:You're not that old by nukenerd · · Score: 1

      CP/M and other precursor OSes are really only of interest to historians and nostalgic geeks,

      You can say that about DOS too.

      it was really the PC, running MS-DOS for the most part, when the vast majority of people were introduced to computers for the first time.

      Some, but not "the vast majority". Many people were introduced by pre-DOS computers. Geeks were still buying non-DOS, non-Windows home (and work) computers through all the 1980's, for nearly 10 years after PC-DOS came out. At work as techies we had a mainframe terminal, a PDP-11, and a Commodore PET. We regarded the IBM PC and DOS as for admin people and would not have given a thank you for one. At home I had a CP/M machine and other techies owned BBCs and Ataris, not IBM PC clones. It was Windows that introduced "the vast majority" of people to computers, unaware that DOS lay beneath the pre-Win95 versions. Even at work, most people did not get a PC on their desk until the Windows era.
       

      So, it's not all that surprising that DOS is seen - rightly, I think - as the OS most used at the beginning of the personal computer revolution.

      No, that's wrong. The personal computer revolution had begun before DOS and in the 1980s was in full swing with or without DOS. There was a wide range of types such as Sinclairs, Commodores, Amigas, Amstrads alongside the IBM/DOS PC in the 1980-95 period. It was standardised on the IBM PC clone only gradually.

    10. Re:You're not that old by AthanasiusKircher · · Score: 2

      it was really the PC, running MS-DOS for the most part, when the vast majority of people were introduced to computers for the first time.

      Some, but not "the vast majority". Many people were introduced by pre-DOS computers. Geeks were still buying non-DOS, non-Windows home (and work) computers through all the 1980's, for nearly 10 years after PC-DOS came out.

      This is completely accurate. The "personal computer revolution" began ca. 1980, and it wasn't until sometime around 1989 or 1990 that DOS-compatible devices started to dominate the home PC market. For that first decade, DOS-based devices were often primarily for business. I still remember a friend whose dad (worked in some tech-savvy industry) got an IBM-compatible PC that ran DOS at home in 1986 or so... and it was seen by everyone else in the neighborhood as some weird novelty. Everybody else had cheap computers (often aimed at gaming) -- Atari computers, Commodore 64s, etc. as well as the more expensive Macs. And they mostly didn't run DOS. People who wanted to use such systems for stuff other than games had different OS options, like loading GEOS on a Commodore, which gave you a GUI and access to word processing, spreadsheets, etc.

      It was Windows that introduced "the vast majority" of people to computers, unaware that DOS lay beneath the pre-Win95 versions. Even at work, most people did not get a PC on their desk until the Windows era.

      That's also true, though I'd say a few years earlier with Windows 3.1 was when PCs really started to move beyond the hobbyist world. It really was the GUI that made it work for most folks (hence the reason why people in the 1980s liked Macs and GEOS on Commodores, etc.). DOS and other command-line OSes were just an annoyance to everyone but hobbyists, and the idea that "the vast majority" got to know computers through DOS is just misguided.

    11. Re:You're not that old by Anonymous Coward · · Score: 0

      You know you're getting old when the kids are calling themselves old.

    12. Re: You're not that old by demonlapin · · Score: 1

      No; there were more C64's sold than any other specific model of computer. Total number of x86 PC's is way, way higher than the 64's numbers.

    13. Re:You're not that old by Dutch+Gun · · Score: 1

      You can say that about DOS too.

      This is the only point I'll flat out disagree with you on. Even today, there's at least one commercial product I know of sold that make use of FreeDOS to boot into a clean PC environment for some of its operations. It's still a real thing for some people, although an admittedly small group.

      No, that's wrong. The personal computer revolution had begun before DOS and in the 1980s was in full swing with or without DOS. There was a wide range of types such as Sinclairs, Commodores, Amigas, Amstrads alongside the IBM/DOS PC in the 1980-95 period. It was standardised on the IBM PC clone only gradually.

      When you start getting into subjective territory like this, there will inevitably be disagreement about how you define the "beginning" of the personal computer revolution, I suppose. My guess is many geeks like us will tend to define it as "when I got my first computer". ;-)

      I should probably have said *thoughout* the personal computer revolution, because you're correct that there were a lot of competitors in the early days. After all, my first computer was an Apple II, not a PC. Also, I think people are misunderstanding one of my statements. I said:

      But it was really the PC, running MS-DOS for the most part, when the vast majority of people were introduced to computers for the first time.

      Which I'd bet is probably accurate (although I admittedly have no numbers to back this up), as these were the machines they likely used at work. When it came time to purchase a machine of their own, it made sense to them to get another DOS or Windows-based PC, because that's what they knew. The DOS-PC's success at work made a bit impact on the home market, because as indicated, there were plenty of great competitors.

      Well, anyhow, history is written by the winner. Or, rather, in this case, we look back and see the DOS-based PC as the most important of the line solely because of its place in history. We have to acknowledge that DOS is important not necessarily because of its qualities, but because of how widely used it became as the basis for Microsoft's reign over desktop computing, which continues even to this day.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    14. Re:You're not that old by Anonymous Coward · · Score: 0

      > The "personal computer revolution" began ca. 1980,

      The first computer that was advertised as a 'personal computer' was the Apple II in 1978.

      In fact the IBM PC (5150) was aimed squarely at being a bit better than the Apple II with CP/M included, just like the Apple II with a Z80 softcard (which Microsoft made).

                            Apple II
      RAM 48Kb plus 64Kb (for CP/M)
      Disk 2 120Kb
      OS BASIC and CP/M
      SW Visicalc Wordstar dBase

                            IBM PC model A
      RAM 16Kb to 256Kb (more on model B)
      Disk 2 160Kb (SSSD)
      OS BASIC and PC-DOS (CP/M clone)
      SW Visicalc Wordstar dBase

    15. Re:You're not that old by mvdwege · · Score: 1

      CP/M and other precursor OSes are really only of interest to historians and nostalgic geeks,

      The fact that you seem to assume that the direct lineage of DOS is the only thing that matters shows you exactly for the kind of young know-it-all I was describing.

      Here's a hint: even though I grew up with 8-bit micros during the CP/M to DOS transition years, I at least know that computing had been going on for a lot longer than that, on a variety of machines from micros to mainframes; and I recognise most of what the PC hipsters hail as 'new and innovative' is usually nothing but badly reimplemented 70s technology.

      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    16. Re:You're not that old by Anonymous Coward · · Score: 0

      There's plenty of COM files and EXE files and BAT files you can still run today on a modern Windows system natively, or Linux with a little bit of work. Then there's the topic of the article- FreeDOS wouldn't be important if it didn't support just a massive shit ton of software, orders of magnitudes more than you saw on prior OSes. It's not about the "PC generation", it's about the fact that there's a straight line of compatibility between here and there, and actual relevant software (including games which actually play BEST in DOS). DOS is modern. Prior OSes are of historical interest only.

  8. BIOS Updates by Anonymous Coward · · Score: 1

    Is it true FreeDOS is one of the more desirable live environments to boot from in order to update BIOS?

    1. Re:BIOS Updates by jo7hs2 · · Score: 2

      At least historically, for a long time, it certainly was. I've seen some utilities push away from it now, but for a very long time you'd load a FreeDOS floppy or other volume that contained the BIOS update .EXE and the update itself.

    2. Re: BIOS Updates by Anonymous Coward · · Score: 0

      These days you typically put the BIOS update on a USB stick and enter the BIOS to update from the stick. No need to boot any OS.

    3. Re: BIOS Updates by Blaskowicz · · Score: 1

      I like to download the iso (something that boots FreeDOS and runs some graphical wizard stuff I'm not interested in), mount the iso, extract the BIOS and flashing program from subdirectories/archive/floppy image, put them on USB and boot MS-DOS 7.10 to run the thing.

  9. DOS, or rather OS/2, lives on by Anonymous Coward · · Score: 0

    https://en.wikipedia.org/wiki/EComStation

    A better "DOS"...

    Memories? Well, remember Pournelle declaring that CP/M was better than DOS.
    And tweaking config.sys and autoexec.bat etc. to get QEMM working.

    Then discovered BSD which makes DOS look like a broken toy...

    1. Re:DOS, or rather OS/2, lives on by mrbester · · Score: 1

      And tweaking config.sys and autoexec.bat etc. to get QEMM working.

      Ah, yes. I managed to get 634K free base memory after tweaking settings to get everything loaded high on QEMM. Took some doing.

      --
      "Wait. Something's happening. It's opening up! My God, it's full of apricots!"
    2. Re:DOS, or rather OS/2, lives on by Anonymous Coward · · Score: 1

      Ah, yes. I managed to get 634K free base memory after tweaking settings

      634K ought to be enough for anybody.

    3. Re:DOS, or rather OS/2, lives on by NormalVisual · · Score: 1

      Ah, yes. I managed to get 634K free base memory after tweaking settings to get everything loaded high on QEMM. Took some doing.

      DEVICEHIGH/LOADHIGH, how we loved ye...

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    4. Re:DOS, or rather OS/2, lives on by obsess5 · · Score: 1

      Unrelated to DOS, but back in the mid-1980s, we used iRMX-86 on 80286 single-board computers in 8086 real mode. Our computers were going out to lunch when returning from an interrupt service routine. Our local Intel representative had never heard any similar complaints and we even got an official Intel 80286 hardware emulator in-house to try and debug the problem. We finally had a conference call with some Intel engineers and they told us, oh yeah, there's a bug in the return-from-interrupt instruction (all interrupts were briefly enabled before the prior interrupt mask was restored from the stack) and they gave us an RTI macro to get around the problem. Then, a couple months later, Jerry Pournelle mentioned the bug in his BYTE column! Aarrgghh! A lot of wasted time and effort--and Pournelle knows all about it!

  10. Use it via DOSEMU by RuffMasterD · · Score: 5, Informative

    I still use FreeDOS regularly to run 20 year old research software. I use DOSEMU, which lets me edit files and move data around in Linux, and then read them into the DOS program without stopping and starting a virtual machine. So I have a DOSEMU terminal open, and my favorite text editor next to it, and maybe tail the log file in another terminal, all at the same time.

    That old DOS software is still superior to any new point-and-click software. The config files leave a precise record of what parameters I set, and the logs leave a precise record of the result. It's fully auditable and reproducible, which is what science should be. And it will still run just as well as the day it was bought in another 20 years from now. The director tried to get us to buy some 'modern' software to do the same task. It 'only' cost $5000 and ran in MS Access. He was surprised when I refused the offer. Does it leave a written record of what I did? No. Are the results reproducible? No. Will it still run in 20 years time? Fuck no. Some things aren't broken yet, leave them alone.

    --
    Human Rights, Article 12: Freedom from Interference with Privacy, Family, Home and Correspondence
    1. Re: Use it via DOSEMU by Anonymous Coward · · Score: 0

      So what you're saying is then, is that your favorite editor isn't 'edit.exe/com'?

      Blasphemy!

    2. Re:Use it via DOSEMU by Anonymous Coward · · Score: 1

      DOSBox is good also, Win and Linux versions exist.

    3. Re:Use it via DOSEMU by nnull · · Score: 2

      I second this. I have plenty of old DOS engineering programs from my father that still work great. I use them from time to time because similar software no longer exist or costs a ridiculous amount of money that doesn't even do what I want. A lot of this software came from engineering enthusiasts which made them great, something that doesn't happen much anymore.

    4. Re: Use it via DOSEMU by KiloByte · · Score: 1

      edit.exe is for spoiled kids. Real {M,Wom}en(TM) used edlin.com!

      Well, strictly speaking I hardly ever used edlin, and ed's source code is pretty much "while read x;do echo ?;done", but on a MUD I've coded for over a decade, you could either muck around with FTP (not compatible with any fuse stuff) or use ed. As their ed was vastly improved over both edlin and Unix ed, it was pretty comfortable once you got used to it.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    5. Re:Use it via DOSEMU by KiloByte · · Score: 1

      DosBox also works on non-x86 hardware. You can run it on any cheap electricity-conserving piece of ARM with more than enough oomph for anything that was written for DOS.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    6. Re: Use it via DOSEMU by Anonymous Coward · · Score: 0

      edit.exe is for spoiled kids. Real {M,Wom}en(TM) used edlin.com!

      Real programmers used COPY CON MYPROGRAM.EXE

    7. Re: Use it via DOSEMU by KiloByte · · Score: 1

      Real programmers used COPY CON MYPROGRAM.EXE

      I doubt if it's possible to make a legal .exe without nulls, and IIRC "copy con" doesn't allow those. As for .com, try this one: Alt-239 Alt-240 Alt-240 Alt-240 Alt-240.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    8. Re: Use it via DOSEMU by Anonymous Coward · · Score: 0

      Ha - Qixx's "ed" program? Are you on RetroMUD or BatMUD or something?

    9. Re:Use it via DOSEMU by techno-vampire · · Score: 1

      ... the logs leave a precise record of the result.

      Not only that, the logs are in clean 7-bit ASCII instead of some undocumented binary format so that you don't need some special program to read them.

      --
      Good, inexpensive web hosting
    10. Re: Use it via DOSEMU by Blaskowicz · · Score: 1

      Eh now there's FTP stuff with fuse. Or Jedit in early 00s to edit files on an ftp (there must be a thousand editors that do this but this one was - is - a desktop java application and thus cross-platform in Windows 9x, XP, Unix)

    11. Re: Use it via DOSEMU by Anonymous Coward · · Score: 0

      edlin is punishment from god

  11. Downloading DOS shareware by Anonymous Coward · · Score: 0

    By the time being online no longer cost serious money, we had already switched to Linux and NT4.
    I remember downloading drivers for our SPEA graphics card and Canon printer from mailboxes in Win 3.1 times, but it took ages to download a megabyte on a 14.4k modem.

    For shareware we relied on floppy disks and CDs. Most of them came attached to some magazine.

    1. Re:Downloading DOS shareware by Jim+Hall · · Score: 3, Informative

      For shareware we relied on floppy disks and CDs. Most of them came attached to some magazine.

      I wonder how many new devs know what "shareware" was? For those wondering: shareware was a concept where devs created something and gave away a limited version of it for free. And you could share that limited version with anyone. Shareware games usually were the first "chapter" or first few levels. Shareware DOS applications usually just nagged you to buy them after 30 days - but I don't remember many that actually stopped working if they weren't registered.

      I mentioned some shareware in the interview, but I played a lot of Wolfenstein 3D, DOOM, Commander Keen, Rise of the Triad, Epic Pinball, Jill of the Jungle, and Duke Nukem back then. These are all DOS shareware games.

      I used a lot of DOS shareware applications for other things. AsEasyAs and GalaxyWrite got me through a lot of my university physics program. I analyzed lab data in AsEasyAs (because the old saying is "as easy as 1-2-3" ... and Lotus 1-2-3 was a popular commercial spreadsheet ... get it?) and wrote class papers in GalaxyWrite (not as powerful as WordPerfect, but great for papers). I also remember a bunch of other DOS shareware applications but can't remember their names anymore: a modem-terminal program, an equation solver, etc.

    2. Re: Downloading DOS shareware by Anonymous Coward · · Score: 0

      Plenty of apps use the shareware model. Download a limited version (usually with ads) for free. Pay for all features and no advertisements.

    3. Re:Downloading DOS shareware by Nethead · · Score: 1

      The comms program was TELEX.EXE. Now cloned for *nix in minicom. I loved that software. My shell for DOS was Norton Commander (NC.EXE) and still use it to this day when I'm on my DOS box programming old Motorola radios and burning EPROMS.

      --
      -- I have a private email server in my basement.
    4. Re: Downloading DOS shareware by Jim+Hall · · Score: 1

      Plenty of apps use the shareware model. Download a limited version (usually with ads) for free. Pay for all features and no advertisements.

      Except that the model you describe is missing "you could share that limited version with anyone." Apps don't have an ecosystem where one user can share the app with someone else.

    5. Re:Downloading DOS shareware by Jim+Hall · · Score: 1

      The comms program was TELEX.EXE. Now cloned for *nix in minicom. I loved that software.

      That was it! I loved Telex too. Great program.

    6. Re:Downloading DOS shareware by Scoth · · Score: 1

      I don't usually do the "internet pedantry" thing, but I have to correct you to Telix. ;) Only because I still use it pretty often for various geeky things that aren't all that interesting and I have a lot of very fond memories of it. It was one of the very few shareware applications I registered as a kid - I didn't have a lot of money but I got a lot of use out of it.

    7. Re:Downloading DOS shareware by Nethead · · Score: 1

      Correct you are sir. I must have confused it with the early form of teletype email using the PSTN and the 910 area code.

      --
      -- I have a private email server in my basement.
  12. kill fucking DOS by Anonymous Coward · · Score: 0

    DOS needs to just fucking die. DOS was a piece of shit when if was first released, and has remained a piece of shit.

    MS-DOG cost software development and entire decade of innovation because it was such a piece of shit. And if I see a company is still using a piece of shit software that uses it, fuck them; unless they're paying $1000/hour or paying me to rewrite it--fuck no I'm staying far away from those motherfuckers. Just NOPE!

    1. Re:kill fucking DOS by Anonymous Coward · · Score: 0

      I know of a couple of retailers still using it for line of business applications. It works and has worked well for decades so why replace it now? If they had replaced it every once in a while they would have already rewritten it several times. First as a GUI application, then VB, then .NET, then Java, then .NET again, then as a web app, then as a web 2.0 app, then as a mobile app, and then as a responsive web app. Or they could just continue using what works and payed much less. Eventually they might rewrite it of course, but I see no reason why they would have to replace it any time soon for no reason.

  13. Downloading? by Anonymous Coward · · Score: 0

    Back in the day you didn't download DOS shareware, you traded floppy diskettes with friends or purchased them via mail order. Damn kids and your internet nonsense.

    1. Re:Downloading? by Anonymous Coward · · Score: 1

      BBS.

    2. Re:Downloading? by tepples · · Score: 1

      Sneakernet was often cheaper than what AT&T was charging for a long distance call to a BBS in the next city.

    3. Re:Downloading? by Scoth · · Score: 1

      I guess I was fortunate that I always lived in pretty big cities back in the day, so I never had a shortage of local BBSes to call. Although I did cause some family drama that I still get reminded of to this day when my little sister broke her wrist at gymastics and spent several hours in the hospital alone because I had the phone lines tied up and had *70'd despite being told not to.

      There are actually a handful of dialup BBSes left that I still call now and then, and long distance is no longer a problem with Google Voice. It's fun.

  14. Modern DOS by Jim+Hall · · Score: 4, Insightful

    I am seizing Control of this article and asking Hey, Slashdot, if there were a modern DOS, what would it be like?

    I know you're posting as an AC so probably won't get seen, but I'll reply anyway because it's an interesting question.

    In short, you get Linux.

    We discussed this in great depth in various places, and if you try to project a "modern" DOS to today, you end up with a 32-bit multitasking kernel that provides native networking and hardware abstraction. You lose binary compatibility; applications written for the newer "modern" DOS won't run on, say, MS-DOS 6. But that wouldn't be surprising; many programs written for MS-DOS 6 wouldn't run on MS-DOS 3, either. You need to provide some method of forward compatibility, of course. To run a "classic" DOS application on the "modern" DOS would require some kind of emulation environment.

    And if you want that, run Linux. Because Linux is a 32-bit multitasking kernel that provides native networking and hardware abstraction. You don't have binary compatibility; applications written for Linux won't run on MS-DOS 6. To run "classic" DOS applications on Linux requires an emulation environment like DOSemu (which requires FreeDOS, by the way).

    Once you break binary compatibility, a "modern" DOS isn't really DOS anymore. What's the point in a "modern" DOS if you can't run classic DOS programs on it? Because that's not DOS, it's something else.

    1. Re:Modern DOS by Blaskowicz · · Score: 1

      Would a modern DOS be something that runs on top of UEFI, or somehow inside UEFI?
      Framebuffer instead of (or in addition to) 80x25, UEFI's mouse instead of DOS mouse driver, etc.
      For all I care it could be single tasking with a flat 64bit memory space.
      It might run on all supported CPU architectures even.
      But you're still stuck with PC speaker and no sound I believe.

    2. Re:Modern DOS by Anonymous Coward · · Score: 0

      I am that AC. Saw it. Good answer!

    3. Re:Modern DOS by Anonymous Coward · · Score: 0

      Would a modern DOS be something that runs on top of UEFI, or somehow inside UEFI?
      Framebuffer instead of (or in addition to) 80x25, UEFI's mouse instead of DOS mouse driver, etc.
      For all I care it could be single tasking with a flat 64bit memory space.
      It might run on all supported CPU architectures even.
      But you're still stuck with PC speaker and no sound I believe.

      UEFI will be difficult for FreeDOS, I think. FreeDOS - like any DOS - requires BIOS services to operate. That's part of what makes it DOS. But more and more UEFI implementations do not provide legacy BIOS services. It's just UEFI.

      Maybe a modern DOS would support UEFI, but I think that would add a lot of bloat.

  15. Freedos rocks! by Lumpy · · Score: 5, Interesting

    The number of older CNC machines I have kept running because of Freedos is huge. I have made a shto-ton of cash on smaller machine shops where "professional" IT companies have told them that they cannot fix the control system for their CNC machines.

    I come in at $95 an hour and make it work again, custom is elated and trash talks the "professional" company that said it was impossible, I get more calls to fix more from other companies they spread the world on... Rinse and Repeat.

    This was 10 years ago when I was almost doing 2-3 CNC repair jobs a week. Now it's maybe one every 2 months, and I don't even do IT professionally anymore.

    --
    Do not look at laser with remaining good eye.
    1. Re:Freedos rocks! by Jim+Hall · · Score: 1

      I'm commenting elsewhere on this article, so I don't have mod points. But if I did, I would mod you up. Thanks.

    2. Re:Freedos rocks! by sumdumass · · Score: 4, Insightful

      I've seen similar experiences. It is often cheaper to fix the older CNC equipment than to replace them by hundreds of thousands of dollars. - Even if it happens several times.

      Of course once the machine itself starts breaking and costing money , replacing it might be more attractive. But if it is software or computer hardware related, it is a no brain'r to keep it chugging along instead of replacing them.

    3. Re:Freedos rocks! by Anonymous Coward · · Score: 1

      Another great component for keeping old CNC and manufacturing systems alive is the HxC2001 or GoTek floppy emulators.

    4. Re:Freedos rocks! by Anonymous Coward · · Score: 0

      Very much so. I've also used it for my own projects. I like the idea of using linux for these but there's just something about the simplicity of dos that seems to make it superior for hardware control and similar things. I would rather spend my time telling the hardware what to do rather than googling for obscure scripting bugs or fighting my way through several layers of OS.

  16. It was to half-assed to have a future by Casandro · · Score: 2

    After all, Microsoft and the DOS community messed up to many points badly. For example the "driver" concept was basically unused. Few people ran ansi.sys because it meant sacrificing a ridiculous amount of RAM. That's why most software had to access the hardware directly, even for primitive things like coloured text.
    Also there was the problem of not having a compiler coming with the operating system which meant that there was no free software movement. People actually sent out binary files. So every software was restricted to a narrow band of hardware.

    Essentially there is now the need for a "new DOS". It would run on hardware like STM32-class microcontrollers which have (much) less than a megabyte of RAM and no memory management.You'd start off with decent lightweight hardware abstraction, then add a file system as well as simple version of the usual UNIX tools. Once you have an editor and a shell you'll have a decently working system which can be used for all kinds of things.

    1. Re:It was to half-assed to have a future by i.r.id10t · · Score: 1

      I recall plenty of code being printed in magazines - either computing magazines in "learning to program" articles, or in other publications like Dragon Magazine (a few character generators, a map generator, etc). But was it Free ? Probably not, at least by the current definitions. But you had access to the source....

      --
      Don't blame me, I voted for Kodos
    2. Re:It was to half-assed to have a future by Casandro · · Score: 1

      Yes, but only a fraction of people could use those on their PCs, as MS-DOS didn't come with an actual development system. Most people had to get Turbo Pascal or something separately.

    3. Re:It was to half-assed to have a future by Attila+Dimedici · · Score: 1

      The reason a compiler did not come with the OS was that Microsoft's main business at that time was SELLING compilers.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    4. Re:It was to half-assed to have a future by Casandro · · Score: 1

      Actually it did come with Microsoft BASIC... which back at that time was the only development environment Microsoft had made.

    5. Re:It was to half-assed to have a future by fizzer06 · · Score: 1
      It came with debug.

      Yes, I'm half kidding, but magazines used to come with code to use with debug to produce small com utilities.

    6. Re:It was to half-assed to have a future by Anonymous Coward · · Score: 0

      Did you actually program on DOS or are you basing your experience on an emulator? To use the ANSI.SYS colors you had to use the DOS calls for outputting text, which used the BIOS calls, which were very slow. The ANSI.SYS calls also required converting what you wanted to accomplish into state machine changes. It was much faster and simpler to write directly to the framebuffer.

      A compiler with MS-DOS? Are you crazy? Not sure if you are suggesting Microsoft (Professional or Quick) C or Basic or Pascal, but each of these came on far more floppy disks than DOS itself and were of virtually no use to anybody since most computer owners were not programmers. And if compilers were readily available nobody would exchange source code at all - DOS came with BASIC interpreters so there was some source code sharing for things like antenna calculation programs. As it happens many computer magazines did print source code listings for programs people could type in on their own through the 1990s, that was a great way for sharing source code pre-internet.

    7. Re:It was to half-assed to have a future by Opyros · · Score: 1

      Strictly speaking, that wasn't a compiler; it was interpreted BASIC.

    8. Re:It was to half-assed to have a future by narcc · · Score: 1

      You had either basica or gw-basic and debug. What more did you want?

      Turbo Pascal was like $400 bucks. I know a few people that had it, but no one that actually paid for it.

    9. Re:It was to half-assed to have a future by Anonymous Coward · · Score: 0

      I had some old magazines and later a very old book of BASIC games (like from 1979 but printed a few years later, with things like Wumpus in it)

      The antique games were easy to get running (but quite often too basic. Simple games for ttys). Those from magazines had to be converted from whatever dialect or machine to someone Qbasic would like. An interesting exercise but I don't think I ever really succeeded.

    10. Re:It was to half-assed to have a future by goose-incarnated · · Score: 2

      Yes, but only a fraction of people could use those on their PCs, as MS-DOS didn't come with an actual development system. Most people had to get Turbo Pascal or something separately.

      Don't forget debug.exe :-)

      As a student a completed a fairly lengthy (6-month fulltime) programming assignment using only DOS debug.exe on a 386. As I remember it, by the time I was done I had much of a proper OS completed within the program: rudimentary scheduler, index for files (floppies were very very slow), primitives for text-based widgets (writing directly to the frame-buffer) and even a working mouse cursor and left button.

      I will seriously consider suicide if I'm ever again forced to use a crippled assembler like that...

      --
      I'm a minority race. Save your vitriol for white people.
    11. Re:It was to half-assed to have a future by Anonymous Coward · · Score: 0

      > Microsoft BASIC... which back at that time was the only development environment Microsoft had made.

      Complete nonsense. Before MS-DOS/PC-DOS Microsoft was a languages company. It made BASCOM(1977), MS COBOL (1978), MS FORTRAN(1977) and MS Pascal (1980) for CP/M. These were ported to DOS for the release of the IBM-PC.

    12. Re:It was to half-assed to have a future by HBI · · Score: 1

      Not going point by point for everything here but:

      ansi.sys: dvansi.com was the cure for that hunk of excrement. Faster, smaller, and no dependency on Desqview, but cooperated with it.

      Colored text: The BIOS would do this just fine via int 10h, which is not writing directly to the hardware. You paid a price in speed for that, which is why people would write directly to B000: (mono) or B800: (color) to get faster output.

      RAM use: On the previous point you were saying hardware support was an issue, but the reason why it was an issue was that DOS itself basically didn't drive hardware. DOS used the BIOS functions to do almost everything it did. All disk functionality was done in the BIOS, as was keyboard input. Video too, to the extent DOS supported video in its API (it only did mono TTY).

      If you wanted to drive hardware in DOS, it would have been a much larger kernel, and with 1MB - (128 to 384KB) to work with...so there's your reason why it never did. Larger kernel means fewer programs would run in the residual address space. Most applications from the later days of DOS assumed ~500k available to even load initially.

      Compiler: If you remember the compilers from then, you'd be stuck with a POS compiler with legacy code in abundance. Maybe a better outcome than now, but probably worse. Are you familiar with the Turbo Pascal Runtime Error 200 plague? Faulty timing code resulted in anything running over 200mhz barfing on TP compiled code.

      --
      HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
  17. Shareware? Met Justin Boyan summer of '89 at CTY by smchris · · Score: 1

    He wrote a modem program on his dad's computer as a teenager and it was very successful as shareware. The shareware system worked for more than one certain crazy antivirus guy.

  18. Jim Hall by Anonymous Coward · · Score: 3, Interesting

    I have had the pleasure of corresponding with, and occasionally collaborating with, Jim Hall a few times over the years. He's not just active in the open source community, he's a really nice guy. Easy to work with, friendly and helpful. We've exchanged notes about package management, he's sent some patches to a project I was working on to make it more user-friendly (and DOS compatible). Jim manages to make a technically focused OS while being pleasant to work with. More open source project leaders could learn by his example.

    1. Re:Jim Hall by Jim+Hall · · Score: 2

      I have had the pleasure of corresponding with, and occasionally collaborating with, Jim Hall a few times over the years. He's not just active in the open source community, he's a really nice guy. Easy to work with, friendly and helpful. We've exchanged notes about package management, he's sent some patches to a project I was working on to make it more user-friendly (and DOS compatible). Jim manages to make a technically focused OS while being pleasant to work with. More open source project leaders could learn by his example.

      This made my day. Thanks, whoever you are!

  19. Corporate? by wisnoskij · · Score: 1

    Sure, the game angle is there, but what I was wondering about is how many people use FreeDOS to keep 20 year old DOS programs running for business and/or government.

    --
    Troll is not a replacement for I disagree.
  20. DOS for programming old radio equipment by Anonymous Coward · · Score: 0

    As a ham radio operator that often comes across legacy radios being decommissioned, I've used DOS many times in the past 5 years to reprogram commercial radios to amateur frequencies. I don't remember if it was FreeDOS or an ancient saved copy of Novell DOS, but without DOS those radios would likely have gone in the trash bin.

  21. BASIC by Anonymous Coward · · Score: 0

    I still use several BASIC programs I wrote in 1978-84 on CP/M and DOS confusers, in my business everyday right this second. I figure those crusty old programs have earned me over $2m. /smile/

  22. Memories by tbuskey · · Score: 3, Insightful

    I got my engineering degree with DOS. Everyone was issued a Z100 (non msdos!) with an 8088, Fortran and Basic. Some other programs such as CAD, PC-TeX were available. Russ Nelson worked at my college and created Freemacs, the word processor and the spelling checker and many other utilties in use at Clarkson

    Some classes gave you a VMS or Unix account. When it was in heavy use at the end of the semester , it was faster to edit in DOS and upload than to scroll down the file in VMS. The DOS FORTRAN didn't have the extensions or libraries. Sometimes its math wasn't as accurate.

    After I got a 286 and had gotten a Unix account (w/ Usenet access), I started trying to learn Unix things. Turbo C, GNUish utilities, Freemacs, Elvis and shell clones helped me. Minix was almost as helpful.

    A 486 w/ 8mb lead to Linux replacing DOS and work as a Unix sysadmin. The DOS intro to C, awk, vi, lex, yacc (via "The Unix Programming Environment" was extremely helpful. Linux at home helped me continue learning. It could single task better than my Sparcstation 1+ running SunOS.

    The 8088, 80286 and 486 systems probably cost ~ $5k each back in the day where a Unix workstation was ~ $20k if you could get one.

  23. Sun Tzu's The Ancient Art Of War by Anonymous Coward · · Score: 0

    Oh, man, I remember visiting a friend with an XT (the 4.77MHz 8088 you mention), who had a game called The Ancient Art Of War where you set up your army and an exciting (and amusing) battle would commence in all its green glory (mono monitor)! I took a copy home, put it on my 20MHz 386 IBM PS/2, started a game... and it was over before I could blink. Whether there was some keys that could slow the game down, I could not find out as there was no time to press anything...

    1. Re:Sun Tzu's The Ancient Art Of War by nukenerd · · Score: 1

      I was recently going through a stack of old floppies (yes I still have a FDD) on my 2.66 GHz PC and found a railway signalling simulation, done in ASCII graphics. It simulated a day of traffic covered in about 2 hours as I recall. I started it in a DOS VM and for a few seconds the screen was agitated and the PC speaker squawked blue murder, and then it stopped with a message on the screen that I was a lousy signalman and I was sacked! My day as a signalman was over.

  24. DOS shareware by Anonymous Coward · · Score: 0

    "memories about downloading DOS shareware applications"
    Downloading? You bought a disk from a rack at a computer store, drove home, inserted the disk into your floppy drive and ran it. Unless you were one of those early adopters with a modem to access a BBS (bulletin board system - look it up, kids)

  25. Downloading? What's that? by Anonymous Coward · · Score: 0

    "I'd be curious how many Slashdot readers have some fond memories about downloading DOS shareware applications."

    Downloading? How about just passing around 5.25" floppies????

  26. I used to run MS DOS 6.2 by Gumbercules!! · · Score: 4, Funny

    but last time I booted it up, it upgraded itself to Windows 10

  27. That why it was great. That's the D in DOS by raymorris · · Score: 2

    > DOS was terrible. Single user and no security what-so-ever.

    Before DOS, there were multi-user network operating systems. Which ran on $100,000 computers. Getting rid of the multi-user and network (and the therefore the need for security) to make a DISK Operating System rather than a network OS allowed to to run on PERSONAL computers. That was awesome. Then the internet happened.

    1. Re:That why it was great. That's the D in DOS by Anonymous Coward · · Score: 1

      Before DOS, there were multi-user network operating systems. Which ran on $100,000 computers. Getting rid of the multi-user and network (and the therefore the need for network security) to make a DISK Operating System rather than a network OS allowed to to run on PERSONAL computers. That was awesome. Then the internet happened.

      FTFY.

    2. Re:That why it was great. That's the D in DOS by Anonymous Coward · · Score: 0

      > Before DOS, there were multi-user network operating systems. Which ran on $100,000 computers.

      One of those was Digital Research MP/M, which ran on 8085 and Z80 in 1978 and ran CP/M software multiuser. DRI also had DR-NET to network these machines together. It ran on 'PC class' computers with the addition of banked RAM. It also could use hard disks. MP/M-86 ran on 8086/8088 'PC class' machines before MS-DOS was even released.

      There were several other PC class multiuser OSes, including Turbo-DOS which used a Z80 board for each user.

      I have here a couple of Polymorhic machines from 1978 that ran a multiuser BASIC system on a single 8080 with 48Kb RAM and two 8inch 1Mb disks. $100,000 machines were not required.

      MS-DOS 1 on an IBM 5150 (I have a model B here) was a pathetic toy compared to what else was available. It even had a cassette port for loading programs. CP/M and CP/M-86 (and others such as TheOS) were mature systems that supported hard disks (which had to wait for MS-DOS 2 and PC-XT) and much business software (some of which was ported to MS-DOS).

    3. Re:That why it was great. That's the D in DOS by Anonymous Coward · · Score: 0

      > to make a DISK Operating System

      CP/M was a DISK Operating System on personal computers several years (1975) before Seattle Computers cloned it and licenced it (later sold it) to Microsoft. There were several others as well. Even Apple II (1978) was a DISK Operating System. IBM PC and MS-DOS didn't support hard disks until version 2 and the PC-XT, while other PC systems had them for years.

      > Then the internet happened.

      and Microsoft nearly missed it. They then tried to bypass it. Windows 95 initially came standard with _no_ internet access at all, but could connect to the original MSN which was a private, Windows 95 only, network that Microsoft controlled and attempted to replace the internet with. It completely failed because third party software was available and many OEMs included it. Later MS had to release the Plus+ pack which gave internet access and this was included in OSR2.

  28. dosemu by Anonymous Coward · · Score: 0

    I still use dos every month to run one set of hybrid scripts in foxpro2.6 for dos.
    it loads FAST, doesn't puke, and makes me money

  29. FreeDOS is needed even today, but... by Brane2 · · Score: 2

    ...just for historical reasons.

    It is absolutely awesome to have when you simply need to run some old program, which is in my case usually bound to some piece of old, but still useful HW, like chip programmer, some old measurement or CNC equipment etc. Or perhaps for analysis of program behaviour in order to do modern reimplementation. Or to enjoy nostalgia trip with some old DOS game...

    WRT to FreeDOs development, I don't think it's needed outside integration into modern OS & HW, like having modern drivers for mouse and optical unit, USB useage for printing, nice, antialiased fonts, good high, EMS etc memory manager etc. I/O virtualisation of some sort would be great, so I can, for example have virtual LPT port that would be seen on desired I/O port address and connected to some real LPT port somewhere entirely else or even to USB driver or some userland program through pipe etc.

    I don't think susbtantial, grand scale reworks like 32-bit and 64-bit implementation, multicore and multitasking are neccessary. We have plenty other solutions for that.

  30. i like freedos by FudRucker · · Score: 2

    but it is quite limited in its capabilities, it would be cool if someone ported some basic linux apps to it like iceWM and some basic browser like dillo and a text editor, maybe something for audio/video and grphics editing like mtpaint or xpaint, make it simple and basic like Windows95 was, not too complicated and just enough to make it usable as a bare bones desktop, if i was forced to use commandline only i would just use Linux without Xorg which is more robust and feature right and even has some ncurses apps that are decent

    --
    Politics is Treachery, Religion is Brainwashing
  31. Remembering my batch file days by Anonymous Coward · · Score: 0

    I have a ton of memories from my old DOS days. I miss those days probably more than I should.

  32. Still has its uses... by Anonymous Coward · · Score: 0

    for some older computer bios updates

  33. BIOS flashing by dbreeze · · Score: 2

    I just used FreeDOS to update this old Optiplex a month ago. Much thanks to the developers for keeping a still valuable tool available.

    --
    When the king heard the words of the Book of the Law he tore his robes.2Kings22:11
  34. FreeDESQView? by cmholm · · Score: 1

    I'd think the more "DOS-like" way to multitask would be to launch DESQView from FreeDOS and spawn processes from that. While DESQView can be freely downloaded and passed around, I don't believe Symantec has ever released the source to this bit of Quarterdesk flotsam. Bummer.

    Why more "DOS-like"? DESQView sucks up 150KB, plus 30KB per task. IIRC, about the minimum Linux memory overhead from among the low footprint Linux distros is about 7MB, although perhaps one can do better with Linux From Scratch. But then who's got less than 7MB nowadays? ;-)

    --
    Luke, help me take this mask off ... Just for once, let me butterfly kiss you with my own eyes.
  35. Useless shit. by Anonymous Coward · · Score: 0

    You can manipulate any DOS storage with any Linux or BSD.

    DOS and everything Windows/Microsoft can go in the shitter. DOS wasn't spyware, that is it's only plus.

  36. FreeDos is not DOS by rcharbon · · Score: 1

    Lord knows no one but me cares, but FreeDOS is not always a good substitute for DOS. I had to work around a BIOS upgrader that insisted on a good battery in a laptop, even when the laptop was plugged in. The workaround involved running the installer from a DOS boot drive, and FreeDOS didn't work. I had to scrape up a Win98/DOS boot drive, but at least I could boot from USB, so I didn't have to go back all the to cave drawings (or floppies).

  37. Problem solved w/ FreeDOS by partofthepuzzle · · Score: 1

    A few years ago, I had gig that involved helping a company sell approx 600 hundred still-useful PCs. The catch was that they all had to be shown to in good working order to the buyers. Of course the drives were all wiped and licensing issues preventing them using Windows, so the easy solution was to install FreeDOS. Super fast install and they could all be shown to be bootable and in good working condition.