Path: chuka.playstation.co.uk!news From: Nick Slaven Newsgroups: scee.yaroze.freetalk.english Subject: Interesting memory card fault Date: Tue, 09 Jun 1998 01:27:21 +0100 Organization: PlayStation Net Yaroze (SCEE) Lines: 32 Message-ID: <357C8169.9A5E5C0A@compuserve.com> NNTP-Posting-Host: ld37-059.lon.compuserve.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.04 [en] (Win95; I) I had something unusual happen on my playstation. One of my memory cards started to malfunction, unfortunatley it was one with all my Gran Turismo data on it :(, fortunately I managed to copy it before it went completely bertie :). Anyway the malfunction was weird, as the memory card seemed to completely cock up the controller readings, ie when switching on the playstation without a disk in it, it would keep flicking from the memory/cd selection screen to the memory card managment screen and back again as if the X were being tapped continually. This has got me thinking that the memory cards and controllers are all linked by one serial address and data bus, having now pulled apart my memory card, this appears to be true. This got me thinking about my dual shock pad, & how to get it to wobble, no I havent, but during experimentation with it I have noticed that the address returned for port 1 always points to physical memory location 0x8004EAEC, and port 2 always points to 0x8004EB10, this is slap bang in the middle of the system area. Does anyone know if these ports are memory mapped, or does the OS just stick the data at those addresses? This is probably no big deal, but these addresses are 36 bytes apart rather than 34 bytes as implied by p104 of the yellow book. So the final question is what do the extra 2 bytes do & will they make the multitap work, as they didn't make the shock pad wobble (admitedly I didn't try writing all 65535 combinations), or are they just padding? Nick S. -- http://www.netyaroze-europe.com/~nslaven/ I'm gonna update it soon honest!