Vista Smacked down by headset

Just because of your hardware
Which may not tell us any thing
As far as vista is concerned

And it does blows up in there face
Are they then suckers

That one and of no help to a person who has a problem with vista and wants to now use XP
But cannot find somewhere to by it

It also says that people have choice
When in fact some people may have none

It also ignores the fact that many people do have no choice when is comes to some computers, Microsoft products and what they may have available for that persons needs

It is a stupid statement made be someone who cannot think of anything more intelligent to say

That the staff of microsoft
Aren?t group of Wiz-kids, hackers, crackers and virus writers?
Or are they just the bad ones
Of course the quality of Wiz-kids, hackers, crackers and virus writers is an unknown factor

Any better on its release than XP was on its release
As far as what you are talking about

That makes more unfit for "mission-critical applications"
Cool move that one by MS

Its cheeper than another computer
Just put any os of your choice on as many as you like
Hard drives are also cheaper that computers
Or you may want to try a boot manager
Cost zero those ones but hard drive space may be a problem

Tells us very little

Since the amount of time they may have
Or their skill level
And how much interest they have in the project
There are more

Are all unknown

An astounding conclusion you have no problems with vista
So vista has no problems
So all the people who do are telling lies
Wow fantastic

You are so smart

Another astounding conclusion you have only old hardware problems with vista

So vista has no problems with new hardware
And it shows that vista has no other problems

So all the people who do are telling lies

Wow fantastic an OS that has problems with old hardware
But if XP has no problems what must that say about Vista

Guess that?s not important

Another smart person wow

That if it has problems I guess you said that it does
It shows how good Microsoft?s testing program is not that good
Or is it
An argument can be made that
If it has a problem the testing was not good enough
Also just how may problems should we accept to make it good enough
It also shows how what we expect from software creators is now so much less than what we expect from others
Fantastic we now can expect all software to have problems
Amazing that they are allowed to sell it

Amazing a product that has an acceptable error level

Can make a car that runs on all available petrol
So the car thing was not even close
Also don?t forget about filters
Was the car a bad design because ford forgot to add a filter?

I have seen BSOD cause by hardware
Just Drivers?
No
You forget some hardware has no drivers
What ones
CPU Ram irq

There are lots
I used ram just to show you
Cpu yes had that happen
Irq no pci didn?t solve all of that problem

BSOD is only the os reaction to a problem

Think about this some are MS drivers
If its their drivers they are at fault
That is if there is no problem with the hardware

Saying that MS can't fix this problem
Or is it that
They have no responsibility for how their os works
Or is it this simple
The device should not been enabled until the driver was updated
Good for most hardware issues

If the computer had sound device there would be no problem
Except no sound

But it cannot be said
If Vista disabled the sound device there would be no problem

But it would work unless the hardware had a problem

"[i]CPU Ram irq[/i]"

Memory errors are all the hardware problems that can cause a BSOD. The only reason a CPU can cause a BSOD is because it sits between the OS and for a bunch of operations. The only reason memory errors cause a BSOD is that memory is where the software resides while it's running (and, thus, memory errors translate into software errors).

IRQs, by the way, are not hardware. They're software.

Actual hardware problems never directly cause a BSOD -- though software that interacts with it may have problems, which can then cause a BSOD. The hardware [b]itself[/b] cannot cause a BSOD, however.

Guess those A, B, C, D labels are all wrong
Must also be wrong about
Hardware being the cause of any software process or action
Amazeing that computers work at all
Now where was the on button

Just get it will you
The cause of an action or reaction is still the cause of the result or reaction

No matter how many other actions or reactions may occur in between the original action and end reaction

Simply put cause and affect

My reference to IRQs was hardware IRQs
The faulty piece of hardware caused an unrelated Interrupt request
This happened on the add-on daughter board
But good software would have been able cope

Static discharge can have some unbelievable effects
Not sure if it was the cause in this case

Understanding is bliss

I have had cords which were pulled on 1 to many times and were shorted and it gave Windows a BSOD . . What should and should not occur are two different things . .

MS Windows is so poorly designed in this instance that something that should not might have happened. Stop trying to blame the hardware for the software's inability to deal with things that it should be able to deal with.

A minor power fluctuation might have caused an insufficiently well designed OS to fail in the manner of a BSOD. An actual system failure that is entirely the fault of the hardware, however -- such as a short that interrupts the operation of software by definition of the type of hardware failure -- would not lead to a BSOD because the entire OS would crash, causing the OS to simply disappear or making the system reboot.

Yes, some hardware failures might lead to software failures. No, a consistent BSOD response to a microphone being plugged in that is solved simply by removing the microphone is not a software failure response to a short. Continuing to try to blame a BSOD on a short circuit (do you even know what that means?) as if it is not a result of poor error handling by the OS is asinine, and will be ignored.

Carry on with your life.

(edit: re "nitpick" . . . my whole point in bringing up the fact that a BSOD is a software issue is to point out that a short circuit in the microphone case would not be the primary cause of a BSOD. Only by degrading an integrated circuit or otherwise long-term damaging other hardware would it lead to BSODs, at which point the BSOD response of the OS would not be so obviously linked directly to whether or not the microphone is currently plugged in. Thus, based on the evidence at hand, the BSOD is obviously not something so trite and unimaginative as a "short", a term whose use in this context seems to me to be the result of a lack of technical understanding of the operation of a computer and its operating system. As I've said many times, yes, a short circuit could cause the software to fail to operate properly -- in this case, however, such a failure would take the form of a shutdown or reboot, or potentially some other symptom that hasn't occurred to me, but certainly not a BSOD.)

The hardware was the start of the whole process
The cause of the process
The whole process would not have happen without the hardware

Again cause and effect

Software is only part of the process not the cause of the process
There would have been no process without the hardware when the computer restarted or was already started
Software cannot be anything other than a process, which has a start
The start was the hardware
Other processes that may have been set in place or started cannot be included in the process if they are not part of the process
BSOD was the end of the process

Simply GET THIS
The start of the whole process was hardware
The middle of the whole process was hardware CONTROLLED by software (the Operating system)
The end of the whole process was the BSOD displayed on hardware
The START, CAUSE, INITIATOR, BEGINNING of the whole process was the hardware

Please don?t answer me if you are so mind-boggling stupid that you cannot grasp such a simple concept is this

AGAIN for the brain dead

CAUSE AND EFFECT
CAUSE AND EFFECT
CAUSE AND EFFECT
CAUSE AND EFFECT
CAUSE AND EFFECT
CAUSE AND EFFECT
CAUSE AND EFFECT
CAUSE AND EFFECT

Good god man wake up

Yes we get the fact that BSOD can be caused by hardware (The processor)CONTROLLED by software
Which may or may not be defective

(Amazing the processor may not be faulty)
(Amazing the processor loaded the software)
(Amazing the RAM contained the software)

The plugging in of the microphone jack was the cause of the software related problem
The defective software only reacted to this
Yes the software was defective but it was not the cause, which was plugging in of the microphone jack a piece of HARDWARE

DO YOU GET IT
HARDWARE
HARDWARE
HARDWARE
HARDWARE
AND JUST IN CASE YOU MISSED IT
HARDWARE

Also short circuit
A path of low resistance bypassing part of a circuit
More HAREWARE

That and the myth that BSOD can be caused by software(Which is untrue) may also be off the point

Your post

https://www.techrepublic.com.com/5208-6230-0.html?forumID=102&threadID=222122&messageID=2233728

States a BSOD is a software issue
Not true as I showed in my posts
It also shows you do not understand Cause and effect

Apply Cause and effect to this post of yours

https://www.techrepublic.com.com/5208-6230-0.html?forumID=102&threadID=222122&messageID=2238384

Software is no more than instructions and information for the CPU
The CPU is part of the process that creates BSOD
It may also be the cause of BSOD when it screws up the software
If it becomes or is degraded (Physical or heat or other damage internal or external don?t care)
Actual hardware is the only thing that can create the BSOD
Software cannot directly cause a BSOD
Cause and effect shows
Actual hardware problems can directly cause a BSOD

These post are the start of your miss understanding and lack of knowledge

You still DO NOT under stand cause and effect

Getting shot by a gun or tranquilizer (the cause)
And ending up in hospital (which is the effect)

The system getting woozy is an effect
Falling over is an effect
The result of weird data getting fed to the system is an effect
The BSOD is an effect

The hardware problem is the cause

How much it affects the system is irrelevant

It shows how clueless you really are when it comes to cause and effect

Like you said
Get the friggin clue yet?

in reading most of these posts (though not all), is the fact thatthe system this supposedly happened on isn't made clear northeactual error message on the blue screen, nor the timing (insert mic, either hardwaresensing or software begins to set-up chat etc, then bsod for ex.) and ifresearch was done on theerror code, etc. for all anyone knowsby reading this thread, itcould be a 966mz compaq w/ 512 ram and a 512 jumper using ready boost, and a minimum drive w/ minimum space. since nothing is really clear here, why would anyone take this seriously, and even if it was both clear and true, does anyone really believe it is actually the fault of the os instead of the driver or any other possibility? i have even tried pulling out a card when the system is running, sometimes get a blue screen, sometimes get a restart, sometimes a lock-up. putting it back never works while it is on. this is one reason a short is a possibility, though slim, or even that the sound card isn't secured properly. the opposite of plug and play, right??! but since the system won't 'load' (read restart here i guess), that is probably not true. i am sticking w/ either the driveris the issue or even the possibility that teamspeak is trying to complete the mic set-up after the crash is why it won't restart. i have spent some time w/ manufacturers support over their vista drivers, and had varying results from "the chipset man. needs to provide that" to 'we know it works so it's your problem' (which obviously may be true), to 'we're not supporting that device in vista' ie my hp scanner which works fine in everything but linux. is any of that the fault of vista?

For agreeing with me
Now please explain it to apotheon
Don?t forget to explain transfer of cause to him as well

He is still clueless
And deaf

My first post to him
Included 3 hardware related faults
CPU Ram IRQ
I also mention some hardware doesn?t have drivers
He then contradicted himself in his reply
Stating that hardware can cause BSOD
Then states
Actual hardware problems never directly cause a BSOD
All to the point of course

Edited to add this

Can you tell me why you keep giving me a process as an example of a result?
But will not accept the process that a hardware fault is the cause of a BSOD

"You forget some hardware has no drivers
What ones
CPU Ram irq"

None of which are microphone jacks, the subject of this thread. You have made some valid, but inapplicable points below. You have done so in an unnecessarily abrasive and inappropriately condescending manner. You're not overwhelming any of us with your knowledge. You are mainly displaying your own difficulty understanding or recognizing relevance in the present context.

Would appear to be your grasp of the facts
It would also appear to be the fact that, you never misunderstood me

What no better answer?

Good to see that you don?t get condescending when losing an argument

Well answer this

Is the screen of death, caused by a process?

Microphones tend to be amplified, so voltage differences are larger than with other audio hardware. Good software should be written anticipating this well-known fact of microphone hardware, and handling it gracefully. Also, an operating system should not allow an audio process to take down the entire system.

Since you are now reading these posts
Can you explain the behaviour of apotheon

Why he would make the statement

A BSOD is a software issue, not a hardware issue

Mystifies me why he would use a flawed statement like that
When the plugging in of microphone jack was clearly the cause of the BSOD
I don?t at all think he was acting superior or condescending in that
Or any other similar statements to other people making the same type of comment
?Hardware was the cause of the BSOD?
He then goes on to make the sooo accurate statement

Voltage drops don't cause BSODs -- they cause things like sudden reboots.

Then wonders why someone questions him on his post
Boy am I surprised by his reply to my post
He contradicts himself with this gem

Memory errors are all the hardware problems that can cause a BSOD

Of course it can only go down hill from there
More stunning was his next statement

The only reason a CPU can cause a BSOD is because it sits between the OS and for a bunch of operations.

Wow is it software or hardware
But wait there?s more

The only reason memory errors cause a BSOD is that memory is where the software resides while it's running (and, thus, memory errors translate into software errors).

So easy to understand all of those statements
His conduct from that point is of course very professional
Should have given up then
But I got pulled into the garbage
(Sorry I was tired)
Any attempts to explain are only seen by blind eyes or deaf ears (you choose)

By now the smoke will be billowing out of his ears
So I give up
You must be right then apotheon
Because I was the one to give in

Anyone out there still wonder why there are so many fights on TR

If you do just ask the experts
I am sure they will give you an answer that is precise, short and to the point
Don?t worry all the extra unwanted stuff is normal
If you still don?t understand
Don?t worry that?s normal on TR

Absolutely thanks for listening

Some it was difficult to understand
Getting tired

But I got some of it
Did enjoy the deaf ears part

I would like to point out
Apart from my explanation of a short circuit
I did not used the term short or short circuit as part of the discussion

Funny don?t remember TheTechmall using it
Just you guys
My first post was directed at apotheon not TheTechmall

One mistake I will correct
An IRQ is a transition in an electrical circuit not a software process
Still a hardware generated interrupt request

By the way a person falling over
Would be because their muscles relaxed and the effect of gravity
Not the bullet or getting woozy
Being carried through the hospital doors on a stretcher will put the person in hospital not the gunshot wound
Unless he was just outside the doors and fell though when shot

post traumatic stress disorder, psychological problems
So we psychoanalyse the BSOD or hardware is that it?

Primary cause = voltage out of bounds
Not my choice of primary cause
That and result are your choices

Voltage spike or voltage drop pick one please

All of these were such a big help in understanding your points

Thanks Absolutely and apotheon I see my mistake

It was reading your posts

Some of them were good laughs
Some ???????????

well i've had all sort of hiccups & blue screen of death etc.I have gone back to windows xp & i don't know the new windows has compatibility problems.Vista reminds me of milenium windows.
ta mick