TRexx-II image (above left) used with permission from the Amiga Hardware Database
TRexx-I, II (A4060)
TekMagic 2060 (A2060)
|Home | Downloads | Documentation
Solutions/Help Requests | History | Bugs
Looking For | Links | Users | Contact
Updates (July 3, 2018)
Solutions, Tips and Notes
DEVICE tekscsi2.device DEVICETYPE NSDEVTYPE_TRACKDISK COMMANDS 2-5,9-15,20-21,23,28 IOERRNOCMDfrom Boing Bag #1 does wonders for tekscsi2.device where removables are concerned. Writes to Zip drive no longer freeze the bus when the Zip is asleep, and there's an "Unexpected Error" while the Zip gets up to speed. In addition, OS 3.5 provides the ability to boot with the new Fast File System (v45); a normally "foreign" filesystem where the Tekmagics are concerned."
From email@example.com (Ralph Babel) Newsgroups: comp.sys.amiga.hardware Subject: Re: tekmagic 2060 and non-gvp prep s/w Date: 6 Nov 1999 00:00 UT Greg Kimnach asked: > is there a guru rom for the tekmagic card? Yes, there is. (Actually, it's _two_ ROMs for the TekMagic card.) I ported the omniscsi.device to the NCR53xxx (also used on the A4091) when I wrote the 68060.library for the TekMagic card in '95. Two years ago, GVP-m voiced their interest in the NCR/Symbios Guru ROM, but I haven't heard from them since, and there simply aren't enough TekMagic cards out there to make it a worthwhile product for Ossowski's Schatztruhe to sell and support.
Apparently the tekscsi2.device/gvpscsi2.device is broken like many others and does not support large drives; i.e. it wraps.
Note: if you're able to solve any of these problems, please let me know so I can post the solution here.
I still haven't solved my GVP-4060 problem. I thought that maybe my SIMMs could be getting too worn, so I went out and bought a new 32 MB EDO SIMM (double sided). I put this in slot CN1, with the other slots empty, and set jumpers JR5 and JR6 to ON. Result: Only the first 16 MB are recognised. The computer knows there *should* be memory from 0x09000000 to 0x09ffffff, but it finds out there isn't (so it thinks the card was lying to it). I know this because the program KSRemap fails, yet "Avail Flush" reports 16 MB Fast memory. If I set JR6 to OFF, KSRemap succeeds, because it never tries to access the second 16 MB memory. What I wonder is, how does the card recognise *half a SIMM*? Shouldn't it either recognise the whole SIMM or not recognise it at all? Maybe it's because it's EDO? Would getting an FPM SIMM instead solve this problem?Joona I Palaste (4060 user) asks for help (original request):
I recently bought Sean Courtney's GVP 4060 card. While the 68060 processor itself is working fine, I seem to have problems with one of my SIMMs. I have 32MB of FAST RAM, in the form of two 16MB SIMMs (both single-sided, with eight chips). During the installation of the GVP 4060, I accidentally broke one of the plastic "poles" holding the SIMM in place in slot CN2 of the GVP 4060. Now when I try to put the SIMMs in slots CN1 and CN2, only 16MB of FAST RAM is recognised.
I think the problem is that the SIMM in slot CN2 is not being recognised. This is because I tried removing the SIMM in slot CN2 entirely, and it did not decrease the amount of detected FAST RAM.
About my GVP setup:
I have jumper JR5 (4MB or 16MB SIMMs?) set to ON (16MB SIMMs), and jumper JR6 (single-sided or double-sided?) set to OFF (single-sided). The manual of the GVP 4060 mentions the start addresses of the memory blocks as follows:
CN1 CN2 CN3 CN4 JR5 off, JR6 off 0x08000000 0x08400000 0x08800000 0x08c00000 JR5 off, JR6 on 0x08000000 0x08800000 0x09000000 0x09800000 JR5 on, JR6 off 0x08000000 0x09000000 0x0a000000 0x0b000000 JR5 on, JR6 on 0x08000000 0x0a000000 0x0c000000 0x0e000000
As I stated above, my configuration is JR5 on, JR6 off (so it's the third row). SysInfo reports finding 16MB of FAST RAM from 0x08000000 to 0x08ffffff, so I suspect it just finds the SIMM in slot CN1.
Is the GVP 4060 capable of using SIMMs in non-adjacent slots? For example, if I have one SIMM in CN1, another in CN3, and slots CN2 and CN4 empty, will it work?
Is there any way I could test the second SIMM, other than replacing the first SIMM with it (which I don't want to do as it may break the first SIMM as well?)