gpz@bridge2.ESD.3Com.COM (G. Paul Ziemba) (02/17/90)
One of the arguments to DosMuxSemWait() is a pointer to a MUXSEMLIST structure. According to the definition of this structure (pp 354-355 of the Microsoft OS/2 Programmer's Reference, Vol. 3), the semaphore handles must have been created using the DosCreateSem or DosOpenSem functions. This seems to indicate that DosMuxSemWait() deals only with system semaphores and not with RAM semaphores. Is this true? ~!paul -- Paul Ziemba zapi!gpz gpz@3com.com (415)940-7671 Current nemesis: CA "winters", cold enough to drive the ants indoors but not cold enough to make them hibernate.
ballard@cheddar.cc.ubc.ca (Alan Ballard) (02/17/90)
In article <1344@bridge2.ESD.3Com.COM> gpz@bridge2.ESD.3Com.COM (G. Paul Ziemba) writes: >... This seems to indicate that DosMuxSemWait() deals only with system >semaphores and not with RAM semaphores. I've certainly used this with no problem with RAM semaphores, having learned it from earlier sources that didn't contain this description. Whether it will continue to work in later releases is something only MS or IBM can comment on. I suspect the documentation is in error. Alan Ballard | Internet: Alan_Ballard@mtsg.ubc.ca University Computing Services | Bitnet: USERAB1@UBCMTSG University of British Columbia | Phone: 604-228-3074 Vancouver B.C. Canada V6R 1W5 | Fax: 604-228-5116