Hi,

(Sorry for delay in replying.)

On Thu, Oct 5, 2017 at 6:49 AM, Richard Fine via Freedos-devel
<[email protected]> wrote:
>
> I wanted to relay a few issues found in 'command.com' , FreeDos version 1.2.
>
> (1) After a successful build (using Turbo C 2.01),

Dumb question, but why are you using TC201? It has some bugs that were
apparently fixed in later versions, e.g. TC++101.

I would recommend instead trying with TC++ 1.01, if possible. Granted,
it's somewhat annoying to acquire freely, but it's still (seemingly)
available (with prior demo download):

* http://edn.embarcadero.com/article/21751

There's also an (unfinished?) port to OpenWatcom, which is probably a
better long-term goal than relying on TurboC. This should be the
proper location of its sources, but you may have to ask KJD (Jeremy)
about it:

* https://github.com/FDOS/freecom

That OW port may have regressions, but I would rather we focused on
"open source" (OSI)'d OW than anything else. Nevertheless, any fixes
for TC are still accepted.

Otherwise, what choice do we have? Centroid's (DJGPP, 386) shell has
several lacks that preclude it from being used full-time. But it's
dirt simple to rebuild (only one .c file!):

* 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/command/contrib/centroidcnc/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to