I don't get what the issue with PCNTPK.COM packet driver is?
Per the amdpd.zip file at http://crynwr.com/drivers/00index.html , it is
copyright Russell Nelson 1990 w/a GPLv1 license in 1990 and copyright AMD
1993 w/a pseudo Public Domain-ish license (PCNTPK.ASM). While not packaged
the way we
Does this mean it will be pulled from the distribution? Or does it
mean we'll actually try and address this issue head-on, because now it
affects two packages?
I think FDNET is pretty mission-critical, given it's in the default
FDAUTO.BAT. The problem with that, if what I read on the wiki is
On 6/3/2021 9:11 AM, Paul Dufresne via Freedos-user wrote:
I decided to make a small research, and found these libraries
suggested to someone:
Turbovision: "TVision was developed by Borland (now Imprise) in 1992
(v1.03) as a tool for your TurboC and TurboPascal compilers."
"Turbo Vision
Hi Paul,
as you mention Nano-X and Turbo Vision, Georg Potthast has
ported some apps to DOS using Nano-X and FLTK, with screenshots:
> https://sourceforge.net/projects/fltk-dos/
> https://sourceforge.net/p/fltk-dos/wiki/NanoX_Introduction/
>
I decided to make a small research, and found these libraries suggested to
someone:
Turbovision: "TVision was developed by Borland (now Imprise) in 1992 (v1.03) as
a tool
for your TurboC and TurboPascal compilers."
"Turbo Vision (TVision for short) is a TUI (Text User Interface) that
> Hi Jeremy, while you are at it:
>
> Wondering how Jerome could test whether the current shell
> is FreeCOM without needing temp files, ... FWIW, at one time I was trying to
> figure out a way to automatically determine whether my executable program was
> being called from the commend line (any
FWIW, in my programs (written in ASM) what I do while parsing the command line
is look at the length stored at PSP:80h. If it is less than 126, I use the
data stored at PSP:81h up to the first 0Dh (Carriage Return) character. If the
length is 126 or more, I look for the CMDLINE environment
Hi Jeremy, while you are at it:
Wondering how Jerome could test whether the current shell
is FreeCOM without needing temp files, I found out that
half of the SET options are not yet listed in SET /? help.
The currently available actual options of SET would be:
SET test=one results in TEST=one
Hi Eric,
[reply on-list as asked]
> On Jun 3, 2021, at 7:38 AM, Eric Auer wrote:
>
> Why cannot FDIMPLES free the allocated memory before calling FDINST?
It is not that it can not do it. It is only that it’s original design (as a
list editor) meant
that all remaining memory was available for
> Yes, I had hoped to get a release out already but ran
> into build issues getting all compilers to build which
> was just fixed*. I will look into the cmdline issue,
> already filled a bug for it. Then post the release.
Hi Jeremy. Thanks for filing the bug report. Could you
please hold off
Yes, I had hoped to get a release out already but ran into build issues
getting all compilers to build which was just fixed*. I will look into the
cmdline issue, already filled a bug for it. Then post the release.
* More improvements are needed, but that's a different issue.
Jeremy
IMO it's a bug in FD command.com. If a command
line exceeds 126 bytes, the value at [PSP:80h]
"should" be 0x7Fh ( and a 0x0D "should" be placed
at [PSP:FFh] ) - that's at least what COMMAND.COM
of Win95/98 does. The environment variable
CMDLINE will then contain the full command line.
It's
Hi Paul,
> When I run a long command, e.g.
>
> pdptest ... (to exceed 126
> characters), and it is a Win32 executable so HX
> gets involved, I get a crash.
You write that Japheth writes:
> IMO it's a bug in FD command.com. If a command
> line exceeds 126 bytes, the value at
Hi Eric,
> On Jun 2, 2021, at 7:47 AM, Eric Auer wrote:
>
>
> Hi Jerome,
>
> if FDIMPLES is specifically used in advanced mode, where
> more data has to be processed, I would suggest to consider
> automatically enabling support for XMS when XMS is found.
Not really needed. When run by the
Hello.
When I run a long command, e.g.
pdptest ... (to exceed 126
characters), and it is a Win32 executable so HX
gets involved, I get a crash.
Japheth has debugged it and reported his
findings.
Could someone please confirm that his analysis
below is correct and it is a
15 matches
Mail list logo
