Why have the Windows Updates (for Build 5308 CTP) been Removed?

  • Thread starter Thread starter Kevin John Panzke
  • Start date Start date
K

Kevin John Panzke

Why have the Windows Updates (for Build 5308 CTP) been Removed?

P.S. Microsoft is really making me mad now!
 
You are a Moron and will always remain a Moron.Go away . I now have put you on my kill file.
 
Well, I would have to agree with Kevin, Build 5342 of Vista is not a CTP
quality release, just an interim build showing snap shot of the progress the
Windows Team is making. Also, the build is only available in Ultimate, 5308
was available in other SKUs such as Home Basic, Premium and Business. So,
bugs filed under those would still be validated if they are unique to the
SKU.
--
--
Andre
Windows Connect | http://www.windowsconnected.com
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
 
Hold on... Start > Control Panel > Windows Update... that updates Windows
Defender definitions (badly) but it still did it. Did anyone elses Windows
Update work?

--
Zack Whittaker
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: www.msblog.org
» Vista Knowledge Base: www.vistabase.co.uk
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and not
of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared
that up!


--- Original message follows ---
 
And the Beta process is an ongoing process.

As an MSDN subscriber, you have limited Beta access "rights".
Obsolete Beta maintenance is not one of them.

PArticipating in the Technical Beta is not the same
as getting limited access through MSDN.




Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
 
bugs filed under those would still be validated if they are unique to the SKU

Isn't there a "closing date" for bugs in previous builds ?

I don't see the sense in maintaining a bug reporting mechanism open
for previous builds, once a newer build is available.

Either a bug was reported for the previous build, and it was fixed,
or the bug is still present in the current build, and should be reported for the current build.

Handling that any other way would be an absolute waste of time.

Bottom line, though : MSDN doesn't manage the Beta program.

Anything found at MSDN should be considered frosting on
the MSDN subscription cake, and not an "acquired Beta right".

If you want full Beta Program participation...you should be participating in the Beta.







Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
 
re:
I am in the BETA Program
Click to expand...

My comments were directed at the OP, who isn't in the Beta program.
I was referring strictly to the Beta frosting of the MSDN cake.

re:
There is no closing date for bugs in previous builds, unless it designated dead code or won't fix.
Click to expand...

I'm not sure I follow you.

If a bug is marked as "won't fix", there's a resolution for it.

I think you are referring to a "closing date" for resolution.
I was referring to a "closing date" for new bug reports.

After a new build is distributed, new bugs are filed against the *current* version, right ?

re:
Windows Connect | http://www.windowsconnected.com
Click to expand...

Shouldn't that be "Windows Connected", instead of "Windows Connect" ?

;-)



Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
 
I am confused by the entire process, especially with this build not being a
CTP. I need to get more info, when I do, I will report back.

re:
Windows Connect | http://www.windowsconnected.com
Click to expand...

Shouldn't that be "Windows Connected", instead of "Windows Connect" ?

Josh changed it on me. :) Thanks
--
--
Andre
Windows Connected | http://www.windowsconnected.com
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
 
Back
Top