I'm going to make my response short, because I think I've spent enough time trying to get answer from you (Famatech).
1. If XP influenced your development, you must be saying you have been developing RAdmin 3 since XP came out. This is 3 years. It didn't take MS that long to write XP.
2. CPU load is still high when you lower your refresh rate. With as many machines as I have - I can also tell you it is a pain modify every connection just to decrease the refresh rate. I'll also bring to your attention that *YOU* set the default refresh rate to 100 - not me. So to be 'compatible' with Windows 2000 your customers have to modify every connection, and the RADMIN experience is not the same when you are sending 15 FPS as opposed to 100.
So your customers are affected because you haven't released a video hook - for 3+ years now.
3. So scripting a remote deployment isn't difficult? So it is safe to say you have already created your own little script to deploy RADMIN? Why not assist your users with it then? Pat is asking for it just a couple posts above this one. If it is so easy, why have your users been asking you for this - for years? I agree it isn't that difficult, but we've had to create our own deployment methods because of your lack of willingness to release one. Now the CEO and you are saying you won't even have one with RADMIN 3.0 - until after RADMIN 3.0 is released. So it is safe to assume this will be another program? Has development started on this yet? Hopefully you started on it a couple years back - with your development cycle, we may never see this program.
It is really disappointing to hear you say deployment is a simple task ... when your customers have been asking for a solution to this. I personally asked famatech for this, and was told I could develop my own. Gee, what an idea - I purchase a product, then have to develop my own method to deploy it. Not to mention installing a remote control program like yours, one of the basics features should be deployment.
The bottom line is -
- Developing a video hook for Windows 2000 should not have taken years, and should have been released already.
- Developing a method to deploy your product should have been released ages ago. Now you make it seem trivial, when even now people would like to have it.
- You have a great product, but it is you have been sitting on your butt while your competition has been developing and releasing product upgrades. Their customers asked for upgrades, and got them. What have your customers gotten? An old program that isn't fully compatible with software released 3+ years ago.
Yes, it functions - but here is a question for you: Would you rather drive down the highway in a new BMW or a 1970 VW ?? Sometimes you need to upgrade - for better features and compatibility. The computer software field changes to quickly to sit on a product for years without making a single upgrade. You quickly / easily get left in the dust.