> On Oct 6, 2015, at 5:41 PM, Rugxulo wrote:
>
> Hi,
>
>> On Mon, Oct 5, 2015 at 4:44 PM, Jerome E. Shidel Jr.
>> wrote:
>>
>>> On Oct 4, 2015, at 10:02 PM, Antony Gordon wrote:
>>>
>>> It was nice of whomever wrote FreeCOM to include that Windows NT command
>>> interpreter function.
>
> On Oct 6, 2015, at 8:55 AM, Eric Auer wrote:
>
>
> Hi Jerome, for clarification: I was referring to
> the specific case where your tools are used as a
> part of the install process of FreeDOS :-)
I know, I was just using an easy to state example. :)
>
> In your given "pick a file and unzip
> On Oct 6, 2015, at 12:12 PM, Antony Gordon wrote:
>
> Hi,
>
> Sometimes doing the "needful" exceeds the "requested". Jim has a vision of
> what he wants, basically a batch file based simplified install. You (Jerome)
> have created some very useful utilities for managing the screen and such.
On Tue, 6 Oct 2015, sparky4 wrote:
> ah ok!!
>
> i am now stuck at the converting the net code from wattcp to mtcp
Why not leave it WatTCP? WatTCP supports 16-bit too.
-uso.
--
__
Hi,
On Tue, Oct 6, 2015 at 12:14 PM, Mateusz Viste wrote:
> On 06/10/2015 17:49, sparky4 wrote:
>>
>> Yeah thats what i am doing and apparently there is no ungz function in watcom
>> C
>
> Of course there isn't, since that's a function I wrote myself. It's a
> core part of fdnpkg. see libgz.c
Hi,
On Mon, Oct 5, 2015 at 4:44 PM, Jerome E. Shidel Jr. wrote:
>
>> On Oct 4, 2015, at 10:02 PM, Antony Gordon wrote:
>>
>> It was nice of whomever wrote FreeCOM to include that Windows NT command
>> interpreter function.
Presumably Stefan Kaiser (who sadly long ago disappeared).
>> I never
Hi,
On Mon, Oct 5, 2015 at 2:08 AM, Joe Forster/STA wrote:
>
> Also, while executing config.sys (_not_ autoexec.bat yet), the (master)
> environment variable block is not pointed to anywhere. I've unable to finish
> another DOS program that would record the boot drive into an environment
> variab
ah ok!!
i am now stuck at the converting the net code from wattcp to mtcp
On 10/06/2015 11:38 AM, Mateusz Viste-4 [via FreeDOS] wrote:
> On 06/10/2015 17:49, sparky4 wrote:
> > Yeah thats what i am doing and apparently there is no ungz function
> in watcom
> > C
>
> Of course there isn't, si
On 06/10/2015 17:49, sparky4 wrote:
> Yeah thats what i am doing and apparently there is no ungz function in watcom
> C
Of course there isn't, since that's a function I wrote myself. It's a
core part of fdnpkg. see libgz.c.
Mateusz
--
Yeah thats what i am doing and apparently there is no ungz function in watcom
C
i just want it to compile 1st then i will debug the crap out of it
--
View this message in context:
http://freedos.10956.n7.nabble.com/FDNPKG16-port-tp23398p23557.html
Sent from the FreeDOS - Dev mailing list
Hi,
Sometimes doing the "needful" exceeds the "requested". Jim has a vision of
what he wants, basically a batch file based simplified install. You
(Jerome) have created some very useful utilities for managing the screen
and such.
My thought was basically to incorporate your V8 tools as a part of
Hi Jerome, for clarification: I was referring to
the specific case where your tools are used as a
part of the install process of FreeDOS :-)
In your given "pick a file and unzip" example, it
would be possible to do alternative tricks like:
VASK-PRO /F *.zip "Pick a file to unzip" "unzip $F"
The
> On Oct 5, 2015, at 8:14 PM, Eric Auer wrote:
>
>
> Hi Jerome,
>
> combining 20 tools of 1-2 kilobytes each into one tool of 10 kB
> sounds like a good plan and using "residency" sounds even better:
>
Yes and maybe there will be an edition that does that at some point.
But, for now that is
Hi guys,
Having resident data will reduce issues with needing SET /P which
has limitations (e.g. using pipes, which in most DOS command.com
variants need temp files on a writeable drive) and is not in the
classic MS DOS version of command.com (in case somebody tries to
use your batch files to up
14 matches
Mail list logo
