Hardware compatibility: Difference between revisions
No edit summary |
No edit summary |
||
| Line 23: | Line 23: | ||
Speeding up your system bus (i.e. beyond the standard 8 or 16Mhz) might result in pixel errors. | Speeding up your system bus (i.e. beyond the standard 8 or 16Mhz) might result in pixel errors. | ||
An accelerator known for doing this is the '''DSTB1'''. | * An accelerator known for doing this is the '''DSTB1'''. | ||
* Overclocked TTs (e.g. 48Mhz) might show artefacts on the screen. It was reported, that disabling the cache might help in this case. | |||
=== Known incompatibilities === | |||
* OverScan ST is incompatible with the ATW800/2 | |||
To be continued... | To be continued... | ||
Latest revision as of 14:06, 26 March 2026
Hardware successfully tested with the ATW800/2
As for now we positively tested the ATW800/2 against these accelerators:
- AdSpeed
- Turbo25
- PAK68
- PAK68/2
- PAK030 (Set your ATW800/2 ROM to TOS1.04)
- TerribleFire 536
- SpeedyTT
Also those devices seem to work OK up to now (more in-depth testing needed):
- Lightning ST
- Cloudy(-Storm) ST (Remove your ATW800/2's ROM chips)
- Thunder TT & Storm TT
- Magnum ST (Most alternate RAM solution should work)
- c´t IDE Interface (needs patched GALs available in the ATW800/2 fileshare)
Known issues
Speeding up your system bus (i.e. beyond the standard 8 or 16Mhz) might result in pixel errors.
- An accelerator known for doing this is the DSTB1.
- Overclocked TTs (e.g. 48Mhz) might show artefacts on the screen. It was reported, that disabling the cache might help in this case.
Known incompatibilities
- OverScan ST is incompatible with the ATW800/2
To be continued...