Bug Reports

Anything issues that occur please take the time to file a bug report on it. Since we are getting so close to RTM most of the kinks should be gone, but there are sill some kinks in the line and it would help MS out a lot. If you encounter BSODs, please remember to include your memory dump located at %windir%\MEMORY.dmp. If you encounter setup issues and you can get back in to either XP or Vista RC1, please bug those as well, and remember to include the logs located at either %windows.bt$\sources\panther or %windir%\panther.

Also please make your feedback public, that way if you have any questions one of us in the TechBeta can look the information up for you.

To make the feedback public follow these steps:

1.Download and install the Microsoft Beta Client
2. Launch MBC
3. Click on the 'Options' button on the left hand side of the window
4. Check the box marked 'Enable advanced tracking options' - NOTE: You only have to check this box once.
5. After you fill out a report, on the finish tab mark the box for 'Public - all site users'
6. File your report.

Also, Microsoft has asked us BTs about designing the new version of the MBC and I and probably some other TechBeta testers have submitted feedback asking for a way for the public to view their feedback.
--
Tom Ziegmann
Microsoft Certified Professional
Windows Vista / Server Longhorn TechBeta Tester
Windows Server 2003 SP2 TechBeta Tester

Tom,
I can't get the FTM to install from the feedback link in 5728. LOL had to go grab it off msft. Bugs in the bug reporter-lol
Jeff
P.S. Running MBC doesn't initialize the FTM; LOL
TOO FUNNY-buggy bug reporter!!-They better take your guys advice;to make a better one.
Jeff
"Tom Ziegmann" <tziegmann@msn.com> wrote in message news:5D3CCC37-E059-4843-B192-6895B44AF887@microsoft.com...
Anything issues that occur please take the time to file a bug report on it. Since we are getting so close to RTM most of the kinks should be gone, but there are sill some kinks in the line and it would help MS out a lot. If you encounter BSODs, please remember to include your memory dump located at %windir%\MEMORY.dmp. If you encounter setup issues and you can get back in to either XP or Vista RC1, please bug those as well, and remember to include the logs located at either %windows.bt$\sources\panther or %windir%\panther.

Also please make your feedback public, that way if you have any questions one of us in the TechBeta can look the information up for you.

To make the feedback public follow these steps:

1.Download and install the Microsoft Beta Client
2. Launch MBC
3. Click on the 'Options' button on the left hand side of the window
4. Check the box marked 'Enable advanced tracking options' - NOTE: You only have to check this box once.
5. After you fill out a report, on the finish tab mark the box for 'Public - all site users'
6. File your report.

Also, Microsoft has asked us BTs about designing the new version of the MBC and I and probably some other TechBeta testers have submitted feedback asking for a way for the public to view their feedback.
--
Tom Ziegmann
Microsoft Certified Professional
Windows Vista / Server Longhorn TechBeta Tester
Windows Server 2003 SP2 TechBeta Tester

Jeff wrote:

> Tom,
> I can't get the FTM to install from the feedback link in 5728. LOL had to go grab it off msft. Bugs in the bug reporter-lol
> Jeff
> P.S. Running MBC doesn't initialize the FTM; LOL

Jeff:

It worked for me, just as it always has.

David Wilkinson

Tom Ziegmann wrote:

> Anything issues that occur please take the time to file a bug report on it. Since we are getting so close to RTM most of the kinks should be gone, but there are sill some kinks in the line and it would help MS out a lot. If you encounter BSODs, please remember to include your memory dump located at %windir%\MEMORY.dmp. If you encounter setup issues and you can get back in to either XP or Vista RC1, please bug those as well, and remember to include the logs located at either %windows.bt$\sources\panther or %windir%\panther.
>
> Also please make your feedback public, that way if you have any questions one of us in the TechBeta can look the information up for you.
>
> To make the feedback public follow these steps:
>
> 1.Download and install the Microsoft Beta Client
> 2. Launch MBC
> 3. Click on the 'Options' button on the left hand side of the window
> 4. Check the box marked 'Enable advanced tracking options' - NOTE: You only have to check this box once.
> 5. After you fill out a report, on the finish tab mark the box for 'Public - all site users'
> 6. File your report.
>
> Also, Microsoft has asked us BTs about designing the new version of the MBC and I and probably some other TechBeta testers have submitted feedback asking for a way for the public to view their feedback.

Tom:

Does this mean we will get feedback? It is very hard to provide reports
when there is no feedback, and no access to Connect.

David Wilkinson

Guess I got a buggy one then.
LOL
Installed FTM from microsoft.com. But now;sending reports through MBC
doesn't initialize the FTM.
I have to run FTM separate.
Jeff

"David Wilkinson" <no-reply@effisols.com> wrote in message
news:upRew4z3GHA.3364@TK2MSFTNGP04.phx.gbl...
> Jeff wrote:
>
>> Tom,
>> I can't get the FTM to install from the feedback link in 5728. LOL
>> had to go grab it off msft. Bugs in the bug reporter-lol
>> Jeff
>> P.S. Running MBC doesn't initialize the FTM; LOL
>
> Jeff:
>
> It worked for me, just as it always has.
>
> David Wilkinson

You probably won't get direct feedback, unless a dev feels that you need to
be contacted. But you will get automatically generated e-mail when your bug
has been closed. But if you make it public I can go in to the feedback
database as a TechBeta tester and look your bug up for you.

Tom
"David Wilkinson" <no-reply@effisols.com> wrote in message
news:O2qYm5z3GHA.3364@TK2MSFTNGP04.phx.gbl...
> Tom Ziegmann wrote:
>
>> Anything issues that occur please take the time to file a bug report on
>> it. Since we are getting so close to RTM most of the kinks should be
>> gone, but there are sill some kinks in the line and it would help MS out
>> a lot. If you encounter BSODs, please remember to include your memory
>> dump located at %windir%\MEMORY.dmp. If you encounter setup issues and
>> you can get back in to either XP or Vista RC1, please bug those as well,
>> and remember to include the logs located at either
>> %windows.bt$\sources\panther or %windir%\panther.
>>
>> Also please make your feedback public, that way if you have any questions
>> one of us in the TechBeta can look the information up for you.
>>
>> To make the feedback public follow these steps:
>>
>> 1.Download and install the Microsoft Beta Client
>> 2. Launch MBC 3. Click on the 'Options' button on the left hand side of
>> the window
>> 4. Check the box marked 'Enable advanced tracking options' - NOTE: You
>> only have to check this box once.
>> 5. After you fill out a report, on the finish tab mark the box for
>> 'Public - all site users'
>> 6. File your report.
>>
>> Also, Microsoft has asked us BTs about designing the new version of the
>> MBC and I and probably some other TechBeta testers have submitted
>> feedback asking for a way for the public to view their feedback.
>
> Tom:
>
> Does this mean we will get feedback? It is very hard to provide reports
> when there is no feedback, and no access to Connect.
>
> David Wilkinson

Tom Ziegmann wrote:

> You probably won't get direct feedback, unless a dev feels that you need
> to be contacted. But you will get automatically generated e-mail when
> your bug has been closed. But if you make it public I can go in to the
> feedback database as a TechBeta tester and look your bug up for you.
>
> Tom
> "David Wilkinson" <no-reply@effisols.com> wrote in message
> news:O2qYm5z3GHA.3364@TK2MSFTNGP04.phx.gbl...
>
>> Tom Ziegmann wrote:
>>
>>> Anything issues that occur please take the time to file a bug report
>>> on it. Since we are getting so close to RTM most of the kinks should
>>> be gone, but there are sill some kinks in the line and it would help
>>> MS out a lot. If you encounter BSODs, please remember to include your
>>> memory dump located at %windir%\MEMORY.dmp. If you encounter setup
>>> issues and you can get back in to either XP or Vista RC1, please bug
>>> those as well, and remember to include the logs located at either
>>> %windows.bt$\sources\panther or %windir%\panther.
>>>
>>> Also please make your feedback public, that way if you have any
>>> questions one of us in the TechBeta can look the information up for you.
>>>
>>> To make the feedback public follow these steps:
>>>
>>> 1.Download and install the Microsoft Beta Client
>>> 2. Launch MBC 3. Click on the 'Options' button on the left hand side
>>> of the window
>>> 4. Check the box marked 'Enable advanced tracking options' - NOTE:
>>> You only have to check this box once.
>>> 5. After you fill out a report, on the finish tab mark the box for
>>> 'Public - all site users'
>>> 6. File your report.
>>>
>>> Also, Microsoft has asked us BTs about designing the new version of
>>> the MBC and I and probably some other TechBeta testers have submitted
>>> feedback asking for a way for the public to view their feedback.
>>
>>
>> Tom:
>>
>> Does this mean we will get feedback? It is very hard to provide
>> reports when there is no feedback, and no access to Connect.
>>
>> David Wilkinson
>
>

Tom:

But only after I have received a "bug-track number", yes? I have never
received one, ever.

What about this bug, for example? Can you track it?

[Note that 32-bit programs on x64 (XP and Vista) are installed to
Program Files (x86)]

1. Install Mozilla FireFox (for example) on Vista x64
2. Click Start->Programs-> and right click on Mozilla FireFox
3. Select Properties
4. Look at the target - it is missing the (x86)
5. Click the General (or any other) tab - error message states that
target is incorrect.

This bug does not occur in XP x64, suggesting that this is a Vista
issue, not a Setup issue.

A pretty fundamental bug in the OS, IMHO. We're not talking about a
missing driver here. This bug, AFAICT, affects every 32-bit application
installed on Vista x64. It certainly affects mine.

Maybe this is fixed in 5728 x64, but x64 is not available to MSDN or CPP
members.

David Wilkinson

I'll ask some of the TechBeta group to see if they can repro it for you.
"David Wilkinson" <no-reply@effisols.com> wrote in message
news:%23KlLcY13GHA.1588@TK2MSFTNGP02.phx.gbl...
> Tom Ziegmann wrote:
>
>> You probably won't get direct feedback, unless a dev feels that you need
>> to be contacted. But you will get automatically generated e-mail when
>> your bug has been closed. But if you make it public I can go in to the
>> feedback database as a TechBeta tester and look your bug up for you.
>>
>> Tom
>> "David Wilkinson" <no-reply@effisols.com> wrote in message
>> news:O2qYm5z3GHA.3364@TK2MSFTNGP04.phx.gbl...
>>
>>> Tom Ziegmann wrote:
>>>
>>>> Anything issues that occur please take the time to file a bug report on
>>>> it. Since we are getting so close to RTM most of the kinks should be
>>>> gone, but there are sill some kinks in the line and it would help MS
>>>> out a lot. If you encounter BSODs, please remember to include your
>>>> memory dump located at %windir%\MEMORY.dmp. If you encounter setup
>>>> issues and you can get back in to either XP or Vista RC1, please bug
>>>> those as well, and remember to include the logs located at either
>>>> %windows.bt$\sources\panther or %windir%\panther.
>>>>
>>>> Also please make your feedback public, that way if you have any
>>>> questions one of us in the TechBeta can look the information up for
>>>> you.
>>>>
>>>> To make the feedback public follow these steps:
>>>>
>>>> 1.Download and install the Microsoft Beta Client
>>>> 2. Launch MBC 3. Click on the 'Options' button on the left hand side of
>>>> the window
>>>> 4. Check the box marked 'Enable advanced tracking options' - NOTE: You
>>>> only have to check this box once.
>>>> 5. After you fill out a report, on the finish tab mark the box for
>>>> 'Public - all site users'
>>>> 6. File your report.
>>>>
>>>> Also, Microsoft has asked us BTs about designing the new version of the
>>>> MBC and I and probably some other TechBeta testers have submitted
>>>> feedback asking for a way for the public to view their feedback.
>>>
>>>
>>> Tom:
>>>
>>> Does this mean we will get feedback? It is very hard to provide reports
>>> when there is no feedback, and no access to Connect.
>>>
>>> David Wilkinson
>>
>>
>
> Tom:
>
> But only after I have received a "bug-track number", yes? I have never
> received one, ever.
>
> What about this bug, for example? Can you track it?
>
> [Note that 32-bit programs on x64 (XP and Vista) are installed to Program
> Files (x86)]
>
> 1. Install Mozilla FireFox (for example) on Vista x64
> 2. Click Start->Programs-> and right click on Mozilla FireFox
> 3. Select Properties
> 4. Look at the target - it is missing the (x86)
> 5. Click the General (or any other) tab - error message states that target
> is incorrect.
>
> This bug does not occur in XP x64, suggesting that this is a Vista issue,
> not a Setup issue.
>
> A pretty fundamental bug in the OS, IMHO. We're not talking about a
> missing driver here. This bug, AFAICT, affects every 32-bit application
> installed on Vista x64. It certainly affects mine.
>
> Maybe this is fixed in 5728 x64, but x64 is not available to MSDN or CPP
> members.
>
> David Wilkinson

Tom Ziegmann wrote:

> I'll ask some of the TechBeta group to see if they can repro it for you.

Tom:

Thanks!!

David Wilkinson

David, I can repro it on RC1 x64 As you posted earlier, this is a Vista
x64 problem, as it doesn't do this on XP Pro x64. Just about every 32bit
program that I have elected to have a desktop shortcut to has done it,
regardless of installer make/version.

--
Jane, not plain 64 bit enabled
Batteries not included. Braincell on vacation :-)
"David Wilkinson" <no-reply@effisols.com> wrote in message
news:%237$VRt13GHA.3476@TK2MSFTNGP04.phx.gbl...
> Tom Ziegmann wrote:
>
>> I'll ask some of the TechBeta group to see if they can repro it for you.
>
> Tom:
>
> Thanks!!
>
> David Wilkinson