PC> However, I have another problem with _beginthread().  In my PM terminal
 PC> program, if I don't call DosSleep(400) after calling _beginthread(), the

I think you are assuming that the new thread is up and running before the
_beginthread() function returns to the calling thread -- this is usually
NOT the case,  and you shouldn't start using something that is 
created/opened/alloced in the new thread without using an event semaphore.

For example:

mainthread:  _beginthread(thread2)
             DosWaitEventSem(hevIMAlive, -1);
             // it is now safe to use the things created by thread 2

thread2:     initialize data
             allocate data
             open data
             DosPostEventSem(hevIMAlive);


 PC> case IDM_SCRIPT_RUN:
 PC>     if(tidScr != 0) {
 PC>       Msg(0, ProgName, "Script already running\nAbort 
 PC> current script first");
 PC>       break;
 PC>     }
 PC>     rc = SelectRexxScript(pdata, fname); // FileDlg to select *.cmd file
 PC>     if(rc == TRUE) {
 PC>       tidScr = _beginthread(RunRexxScript, 16384, (PVOID)fname);
 PC>       if(tidScr == 0xffff) {
 PC>         Msg(0, ProgName, "%s %d\nError starting script thread",
 PC>         __FILE__, __LINE__);
 PC>         tidScr = 0;
 PC>       }
 PC>       else
 PC>         DosSleep(400);  // without this the thread won't start
 PC>     }
 PC>     break;

In general,  it is usually a better design to have the thread running
before you need it (ie: you start up your oft used secondary threads before
creating any windows,  and they never end).  You send them messages (not
nec PM messages) when you want them to do something.


--- Maximus/2 3.00