NOD32 2.5 BETA

  • Thread starter Thread starter Ian JP Kenefick
  • Start date Start date
From: "lee" <[email protected]>

|
| I have mixed feelings about public BETA releases. Which "party" gains
| the most from public BETA testing?

I totally agree. I don't like being an unpaid software tester.

*IF* you are going to try the software out, it should only be installed on a non-production
spare computer.

Take the MS WinXP SP2 Beta, MS Anti Spyware Beta or the MS Installer v3.1 Beta.
Unknowledgeable people use them and then bitch in the MS News Groups when they crash or have
complications.

What did they expect ?
 
David said:
From: "lee" <[email protected]>
|
| I have mixed feelings about public BETA releases. Which "party" gains
| the most from public BETA testing?

I totally agree. I don't like being an unpaid software tester.
Exactly, David, that's the essence of my objection to public BETA
testing. It subcontracts (without consideration) the obligation for
debugging and overall quality assurance to the public.
 
Exactly, David, that's the essence of my objection to public BETA
testing. It subcontracts (without consideration) the obligation for
debugging and overall quality assurance to the public.

I disagree. It does not subcontract the public at all. A public BETA
is there for experienced users to try out the new software and report
back and issues experienced. There is no obligation and there is
plenty of wanring. The software is labelled BETA for a reason.
 
From: "Ian JP Kenefick" <[email protected]>


|
| I disagree. It does not subcontract the public at all. A public BETA
| is there for experienced users to try out the new software and report
| back and issues experienced. There is no obligation and there is
| plenty of wanring. The software is labelled BETA for a reason.
| --
|
| Regards,
| Ian Kenefick
| www.ik-cs.com/got-a-virus.htm

Disclaimers and being called Bata does not assure that they will be used on production
platforms

Post 1 -
"Installed the Beta on a server that is used for Citrix. Worked well for
approimately a week and then blew up. Generated an error log of 1.7 gig and
filled up the root drive. Had to kill the error log before reading and
removed the program. Any one have any ideas why it might have blown up?"


Post 2 -
"This morning two of our computers started running the Windows Installer 3.1
Beta. The computers are running XP professional and the install hangs half
way through. Any known issues and how can I get this update off my computers
now that it has been downloaded and is ready to install."


Post 3 -
"Today WindowsUpdate (or rather AutoUpdate) installed Windows Installer
3.1 on my Windows XP Pro SP2. After rebooting I found an entry in my
Add/Remove Programs "Windows Installer 3.1 RC1". I also found
C:\WINDOWS\MSI31-RC1.log - both of which seem to indicate that I have a
beta or release candidate installed.

Is that normal that WindowsUpdate now installs beta ware without even
telling me? It just said

Windows Installer 3.1

The Microsoft® Windows® Installer 3.1 is the application installation
and configuration service for Windows and is available for Microsoft
Windows 2000 SP3 and later, Microsoft Windows XP, Microsoft Windows XP
SP1, Microsoft Windows XP SP2, and Microsoft Windows Server 2003. The
additional features in version 3.1 help make creating, distributing, and
managing updates to applications easier and more efficient."
 
Ian said:
I disagree. It does not subcontract the public at all. A public BETA
is there for experienced users to try out the new software and report
back and issues experienced. There is no obligation and there is
plenty of wanring. The software is labelled BETA for a reason.

You're missing my point. Maybe that's because I was less clear than I
should have been. My error.

I realize there is no obligation on the part of the public to test BETA
software. That's not the *obligation* I was referring to. And I do
understand why BETA software is labled as such :). My point is, what
exactly does the public gain from participation in public BETA testing?
Other than the privilege of assisting the developer in containing his
cost of quality? You don't need to feel obligated to respond. My
questions are mostly rhetorical.
 
Disclaimers and being called Bata does not assure that they will be used on production
platforms
Agreed.

Post 1 -
"Installed the Beta on a server that is used for Citrix. Worked well for
approimately a week and then blew up. Generated an error log of 1.7 gig and
filled up the root drive. Had to kill the error log before reading and
removed the program. Any one have any ideas why it might have blown up?"

:( Not ur friend lol
Post 2 -
"This morning two of our computers started running the Windows Installer 3.1
Beta. The computers are running XP professional and the install hangs half
way through. Any known issues and how can I get this update off my computers
now that it has been downloaded and is ready to install."
Sticky...

Post 3 -
"Today WindowsUpdate (or rather AutoUpdate) installed Windows Installer
3.1 on my Windows XP Pro SP2. After rebooting I found an entry in my
Add/Remove Programs "Windows Installer 3.1 RC1". I also found
C:\WINDOWS\MSI31-RC1.log - both of which seem to indicate that I have a
beta or release candidate installed.

This is not an opt-in? BETA releases are opt-in on Auto update?
Is that normal that WindowsUpdate now installs beta ware without even
telling me? It just said

Windows Installer 3.1

The Microsoft® Windows® Installer 3.1 is the application installation
and configuration service for Windows and is available for Microsoft
Windows 2000 SP3 and later, Microsoft Windows XP, Microsoft Windows XP
SP1, Microsoft Windows XP SP2, and Microsoft Windows Server 2003. The
additional features in version 3.1 help make creating, distributing, and
managing updates to applications easier and more efficient."

Im almost sure that public beta are opt-in for windows Update. I will
go look and post a link to my findings later.
 
You're missing my point. Maybe that's because I was less clear than I
should have been. My error.

No problem... :)
I realize there is no obligation on the part of the public to test BETA
software. That's not the *obligation* I was referring to. And I do
understand why BETA software is labled as such :). My point is, what
exactly does the public gain from participation in public BETA testing?
Other than the privilege of assisting the developer in containing his
cost of quality? You don't need to feel obligated to respond. My
questions are mostly rhetorical.

I get this from BETA stuff...

-I get to see new software and new features and test them on one of my
systems to see how they work. I can see how new technologies will
effect my system.

-As it is still in the BETA stage you can recommend changes to the
software.

-I get to test new stuff. Since I'm a techie I like interacting with
vendors and making suggestions.


this is just some...
 
I get this from BETA stuff...

-I get to see new software and new features and test them on one of my
systems to see how they work. I can see how new technologies will
effect my system.

-As it is still in the BETA stage you can recommend changes to the
software.

-I get to test new stuff. Since I'm a techie I like interacting with
vendors and making suggestions.

this is just some...

An informative place to read and post about the current, IMO excellent
NOD32 2.5 beta, rather than whine about its existence, is here:

http://www.wilderssecurity.com/showthread.php?t=73278
 
My point is, what
exactly does the public gain from participation in public BETA
testing?

What possible gain does the public get from helping?! One way or the
other, that program would become available. Why shouldn't they (those
willing and capable of testing) be afforded the opportunity to do so to
ensure a better final product?
Other than the privilege of assisting the developer in containing his
cost of quality?

It's more the quality than the cost of quality. As a software developer,
how would you even hope to test against all possible configurations and
environments, or at least a large percentage of them? BETA allows the
software to be exposed to a greater number of variables than would be
possible internally.
 
Kindly refrain from referring to my positive remarks about Nod32 2.5
BETA as 'whining'

I had no intention of referring to your remarks as whining and am sad you
should have thought I was doing so.
 
[snip]

BETA as 'whining'
I had no intention of referring to your remarks as whining and am sad you
should have thought I was doing so.

Don't be sad but reply to the person who you are directing your
remarks to. If it a general reply reply to the OP.
 
[snip]

BETA as 'whining'
I had no intention of referring to your remarks as whining and am sad you
should have thought I was doing so.

Don't be sad but reply to the person who you are directing your
remarks to. If it a general reply reply to the OP.

Thanks for the advice. I keep over-estimating the intelligence and
underestimating the fragility of people's egos in these news groups.
 
From: "Howard Harris" <[email protected]>


|
| Thanks for the advice. I keep over-estimating the intelligence and
| underestimating the fragility of people's egos in these news groups.
|
| --
| Howard

Welcome to UseNet ! ;-)
 
Back
Top