What is the actual number of significant characters for a batch file
label in 4DOS? I know DOS only uniquely recognizes 8 significant
characters for a label. I also did a couple of tests and determined
that 4DOS recognizes more. But I have yet to find in the help what
the limit is for 4DOS (of course, maybe I just missed it).

As an aside, is the significant label length the same in TCC? I
couldn't find it in those docs either.

Thanks

Am I missing something, or is this a bug?

set var=teststring
gosub test %%var
set var=`test string`
gosub test %%var
set var=test/string
gosub test %%var

:test [passed]
echo %%passed
return 0

Output
----------
teststring
test
test

It appears that variables/values passed to gosubs are truncated on
spaces (even if enclosed in back ticks) or forward slashes when
assigned to the gosub variables.

Hi,
I start 4DOS in my CONFIG.SYS as follows;

SHELL=C:\4DOS\4DOS.COM C:\4DOS

When I start a secondary shell, no matter what directory that I'm
in, the directory changes to C:\4DOS

I thought that changing CONFIG.SYS to the following;

SHELL=C:\4DOS\4DOS.COM

would change this behavior, but still the same results.

Is there a way that, when a secondary shell starts, it can remain in
the current directory?

When COMMAND.COM is executed as a secondary shell, it remains in the
same directory that it was started from.

Thanks,

Joe

Hi,

I used 4DOS back in the old DOS and Windows 3.x/9x days. I have since
migrated to newer Windows-NT based Windows versions and 4NT/TCMD.

I was wondering what the use case for still using 4DOS in this day might
be. I guess it is mostly running on older machines needed to support old
DOS programs? Any other reasons?

Hope someone can satify my curiosity!

Hi,
In 4NT, I have developed a plugin using Delphi 2.0, which includes
an internal variable that I created, _WOY, to the ISO8601 standard.

To use this in 4NT, I simply use %%_WOY to get the value.

I've taken the pascal code from delphi and, using TP7.0, created
WEEK.EXE, which returns the week of year to the ISO8601 standard, as
an errorlevel. To get this into something like an internal variable in
4DOS, I do the following in my 4START.BTM;

WEEK.EXE
set _woy=%%?

This works fine, and I'm happy with it. I was just wondering, is
there a way to get the errorlevel of a program into an environment
variable, using one line? For example, set _woy=get the errorlevel
from WEEK.EXE and put it here.

Thanks,

Joe

Two questions.

1) I'm not sure if this is a bug or an invalid assumptions on my
part. Shouldn't "set /m var=value" work even from within the primary
shell (i.e. shell 0). I understand the primary purpose of "set /m" is
to be able to set a master variable when in a secondary shell, but
shouldn't it still set the variable even if you're in the primary
shell?

2) When you're inside a setlocaI, is there any way to set or create
a variable that can still be around after the endlocal? This is how I
ran across issue 1. I was looking for a way to set a variable inside
a setlocal that would still be around after endlocal. I thought "set /
m" should be able to do that, but it doesn't work.

Thanks

does 4dos have an equivalent to msdos "command.com /z" that will show
the errorlevel when a program exits to command prompt?

Nike Air Jordan 1 I Force 1 Jordan Fusion AJF 1 AJF1 AJ1F www.topbrandbiz.net
Jordan 1 fusion
Nike Air Jordan 2 II Force 1 Jordan Fusion AJF 2 AJF2 AJ2F www.topbrandbiz.net
Jordan 2 fusion
Nike Air Jordan 3 III Force 1 Jordan Fusion AJF 3 AJF3 AJ3F www.topbrandbiz.net
Jordan 3 fusion
Nike Air Jordan 4 IV Force 1 Jordan Fusion AJF 4 AJF4 AJ4F www.topbrandbiz.net
Jordan 4 fusion
Nike Air Jordan 5 V Force 1 Jordan Fusion AJF 5 AJF5 AJ5F www.topbrandbiz.net
Jordan 5 fusion
Nike Air Jordan 6 VI Force 1 Jordan Fusion AJF 6 AJF6 AJ6F Jordan 6
Rings www.topbrandbiz.net Jordan 6

fusion
Nike Air Jordan 7 VII Force 1 Jordan Fusion AJF 7 AJF7 AJ7F www.topbrandbiz.net
Jordan 7 fusion
Nike Air Jordan 8 VIII Force 1 Jordan Fusion AJF 8 AJF8 AJ8F www.topbrandbiz.net
Jordan 8 fusion
Nike...

http://husband.googlebong.com

Oris Accardo GoogleBong

img { border: 2px solid Black }

pre { font: 6pt/8pt }

p,blockquote { font: 16pt; font-family: verdana, arial, 'sans serif' }

h1,h2,h3,h4,ul { font-family: verdana, arial, 'sans serif'; font: 14p }

table,li,td { font-family: verdana, arial, 'sans serif'; font: 12p }

ul { list-style: disc }

ol { list-style: decimal }

body { background: "#EEEEEE" }

h1,h2,h3,h4,hr,p,ul,blockquote,pre { color:Black }

a:link { color:Blue }

a:visited { color:Blue }

a:active { color:"#008000" }

a:hover { color:"#008000" }

h1.header { padding:0em; margin:0 }

div.container { width:100%%; margin:0px; border:1px solid Black; line-height:150%% }

div.header,div.footer { padding:0.5em; color:white; background-color:Black; clear:left }

div.left { width:15%%; margin:0; float:left; padding:0; }

Hi,
When I upgraded from 4NT 6.0 to 4NT 8.0, one of the neat features I
immediately liked was the ability to create "plugins".

I have developed a few plugin routines, using Delphi 2.0, for use
with 4NT 8.0

I was scanning the 4DOS directory, and came upon the 4DOSTECH.TXT
document. In that document, it discusses the use of "installable
commands". I remember reading this document last century (!), but had
forgotten all about it.

4NT 8.0 provided a template plugin, called DELPHIDEMO.DPR, that
demonstrated how to create a plugin for 4NT 8.0. Working from this
template allowed me to create my own plugin.

Would anyone have an example program to create an "installable
command" for 4DOS? I've done TSRs in Turbo Pascal and PowerBASIC, but
an "installable command" example in assembler or C would be okay. If
not, I will work with the info in 4DOSTECH.TXT, and build from there.