Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!brutus.cs.uiuc.edu!psuvax1!psuvm!ims103 From: IMS103@psuvm.psu.edu (Ian Matthew Smith) Newsgroups: comp.sys.amiga Subject: Re: Turbo and the 2630 Message-ID: <90068.135108IMS103@psuvm.psu.edu> Date: 9 Mar 90 18:51:07 GMT References: <9003090636.AA11199@gaudi.CSUFresno.EDU> <25F7DA71.9670@orion.oac.uci.edu> Organization: Penn State University Lines: 23 In article <25F7DA71.9670@orion.oac.uci.edu>, eaeu079@orion.oac.uci.edu (Jason Goldberg) says: > >In article <9003090636.AA11199@gaudi.CSUFresno.EDU> erick@GAUDI.CSUFRESNO.EDU >(Eric Keisler) writes: >>[-----------------------------------------------------------------------] >>Well, I've been using Turbo Silver 3.0 *and* SA4D on my GVP3001 equipped >>A2000 without a hitch for months. Must be a problem with the 2630 or >>the 2091... > >BTW, I have herd completely unconfirmed rumors that the problem is a simple >as something in the A2091 code writing to Mem Location 0. I don't know if >this is the problem but after booting up I did run a test program and >sure enough Mem location 0 was nonzero. > >-Jason- This is a problem with a few programs. Notably JRComm. I wrote a small assembly program that displays location zero, then either clears or sets it depending on the command line argument. It is only about 400 butes so I will UUENCODE it tonight ant post it. Ian Smith