Hi Bernd, Diego and Johnson,

From: Bernd Blaauw <[EMAIL PROTECTED]>
[...]
Diego Rodriguez schreef:
Will it work with 80286 processors ?? Why doesn't work with 8086 ones
??

MEM still has some 386-specific machine instructions which are not
present in earlier processor generations
(386 is 32bit CPU, older is 16bit CPU). Or the queries for XMS are not
protected by 'if not 286 or later, return [not_available]'.

Actually I found that Eric sent me some detailed instructions about what he thinks needs to be fixed so I will try and address all those additional places we need to do 386 checks and probably release a special MEM.EXE which has some debugging stuff built in so you can specify MEM /DBGXMS and it will output a trace of the checks and other stuff the XMS code is doing so we can tell where it hangs (if it still does).

AFAIK, there isn't a CVS, you simply make a MEM19X.ZIP archive with
binaries and a MEM19S.ZIP archive with sources, upload them to ibiblio
and announce it at freedos.org

http://cvs.sourceforge.net/viewcvs.py/freedos/?only_with_tag=MAIN#dirlist

I'd also recommend to upload as a package. Blair and Jim have access to
Ibiblio. Jeremy has access to Sourceforge (empty project so far),
and I've access to Jeremy's fdos.org server. Plenty of locations possible.

SourceForge isn't empty - http://freedos.sourceforge.net/mem/ has some files.

From: Johnson Lam <[EMAIL PROTECTED]>
[...]
I'm currently working on a few minor issues. As for the bigger issues=20 of MEM not working on 8086 machines without /N[OSUMMARY] being used,=20 adding PCTools-like output, and possibly other things I've forgotten,=20 I'd rather leave these for later than possibly delay the next release=20
of MEM for too long.  I hope nobody objects to that.

Can you release as "beta" and notice on the program help (mem /?). Or
temporary force "/N" until manual override? So most of the users can
run it

Yes, Bernd made the same suggestion to me about forcing /N on pre-386 machines so if I can't fix the code I will at least do that.

I would like to call the release "1.9" instead of "1.8" due to the=20 fact that 'MEM /?' with the "1.8 alpha 1" version actually shows "1.8"=20 and it would be nice to avoid confusion. I will make sure that the=20
next alpha release shows "1.8a2" or "1.9a1" or something to avoid=20
wasting more version numbers :)  Any objections?

I agree.
Since you add PC-TOOLS like output screen, this is quiet a changes.

Actually I'm afraid I haven't added that yet, sorry! It is on the wiki though as a future enhancement - see http://wiki.fdos.org/Main/Mem Perhaps you could help me by sending me a text file including "MI /?" and then all the different combinations of options it supports. If you could attach it as a text file instead of pasting it in the email it might be better because in the email you sent the formatting got messed up a bit [possibly on my end :) ].

Thanks in advance,
David

-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to