oooooohhhhhhhh

just 2

nice try though. sounded like a good 1

hey John...did you happen to hit 'refresh data' under View tab????

ya many times

ifn stardock can't set me straight i dunno who can. maybe 1 of the stardock experts will see this thread. i'll be checkin. over and out

I've a silly question, how much ram do you have installed and what size swap file and also do you run out of virtual memory at times?

You may need to remove un-needed services from memory to free up some operational space. That server busy thing is a local issue, I am pretty sure...

You might want to load Taskmanager, though it isn't that informative, I use TaskInfo2003, before the error, or it will take forever to load after you get that error. With TaskInfo you can see each and everything in memory in detail and you will be able to see if it is actually SDC or a local service doing the dirty deed, I know it is local on my end and revoles around the fact that I have only 128 meg of ram installed and once Windows XP Pro is loaded there is only 20 megs of less free, so if I have something loaded and then load SDC and then click a link or try to load IE I get the "server busy, switch to, retry,etc" and it pretty much hangs the system because it is eating up CPU cycles and constantly swapping to drive and back...

little studder problem there, lPlural?

hey Jam....in case you peek back at this thread.......your wallpapers are great

iplural, i got 512 of ram goin. 767mb allocated for swap file. virtual memory hasn't been a problem for me since i went from winme to xp. i'm sure it's an issue on my end.

fixed it here...

and nope not a ram issue after all, I finally took a look at it instead of just ignoring it.
I opened up Internet Explorer for all in coming and out going traffic onall UDP ports to the following addresses

www.wincustomize.com
www.stardock.com
www.stardock.net

and *poof* all gone...

probably mess around with it later and try to nail a range of UDPorts instead of all of them.

I did try the specific UDP port that was coming up when the error did happen.. But then it rolled over to another port when I enabled the first port, so then I enabled the new port and it rolled over again...

That is what prompted me to open all to specific addresses, and sure enough, no more error...
odd...
has to be a real fix to it, other than the one that I am using at this point...

I m going to head over to MSDN and see what they have on the -Embedding switch when calling up IE from a parent application as a plugin... Maybe be something there, or on another site, who knows. but it has to be a common issue to some extent in some forum some where, meaning there is an answer just got to find it....

wommers, your system is probably something totally different and I m not using Zone Alarm so it probaly wouldn't work anyway even if it happened to be the same thing on your system, but it is a local issue, soooo...

good luck, I'll let you know if I find something...

jam