Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!sol.ctr.columbia.edu!ira.uka.de!sun.rhrk.uni-kl.de!seimet From: seimet@rhrk.uni-kl.de (Uwe Seimet [Chemie]) Newsgroups: comp.sys.atari.st Subject: Re: Bug in TT hardware? Message-ID: <1991May29.064319.14892@rhrk.uni-kl.de> Date: 29 May 91 06:43:19 GMT Article-I.D.: rhrk.1991May29.064319.14892 References: <1991May27.101719.2923@rhrk.uni-kl.de> <1991May28.130252.3634@lsuc.on.ca> Distribution: eunet Organization: University of Kaiserslautern, Germany Lines: 27 jimomura@lsuc.on.ca (Jim Omura) writes on my article <1991May27.101719.2923@rhrk.uni-kl.de> seimet@rhrk.uni-kl.de: > It sounds like the 68030 has "pre-fetch" active. You can >shut this off "manually". Check a 68030 instruction list. The >only problem might be that the "pre-fetch" might be built into >the driver and not over-rideable without writing your own driver. I don't think the 68030 is responsible for the bus error. Remember that the error is reported by the scsi controller. During dma transfer the 68030 is not active. I do use my own driver but there it is the same problem with the original atari driver. BTW, in AHDI 4.02 you still find an old error: After initialising the driver exits with PTERMRES. Instead of specifying its length to stay resident it uses its start adress as parameter for PTERMRES. The effect: after running AHDI several times you run out of memory. The first time it is started you loose about 64KBytes of RAM. This means that by using AHDI you have always less memory than with other drivers (e.g. HDDRIVER). ******************************************************** * Uwe Seimet * * seimet@sun.rhrk.uni-kl.de * *------------------------------------------------------* * I hate this machine, I wish that they would sell it. * * It doesn't what I want but only what I tell it. * * (Programmer's lament) * ********************************************************