Hello Denis!

Tue Dec 17 1996 12:35, Denis Tonn wrote to Dmitry M Golubovsky:

 DG>> I have found that under TSHELL, DOS executables cannot be run by
 DG>> "start" command (that appears to call
DosStartSession) but under
 DG>> PM environment, they can be run. Where is the difference and how
 DG>> can I run realmode EXE under TSHELL?

 DT>  From the README that comes with TShell..

Certainly, I have read this before...

 DT>  STARTD.ZIP should be available from the same place you obtained
 DT> TSHELL. I have not checked into "why" CMD.EXE does not
properly start
 DT> a Dos session, but since the STARTD package allows much more (Dos
 DT> sessions settings to use) than CMD does, it is the prefered method
 DT> anyway.

 DT>  I suspect that CMD is trying to call the "shell" to determine the
 DT> app type and start the session, but the "shell" (PMSHELL) is not up
 DT> when running Tshell only.

I've FOUND THIS!!!! When I slightly modified the startd source (let the
author forgive me ;) to print out the return code from DosStartSession I
saw that rc was 461 i. e. invalid SMG data length. Then, in the OS/2
control program documentation, I found that in absence of the PM first
field of STARTDATA structure may not be greater than 32. I added a /t
option to the startd to explicitly set this field to 32. And it works
now!!!!!!!!!

I don't understand IBM's logic in this case. Fields with offset >32
contain some parameters usable in the PM only and might be ignored when the
PM is not running. But OS/2 retruns error code.


                                     [TEAM OS/2 Member DG008]

Dmitry

--- GoldED/2 2.50.Beta5+