Hi!
2-Ноя-2005 23:22 [EMAIL PROTECTED] (Blair Campbell) wrote to
freedos-devel@lists.sourceforge.net:
BC present...), and 2) FreeCOM is already VERY Turbo C specific;
BC portability is definately not an issue.
Portability _is_ issue. At least, to OpenWatcom (which is MSVC, not BC
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
MOVE 3.3 packages were uploaded to ibiblio:
www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/move/MOVE33X.zip
(binaries)
and
www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/move/MOVE33S.zip
(sources)
New in this version:
- Cats (kitten) support
- OpenWatcom suport (Thanks to Blair
Aitor Santamaría Merino escreveu:
Given the interest back of the FreeDOS 1.0 issue,
I really don't understand why so much effort is put in new and 1.0 stuff
and when I report a BUG in the KERNEL so serious that I had to remove
FreeDOS from a real user machine I didn't even get ONE answer
On Thu, 03 Nov 2005 15:30:53 -0200, you wrote:
Hi Alain,
I don't like this. Even if it is better, it should be only with an
optional parameter (or environment variable). Main goal is to make it
just like DOS
To make things clear, my original idea is add a switch and display
like PC-TOOLS v9's
Hello Alain,
I really don't understand why so much effort is put in new and 1.0 stuff
and when I report a BUG in the KERNEL so serious that I had to remove
FreeDOS from a real user machine I didn't even get ONE answer from the list
what do you expect ?
'some program of mine doesn't
Blair Campbell escreveu:
BC present...), and 2) FreeCOM is already VERY Turbo C specific;
BC portability is definately not an issue.
Portability _is_ issue. At least, to OpenWatcom (which is MSVC, not BC
compatible).
Portability is definately not an issue to non-DOS compilers.
As I
Johnson Lam escreveu:
I don't like this. Even if it is better, it should be only with an
optional parameter (or environment variable). Main goal is to make it
just like DOS
To make things clear, my original idea is add a switch and display
like PC-TOOLS v9's MI
I agree.
Yes, I agree
Blair Campbell escreveu:
[...] It will make FreeCOM a smaller binary (desperately needed;
Why do you need so much space? Can you tell me what target application?
2) FreeCOM is already VERY Turbo C specific; portability is definately not an
issue.
I understood from previous discussions
Why do you need so much space? Can you tell me what target application?
FreeCOM can't currently be compiled with all of its features due to
size; the limit of the small memory model is 64kb and FreeCOM is
exceeds this limit with all features compiled in.
Hi Tom,
what do you expect ?
'some program of mine doesn't work; it was to do X'
unless to give precise instructions how to reproduce the bug, and the program
as well, noone will even have a chance to work on this - even IF they
would be interested
I am sorry to disapoint you, but I
Blair Campbell escreveu:
Why do you need so much space? Can you tell me what target application?
FreeCOM can't currently be compiled with all of its features due to
size; the limit of the small memory model is 64kb and FreeCOM is
exceeds this limit with all features compiled in.
Ok,
ok Jeremy, I believe that you arfe entitled a lot more than two cents on
this topic ;-)
I also believe that FreeDOS is ready to 1.0. I installed it in a real
user application which is heavy database + graphics in 32 bits and it
behaved *better* than MS-DOS 7.10!!!
The only problem is that
Hi Alain,
Alain said to me:
PS as to Translation, if some day it kets Kittenized, surely I will
help :)
It is already kittenized in version 1.7 beta (maybe even before that,
I don't know). Currently I'm in the process of kittenizing all the
new code I added and I'm almost done. Once I'm
14 matches
Mail list logo
