> The question whether Masm or Nasm has a larger "community" or is more
> "widely
> used" is indeed somewhat interesting, but it's interesting because it's a
> common propaganda item which nicely shows that people tend to believe
> what
> they want to believe.
It's also interesting because JWA
> fdpkg requires c:\FDOS?
No, just a %DOSDIR% variable pointing to it.
Simply use SET DOSDIR=... to set it.
> perhaps fdpkg could be modified to use a database
> to store where the packages are came from etc.
The LSM files and FDUPDATE work well enough imho ;-)
It also has a structure of one di
Hi Japheth,
> ... And I think that the "more free"-advantage of Nasm, which you and
> Eric did point out is nonsense. That's virtually all my post was about.
As JWASM is "in the same boat" as OpenWatcom, I think it would make
sense to try to convince eg Debian / Fedora people that those are
fre
> So, do you want to accuse me of the "not-so-positive intention" to say
> that JWASM has indeed disadvantages?
No, this was "generally" spoken. I don't know your intentions.
> Of course _I_ think that NASM is better.
Yes, I know. And I think that the "more free"-advantage of Nasm, which you
> fdpkg requires c:\FDOS?
> how do you maintain a working existing environment
> along side the beta one even following the existing
> structure and using c:\FDOSBETA or something acceptable.
No, it doesn't require this directory name. The directory name is read
from the DOSDIR environment vari
On Sat, 28 Mar 2009, usul wrote:
> perhaps fdpkg could be modified to use a database to store where the
> packages are came from etc.
>
> Is there a open source database that can be used in an dos
> application, if none exist a flat file could be used as well.
I randomly wonder if it's possible
It's okay if you know vaguely about the internals of something, but when
you write an imitation of it, chuck all that code aside and try to write
yours along different lines. For example, if the original was written to
conserve memory usage, go for speed instead, or go for generality. The
code
Hi!
btw, i guess Mateusz still need some help with FD 1.1 package
you and/or other guys may help him to check packages and release FD 1.1
http://www.viste-family.net/mateusz/fdupdate/wip/
See Ya!
Geraldo
Sapere Aude
Non ducor, duco
São Paulo, Brasil, -3gmt
site: http://exdev.sf.net/
msn: geral
fdpkg requires c:\FDOS?
how do you maintain a working existing environment
along side the beta one even following the existing
structure and using c:\FDOSBETA or something acceptable.
perhaps fdpkg could be modified to use a database to store where the
packages are came from etc.
Is there a open
I am not ready to write driver code, yet.
My main an interest is in designing writing a gui/desktop,
and in writing libraries that can be shared and used by command line
application as well as gui.
But I also have an interest device and similar programming.
I think FreeDos relies alot on closed s
Japheth,
Politics of any sort are this way. It is always extremes that shout
the loudest. In my opinion is aways in the middle the answer always is
in the middle, the middle rarely if ever has an advocate. :P
I like open source and free software. More the spirit of the law
though then the law its
Christian Masloch schrieb:
>>> If you want to learn about (16-bit) DOS kernel stuff, first get the RBIL
>>> (Ralf Brown's Interrupt List) and the source of DOS-C (mostly C) and
>>> Udo's
>>> Enhanced DR-DOS kernel (Assembly). (You might as well get the old RxDOS
>>> 7.1.5 Assembly sources but oh
>> If you want to learn about (16-bit) DOS kernel stuff, first get the RBIL
>> (Ralf Brown's Interrupt List) and the source of DOS-C (mostly C) and
>> Udo's
>> Enhanced DR-DOS kernel (Assembly). (You might as well get the old RxDOS
>> 7.1.5 Assembly sources but oh well.)
>
> ...and the sources fo
>> As Eric put it, NASM is considered more free than JWASM.
>
> as you probably can see there are also rather "questionable" sentences
> to find
> in this mailing-list. "Freedom", "Democracy", "Justice", "Fairness", ...
> are
> commonly regarded as positive terms and because of this they are al
On Sat, 28 Mar 2009, Christian Masloch wrote:
>> A (or more then one) virtualizer is a good source for initial developing
>> and testing, often an emulator is even more picky about how you
>> implement. DOSBox is good for DOS games but many utilities refuse to
>> work.
>
> You can boot a real DO
> A (or more then one) virtualizer is a good source for initial developing
> and testing, often an emulator is even more picky about how you
> implement. DOSBox is good for DOS games but many utilities refuse to
> work.
You can boot a real DOS (f.e. FreeDOS) disk image inside DOSBox which
make
usul schrieb:
>> You could put toghether FreeDOS 1.1...
>> most programs have new versions that are ok, but what is mostly needed
>> is put all of it toghether, test new versions, fix a few things and
>
> This sounds like a good task for me to start. And I am most certainly willing.
> Would this b
Hi !
If you are more interrested in low level stuff you can work with Eric Auer on
the FreeDOS kernel. There is few bugs to fix and few feature to add - mainly
implement the COUNTRY.SYS (functions about national support). You don't have to
write it from scratch as it is already present in unstab
Hi Adam,
> As Eric put it, NASM is considered more free than JWASM.
as you probably can see there are also rather "questionable" sentences to find
in this mailing-list. "Freedom", "Democracy", "Justice", "Fairness", ... are
commonly regarded as positive terms and because of this they are also f
19 matches
Mail list logo
