Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!csc.anu.oz.au!myb100 From: myb100@csc.anu.oz.au Newsgroups: comp.sys.amiga.tech Subject: Hardware problem in Software ?? Message-ID: <1990Dec4.183634.3676@csc.anu.oz.au> Date: 4 Dec 90 08:36:34 GMT Organization: Computer Services, Australian National University Lines: 36 Hi I'm not sure where this belongs (even with the new CSA split-to-be :-) ) but anyway: I have a problem that recurs about once in every 100 or so reboots (My A2000 lives in a high-risk-of-lightning area :-( ) Amyway, sometimes on boot-up, my 'm' and 'n' keys don't work. 'Fine' everybody says - 'check your keyboard contacts'. Well, yes, that'd be my reaction too, except for this: There is no way to cheat in software to get the 'n' or 'm' to appear either. I used Snap to pick up a word containing an 'n', and when I put it down, the 'n' was gone !! e.g. I was logged onto our VAX, and tried to 'run login2'. This appeared on the screen as 'run logi2', and that is how the VAX saw it. So I (in a hurry) did a 'dir log*' and snapped the 'login2' that appeared there. When I put the snap'ed text back down, out came 'logi2'. Ugh. This is not a major problem - a reboot usually fixes it. Oh - this happens after cold and warm boots. Any suggestions as to what this could be ? (and how to fix it ? :-) ) [Oh: this is an A2000, 512kAgnus, GVP Hardcard(46M ST)+2M-RAM] Cheers, Markus =============================================================================== Markus Buchhorn /// | This space Mt Stromlo and Siding Spring Observatories, Canberra /// | PMB Weston Ck. P.O. A.C.T. 2611, Australia \\\/// | intentionally markus@mso.anu.oz.au -or- nssdca::psi%mssso::markus \XX/ | left blank ------------------------------------------------------------------------------- Phone donations: AUS-6-249-0280 Flames: alt.dev.null Disclaimer: standard ===============================================================================