Linked by Thom Holwerda on Sat 9th Jan 2010 22:52 UTC, submitted by poundsmack
OS/2 and eComStation We're already nine days into the year 2010, and yet, eComStation 2.0 has not yet been released. The final release should've been released before the end of 2009, but December 31 came, and no release. Luckily, the eComStation team has released a statement, saying that the final release is definitely around the corner.
Thread beginning with comment 403461
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: It is a pity...
by frajo on Sun 10th Jan 2010 23:14 UTC in reply to "RE[6]: It is a pity..."
Member since:

At least, when your DOS software requires direct hardware access, it's not advisable to run it within a multitasking enviorement.
In the early nineties I used to run DOS games on Warp 3. There was no problem having several different DOS games playing their sounds concurrently with one sound card only. I think this is not any more possible on modern systems.

The Windows enviorement within OS/2 requires, starting from OS/2 Warp 3.0 a copy of Microsoft Windows 3.x.
OS/2 will integrate this windows copy into itself.
(OS/2 2.x had windows support out of the box)

As OS/2 Warp 3+ (and so, eCS since it's based upon OS/2 4.51) requires a copy of windows 3.x, it would be more logical to run that on top of a (MS)-DOS.
No. You don't need a windows licence for any OS/2 or eCS version.

Reply Parent Score: 1

RE[8]: It is a pity...
by Andre on Sun 10th Jan 2010 23:22 in reply to "RE[7]: It is a pity..."
Andre Member since:

games, yeah, but wasn't software mentioned to control specific hardware?

Reply Parent Score: 1

RE[9]: It is a pity...
by mbpark on Mon 11th Jan 2010 00:31 in reply to "RE[8]: It is a pity..."
mbpark Member since:


Yes. If I'm putting something in to run controls programs, I want to make sure that there is a company providing support to me when running their OS on newer hardware.

This is something many people who use Open Source and freeware don't understand. The people outside of IT who make the purchasing decisions usually will not approve the use of obsolete, Open Source, or freeware software to support something really critical (i.e. used in medical procedures) unless there's an ironclad support contract in place. This is why companies like Serenity Systems exist, to support those applications that would cost too much to upgrade. Not all companies are like some of those in the IT world ;) .

In my real job, I do have a lot of open source software in production, including boxes that run CentOS. The only reason we run CentOS is because we have a support contract with a very large multi-national company that puts an engineer in our data center within 4 hours to fix any issues with CentOS, or more importantly, the application on top of it.

I do use FreeDOS at work, specifically for flashing the firmware on Intel NIC cards so I can turn on Adapter Fault Tolerance. However, as good as it is on an HP Proliant DL580 G5, it still gives me some very interesting messages about the PCI buses, so much so that I would never use it in a commercial embedded system.

OS/2 is used in a lot of embedded systems. So is DOS. Serenity Systems provides a fully supported path to running older applications on newer hardware because they provide what companies are looking for in terms of hardware and application compatibility.

I don't get that from FreeDOS. I can throw a rock and hit consultants/support organizations for many limited-use/older/obsolete OSes out there, including VMS, AmigaOS, and the BSDs, but not for that.

This company is positioned very well.

Reply Parent Score: 1