dos386 wrote:
to me it's still unclear what it is supposed to do and whether it
works in (Free-)DOS at all, considering the shots you posted ;-
It is a LAN status monitor. It monitors the status of your LAN. ;-0
--
Hi,
Just a quick note - I've posted a new version of mTCP at
http://www.brutman.com/mTCP .
The biggest change is a bug fix. Some packet drivers refuse to send
packets less than 60 bytes in size while many older packet drivers don't
care. Technically speaking, a packet less than 60 bytes in
Mateusz Viste wrote:
I believe you wanted to say frame instead of packet and 64 instead of
60? As far as I know, an IP packet can transport no payload, which gives a
20-bytes packet in result. :-P
The limitation is about the minimum size of the frame, which (on ethernet) is
of 64 bytes, to
I just posted the latest and greatest code at
http://www.brutman.com/mTCP . This version supports IP fragments, which
might help with some of the stranger network and gateway setups out there.
Another neat feature that I should have done a while ago is command line
editing for FTP, including
Geraldo Netto wrote:
Hi Michael/All,
Would be possible to release it as gpl or any other oss license?
(i guess someone already asked for it, but anyway...)
Kind Regards and Best Wishes,
Geraldo
Geraldo,
It is in the works. My employer has to review the code and bless it
first to protect
A new version of mTCP is available in the usual place:
http://www.brutman.com/mTCP .
If you are on an older clone machine and you have not been able to make
the larger apps run correctly, then you want this version. The Watcom
compiler runtime that I am using now was incorrectly flagging some
On 12/21/2010 8:54 AM, dos386 wrote:
AFAIK the inline ASM is more painful in WATCOM than in Boreland C or
CC386 compilers (I ever tested the latter one only). The are also
pre-brewn int86() int386() and maybe more functions to fire the INT
instruction but don't ask me how they exactly work.
Are there any FreeDOS users using a PCjr?
I suspect that except for the weird memory hole that the video hardware
creates and the use of NMI for keyboard handling, everything else should
work pretty well. But I'd like to hear from somebody who knows.
Regards,
Mike
I have posted the latest and greatest code (again) at
http://www.brutman.com/mTCP . This version has some minor bug fixes and
a new FTP server application.
Besides downloading it from the link above, for a limited time you can
get it using FTP directly from the PCjr that I do my testing on.
On 1/15/2011 10:23 AM, Ulrich Hansen wrote:
The new ftpsrv app from mTCP works, but at least on my system seems to
have problems with showing correct DOS paths. For instance it shows
c:\ as c:/\. So f.i. creating new directories in filezilla doesn't
work without manual correction.
regards
this problem.
Regards,
Mike
On 1/15/2011 4:33 PM, Ulrich Hansen wrote:
Am 15.01.2011 18:10, schrieb Michael B. Brutman:
On 1/15/2011 10:23 AM, Ulrich Hansen wrote:
The new ftpsrv app from mTCP works, but at least on my system seems to
have problems with showing correct DOS paths. For instance it shows
I had seen the original suggestion to use CTTY to redirect the console
to a serial port but
I had seen the original question on how to redirect DOS to use the
serial port and I probably should have chipped in then, but now you know
the limitations of CTTY.
CTTY to a serial port only works
The mTCP DHCP client writes output to STDOUT and to the MTCPCFG file,
which is pointed to by an environment variable. It's a simple matter of
programming/scripting to convert the output from either one into
something that looks like a static WATTCP configuration. I've tested my
DHCP client
I'm not a Lynx user so forgive my ignorance .. but are you using the
version supplied by Fred C. Macall? In the past he has been very good
about supporting DosLynx for other people.
The output from the mTCP DHCP client is probably not in a form directly
usable by the WATTCP apps. You are
My advice ...
Your problem reports are confusing. You say that something is not
working, but it had been working before. If that is the case, what are
you changing? If you can't remember what you changed then it is time to
slow down and take some notes.
The general method for getting a
Things have been quiet on the list lately, so I feel compelled to
generate some noise ...
A new version of mTCP is available at http://www.brutman.com/mTCP . The
notable changes are:
- IRCjr now supports multiple sessions using virtual windows.
- A high contrast screen mode for IRCjr; useful
On 4/10/2011 5:20 AM, escape wrote:
Vote with your wallet. I'm personally not buying any 4k drives nor for
myself nor for companies I'm working for. When you need more than 2Tb of
space you always can add another 2Tb drive instead of replacing old
drive with bigger (3Tb) one.
I think that is
On 4/10/2011 12:08 PM, escape wrote:
Please get it right. I'm not arguing against support of new
technologies. But now it's often when manufacturers trying to disguise
cost cutting and marketing rubbish as prominent new technology.
Look at monitors as an example. Getting 16:10 aspect along
Jack,
I love a good rant as much as anybody, but some context is needed.
PCI was desperately needed by server class hardware. The ISA bus and
the extensions to the ISA bus were failing for several reasons:
- Inability to share interrupt lines
- Three fragmented standards (ISA, VL, and EISA)
Jack,
There are so many inaccuracies and distortions in the reply that you
sent, I'm going to assume you are just irritated or in a bad mood.
The world moves on ... it doesn't make sense to support existing
standards forever. You can have eternal support, or affordable prices,
but not both.
On 4/10/2011 11:35 PM, Jack wrote:
Also, I do not know you and you do not know me, so WHO ARE YOU to assume
I am irritated or in a bad mood?!! Are you in fact a COMMUNIST?? I
seem to recall THEY used to operate via trying to beat-DOWN opposition
with such unqualified INSULTS as you have
Come and get it! http://www.brutman.com/mTCP/
In this version:
- CTCP support in IRCjr (you can do /me now!)
- DHCP client enhanced to do multiple retries and give better error messages
- Fixed a parsing error in the FTP server
- Telnet can now work with servers that do not accurately interpret
I released mTCP as open source today: http://code.google.com/p/mtcp/
Enjoy!
Mike
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you
On 5/28/2011 3:57 AM, Bernd Blaauw wrote:
hi Michael, congratulations on possibly having the first GPL3 DOS program ^^
I seem to recall you needing permission from your employer to do this so
thanks go out to them as well.
I think that honor was claimed already. I solved the permission
On 6/1/2011 5:30 PM, Ulrich Hansen wrote:
Actually this is not really news but just a wish from my side. The
discussion what*s part of FreeDOS 1.1 takes place since some time at
freedos-devel. I think the developers decide, while we users should
publish our expectations and wishes.
So I
On 6/2/2011 1:42 AM, Willi Wasser wrote:
Some developers may not be too happy
about the license choice, especially
those who would like to grab your code
and try to make money from it by making
it part of an unfree software.
Let's be serious! Is there still a market for any kind of DOS out
On 6/22/2011 9:15 AM, Marcos Favero Florence de Barros wrote:
Hi Mike,
Thanks for mTCP!
I experimented with it yesterday for the first time, and it took
me just 15 minutes to get started, in spite of my near complete
lack of internet experience (except of course web browsers and
email
On 6/22/2011 10:49 PM, Marcos Favero Florence de Barros wrote:
Hi Mike,
I shouldn't even have called this thing a bug. It is, at most, an
issue of semantics. Because the SNTC screen message used the word
timezone, I thought it would write UTC+3.
I'm probably right on that point (just
On 6/22/2011 8:10 PM, Mike Eriksen wrote:
If SNTP works anyway like in Linux/UNIX then the computer takes its
hardware clock as UTC. If the hardware clock is offset to local time
it will be misinterpreted. The poor computer doesn't have any
conception of UTC by itself, it only knows its
I have an early version of HTGet ready that I would like to get some
more testing on before it becomes part of mTCP. It is available here:
http://www.brutman.com/mTCP/htget.zip
HTGet lets you download a file (or whatever content) from an HTTP
server. Just put the URL on the command
On 7/25/2011 6:52 PM, Bernd Blaauw wrote:
Thanks for creating this. It means you're pretty close to a basic WGET,
and also reminds me why I never liked HTGET: no support for FTP and
REDIRECT/MOVED. URL parsing seems fine. Not sure if/how HTGET would
respond to HTTPS://
Example URL
On 7/25/2011 7:46 PM, Mike Eriksen wrote:
Maybe a stupid idea, but couldn't HTGet just call you FTP client in
case of a FTP-URL and let that one handle the download and keep the
rest inside HTGet?
Mike
There is no simple call ... the FTP client is a stand-alone program.
In the event of a
On 7/26/2011 12:09 PM, Bernd Blaauw wrote:
snip
HTGET supporting common HTTP URL/URI syntax
(http://server.domain.extension/path/file.ext) is good enough already.
your -userpass seems to indicate no complete syntax is possible, and
portnumbers either assumed 80 or not changeable.
The next mTCP is available, with HTGet now included:
http://code.google.com/p/mtcp/
There are two versions of the pre-compiled binaries to choose from -
standard and -upx. The -upx version binaries are compressed with a
program called UPX that decompresses the programs at load time. You will
On 8/25/2011 6:20 PM, Rugxulo wrote:
Hi,
On Wed, Aug 17, 2011 at 1:48 PM, escapeesc...@front.ru wrote:
If you use dos alone and purely on your machine, but nevertheless have
some *nix server access you can use rsync client for dos:
http://www.2net.co.uk/rsync.html
Good, GPL. Interesting,
On 8/30/2011 1:46 AM, escape wrote:
Great to hear, as mTCP becoming all-you-need-for-dos-networking
solution. BTW what do you think about how hard it wiil be to implement
DOS-based rsync server, even if feature-limited?
I started looking at the rsync client - getting past the compiler and
Alerting us to the clashes in ReactOS serves to remind us of how good we
have it here; the group is small and flare-ups are at a minimum.
That being said, I don't think it is productive to keep making your case
here; it is not a FreeDOS issue and it is not for us to judge who is
right or
Here is the link to the announcement:
http://www.bttr-software.de/forum/forum_entry.php?id=10488
To me this is a serious problem - losing a piece of the DOS community is
bad. Losing the place where a lot of the programmers hang out is even
worse.
Mike
On 9/13/2011 7:10 PM, Michael C. Robinson wrote:
Look at it this way, it is extremely hard to support modern hardware in
a DOS style environment because DOS allowed application programs to use
hardware directly. Jim Hall has said himself that he has limited
interest in the GUI end and most
On 9/14/2011 6:14 AM, Zbigniew wrote:
Most probably you can run on your multicore machine concurrent
sessions of DOSBOX (or DOSEMU).
modern hardware can emulate older hardware. Now you have
a clean means of supporting modern hardware for people using old DOS
applications. Want your multi
The current DOS path handling in the FTP server is kind of broken - it
works for some clients, but not for others. Ironically, the smarter the
FTP client the less likely it is to work.
The problem has to do with exposing drive letters in the path.
Filezilla in particular detects the drive
On 9/21/2011 9:48 PM, Rugxulo wrote:
Why not imitate DJGPP instead? It's probably more familiar to people,
e.g. /dev/c/ or /dev/d/ or whatever. Or use both (or not,
whatever). ;-)
I was given good advice to shorten it, so it might not be in the form of
/drive_x/ but something more like just
at 08:37 -0500, Michael B. Brutman wrote:
I have made a large round of improvements to the FTP server in mTCP and
I am looking for a little testing help with it. If you have a few spare
moments over the next day or two just try to connect to it and browse
the file structure. Using a few
On 10/1/2011 11:09 AM, Jim Hall wrote:
I uploaded my file successfully, but wasn't able to complete my download:
Jim,
Please try it again - we have a common enemy, and it is my ISP.
I've tested this with files as large as 170MB under DOS 5. I'm sure it
will work if the connection stays up.
You've probably seen enough chatter already, so I'll keep this brief.
The FTP server testing is done, and I've released a new version of
mTCP. Most of the changes were improvements to the FTP server. IRCjr
now allows the user to edit their input before sending it, and the
default transfer
Sorry everybody .. the FTP Server was tragically broken under FreeDOS.
I have coded a workaround for some bad drive detection code that I put
in and uploaded a new release of mTCP.
Thanks go to Ulrich, Eric and Ralf for reporting the problem and helping
me debug it.
(I don't fully
Excellent, and you are welcome! I am glad it is working this time
around - I get embarrassed when I let broken code out. Some questions:
For best performance the following should be set in the mTCP config file:
MTU 1500
FTPSRV_FILEBUFFER_SIZE 16
FTPSRV_TCPBUFFER_SIZE 16
On 10/5/2011 7:27 PM, Alain Mouette wrote:
I had problems with networking in dos for a few users, a short time ago.
After a lot of headache, I discovered that those were conections via
ADSL that used PPPoE, which has a 28 bytes overhead.
So now I use
MTU=1472
and I had no more problems
On 10/13/2011 9:18 PM, Ralf A. Quint wrote:
At 03:02 PM 10/13/2011, Eduardo Casino wrote:
2011/10/10 Ralf A. Quintfree...@gmx.net:
At 01:38 PM 10/9/2011, Eduardo Casino wrote:
Would you be so kind of testing it in one of your 286? It should fail
with ERROR: Not running on top of VMWARE.
On 10/18/2011 4:50 PM, Rugxulo wrote:
Well I finally did it. Took a few hours, and I really didn't know Pat
well enough (online) to do him justice, but I sure tried very very
hard.
Well done. I've noticed that the FreeDOS page at Wikipedia has been
updated quite a bit recently too - it was
Jack,
[1] Not everybody on the list is a native English speaker.
[2] You need to calm down. The tone of many of your postings is
borderline hostile.
-Mike
--
The demand for IT networking professionals continues
On 10/25/2011 4:25 PM, Koh Choon Lin wrote:
Does that means FreeDOS would not be able to support multiplayer
network DOS games like Doom, CC, etc.. which MSDOS is able to do so
with ethernet?
For most of your questions, FreeDOS is equivalent to PC DOS or MS DOS.
So however you use those,
Andrew,
You should look for a product called Disk On Module. They are
composed of FLASH chips and are designed to be direct replacements for
IDE hard drives. Unlike a lot of CF cards that can be used with an CF
to IDE adapter but might not support CHS addressing, DOMs are designed
as IDE
Hi Eric,
I don't have a lot of experience myself, but a lot of my fellow hackers
who specialize in obsolete machines have reported problems with CF
cards. While CF cards are supposed to emulate IDE devices, a lot of the
newer ones do not support CHS addressing and do not work in older
Rugxulo,
I could have looked up Z machine - was just pressed for time this
morning. I try not to sound willfully ignorant. ;-0
(Which reminds me - I wanted to do a telnet server that used the Zork
virtual machine as a proof of concept. Now I know where to go start
when I find the time. Zork
On 12/11/2011 11:55 PM, David Griffith wrote:
On Sun, 11 Dec 2011, Ralf A. Quint wrote:
At 09:36 PM 12/11/2011, Ralf A. Quint wrote:
How can I get this code to do the Right Thing?
Actually just realized that it's pretty easy, you just need to
typecast properly all parts of the makeid macro:
The list membership is not that large. You can assume that people are
busy or don't know the answer.
As far as 4K blocks go, I wouldn't worry about it too much. 512 byte
sectors will be supported either natively or by emulation in the drive
itself for a long time to come - at least 5 to 10
Hi Eric,
I expect that in the next few years we'll see very large hard drives and
they will continue to support 512 byte sector sizes - that is what the
system manufacturers demand. The actual sector size of the drive might
be 4KB but the drive will allow the host to choose a 512 byte or 4KB
Bertho,
I spoke from the point of view of the device (the hard drive) - if the
hardware that the device is attached to chooses not to expose all of the
options that the device supports, there is little the device can do
about that. In the case of your external storage somebody made a design
On 2/12/2012 11:42 AM, kqt4a...@gmail.com wrote:
I took a different approach
I downloaded the latest iso, moved the Tandy harddrive to a pc, and installed
Now I have the Tandy up on FreeDOS
One itch to scratch is when I run dir I get Press any key to continue after
every single line
Next I
On 2/13/2012 6:06 AM, kqt4a...@gmail.com wrote:
I am connected!!!
I used the Intel EtherExpress/16 packet driver from crynwr.com
Now, how do I go about getting apps to use dns and is there such a thing as a
host table
Richard
What are you using?
If it is mTCP there is a nameserver
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.
My two favorite compilers are:
Borland Turbo C++ 3.0 for DOS: I did most of my early mTCP work. It
On 4/3/2012 1:18 AM, Michael Robinson wrote:
There is a syntax error message that flashes before the where to install
freedos to and from menu comes up. Another problem, install freezes at
installing command.com. Uge!
Are you installing on old hardware or in a virtual machine?
Some of us
On 4/8/2012 8:46 PM, Kenny Emond wrote:
Hey,
I was finnaly able to find a packet driver for my DOS computer
(ethernet connection), but for some reason Arachne shows the main
page, but when I try to go to a different page, it brings up
a roadrunner search thing. I tried to edit the
On 4/8/2012 10:00 PM, cordat...@aol.com wrote:
FreeDOS User ...
If WATTCP is working correctly you don't need the other lines in your
config file beyond my_ip=dhcp as they are filled in if DHCP works.
As has been discussed here before some versions of WATTCP support DHCP
and some don't.
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
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
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
I am looking for wish lists items, bug reports, and ideas for the next
release of mTCP.
The current version is about six months old now. I haven't had too many
bug reports so there has not been a great need to update it. That is
also the release that FreeDOS 1.1 chose to use, so it has seen
Marcos,
A network drive letter similar to the Microsoft LAN client would be
great, but that is a major undertaking - far larger in effort than the
FTP server, which was the last major addition. That is not coming any
time soon - it might as well be a separate project for the amount of
work
On 4/21/2012 5:44 AM, Marcos Favero Florence de Barros wrote:
snip
Also, it would be nice if mTCP became FDAPM-aware.
Regards *and* thanks,
Marcos
Marcos,
I'm testing this now. With FDAPM set to APMDOS VirtualBox is idling.
Before I made the change it was chewing up an entire CPU.
I
On 4/26/2012 10:18 PM, jasse...@itelefonica.com.br wrote:
My wishes:
1) Support for class 6 packet drivers
2) TCP/IP packet logging capability
3) A TSR version
Best regards,
JAS
1) mTCP does not support serial (class 6) directly. But DOSPPP can be
used with mTCP and I have used one
If your network attached printer is listening on TCP/IP port 9100 (HP
JetDirect protocol) and your DOS program can generate something the
printer can understand, then do the following:
- Print your printer output to a file
- Send the file to the printer using this command:
nc -target
On 5/6/2012 4:10 PM, nospam wrote:
Very interesting. I suggest you make a FreeDOS Wiki page from this
information.
Georg
It is just a trick that I found. I was waiting to do a more
comprehensive writeup on network printing until after I write an LPR daemon.
Netcat is one of the best kept
On 5/7/2012 6:32 PM, dmccunney wrote:
On Sun, May 6, 2012 at 5:30 PM, Michael B. Brutman
mbbrut...@brutman.com wrote:
Netcat is one of the best kept secrets in the world of networking. You
can use it to send email, printer files, or any arbitrary data from one
machine to another machine
It has been a while and I've accumulated a lot of changes and fixes.
Here is what you can look forward to:
* Power awareness for virtual machines and laptops
*IRCjr fixes to improve compatibility with more servers
*Howto style documentation for setting up SLIP and PPP with mTCP
*FTPSrv
Marcos,
As far as networking is concerned, I abuse my older machines all of
time. I don't think you have a networking problem; I think it is a
hardware problem, or very bad device driver settings.
General failure reading drive C is a bad sign. I would make a new
backup of that server hard
On 6/22/2012 2:01 PM, Bob Tanner wrote:
Asking here as I cannot find any mailing list or new group for pythond.
Looking for a reason why pythond under FreeDOS does not support the
icmp protocol.
PythonD 2.4.2r1 for DJGPP [GCC 3.3.2] on ms-dos5
import socket
socket.getprotobyname(icmp)
I have been blissfully unaware of the packaging requirements for
FreeDOS. I update mTCP a few times a year, and I know that is a lot of
work to get right. Is there a FAQ or notes on how FreeDOS manages
packages? If I can make the mTCP updates easier I will.
Mike
Hi David,
There are versions of DOS supplied with machines that have a mode
command that can redirect the printer port. It might even be a standard
feature of the mode command. But it is strictly a port change - instead
of using the BIOS to send characters to the printer it uses the BIOS to
I'm missing something here.
The big restriction that a GPL license imposes is copyleft. If you use
GPL code *AND* you distribute your work then you have to make your
source code available too. You can profit from your work and the work
of others but you can't hide your changes.
In the case
Overly pedantic.
The thread title stopped matching the thread contents a few replies ago
- it has not discussed FreeDOS compatibility in the recent replies. It
has devolved into an open source licensing meta discussion. It is a
meta discussion by most reasonable measures, and I changed the
On 7/6/2012 12:25 PM, C. Masloch wrote:
I agree, I'm certainly overly pedantic and unreasonable and silly.
And you're the one using the term intellectual property as if that was a
coherent concept.
=)
I guess I don't understand that last message either. The purpose of all
of these
You sent your query to the freedos-user list. Are you subscribed to
freedos-devel too? If not, then you should.
Another great resource is the forums at BTTR software:
http://www.bttr-software.de/forum/forum.php
And one more link - the programming area of the Vintage-computer forum:
John,
Maybe you could help us by being very specific with what worked and what
went wrong? The only thing I could gather from your message was that it
was difficult to do, and it was slow.
One thing that is essential for good performance is to ensure that your
host machine is new enough to
John,
Just to make sure I understand ...
You are running a batch file that is doing net use to setup printer
shares, a file share, and loads nansi.sys. And the output to the screen
during that time is around 8.5 chars per second?
Just as a comparison, running the FreeDOS Beta of 1.1 under
I noted that FDNPKG is using WatTCP - I don't see that as a problem.
While I prefer mTCP and I think it has many advantages (speed, size, bug
fixes, etc.) WatTCP works well enough and people are comfortable with
it. I also have a slight bias, so I am trying to be objective. ; - 0
The
We are far off topic now and I probably should not admit this but ...
I've installed both DOS 3.3 and DOS 5 on the same machine lately. And
yes, I had to use 32MB partitions.
I wanted to be able to dual boot my machine (a PCjr, 1983) to both
operating systems. DOS 3.3 uses an earlier
, but often not productive. That is not a typical use-case for DOS.
Mike
On 11/13/2012 9:50 PM, Rugxulo wrote:
Hi,
On Nov 13, 2012 8:39 PM, Michael B. Brutman mbbrut...@brutman.com
mailto:mbbrut...@brutman.com wrote:
I think that 8GB is more than enough for any DOS system I'm ever going
Does the SCSI card have an onboard BIOS? If so, it should provide BIOS
level access to hard drives using INT 13h. You should not need device
drivers to access that function.
Windows wants device drivers for additional device support and
performance. FreeDOS is just fine with BIOS level
mTCP sounds right. ; - 0
The latest versions are at Google Code: https://code.google.com/p/mtcp/
. It gets updated more frequently than FreeDOS does, hence the spamming
the mailing list.
The next version so far has mostly IRCjr fixes and improvements. I'm
also looking into making it more
First, the good news - Watcom includes code at the start and end of each
function to detect stack overflows. It is a lot easier to debug code
when you know what the root cause of the problem is. If the stack
overflow were to happen and remain silent, you could have all sorts of
strange
On 12/20/2012 2:41 PM, Tom Ehlert wrote:
asking programming errors on a mailing list that is focused on
operating system development is considered BAD.
I don't think we have enough developers (OS or application) or enough
list traffic where we can afford to be picky ...
Mike
On 12/20/2012 3:11 PM, Ralf A. Quint wrote:
At 12:58 PM 12/20/2012, Louis Santillan wrote:
The Memory Model (Tiny vs. Small vs. Compact vs. Medium vs. Large,
.COM vs. .EXE) of the compiler could be causing the issue. Some
compilers used to default to Small. What compiler flags are you using?
The time to consider DOS compatibility is *before* you purchase the printer.
If your printer can do some form of PCL then you are probably safe. A
higher end HP laser printer should definitely understand PCL. Old Epson
printer emulation and PostScript would be acceptable too - a Brother
On 1/7/2013 5:34 AM, Russell Benson wrote:
Hi I have loaded freedos and I get to Welcome To FreeDos Operating system
C:\
What do I need to do to get into the system?
That is probably the best/only laugh I have ever had on this mailing
list ...
It reminds me of the introduction to an old
Most people have a favorite editor already; you have an uphill battle
if you think that one editor can replace the rest. Here are some
comments on your feature list:
- 8088 class machines should be supported. There is nothing in the
80286 or 80386 opcode set that should be required for a
On 1/29/2013 11:09 AM, Tom Ehlert wrote:
- An editor should be small enough to run on a 128K machine.
FreeDOS will not run on a 128K machine.
Ok. Then make it 256. You get the idea.
I haven't looked into the source code, but is FreeDOS really that much
of a memory hog where it will not boot
Tom,
Get up on the wrong side of the bed today? Why so defensive?
PC/MS DOS 5.x and 6.x will run in 256K with usable memory to spare.
PC/MS DOS 3.x will run in 128K with usable memory to spare. If FreeDOS
is designed/optimized for a bigger footprint then that's fair, but there
is nothing
1 - 100 of 118 matches
Mail list logo
