Is DGM going to be updated?

from Stardock Forums
There are a couple of issues with DGM and I was wondering if these might be addressed before the final release of GalCiv. I assume there will be much more use of DGM when GC is released.

I say this for two reasons.

1) The seti@home program conflicts with DGM. This has been noted in some previous posts and I have observed this myself. Not sure why though.

2) I was trying to DL GalCiv at work today (Slow day!) and it would not DL unless I disabled most of the background processes. (Norton, wallpaper changer, and some others) Don't know which one was causing it. It would stop about halfway through the process and DGM would give me some errors. Sorry I didn't write them down at the time.

I think there will be some frustrated people when you release GalCiv and they have these problems. (Or maybe I'm the only one that has these problems! :sniff!: )

Scott
179 views 5 replies
Reply #1 from Stardock Forums Top
I were the one origninally making the post about the SETI@Home problems (or so I think :-). I haven't run SETI@home while using DGM since then. I just tried a few moments ago and suddenly DGM is having no problems with SETI??? It is as fast and smooth as always?????

Strange??????

Peter
Reply #2 from Stardock Forums Top
i think brad said ther server was getting hit pretty hard. check out their other products (object gesktop, windowblinds) they are getting tremendous numbers of hits. So you might have hit it at a hard time, i had a few errors a while back, but everything has been great lately.

rich
Multiplicity - Control multiple PCs using one keyboard and mouse
Reply #3 from Stardock Forums Top
is DGM really needed to play the GalCiv.? sometimes i just click on galciv.exe to start game.
Reply #5 from Stardock Forums Top
'1) The seti@home program conflicts with DGM. This has been noted in some previous posts and I have observed this myself. Not sure why though.'

The problem occurs with any background time-consumption software, and doesn't just affect the DGM (Cygwin's system pipes, for one, are also affected).

It has something to do with how they subsume the IDLE process, if I had to guess, which means that it probably isn't something that could easily be fixed.