Re: bad problem
- Posted by Irv Mullins <irvm at ellijay.com> Aug 07, 2001
- 472 views
On Tuesday 07 August 2001 10:09, George Walters wrote: > > The lockup when my monitor goes to sleep and can't be awakened is not the > only lockup issue. I've discovered that the program I've been working on, > customer file maintenance, that all have been helping me with, will also > lock up my telephone answering system which will answer the phone after 3 > rings. If I kill my ARF020 program the phone system will immediately pick > up the line. I will certainly like to find a solution to this. What could > EU be doing (or I'm doing) that could cause this?? Have you tried running the system resources monitor while doing this? It might prove interesting. Regards, Irv > ..george > > > ----- Original Message ----- > From: <gertie at ad-tek.net> > To: "EUforum" <EUforum at topica.com> > Sent: Monday, August 06, 2001 3:57 PM > Subject: Re: bad problem > > > On 6 Aug 2001, at 11:31, George Walters wrote: > > > I've noticed that everytime that I leave an EU program running (i.e. > > mike - > > > > nz's editor in particular) and my monitor goes into sleep mode, I can't > > wake > > > > the it up and have to hardware reset and reboot(even ctrl-alt-del is > > dead). > > > > Without it running, wake-up works fine and does so over several days. > > > > I had this same problem with another application a few months ago, and > > found no > > > solution for it, but i suspect it caused by quick loops in the code, that > > for some reason > > > the code doesn't deal with the OS grabbing the cpu back. Try putting some > > sleep(0) > > > into the source after every "while" line? > > > > The code i was running was a internet app that used EInetLib_full.ew, but > > i switched > > > everything over to tcp4u before i thought of this possible solution. My > > monitor was > > > going to sleep, even tho all bios and os settings said "no sleep", and on > > wakeup, i > > > discovered the *entire* puter was asleep, the clock had not been updated, > > the internet > > > connection was off and no net application knew about it, and no code had > > been > > > running anywhere on the puter. > > > > Kat > >