Path: utzoo!attcan!uunet!mcvax!hp4nl!philapd!ssp2!mbrands
From: mbrands@idca.tds.PHILIPS.nl (Manfred Brands)
Newsgroups: comp.sys.ibm.pc
Subject: MKS Toolkit Question
Keywords: Turbo Pascal 4.0 under the MKS shell
Message-ID: <167@ssp2.idca.tds.philips.nl>
Date: 7 Nov 88 14:22:35 GMT
Organization: Philips Telecommunication and Data Systems, The Netherlands
Lines: 38

The MKS shell acts strange in combination with Turbo Pascal 4.0

When I try to compile a program TPC is not able to find its configuration
file. Normally the compiler searches for it in de same directory as the
executable is in, using argv[0] on DOS 3.0 and up. 
The problem is, I suppose, that TPC only recognizes the backslash as a
path separator and the MKS shell ALWAYS uses forward slashes. Even if I
don't use the switch program to set the switch character.

Ok, this problem can be solved by making an alias for TPC in which the
options from the configuration file are given as command line options.

Is it possible to tell the MKS shell to use backslashes instead, so that there
is no compatibility problem with existing DOS programs ?

But now the REAL PROBLEM !!

The program generated by TPC is NOT executable under the MKS shell.

When I type:
	program

I get the message:
	program: Not executable

BUT when I type:
	command /c program		(or command -c program)

the program runs normally.

Does the MKS shell perform some checks on de .exe header to see whether a
file is executable, and does TPLINK not fill in the correct values ?

Please email me if you know what either TPC or SH do wrong.


Manfred Brands
mbrands@idca.tds.PHILIPS.nl