sorry, but thats wrong. as per my above comment, I work for a helldesk with a certain set of hardware configurations. We know fairly fast if a system is having a hardware issue, because the engineers pay attention to all the warranty calls, and if 35% of the people with model x_shiny_270 call in, then they check for a problem (random numbers here, ionno if its 35%). Win XP is still *perfectly* capable of BSOD'ing on its own, try searching microsoft.com for some errors like 0x000000ED, off the top of my head: Hard drive problem, or, windows just managed to "oops" corupt an important file. If you know what your doing, sure, the recovery console (gag) can be used to fix some of those. I am so glad, however, to see a real CLI being created, My job will be so much easier. My only hope is that it be able to run when windows GUI wont, when the dreaded aforementioned BSOD has hosed it...
Please. I work in technical support (yes, I am one of the helldesk) for a large computer manufacturer: it rhymes with well. I even support corporate customers, not jim-bob and his "that thar modem thing". I consider it a lucky day to only see 2 or so BSOD's, and at an average call time ~ half an hour, thats a significant portion of my calls in a 10 hour day. The people that havent seen a BSOD on thier little quake III machine in the corner for the past month and forget all about them, make me angry.
Well, it is unfortunate, but, in the real world, guess what? People do use excel. plenty of people work in some sort of environment with . To those people, sometimes the only tool you have, is excel. I know, Im one of them, Ive had to make API calls from VBA in excel, to make an app for users. What Id like to see is someone make a C++ compiler in excel, cause then I can use it, and claim it isnt a "program" its a "spreadsheet" and then use the output, because we are allowed self made programs:p
Slashdot Mirror
sorry, but thats wrong. as per my above comment, I work for a helldesk with a certain set of hardware configurations. We know fairly fast if a system is having a hardware issue, because the engineers pay attention to all the warranty calls, and if 35% of the people with model x_shiny_270 call in, then they check for a problem (random numbers here, ionno if its 35%). Win XP is still *perfectly* capable of BSOD'ing on its own, try searching microsoft.com for some errors like 0x000000ED, off the top of my head: Hard drive problem, or, windows just managed to "oops" corupt an important file. If you know what your doing, sure, the recovery console (gag) can be used to fix some of those. I am so glad, however, to see a real CLI being created, My job will be so much easier. My only hope is that it be able to run when windows GUI wont, when the dreaded aforementioned BSOD has hosed it...
Please. I work in technical support (yes, I am one of the helldesk) for a large computer manufacturer: it rhymes with well. I even support corporate customers, not jim-bob and his "that thar modem thing". I consider it a lucky day to only see 2 or so BSOD's, and at an average call time ~ half an hour, thats a significant portion of my calls in a 10 hour day. The people that havent seen a BSOD on thier little quake III machine in the corner for the past month and forget all about them, make me angry.
Well, it is unfortunate, but, in the real world, guess what? People do use excel. plenty of people work in some sort of environment with . To those people, sometimes the only tool you have, is excel. I know, Im one of them, Ive had to make API calls from VBA in excel, to make an app for users. What Id like to see is someone make a C++ compiler in excel, cause then I can use it, and claim it isnt a "program" its a "spreadsheet" and then use the output, because we are allowed self made programs :p