That's normal. If you start a new shell, the aliases are a clean
sheet. Unlike Unix shells, FreeCOM doesn't have startup files (perhaps
an idea for the future).
On Mon, 12 May 2025 at 13:29, Wilhelm Spiegl via Freedos-devel
wrote:
>
> Hi,
> when running FDT2505 (and earlier) I noticed the followi
Many people leave default admin passwords unchanged when installing
third party software on their webservers, so there's a lot of bots out
there looking for such pages. Once they have admin access they can do
a holl of a lot of damage including hijacking your whole system if
your security settings
I would say this is more likely a wider infrastructure problem. I've
experienced trouble with several sites over the last two days that
keep springing error messages or slow access on me. I'd say this isn't
an ibiblio problem, but more like a backbone going poof somehwere in
Americaland. Considerin
I'll do some tests on that tomorrow if it is really tied to the
absence of a co-proc. Considering that Fortran was originally meant to
be a math heavy language it might just as well be.
Cheers, Danilo
On Tue, 1 Apr 2025 at 21:30, Jim Hall via Freedos-devel
wrote:
>
> I've installed it on both my
What we would probably need is a Unix-style NLS system. under Unix you
would have
LANG=PT_PT.latin1
or
LANG=PT_BR.UTF8
It's not only about messages in programs, but date formats, currencies etc.
On Mon, 3 Mar 2025 at 20:13, Jerome Shidel via Freedos-devel
wrote:
>
>
>
> > On Mar 3, 2025, at 1
Dagnabbit, that's a brilliant piece of comedy. And there I was trying
to make a living by actually programming stuff for thirty years. This
guy certainly had a sense of humour that we Germans are undeservedly
said to be lacking.
I shall, from now on, include that disclaimer in all my stuff
/* if
main code body instead. That way you could
make it clear to an outside reviewer from which point on a variable is
actually used.
On Tue, 25 Feb 2025 at 20:10, Bernd Böckmann via Freedos-devel
wrote:
>
>
> On 25.02.2025 19:16, Danilo Pecher via Freedos-devel wrote:
> > Actually the f
Actually the first snippet looks a bit dodgy to me. Why initialize one
pointer and not the other? It almost looks like someone just wanted to
make his patch look a bit more substantial than it really is.
On Tue, 25 Feb 2025 at 17:45, tom ehlert via Freedos-devel
wrote:
>
> Hi,
>
> > Recently, ECM
Funny. My go-to language in the early 90s was Pascal as well, but I
don't think I could code in anything but C or assembler these days.
Compared to those two Pascal seems almost cumbersome with 30 years of
hindsight...
On Tue, 25 Feb 2025 at 13:53, Jerome Shidel via Freedos-devel
wrote:
>
> Hi,
I would very much vote against replacing FreeDOS edit. I agree it is
bloated and not very well programmed, but instead of throwing it out,
we should make an effort to de-bloat and stream-line it. FreeDOS was
created as as replacement/continuation of the original DOS, and as
such we should keep to t
In general I would suggest we don't start spamming the list with
messages about utilities to be relegated to downloadable add-ons.
Could we set up a forum or something whre we could sort this out?
On Mon, 17 Feb 2025 at 20:15, victoria crenshaw via Freedos-devel
wrote:
>
> keep in repo remove fro
Have you taken a look at it with a hex editor? It might actually be an
exe file. If I remember correctly DOS allowed you to load executable
with both exe and com extendions and actually decided how to load it
by the existence or absence of an MZ header.
On Mon, 17 Feb 2025 at 17:51, Paul Dufresne
Half of the commands don't require much more than an alias in
fdauto.bat, so I guess it isn't of much use even if when it doesn't
segfault.
On Mon, 17 Feb 2025 at 18:22, Jerome Shidel via Freedos-devel
wrote:
>
> Tom suggested in another message thread the removal of MiniBox from the
> release m
I wouldn't assuime any unwarranted wisdom here, but my impression is
that some programs seem to be included because they are there and
there is no alternative. As a font nerd of sorts, I noticed the
gnuchcp package that Jim even made a video about. It is ridiculously
trivial and not very well progr
As I said, we should perhaps take a tally of what is really useful,
but perhaps we should take some time to trawl through all the
packages. and not delay the upcoming release over it. I would say this
would be a project for FreeDOS 1.5
On Sun, 16 Feb 2025 at 23:49, tom ehlert via Freedos-devel
wr
+1
>From what I can see. There's pretty much a consensus it should go.
Perhaps, since release cycles of FreeDOS tend to be rather long, we
should perhaps have a look at all packages and sort out the ones who
are really needed and those that shouldn't come with the main
distribution. We could still
3/9 works for me - would take my mind off becoming yeat another year
older that day.
On Sun, 16 Feb 2025 at 20:13, Jim Hall via Freedos-devel
wrote:
>
> Let's schedule the next FreeDOS virtual get-together in March. This
> should be a "technical" focus for anyone who wants to "live debug"
> RC3.
that some people
still use today, 28 years later. When I learned about that 3 years
ago, it completely blew my mind.
On Wed, 15 Jan 2025 at 17:19, Paul Dufresne wrote:
>
> Le mer., 15 janv. 2025 08:10:55 -0500 Danilo Pecher a écrit
>
> > To be honest, it looks like
To be honest, it looks like just another student project cobbled
together while flunking math lessons. I've written at least two of
those in the nineties and soon learned I was going nowhere. To be
frank, we shouldn't try to bloat FreeDOS's software base, and instead
concentrate on software that re
The trouble is, unless you still have a vintage machine, it's
ridiculously hard to find a good one these days, at least if you want
one where the mainboard hasn't been half-eaten by a leaking battery.
And even then, at 20 years of age they are often prone to hardware
conking out.
On Tue, 7 Jan 202
I might get myself one of these
https://www.youtube.com/watch?v=B8WfiRRvQXo
Has anyone experience with those in terms of hardware compatibility?
Cheers, Hippo.
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourcefor
The trouble with new baremetal machines goes beyond just UEFI or lack
of CSM. You would perhaps be able to run freedos, but couldn't use
most of the hardware. The only real metal that I can haveTCP acces for
instance is a 17 year old laptop. I have yet to see any network or
sound drivers for recent
Why should we update the kernel and FreeCom only with major releases?
Can't we just do that with non-release updates? Linux pushes out a new
kernel revision every 45 minutes and it has worked for many years.
On Sat, 21 Dec 2024 at 16:43, Jerome Shidel via Freedos-devel
wrote:
>
> Hi,
>
> > On Dec
May I ask a stupid question? CGA had four colours, quite garish ones
in fact, in both available palettes. How did they emulate 4 colours on
a monochrome card? Am I missing something?
On Thu, 19 Dec 2024 at 15:01, Ben Collver via Freedos-devel
wrote:
>
> I don't know about ZULIA, but back in the d
On Wed, 18 Dec 2024 at 16:44, tom ehlert via Freedos-devel
wrote:
>
> Dear Danilo Pecher,
>
> am Dienstag, 17. Dezember 2024 um 13:43 schrieben Sie:
>
> > I agree. We should start keeping track of who maintains what,
> Yes. Would be cool to know if anybody cares about th
4 at 17:42, Jim Hall via Freedos-devel
wrote:
>
> On Tue, Dec 17, 2024 at 10:29 AM Danilo Pecher via Freedos-devel
> wrote:
> >
> > Right, let's not make a theoretical discussion of it. We have a list
> > of 'official' packages, as visible by starting fdim
Right, let's not make a theoretical discussion of it. We have a list
of 'official' packages, as visible by starting fdimples. Since I'm
holed up at home anyway, recovering from a massive coronary, I have a
lot of time on my hand. I'll try to contact the original authors and
find out, if those packa
grammer / still active yes/no? / known bugs?
> (maybe short, e.g. https://sourceforge.net/p/freedos/bugs/ bug number) or:
> (https://gitlab.com/groups/FreeDOS/base/-/issues)
>
> Willi / Fritz
>
>
> Sent: Tuesday, December 17, 2024 at 1:43 PM
> From: "Danilo Pecher via Fre
I agree. We should start keeping track of who maintains what, and
perhaps even throw out packages that are not maintained and nobody
feels like taking over. That could also help to reduce the inflation
in neccessary installation media size.
On Tue, 17 Dec 2024 at 12:24, Bernd Böckmann via Freedos-
Do we have a list somewhere of packages that don't have a maintainer?
On Mon, 16 Dec 2024 at 23:50, Wilhelm Spiegl via Freedos-devel
wrote:
>
>
> Would be a great idea. What about edit? There are a lot of bug reports about
> edit.
> But there are more.
>
>
> Willi
>>
>>
>> * Volunteer to become
Well, in extremis you could go down the ReactOS route and reverse
engineer Windows 3. But I doubt you'd be doing it for much more than
shits and giggles. There's simply no demand for something like that.
FreeDOS itself is a niche product to begin with.
On Mon, 16 Dec 2024 at 19:23, Liam Proven via
I don't think you'll find too many 8086 machines these days, let alone
80186. I fact I saw such a thing once in my entire life. A
Triumph-Adler with an amber monochrome monitor, which I found so cool,
I still change the font settings to amber-on-black 30 years later on
whatever system I'm working o
Open Watcom makefiles are somewhat peculiar about non-tangible build
targets, like 'clean:' for instance. You have to use a proprietary
macro to make that work, but I can't quite remember it right now. It
was something like %SYMBOLIC% or somesuch, else the Watcom make
rebuilds stuff unneccessarily
41 minutes to build is quite a plank... You can compile a Linux kernel
faster than that. Are you sure that there isn't something else
interferring with it? Something that compiles for that long is usually
a massive chunk of code.
On Sun, 15 Dec 2024 at 13:37, Bernd Böckmann via Freedos-devel
wrot
I guess we were all at this point at some time or other.when we
thought we had a brilliant idea and then realised that our plans were
more than just a little fanciful. I spent the best part of 1992 and
1993 writing a rather fancy GUI library that worked on EGA, VGA, a
weird-arse 512K Realtek SVGA
Tom, what's the joke with the references to Linux? Not that I would
mind. I've run Linux since 1994. Took home an early Slackware system
on 64 floppy disks, had to write an X11 driver for my weird-ass 512K
Realtek SVGA card and then ruined my eyes looking at 1024x768 pixels
interlaced, but why woul
gt; Does anyone know why the strings were put into separate files in the first
> > place?
>
> Because that's how the vast majority of projects are organized; The text
> strings for each supported language live in their own separate translation
> files.
>
> --
>
I'd agree with Tom here. Reinventing the wheel makes little sense.
After all, one of the points of FreeDOS is being a free replacement
of, well DOS, so you shouldn't really need a replacement for something
that has worked fairly well since the Romans left.
In fact, I'm not even sure we should go t
I've made it a tradition to spend the last day of the year
programming, and I still haven't got anything for this year :)
On Sat, 14 Dec 2024 at 18:18, Jim Hall via Freedos-devel
wrote:
>
> On Sat, Dec 14, 2024 at 9:34 AM Danilo Pecher via Freedos-devel
> wrote:
> >
> >
Unless any program uses gas' AT&T assembler syntax there should be no
source that requires gcc to compile. Everything else can be handled
via #ifdef's.
On Sat, 14 Dec 2024 at 18:18, Jim Hall via Freedos-devel
wrote:
>
> On Sat, Dec 14, 2024 at 9:34 AM Danilo Pecher via Fr
the target system is a 386
> >> or better, IA-16 GCC requires a 386 to compile but the exe can run on
> >> lower systems).
>
>
> Danilo Pecher wrote:
> >
> > Hi Jim,
> >
> > I don't think it is a good idea to introduce a second toolchain. Mo
As I wrote in my reply to Jim's email, I don't think introducing
additional toolchains makes any sense. In fact it would be a good idea
to have all 'official' packages that are based on C compile with OWC.
I don't know if that has changed, but I remember MKEYB at some point
required Turbo-C to comp
Dflat+ is a dos text mode library that is styled to mimick the
Microsoft windows API.
Some info can be found here :
https://pushbx.org/ecm/editsrc/DOC/DFLATP/DFP100.HTM
On Sat, 14 Dec 2024 at 16:38, victoria crenshaw via Freedos-devel
wrote:
>
> i need help with a new freedos program! :D?
>
> it
just compiling it with a GCC compiler like IA-16 GCC.
> (Djgpp is great too, but requires the target system is a 386 or better, IA-16
> GCC requires a 386 to compile but the exe can run on lower systems).
>
>
>
>
>
> On Sat, Dec 14, 2024, 5:07 AM Danilo Pecher via Freedos-d
I have to admit, I'm rather confused about the gcc IA-16 thing too.
Jim seems to like it a lot, but Watcom code runs on all processors
too, provided you use the proper options to have it compile for the
lowest common demoninator, which would be the 8086.
On Sat, 14 Dec 2024 at 11:04, Bruce Axtens
It definitely was fun. I thoroughly enjoyed it.
On Sun, 8 Dec 2024 at 21:11, Jim Hall via Freedos-devel
wrote:
>
> On Sun, Dec 8, 2024 at 12:37 PM Jerome Shidel via Freedos-devel
> wrote:
> >
> > Hi Jim,
> >
> >
> > FYI, Google now immediately ends the meeting when you disconnect.
> >
> > So, no
Hi Jim,
Since that would be my first participation in the event, can you give
a short reminder about the neccessary software for newbies like
myself?
Thanks.
On Fri, 6 Dec 2024 at 05:26, Jim Hall via Freedos-devel
wrote:
>
> Hi everyone!
>
> I'm sending a reminder that we have our FreeDOS virtu
I just don't get it. What are those wastes of skin and organs who get
a kick out of making other people's lives miserable, The wayback
machine is a brilliant idea, archiving web pages that their authors
have long since given up upon. How sad must your life be if it gives
you a kick to just fuck up
Probably the best DOS programming channel is root42:
https://www.youtube.com/@root42
He also has other retro computing stuff going on, but he does an good
lot of videos on DOS programming as well.
Cheers, Hippo
On Wed, 8 May 2024 at 17:57, Jim Hall via Freedos-devel
wrote:
>
> On Wed, May 8, 20
Not to put too fine a point on it, but may I point out that your mail
comes across as somewhat rude? As for your answer: Had you even
bothered to install FreeDOS before kicking up a fuzz, you would have
known that the source code is included in it.
Cheers mate
On Wed, 8 May 2024 at 03:47, Green F
Neofetch is a good way to give you a quick overview of the machine's
parameters. It's perhaps more of a gimmick under DOS, but in a unix
environment it can be a godsent. When I was database administrator at
Infineon I had to work with about 3000 different machines running
either Linux, Solaris, AIX
Used not is it.
As far as I know there is no component or application for FreeDOS
that's developed in Forth. But it should be perfectly useable under
FreeDOS, so if you have some ideas, fill your boots mate. :)
Cheers,
The Hippo
On Thu, 21 Mar 2024 at 02:20, Bruce Axtens via Freedos-devel
wrote
The most common translation of MAD would be Verrückt (bonkers, crazy),
although it can translate to wütend in some contexts. The more
accurate translation of wütend would be 'raging'. So if your theory is
right, it was a German who was rather inexperienced at English or just
took the translation fo
I'm having real problems to read about MAD code written with FAP
subroutines with a straight face. I'm such a child...
On Tue, 30 Jan 2024 at 23:00, Ralf Quint via Freedos-devel
wrote:
>
> On 1/30/2024 1:37 PM, Jim Hall via Freedos-devel wrote:
> > Jim Hall wrote:
> >>> On Mon, Jan 29, 2024 at 8:
Hi Jim,
NASM already comes with FreeDOS. It's a good one to start with. It
works perfectly fine under DOS. There is a German youtuber named
'root42' who has made some pretty good DOS Assembler tutorials in
English.
cheers, Danilo
On Tue, 26 Dec 2023 at 17:50, Jim Hall via Freedos-devel
wrote:
Hi Jim,
I know a lot of works has probably gone into this, but quite frankly I
think it looks just like all the other plastic-y websites you find
everywhere. I might be a bit weird, but I kind of like old school
websites that are simple and render on anything. It is sort of funny
to think that we
Hi Rob,
I would start a bit more at the meta level and research how kernels
work. There are also many sites dealing with OS development (osdev is
useful search term). It is quite instructive to see the first steps
that happen after the machine boots (the boot loader mainly). Once
you've really und
Hi,
I think the question is rather academic. The Patreon membership is
voluntary. Nothing prevents a user from downloading and using the
program for free and under conditions described by the program's
author. This is different to, let's say, a website that requires a
paid membership to get access
The simple answer is - you can't. For starters you would need to
activate the secondary character table in text mode, giving you 512
characters to work with, at the expense of 8 background colours.
Therein lies the problem though. Firstly, it only works on EGA and VGA
cards and secondly - as the hi
As far as I know the earlier Turbo-Pascal compilers (I think 5.5 and
earlier) have been freeware'd years ago. They can natively compile
16bit code on Freedos and might be worth a try. You can find even
ancient versions of TP, like 3.0 on winworldpc, and I actually quite
like to go down memory lane
If you have a windows or Linux machine at hand, you might want to
check with pcem. It can emulate several 286 BIOS/board variants. That
would give you a hint if it might be a problem with your board or the
286 architectur in general.
On Wed, 8 Nov 2023 at 14:33, tom ehlert via Freedos-devel
wrote
Sorry, Tom, but this reply is, to use a technical term, pretty shit.
We're talking about FreeDOS, a system that by design was created for
hardware that would lose to our phones these days. If you 'only want
to support 386+' then you can just as well install Dosbox. Either
FreeDOS has the ambition t
As far as I know, VESA graphics mode numbers are not standardized,
which is why the vesa info block of standard 1.2 and higher, returned
by INT 10h function AX=4F00h, contains a mode list, which you then
need to traverse using INT10h AX=4F01. So as a first step I'd check if
the watcom graphics libr
I've had a look at it, and I doubt there's much use for it on FreeDOS.
The most glaring obstacle is the choice of programming language.
Neither Microsofts Quickbasic, nor Borlands Turbo-Basic are free
software, so the amount of people who would be able to compile it, is
probably dwindingly small.
> Beside that
> leaves you in general also with the problem on how to transfer your
> programs from your fancy Windows/Linux/macOS box to that VM. That's a
> problem that that you simply do not have when programming ON DOS.
Well, I often use DOS in an emulator (pcem) because that emulates
specific
Hi,
I'm with Kirn on this one. I think people have a wrong idea what
people use FreeDOS for, if at all. First of all, I think that the
assumption that there's a mahoosive community out there might be a wee
bit optimistic. It's probably rather modest, as not too many people
these days use DOS for a
I think the developer tools should go to the bonus CD. As was
mentioned, most FreeDOS users will probably use it to run legacy apps
and games. People who still have the knowledge to do some
honest-to-god proper DOS programming will probably be quite able to
switch the CD and install the stuff from
Yeah, around 1993 was when the first ones arrived.
On Mon, 7 Aug 2023 at 01:12, Steve Nickolas via Freedos-devel
wrote:
>
> On Mon, 7 Aug 2023, Danilo Pecher via Freedos-devel wrote:
>
> > The first one I can remember was the Mitsumi CRMC-LU005S single speed
> > drive, wh
The first one I can remember was the Mitsumi CRMC-LU005S single speed
drive, which was the one I had. It had its own card because it was
non-IDE despite the fact that the cable and plug looked exactly like
IDE. They did use a proprietary standard. They definitely worked on an
80286, so I think we c
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 a
Jim put it best, I think - remove the GUI's from the official media,
but leave them on ibiblio, which would be the FreeDOS equivalent of
the Hobbes archive for OS/2.
On Wed, 22 Feb 2023 at 23:53, Liam Proven wrote:
>
> On Sun, 19 Feb 2023 at 17:52, Jim Hall wrote:
> >
> > It's been a few days si
Quite frankly, I would throw them all on the scrap heap. As Jim said,
none of them has any number of apps worth noting and there is a reason
why no GUI other than Windows 3.11 ever took off under Dos. I know
that from painful experience of wasting two years on an attempt to
create one in the early
If you are comfortable programming in Pascal, stay with it. In fact
Turbo-Pascal has pretty much the best integration of inline assembler
of all the languages I encountered in 30 years. And in general, just
don't follow tutorials blindly, collect your own experience. Maybe it
would help if you told
Accepting the danger of sounding somewhat arrogant, but you seem to
lack some basic knowledge of system programming. Are you sure you
need assembler programming in the first place? Everything you've set
out so far is perfectly doable in C.
On Fri, 13 Jan 2023 at 17:35, Knedlik wrote:
>
> Okay, t
Oh dear, if you really want an answer for that, you need to give more
infos, like which linker are you using, which memory model?
On Thu, 12 Jan 2023 at 20:45, Knedlik wrote:
>
> Hello,
> I’m currently trying to make a function in a separate assembly file, but I’m
> having problems linking it wi
Hi all,
I say the most important thing first - I'm not very keen on a Live
DVD. One of the things that severely goes on my man-mammaries is that
every Linux, BSD and whatnot nears the 1GB mark, when a basic system
install could easily fit in a 300MB image. I don't think we have too
many casual use
Since thengraphics cards of VMs are, as far as I'm aware generally
VESA compatible, unless you specifically decide not to use one in qemu
or bochs, you should have a relatively high hitrate by using the 4Fh
interrupt to query the VESA info. In the case of Virtualbox/VMWare,
you'll definitely find o
Well, one could also question the point of shared libraries in a
system that doesn't support multitasking.
Dynamic loading has a point in so far as to load binaries based on the
availability of hardware, as in the BGI drivers. Having the code to
support all gfx cards in the exe would be wasteful,
IIRC there was never something like a standard DLL concept, but we
used to use flat binaries for that concept. Back in 1994 or something,
a friend of mine and I wrote something akin to fractint and we defined
a 'fractal driver' for each type. What it basically boiled down to was
typedef'ing a funct
Hi
Ralf makes a very interesting and important point here, especially as it
reminds me of my idealistic and somewhat overconfident self from 1993. Like
many people back in the day I thought I was a l33t hax0r after three years
of dabbling with Turbo-Pascal, Turbo-C and even some assembler. So,
nat
to the 32-bit realm
> in the form of the Night Kernel. As part of that journey, we eventually want
> a compatibility layer to make running Windows 3.x executables possible.
>
>
>
> Sent with ProtonMail Secure Email.
>
>
> ‐‐‐ Original Message ‐‐‐
> On Thurs
Hi Eric,
The ReactOS/Wine combo was what got me thinking in the first place.
ReactOS was from the start meant to replicate WIndows NT though, which
isn't quite what I had in mind, as that isn't quite the 16 bit world
in which FreeDOS exists. Wine would be a starting point, as that
definitely has 1
Ho,ho, everybody,
First of all, merry holidays to all and I hope you're all safe in
these difficult times.
As the new year looms, it's time to get them new years resolutions in.
I'm foregoing the usual stuff, like losing weight, because that won't
work, just like the other years. Instead, inspire
It happens on both Virtualbox and my ancient Compaq NX-8220. And
indeed, as hinted by several folks, it seems to be connected to fdapm.
On Mon, 21 Dec 2020 at 20:03, Robert Riebisch wrote:
>
> Hi Danilo,
>
> > I still have legal copies of Turbo Pascal 3.0, 4.5, 6.0 and Borland
> > Pascal 7.0, so
BGI ran like a three-legged pregnant hippo in a mud pit, mainly
because it used the INT10h functions. Pretty much everyone I know, who
also started programming in the late 80s got their first taste of
inline assembler and hardware programming, when we realized that you
could speed up things by magn
I still have legal copies of Turbo Pascal 3.0, 4.5, 6.0 and Borland
Pascal 7.0, so if there's interest, I'd be willing to take a look at
them to see if there's any insects to weed out.
Speaking of which. I noticed that pretty much all Borland Test-mode
IDE's for Turbo-C, Turbo Pascal and Turbo-Pro
I agree Jim,
If you go for effective, then the standard FreeDOS window is certainly not
the ideal solution, and perhaps I should have made it clearer that my
remark to Tom wasn't meant overly seriously.
The nice thing about FreeDOS is that you have choice these days, unlike in
the days of yore, s
Hi Tom,
Well, I guess we'll have to agree to disagree then, and maybe I'm just
weird. I'm the sort of guy that actually would look for spare parts on
horse back, because that's way more fun. Probably not for the horse though,
considering that, unlike 30 years ago, I weigh more than Belgium these
d
wireless, I don't even go there, it's an iwi that need proprietary Intel
firmware - no sale.
No, the machine is a geriatric Compaq Nx8220 and the NIC in question is a
Broadcom Ethernet card. BCM5751M.
On Wed, 2 Dec 2020 at 00:09, Eric Auer wrote:
>
> Hi!
>
> > laptop is 15 years old, and even t
Hi Eric,
Well, your argument is compelling, but I think it sort of misses the point.
FreeDOS is a system for legacy hardware - I mean - really legacy. My oldest
laptop is 15 years old, and even that has hardware that is 'too new' and
not supported by FreeDOS. I'm currently trying to nail a Packet
Tom,
Sorry, but I think you're too snippy here.
First of all, if the idea of an 80x25 single file editor frightens you,
you're either a wimp or too young to have done any programming when that
was the norm. May I introduce you to Turbo Pascal 3.0? 80x25 text is the
best there is.
As for not find
I would agree with Ralf on most points.
As for the 16 bit C-Compiler, I think Turbo-C fits that bill but acquiring
it legally requires a registration with embarcadero, so not exactly optimal
and not everyone is an old hack like me, who started coding in 1989 and
still legally owns nearly every Bor
92 matches
Mail list logo
