Bernd Blaauw wrote:
Guess I should read up about what the difference is between these
large/normal/small models.
In short:
tiny: one segment for everything, CS = DS = SS, data pointers are near,
function pointers are near (everything must fit in in 64 KB, no segment
reserved for stack an
From: tom ehlert <[EMAIL PROTECTED]>
[...]
if you want more features, make it compliable with watcom
I think I would find this an interesting project but I should wait
until MEM is done :)
From: Bernd Blaauw <[EMAIL PROTECTED]>
[...]
I think Jeremy's descript.ion support has to be inserte
Hi,
Now that I can Compile FreeCOM, I just fixed 2 bugs:
1)--
file critrchk.c is missing
#include
which is from SUPPL and causes two calls do functions with no prototype:
_fmemset and _fmemcpy
2)--
file set.c is missing
#include
also from SUPPL and causes a call with no pr
regarding the descript.ion thing not working, are you sure it was
compiled in or was that why you were building? (not sure why you were
trying to build in large model though, see Tom's remarks, basically not
going to work, even if you manage to get an executable)
...
I think Jeremy's descript
tom ehlert schreef:
as a GPL site note:
GPL 4 should probably contain some statement, that you mustn't only
give sources, but also a WORKING description HOW to compile these
sources into a binary ;)
side note for GPL5: free compilers? :)
I think Jeremy's descript.ion support has to be
Hello David,
>> FreeCom only compiles in small model (see below).
> I'm pretty sure I got everything to compile in large model
even if you can compile it in large model, XMS-SWAP will DEFINITIVELY
not work, no matter how much work you put into it.
it's in the concept, not the actual implementati
Howdy,
Date: Wed, 09 Nov 2005 20:17:30 -0500
From: "Kenneth J. Davis" <[EMAIL PROTECTED]>
To: [email protected]
Subject: Re: [Freedos-devel] Compiling FreeCOM...
Reply-To: [email protected]
Alain wrote:
...
it works in small model, but i
Thanks, now I can compile FreeCOM
Tomorow I will try to figure how to localize it ;-)
Alain
---
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
Alain wrote:
...
it works in small model, but in large it seems that locks compiling
FreeCom only compiles in small model (see below). I think at one time
at least the suppl library could use small or large, but I don't know if
that is still true or not.
...
wait while it compiles
I
Hi Jeremy,
the easy part is a theory, just that. I am working on it for 9 hours now
and it just does not work. Error is bellow
maybe I was not clear, a mini suppl library is now included
I figured that out. Not the easy way.
so you do
not have to do anything regarding it. Do not create
maybe I was not clear, a mini suppl library is now included so you do
not have to do anything regarding it. Do not create the skip file, do
not try to download it, just ignore any mention of it existing.
(The docs still explain it because you can still use the full suppl
library and everything
Bernd Blaauw escreveu:
What sould I do? If I use SUPPL, would I get a bigger FreeCOM?
I will stop trying until I understand what to do...
Suppl is required somehow, but you have the choice of compiling it each
time again, or use a precompiled version (which the file SKIP is for).
That is ex
Alain schreef:
What sould I do? If I use SUPPL, would I get a bigger FreeCOM?
I will stop trying until I understand what to do...
Suppl is required somehow, but you have the choice of compiling it each
time again, or use a precompiled version (which the file SKIP is for).
Good luck trying to
More problems:
I managed to start compiling but one of the first files
utils\mkinfres.c
has this command:
#include
I could find this file in SUPPL, but it I am usinf a SUPPL\SKIP file, I
don't have SUPPL...
What sould I do? If I use SUPPL, would I get a bigger FreeCOM?
I will stop trying
Hy Jeremy,
I am just starting to prepare for compiling FreeCOM. should I stick to
docs\compile.txt or is there any other explanation?
>
It should be fine.
It is in fact very outdated :(
If you build on Windows be sure to use the win
version of nasm,
> I am using DOSEMU with FreeDOS, so
Johnson Lam schreef:
Hi Jeremy,
Thanks for improving kernel, last time I use an old kernel (Jul) so
have COPY CON blah.txt (CTRL-Z) problem, but this seems OK in (Oct)
build.
That wasn't Jeremy, see the commit details from 2005-10-22
http://sourceforge.net/mailarchive/forum.php?forum=freedos
Hi Jeremy,
Thanks for improving kernel, last time I use an old kernel (Jul) so
have COPY CON blah.txt (CTRL-Z) problem, but this seems OK in (Oct)
build.
Can you announce here when some major update was made? Sorry for
additional workload ...
Thanks.
Rgds,
Johnson.
--
Alain wrote:
Hi,
I am just starting to prepare for compiling FreeCOM. should I stick to
docs\compile.txt or is there any other explanation?
Alain
It should be fine. If you build on Windows be sure to use the win
version of nasm, and every so often the build may fail in the middle (I
thi
18 matches
Mail list logo
