Getting on Vista Connect....

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.

"Mark Gillespie" <mark.gillespie@gmail.com> wrote in message
newsp.tdzmwoymj2q9yy@mark-pc...
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!

> 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.

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

--
"Those are my principles. If you don't like them I have others."
"Mark Gillespie" <mark.gillespie@gmail.com> wrote in message
newsp.tdzmwoymj2q9yy@mark-pc...

> 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 you have the feedback ID numbers I can try to get you the information you
need.
"peter" <peterk@nowhere.net> wrote in message
news:%23JAYlb0uGHA.3912@TK2MSFTNGP03.phx.gbl...

>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
>
> --
> "Those are my principles. If you don't like them I have others."
> "Mark Gillespie" <mark.gillespie@gmail.com> wrote in message
> newsp.tdzmwoymj2q9yy@mark-pc...

>
>

Your circumstance is different to Mark's. You decided to leave Windows
Vista Connect Beta whereas he wishes to join it.



<kevpan815@hotmail.com> wrote in message
news:%23ZMZsJ0uGHA.1504@TK2MSFTNGP03.phx.gbl...

>
> "Mark Gillespie" <mark.gillespie@gmail.com> wrote in message
> newsp.tdzmwoymj2q9yy@mark-pc...
> 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!
>

>

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
csnows@microsoft.com

Nick White [MSFT] <nicholas.white@.microsoft.com>
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" <mark.gillespie@gmail.com> wrote in message
newsp.tdzmwoymj2q9yy@mark-pc...

> 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.

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.

"Tom Ziegmann" <tziegmann@msn.com> wrote in message
news:e2FkWr0uGHA.1296@TK2MSFTNGP02.phx.gbl...

> If you have the feedback ID numbers I can try to get you the information
> you need.
> "peter" <peterk@nowhere.net> wrote in message
> news:%23JAYlb0uGHA.3912@TK2MSFTNGP03.phx.gbl...

>
>

.... summary of situation : 'MS disconnects Connect connectors'


"Mark Gillespie" <mark.gillespie@gmail.com> wrote in message
newsp.tdzmwoymj2q9yy@mark-pc...

> 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.

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: <csnows@microsoft.com>

Reason: 5.1.1 User unknown"




"Chad Harris" <HQ@MSFTtindenialovervistamess.com> wrote in message
news:%23Pav6p1uGHA.1372@TK2MSFTNGP04.phx.gbl...

> 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
> csnows@microsoft.com
>
> Nick White [MSFT] <nicholas.white@.microsoft.com>
> 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" <mark.gillespie@gmail.com> wrote in message
> newsp.tdzmwoymj2q9yy@mark-pc...

>
>

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

csnow@microsoft.com

or nicholas.white@microsoft.com

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" <REMOVETHISBIT@com> wrote in message
news:%23ku$H22uGHA.4460@TK2MSFTNGP04.phx.gbl...

> 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: <csnows@microsoft.com>
>
> Reason: 5.1.1 User unknown"
>
>
>
>
> "Chad Harris" <HQ@MSFTtindenialovervistamess.com> wrote in message
> news:%23Pav6p1uGHA.1372@TK2MSFTNGP04.phx.gbl...

>
>