Report IE7 bugs to Microsoft using the Beta Tool  
Author Message
Copernicus





PostPosted: Fri Mar 24 04:12:39 CST 2006 Top

Internet Explorer / IE >> Report IE7 bugs to Microsoft using the Beta Tool

From the IE blog:

As with the Beta 2 Preview, we are very interested in feedback and bug
reports for any issues found using it. Please feel free to utilize any of the
following feedback mechanism to send us your feedback.

Beta Client Bug Reporting Tool â?? You may install the Microsoft Beta Client
Tool ( http://www.hide-link.com/ ), which will help you fill
out a bug report and include important logs and machine information to help
us investigate a problem. This is the preferred way to report any issues that
you run into with the new build.


be given to IE team members to review and act upon.


http://www.hide-link.com/

Internet Explorer65  
 
 
Melelina





PostPosted: Fri Mar 24 04:12:39 CST 2006 Top

Internet Explorer / IE >> Report IE7 bugs to Microsoft using the Beta Tool That tool requires .NET Framework 2.0. I have a one month old computer but
it didn't have 2.0. So, I had to install that first and then the tool. The
tool is buggy. I wrote a report and then clicked back to check something
and most of what I had written in the "steps to reproduce" field was gone. I
had to do it all over again. Then it timed out uploading on validation and I
had to override that. This is improved though over what we had a year ago
when I last beta tested for Microsoft.




> From the IE blog:
>
> As with the Beta 2 Preview, we are very interested in feedback and bug
> reports for any issues found using it. Please feel free to utilize any of
> the
> following feedback mechanism to send us your feedback.
>
> Beta Client Bug Reporting Tool - You may install the Microsoft Beta Client
> Tool (http://go.microsoft.com/fwlink/?LinkId=43655), which will help you
> fill
> out a bug report and include important logs and machine information to
> help
> us investigate a problem. This is the preferred way to report any issues
> that
> you run into with the new build.
>

> be given to IE team members to review and act upon.
>
>
> http://go.microsoft.com/fwlink/?LinkId=43655


 
 
Sandi





PostPosted: Sat Mar 25 08:34:30 CST 2006 Top

Internet Explorer / IE >> Report IE7 bugs to Microsoft using the Beta Tool You seem to have quite a smattering of problems Melelina. I'm wondering if
your system itself, or the install is broken. Also, if you're using the
report tool in a Virtual Machine, that could likely cause issues as well.

--
__________________________________________
Sandi - Microsoft MVP since 1999
http://www.ie-vista.com
http://inetexplorer.mvps.org



> That tool requires .NET Framework 2.0. I have a one month old computer but
> it didn't have 2.0. So, I had to install that first and then the tool. The
> tool is buggy. I wrote a report and then clicked back to check something
> and most of what I had written in the "steps to reproduce" field was gone.
> I had to do it all over again. Then it timed out uploading on validation
> and I had to override that. This is improved though over what we had a
> year ago when I last beta tested for Microsoft.
>
>


>> From the IE blog:
>>
>> As with the Beta 2 Preview, we are very interested in feedback and bug
>> reports for any issues found using it. Please feel free to utilize any of
>> the
>> following feedback mechanism to send us your feedback.
>>
>> Beta Client Bug Reporting Tool - You may install the Microsoft Beta
>> Client
>> Tool (http://go.microsoft.com/fwlink/?LinkId=43655), which will help you
>> fill
>> out a bug report and include important logs and machine information to
>> help
>> us investigate a problem. This is the preferred way to report any issues
>> that
>> you run into with the new build.
>>

>> will
>> be given to IE team members to review and act upon.
>>
>>
>> http://go.microsoft.com/fwlink/?LinkId=43655
>
>


 
 
Melelina





PostPosted: Sat Mar 25 17:49:28 CST 2006 Top

Internet Explorer / IE >> Report IE7 bugs to Microsoft using the Beta Tool The host computer is a five week old new Dell XPS 600. Not likely the system
although this computer is a replacement for my 8300 which had multiple
hardware problems when less than two years old and still under a three year
extended warranty. Dell computers are not as solid as years ago when I got
my first Dell, but I don't think it is a hardware or general software
problem. I do tweak a bit and it could be I tweaked something that I
shouldn't have. I don't go crazy with tweaking though. I think the problem
of IE7 on the host computer has to do with my initially not being able to
uninstall the earlier beta as it didn't show up in add/remove programs. That
first beta didn't have any odd problems except no way to remove it. I tried
the command line which had an error in it when I tried it and thus it did
nothing. I then tried the registry fix, which got the beta to show in
add/remove programs, and I was able to uninstall it. In retrospect, I wonder
if it did not fully uninstall and that now I have some hodgepodge of two
betas on here.

I used the report tool on the host machine. I was surprised that a brand new
computer would not have .NET 2.0 installed. But I suppose that is because
Dell installs 1.1 for their help program not 2.0. Why would this report
tool cause issues on a virtual machine? I installed it there also (after
installing .NET 2.0). It is much improved since I participated in the MBSA
2.0 beta.

I noticed that I had no problems getting Google as the default search engine
on the guest virtual machine. That was because XP balloon popups have not
yet been turned off on that machine. I had issues getting Google to be
default on the host machine where I have balloon popups turned off. I wish
that Microsoft could give us a way to turn off those popups by application
instead of a blanket on or off. So, I suppose some problems on the host
could be due to my routine tweaking of XP Pro.




> You seem to have quite a smattering of problems Melelina. I'm wondering
> if your system itself, or the install is broken. Also, if you're using
> the report tool in a Virtual Machine, that could likely cause issues as
> well.
>
> --
> __________________________________________
> Sandi - Microsoft MVP since 1999
> http://www.ie-vista.com
> http://inetexplorer.mvps.org
>


>> That tool requires .NET Framework 2.0. I have a one month old computer
>> but it didn't have 2.0. So, I had to install that first and then the
>> tool. The tool is buggy. I wrote a report and then clicked back to check
>> something and most of what I had written in the "steps to reproduce"
>> field was gone. I had to do it all over again. Then it timed out
>> uploading on validation and I had to override that. This is improved
>> though over what we had a year ago when I last beta tested for Microsoft.
>>
>>


>>> From the IE blog:
>>>
>>> As with the Beta 2 Preview, we are very interested in feedback and bug
>>> reports for any issues found using it. Please feel free to utilize any
>>> of the
>>> following feedback mechanism to send us your feedback.
>>>
>>> Beta Client Bug Reporting Tool - You may install the Microsoft Beta
>>> Client
>>> Tool (http://go.microsoft.com/fwlink/?LinkId=43655), which will help you
>>> fill
>>> out a bug report and include important logs and machine information to
>>> help
>>> us investigate a problem. This is the preferred way to report any issues
>>> that
>>> you run into with the new build.
>>>

>>> will
>>> be given to IE team members to review and act upon.
>>>
>>>
>>> http://go.microsoft.com/fwlink/?LinkId=43655
>>
>>
>
>