A2630 memory

[RMorewood]

Hello all,

A question about the A2630 memory:

Does it HAVE to be located in the auto-config space?
There is a jumper to disable the auto-configuration
of the memory.  Can this memory (possibly with some
hardware modification) be mounted outside the auto-
config space?  I need that 4 Megs for my new video card!

A2000;A2091+2Meg;A2630+4Meg;XSurf+Subway;A2386+IO+SVGA+Sound/modem
hoping to repair the DKB2632 and add the Cybervision 64.

Regards,

Robert Morewood.

[RMorewood]

Hi Iggy,

The video card is a Cybervision 64/3D, which according to the manual requires 4Meg of auto-config space in which to put its own memory.  (That's on Zorro-II.  Zorro-III it grabs 256Megs.)

Other strangeness:  With the A2630 memory disabled, I plugged the DKB2632 back in, which had tested fairly throughly as "dead" last week. (On my system - I don't have a second A2630 to check it on.)  It seems to work perfectly?  Even when I re-enable the A2630 memory.

Right now my main problem is that the system is just continuously reboots when I attempt to start it normally.  It might have to do with SetPatch.   With SetPatch commented out of the Startup-Sequence it will boot, but a bunch of stuff (like Prefs and AmiDock) doesn't work.  My latest experiment:  boot without startup-sequence and run SetPatch - on reboot, again reboot without startup-sequence and run SetPatch.  Then run s:startup-sequence.  The system seems to be working properly.  But is it repeatable?  Why would SetPatch work from a command line and not from the  Startup-Sequence?  However, it SEEMS that I need to run SetPatch BEFORE running the rest of the startup-sequence
else it just reboots again the second time?

Puzzled and confused,

Robert Morewood

[RMorewood]

Hi Iggy,

The A2630 memory sits in Zorro II memory space (so as to be accessible to other ZII devices for DMA).  It definitely collides with the CV3D.  With everything enabled, the early boot screen shows some cards as "not working".  When the A2630 memory is disables, or the CV3D is pulled, everything shows as "working".  

There is a jumper to disable auto-config of the A2630 memory, but it appears to completely disable the memory rather than just moving it out of the auto-config space.  It would be nice to confirm that - are there schematics anywhere?

However, there is really no problem if the DKB2632 keeps working.  100+Meg on an Amiga is like infinity.  I just wish knew what was wrong before - was it the DKB or the A2630, or something else?

Regards,

Robert Morewood