🚀 go-pugleaf

In article <1993Jan21.032019.9452@netcom.com> tomd@netcom.com (Tom Dempster) writes:
>Rich Bersamin (cfgs@td2cad.intel.com) wrote:
>: 
>.  I can hear the connect
>:  but the problem is that I don't see anything on my screen which
>:  tells me this (i.e Connect 2400 or whatever). 
>
>I had precisely this problem for many weeks last year. Nothing I did with
>messing around with the init string, port selection, result codes, environment
>or anything else everyone suggested had any affect. Then the problem disappear-
>ed suddenly when, as a result of total disgust and lack of need, I stopped
>using Windows altogether. (V.3.0) Then one day about 8 months later I invoked
>Windows once to do something. After exiting Windows, I found that the problem
>had returned, just as before. (Again-this after 8 months of *flawless* modem
>performance) A warm re-boot at this point did not restore proper operation,
>however a cold restart did. Since then Windows has been entirely removed from
>the system. I dont know beans about this stuff; especially Windows config-
>uration gobbledy-gook, but I do know what works. 

Thanks for all the response to my ProComm Plus query.  It seems I had pretty
much the same problems as Tom Dempster (see above).  I tried running PCPLUS
again using the same setting I mentioned only this time I loaded DOS (5.0) off 
of floppy disk and everything worked just fine.  With this in mind I started
to play around with my autoxec.bat and config.sys files to see what was the
real cause.  I've narrowed it down to either 'running smartdrv' or 'loading
DOS into high mem'.  I'll keeping playing around though.  Thanks again.