KVR Audio

t3toooo · Post by **t3toooo** » Wed May 23, 2012 3:28 am

yes, the term "offering a solution" might be confusing but at least microsoft asks for your permission to send it unlike that apple.
well,at least we are all using the same chinese components which must not be a bad thing,the only tiny difference is my pc is a bit faster than a macc and it always will be.

hibidy · Post by **hibidy** » Wed May 23, 2012 3:55 am

CapnLockheed wrote:Which is why you should use a Mac...because problems never occur...BUT...if they did you your machine would offer you a solution...in a soothing female voice...while it made you a latte.

Don't you read the KVR rules????????????????????????????????????????????????????

Now it's just time for someone to come in and mention that sodding host

careyletendre · Post by **careyletendre** » Wed May 23, 2012 4:19 am

hibidy wrote:Now it's just time for someone to come in and mention that sodding host

ouroboros · Post by **ouroboros** » Wed May 23, 2012 4:24 am

I leave a note every time it happens.
I dutifully submit my data, in the hopes that somewhere on the other end of the line there sits an earnest programmer who spots a pattern, a cries out, " Will you look at that! I think I know what's happening here," and days later, my computer fixes itself.
I generally am loathe to admit it, but deep down, hope springs eternal

aciddose · Post by **aciddose** » Wed May 23, 2012 4:30 am

i'm not sure about win 7/8. you should be able to disable the "report errors" service/option and the dialog should return to it's old format without the bogus "finding a solution" message. there is a lot less delay when an app crashes because the whole state capture never happens for the report which is never made ready to be sent. so app crashes, you hit "ok", instant.

the pop-up is actually quite annoying sometimes. it would be better if you have debugging disabled to just flash a message in the corner of the screen. the error itself is logged in the system log anyway.

kv331 · Post by **kv331** » Wed May 23, 2012 4:46 am

One of the things I really like about MacOSX is it gives you a detailed report when a crash occurs. So much detailed that you get the call stack information so you know exactly where the program crashes!

So far, this has not been the case for Windows

hibidy · Post by **hibidy** » Wed May 23, 2012 4:49 am

Yeah, but everyone is so busy celebrating that they are on mac, they carefully and conveniently ignore any info on any "actual" issues

aciddose · Post by **aciddose** » Wed May 23, 2012 4:56 am

that is also available for windows, it just isn't part of standard package.

if you want callstack analysis, you need to configure it.

why isn't this available by default in windows? that's because windows was never intended to be a programmer's os. unix/bsd was.

besides the callstack is pretty useless if you don't get any function names, even to a programmer. what would the purpose be of having ms-word barf out a huge list of xml parsing functions to the user?

that's some of the data sent by the error reporting service, actually.

Panphobia · Post by **Panphobia** » Wed May 23, 2012 5:18 am

kv331 wrote:One of the things I really like about MacOSX is it gives you a detailed report when a crash occurs. So much detailed that you get the call stack information so you know exactly where the program crashes!

So far, this has not been the case for Windows

Windows has a very detailed crash log. It usually lists some generic reason for the crash, and then follows with an unintelligible log of numbers. You then get to go to your nearest techie forum and post it there in the hopes that some ultra-bored video-game hating programmer is just sitting in front of his computer waiting to help (assuming you can get the thing to start up in safe mode, or at the very least beg your wife to log off of facebook for fifteen minutes). oh, and also you need to consult said tech forum just to find the location of the crash log, but that is a whole other adventure.

As for the widows pop up help thingy, yes it actually did fix the problem for me ONCE. Out of how many failures I don't know. It was some miscellaneous component that needed a driver update, some mundane thing that should be minding its own business but is in stead harassing the mouse or whatever.

hibidy · Post by **hibidy** » Wed May 23, 2012 5:23 am

And yet, despite my overly picky tude towards computers.......I've had far less issues with windows (since 98 ) than I did in the 15 months I had a mac

ford442 · Post by **ford442** » Wed May 23, 2012 5:23 am

i have a good one - i had some bad ram - but, xp wasn't using it (above 3.25gb) - upgraded to 7 x64 and got BSODs - tore the computer apart until i ran memtest and finally pinned it down - got new ram - later win 7 says 'would you like me to check for solutions to problems that have not been solved?' i said yes - windows thought really hard and then says 'it looks like your computer may be suffering from a memory related problem. would you like to run memory diagnostics?'.. LOL...

knobs · Post by **knobs** » Wed May 23, 2012 8:44 am

lmao! never, and anyone who says it did is flat out LYING.

Fritze · Post by **Fritze** » Wed May 23, 2012 9:00 am

skitchy wrote:Windows has, in fact, NEVER ONCE 'found a solution to my problem'.

THIS!!! A close second is some stuff in the help section. Micro: "Did this help you? No? Click here..."
And then it suggests me to ask a friend! Woahhhh!!!!

Ingonator · Post by **Ingonator** » Wed May 23, 2012 9:57 am

Recently i had the problem that the WLAN connection of my PC was cut off.
I clicked on the "problem solving" in the right-click menu of the WLAN icon ( in the taskbar) and the WLAN was working again after Windows 7 found it has to reset the WLAN adapter.

Ingo

thecontrolcentre · Post by **thecontrolcentre** » Wed May 23, 2012 10:25 am

skitchy wrote:You know when your VSTi, VST, DAW, sound editor, game, or notepad crashes. A helpful little window pops up. It informs you that 'Windows is checking for a solution to your problem' and it sits there for a while.

No. Never seen it ... I'm on XP if that makes any difference.

Has Windows ever actually FOUND a solution to your problem?