Hyperion Entertainment Message Boards

Of course my configuration is a X1000 coupled with a HD5870 so you can take low power out of the equation. Why, are other Amigas out there? If Candi doesn't like Context Menu and the other way around it should say so. I love compositing effects so of course they are enabled. Also everything is the last version I have access to.

Recent testing points me more towards the combination of Odyssey + Candi as problematic. Also forgot to add previously that after the recent upgrade of Candi, errors began poping up whenever I used ResetWB while Candi was running.

Srtest wrote:Of course my configuration is a X1000 coupled with a HD5870 so you can take low power out of the equation. Why, are other Amigas out there? If Candi doesn't like Context Menu and the other way around it should say so. I love compositing effects so of course they are enabled. Also everything is the last version I have access to.

Recent testing points me more towards the combination of Odyssey + Candi as problematic. Also forgot to add previously that after the recent upgrade of Candi, errors began poping up whenever I used ResetWB while Candi was running.

Odyssey by itself can have some dramatic effects on the entire OS. Several days ago AmigaWorld.net began showing an advertisement by Cisco that didn't appear to be loading correctly and caused my entire system to slow down. The mouse pointer movement was jerky, scrollbars wouldn't drag properly and windows opened/closed in slow motion. If I disabled javascript in Odyssey, the slow-down effect was gone and the rest of the system operated normally.

Since you stated that you think the combination of Odyssey and Candi is problematic, you might try disabling javascript in Odyssey and see it it affects the problem. I must say that there is probably a lack of interest in solving problems with the previous operating system (OS 4.1u6).

I think that compatibility is not a matter of a certain version of the OS. An advertised feature should work pretty well all around and even if you throw at it some utils and startup options even on a "small parts" enviroment as when you combine AOS with a selection of utils.When I did the remodeling lately based on Candi and several new apps and utils I knew I was gonna get added functionality at the cost of some stability and mabye a small performance hit. Where it doesn't work you know beforehand so you don't even try. If I use AutoPoint it sometimes accelerates the appearance of an error on the exact moment of window switching so I guess some people knew what they were doing by not enabling it at startup. If the thing I'm talking about here was predictable it would also have been fine by me so this is why I try to isolate it.

I can't let go of Javascript in-browser as it is the main reason I use Odyssey and was stable until the recent updates of Candi + HD driver (I don't want to fiddle with downgrading). My continued testing shows that mixing Candi and Facebook is highly not recommended which I'm sure will be appreciated here till the point it makes you think it was deliberate

Happy Purim everybody! this is my beloved niece!

The most recent analysis:

Candi gives the DSI posted in this correspondense even if I just boot and wait. It is rare but is also proof that even if nothing does practically anything it still can produce the error. Fell asleep and caught it...

zzd10h advice helps: because I use AutoPoint I noticed that after enabling the non-blocking setting of both menus in GUI prefs, when issuing a first right click on the desktop it defaults to the previous menu so it seems it prevents a certain mix-up with the context menu (as far as the error goes) and reduces the chance of said error. Then if Context Menu is summoned it almost never causes it.

The heavy load condition which can produce mouse lags, system lags and eventually errors is lost on me. It seems to be a matter of other stuff as well which seems in itself related to the Odyssey, E-UAE, etc... usage when combined with Candi.

I mention again that it is best to remove Candi with exchange before ResetWB or changing settings that requires such reset because simply stopping it doesn't help.

All of this makes me wonder if maybe the very same thing which enables Candi to switch performance and halt its impact on the system while the system use other performance intense stuff (browsing with Java, Video - not Smtube, emulation), is causing this so called errors-lag issues with its own constant updating and starting/restarting, so it is a theory.

This concludes the issue on my part. Thanks for all who helped.

*addendum

After extensive harvesting of data and comparing to my recent usage it seems many people are reporing issues with the latest updates of MUI which obviouslly effects Odyssey and can contribute greatly to the heavy load condition and to Odyssey lock-ups like the general destabilization of the system whenever Odyssey is loaded.

After the recent update of Candi my issues with right clicking and ResetWB have been resolved, and so it seems the issues that remain become a factor when Odyssey is active and used heavilly which maybe even a recent MUI issue from what i gathered, and even those almost never happen when you switch to lower resolutions than 1600x1200 like I do on a crt monitor.

Saying that, I don't like the vibe of not supporting 4.1.6 because FE is out. Perhaps I'm a little late to the party as there have been 6 big updates but I think you always support the OS version that came before the last one was released. Maybe even the focus on stabilty rather than performance can reduce the attention needed for such support.

Either way, issue resolved.