home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!pdxgate!parsely!agora!bcapps
- From: bcapps@agora.rain.com (Brent Capps)
- Newsgroups: comp.windows.ms,comp.os.ms-windows.apps
- Subject: Re: NDW Quick Access window gone - help!
- Message-ID: <C1JwDJ.5Jp@agora.rain.com>
- Date: 28 Jan 93 06:22:30 GMT
- Article-I.D.: agora.C1JwDJ.5Jp
- References: <1993Jan23.002034.22896@ucsu.Colorado.EDU>
- Distribution: usa
- Organization: Open Communications Forum
- Lines: 27
-
- baileyc@ucsu.Colorado.EDU (Christopher R. Bailey) writes:
- >This all happened when I tried to run Procomm Plus for Windows and it came up
- >with an error telling me that it couldn't allocate a system timer and to close
- >another app. I've never had this problem until I stared using NDW and it's
- >screen saver (Sleeper). I know it's Sleeper causing the sys timer alloc
- >problem, but didn't know if this could have some other bizaar effect.
-
- I've experienced a bunch of problems with NDW 2.0 and Windows 3.1.
- The most annoying is a Procomm Plus for Windows interaction; if
- I pull up PPW then close it, any subsequent attempt to open it
- will result in an error message "unable to open COM2 -- port in use".
- This never happened until I installed NDW. The only workaround I've
- been able to find is to pull up WinFAX Pro (of all things) which
- will immediately note that COM2 is busy -- do you want to reset it.
- After resetting the port I send WFP away and then I can open PPW
- normally.
-
- The bugs in NDW 2.0 are legion. Dialog boxes with font problems,
- automatic processes that claim I don't have enough memory available
- (8 Meg of RAM not enough??!), mysterious unexplained system slowdowns,
- etc. If it didn't have such useful utilities I'd have chucked it
- by now.
-
- --
- Brent Capps (B4) htw-c++g+k++s-e++ | Collars and blindfolds and bullwhips
- bcapps@agora.rain.com (gay stuff) | that sting, these are a few
- bcapps@atlastele.com (telecom stuff) | of my favorite things
-