I, too, was a newbie but at least I learn (after being reprimanded by one of the
MVPs while testing Office XP) to lurk in the beta newsgroups before making any
posts. Experience testers want to make the software work, newbies just whine.
IMO, there are no strict rules on what to include when posting problems, but at
least include what happened before the problem pop up. The reason is so that
the developers of MSAS and helpful people can try and reproduce the same outcome
and then file or post a bug to MS. I do not know what is the failure rate, but
if more than half can reproduce the same outcome, I suppose someone has to read
and rewrite the code.
posting "cannot connect to the Internet" is pretty useless.
Start
Helpful post could be;
Boot up my computer.
Antivirus, firewall, MSAS, blah blah blah running in the background
cannot connect to the Internet
stop firewall from starting up, but AV and MSAS running when system boot
still unable to connect to the Internet
(Firewall not at fault)
stop antivirus from starting up, but firewall and MSAS running
aha, can connect to the Internet
(AV at fault)
check the settings of AV and reconfigure
Boot up my computer.
Antivirus, firewall, MSAS, blah blah blah running in the background
can connect to the Internet
End
But many posters don't basic details.
another fine example;
"I am using the latest version of MSN and my audio/video is giving me problems.
Please help."
and my ususal response would be
"post details of OS, hardware,blah blah blah)
Translated, it means, if running WinXP, which version, CPU and RAM, Video
adapter, brand, drivers version, webcam, brand and driver versions.
(As a volunteer, I am under no obligation to check for posts to my responses
since I am doing it for free)
and if the original poster makes another response, I might have missed the post
and hence may not be able to post a solution.
If the poster would have included the basic details in the original post, then
I'm sure any reponses would surely offer a possible solution.
charlievan wrote in news:
[email protected]