Moin Richard,

16.04.96 11:26, you wrote a message to All:

 Rw> Doesn anyone know if I have to serialise access to the Open,
 Rw> Close and Ioctl strategy routines in an OS/2 character device
 Rw> driver.

You don't have to if your device allows concurrent access.

[...]

 Rw> I stripped the driver down to a very simple dd that has a timer
 Rw> service routine and an ioctl. When the ioctl is called it blocks,
 Rw> then the timer routine ProcRuns after 256 calls; again the same
 Rw> problem if the driver is reopened while the original thread is
 Rw> blocked.

What magic do you use as the 'event id'? I'm very sure (and will check 
tomorrow), that I used a similar approach using the IOCtl data packet
address as event id. It's in an ADD (counts as character driver) and
several programs 
may access a controller via DosDevIOCtl concurrently.

Tschuess,
	Vitus

PIN:  10:1000/100.20
Fido: 2:2474/100.20

---