Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!uunet!mcsun!ukc!harrier.ukc.ac.uk!zodiac.ukc.ac.uk!spr003
From: spr003%cluster@ukc.ac.uk (Jim Mansell)
Newsgroups: comp.windows.ms
Subject: Re: Problems w/ Win 3 and communications
Message-ID: <21537.2781ac54@cluster@ukc.ac.uk>
Date: 2 Jan 91 09:48:04 GMT
References: <1990Dec28.223625.4303@janus.mtroyal.ab.ca> <1990Dec29.000307.4305@janus.mtroyal.ab.ca>
Organization: Computing Lab, University of Kent at Canterbury, UK.
Lines: 31

In article <1990Dec29.000307.4305@janus.mtroyal.ab.ca>, hfreedman@janus.mtroyal.ab.ca writes:
> In article <1990Dec28.223625.4303@janus.mtroyal.ab.ca>, hfreedman@janus.mtroyal.ab.ca writes:
>> I am having a problem using any communications package within
>> Windows 3. Same or similar problems occur with Procomm Plus,
>> PC Anywhere, and even Windows Terminal.  I cannot seem to
>> configure these to use COMM 4 where my external modem resides.
>> No problem using these in DOS. Error messages upon Windows
>> configuration refer to Comm Port assigned to a DOS application. Mouse
>> also hangs.
>> 
> 
> 
> 
>> Any help would be greatly appreciated
>> Thanks
>> 
> 
> 
> details of system included in original posting.
> 
> 
> After trying various possible solutions, I managed to communicate
> using Terminal in Windows real mode. This was also after a change
> to WIN.INI to include under [TERMINAL] an indication that port is
> COMM 4. This does not seem to help in 386 enhanced mode, and DOS
> communications programs still do not work.  
> 
> Hope that the foregoing assists some others and further help
> would still be appreciated. Thanks again
> 
> [sorry for no signature - have not gotten to figure that out yet]