Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!bunker!hcap!hnews!369!8!Doug.Geoffray From: Doug.Geoffray@f8.n369.z1.fidonet.org (Doug Geoffray) Newsgroups: misc.handicap Subject: who's to blame? hardware or software? Message-ID: <13431@bunker.UUCP> Date: 12 Aug 90 03:59:01 GMT Sender: news@bunker.UUCP Reply-To: Doug.Geoffray@f8.n369.z1.fidonet.org Distribution: misc Organization: FidoNet node 1:369/8 - The Catwalk BBS, Davie FL Lines: 38 Approved: wtm@bunker.UUCP Index Number: 9756 [This is from the Blink Talk Conference] BK> Doug, I suspect that you sent that message in jest or tongue in BK> cheek. You know, the one about it always being a hardware BK> problem. However, frankly, that's why I haven't gotten my BK> courage up to ask the question, as I'm sure that's what I'll be BK> told. What do you think? Bill, Unfortunatly, this problem has been around a long time. It is extreemly difficult at times to tell the difference between a bug in the software or a hardware problem. If someone comes to me and says they are having a problem with our stuff that I have never hear of I try and duplicate it on my machine. If I can duplicate it then of course it is the software. However, just because I may not be able to doesn't mean it is the hardware. Therefore I ask them what is in their machine. Both hardware and software. Then maybe try removing each piece until something different happens. If that still does not help I usually punt and dig in the code of the program and try and figure out what could possible cause the problem. Even when I know that it is a hardware problem I alway hate to tell the user. It sounds like I am passing the buck. I am afraid there is no good answer. You may want to try Vocal-Eyes and see if you are having the same problems. If you are not then it is probably Flipper. Well, I am beginning to talk in circles. I wish you luck. Regards, Doug -- Uucp: ..!{decvax,oliveb}!bunker!hcap!hnews!369!8!Doug.Geoffray Internet: Doug.Geoffray@f8.n369.z1.fidonet.org