Those Little Letters After the Version

Group?

I know from past experience that software is considered alpha release if an "A" is after Ver # and Beta release if a "B" is after the version but, What are the rest of these letters after the version # of Stardock Products?

The reason I'd like to know is, I don't want to download any Betas...Just Completed releases.

I do not like Betas of any software and they should only be released to beta testers...not paying customers.

So in the end ,How do I tell if a product is a fullly completed release? :I


TIA
3,079 views 15 replies
Reply #1 Top
RC = Release Condidate
RC+# = Release Condidate Number

C,D,E etc. are their build numbers.

If you have an ODNT subscription and are using thier Component Manager Normally Stardock places a bit of info including if it is a BETA or not in the download section at the bottom.

Though the best way to not download any BETA's from ODNT is to set your download area to "view only released components"(in the download section - top right drop down box) within the CM.
Reply #2 Top
Third Eye

The part about "view only released components" is wrong.
That's what I have on normally and WB 3.20b as well as AssWizard 1.00b, ObjSweeper 1.0a, ObjZip 1.11b, SprFolders 1.00a, and WB 3.10a show up as available.

So I'm running all Alpha/Beta releases of these components because there are no other alternatives.

WB acts like a alpha/beta release(unstable) but then again so does ObjectBar(not an alpa/beta release).

Frankly the only GUI component that hasn't acted like a beta is WebBlinds.

Thanks for the letter info.
Reply #3 Top
No, those are released components. Your past experience is not correct, in this case - a and b merely mean that they are not the inital release (probably because a bug was found in it). Whether or not they *act* like "released" components is a matter of opinion, but they have been marked as such.
Reply #4 Top
Incidentally, many of the paying customers partly paid in order to get access to those betas, which is why they're an option - some people like to get their hands on the very latest components, even if they're not necessarily the most stable (sometimes they are, sometimes not).
Reply #5 Top
TheGreenReaper

I really like the way Stardock products put a face lift on windows but, I'm really not happy about sacrificing the stability of other applications just to get a GUI that's more pleasing.

Please forgive me if I seem harsh about what follows but I'm only stating what I believe to be facts(maybe some opinion).

When you (or anyone else for that matter) purchase software from a vendor, are not you buying this because it is a completed program (although patches may come later for minor bugs) and not because it allows you access to all current programs still in the coding stage but working "good enough".

And is it not standard practice to relay information of this sort to the potential customer? Well that's not the case with Stardock....No mention of the fact that in order to keep your software working correctly you will be downloading new releases indefinitely.

I do not want my money back from this purchase, I just want a version that is stable under all circumstances and not just when I don't put too heavy a load on the OS.

And I don't want releases every other day/week just because the last release had bugs...Very Unprofessional..

If others would get over the glamour of this new face lift and the fact that can be part of the face lifts that sit on others desktop, then you may find that they too would abmit to many annoyances in Stardock programs.

Incidently, I didn't pay $50.00 so I could have access to those betas as you suggested so many others did.
I payed for what I thought was a full fledged stable and working program with possibly patches to follow in later months to cover any minor bugs reported.
Reply #6 Top
The release versions *are* intended to be completed versions. If you are having any specific problems with them, then you should indeed contact Stardock's support through the indicated channels (eg [email protected]). Alternatively you could ask here, or in the appropriate Stardock newsgroup(s) at news://news.stardock.com/ - so far, all you've said is that they act like beta programs - how?

The releases every day/week are *not* to be considered "releases". They would normally be restricted alpha versions, distributed to a select group of testers. However, Stardock hasn't got that. It *has* got an active user population who wish to get good products as much as Stardock wants to sell good products.

The fact is, programs are *always* "in the coding stage". The only difference is that Stardock snd it's customers have both found it benificial for them to allow users greater access to the works in development, especially considering the diversity of systems on which WindowBlinds etc are expected to work. Stardock isn't big - it can't provide huge testing labs to it's coders (which would drive the price up considerably) - but there are users that are willing to help test. You don't have to be one of them - all you have to do is use the fully released components. If these don't work then, yes, you have cause to complain . . . but you have to say what's wrong!

I'd also note that the trial versions are available so that you can gauge how well the product works on your system. If you had these problems with the trial versions of the components then, well . . . speaking as a user, I probably wouldn't have bought them. I would at least have checked beforehand to see if the problems I had experienced were fixed.
Reply #7 Top
>1st Paragraph reply....
The key work here is "intended"...Good Intentions pave the road to...well, you get the message.
How they act like betas...
1. mouse movement through items on menus leaves prior item hightlighted because code is slow to respond.
2. unloading and reloading of (espcialy OB) and WB necessary at times for desktop refreshing.
3. minimized windows don't always show up in task bar
4. clicking prevent WB from loading at startup is futile
5. graphical areas of simple applications sometimes distorted and requires number 2.
These are just a few oddities and happen with all skins, not just certain ones.

>2nd paragraph reply....
Cop-Out(Commercialism)

>3rd paragraph of reply....
Diversity of the systems expected to work on?....I suppose you are an advocate of the infamous(although lame)Linux OS(if that's what you want to call it)?
I believe the price of Stardock's products are in the ballpark of current day software of it's type so, being a small company is of no consequence.
I itemized a few of the problems that are ongoing.

>4th paragraph reply....
This paragraph seems like a "shot"(Archie Bunker Style) at me....If so then apparently I've struck a nerve of awareness.
Reply #8 Top
sorry to butt in here and I know I am no computer guru or artist or anything, but Nolen, if you are having so many problems than why did you buy Windowblinds???

I admit I do I have problems with WB and some apps, that is why I put them as apps on the ignore list (maybe you didn't know that was possible?). Plus, WB can't work with all programs because not all programs are meant to be skinned. The nice thing about WB it seems to me is that it tries at least to skin these apps and more often than not it succeeds.

Other than specific apps, I have not noticed any of your other problems with the latest beta of WB (maybe it's just me?). If you don't like what WB does then why did you buy it?? **stop whining**. No bad feelings intended.

Reply #10 Top
Nolen, just to respond to one 'small' part of your comments....that querying the 'OS diversity'...there is more to Windows than just '98 and XP.
There's 'one or two' others...and then multiply them by the number of diverse Shell-replacements and/or enhancements, and Windowblinds actually is running on dozens, if not hundreds of permutations.
LiteSTEP alone is in the wild in hundreds of release versions, each of which may, or may not affect WB and vise-versa differently.

Skinning is 'still' young...and developing....and evolving.

Just tell Microsoft to put a hold on OS development and [service packs] bug-squashes...for a few YEARS and Stardock may just be able to finally release a definitive WB version.

MS won't be doing that, so WB will realistically be an on-going project for some time to come...
Reply #11 Top
Ctitzen Nolan :
WB acts like a alpha/beta release(unstable) but then again so does ObjectBar(not an alpa/beta release).

Frankly the only GUI component that hasn't acted like a beta is WebBlinds.

Thanks for the letter info.

If you are having stability problems, it is much more likely to be your computer, or the operating system.
Reply #12 Top
snozzberry
Prozac? Yes, that's probably the answer for a lot of today's society in order to avoid any kind of thought provoking discussion.

builderjw
BS!

Jafo
A very intelligent post indeed. Finally someone has hit the nail on the head. The post is very insightful and awakening and truthful and as such I think this discussion is over.

Incidently, I'm not giving up hope on Stardock products as I'll continue to download latest releases until I get one that agrees with the OS.

If I've pissed anyone off then so be it...I'm entitled to my thoughts and opinions as well as all others.
Reply #13 Top
> The key work here is "intended"
> ...Good Intentions pave the road
> to...well, you get the message.

I get it, but what more do you want? For example, there has never been a stable feature set for WindowBlinds - users have always pushed for more features. Sometimes I get annoyed that bugs are not fixed, but I understand why. I would be much less pleased (and Stardock would be selling far fewer copies) if, for example, WindowBlinds was perfectly stable, but didn't skin any of the XP taskbar and start panel.

As to the specific problems, 1. is the only one I can make a suggestion on - menu items remain hilighted because the popup menus that are expanded when they are hilighted are still open (eg. I move over Accessories, it opens, then I move to Games and it will be hilighted too until it opens and Accessories is closed) - this isn't a bug, although it might not be the way you feel it should work (the standard Windows start menu doesn't work like this).

> Cop-Out(Commercialism)

Not sure what you mean there. Either Stardock lets ODNT subscribers get the alpha/beta versions or it does not. Some people want them. You don't have to get them. You can get the "released" updates that come out every month or so.

> Diversity of the systems expected
> to work on?....I suppose you are an
> advocate of the infamous(although
> lame)Linux OS(if that's what you
> want to call it)?

No. I mean Stardock products are run on every Microsoft OS, from 95 to XP (incidentally, of these, 98 and ME cause the most problems). As much as MS has done to make them look and act the same, there are significant differences between each of them. Worse, there are differences that *seem* insignificant but actually turn out to be the root cause of bugs. Then add in all the programs that can interfere - mostly because they do things incorrectly but it hasn't ever mattered before - and you have a highly volatile situation.

It doesn't help that one of the programs that Stardock programs use heavily are the display device drivers, which tend to be notoriously flaky in 2D (because fast games are what sell them, not fast window dragging). Most software doesn't have to work with any other software, apart from the OS. WindowBlinds and WindowFX have to work with *all* of it, and ObjectBar and DesktopX have to work with lots.

> This paragraph seems like
> a "shot"(Archie Bunker Style) at
> me....

Partly, yes (hey, if you're going to be harsh . . . ), but it's true as well. If you felt that the products were not to the standard you required (and all of the things you mentioned could have been seen in the evaluation version) you shouldn't have bought it! Saying "I'm not buying this because" has a motivating effect on companies.

> I believe the price of Stardock's
> products are in the ballpark of
> current day software of it's type
> so, being a small company is of no
> consequence.

Software has high fixed cost and low variable (per-unit) cost. This is one reason why it's easy for companies to expand fast - if they have a killer product, they can sell lots of copies of it quickly. It also means that small companies have to either price their products higher or focus on critical areas first.

On the stability issue, I'd have to ask: are you running 98 or ME? If so, maybe you should consider upgrading to an OS that actually provides a stable base for applications. Those legacy OSs also have severe limitations in the areas which ODNT uses most - the GDI and User resource blocks. If they run out, you're going to have problems.
Reply #14 Top
TheGreenReaper

Thanks for your input on this matter and coping with the harshness of my complaints/opinions.

No offense was intended to anyone that entered this discussion but if they were offended, I'm not gonna lose any sleep over it.
Reply #15 Top
To those who participated in this discussion..

I do appologize for any flames I may have thrown at you for I have just went to my primary OS(WIN2K) and set it up with all the OD products and to my surprise Win2K handles it much better than my alternative boot(WinME).

The only reason I didn't want to resort to this to begin with is that Win2K doesn't handle 3D Gaming as well as earlier versions of Windows(especially WinME) so I wanted an OS that would handle everything that I throw at it without having to switch OSes to gain an advantage due to the application I may be running.

I'm more comfortable with Win2K anyway because I've run it primarily for about 2 yrs.

It is realy too bad we are the mercy of Microsoft as far as getting what we want/need from an OS without having to buy multiple versions.

As of now, most(not all) problems I relayed before are gone due to the switch.

It would have been nice though if Stardock had mentioned the fact that their products were much more suitable for Win2K and above.

A final note:
I hate being wrong so expect this attitude in future endeavors of knowledge...But I'm not the kind of person that can't admit when I am wrong.

Regards and many thanks for the discussion and awakening.