We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

Sleeper/GV 33.6 Speakerphone problem

sdmichael
sdmichael asked
on
Medium Priority
325 Views
Last Modified: 2010-04-25
Here's a real winner of a problem that's got me baffled.

I have a PowerMac 8100/100AV with a 256k L2 cache and 32MB of RAM and using System 7.5.5. I am
running the new GV Speakerphone 33.6 and I use Sleeper (a Screen Saver
and Disk Spindown utility) version 2.1.1.

If I use the Disk Spindown part of Sleeper, after a certain amount of
time, my Mac no longer recognizes that the GV Phone Engine extension has
loaded. So if someone tries to call me, the following error message
appears:

"The application "unknown" has unexpectantly quit because an error of
type 1 occured."

This effectively hangs the machine until I get home to click the "OK"
button. When I click the "OK" button, I get a second window which says
the following:

"Global Village Call Center could not start because the GV Phone Engine
Extension is not running. Use the Extensions Manager to turn on the GV
Phone Engine and restart your computer or reinstall the Call Center
software."

These events do not occur unless the disk has spun down *and* sat there
for a while. I have checked for conflicts, I have tried reinstalling the
software, I think I have tried everything. Have I ?

Is this actually a memory problem of some kind ("type 1") ?

This never happened to me using Megaphone with my Geopod, but then
again, that application had to be running to answer the phone and this
one did not. (Plus, I had a whole *bunch* of other problems with the
Geopod!)

I use the Disk Spindown feature only to save energy. I'm not worried
about HD wear. Should I just leave it Spin or is there a solution or
workaround?

Thanks in advance for your help!

Comment
Watch Question

Commented:
Sounds like a bug in "Sleeper". Sometimes code needs to be read from disk after it was purged from memory to make room for other stuff. With the geoport, the drivers probably get locked in memory for speed purposes so you probably wouldnt see this for the Geopod. If I were you I'd just disable the disk spindown. If its any consolation, keeping the drive spinning doesnt take up all that much energy compared to running the monitor. You may even use more energy spinning down and spinning up again since rotational kinetic energy varies directly with the square of rotation speed.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.