On Fri, 23 Apr 2004 16:39:45 +0200 (MEST), you wrote:
Hi Eric,
Sigh... have to followup myself...
Sorry I'm slow, I hurt HongKong's speedy reputation :-(
[ http://www.coli.uni-sb.de/~eric/stuff/soft/ mode-23apr2004.zip ]
The cannot read config in MODE COMn BAUDHARD=1 mode bug was caused
by
Hi Michael,
Ok, thanks. Then is noone is against, I'll move those to post-1.0.
I chose to set those there, as in the examples they seemed to be popular
options.
Particularly, what I missed mostly is VCPI, so thanks for that.
By the way, I have remembered that I should list VDMA there too, pre-
Hi,
I forgot the link. There's a direct link from freedos.org on top
(directly from http://www.freedos.org/news/version1/), although files
are being posted to
TODOS: http://fdos.org/ripcord/fdos_1_0/official/todos.htm
POST-1.0: http://fdos.org/ripcord/fdos_1_0/official/post.htm
Aitor
Hi all... great, I like TODO list changes :-).
http://fdos.org/ripcord/fdos_1_0/official/todos.htm
EMM386 RAM= is well enough implemented if you make it an alias to X= if
you ask me. ROM= on the other hand would be not too hard to do (Michael
already shadows ROM to trap :0 reboots). But
Hi!
24--2004 23:05 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:
EA EMM386 RAM= is well enough implemented if you make it an alias to X= if
EA you ask me.
Wrong.
__O\_/_\_/O__
X=-
Prevents EMM386 from using a
Hi,
(Arkady, I know that you also posted to this thread, but the shit of
programs that I used to remove spam trashed your message, could you
please re-send to me that in private? I like keeping those messages as
mails than acceeding them from web; anyone kind out there can also
resend,
At 01:52 AM 4/25/2004 +0400, Arkady V.Belousovwrote:
Hi!
24-áÐÒ-2004 23:05 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:
EA EMM386 RAM= is well enough implemented if you make it an alias to X= if
EA you ask me.
Wrong.
X= will limit the range checked, same as RAM does, but
