At 03:01 AM 10/9/2005 +0400, Arkady V.Belousov wrote:
MD> As the front line guy taking most of the tech support on EMM386 (and
MD> HIMEM), I herewith state that you are incorrect. HIMEM delayed loading
I _not_ say about loading HIMEM from command line, I say about CPU
detection and preven
At 02:36 PM 10/9/2005 +0400, Arkady V.Belousov wrote:
>> And how this should be look? Drivers doesn't return errorlevels,
>>whereas INSTALL= executed after DEVICE=.
MD> Perhaps you could have it conditional on a register return value from an
MD> application,
Even if I introduce new in
At 11:28 PM 10/10/2005 +0400, Arkady V.Belousov wrote:
MD> %IF CHECK386 DEVICE=EMM386
Why to duplicate checks, which already present in himem and emm386?
Why depend on on drivers to unload cleanly if they fail, which they already
do not always do in closed-source drivers, despite prot
At 12:39 AM 10/11/2005 +0200, Bernd Blaauw wrote:
Again a nice theoretic discussion :) Anyway, are FreeDOS related programs
and drivers also ment to be used on MSDOS or not as partial replacement?
The drivers could be used on MS-DOS freely, it is only the control programs
which would extend F
At 11:25 PM 10/11/2005 +0200, Bernd Blaauw wrote:
Markus Oberhumer seems to have his own website and seems quite active.
Maybe he's interested in your patch.
It's not in a good patch form consistently matching the rest of the source,
but rather a basic hack to make things work. Also, it forc
At 01:11 PM 10/12/2005 -0700, Blair Campbell wrote:
> minutes. Doubtful they'd be interested in a patch that wasn't good to
> insert as-is at the time of submission.
Can you at least make it available for compressing other things like Turbo
disk?
When I post next release HIMEM and EMM386 (n
At 02:27 PM 10/11/2005 -0700, Blair Campbell wrote:
> bypassed. After three days of on-and-off hacking on it, I built a mutant
> UPX 1.25 to compress EMM386.EXE and HIMEM.EXE to work both as a device
> driver and as a stand-alone EXE file. As almost always is the case, the
> actual changes wer
At 04:02 AM 10/13/2005 -0500, I wrote:
I have uploaded a file called mods-upx125-dos.zip in directory
ftp.devoresoftware.com/downloads/emm386 which contains the two modified
files, p_exe.cpp and l_exe.asm. These changes were used to compress HIMEM
and EMM386 with revised UPX 1.25. They have
Andre Tertling <[EMAIL PROTECTED]> said
>
> Hi there,
>
> recently, I read quite some discussion about network support under DOS
> on this list, but couldn't make up a consistent picture from the details
> mentioned. That is why I would like to ask for more information and
> especially about wha
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386 are the files
emmx207.zip, EMM386/HIMEM mostly executable package, and emms207.zip,
EMM386/HIMEM mostly source package. Also available are the files
nhimem.zip, nomyso.zip, and mutant-upx125-cygwin-exe.zip.
Version 2.07 of EMM386 fixes
Message clarification #1: The converter file is named nomyso10.zip, not
nomyso.zip
Message clarification #2: NASM may generate harmless warnings if you
recompile other MASM/TASM source code, making complaints about redefinition
of segment attributes. Test files show these warnings are trigg
Message clarification #1: The converter file is named nomyso10.zip, not
nomyso.zip
Message clarification #2: NASM may generate harmless warnings if you
recompile other MASM/TASM source code, making complaints about redefinition
of segment attributes. Test files show these warnings are trigg
Message Clarification #3. It's the HX DOS Extender, nor HRX.
Such are the fruits of staying up all night to get the thing out the door.
To make this slightly more useful, here are links to items mentioned in the
original message:
HX Extender: http://www.japheth.de/HX.html
Cygwin site (you
At 10:29 PM 11/15/2005 -0800, Brolin Empey wrote:
Michael Devore wrote:
And another warning: NASM done got it some bugs. Even with the
relatively modest source of HIMEM, I hit a couple.
Have you told the NASM maintainers about these issues? I think they would
probably be interested in
At 11:29 AM 11/17/2005 -0800, Quentin Liedtke wrote:
I'm having a real tough time trying to get FreeDOS to boot from a USB
flash drive and I'm hoping that the fine folks on this list might be able
to help me.
Hardware I'm using:
- I'm using an Intel D865GBF motherboard with BIOS version
BF86
At 09:28 PM 11/17/2005 +0100, Bernd Blaauw wrote:
Michael Devore schreef:
(I do see that 256M Cruzer's can now be purchased for a mere 30 bucks,
but unfortunately between the new USB floppy drive for testing a laptop
with EMM386 VDS changes, the TASM upgrade, and the Red Cross thin
At 08:25 PM 11/22/2005 +0100, Almacha wrote:
I have a problem with the SBPCI Sound Driver under FreeDOS, could someone
help me ?
When I use the default configuration for HIMEM and EMM386 :
DEVICE=C:\FDOS\BIN\HIMEM.EXE
DEVICE=C:\FDOS\BIN\EMM386.EXE
I have then 32MB of EMS.
and then I try to loa
At 08:46 PM 11/23/2005 +0800, Johnson Lam wrote:
>I have a problem with the SBPCI Sound Driver under FreeDOS, could
>someone help me ?
You got the same problem as me, but I'm using SBLIVE.
Try to use:
device=c:\fdos\bin\emm386.exe memcheck x=test ems=1200
If you are using the latest EMM386
At 08:38 PM 11/24/2005 +0100, you wrote:
Anyone else seeing massive virus outbreaks?
I never imagined being able to use 40% of a 250MB hotmail emailbox (add 3%
each hour), but MS manages to not filter these (75KB attachment).
Even the "delete junkmail" button times out with 1400 emails.
Prett
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386 are the files
emmx208.zip, EMM386/HIMEM mostly executable package (EXEs compressed via
mutant UPX), and emms208.zip, EMM386/HIMEM mostly source package. Nomyso
version 2.0 was uploaded to ftp://ftp.devoresoftware.com/downloads/nomyso
na
At 11:02 PM 11/28/2005 -0800, Blair Campbell wrote:
Speaking of bugfixes, a person on FreeDOS IRC has mentioned many times
that the latest versions of HIMEM/EMM386 won't work with certain hard
drives, but will work with others. AFAIR, he also says that NOVDS
does nothing to change this.
Possi
At 11:52 PM 11/29/2005 +1300, Bart Oldeman wrote:
On Mon, 28 Nov 2005, Blair Campbell wrote:
PS: If the C is ever to be compiled with Watcom C, as Bernd
suggested, the global functions in the asm would need to have a _ in
front instead of behind, as this is (for some weird reason) the way
Ope
At 09:47 PM 11/29/2005 +0300, Arkady V.Belousov wrote:
Hi!
__O\_/_\_/O__
---> RETR /downloads/emm386/emmx208.zip
550 No such file.
Failure on 'RETR /downloads/emm386/emmx208.zip' command
failed to get /downloads/emm386/emmx208.zip
--->
At 07:15 PM 12/1/2005 +, Gerry Hickman wrote:
What we do know is this:
2. EMM386 with SCSI controllers and VDS enabled is completely unusable and
should never be tried outside the test lab.
What? Completely untrue. More like 2. EMM386 with SCSI and VDS works on
all tested systems, bu
At 11:02 PM 11/28/2005 -0800, Blair Campbell wrote:
I would personally really appreciate the ASM in FreeDOS HELP being a
test case, as this assembler won't even compile with Arrow Assembler
or the Watcom Assembler (which both use older MASM/TASM syntax,
afaik).
The only ASM file I found in Fre
At 01:27 PM 12/3/2005 -0600, I wrote:
The three people following to this point might wonder why Nomyso doesn't
just eliminate the 'DWord' in the $DEFINE statement and eliminate the
problem. Well, you can't automatically do that because the DWORD would be
necessary in some cases where you migh
At 08:37 PM 12/3/2005 +0100, Bernd Blaauw wrote:
Another victim / testcase could be UMBPCI, as it's written in TASM.
Either the 1995 version, or Uwe Sieber's current one
(sources only available on request)
My interests lie in converting sources which could help people without
destroying the o
At 12:53 PM 12/24/2005 +1100, John Mills wrote:
alan
Don't know if your program uses DPMI, but some out of memory problems can be
solved by disabling memory drivers e.g. EMM386/HIMEM, and letting DPMI take
over extended memory.
Nothing to do with a modern, e.g. FreeDOS version, HIMEM or EMM386.
At 12:44 AM 12/25/2005 +1100, John Mills wrote:
Thanks for info. I'm out of my depth here.
Apologies to anyone misled by my suggestion.
My EMM386 is version 1.13.
Current EMM386 version is 2.08. You're one major release, many minor
revisions, and a number of recommended updates behind.
At 12:22 AM 12/28/2005 +1100, John Mills wrote:
Can I run EMM386 2.08 with my Beta9sr1 installed?
Or should I download the Beta9SR2 iso, and download latest EMM386 separately
?
Any official FreeDOS build which isn't ancient should run with latest
EMM386 just fine. Most unofficial ones, too.
At 09:17 PM 1/18/2006 -0800, Caleb9849 wrote:
ARG! Can someone please help me with this? I'm trying to run an old DOS
Star Trek Game of mine. By DOS standards, it's pretty resource-heavy and
requires upper memory. So I added the lines into my fdconfig.sys to load
up emm386.exe (with the "n
Hi,
I ask me all the time if applications, which are written for MS-DOS, are compatible for working in FreeDOS. I know the question can't have a general answer but perhaps some additional thoughts can help me. Thanks a lot.
P.S.: (written in german) Antworten in Deutsch wären mir am liebsten
Hi,
is it possible to get r/w access to NTFS? I have the Winternals Admin Pack 5.0 which includes the NTFSDOS driver, but I don't know how to integrate it into FreeDOS. And ATM I can't find about native access to NTFS from FreeDOS.
The same question I have about USB access.
Thanks a lot.
At 08:40 AM 2/2/2006 -0600, Charles Peck wrote:
The first two drivers, generic ones-- protman.dos and dis_pkt.dos load
up fine, but when I try to load each individual network driver, the
entire process outputs an error, some hex, and hangs. I'm not sure
whether I have himem.sys and emm386.exe co
A FreeDOS user e-mailed these questions to me, concerning a subject about
which I know very little. If someone who knows more could reply to him
with decent information, that would be great.
From: Dimitris Dimitris <[EMAIL PROTECTED]>
Hello,
1) I installed MS Client 3.0 and the pc freezes w
Hi,
I ask me if FreeDOS can read and use Hardlinks. And if it isn't, is there a tool which makes it possible?
Thanks a lot.
Regards from Germany.
P.S.: You can answer me in german, too.
Aber solange ich die genannten Programme nicht aufrufe, ginge es, oder ?!
DOS ruft die Programme doch nicht etwa beim Booten auf, solange sie nicht in der autoexec.bat stehen?!
Am 13.02.06 schrieb Florian Xaver <[EMAIL PROTECTED]>:
Hi!Meinst du mit Hardlinks Datei-Links die auf einen anderen Eintr
Hi,
does a firewall for DOS exist? If it is, where can I find it?
Thanks a lot.
Regards
McStarfighter
P.S.: You CAN answer in german, too.
Oh yes I know what a firewall is. For MS-DOS i know that there is now firewall need, but DR-DOS / FreeDOS is perhaps another thing. Ok, there is no firewall and that is all I wanna know. Thanks to you.
2006/2/13, Robert Riebisch <[EMAIL PROTECTED]>:
Michael McStarfighter wrote:> does a
At 08:05 PM 2/15/2006 +0400, Senthil Kumar wrote:
Can we load Himem.EXE w/o using gate A20 method. If so, whats the himem
loading syntax in config.sys
Assuming you are asking what you appear to be asking, the HIMEM option
/METHOD: will allow you to force the exact A20 method you want to
use.
At 11:19 AM 2/19/2006 +0400, Senthil Kumar wrote:
Thanks for your feedback. I have checked and found the m/c is hanging
after loading the HIMEM with the option /METHOD:ALWAYSON.
However I am checking further and update you the progress.
That would suggest the machine does not always have the A2
Last night I picked up a few off-brand 128M USB sticks and tried formatting
them to boot FreeDOS on my system. As a pleasant surprise, the latest
FORMAT 0.91v and SYS from 2/20/2006 32-bit kernel formatted all three
brands to FreeDOS-bootable sticks -- although each received a runtime
FORMAT m
At 09:27 AM 2/28/2006 -0500, Mark Bailey wrote:
Hi Michael:
I received a sealed envelope from you yesterday. It contained
a card with a note about a white cover but no USB stick! :-(
Did the stick fall out or something?
Ha, if there's not a hole somebody nabbed it. And it was worth a
At 03:46 PM 2/28/2006 -0600, charlie_chan wrote:
As a postal worker for 22 years, I will tell you with certainity that if
you use an envelope to mail it you made
a mistake. Every post office that processes mail and some that don't have
a collection items that should
never have been mailed in
At 07:36 AM 3/14/2006 +1000, TechFan wrote:
I saw a thread go around earlier about using a bootable USB key. Did
that get polished or handled? I have an extra USB key to play with, but
I would like to make it bootable. . .getting tired of using the very
slow usb floppy drive to boot our ghosti
At 08:20 PM 3/14/2006 +, Gerry Hickman wrote:
My own issue is that I can create a stick which either boots as a big
floppy (A: via USB-ZIP) or a hard drive (C: via USB-HDD), but I can't
seem to switch back and forth between the two types after I'm done.
I'm not sure what you mean, but in g
At 12:55 AM 3/15/2006 +0300, Arkady V.Belousov wrote:
14-íÁÒ-2006 00:11 [EMAIL PROTECTED] (Michael Devore) wrote to
freedos-user@lists.sourceforge.net:
MD> My own issue is that I can create a stick which either boots as a big
MD> floppy (A: via USB-ZIP) or a hard drive (C: via USB-HDD),
At 11:09 AM 3/15/2006 +0300, Arkady V.Belousov wrote:
MD> If I start up FDISK, it sees a partition on the USB
MD> stick. If I then use FDISK to remove that partition, afterwards the USB
MD> stick cannot be accessed by FreeDOS tools (including FORMAT or DEBUG) or
MD> Windows re-format.
Of
At 12:07 PM 3/15/2006 +0300, Arkady V.Belousov wrote:
15-íÁÒ-2006 02:36 [EMAIL PROTECTED] (Michael Devore) wrote to
freedos-user@lists.sourceforge.net:
MD> Yes. Creating a new partition with FDISK doesn't work. It thinks it
MD> works, but the stick remains unusable until the HP too
At 07:36 AM 3/17/2006 -0800, Andrew Greenberg wrote:
Hi everyone,
HIMEM64 3.11 [Apr 09 2004] has worked solidly for us across many
machines. We thought we'd try the latest version, HIMEM64 3.12
[09/11/2005] but it consistently is freezing on us, especially on thinkpads.
Booting from a CD, with
At 04:50 PM 3/17/2006 -0800, Andrew Greenberg wrote:
-
DEVICE=A:\DRIVERS\HIMEM.EXE
SHELL=A:\COMMAND.COM A:\ /E:1024 /MSG /P=A:\AUTOEXEC.BAT
DOSDATA=UMB
DOS=HIGH,UMB
FILES=20
BUFFERS=20
LASTDRIVE=Z
SET BOOTDISK=A:
SET DIRCMD=/p /ogn
SET LANG=E
Hi,
I want to know if the "original" FreeDOS kernel is 16bit or 32bit. I ask it because I coincidentally found the website http://freedos-32.sourceforge.net/ and I want to use 32bit tools in FreeDOS, too (perhaps).
Thanks for answer.
P.S.: Answering in german language is preferred for me
At 10:55 PM 3/21/2006 +, FreeDOS Ankreuzen wrote:
Yes on some mainbords PC s with PENTIUM II, there is a problem
to install FDOS BETA 9SR2 from CD.
If it s possibel use a Bootdisk with old FreeDOS Version
and pre-install FreeDOS manually.
Please tell me if you are using a Pentium II or whic
At 02:07 PM 3/25/2006 -0600, I wrote:
As an alternate choice, you might try locating the actual problem, which
likely is not within EMM386 itself, rather than telling people to use
obsolete versions of software which won't fix the underlying problem and
which fail to provide a full range of mac
EMM386 X=A000-EFFF NOVDS NOEMS is probably the most compatible option
setting for a computer which doesn't use EMS. Later, you can add areas for
UMB inclusion and possibly turn back on VDS services when you have ensured
that minimal operation works. If you require EMS, then remove NOEMS.
At
At 06:15 PM 4/14/2006 -0400, you wrote:
Hello, all. Here is another issue arising from my check-out of the new
Service Release 2.
I find that loading EMM386.EXE can cause Ctrl-Alt-Del to fail. I boot
fine, then press Ctrl-Alt-Del from the DOS prompt. The screen goes black,
but the video an
At 09:29 AM 4/15/2006 -0400, you wrote:
So I added back a range exclusion, thus: NOEMS X=A000-EFFF VDS NOALTBOOT.
This booted up in unstable condition, locking altogether (or with
Ctrl-Alt-Del still not working).
I increased the exclusion to the range that one of you had recommended:
NOEMS X=A0
QHIMEM is a totally new and alternate -- utterly superfluous in my opinion
-- memory manager that can have nothing to do with your problem, and I do
not recommend it's use for debugging here.
There is no correlation between the HIMEM-style memory manager and an
application's use of upper memor
At 01:17 PM 4/17/2006 +0800, Johnson Lam reposted a private e-mail:
What I suggest you reflect upon, Mr. Lam, are your personal reasons for
posting this entire private e-mail to the public list. It serves little
purpose here other than to incite more anger and hurtful retaliatory
remarks.
At 01:43 PM 4/19/2006 +0800, Johnson Lam wrote:
Forward an email from Jack, hoping everyone can understand what's
going on, I'd like the others to understand the whole thing, not out
of context:
It is a flame, as you well know, but it seems you have become immune to any
sense of hesitation
At 09:04 PM 5/2/2006 -0400, Mark Bailey wrote:
Bad or missing Command Interpreter
Enter the full shell command line:
command.com /P /E:256
The development kernel fixed the "Error in the DJ mechanism!" but still
doesn't find the shell. Any suggestions? Is there a problem with SCSI
drives?
Do
At 04:48 PM 5/3/2006 -0400, Mark Bailey wrote:
Thanks very much. I'll have Steve try to trace the problem.
I am rather DOS illiterate, I'm afraid. What do you mean by
"Will the SCSI base address conflict?" Do you think the BIOS
grabs some high memory that emm386 might affect? The
current fdco
At 09:07 PM 5/3/2006 -0400, you wrote:
Steve tells me it works without emm386 loaded, but fails with
X=test and NOVDS. Is there any way to debug this remotely?
Separately fails with each option, or just together? No remote debugging
that low-level on DOS. Looks like he might have one of th
At 12:02 AM 5/5/2006 +0300, dima wrote:
Hello.
Does anyone there have experience about how to run "x-com apocalypse" under
FreeDOS?
Send the game to me or tell me where to grab it; I'll take a look.
---
Using Tomcat but need to do more? Ne
At 04:52 AM 5/5/2006 +0200, Eric Auer wrote:
of course this is unrelated to the problem that
Descent and some other games with DOS4GW DOS extender
do not run well in plain FreeDOS. The problem does
not seem to occur in DOSEMU. This can mean that either
emm386 / himem have a compatibility problem
At 11:28 PM 5/5/2006 +0800, Johnson Lam wrote:
Mister,
>I also don't like this sort of extremely early speculation coming on the
>heels of Mr. Lam's recent spate of ridiculous posts, because it just feeds
Thank you for your "praise".
>into him posting more irrelevant advice about trying alter
At 12:09 AM 5/6/2006 +0300, dima wrote:
Game won't to run without himem and emm386 or fdxxms and umbpic, cause not
enough memory.
> I found that it also helped to run the game with DOS32A
> instead of the built-in DOS4GW. You can get it here:
Yes, sometimes it helps. But in this case I have su
At 12:09 AM 5/6/2006 +0300, dima wrote:
Game won't to run without himem and emm386 or fdxxms and umbpic, cause not
enough memory.
Okay, I stole a 48M Pentium 133Mhz laptop from the clutches of a Cro-Magnon
in a passing time-rift and tried the game out on that. Under FreeDOS
SETUP.EXE still d
At 12:09 AM 5/6/2006 +0300, dima wrote:
This is screenshot with error message:
http://www.geocities.com/x696365/stuff/xcomap01.zip
Okay, final progress report for a while. I installed new DOS sound drivers
on the old machine. After the installation I was able to successfully run
the xcom g
At 04:23 AM 5/6/2006 +0800, someone who refuses to directly face those he
accuses wrote:
>As far as I remember, Jack did not want to tell us about the
>four (if I remember correctly) critical bugs in himem/emm386,
>so Michael cannot fix them either. He only told us THAT there
>a
At 08:11 PM 5/6/2006 -0500, I wrote:
I happen to believe that FreeDOS HIMEM probably does still contain an
obscure bug or two. Maybe even three.
I did fix a fairly obscure HIMEM bug today, as a matter of fact. Haven't
found anything which needed the fix, but it was definitely a
deviation-fr
At 11:38 AM 6/5/2006 -0400, John Hupp wrote:
> I could also have added that all my DOS games (Doom, Quake, Duke,
> Spacequest, Beneath A Steel Sky) run fine on this computer and configuration.
>
>On the chance that there was a physical memory problem I dropped from 16
>to 8 MB (no difference),
I found a site by George Potthast and unfortunately though I got his
USB2 driver to work for a while, it stopped working. Another concern,
he wants an atrocious amount of money for a copy that doesn't stop
working. I'd much rather donate $600 to the freedos maintainers to
advance the support of U
On Wed, 2019-05-08 at 15:38 -0400, Karen Lewellen wrote:
> Hi Michael,
> I have a DOS USB driver created by Panasonic that is Excellent.
> If you desire a copy, write me privately and I will share.
> Karen
Are you talking about aspidos.sys and di1000dd.sys? They work together
a
oping the
capability to restore the analyzer's system to an outside hard drive.
This Panasonic driver may be ghost compatible and I may be able to
restore directly onto the external drive. In that case, I won't have
to worry about getting a boot loader on and preserving long filenames
On Wed, 2019-05-08 at 15:21 -0700, Ralf Quint wrote:
> On 5/8/2019 1:37 PM, Michael Christopher Robinson wrote:
> > Before Windows 2000, even in Windows 95, FAT32 was introduced with
> > supported for longer filenames than the 8.3 limit of Dos 6.22.
>
> Sorry, but this not c
passing the whole long filename problem.
-- Michael C. Robinson
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
On Wed, 2019-05-22 at 01:10 +0200, Eric Auer wrote:
> Hi!
>
> > The two aren't currently compatible.
>
> Which problems did you encounter in which context?
Opcodes and hard crashing of a lfndos aware file manager something
commander. I was trying to copy to a fat32 partition out on usb
created
nment on Freedos, but how do you implement the WIN32 API or does
wine work with FLTK and Freedos?
-- Michael C. Robinson
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Is it possible to get the source code to Windows 9x and ME since
Microsoft isn't supporting it anymore?
One would want to get the source code and then open source it of
course. Even Windows 3.1 and Windows 3.11 is closed source. Surely,
Microsoft could release pre 9x Windows? It wouldn't h
Quoting andrew fabbro :
On Thu, Sep 26, 2019 at 6:36 AM Michael C Robinson <
mich...@robinson-west.com> wrote:
Is it possible to get the source code to Windows 9x and ME since
Microsoft isn't supporting it anymore?
One would want to get the source code and then open source i
d Wine, and it would
be good if the old MS source code could be released, or, failing
that, the binaries could at least be put under an open-source
license that explicitly allowed reverse engineering.
Original message
From: Michael C Robinson
Date: 9/26/
Quoting Ralf Quint :
On 9/26/2019 6:35 AM, Michael C Robinson wrote:
Is it possible to get the source code to Windows 9x and ME since
Microsoft isn't supporting it anymore?
No.
One would want to get the source code and then open source it of
course. Even Windows 3.1 and Windows 3.
rce and supported across both heads.
-- Michael C. Robinson
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Note that I am running it in VirtualBox on an AMD FX 8350 processor
with 8 cores.
Might have something to do with CentOS 7 x86_64 as the host system.
Maybe I'm giving freedos too much ram?
Can anyone else reproduce the Bolitare black screens on exit issue?
-- Michael Rob
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.
>
> reg
ing lftp) have
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 proble
On 2/23/2011 2:47 AM, teo gum wrote:
> Please explain me how to setup an IRC client under DOS.
> Supposed that an internet connection already run.
> A sample config should be the best (I'm a humanitarian a Slavic
> filologist :)
> - with an explanation where to put target server and where somethin
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 for
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 f
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 DHC
Is there a dos driver for a standard 4x scsi cdrom reader connected to
an Adaptec 2940U2W?
--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your c
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
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 alon
701 - 800 of 993 matches
Mail list logo
