Jack wrote:
> Japheth,
>
> I noted your reply to Eric Auer on FD-User re: the idea of
> over 4-GB for DOS, in which you wrote:
>
>> PAE paging most likely isn't needed, the simpler approach
>> "32-bit paging with 4 MB pages" should do as well.
>
>
#x27;t needed, the simpler approach "32-bit paging with
4 MB pages" should do as well.
japheth
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integr
Hello,
> Japheth, I tried what you said: ran hdpmi32 -r-m, then the exe, and it
> worked;
> then tried cwsdpmi -x then the exe, that also worked. Remaining question:
> how do I "build-in" the '-x' switch at compile time? The sandman site
> does not address
> Eric, the program I wrote, which drew the page fault, uses the int86 in
> four of the eight functions. the program
> is a mouse event handler, and "micro-gui". I already had included
> 'dos.h', but I did not realize ther was a 'dpmi.h'!
> I'll have to pry into that header to try to see what exa
>> Internet Exporer 5 and earlier, maybe 6.
>
> Hardest-core CRAP, please don't pull it out if it's grave.
Using IE 5 instead of Arachne is a good idea. It has support for the MS
version of JavaScript (JScript) and runs even on Windows 3.11 standard mode.
This makes it render a lot of web sites
Hi,
> Blake Stone Aliens of Gold requires the MS-DOS 6.22 or the Windows 9x
> version. It can run on top of Windows 9x.
>
> Wolfenstein 3D has the same problem because it's probably based on the
> same underlying engine. It starts under Freedos, but none of the keys
> work.
I just tried BS and
> Yes, I prettymuch get that, but for instance that djgpp hack someone
> mentioned; it has a file named
> 'makefile', but in what directory should it be placed?
I guess that you are refering to my previous post. It's hard to follow because
the newsreader which I use did put your recent post i
Hello
> Ahhh, it's amazing; not one tutorial specifically for the dos version of
> 'make'; even what there is, not too
> specific. To wit: indeed, some thing you are trying to install,say , HX,
> GEM, etc., they do include makefiles,
[snip]
You mentioned HX so I'm forced to feel somewhat "resp
> Are the BLASTER settings described anywhere in detail? VPC says it
> emulates the Creative Labs Sound Blaster 16 ISA Plug and Play. Maybe my
> settings are wrong.
You can use the GETSB.EXE tool which is contained in HXGUI
(http://www.japheth.de/hx.html). It reads the SB16 mixer status direct
> why do you think that the RxDOS kernel is superior - besides having
> many more bugs ?
What about built-in support for LFN?
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With
> also many things are running in background :)
> just ask Eric, Mateusz, Rugxulo, Blair, ...
That's probably one of FreeDOS's problems: there's ony guy - I don't want to
be more specific - who forces all communication into private mails. This makes
the current FD status absolutely intransparen
> Hope you don't mind me to ask, why didn't you rather contribute to FreeDOS?
But he DOES contribute to FreeDOS: once the few remaining bugs are fixed in
the RxDOS kernel, it will replace the inferior current FD kernel.
---
> PS: What does all that tell us about compressed FS...?
I'm a gentle and polite person, so I will try to answer your question, just in
case you asked me: it probably tells us nothing about compressed FS.
However, if someone decides to reply to your extraordinary brief posts then
it's virtuall
>>> Would you want a compressed filesystem at all?
>>> My discouraging answer: I just don't need it.
>
>>> I think, what FreeDOS needs for daily use is a good graphical web
>>> browser, a nice e-mailer, a word processor like Abiword, FOSS USB
>>> drivers, ...
>
> In what way would FreeDOS differ
Hello,
in the latest FreeDOS kernels (from 03/2008 and 09/2007, AFAIU they are called
2038 and 2038pre) there might be a tiny incompatibility concerning the Ctrl-C
handling.
As a test case I use this version of the FTE editor:
http://www.japheth.de/Download/FTE-HX.zip
Once a text file has bee
>> 2. use Jemm386 instead of JemmEx and continue to use your previous
>> XMS host.
>>
>> 3. JemmEx's source can be extended to be able to manage more than
>> one block. This means some work, because the current implementation
>> isn't very flexible.
>
> Nothing wrong in my fdconfig.sys?
> JEMMEX.E
> Sorry for long responce. I was update Jemm, because previous version
> have no xmsstat. The xmsstat output attached as memstat.zip.
the report for Jemm did display
no handle regionsize(kB) locks flags
1 00A8 0011-0
>> Try to use no or another emm386: FreeDOS EMM386, JEMM386, JEMMEX?
>> Also read the docs for the "compatible safe" settings :-)
>
> Hmm. With an 'jemmex' i've got some gifts: more free conventional
> memory (about +3 kb.) and Nautilus works VERY WELL in this
> configuration. However, I lost some
Hi,
an update for JWasm was necessary, now v1.91 is current. The update is
strongly recommended, v1.9 contains a pretty nasty bug in 16bit code
generation, bad code might be generated without warning.
Besides bugfixes, there's one improvement: the /bin switch allows to create
raw binaries, no
> Note that JWASMD, a WASM variant with MASM .asm support, needs
> the HDPMI32 DOS extender in your PATH. See www.japheth.de ;-).
there's now JWasm v1.9 available, which contains a stand-alone DOS binary.
download: http://www.japheth.de/JWasm.html
changelog: http://www.japheth.de/JWasm/history.t
Both problems with the keyboard and the mouse are known and were already
posted in this list. However, the posts were related to Qemu, not VirtualBox.
Since VirtualBox is - to a large degree - a clone of Qemu, the issues occur
with this virtualizer as well.
There exist workarounds. The Ctmouse
>> It's fixed in v1.8.
>
> Odd, my report already was about 1.80 ...
Ok, then you forgot to tell us that you have access to a time machine. Because
the versions stored on my site are v1.7 and v1.8pre.
> Then an error message would have been better than a 0 value...
Sure. Looking back, many thin
>
> Maybe it is context sensitive in TASM, 0 in .data and nop in .code?
> I believe NASM has a whole range of ways to align things, including
> "pad with user-specified value" and "pick a multi byte noop machine
> code instruction where appropriate" but you would have to check the
> docs which is
Hi,
thanks for posting your results!
> - TASM evendata pads with 0, JWASM even pads with 0fch
> I do not know how to change this, I just used "db 0".
this is indeed hard-coded in the source and will be used only if a 16-bit CODE
segment has to be padded by 1 byte. The reason why not just 0x00
> Hi :-)
>
>> v1.13 of FD Debug is available: http://www.japheth.de/debxxf.html.
>> v5.71 of Jemm is available: http://www.japheth.de/jemm.html.
>> Both are just bugfix releases, and the bugs fixed are minor.
>
> Nice,
Thanks for your kind remark! :)
> but could you update the two readme files
Hello,
v1.13 of FD Debug is available: http://www.japheth.de/debxxf.html.
v5.71 of Jemm is available: http://www.japheth.de/jemm.html.
Both are just bugfix releases, and the bugs fixed are minor.
-
This SF.net email is spon
Hello,
Debug v1.11 is out. 7 bugs have been fixed (same as in Jemm v5.70 - seems to
become my new "standard"). Also, debugx can now display floating point
registers much nicer. So this update is highly recommended - at least for
those who still know what DEBUG is good for.
1.11 [06 Febru
> The forum discussion suggests that most of the bugfixes
> in jemm386 5.70 fix minor or rarely occurring bugs :-).
Yes. The one thing which I'm unable to decide whether it's relevant is the
lacking reentrancy of v5.69 converning XMS block moves. A TSR which hooks the
timer interrupt and then c
... is out:
http://www.bttr-software.de/forum/forum_entry.php?id=3132&page=0&order=time&descasc=DESC&category=all
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://cl
is out. It can be found at http://www.japheth.de/jemm.html
changes for v5.69
- memory block copies are now done with interrupts enabled - if client's
interrupt flag is set. This avoids interrupt latency and makes the
previously implemented "interrupt windows" obsolete. It also avoids
problems wi
>> I'm happy that this thing - which is old and hard to maintain...
>
> But I was talking about hdpmi32...!?
Yes, me too. hdpmi32 v1.0 (10/1993) is older than FreeDOS v0.001
-
This SF.net email is sponsored by: Microsoft
De
> Actually: Why does hdpmi use a non-1:1 mapping linear/physical?
> I mean it has every right to do so, but it turned out that this
> can make DPMI usage a bit more foolproof ;-). I assume it saves
> a bit of page table space? Being NOT foolproof can be good as
> it can help to detect bugs, but oto
> PS: The CTS Toasted 1996 ctstoast demo runs okay in LFB
> mode if CWSDPMI is resident or if you use DOSEMU, but I
> promise you that I did not write CTS Toasted and did not
> ask the authors to give it the same bug as PCXTEXT ;-).
I don't understand what you are talking about. There was a bug in
>
> Just tell me what the bug is :-).
>
in vesainit.c, search for "/* update */"
>> It happens to run with CWSDPMI, but I'm almost
>> sure this is the only host it really runs with.
>
> What is special about CWSDPMI (and DR EMM386) then?
I don't know.
> Even easier, you can tell DOSEMU to em
> You can download it as part of my NEWTRACK eye-tracking DOS
> software, and of course you need no dual VGA for PCXTEST ;-).
>
>
> The download is at www.coli.uni-saarland.de/~eric/newtrack/
>
> I found out that:
>
> - pcxtest always works with dr emm386
>
> - pcxtest fails (while some select
> Remember that there is a parameter in HIMEM to set apart a little memory
> for int15.. Did you try that?
I tried nothing because it is Eric who has a crashing program. :)
And from the error descriptions I got so far the problem is inside the
DOS-extended application, not in the EMM.
What mig
> - the program uses dos4gw but using dos32a instead does not help
> - the program crashes with fd emm386 and with jemm386...
> - the program works okay if only himem but no emm is loaded :-)
this is no proof at all that the error is in the EMM! :))
> So maybe it uses the int 15 memory copy funct
> No, the crashing program just uses a DOS extender for
> direct framebuffer access.
The DOS extender uses its own memory context (CR3, page tables), GDT and IDT.
The EMM (Jemm) is responsible vor v86-mode only.
-
This SF.
> Hi, I just double-checked my own EMM problem:
>
> With my PCIe GeForce 7600 VGA, both with the
> classic FD EMM386 and with JEMM386, I get a
> page fault when attempting to use VESA VBE
> 2.0/3.0 LFB framebuffer access to graphics.
Please explain in more detail how you come to think that this i
> There it is: "Jemm386: Exception 08 occured at: ... ERRC = 00110B40Col:1"
Yes, the ERRC=0011 confirms that it is an IRQ 0, not an exception.
However, I have no clue what the "Col:1" suffix is meant to be. If this isn't
a "typo", there is a chance that Jemm's code in memory has been -
unin
> I replaced HIMEM and EMM386 by HIMEMX and JEMM386 today (I am running FreeDOS
> 1.0). Unfortunately, it hangs my PC. The system is booting okay, but when I
> use the PC, it displays an error message "Jemm386: exception 08 occured
> at..." and various hex numbers.
> It never happens (so far) wh
Lelio wrote:
> Thanks, now was with 613K of Convetional Memory Free... and with DOS
> VPC's Guest Additions.
Good to know! The mentioned bug in Jemm which must be cirumvented currently by
setting option X=CC00-CCFF will be fixed in the next release.
-
is there, it's the "Year's End Edition":
http://www.bttr-software.de/forum/forum_entry.php?id=2808
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/
Hi,
> You should have mentioned something about the context
> instead of only throwing URLs at us ;-). The first URL
> talks about making more low RAM free by loading things
> high into UMB and by using fewer drivers. The second
> URL talks about DR DOS. One thing that might be useful
> for FreeDO
> --
> Creative SB16 Emulation Driver, Version 5.00
> Copyright(c) 1996-2001, Creative Technology Ltd., All Rights Reserved.
>
> Creative Audio @ Port d800, IRQ 7
> error: Counld not allocate code/patch RAM below 4 Mbyte boundary. Try
> loading SBEINIT.COM before SMARTDRV.E
Hello,
when I run ctmouse v2.1beta in Qemu, it says "Installed at COM1 (...) in Mouse
Systems mode" and the mouse does NOT work inside the emulator.
If I try "ctmouse /P", it displays "Error: device not found"
The old ctmouse v1.91a does not have such a problem, it detects a PS/2 mouse
and wor
> Why I am surprised: running on virtual machines I would have immagined
> that these would be useless. Not the least that I doubt, but I am
> *curious*, having a reasonable hardware knowledge. Could you please give
> a (short) explanation of what happens in this situation?
Hi Alain,
I measure
I made tests running xdma32/xcdrom32 in Qemu, VirtualBox and VirtualPC. There
are significant speed increases to achieve, but they require to set additional
parameters. For details see:
Qemu: http://www.bttr-software.de/forum/forum_entry.php?id=2463
VBox & VPC: http://www.bttr-software.de/forum/
> I was referring to "one forum already banned some
> of the people involved in this flamewar and another
> forum was closed because of this flamewar". I am
> not suggesting to follow those examples... ;-).
Eric, you are a wag. :))
btw, I was banned by the admin of the EDR forum ("Evil DoctoR") b
Jack, my fRiend, do you think it is a good idea to make a "federal case" of a
missing little "r"? Try to calm down!
Jim Hall isn't a FOOL by having ignored it, it's at best an indication that he
isn't paranoid.
The guys you mentioned to be your witnesses, Kuhnt and Lucho, they are
"slightly"
Hello,
Jemm v5.68 is now available at http://www.japheth.de/Jemm.html
changelog for 5.68:
- bugfix: JLOAD's "Lock DMA" function ignored flag to check for 64 kB
border crossing.
- NMIs occuring inside the monitor are now silently routed to v86-mode.
Previous Jemm versions displayed an
o
v5.65, therefore all versions < v5.65 didn't ensure 16 kB alignment.
Japheth
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and config
Hello,
running Phar Lab TNT binaries didn't work with Jemm versions 5.60-5.65.
This is fixed in v5.66:
http://www.bttr-software.de/forum/forum_entry.php?id=342
-
This SF.net email is sponsored by: Splunk Inc.
Still greppin
> Eric Auer wrote:
> ... [very detailed explanation] ...
Thanks for your thoughts and hints, Eric!
> It is
> interesting that the "catch" just puts an int 19 there,
> is that a real reboot or just a fastboot in this case?
I've forgotten by now. But you can test with DEBUG:
a
:0100jmp
see
http://www.bttr-software.de/forum/forum_entry.php?id=325&page=0&order=time&descasc=DESC&category=all
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search lo
>> allow you to choose out of saving a text file that you've accidentally
>> altered while reading it and you're forced to save the "oopses." The
>
> Hmmm I cannot reproduce that problem. Both edit 0.7d and edit 0.81
> ("European" and "original American" branch) let me select "No" when
> I select
> There is a bugfix release available for HimemX at
>
> http://www.japheth.de/Himem331.zip
>
sorry, the link actually is
http://www.japheth.de/Download/Himem331.zip
-
This SF.net email is sponsored by: Splunk Inc.
Still gr
Hello,
There is a bugfix release available for HimemX at
http://www.japheth.de/Himem331.zip
The first bug caused v3.30 to fail on cpus < pentium when running in
real-mode, the latter gave "unexpected results" when running on MS-DOS 6.x
(and most likely 5.x, 4.x and 3.x as well).
In case you w
>> - FDHimem opens an "interrupt window" in v86-mode only. HimemX opens
>>an "interrupt window" in both v86- and real-mode.
> that was probably the point where Jack started his own civil war ;)
At least it WAS a bug, because this issue is mentioned in the XMS docs.
>> - in FDHimem the rout
Hi,
> Hi Japheth,
>
> Japheth escreveu:
>> Btw, in the name of how many people are you speaking exactly? And what do
>> you
>> regard as "well tested". Because, as for me, I seriously doubt that a
>> program
>> is "well tested"
>
> We (many people in this list) espent months testing himem and emm386
> from Michael Devore. Are those two just a bugfix from *that* well tested
> version or is it descendent from somewhere else?
As for HimemX: there are 12 bugfixes and some optimizations, all described in
the readme.txt.
> Eric remarked that before restoring interrupt vectors the code should
> probably do a CLI which your code does not do either.
Might be. But since the restore is done inside INT 19h, IF should be 0 anyway.
> I'm suddenly worried about the IRQ vectors too, as they are redirected
> if STACKS>0. Mi
> Bart has added support for that to the CVS/SVN version of
> our kernel. I hope Japheth noticed :-). The changes are:
> On int19 ("prepare for warm boot / warm boot / run boot
> sector" or however you want to call it), FreeDOS now un-
> hooks all hooked BIOS interrupts. A
>
> BTW: from the JEMM 5.60
> what CL is needed (probably VC 4.0 or better)
> where do I get POLINK ?
I tested several C compilers with good results: MS VC 2 and 6, LadSoft CC386,
Digital Mars C++, Pelles C, and one which failed: Open Watcom WCC386.
PoLink is not required, any linker
> Maybe you could save 1, 2, or 3 KB lower memory, but probably not more. Hardly
> worth the work that would have to be put into this move.
Ok, but did I indicate that I want to optimize DOS' low memory usage at all?
> Moving a 16 Bit DOS program that uses far pointers *extensively* to a
> 32 bi
> Dos is much more than a FAT driver
Do you talk about the "date/time" functions? :)
> but a JEMMX plugin version of DOSLFN would be an idea...
why should this be better than a full VFAT driver? AFAICS DOSLFN suffers from
not being tightly integrated into the DOS FAT driver.
> For example if y
> Very good idea. And JEMMX as option - it has plugins, one might
> eventually write a "virtual SB16 to AC97 hardware" plugin for
> that plugin system.
I uploaded a beta version of Jemm v5.6 (http://www.japheth.de/Jemm.html) which
also includes samples for the "plugins". One sample is a 32bit p
> The hxrtd.zip file mentioned above also seems to have something wrong
> with it, the 'ole32.dll' file has a file size of 0 bytes!
>
Thanks for the hint! It has been fixed. However, this file isn't relevant for
mplayer AFAICS.
> I tried it too again with those files, but get lots of errors wit
> Hi!
What version of MPlayer is the most willing to go on DOS?
I downloaded
http://oss.netfarm.it/mplayer/builds/mplayer-p4-svn-22870.7z
from
http://oss.netfarm.it/mplayer-win32.php
which worked (on a P4).
> Which DLL's have I to steal from Windows?
It's opengl32.dll and glu32.dll (from wi
> Then you should try www.japheth.de JEMM386 and maybe some manual
> tuning for the options. Try for example X=e000-efff X=test and
> maybe some options which are recommended in the JEMM386 readme.
The most important setting in Jemm386 concerning MS VPC might be "NOINVLPG".
Indeed, this option wa
>
> How much?
MS VC is 6% "better" than OW, both optimizing for size. OW is not bad,
especially if comparing MSVC with TC, where MSVC is 25% "better".
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceF
>
> May you show examples? Starting from minimal "void main(){}", then with
> printf("Hello, world!\n"), then something more complex? With OW 1.6:
a "dummy" main and a "hello world" main are utterly irrelevant if you want to
compare size/speed optimisations (leaving CRT aside).
A "complex"
> Better than watcom? How much better and in which areas?
In Open Watcom just the 32bit C(++) compiler and WD are pretty good. The rest
is of "mixed" quality.
With optimisation on MSVC CL.EXE beats OW WCC.EXE significantly both in speed
and binary size (not counting the CRT part).
One re
I own MS VC 1.5 which runs in DOS with the Phar Lab TNT DOS Extender.
IMO it is the best 16-bit C(++) optimising compiler :)
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and yo
Are the binaries unmodified?
I'm asking because there is a KNOWN bug in OW 1.6 with DOS4G applications
launching other applications. The enviroment of the launched application
contains garbage, which makes it pretty impossible to use BINW\WMAKE for
example.
---
> of Linux or Windows. This means that for example you have
> to wait until your app gets a new DHCP lease every time
> when you start it, because no central networking driver
> of the operating system would be around to cache that.
IIRC watt-32 (not sure about wattcp) caches this info in file
%T
Lester wrote:
> I'm trying to replace SRDISK with SHSURDRV (v1.11, 2005-12-21) to make a
> ram drive "E". Fdconfig and Fdauto load ok but when using Arachne
> browser, after exiting (to dos shell or permanently), I get the following
> error:
>
> "error reading from drive E: DOS area: write prot
Lester Vedrox wrote:
> My connection: DSL modem + router + Realtek NIC.
>
> The packet driver RTSPKT.com loads fine but Arachne won't open any web page.
>
> _http://img138.imageshack.us/img138/9059/10112006035337it6.png_
>
> Which version of "Arachne.cfg" shown below is correct?
>
>
> Ver #1 (
> C:\FDOS\BIN>cwsdpmi --help
> HDPMI32 v3.05 (c) japheth 1993-2006
> usage: HDPMI32 [ -options ]
> -r: install as TSR permanently. Without this option HDPMI32
> remains installed until the next client terminates.
> -u: uninstall a running instance of HDPMI32
>
> *New memory managers (HIMEM and EMM386) with support of new hardware.
What does "with support of new hardware" mean? These programs require at least
a 80386 cpu (could this be regarded as "new"?) and the Himem.sys driver has
some A20 gate switching variants implemented, but besides that they a
The host stack problem is solved. Fine :)
Not a severe problem (IMO it's more like a feature), but the A20 line
switching will only work if an UMB handler has been installed. There are some
constellation where this is not true, and then the A20 gate is unhandled by
Emm386.
There is also still
Also, your patch doesn't solves issue (which you
> try to explain) in case, if extended key pressed together with Ctrl-Alt.
> Ie., even if problem exist, then you fix for it incomplete.
Yes, since it is a bug in *qemu*, not Emm386. Emm386 can do its best to work
around this bug, but not fix it
> J> (apparently gives problems with extended keys).
>
> Which ones?
As you possibly know, by reading port 60h you send the keyboard controller an
"interrupt acknowledged" signal, so it can send the next byte. On real
hardware this takes some time (some microseconds at least), but qemu is
>
> 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.
>
> But I agreed, that there not enough explanations what changed. For
> example, I see, that e
> Are you willing to do that trivial task and
> demonstrate an actual interest in helping to correct the issue, or will you
> just preach and post here?
Neither nor. The issue is of minor general interest, since most FD users will
use FD Himem and FD Emm386 with the standard parameters. For me
I have been made aware that there is no description of the error I was
refering previously here on the list. That's true, sorry, it was described in
BugZilla. But a brief overview is:
- it requires Himem + FD Emm386 to be loaded
- it occurs when FD Himem has been started with parameter /NOX2MAX3
>
> 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".
Since the error is evident in my eyes, I will not spen
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
> have re-uploaded the ISO with the updated install.exe i
After the first installation I wanted to test if FD is now able to detect if
it has enough free space (or at least is able to abort the install process in
a friendly manner).
I renamed directory FDOS to FDOSALT. About 6,5 MB free space are left on C:
- I booted from CD and select Install, FD do
this is the c:\fdos\fdauto.bat which was generated. May give a hint where the
"messages" are coming from.
@echo off
SET dosdir=C:\FDOS
SET LFN=N
set PATH=%dosdir%\bin
set NLSPATH=%dosdir%\NLS
set HELPPATH=%dosdir%\HELP
set temp=%dosdir%\temp
set tmp=%dosdir%\temp
SET BLASTER=A220 I5 D1 H5 P330
RE
> If the major problems that affected people are fixed in this
> distribution, I will release this ISO and the other ISOs (probably
> with a few more minor changes) as 1.0. Cheers to everyone for getting
> this far!
Thanks for the new version!
The good thing is: I got a running system with the f
> Since low-level changes were made to this version of EMM386, please keep an
> eye out for any problems and report them as soon as you can. While I don't
The IF bug fix may have disclosed some previously hidden bugs which are due to
a careless handling of flags. The following is an excerpt fr
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.
This is my experience so far:
First attempt
I tried to install on a pretty small partition (QEMU) where MS-DOS 5.0 was
already installed. The installation very soon stops due to insufficient
hard disk space (although nothing is told, you just see no more "progress"
on the screen). After that the
>
> Without a true SB card, I can't duplicate the problem, but I would strongly
> bet against the Windows-introduced and flavored GEMMIS being used in any
> meaningful (or at least critical) manner by DOS4G -- or any other DOS
> extender of notable popularity. Function 4a15h is much more likel
> 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.
And "do work" doesn't mean "works well". For example, the M
There is a bug left in the FD-Himem.exe memory manager.
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 the memory is not "permanently" lost, FD-Himem is able to
regenerat
Digital Mars
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
98 matches
Mail list logo
