On 04/11/2012 12:37 AM, Alex wrote:
Hi
This topic is not about DOS vs other operating systems, or the fact
that users tend to gradually abandon DOS. It's about the survivability
of DOS vis-a-vis hardware.
The starting point for my reasoning is: what will happen with the
future development
On Tue, 10 Apr 2012 22:16:50 -0700, Ralf A. Quint free...@gmx.net wrote:
At 01:13 PM 4/10/2012, Jack wrote:
Cannot answer on all subjects, but re: disk/CD/DVD drivers, I am NOT
overly optimistic! Intel/Microsoft want us all to buy into AHCI,
and they may have started ordering mainboard
The problems, that I was writing about lately, are caused by 4DOS'
tinkering with Timer 0. Ed (DXForth creator) sent to me a little
utility to check out; it's short Forth listing, but most is assembler:
#v+
\ Check current mode of the 8253/4 PC tick timer
\
\ Compile with DX.EXE - INCLUDE GM.F
On Wed, Apr 11, 2012 at 10:07 AM, Jim Lemon j...@bitwrit.com.au wrote:
I have been battling with this for some years, and my colleagues have
to scavenge for old PCs that will run DOS natively.
This is exactly the sort of nightmarish scenario I was worrying about!!
I was hoping that someone
On 4/11/2012 5:21 AM, Alex wrote:
This is exactly the sort of nightmarish scenario I was worrying about!!
I was hoping that someone would point out how foolish my worries were,
but now they appear to be not so foolish after all...
As an end user, your fears are probably foolish. Emulation
Hi Bernd,
it seems even on modern hardware unpacking FreeCOM
during install may take VERY long, so we need a fix:
This seems to be specific to the old installer (v3.7.8 by Jeremy) I
think, as that unpacks entire packages. Sourcecode modification would be
required to add a -x source/*.
1. Its history records empty lines (e.g. when one hits Enter) -
I think, there's no need for that. It should record a line only in
case, when after eliminating blank characters (CR, LF, space...) from
both ends, its length still remains 0.
2. Could it be made to use slash as separator in
Hallo Herr Zbigniew,
am 11. April 2012 um 19:19 schrieben Sie:
1. Its history records empty lines (e.g. when one hits Enter) -
I think, there's no need for that. It should record a line only in
case, when after eliminating blank characters (CR, LF, space...) from
both ends, its length still
Hi,
On Wed, Apr 11, 2012 at 12:19 PM, Zbigniew zbigniew2...@gmail.com wrote:
1. Its history records empty lines (e.g. when one hits Enter) -
I think, there's no need for that. It should record a line only in
case, when after eliminating blank characters (CR, LF, space...) from
both ends, its
2012/4/11, Tom Ehlert t...@drivesnapshot.de:
2. Could it be made to use slash as separator in pathnames, just like
4DOS allows both slash and backslash? Every Linux/BSD user will
appreciate that.
whats supposed to happen on
C:DATE/T
/T is probably an option
DATE\T
probably some
Op 11-4-2012 20:02, Rugxulo schreef:
Users will always need sources, esp. if they share, but they don't
necessarily need to unpack them. (Well, anyways, they probably don't
have all compilers anyways.)
The entire idea of opensource was to be able to modify sources to suit a
person's needs.
Hi,
On Sat, Apr 7, 2012 at 7:12 PM, Michael B. Brutman
mbbrut...@brutman.com wrote:
For hard-core application programming where you need to use a few BIOS
and DOS interrupts I like to use C and C++ (carefully). C gives you a
tremendous amount of control and flexibility.
Open Watcom is open
Op 11-4-2012 20:25, Rugxulo schreef:
(PS: If we have FreeDOS code that doesn't compile under OW I'd be
interested in seeing it. A few #defines can fix a lot of problems. The
debugging is the hard part.)
There is a tcc2wat library by Blair Campbell on iBiblio, if anyone
wants to take a
Freedos may provide pressure if it is popular enough to stay with well
known standard interfaces. If AHCI is going to be a well known
interface and it offers some advantage over SATA, Freedos can have a
driver for it and there is no reason to worry. In environments that are
more time sensitive,
On 4/11/2012 6:14 AM, Michael B. Brutman wrote:
As an end user, your fears are probably foolish. Emulation and virtualization
work fine
for anybody playing with DOS at the application level.
Application-level? But doesn't DOS more or less give an application (nearly)
unfettered access to the
Hi,
On Wed, Apr 11, 2012 at 1:24 PM, Bernd Blaauw bbla...@home.nl wrote:
Op 11-4-2012 20:02, Rugxulo schreef:
The entire idea of opensource was to be able to modify sources to suit a
person's needs. Most people, including me, haven't got enough interest
or experience to be a programmer, but
My personal vote would be for bringing a little more order, I mean:
to suppress recognizing such input as option, if slash is directly
after some string of characters - in such case path recognition
should be assumed.
Problem with that is that I've seen programs that _require_ the options to
On Wed, Apr 11, 2012 at 3:34 PM, Alex alxm...@gmail.com wrote:
Sorry but I still don't find the above comments very reassuring, with
regard to the future usability of (Free)DOS on new hardware. The fact
that we will be able to run DOS in emulators/virtual machines, because
we can no longer
On Wed, Apr 11, 2012 at 10:54 PM, dmccunney dennis.mccun...@gmail.com wrote:
On Wed, Apr 11, 2012 at 3:34 PM, Alex alxm...@gmail.com wrote:
Sorry but I still don't find the above comments very reassuring, with
regard to the future usability of (Free)DOS on new hardware. The fact
that we will
Some DOS *apps* cared and choked on it, so I wrote Korn shell alias
wrappers to reset the option
delimiter char to / before running them, and set it back to - when they
exited.
Like I said, this is why it won't work in the _general_ case. There are
situations and programs where it can work,
On Wed, Apr 11, 2012 at 5:51 PM, BretJ bretj...@juno.com wrote:
Some DOS *apps* cared and choked on it, so I wrote Korn shell alias
wrappers to reset the option delimiter char to / before running them, and
set it back to - when they exited.
Like I said, this is why it won't work in the
On 4/11/2012 1:25 PM, Rugxulo wrote:
Hi,
On Sat, Apr 7, 2012 at 7:12 PM, Michael B. Brutman
mbbrut...@brutman.com wrote:
For hard-core application programming where you need to use a few BIOS
and DOS interrupts I like to use C and C++ (carefully). C gives you a
tremendous amount of
On 4/11/2012 1:38 PM, John Wesley Cooper wrote:
On 4/11/2012 6:14 AM, Michael B. Brutman wrote:
As an end user, your fears are probably foolish. Emulation and
virtualization work fine
for anybody playing with DOS at the application level.
Application-level? But doesn't DOS more or less
On 4/11/2012 2:34 PM, Alex wrote:
Sorry but I still don't find the above comments very reassuring, with
regard to the future usability of (Free)DOS on new hardware. The fact
that we will be able to run DOS in emulators/virtual machines, because
we can no longer boot it, is no reason at all for
Hi,
On Wed, Apr 11, 2012 at 7:30 PM, Michael B. Brutman
mbbrut...@brutman.com wrote:
On 4/11/2012 1:25 PM, Rugxulo wrote:
On Sat, Apr 7, 2012 at 7:12 PM, Michael B. Brutman
mbbrut...@brutman.com wrote:
For hard-core application programming where you need to use a few BIOS
and DOS
25 matches
Mail list logo
