Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386/ are the files
emmx226.zip, EMM386 2.26 and HIMEM version 3.26 memory manager, mostly
executable files; and emms226.zip, source code files. The FTP-challenged
may find the files at http://www.devoresoftware.com/emm386 .
EMM386 2.26 is r
At 02:50 PM 8/21/2006 -0600, Eddie wrote:
>I was really hoping that this problem had been silently fixed by
>all of the other work that has been done recently.
Doesn't look VDS-related, the executable only uses a couple of common calls
there. Not much more I can tell you. Maybe the origina
At 02:50 PM 8/21/2006 -0600, Eddie wrote:
> I was really hoping that this problem had been silently fixed by
>all of the other work that has been done recently. I was disappointed
>when the same problem cropped up again - because that means more work.
>
>So far I haven't done the work to iso
At 09:37 AM 8/21/2006 +0200, Norbert Remmel wrote:
>During testing I discovered a bug concerning STR-ALT-DEL usage.
>When pressing these keys, freedos crashes with invalid opcode outputting
>some memory addresses and registers.
Eric made a change suggestion which seems to clear up the problem with
At 09:37 AM 8/21/2006 +0200, Norbert Remmel wrote:
>During testing I discovered a bug concerning STR-ALT-DEL usage.
>When pressing these keys, freedos crashes with invalid opcode outputting
>some memory addresses and registers.
>As I remember this wasn't like this using earlier versions of
>himem/
At 05:15 AM 8/21/2006 -0600, [EMAIL PROTECTED] wrote:
>This problem occurs when using SMARTDRV.EXE (with write caching
>enabled) from MSDOS 6.22 with FreeDOS. Replacing either avoids the
>problem.
SMARTDRV is pretty particular on some machines. I just pulled the
following from the Microsof
At 06:50 PM 8/21/2006 +0200, Norbert Remmel wrote:
> You should also be prepared to send/sponsor this network card to
> >>> I really would like to do but my boss would cut my head off if I would
> > AT> That's just another way to solve the problem :D
> > AT> SCNR ;)
> >
> > What is SCNR?
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386/ are the files
emmx225.zip, EMM386 2.25 and HIMEM version 3.25 memory manager, mostly
executable files; and emms225.zip, source code files.
This release of EMM386 and HIMEM works around a bug in some BIOS chips
which affects HIMEM, impro
I've uploaded to ftp://ftp.devoresoftware.com/downloads/emm386/ the file
himem324.zip, containing a revised HIMEM executable and source file changed
from version 3.23.
This is an alternative version of HIMEM I'm making available for
testing. It is only slightly modified from the previous versi
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386/ are the files
emmx223.zip, EMM386 and HIMEM version 2.23 memory manager, mostly
executable files; and emms223.zip, source code files.
This release of EMM386 and HIMEM should improve compatibility with some
DOS-extender applications, suc
I still can't read your list mails very well, but I was able to pick
through most of this. (No, my e-mail utility which has worked for a good
many years and doesn't fail on other user comments is not buggy and
therefore in need of replacement. Although, it could use an update or
change-over fo
At 06:37 PM 8/4/2006 +0200, Japheth wrote:
> The issue is of minor general interest, since most FD users will
>use FD Himem and FD Emm386 with the standard parameters.
I've finally been able to duplicate a problem with DOOM under VPC 2004 set
at 512M, but not under straight FreeDOS with 1.5G fr
At 02:36 PM 8/4/2006 +0200, Japheth wrote:
>or if another Emm386 compatible XMS host is used (MS Himem or QHimem2),
>which lacks this (NO)X2MAX32 parameters at all
Incidentally, if anyone wants to see why HIMEM/XMS managers should support
a /X2MAX32 option, I have available a copy of the
At 06:37 PM 8/4/2006 +0200, Japheth wrote:
>The test case you are requesting, yes, sure, I didn't do that yet, since
>dealing with a fixed bug is like reading the newspaper of the day before
>yesterday. Compare this my lack of interest with your's not wanting to
>provide
>a working build environ
At 08:29 PM 8/4/2006 +0400, Arkady V.Belousov wrote:
>you. In Japhet' source, I see _at least_ one important change: you
>eliminate "retf 2", but forgot "ret 2" in NEW15 (where you explicitly STI
>before exit). This not need any demonstrations.
Nor was it reported.
> But I agreed, th
At 10:29 AM 8/4/2006 -0500, I wrote:
>At 01:22 PM 8/4/2006 +0200, Japheth wrote:
> > >
> > > Barring the fileset I requested, or other testable indication that your
> > > problem occurs with anyone else, I should not think that would be a
> > > problem. In other words, no need to wait for EMM386
At 01:22 PM 8/4/2006 +0200, Japheth wrote:
> >
> > Barring the fileset I requested, or other testable indication that your
> > problem occurs with anyone else, I should not think that would be a
> > problem. In other words, no need to wait for EMM386 3.0 - codenamed "The
> > Arkady Factor".
>
>Si
At 10:46 PM 8/3/2006 +0200, Japheth wrote:
>Blair Campbell wrote:
> >> I renamed directory FDOS to FDOSALT. About 6,5 MB free space are left
> on C:
> >>
> >> - I booted from CD and select Install, FD does not complain!
> >
> > I am so sorry. I forgot to include the updated install.exe ! I
>
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386/ are the files
emmx221.zip, EMM386 version 2.21 memory manager, mostly executable files;
and emms221.zip, source code files.
This release of EMM386 has a few fixes and changes, mostly directed to Qemu
and FDAPM users, although those modi
At 11:44 AM 7/28/2006 +0200, Norbert Remmel wrote:
> > Use X=A000-EFFF NOVDS
> >
> > Remove all device drivers.
> >
> > Then change and add as booting works.
>
>O.K. did it and found out the following...
>
>So far no pc crashes with vds disabled (I have not tested all pcs yet,
>but these having had
At 03:02 PM 7/28/2006 +0200, Eric Auer wrote:
>Would it be possible to have a test binary where the A20
>trick is disabled and another one where the IF trick is
>disabled? Then those, for whom the update makes things
>worse, could check which of the changes caused that.
A20 might be controlled th
At 10:39 AM 7/28/2006 +0200, Japheth wrote:
>On my machine A20 is always enabled. BIOS int 15h reports kbd and "fast" PS/2
>methods being available, but none works to disable A20. IMO if A20 cannot be
>disabled in real-mode, emm386 shouldn't try to emulate "A20 disable" in
>v86-mode.
I thought a
At 02:34 AM 7/28/2006 -0500, I wrote:
>Use X=A000-EFFF NOVDS
>
>Remove all device drivers.
>
>Then change and add as booting works.
Also, pure boot failure almost has to be A20-related. Nothing else is
related to vanilla-configured boot. Manager, kernel, hardware, driver,
application, somethin
At 09:18 AM 7/28/2006 +0200, Norbert wrote:
>Do you have an idea, why the Pentium III machine is o.k. now and the
>others not?
Use X=A000-EFFF NOVDS
Remove all device drivers.
Then change and add as booting works.
-
Take
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386/ are the files
emmx220.zip, EMM386 version 2.20 memory manager, mostly executable files;
and emms220.zip, source code files.
This release of EMM386 and HIMEM has several changes and fixes, two of a
low-level nature, but at a guess, relati
At 02:20 PM 7/24/2006 +0200, Japeth wrote:
>I was advised (thanks Eric!) that there exists a "SB" option for FD-Emm386.
>Setting this option indeed cures the SB MPU issues for the protected-mode
>games I tried.
The SB option is easily the goofiest option I've added to any program I've
worked on
At 09:31 AM 7/25/2006 +0200, Norbert Remmel wrote:
>As promised detailled error description...
>
>PC description:
>Intel Pentium III 600 MHz
>256K Cache
>ASUS P2B Motherboard (Intel 440BX Chipset, AWARD ACPI Bios Rev. 1012)
>384 MB SDRAM (133 MHz)
>
>3COM 309B 10/100 PCI Ethernet Adapter
>
>Config
At 07:56 AM 7/24/2006 +0200, Japheth wrote:
> > But: DOOM does work with the current himem/emm386.
>
>As for me this is true for the newest versions of himem/emm386 (July 2006)
>only. In fact, any DOS4G application didn't work with FD-Emm386 previously
>because my machine has 768 MB.
Generally s
As a matter for record, since it's been incorrectly reported twice now:
FreeDOS, HIMEM, and EMM386 work fine with Doom. It was one of the first
tests of VCPI support and is often checked against as a baseline. There
are no known applications which fail under FreeDOS HIMEM or EMM386 with the
F
At 06:20 PM 7/18/2006 +0200, you wrote:
>There is a bug left in the FD-Himem.exe memory manager.
Nope. But see further...
>When a program that had allocated several XMS blocks doesn't release these
>blocks in the order FD-Himem likes it, it will report a too small "largest
>free block". Luckily
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386/ are the files
emmx211.zip, EMM386 version 2.11 memory manager, mostly executable files;
and emms211.zip, source code files. 2.11 is a minor update from 2.10 --
minor, of course, unless you need it.
EMM386 2.11 fixes a problem with a few
At 09:21 PM 7/12/2006 -0400, Keith Weisshar wote:
>Microsoft just released VPC 2004 as freeware today. When I install from
>the FreeDOS ISO under VPC 2004 I get an CRC error on mode.com with missing
>required package.us during install and at the end of the install and I
>reboot I get a missing
At 10:18 PM 7/8/2006 -0500, Michael Devore wrote:
I used the newest release UPX 2.01d to compress this version of EMM386 and
HIMEM. It saved about 400 bytes for EMM386.EXE and 200 bytes for HIMEM.EXE
over the old mutant UPX.
Yeaaa, the new UPX works with DOS EXE/SYS files. Yeaaa, the UPX
Uploaded to ftp://ftp.devoresoftware.com/downloads/emm386/ are the files
emmx210.zip, EMM386 version 2.10 and HIMEM version 3.13 memory managers,
mostly executables; and emms210.zip, source code files for the new release.
The latest revisions (effectively completed in May) contain several
compa
At 11:38 AM 6/5/2006 -0400, John Hupp wrote:
>I am using current stable:
>kernel - 1.1.35 Build 2035b-cvs, 2006-05-21
>freecom - 0.84-pre XMS_Swap, 2006-05-21
>himem + emm386 - from emmx208 or emm208x ZIP archive
>
>I might have added to the original post by saying that this problem does
>not occ
At 04:39 PM 7/3/2006 -0500, Neal Gompa wrote:
>Yet, without much modification to the configuration of the system, and
>grabbing some proprietary utils, it cannot run Windows for Workgroups...
>It is better, I agree, but to be fully compatible, it should run one of
>the most complex apps out of t
At 01:19 PM 6/21/2006 +0200, you wrote:
>Hello! It's me again.
>
>I changed my compiler back to Open Watcom 1.1, because 1.2
>can't compile the Duke Nukem 3D source code. :)
>
>But now, I have a problem: it comes with an old version of
>CauseWay, and I don't know how can I update to the latest
>CW.
At 08:26 AM 6/15/2006 -0500, jp_freedos wrote:
>On Thu, Jun 15, 2006 at 07:44:08AM -0500, Jim Hall wrote:
> > I'm sorry my president's an idiot. I didn't vote for him.
>
>Clinton is not President anymore.
Clinton was, among other things, a Rhodes Scholar, and generally conceded
as brilliant by hi
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),
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 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
>are bugs, but did
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 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:
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 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 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 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 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 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: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 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 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.
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 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
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
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 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
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 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
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 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 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: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 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 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 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 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 whole
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 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
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.
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
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
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
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 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: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 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 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 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 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 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 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 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
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 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
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: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 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 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 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
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
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
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
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
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 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 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 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: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
1 - 100 of 274 matches
Mail list logo
