Getting on Vista Connect....

  • Thread starter Thread starter Mark Gillespie
  • Start date Start date
M

Mark Gillespie

Have raised lots of bugs, and get closure and/or feedback reports most
days regarding vista bug reports I have submitted, however, I am not on
Connect Vista, so cannot view or the reqested followup comments, because I
got my Vista via MSDN CTP. If someone can help from MS, I would much
apprciate it.

I know the official line, is that Connect Vista is closed, but I sure it
can be worked around...

Thanks.
 
If Microsoft won't let me back in the Windows Vista Connect Beta, than I
hope that they don't let anyone else in either, Just FYI!
 
I have the same problem and after receiving a reply to an error report and
not being able to view the "fix" on Connect I send an error report to
Connect and as a reply received a statement that says this will be fixed in
the future...........
Please stand by
peter
 
If you have the feedback ID numbers I can try to get you the information you
need.
 
Your circumstance is different to Mark's. You decided to leave Windows
Vista Connect Beta whereas he wishes to join it.
 
Mark--

Email these contacts--they want feedback, and oblige them by feeding them.
They were on the setup group 3 hours ago, (so much for "MSFT doesn't ever
monitor these groups" and I posed a very similar question and you can go
look at it: You shouldn't have to use a middle man to get your questions
answered although I know the offer was well intentioned. This whole
transparency thing is frankly stupid. There is lack of information on Vista
components to a ridiculous degree by MSFT who pays hundreds of thousands of
dollars in salaries to employees who have computer science training and
degrees who are designated writers and community liasons and they haven't
written a thing on major components on Vista yet on MSFT's site.


Corey Snow Microsoft Connect Feedback Team
(e-mail address removed)

Nick White [MSFT] <[email protected]>
Nick runs a Technet Vista Team Blog

I posted to them: (and got no reply which was expected)

Why Nick/Corey--

1) Aren't the bugs' categories that Paul Donnelly has massaged 50 million
ways to Christmas for distribution to the appropriate developers, team
members and PMs, since you all have access to cluster servers and SQL and
all of MSFT's expertise can be brought to bear in sorting them haven't you
posted the categories of bugs and their contexts like

1) Fixed in Build
2) Will definitely be fixed in a future build or SP whatever
3) We won't fix until perhaps Vienna Blackcomb or never

so that the public can see what the bugs have been and continue to be in a
one stop shop searchable place on Connect just as the TBTs can? Why freeze
out the public in so many respects? There is no harm into distributing this
knowledge. The Gates Foundation has a big educational component. The Beta
for Vista denies information in a very harmful way toward Vista learning
curves. The technical writers on the Vista team have dragged in getting
info onto MSDN or Technet and the Product Guide is very very superfiical
sometimes giving important topics like Desmond Lee's teams' Win RE a couple
sentences. There is very little on Win RE on the Web--I include nearly all
the links when I post to help someone fix Vista that exist unless they add
nothing more to the info on my links as it is now.

Win RE btw is not working nearly as consistently as a Repair Install in XP
does. Auto Repair for apps and utilities and components of Vista
themselves is a good idea, but it fails much of the time.

Why doesn't the public who I believe is getting a couple builds as a primary
**marketing** i.e. sales tool have the same access to bug reports as
TBTs--why the "considering it"--it should be a no brainer.

Why deny the public access to the Vista Beta chats so that they can get
information on using Vista and a little of the information they are denied
by not having access to the bug info on Connect?

Why deny the public access to the Vista Live meetings?

What in the world is the downside and the harm to MSFT or anyone else not to
share this info.

There is scant information on MSFT's site now on several key topics,
features, and components within Vista.

CH
 
Several of us have tried that. Good luck, but I think you will get an
error. One problem is that almost none of the bugs are posted public and
there is no way to change it after it has been filed.
 
Chad, look at this email reply:

"This Message was undeliverable due to the following reason:

Each of the following recipients was rejected by a remote mail server.

The reasons given by the server are included to help you determine why each
recipient was rejected.

Recipient: <[email protected]>

Reason: 5.1.1 User unknown"




Chad Harris said:
Mark--

Email these contacts--they want feedback, and oblige them by feeding them.
They were on the setup group 3 hours ago, (so much for "MSFT doesn't ever
monitor these groups" and I posed a very similar question and you can go
look at it: You shouldn't have to use a middle man to get your questions
answered although I know the offer was well intentioned. This whole
transparency thing is frankly stupid. There is lack of information on
Vista components to a ridiculous degree by MSFT who pays hundreds of
thousands of dollars in salaries to employees who have computer science
training and degrees who are designated writers and community liasons and
they haven't written a thing on major components on Vista yet on MSFT's
site.


Corey Snow Microsoft Connect Feedback Team
(e-mail address removed)

Nick White [MSFT] <[email protected]>
Nick runs a Technet Vista Team Blog

I posted to them: (and got no reply which was expected)

Why Nick/Corey--

1) Aren't the bugs' categories that Paul Donnelly has massaged 50 million
ways to Christmas for distribution to the appropriate developers, team
members and PMs, since you all have access to cluster servers and SQL and
all of MSFT's expertise can be brought to bear in sorting them haven't you
posted the categories of bugs and their contexts like

1) Fixed in Build
2) Will definitely be fixed in a future build or SP whatever
3) We won't fix until perhaps Vienna Blackcomb or never

so that the public can see what the bugs have been and continue to be in
a
one stop shop searchable place on Connect just as the TBTs can? Why
freeze
out the public in so many respects? There is no harm into distributing
this
knowledge. The Gates Foundation has a big educational component. The Beta
for Vista denies information in a very harmful way toward Vista learning
curves. The technical writers on the Vista team have dragged in getting
info onto MSDN or Technet and the Product Guide is very very superfiical
sometimes giving important topics like Desmond Lee's teams' Win RE a
couple
sentences. There is very little on Win RE on the Web--I include nearly
all
the links when I post to help someone fix Vista that exist unless they add
nothing more to the info on my links as it is now.

Win RE btw is not working nearly as consistently as a Repair Install in
XP
does. Auto Repair for apps and utilities and components of Vista
themselves is a good idea, but it fails much of the time.

Why doesn't the public who I believe is getting a couple builds as a
primary
**marketing** i.e. sales tool have the same access to bug reports as
TBTs--why the "considering it"--it should be a no brainer.

Why deny the public access to the Vista Beta chats so that they can get
information on using Vista and a little of the information they are denied
by not having access to the bug info on Connect?

Why deny the public access to the Vista Live meetings?

What in the world is the downside and the harm to MSFT or anyone else not
to
share this info.

There is scant information on MSFT's site now on several key topics,
features, and components within Vista.

CH



Mark Gillespie said:
Have raised lots of bugs, and get closure and/or feedback reports most
days regarding vista bug reports I have submitted, however, I am not on
Connect Vista, so cannot view or the reqested followup comments, because
I got my Vista via MSDN CTP. If someone can help from MS, I would much
apprciate it.

I know the official line, is that Connect Vista is closed, but I sure it
can be worked around...

Thanks.
 
My fault Intel Sorry. I'm usually doing this with some other things going
on. I mistyped.

(e-mail address removed)

or (e-mail address removed)

I put an inadvertant "s" in Corey's address. Sorry.

Be very specific about the situation that you want to access bugs, etc. and
search them on Connect.

CH


Intel Inside said:
Chad, look at this email reply:

"This Message was undeliverable due to the following reason:

Each of the following recipients was rejected by a remote mail server.

The reasons given by the server are included to help you determine why
each recipient was rejected.

Recipient: <[email protected]>

Reason: 5.1.1 User unknown"




Chad Harris said:
Mark--

Email these contacts--they want feedback, and oblige them by feeding
them. They were on the setup group 3 hours ago, (so much for "MSFT
doesn't ever monitor these groups" and I posed a very similar question
and you can go look at it: You shouldn't have to use a middle man to get
your questions answered although I know the offer was well intentioned.
This whole transparency thing is frankly stupid. There is lack of
information on Vista components to a ridiculous degree by MSFT who pays
hundreds of thousands of dollars in salaries to employees who have
computer science training and degrees who are designated writers and
community liasons and they haven't written a thing on major components on
Vista yet on MSFT's site.


Corey Snow Microsoft Connect Feedback Team
(e-mail address removed)

Nick White [MSFT] <[email protected]>
Nick runs a Technet Vista Team Blog

I posted to them: (and got no reply which was expected)

Why Nick/Corey--

1) Aren't the bugs' categories that Paul Donnelly has massaged 50 million
ways to Christmas for distribution to the appropriate developers, team
members and PMs, since you all have access to cluster servers and SQL and
all of MSFT's expertise can be brought to bear in sorting them haven't
you
posted the categories of bugs and their contexts like

1) Fixed in Build
2) Will definitely be fixed in a future build or SP whatever
3) We won't fix until perhaps Vienna Blackcomb or never

so that the public can see what the bugs have been and continue to be in
a
one stop shop searchable place on Connect just as the TBTs can? Why
freeze
out the public in so many respects? There is no harm into distributing
this
knowledge. The Gates Foundation has a big educational component. The
Beta
for Vista denies information in a very harmful way toward Vista learning
curves. The technical writers on the Vista team have dragged in getting
info onto MSDN or Technet and the Product Guide is very very superfiical
sometimes giving important topics like Desmond Lee's teams' Win RE a
couple
sentences. There is very little on Win RE on the Web--I include nearly
all
the links when I post to help someone fix Vista that exist unless they
add
nothing more to the info on my links as it is now.

Win RE btw is not working nearly as consistently as a Repair Install in
XP
does. Auto Repair for apps and utilities and components of Vista
themselves is a good idea, but it fails much of the time.

Why doesn't the public who I believe is getting a couple builds as a
primary
**marketing** i.e. sales tool have the same access to bug reports as
TBTs--why the "considering it"--it should be a no brainer.

Why deny the public access to the Vista Beta chats so that they can get
information on using Vista and a little of the information they are
denied
by not having access to the bug info on Connect?

Why deny the public access to the Vista Live meetings?

What in the world is the downside and the harm to MSFT or anyone else not
to
share this info.

There is scant information on MSFT's site now on several key topics,
features, and components within Vista.

CH



Mark Gillespie said:
Have raised lots of bugs, and get closure and/or feedback reports most
days regarding vista bug reports I have submitted, however, I am not on
Connect Vista, so cannot view or the reqested followup comments, because
I got my Vista via MSDN CTP. If someone can help from MS, I would much
apprciate it.

I know the official line, is that Connect Vista is closed, but I sure it
can be worked around...

Thanks.
 
Doh!
Thanks

Chad Harris said:
My fault Intel Sorry. I'm usually doing this with some other things going
on. I mistyped.

(e-mail address removed)

or (e-mail address removed)

I put an inadvertant "s" in Corey's address. Sorry.

Be very specific about the situation that you want to access bugs, etc.
and search them on Connect.

CH


Intel Inside said:
Chad, look at this email reply:

"This Message was undeliverable due to the following reason:

Each of the following recipients was rejected by a remote mail server.

The reasons given by the server are included to help you determine why
each recipient was rejected.

Recipient: <[email protected]>

Reason: 5.1.1 User unknown"




Chad Harris said:
Mark--

Email these contacts--they want feedback, and oblige them by feeding
them. They were on the setup group 3 hours ago, (so much for "MSFT
doesn't ever monitor these groups" and I posed a very similar question
and you can go look at it: You shouldn't have to use a middle man to
get your questions answered although I know the offer was well
intentioned. This whole transparency thing is frankly stupid. There is
lack of information on Vista components to a ridiculous degree by MSFT
who pays hundreds of thousands of dollars in salaries to employees who
have computer science training and degrees who are designated writers
and community liasons and they haven't written a thing on major
components on Vista yet on MSFT's site.


Corey Snow Microsoft Connect Feedback Team
(e-mail address removed)

Nick White [MSFT] <[email protected]>
Nick runs a Technet Vista Team Blog

I posted to them: (and got no reply which was expected)

Why Nick/Corey--

1) Aren't the bugs' categories that Paul Donnelly has massaged 50
million
ways to Christmas for distribution to the appropriate developers, team
members and PMs, since you all have access to cluster servers and SQL
and
all of MSFT's expertise can be brought to bear in sorting them haven't
you
posted the categories of bugs and their contexts like

1) Fixed in Build
2) Will definitely be fixed in a future build or SP whatever
3) We won't fix until perhaps Vienna Blackcomb or never

so that the public can see what the bugs have been and continue to be
in a
one stop shop searchable place on Connect just as the TBTs can? Why
freeze
out the public in so many respects? There is no harm into distributing
this
knowledge. The Gates Foundation has a big educational component. The
Beta
for Vista denies information in a very harmful way toward Vista learning
curves. The technical writers on the Vista team have dragged in getting
info onto MSDN or Technet and the Product Guide is very very superfiical
sometimes giving important topics like Desmond Lee's teams' Win RE a
couple
sentences. There is very little on Win RE on the Web--I include nearly
all
the links when I post to help someone fix Vista that exist unless they
add
nothing more to the info on my links as it is now.

Win RE btw is not working nearly as consistently as a Repair Install in
XP
does. Auto Repair for apps and utilities and components of Vista
themselves is a good idea, but it fails much of the time.

Why doesn't the public who I believe is getting a couple builds as a
primary
**marketing** i.e. sales tool have the same access to bug reports as
TBTs--why the "considering it"--it should be a no brainer.

Why deny the public access to the Vista Beta chats so that they can get
information on using Vista and a little of the information they are
denied
by not having access to the bug info on Connect?

Why deny the public access to the Vista Live meetings?

What in the world is the downside and the harm to MSFT or anyone else
not to
share this info.

There is scant information on MSFT's site now on several key topics,
features, and components within Vista.

CH



Have raised lots of bugs, and get closure and/or feedback reports most
days regarding vista bug reports I have submitted, however, I am not on
Connect Vista, so cannot view or the reqested followup comments,
because I got my Vista via MSDN CTP. If someone can help from MS, I
would much apprciate it.

I know the official line, is that Connect Vista is closed, but I sure
it can be worked around...

Thanks.
 
"MSFT doesn't ever monitor these groups"
When was that stated?
If someone said that, it is obviously wrong.
But, there is no requirement for Microsoft to monitor these peer to peer
newsgroups and there should be no expectation of monitoring.
When Microsoft does post to the newsgroups, it is on their own time.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar
http://www.dts-l.org


Chad Harris said:
Mark--

Email these contacts--they want feedback, and oblige them by feeding them.
They were on the setup group 3 hours ago, (so much for "MSFT doesn't ever
monitor these groups" and I posed a very similar question and you can go
look at it: You shouldn't have to use a middle man to get your questions
answered although I know the offer was well intentioned. This whole
transparency thing is frankly stupid. There is lack of information on
Vista components to a ridiculous degree by MSFT who pays hundreds of
thousands of dollars in salaries to employees who have computer science
training and degrees who are designated writers and community liasons and
they haven't written a thing on major components on Vista yet on MSFT's
site.


Corey Snow Microsoft Connect Feedback Team
(e-mail address removed)

Nick White [MSFT] <[email protected]>
Nick runs a Technet Vista Team Blog

I posted to them: (and got no reply which was expected)

Why Nick/Corey--

1) Aren't the bugs' categories that Paul Donnelly has massaged 50 million
ways to Christmas for distribution to the appropriate developers, team
members and PMs, since you all have access to cluster servers and SQL and
all of MSFT's expertise can be brought to bear in sorting them haven't you
posted the categories of bugs and their contexts like

1) Fixed in Build
2) Will definitely be fixed in a future build or SP whatever
3) We won't fix until perhaps Vienna Blackcomb or never

so that the public can see what the bugs have been and continue to be in
a
one stop shop searchable place on Connect just as the TBTs can? Why
freeze
out the public in so many respects? There is no harm into distributing
this
knowledge. The Gates Foundation has a big educational component. The Beta
for Vista denies information in a very harmful way toward Vista learning
curves. The technical writers on the Vista team have dragged in getting
info onto MSDN or Technet and the Product Guide is very very superfiical
sometimes giving important topics like Desmond Lee's teams' Win RE a
couple
sentences. There is very little on Win RE on the Web--I include nearly
all
the links when I post to help someone fix Vista that exist unless they add
nothing more to the info on my links as it is now.

Win RE btw is not working nearly as consistently as a Repair Install in
XP
does. Auto Repair for apps and utilities and components of Vista
themselves is a good idea, but it fails much of the time.

Why doesn't the public who I believe is getting a couple builds as a
primary
**marketing** i.e. sales tool have the same access to bug reports as
TBTs--why the "considering it"--it should be a no brainer.

Why deny the public access to the Vista Beta chats so that they can get
information on using Vista and a little of the information they are denied
by not having access to the bug info on Connect?

Why deny the public access to the Vista Live meetings?

What in the world is the downside and the harm to MSFT or anyone else not
to
share this info.

There is scant information on MSFT's site now on several key topics,
features, and components within Vista.

CH
 
I posted everyone of my bugs public. I figured, Hey, it's a test unit with
no data on it, maybe it helps someone else.
 
Jupiter --

I don't know of requirements for MSFT to do anything. Since they are
blocking full participation of bug reviewing on Connect, and willfully
setting up a 3 card monte situation with bug reporting and reviewing on
Connect like on the sidewalks of the lower East side of NYC, and since they
refuse to share bugs and context them to the public, I am promoting
democracy by posting direct email addresses for the appropriate team members
when I see the need for feedback to get to the teams.

They just intensified their spyware called WGA and they secretly met with
the United States government (after receiving criticism for covering this
for 9 months from their own employees and their best known blogger Rob
Scoble) on June 1 and June 2 to turn over customer information to the DOJ
and MSN searched. The inflammatory flag in typical Gonzales deception mode
was to feint it had anything to do with the war on pornography.

This from a government that used pornographic torture and an AG who wrote
the memos supporting it along with John Yoo and several West Wing attorneys.

I haven't got any substantive expectations that MSFT do anything, so I'm
never surprised by them.

MSFT Turning up its Spyware called WGA Heat
http://www.microsoft-watch.com/article2/0,2180,2001181,00.asp

Microsoft Removes WGA 'Phone Home' Component
By Ryan Naraine
June 27, 2006

http://www.eweek.com/article2/0,1895,1982591,00.asp


CH


Jupiter Jones said:
"MSFT doesn't ever monitor these groups"
When was that stated?
If someone said that, it is obviously wrong.
But, there is no requirement for Microsoft to monitor these peer to peer
newsgroups and there should be no expectation of monitoring.
When Microsoft does post to the newsgroups, it is on their own time.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar
http://www.dts-l.org


Chad Harris said:
Mark--

Email these contacts--they want feedback, and oblige them by feeding
them. They were on the setup group 3 hours ago, (so much for "MSFT
doesn't ever monitor these groups" and I posed a very similar question
and you can go look at it: You shouldn't have to use a middle man to get
your questions answered although I know the offer was well intentioned.
This whole transparency thing is frankly stupid. There is lack of
information on Vista components to a ridiculous degree by MSFT who pays
hundreds of thousands of dollars in salaries to employees who have
computer science training and degrees who are designated writers and
community liasons and they haven't written a thing on major components on
Vista yet on MSFT's site.


Corey Snow Microsoft Connect Feedback Team
(e-mail address removed)

Nick White [MSFT] <[email protected]>
Nick runs a Technet Vista Team Blog

I posted to them: (and got no reply which was expected)

Why Nick/Corey--

1) Aren't the bugs' categories that Paul Donnelly has massaged 50 million
ways to Christmas for distribution to the appropriate developers, team
members and PMs, since you all have access to cluster servers and SQL and
all of MSFT's expertise can be brought to bear in sorting them haven't
you
posted the categories of bugs and their contexts like

1) Fixed in Build
2) Will definitely be fixed in a future build or SP whatever
3) We won't fix until perhaps Vienna Blackcomb or never

so that the public can see what the bugs have been and continue to be in
a
one stop shop searchable place on Connect just as the TBTs can? Why
freeze
out the public in so many respects? There is no harm into distributing
this
knowledge. The Gates Foundation has a big educational component. The
Beta
for Vista denies information in a very harmful way toward Vista learning
curves. The technical writers on the Vista team have dragged in getting
info onto MSDN or Technet and the Product Guide is very very superfiical
sometimes giving important topics like Desmond Lee's teams' Win RE a
couple
sentences. There is very little on Win RE on the Web--I include nearly
all
the links when I post to help someone fix Vista that exist unless they
add
nothing more to the info on my links as it is now.

Win RE btw is not working nearly as consistently as a Repair Install in
XP
does. Auto Repair for apps and utilities and components of Vista
themselves is a good idea, but it fails much of the time.

Why doesn't the public who I believe is getting a couple builds as a
primary
**marketing** i.e. sales tool have the same access to bug reports as
TBTs--why the "considering it"--it should be a no brainer.

Why deny the public access to the Vista Beta chats so that they can get
information on using Vista and a little of the information they are
denied
by not having access to the bug info on Connect?

Why deny the public access to the Vista Live meetings?

What in the world is the downside and the harm to MSFT or anyone else not
to
share this info.

There is scant information on MSFT's site now on several key topics,
features, and components within Vista.

CH
 
Drop a bug id and I'll see if it is visible.

Mark D. VandenBeg said:
I posted everyone of my bugs public. I figured, Hey, it's a test unit with
no data on it, maybe it helps someone else.
 
"The following feedback item you submitted at Microsoft Connect has been
updated:

Product/Technology - Windows Vista, Longhorn Server and IE 7 Beta
Feedback ID - 165187
Feedback Title - No License Agreement (EULA) Included With Product

The following fields or values changed:

Field Status changed from [Resolved] to [Closed]"
 
I hope you're not on any beta programs or expecting to be on any betas
anytime soon, because if you are you probably just lost any chance of
getting on any.
Chad Harris said:
Jupiter --

I don't know of requirements for MSFT to do anything. Since they are
blocking full participation of bug reviewing on Connect, and willfully
setting up a 3 card monte situation with bug reporting and reviewing on
Connect like on the sidewalks of the lower East side of NYC, and since
they refuse to share bugs and context them to the public, I am promoting
democracy by posting direct email addresses for the appropriate team
members when I see the need for feedback to get to the teams.

They just intensified their spyware called WGA and they secretly met with
the United States government (after receiving criticism for covering this
for 9 months from their own employees and their best known blogger Rob
Scoble) on June 1 and June 2 to turn over customer information to the DOJ
and MSN searched. The inflammatory flag in typical Gonzales deception
mode was to feint it had anything to do with the war on pornography.

This from a government that used pornographic torture and an AG who wrote
the memos supporting it along with John Yoo and several West Wing
attorneys.

I haven't got any substantive expectations that MSFT do anything, so I'm
never surprised by them.

MSFT Turning up its Spyware called WGA Heat
http://www.microsoft-watch.com/article2/0,2180,2001181,00.asp

Microsoft Removes WGA 'Phone Home' Component
By Ryan Naraine
June 27, 2006

http://www.eweek.com/article2/0,1895,1982591,00.asp


CH


Jupiter Jones said:
"MSFT doesn't ever monitor these groups"
When was that stated?
If someone said that, it is obviously wrong.
But, there is no requirement for Microsoft to monitor these peer to peer
newsgroups and there should be no expectation of monitoring.
When Microsoft does post to the newsgroups, it is on their own time.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar
http://www.dts-l.org


Chad Harris said:
Mark--

Email these contacts--they want feedback, and oblige them by feeding
them. They were on the setup group 3 hours ago, (so much for "MSFT
doesn't ever monitor these groups" and I posed a very similar question
and you can go look at it: You shouldn't have to use a middle man to
get your questions answered although I know the offer was well
intentioned. This whole transparency thing is frankly stupid. There is
lack of information on Vista components to a ridiculous degree by MSFT
who pays hundreds of thousands of dollars in salaries to employees who
have computer science training and degrees who are designated writers
and community liasons and they haven't written a thing on major
components on Vista yet on MSFT's site.


Corey Snow Microsoft Connect Feedback Team
(e-mail address removed)

Nick White [MSFT] <[email protected]>
Nick runs a Technet Vista Team Blog

I posted to them: (and got no reply which was expected)

Why Nick/Corey--

1) Aren't the bugs' categories that Paul Donnelly has massaged 50
million
ways to Christmas for distribution to the appropriate developers, team
members and PMs, since you all have access to cluster servers and SQL
and
all of MSFT's expertise can be brought to bear in sorting them haven't
you
posted the categories of bugs and their contexts like

1) Fixed in Build
2) Will definitely be fixed in a future build or SP whatever
3) We won't fix until perhaps Vienna Blackcomb or never

so that the public can see what the bugs have been and continue to be
in a
one stop shop searchable place on Connect just as the TBTs can? Why
freeze
out the public in so many respects? There is no harm into distributing
this
knowledge. The Gates Foundation has a big educational component. The
Beta
for Vista denies information in a very harmful way toward Vista learning
curves. The technical writers on the Vista team have dragged in getting
info onto MSDN or Technet and the Product Guide is very very superfiical
sometimes giving important topics like Desmond Lee's teams' Win RE a
couple
sentences. There is very little on Win RE on the Web--I include nearly
all
the links when I post to help someone fix Vista that exist unless they
add
nothing more to the info on my links as it is now.

Win RE btw is not working nearly as consistently as a Repair Install in
XP
does. Auto Repair for apps and utilities and components of Vista
themselves is a good idea, but it fails much of the time.

Why doesn't the public who I believe is getting a couple builds as a
primary
**marketing** i.e. sales tool have the same access to bug reports as
TBTs--why the "considering it"--it should be a no brainer.

Why deny the public access to the Vista Beta chats so that they can get
information on using Vista and a little of the information they are
denied
by not having access to the bug info on Connect?

Why deny the public access to the Vista Live meetings?

What in the world is the downside and the harm to MSFT or anyone else
not to
share this info.

There is scant information on MSFT's site now on several key topics,
features, and components within Vista.

CH
 
Actually Michael, I'm on many and have been for a good while, and contrary
to conventional wisdom the "suckass brown nose" allow your thinking to be
forced by people you want favors from perception of living" that seems to be
prevalant in a non-thinking, non-reading, non-critical America does not
always hold true or conform to a cookie cutter paradigm.

I understand you think that MSFT wants synchophant devotees who worship them
only on Betas, but it is constructive criticism that keeps them from
shipping even worse crap.

I would much rather see a post from you on the merits of what I said about
the software.

Are you ready to take that OEM challenge vs. retail media? Please enlighten
me with your vast experience in no boot Windows and the quality of OEM
materials for doing either a Repair Install in XP or reaching Win RE
(Startup Repair etc.) in Vista. I can hardly wait.

CH


michael e dziatkowicz said:
I hope you're not on any beta programs or expecting to be on any betas
anytime soon, because if you are you probably just lost any chance of
getting on any.
Chad Harris said:
Jupiter --

I don't know of requirements for MSFT to do anything. Since they are
blocking full participation of bug reviewing on Connect, and willfully
setting up a 3 card monte situation with bug reporting and reviewing on
Connect like on the sidewalks of the lower East side of NYC, and since
they refuse to share bugs and context them to the public, I am promoting
democracy by posting direct email addresses for the appropriate team
members when I see the need for feedback to get to the teams.

They just intensified their spyware called WGA and they secretly met with
the United States government (after receiving criticism for covering this
for 9 months from their own employees and their best known blogger Rob
Scoble) on June 1 and June 2 to turn over customer information to the DOJ
and MSN searched. The inflammatory flag in typical Gonzales deception
mode was to feint it had anything to do with the war on pornography.

This from a government that used pornographic torture and an AG who wrote
the memos supporting it along with John Yoo and several West Wing
attorneys.

I haven't got any substantive expectations that MSFT do anything, so I'm
never surprised by them.

MSFT Turning up its Spyware called WGA Heat
http://www.microsoft-watch.com/article2/0,2180,2001181,00.asp

Microsoft Removes WGA 'Phone Home' Component
By Ryan Naraine
June 27, 2006

http://www.eweek.com/article2/0,1895,1982591,00.asp


CH


Jupiter Jones said:
"MSFT doesn't ever monitor these groups"
When was that stated?
If someone said that, it is obviously wrong.
But, there is no requirement for Microsoft to monitor these peer to peer
newsgroups and there should be no expectation of monitoring.
When Microsoft does post to the newsgroups, it is on their own time.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar
http://www.dts-l.org


Mark--

Email these contacts--they want feedback, and oblige them by feeding
them. They were on the setup group 3 hours ago, (so much for "MSFT
doesn't ever monitor these groups" and I posed a very similar question
and you can go look at it: You shouldn't have to use a middle man to
get your questions answered although I know the offer was well
intentioned. This whole transparency thing is frankly stupid. There is
lack of information on Vista components to a ridiculous degree by MSFT
who pays hundreds of thousands of dollars in salaries to employees who
have computer science training and degrees who are designated writers
and community liasons and they haven't written a thing on major
components on Vista yet on MSFT's site.


Corey Snow Microsoft Connect Feedback Team
(e-mail address removed)

Nick White [MSFT] <[email protected]>
Nick runs a Technet Vista Team Blog

I posted to them: (and got no reply which was expected)

Why Nick/Corey--

1) Aren't the bugs' categories that Paul Donnelly has massaged 50
million
ways to Christmas for distribution to the appropriate developers, team
members and PMs, since you all have access to cluster servers and SQL
and
all of MSFT's expertise can be brought to bear in sorting them haven't
you
posted the categories of bugs and their contexts like

1) Fixed in Build
2) Will definitely be fixed in a future build or SP whatever
3) We won't fix until perhaps Vienna Blackcomb or never

so that the public can see what the bugs have been and continue to be
in a
one stop shop searchable place on Connect just as the TBTs can? Why
freeze
out the public in so many respects? There is no harm into distributing
this
knowledge. The Gates Foundation has a big educational component. The
Beta
for Vista denies information in a very harmful way toward Vista
learning
curves. The technical writers on the Vista team have dragged in
getting
info onto MSDN or Technet and the Product Guide is very very
superfiical
sometimes giving important topics like Desmond Lee's teams' Win RE a
couple
sentences. There is very little on Win RE on the Web--I include
nearly all
the links when I post to help someone fix Vista that exist unless they
add
nothing more to the info on my links as it is now.

Win RE btw is not working nearly as consistently as a Repair Install
in XP
does. Auto Repair for apps and utilities and components of Vista
themselves is a good idea, but it fails much of the time.

Why doesn't the public who I believe is getting a couple builds as a
primary
**marketing** i.e. sales tool have the same access to bug reports as
TBTs--why the "considering it"--it should be a no brainer.

Why deny the public access to the Vista Beta chats so that they can get
information on using Vista and a little of the information they are
denied
by not having access to the bug info on Connect?

Why deny the public access to the Vista Live meetings?

What in the world is the downside and the harm to MSFT or anyone else
not to
share this info.

There is scant information on MSFT's site now on several key topics,
features, and components within Vista.

CH
 
Drop a bug id and I'll see if it is visible.

ConnectFeedback ID 170896


---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0632-2, 08/10/2006
Tested on: 8/10/2006 7:51:22 PM
avast! - copyright (c) 1988-2006 ALWIL Software.
http://www.avast.com
 
The Only Reason that I dropped out of the Microsoft Connect Beta is the fact
that I had Severe Problems with Windows Vista Beta 1, Build 5219 CTP, 5231
CTP, 5270 CTP, and 5308 CTP (These Build's Destroyed my Dell Dimension 8400,
Just FYI). With Windows Vista Build 5270 CTP, all I got was the now famous
installation error message: There was a Problem Configuring the Windows
Image Foundation, most of the time, Just FYI. Windows Vista Beta 2 and
Build 5472 CTP, are the very first MSDN Build's that I do not have Severe
Problem's with (as long as I am care full not to install Incompatible
Program's), Just FYI.
 
Back
Top