Producer for PowerPoint Slow Startup

[Guest]

Every time I start up Producer, it stalls at the splash screen for over two
minutes...taking up all my computer resources (100% CPU usage). The program
works fine, but the slow startup is really bothersome.

I'm wondering if this is normal, or if something wrong. Thanxs. =)

 

[Michael Koerner]

You may want to ask this question in the Producer newsgroup
news://msnews.microsoft.com/microsoft.public.producer

 

[Brian Sullivan]

Every time I start up Producer, it stalls at the splash screen for over two
minutes...taking up all my computer resources (100% CPU usage). The program
works fine, but the slow startup is really bothersome.

I'm wondering if this is normal, or if something wrong. Thanxs. =)

I takes only 10 seconds or so to startup on my 3 Ghz 512MB machine under
"normal" conditions-- so your startup time seems a little high.

But the time would depend on the cpu speed, the amount of memory on the
machine, what else is running, perhaps the speed of the hard disk.

Since you haven't provided any information about the configuration
conditions at startup it is hard to provide even a guess as to whether this
is normal.

 

[Steve Rindsberg]

Every time I start up Producer, it stalls at the splash screen for over two
minutes...taking up all my computer resources (100% CPU usage). The program
works fine, but the slow startup is really bothersome.

I'm wondering if this is normal, or if something wrong. Thanxs. =)

I don't use Producer so I don't know what's normal, but this kind of delay at
startup is often caused when you have this situation:

- You've opened a file from a network drive previously

- You start the program up when you're not attached to the network or the
previous network drive mappings are no longer in effect (ie, you had the P:
drive mapped to \\Server\Sharename and opened the file from there but no longer
have the P: drive mapped to anything)

If there's a list of recently opened files on the Producer menu, look at it
carefully. See if any of the files live on a network drive that's not
accessible now.

 

[Guest]

I'm running a mobile 1.6 Ghz Pentium 4 with 767MB of memory. The processor
isn't all that fast, but no other programs hangs up my computer like Producer
does. I timed the startup and it took about 80 seconds to start up.

Thanxs for the reply. =)

 

[Brian Sullivan]

I'm running a mobile 1.6 Ghz Pentium 4 with 767MB of memory. The processor
isn't all that fast, but no other programs hangs up my computer like Producer
does. I timed the startup and it took about 80 seconds to start up.

Not sure what the problem might be -- check out the network suggestion
(perhaps it is attempting to read a network location no longer there?)

There is nothing intrinsic in Producer that makes it slower than any other
program to load - at least nothing that I am aware of.

 

[Steve Rindsberg]

Not sure what the problem might be -- check out the network suggestion
(perhaps it is attempting to read a network location no longer there?)

Just to follow up on the logic there:

If a disk is physically present, checking to see if a file's there or not is a
matter of milliseconds. If it's a network share and not reachable, it may be
because the drive's not available or it may simply be network traffic, a temporary
glitch, whatever, so the system waits a good long while, sometimes 30 seconds,
before it gives up. If there are 10 files on the MRU list and it checks each one,
that can add up.

 

[Guest]

Thanks for the response. I don't have any network drives...so I don't
believe that's the problem. Would reinstalling Producer work?

 

[Brian Sullivan]

Thanks for the response. I don't have any network drives...so I don't
believe that's the problem. Would reinstalling Producer work?

Without knowing the cause of the slowness there is no way to know.

Uninstalling and reinstalling though I can't see having any negative effect
so you could try it I guess.

 

[Steve Rindsberg]

Thanks for the response. I don't have any network drives...so I don't
believe that's the problem. Would reinstalling Producer work?

Over to you on that one, Brian. But I don't imagine it could hurt anything, so I'd
think it's worth a try.