Re: 14MHz 65816??

[tony@ccn.cs.dal.ca (Tony Cianfaglione)]

Nathan Mates (nathan@visi.com) wrote:
:    You cannot drop a faster 65816 into the motherboard and expect it
: to run any faster-- the timing signals on the motherboard are locked
: at the 2.8Mhz speed, and changing that would require a motherboard
: redesign. Running a chip slower than its rated speed is fine-- it will
: just run at the slower speed. (Well, up to a point... if you ran a
: 658116 at maybe 1/32 or 1/64 of its rated speed, it'd probably start
: having a bad day)

   That's too bad because it would have been great to simply switch chips.

:    That is why you need the accelerator cards-- a place to run a
: faster 65816, an oscillator for the faster 65816, and the logic needed
: to interface a fast 65816 to the GS motherboard at 2.8Mhz. 

   I use a Twanswarp GS.  I have 2, one with the tin can set at 7, the 
other with an interchangeable socket running at 13.75.  

: >   They keep crashing in the middle of vital projects and I'm forced to 
: >disable the cards and run at the native speed.

:    What speeds? Some people say that the bleeding edge speeds (>12Mhz
: or so) can be flakey, but reducing the speed one notch on the ZipGS
: control panel made it run fine. My Zip 9/32 is rock solid (the only
: problem with it is that the cache access LED has never worked, but as
: I keep the case on my GS, I don't care about that). Also, the default
: ZIP CDev is buggy as hell, and should not be used. The FTA's ZIP
: CDA is fine as long as you don't try and run it under ProDOS 8.

   Both cards give me grief, especially the socket model.  I've tried 
using a 28, 50 and a 55 oscillator, with no great success.  Even with a 
System Saver, the system overheats within a half-hour and hangs.  I have 
to cool everything down for about 8 hours before using it again.

:    Have you also considered that it's a software crash caused by the
: loading of the inits/das to control them?  In my experience, just
: adding removing, or changing the load order of things can cause memory
: trashing caused by another program to suddenly step on 'critical'
: areas of ram or more 'useless' areas. 

   I only use GSCII+ and no cdas/ndas at all except for the TWGS cda 
which autoloads with the card.  I don't have to run any software.  I'm 
just copying files from 3.5 to the HD and back and 'doink' (love that 
sound - NOT).  I have a Fingerprint GSi, Rev 2 in Slot 1, a Lightning 
Scanner in Slot 2, Slot 3 empty, TWGS in Slot 4, Slot 5 empty, RAMFast 
SCSI card, rev D in Slot 6 (running a Quantum 80 meg HD) and a Vulcan 20 
meg HD in Slot 7.  I have 6 meg RAM in a GSRam + card. 

   Even pulling everything except the TWGS and the Vulcan doesn't help.  
Still the overheating problem.  I have 3 GSs and they all react the same, 
and both TWGS cards have the same experience which is why I don't care 
for accelerators.

Tony