Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
GNU is Not Unix Open Source Operating Systems

Interviews: For the 25th Birthday of FreeDOS, Ask Its Founder A Question (freedos.org) 94

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 Computerworld's 2016 interview with FreeDOS's founder and project coordinator, Jim Hall. "I packaged my own extended DOS utilities, as did others," he explains on the FreeDOS web site, "and we found other public domain or open source programs that replaced other DOS commands."

But that was back in 1994, when Jim Hall was still a college student. He went on to spend 11 years as a CIO in local government and the public sector, and served a year on the GNOME Foundation's board of directors. Now it's been 25 years, and as a prominent free software advocate, Hall contacted Slashdot to remind us that the FreeDOS Project "will turn 25 years old on June 29, 2019. This is a huge milestone for any open source software project, and especially for an open source DOS project."

So in honor of FreeDOS's 25th birthday, he's agreed to answer the 10 best questions submitted by Slashdot readers. Leave your questions in the comments. (Ask as many questions as you'd like, but please, one per comment.) We'll pick the very best questions and forward them along for answers.

What else has Jim been up to? "I've decided I want to focus on coaching, advising, and mentoring IT Leaders," explains his page on the FreeDOS site. "I am starting an IT Executive Consulting practice, IT Mentor Group LLC, to help IT Leaders with strategic planning and organizational turnarounds. I am really excited for this new opportunity. It's not every day that you start your own business!"

Jim Hall is also Slashdot reader #2,985...

"Jim isn't rich or famous," wrote RobLimo back in 2000, "just an old-fashioned open source contributor who helped start a humble but useful project back in 1994 and still works on it as much as he can." At this URL you can read the questions he was asked by Slashdot users in 2000 -- and the answers he gave, just six years into the FreeDOS project.

Then leave your own best questions in the comments below -- one question per comment -- and we'll send them along to Jim to answer for the 25th anniversary of FreeDOS.
This discussion has been archived. No new comments can be posted.

Interviews: For the 25th Birthday of FreeDOS, Ask Its Founder A Question

Comments Filter:
  • by UnknownSoldier ( 67820 ) on Monday June 10, 2019 @05:39AM (#58738280)

    How hard was it to add support for Long Filenames (DOSLFN) and what were the lessons learnt?

    Thanks for making FreeDOS!

  • Motivation (Score:5, Interesting)

    by Camembert ( 2891457 ) on Monday June 10, 2019 @05:43AM (#58738286)
    What keeps you motivated to work for so long on this project (no criticism intended) while there are so many fascinating newer technologies to work on instead?
  • Best use of FreeDOS (Score:5, Interesting)

    by iampiti ( 1059688 ) on Monday June 10, 2019 @05:55AM (#58738304)
    What's the, in your opinion, best use you've seen of FreeDOS (most surprising, most useful...)?
  • by Anonymous Coward

    After getting out of the mainstream DOS lived on, mainly in embedded systems with minimal hardware or low resources. Anything embedded today is dominated by ARM designs, running in hardware much more powerful than required by DOS back in the day.

    With Ghz CPUs and GB RAM costing so little today, have DOS at long last lost its purpose?

  • by Anonymous Coward

    FDPP aims to be the DOS used for DOSEMU. Basically a protected mode way of running DOS. Have you looked at the project ?

  • by Anonymous Coward on Monday June 10, 2019 @06:44AM (#58738392)

    FreeDOS, as I understand it, is meant to be compatible with MS-DOS 6. Is it tricky to maintain this legacy compatibility while also trying to improve, or modernize, FreeDOS? I see a lot of utilities are developed for the OS and I'm guessing you get a lot of requests to port FreeDOS to modern CPUs, or add advanced features. So how do you decide what can go into FreeDOS and what is kept out to maintain backward compatibility?

    Thanks for making FreeDOS. It and related projects have kept a handful of classic DOS applications and games running for me for years.

    • DOS isn't that complex of an OS. There are no drivers per say only TSR which often add common controls for a mouse. But DOS mostly just handles the raw machine code, and depending if it is an exe or com file will split the memory command into chunks so larger programs can be run.

      During the golden days of DOS Games, we went up VGA 320x200 265 color graphics because that was the last fully standard video card, SVGA started having variances in their standard making difficult for MSDOS to handle.

      But for many

      • But trying to make DOS to support 64bit multi-core CPU's with Gigs of RAM, and Terabytes of disk space while possible, will cause problems later on. Unless it is designed to be more complex, then it wouldn't really be DOS anymore, and you would need DOSBox for your DOS environment ro run you old DOS Apps.

        Multi-core I understand, since DOS is a single CPU OS. But why would a simple extension of the code from 16 to 32 or 64 bits be problematic? Keep the 16-bit part of it as is, so that it can still run on a PC from 1989, but add maybe a 32-bit version based on just, say, the 386SX instruction set (assuming here that DOS doesn't need a 387) and a 64-bit version based on the first Athlon-64 CPU (not using the instructions that are different b/w Intel and AMD). On these longer versions, have support for 4GB o

        • Add a few things like long filename support, Powershell commands and so on.

          I like your thinking, with PowerShell, but there's a ton of .NET underneath each cmdlet that would make porting all but impossible. Sure, you could edit COMMAND.COM and alias gci and ls to dir, but that's about it, barring one heck of a DOS extender.

  • Corporate support (Score:2, Interesting)

    by Anonymous Coward

    FreeDOS is still in use for some firmware updaters, or is a practical way to run some DOS-based updaters. So, did it bring you any nice corporate support, whether it was patches, man-days or just money to improve or maintain FreeDOS?

  • Back in the '90s and early millennium, I could see the need for FreeDOS and appreciated the passion you put into now.

    Now, with Linux being very mature and having CLI only options (including WINE) for minimal system footprints, does it make sense to continue with FreeDOS?

    If it does, could you explain why and when, if ever, you can see support ending for FreeDOS?

    Thanx.

    • by Anonymous Coward

      WINE is only a compatibility layer for Windows, for DOS applications you need something like FreeDOS. It works very well if you want to play games from the 1980s or early 90s. There are plenty of games on places like gog.com that actually ship with FreeDOS so they're playable on modern systems. It's also pretty useful for bootdisks to install firmware updates.

    • Now, with Linux being very mature and having CLI only options (including WINE) for minimal system footprints, does it make sense to continue with FreeDOS?

      Statistically nobody is using DOS because it's small. They're using it for DOS compatibility. You could run Unixlikes on a 286! I used to have a 286@6MHz with 1MB of RAM and a 40MB RLL disk, and I ran Xenix 2.3.2 on it as a UUCP node. It was flawless, literally never giving me so much as a moment's grief.

      • by Anonymous Coward

        Hmmmm.... sounds like an old AT&T6300 vintage computer I used to have. It actually had a problem running DOS because the timer chip wasn't generating interrupts at exactly the same number of interrupts per second that DOS expected every computer to have.

  • by Anonymous Coward

    Since you started very early in the history of personal computing, have you noticed a degradation of coding 'cleverness' (for want of a better word), as hardware processing capabilities, network speeds, and power consumption increased ?

  • What Next (Score:5, Interesting)

    by markmay ( 557326 ) on Monday June 10, 2019 @07:18AM (#58738478) Homepage
    What do you see next as the direction for FreeDOS? Anything specific you'd really like to add?
  • by Anonymous Coward

    What commercial uses (of any) of FreeDOS are you aware of? For example, driver update disks.

  • Languages (Score:5, Interesting)

    by AmiMoJo ( 196126 ) on Monday June 10, 2019 @07:36AM (#58738540) Homepage Journal

    It looks like FreeDOS is mostly C and assembler. Have you been tempted to move to C++, or any other language?

  • With Operating Systems likely to be moving to the Cloud (Microsoft has already indicated that they are going to do this), do you see locally run full OSes to have no future? Will most people migrate to a cloud-based operating system?

  • Microsoft (Score:4, Interesting)

    by Anonymous Coward on Monday June 10, 2019 @07:58AM (#58738620)

    How has Microsoft responded to your project over the years?

    • by Anonymous Coward

      I've had to go in hiding, keeping the shades drawn on my homes and
      traveling with Groucho Marx disguise glasses and nose, which is difficult
      at airports. It's especially hard on the wives since they really don't like
      using the same disguise (women). The kids are dressed as young Bill
      Gates (even the girls) since it's assumed that Bill won't go after someone
      who looks like him, but then I remember what he did to Ballmer and cringe
      at the possibility. It's been a scary life to say the least. My best bud, J.O.,
      w

  • by Anonymous Coward on Monday June 10, 2019 @08:06AM (#58738644)

    DOS relies on code built into the BIOS, and BIOS is starting to become unavailable in newer hardware. I noticed the last motherboard I bought was UEFI only. The FreeDOS website says that FreeDOS cannot emulate BIOS.

    So what's the long term plan for FreeDOS? Will FreeDOS die, or will it only run on older systems that support BIOS, or inside a VM?

    • If I had to guess, and I do because we don't have the answers yet, I'd guess that most use of FreeDOS is inside of VMs.

      I'd further guess that most non-VM use of FreeDOS is on antiquated hardware, the kind of hardware they'll simply keep putting BIOS on into the future. You know, passive backplane motherboards, PC-104-bus embedded PCs, that kind of thing.

  • by puddingebola ( 2036796 ) on Monday June 10, 2019 @08:25AM (#58738706) Journal
    Will I be able to get support for my AdLib sound card to work in Dune II?
  • by drinkypoo ( 153816 ) <drink@hyperlogos.org> on Monday June 10, 2019 @08:36AM (#58738764) Homepage Journal

    Who are the most numerous users of FreeDOS? Is it gamers, or industrial control, or some other group I haven't imagined?

    • by musicon ( 724240 )
      I've seen FreeDOS in elevators and drive-through order screens, but I imagine most of those will be migrating to Linux.
      • I've seen FreeDOS in elevators and drive-through order screens, but I imagine most of those will be migrating to Linux.

        As long as you can get rugged PC hardware about as cheap (or cheaper!) than non-PC rugged hardware, DOS will continue to be viable for such simple tasks.

  • by JoeyRox ( 2711699 ) on Monday June 10, 2019 @08:39AM (#58738772)
    Thanks for answering.
  • by blind biker ( 1066130 ) on Monday June 10, 2019 @09:20AM (#58738946) Journal

    Have you tried to contact the companies that hold the rights to classic DOS tools like Norton Commander, Norton Disk Doctor, PC Tools, DiskDupe, Laplink etc? Maybe some would be willing to release their old DOS software as a goodwill gesture?

  • Just wondering, as hardware has advanced, have there been a lot of times where some new notionally-compatible CPU just totally breaks things and you have to tweak things to make FreeDOS run on it?

    (Also, what's it like to have a Slashdot ID under 3,000?)

  • by Grog6 ( 85859 ) on Monday June 10, 2019 @11:05AM (#58739518)

    I'd like to start with saying Thanks!

    My question: Is there a way to keep the DOS tradition, in a hardware world that is increasingly divorced from the actual hardware?

    Ex: An IBM PC in 1984 has BASICA in ROM, and you could write applications out of the box, to do actual hardware operations, even if they crashed.
    Now, there's is no standard hardware/software support included with any operating system that doesn't require elaborate drivers to function, and no impetus to write drivers for old or otherwise unsupported hardware.
    The latest OS with support for some of my cards was Linux, and that ended in 98 or so; and driver virtualization and timing skews don't really allow mutitasking type OS'es to work anyway.

    FreeDOS still works fine, however. :)

    I still run old hardware, mostly to use some data acquisition hardware that either no longer exists, or would be incredibly expensive to replace.

    I have various setups doing research, that take data continuously, and have been running for years.

    Some of the hardware will run under Win95 or 98, but for solutions that are timing sensitive, DOS is still the best.

    I've found that different old DOS versions all have their quirks, so standardizing on FreeDOS makes things simpler, and if I have to help someone out with old hardware, there's no licensing embuggerences to deal with.

    Setting up EISA hardware Requires DOS, of some flavor, as well as most Adapted SCSI raid setups, so this won't go away until the hardware does.

  • by ctilsie242 ( 4841247 ) on Monday June 10, 2019 @11:19AM (#58739580)

    First, I want to thank the people who have kept FreeDOS going. FreeDOS is a great embedded platform, and with some basic C coding, it can be used to handle realtime applications with ease. For a very limited environment, writing code and using libraries to use FreeDOS as a RTOS is a useful thing.

    One thing that would be nice to see. Something like DoubleSpace/DriveSpace/Stacker implemented. The patents on these things have long since expired, and it would be nice to have some volume compression, especially in some embedded environments where space is at a premium.

  • How much commercial support have to had for FreeDOS? By that I mean code contributions from businesses, financial support for yourself, that sort of thing.

  • Temptations (Score:3, Interesting)

    by kansas_plainsman ( 4837391 ) on Monday June 10, 2019 @11:40AM (#58739712)
    Did you get tempted to incorporate features like multitasking into DOS?
  • There needs to be a very strong motivation, or even more than just one, among the freedos team to make this project so far and beyond.
    Please, explain them to us all.

  • One of the limitations of DOS back in the day was the 640kB limit. There were things like DOS extenders and so on, but essentially, since the OS was built on a 286, it was 16 bit and that was it: hence the memory limitations.

    Has it ever been contemplated extending the OS to either 32 or 64 bits since we had several generations of x86 CPUs? Maybe a 32-bit version w/ just the 386 instruction set and maybe a 64-bit version w/ either the AMD64 or Intel 64 instruction sets? Something where one could still d

  • What's the biggest deployment or use for FreeDOS that you are aware of? And what would you say the current active use cases this is being deployed today, in 2019?

  • by Anonymous Coward

    Did you ever face burnout, or troubles relating to dealing with thousands of requestsnfrom users, and how did you cope?

  • How are your cats doing, and how do you keep them off of your keyboard?

  • Hello,

    A few questions, if I might:

    1. What is the largest installed single-base or use of FreeDOS of which you are aware?
    2. What is the most novel, interesting and surprising use of FreeDOS that you have seen, so far?
    3. What was the most difficult part of MS-DOS (or PC-DOS/IBM-DOS) to support in FreeDOS?
    4. What is the most frequently-requested feature or add-on you hear about for FreeDOS
    5. What would you like to see the FreeDOS Project become in the next 5 years? What about the next 25?

    Thank you for taking the time to

The "cutting edge" is getting rather dull. -- Andy Purshottam

Working...