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 403432
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: It is a pity...
by marcp on Sun 10th Jan 2010 17:05 UTC in reply to "RE[4]: It is a pity..."
marcp
Member since:
2007-11-23

FreeDOS maybe? it's free and open.

To me it's all about the knowledge - you just have to know about alternatives, or you will gonna pay some ridiculous amount of money, which is unneeded in most cases.

Reply Parent Score: 1

RE[6]: It is a pity...
by Andre on Sun 10th Jan 2010 20:43 in reply to "RE[5]: It is a pity..."
Andre Member since:
2005-07-06

I suppose FreeDOS is a better option in this case. At least, when your DOS software requires direct hardware access, it's not advisable to run it within a multitasking enviorement.

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.

Reply Parent Score: 1

RE[7]: It is a pity...
by Thom_Holwerda on Sun 10th Jan 2010 21:27 in reply to "RE[6]: It is a pity..."
Thom_Holwerda Member since:
2005-06-29

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.


That's wrong. My copy of eCS 2.0 has Windows 3.x built-in. You don't need a separate copy.

Reply Parent Score: 2

RE[7]: It is a pity...
by frajo on Sun 10th Jan 2010 23:14 in reply to "RE[6]: It is a pity..."
frajo Member since:
2007-06-29

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[7]: It is a pity...
by rcsteiner on Tue 12th Jan 2010 23:34 in reply to "RE[6]: It is a pity..."
rcsteiner Member since:
2005-07-12

OS/2 Warp 3 was available in four flavors back in the day:

OS/2 Warp 3 - red spined box - required Windows 3.1 if you wanted to run Windows. It would integrate with an existing installation, or you could install Windows later on, even on an HPFS partition.

OS/2 Warp 3 "Fullpack" - blue spined box - came with its own copy of Windows 3.x called WinOS2.

OS/2 Warp 3 Connect - red and blue versions as above plus peer to peer networking, TCP/IP, etc.

The first two just had SLIP and PPP dial-up networking, which wasn't a big deal because very few home users had access to anything requiring ethernet (or other) drivers and hardware.

OS/2 Warp 4 removed all of those variations, and was only available as a fullpack client with full networking support.

In other words, you might've been correct depending on which version of Warp 3 you were talking about. :-)

Reply Parent Score: 2

RE[6]: It is a pity...
by Bill Shooter of Bul on Mon 11th Jan 2010 14:37 in reply to "RE[5]: It is a pity..."
Bill Shooter of Bul Member since:
2006-07-14

FreeDOS maybe? it's free and open.


Oh hell no. I don't mean to be too dismissive, but on to work with CNC machinery? That's not smart. If the whole thing kills itself (which will cost $200,000 to fix), do you really want management to find out that you went with a free solution instead of something guaranteed to work just to save $200?

I'm all about free and open code, as long as the potential damages from non compatibility are less than $200 K. Anything new => Open source. Anything legacy => USE LEGACY SYSTEMS FOR COMPATIBILITY.

Reply Parent Score: 2