Digital Workshop

I thought it would be helpful to assist DW by stress testing Opus XE 5.0. This would allow the Opus team to find many of the findings / discoveries and results in one place and updated. The method of presentation will be screen captures with annotations or movies all published here at the user forum.

I would encourage others to interact as a basis of feedback.. If any one would like to send me a series of screen captures with comments on issues that will impact Flex, I will be happy to try to recreate the problem and then post it as screen captures or movies.

The test will be primarily on the Flex module. Flex iwill become the primary means in which to publish for internet using Opus, so the Flex side of Opus will become a major part of our development using Opus here at eiProject Inc.

I hope this meets with the approval of DW.

Rick
_______________________________

___ link was removed by Rick ______

In general we would prefer people to confirm any potential issues directly with us via Technical Support before posting to the forums - this gives us a chance to confirm the issue is actually a problem before people get up in arms about things that may be limitations or misunderstandings rather than actual problems with the program.

Note this is NOT directed at anyone in particular, just a general comment that seems to be suitable here! Obviously you can discuss issues but it would be nice if you can ask us before shouting at us in public!

Hi Duncan,

First of all I would like to apologize for posting what I had discovered as a problem which (you say) I should have informed technical support first. .How was I to know that this particular issue was not to be made public or was sensitive information?

In short this is what happened: I ran my registry cleaner. Then I try later to start Opus and it was broken. I had to re-install it. Then again I ran the registry utility and again Opus broke. After several more times I decided to find out what was the problem. I then posted this on the site as an issue.

I am not a code worrier and was just reporting back from my system tools I purchased.

I quote you:

I am using a standard off the shelf registry cleaner and found that each time I use it, Opus breaks and I need to re-install it again.

Are you telling me that the majority of posting which describes isuues, potential problems, potential bugs, and bugs are cleared by technical support prior to being posted? This is not usual in users forums, when you find a problem, you post it on the forum.

Obviously - the bulk of post describing issues, bugs or discoveries are not going first to technical support prior to being posted.

I quote again:

I thought I was being helpful by posting our discoveries so that the Opux / Flex users may interact so that Opus becomes a better product. This was the spirit of my posting a Stress Test post was not to tear down Opus or to humiliate DW.

If you are offended by the title: "Stress Testing" then perhaps "Reviewing" would be better.

There is nothing in your policies which states that issues by users need be cleared first by technical support before they can be posted. Ultimately, each member will need to use their discretion on what is to be sent to technical support first. Without any clear guidelines, how does one know which questions need to cleared first?

For instance, what is the difference in posting about a Flex page jumping the gun by playing a movie when it should not play and a registry issue that if I use Clean Sweep, Opus breaks?

I am confused - as to how and when should you know which problems go to the forum or needs to go first be approved by technical support. I am feeling like I am being penalized for bad conduct when it was in the spirit of trying to resolved issues among seasoned uses.

Regards,

Rick

All I was suggesting is that people check first whether an issue is known or not actually a problem before treating it as a bug. That was all - a suggestion! Not a demand, a rule or a policy - just a suggestion. There is no approval or moderation of posts.
As I said - it wasn't you I was talking to/about in particular but everyone in general.

Thought I'd step in on Duncan's side here -- I have no relationship to
DW, just a satisfied customer that has been using Opus since 2001
and computers since you had to buy the parts and build your own.

Registry cleaners make very little difference (if any) to a modern
operating system, they just run through the registry deleting whatever
they have decided is not needed, sometimes compacting it as well.
I have had the same problem with all my Macromedia apps not
running after running a well known Register Cleaner several years ago.

I stopped using utilities like this when some published benchmarks
showed little or no performance or stability benefits against the risk of
running the cleaner and destabilizing the OS.
This applies to most so called "system tools" available today, including
those from some very well known manufacturers.

Paul

We test on the average of around 3 products per week hear in our product review labs, and although we do not perform benchmark testing, our staff members realize the benefits of fixing the problematic and fragile Window's system registry.

It is one thing to talk benchmarking and quite another to be working in the trenches. I provide user support for the Techsmith site with over 500 postings in helping others. Many of the problems stem from errors in the system registry.

A - When a pop up or a "display ontop" is requested by the user - where are these setting located?

B - When you uninstall a program what happens to the registry entries?

C - Now what if you are installing and uninstalling programs weekly - what would a registry look like?

Your statement which seems to be in agreement with the benchmark testing implies that a bloated or errors riddled system registry does not in anyway appreciably effect the performance of the OS and applications.

You act as those registry errors has little effect on the total performance and with regard over the management of settings for each program and path statements..The system registry has replaced the winini configuration system. If you have ever tweaked with these setting or just peeked in this file you would understand what the registry does and how changing these settings can have a great impact on programs.

The discussion had little to do with registry cleaners and had all to do with posting information that should have been sent to technical support first.

So from now on I will post what I think are bugs first to DW and will post then post on the user forum upon DW's approval. On all other issues, I will post here.

The topic of the Window's system registry is plentifull on the web, I speak from the experience from supporting user and from our own testing.

Regards,

Rick

Spoken like the average techie -- I know what the function of the
registry is -- I guess we'll just have to agree to disagree on some aspects of it.

Paul