I'll see your error 0x8050800c and raise you (0x8050800d)

[Guest]

What's the purpose of error codes like this (0x8050800d)?...

Microsoft surely has enough money to pay someone to code up the
human-readable version. It's 2006 and we shouldn't accept this poor
quality, even in a Beta product!

Shame on the hackers who wrote that!

 

[Guest]

Hello SpamFighter,

Which one is 0x8050800c in the Subject or 0x8050800d in the Message.

Have a look at this article. It may be relevant to your prºblem.
Subject: Error 8/10/2006 1:54 AM PST
By: Trish In: microsoft.private.security.spyware.general

There has also been some input from the MSFT guys regarding the issue. Using
the Search For function type: `0x8050800d or 0x8050800c` and you will see
what I meªn.

Good luck

 

[Guest]

Hello SpamFighter,

Which one is 0x8050800c in the Subject or 0x8050800d in the Message.

Have a look at this article. It may be relevant to your prºblem.
Subject: Error 8/10/2006 1:54 AM PST
By: Trish In: microsoft.private.security.spyware.general

There has also been some input from the MSFT guys regarding the issue. Using
the Search For function type: `0x8050800d or 0x8050800c` and you will see
what I meªn.

Thanks for the reply.

When my disk is full, Microsoft tells me "Disk is full. Remove some
files." ... it doesn't say "Error code 1208098234" and then I have to go
look it up in a forum...

Error code 0x8050800d is how software worked in 1975...

The whole point of my posting is that we shouldn't have to SEARCH forums
for the information. Why should an error be a secret code, except to
hide some incompetence?

If I were Bill Gates, I'd dock the pay of the manager who didn't put
messages in place of error codes in beta software (but it's clear that
I'm not Bill Gates).

 

[Guest]

Hi,

Now I see your point.
--

Thanks for the reply.

When my disk is full, Microsoft tells me "Disk is full. Remove some
files." ... it doesn't say "Error code 1208098234" and then I have to go
look it up in a forum...

Error code 0x8050800d is how software worked in 1975...

The whole point of my posting is that we shouldn't have to SEARCH forums
for the information. Why should an error be a secret code, except to
hide some incompetence?

If I were Bill Gates, I'd dock the pay of the manager who didn't put
messages in place of error codes in beta software (but it's clear that
I'm not Bill Gates).

 

[Guest]

Actually, it would be for purposes of consistancy and ease of searching
knowledgebases. It avoids "such and such is broken" and "thingamajig don't
work" both in reference to the same problem. , but neither contains the same
search string.

It may make it difficult for some people to comprehend, but it lends
infinite clarity to those who need to research the problem.

Always happy to obfuscate. ;-)

 

[Guest]

I am only posting here because i couldn't post a new topic/thread.
I recently installed windows defendr beta 2 (After finalll figuring out how
to get GDI working) But i have problems updating, ti said i had not updated
in 259 days, the help file said to enter some commands into run (to clear the
old signature and to make sure autoupdate was on) i did this, restarted
defender, and clicked update, it would minimize, and after about 20 minutes
it would give me an error stating it timed out.

Any help on this is appreciated.
Thanks

 

[Guest]

Actually, it would be for purposes of consistancy and ease of searching
knowledgebases. It avoids "such and such is broken" and "thingamajig don't
work" both in reference to the same problem. , but neither contains the same
search string.

A good error message wouldn't require SEARCHING!

Anyway, google tells me nothing when I search for 0x8050800d, so your
point doesn't make sense. It's only people asking WTF this code means.

So far, the best info I found was to reinstall WD. In fact, what's
stupid about that is that the error doesn't happen all the time, so why
should I re-install?

The lamest tech support answer is to reinstall the software Anybody
can give you that advice.

It may make it difficult for some people to comprehend, but it lends
infinite clarity to those who need to research the problem.

Geeks like error codes. Humans like human-readable messages that don't
require us to be geeks and look it up in the Fortran manual... I thought
Windows was all about having an intuitive interface?

What's intuitive about 0x8050800d??? It's a geek code...

 

[Guest]

I am only posting here because i couldn't post a new topic/thread.
I recently installed windows defendr beta 2 (After finalll figuring out how
to get GDI working) But i have problems updating, ti said i had not updated
in 259 days, the help file said to enter some commands into run (to clear the
old signature and to make sure autoupdate was on) i did this, restarted
defender, and clicked update, it would minimize, and after about 20 minutes
it would give me an error stating it timed out.

Any help on this is appreciated.
Thanks

It's a shot in the dark, but perhaps the update is being blocked by a
firewall (hardware/software). Do you run anything other than Windows
firewall (zonealarm, etc)?

 

[Bill Sanderson MVP]

http://support.microsoft.com/kb/918355

SpamFighter's certainly hit on one possibility. Defender updates either via
AutoUpdate, or via Windows or Microsoft Update. So--you need to be able to
have those mechanisms work from your machine.

If you have had the problem only in the last 48 hours or so, I'd try
again--there have been some issues beyond your control that should be fixed
now.

 

[Guest]

I'm a pseudo-geek. I have not cranked code for many years. I guess that
makes me "human" again. ;-)

Yes, I cut my teeth on Fortran, and even played with a few million lines of
Cobol. Both date me. I also cranked a variety of assemblers (for speed and
compactness). Bloatware begets intuitive erro codes, I suppose.

How 'bout this for an intuitive error message that will not lead to more
bloatware: "IT'S BROKEN! CALL A GEEK!" Is that any more insightful? ;-)

Don't get me wrong, I get frustrated when an error code fails to properly
identify a problem or its solution to whatever is ailing the system. I just
look a bit harder than the "average" person. Call it self-reliance.

I would *NEVER* expect Google to provide the best answers to Microsoft
problem, however. Next time please try searching Microsoft.com for an
answer. It may not always work; but whenever it doesn't, you can take a
modest amount of comfort in being a pioneer. ;-)