I did have a Mitsumi single speed CD-ROM drive on my massive 20 Mhz
80286 back in 1993. It came with an own ISA interface card, so I think
it probably used some proprietary protocol instead of ATAPI.
Funnily enough that thing did faithful service until 2007 when it
still happily see-sawed inside
On 8/3/2023 11:54 AM, Jerome Shidel via Freedos-devel wrote:
On Aug 3, 2023, at 12:37 PM, Bret Johnson via Freedos-devel
wrote:
Yeah, USB and CD/DVD makes only sense for a 386+ ...
USB, yes. CD/DVD, no. USB requires PCI which in turn requires 386+.
Actually, there were supposedly
> On Aug 3, 2023, at 12:37 PM, Bret Johnson via Freedos-devel
> wrote:
>
>
>>
>> Yeah, USB and CD/DVD makes only sense for a 386+ ...
>
> USB, yes. CD/DVD, no. USB requires PCI which in turn requires 386+.
> Actually, there were supposedly USB host controllers manufactured for the ISA
> Yeah, USB and CD/DVD makes only sense for a 386+ ...
USB, yes. CD/DVD, no. USB requires PCI which in turn requires 386+.
Actually, there were supposedly USB host controllers manufactured for the ISA
bus instead of PCI, but I've never actually seen one. But USB protocols assume
you're
On 8/2/2023 1:30 PM, Jerome Shidel via Freedos-devel wrote:
My stuff for FreeDOS requires only an 8086. The exception being LOGGER which
can run on an 8086. But, I have that functionality turned off at present.
The CD and USB install media need a 386 do to the reliance on grep during
Hi!
There are other base components in FreeDOS, such as CuteMouse that do not
support an 8086.
That should be a almost compile time option. If neither .286 nor .386
are set early in the code, neither USE_286 nor USE_386 should trigger
and you should get an 8086 compatible variant. However,
> On Aug 2, 2023, at 3:05 PM, Rugxulo via Freedos-devel
> wrote:
>
> Hi,
>
>> On Wed, Aug 2, 2023 at 2:29 AM Paul Edwards via Freedos-devel
>> wrote:
>>
>>> FreeDOS should run on 8086, both kernel and shell. If it doesn't,
>>> that's a bug or omission.
>>
>> Are you sure? I thought I was
Hi,
On Wed, Aug 2, 2023 at 2:29 AM Paul Edwards via Freedos-devel
wrote:
>
> > FreeDOS should run on 8086, both kernel and shell. If it doesn't,
> > that's a bug or omission.
>
> Are you sure? I thought I was told that the standard
> distribution relied on an 80386.
Jerome's work on the
> Sure, thanks. Possibly the Book 8088 BIOS is deficient
> and Freedos is relying on that (while MSDOS 6.22 is not).
I thought of another possibility.
I think the Freedos VHD I use was created under Windows 7.
And probably partitioned there too. I can't remember if I
repartitioned it under
Hi Rugxulo.
>> Ok, so an entire toolchain plus OS plus fullscreen editor can be
>> written - what definition of "useful" is being used? That's enough
>> to quite literally rebuild the world.
> I don't know, some people are never satisfied.
> C is a bit of a red herring. (Isn't everything?) ISO
Hi,
On Tue, Aug 1, 2023 at 3:24 AM Paul Edwards via Freedos-devel
wrote:
>
> > However, most people don't care about standards, and even the ones who
> > do don't really think anything "useful" can be written in them. Which
> > is untrue and a shame.
>
> It is only recently - perhaps only a few
From what has been said in this thread,
Linux uses ANSI escape sequences for console
I/O.
But runniing both Linux and (any) DOS in
the same x86 machine is quite common.
So, how is this done ? The BIOS is the
same; is the Linux console driver that
translates keycode into ANSI?
> However, most people don't care about standards, and even the ones who
> do don't really think anything "useful" can be written in them. Which
> is untrue and a shame.
It is only recently - perhaps only a few hours ago - that I started
to have confidence that it was untrue.
Ok, so an entire
> The problem (and the competitive edge for software) is that DOS calls,
> even BIOS and also ANSI sequences are excruciating slow, compared to
> direct hardware access. That was a decisive factor as to why IBM
> prevailed, even though contemporary machines like the Sirius 1 or TI
> Professional
Hi,
On Mon, Jul 31, 2023 at 8:38 PM Paul Edwards via Freedos-devel
wrote:
>
> Yes, if you're prepared to add a curses layer, then you can
> support both the standard, plus non-standard things like
> a PC BIOS. But neither fullscreen application that I actually
> used and care about (microemacs
On 7/31/2023 6:37 PM, Paul Edwards via Freedos-devel wrote:
> Trying to force decades
> old operating systems to match is probably a dead end.
Do you mean started decades ago or ended decades ago?
Both Freedos and PDOS/86 are in active development.
As far as FreeDOS goes, it's goal is to be
On 7/31/2023 6:01 AM, Paul Edwards via Freedos-devel wrote:
I never knew why DOS only had ANSI for output, not input.
That is not co correct. And it wouldn't be as much a DOS issue, but an
issue with the ANSI driver being loaded. Beside the very early days of
DOS, with it originally being
> And this is the first application I've heard of
> that insists on ESC sequences instead of using
> the BIOS routines,
I think it's not that straightforward. I would expect (ie could
be wrong) that most fullscreen text applications - written
by people who don't even use DOS - e.g. Amiga, VAX,
In the thread on the other forum I pointed out that remapping the cursor
keys to generate ESC sequences instead of passing through the {0, scan
code} value was going to break other DOS software. So while adding the ESC
sequences to FreeCOM seems harmless, it also really only benefits people
who
> Note that I have a different goal to most people. Most people
> want to run DOS-era software. I want to redefine the DOS era
> now that the "rush to market" is long over.
> Any thoughts?
Yes.
Good luck with that.
Tom
___
Freedos-devel mailing
Hi Jim.
Direct link here:
https://www.pdos.org/uc8086.zip
Since my previous email I have included a couple more
binaries for unrelated reasons, so the archive has (just
now) been refreshed (again).
BFN. Paul.
___
Freedos-devel mailing list
On at 2023-07-31 08:44 -0500, Jim Hall via Freedos-devel wrote:
FYI: Your post was 104 lines and 618 words. How-to articles on
websites are between 500 and 800 words, so this email was a bit long.
:-/
The point is you have released a new microemacs?
There is some more context to all of this
FYI: Your post was 104 lines and 618 words. How-to articles on
websites are between 500 and 800 words, so this email was a bit long.
:-/
The point is you have released a new microemacs?
:: Anyway, long story short - I have banged microemacs 3.6 into
:: shape so that it is C90 compliant with the
Hi.
When I started programming in Turbo C 2.0 on my
Commodore PC 5 (IBM PC XT compatible) with
20 MB hard disk and monochrome text monitor
circa 1987, I didn't write any MSDOS or 8086-specific
code at all. Everything I did was C90.
My code worked on the mainframe (MVS) too.
I resisted making
24 matches
Mail list logo
