Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!udel!news.mathworks.com!news.kei.com!world!jhaungs
From: jhaungs@world.std.com (Jim Haungs)
Subject: Re: serial comm under VW 2.0
Message-ID: <D8znKM.50K@world.std.com>
Organization: The World Public Access UNIX, Brookline, MA
References: <3po8b6$6td@ixnews3.ix.netcom.com>
Date: Mon, 22 May 1995 16:38:45 GMT
Lines: 32

positiv1@ix.netcom.com (Suzanne Snow) writes:

>    Under Visual Works 1.0 the following statement opens a connection
>to the serial port.

>    DosTtyAccessor open:'COM2:'

>    Under Visual Works 2.0 the seemingly equivalent statement

>    PCTtyAccessor open:'COM2:'

>     returns with 'ERROR_FILE_NOT_FOUND'

>    Do I need to initialize something.   Even if this works it seems
>the  getOptions message for PCTtyAccessor won't work.   Do I need to
>file in  something besides serial.st?

There is a bug in the PCTtyAccessor class>> open: method.
The VM (or the OS) won't allow the colon as part of the device 
file name, but the match expression in this method requires it.  

Remove the colon from the 'COM#:' string,in this method,
and it will work.

I reported this to ParcPlace last fall, but I don't think the fix
got into the maintenance release.  I should warn you: this fix works
correctly in OS/2; I don't know how DOS will handle it, but my 
guess is, it should work.

Jim


