Very Computer

Hi,
I'm trying to migrate a COMPLEX UNIX-application to Windows2003,
basically using our shell scripts from unix, converted (mostly
regarding the names of called scripts. e.g. rather *.ksh than *.bat)
and my experience from the migration we did 5 years ago to winNT (with
mks for kornshell and hamilton-csh).

The newer version now on w2k3 is MKS Toolkit for Developers 8.7.0200
seems to have problems with things like

TMPSYS=`uname -s | cut -c 1`

that is: calling some commands, often using pipes to process the
outputs and then putting the result into a variable to be used for
further decisions, sometimes fails resulting in an empty string!.

I managed to get "nondeterministic" results from such scripts, that is
running a testscript which does 1000 times (sequentially) the same
thing some times fails, which I controlled via the
stderr-debug-listing produced by ksh -vx.

any ideas?
It might be some problem of the server itself I have to admit, some
configuration regarding memory/processes/..., I'm not the
win-administrator-type.

I just want to exclude any known bugs or undocumented variables to be
set (of the TK_DO_NOT_whatsoever=1 type ...)

thanks a lot!

Quote:> Hi,
> I'm trying to migrate a COMPLEX UNIX-application to Windows2003,
[..]
> The newer version now on w2k3 is MKS Toolkit for Developers 8.7.0200
> seems to have problems with things like
> TMPSYS=`uname -s | cut -c 1`

Fill in a bug report to the authors?

[..]

Quote:> any ideas?

Migrate the app to Linux, could be a matter of typing make.;)

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: 0xEDD27B94)

#bofh excuse 157: Incorrect time synchronization

A bit less radical would be to switch to cygwin, since the OP is asking
for a solution to a windows port.

Janis

Janis got it right: the customer refuses to change to UNIX-whatsoever,
all the others run on AIX, Linux or Unixware (to be moved to Linux
sooner or later), so I have no chance (as the customer is to big to be
sent to hell :-)
The salesperson agreeing in WinNT 5 years ago is no longer part of our
company so no chance for revenge either :-(

So it has to be using Unix-scripts ksh+csh the way they are or changed
automatically (as we do with awk now for mks and hamilton-csh on
WinNT) to be used on w2k3.

Thanks,
bine

[..]

Quote:> So it has to be using Unix-scripts ksh+csh the way they are or changed
> automatically (as we do with awk now for mks and hamilton-csh on
> WinNT) to be used on w2k3.

So fill in a bug report to the authors, as I already suggested in
my first reply to your OP.

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: 0xEDD27B94)

#bofh excuse 271: The kernel license has expired