This post is about my trials with a 68010, PiStorm, 2xTerribleFire-536 (TF536) and a 68030-TK2 running on my PAL Amiga 1000 (no piggyback).
Disclaimer: There is no sponsorship or payment in kind, and all comments are my own experience / opinions unless stated otherwise. I am a private individual member of the public, I am not a business, nor am I representing any business. This blog should not be taken or used as advice or instruction as I am not an engineer or qualified in the field of electronic repair. Replicate at your own risk. I have destroyed 1 x accelerator, 2 x GOTEK drives, and 1 x Amiga 1000 (at time of writing) in my (mis)adventures so far 😅
--------------------------------------------------------------------------------------------------------------------------------
Consider if you really need an upgrade. Nearly all Amiga games were written for the 68000 processor and that's where you maximise your compatibility and fun. Expect problems if you upgrade anything!
If you must upgrade, consider the 68010 instead. The speedup is barely noticeable, but it's nice to know it has just a little more magic in the box, and using a virtual floppy device like a GOTEK provides further compatibility for all 680x0. Virtual floppy images are often 'fixed' (hacked) - look for AGA Fixed versions to solve many remaining compatibility problems in my experience. I tried this and still moved back to the 68000 for a while as the 9-Fingers and State-of-Art demos would not work for me on an accelerated Amiga.
Today I am very happy with my 68030-TK2 and 68882 FPU, running stable @ 40MHz CPU / 40MHz FPU, and nearly everything I want run (only 9-Fingers demo won't work <sniff> ). State-Of-The-Art demo works with the WHDLoad version for 512k ChipRAM Amigas, but would fail if I overclocked my CPU to 56MHz.
For more info upgrading with the 68010 (the easiest and most trouble free), check Robert Davis's page here.
"Many respondents to news postings caution potention users of the 68010 to get the old program DECIGEL which will fix a problem with one instruction on the 68000 which is not handled in the same manner on the 68010. They tell everyone that some of their software will crash without decigel.
That is garbage.
The particular MOVE instruction which messes up on the 68010 but not on the 68000 will also crash any computer using a 68020, 68030, 68040 or 68060 cpu. And all programmers have been aware of that instruction and its problems since the mid-1980s. More specifically, writers of compilers have made sure their code generating software did not use that instruction as it was defined on the 68000. It has been literally years since any new software for the Amiga suffered from the MOVE SR,Destination bug in the 68000."
--------------------------------------------------------------------------------------------------------------------------------
This post covers my experience with a PiStorm, a buffered and unbuffered TerribleFire-536 and a 68030-TK2 running on my PAL Amiga 1000. The first thing to note is that yes they will work in an Amiga 1000, but there are compromises to be made. If you just want to play Amiga games, or play like it's 1986, then don't bother with an accelerator - it won't do anything except likley cause some games/demos to not work.
The extra memory won't do anything that the Parceiro does not already do, and I have never ran out of Fast memory with the 8Mb the Parceiro gives me.
So how does a 32-Bit CPU work in a 16Bit machine? The 68030 has two legs/pins that provide/enable configurable bus speeds on the mainboard, which is how a 32Bit CPU can still work with our smaller 68000 bus. I found the s100 site helpful in understanding what Motorola were providing here.
On a stock 68000@7MHz I had discovered that OS3.2 really slows down apps and WHDLoad games.
One example, the startup music in Defender of the Crown becomes morbidly slow when run using WHDLoad on OS3.2. Because of these slow downs and to continue my playing-around with coding, I was seeking a speed boost. Using the ‘030, the WHDLoad version of Defender of The Crown does play at the right speed and OS3.2 is much snappier. Of course, everything does play at the right speed on OS1.3 even with the ‘010, but is noticeably slower, even with the ‘010 on OS3.2
The vast majority of games will not benefit from a 68030, in fact, they may not work at all!
I found re-capping The Amiga 1000 power supply AND Mainboard (and Daughterboard) was essential to getting an '030 accelerator to remain stable. If you're not ready to recap, stick with the 68000 or 68010. See my recapping blog entry for the recap fun.
I agree with both David Dunklee (Pareceiro inventor) and Stephen Leary (TerribleFire inventor), play the games that were designed to be played on your Amiga. Buying an accelerator just to run Gloom/Doom/Quake etc on your Amiga is a bit pointless - the best experience will always be the machine it was designed for. One exception I found was with Dune 2 - it runs, but just was not designed for the Amiga and it's frustrating to play on 68000 platform without an accelerator.
The benefits I have gained from a 68030 include:
- Workbench zings and is noticeably snappier (Don't forget to install MuTools)
- BBS screens are lightning-fast using NComm compared to running on a 68010 which is a little slow
- Frontier runs silky smooth, although I'm yet to do more than watch the intro
- FractInt draws pretty fractals in a few seconds and really benefits from the FPU
- I gain internet access (slow, but it works)
- I get to try some new development toys, being the expanded instruction set of the '030 and the FPU
- Multitasking certainly works better
What I have lost with using the accelerator:
- I can't use my Paceiro for anything more than KickROMs. I lose the clock, the memory, and the Hard drive (SD Card).
- I had to remove my Floppy Drive (The CF Card sticks out the floppy drive slot now)
- Some games that might benefit from a speed boost (i.e. Civilisation), might be better off with emulating an Amiga (Amikit is the best) if you want speed and compatibility and more Chip RAM!
- I need to make a compromise for the CF Card:
- 40-pin or 44pin IDE cable hanging out my case;
- cut a hole in the case for the CF-Card (no way!);
- the CF-Card remains hidden in the case and unaccessible for updating without some effort;
- OR (the choice I made) was to remove my floppy drive and mount the CF-Card Adapter behind the floppy slot with the help of hot glue, enabling the CF-Card to be easily removable for backups.
- I can't use my metal RF shield anymore, as the accelerator will sit too high, but I can put the plastic lid back on and that works fine. This includes the floppy drive RF Shield and even the floppy drive if using a relocator. RF Shields will have to be removed to fit the accelerator card in.
 |
| The accelerator board is also too wide to fit inside the floppy RF Shield |
 |
| The floppy drive RF Shield must be removed to fit an accelerator card |
BEFORE YOU START: PiStorm eliminates the need for a KickStart disk (woohoo!), however, the other '030 accelerators require that you have modded your Amiga 1000 to have a Kickstart ROM in hardware and no longer need the kickstart disk. You can do this with a Parceiro, or maybe you could use a kickstart mod like the SYANNE-514 which Cliff mentions in the comments below (I have not used the SYANNE so unable to confirm if this works with the accelerators).
None of the '030 accelerators will work with a Kickstart disk, and only the Parceiro still allows fall-back to a kickstart disk. However, needing a kickstart disk to boot is not a feature I miss or have found any use for.
In addition, re-capping (Both the power-supply and the Amiga) is a must in my experience to meet the stable power requirements for acceleration. Even a few milliVolts I found was enough to destabilise my Amiga 1000 and cause endless address and data bus errors (crashes and freezes galore). You can read about my Re-Capping experience here. Examples of unstable power issues I saw were:
- After a few seconds, I was 'enjoying' Guru/Software errors:
- 80000004 ( Illegal instruction),
- 80000008(Privilege violation),
- and once an 80000000B (OpCode 1111)
- Killing Game Show freezes up about 60 seconds into the game, even using the original IPF 'disks'
- Dune2 reboots anywhere from loading the intro, to mid-game.
- Turrican II, Xenon II, and IK+ had slow intro sound problems with the PiStorm
All these crashes occurred very soon after, or while booting from the CF Card. Even trusted tools like Amiga Analyser or the DiagROM would hang as soon as it loaded with any of the new accelerator cards installed before I had recapped my Amiga 1000.
A search across the net also pointed at a possible CF-Card MaxTransfer issue. I had removed the CF-Card, to eliminate the possibility of a MaxTransfer type issues while I was testing, but still saw the same crashes mentioned above.
Lots of posts advise that CF-Cards need to set a MaxTransfer Rate of 0x1FE00 or 0xFE00, there is an article here that makes some sense https://eab.abime.net/showthread.php?t=45491.
I did have to set my MaxTransferRate to 0xFE00 before I had a stable Amiga booting from a CF Card and running an '030 reliably (for over a month now with daily use). 0x1FE00 did not work reliably for me, I still saw damaging read/write errors.
I use the Parceiro card to provide my KickROM and I'm really happy with it. I also use a custom modified Parceiro card that provides Kickstart ROM only (no RTC, no RAM, no SD Card etc, just Kickstart ROM). Contact David Dunklee if you need a KickROM-Only Parceiro, or use another hardware Kick ROM solution, something like a SYANNE-514 (I have not used this and cannot comment on whether it works).
I purchased four 68030 accelerators, the fastest delivery and best packaged was the TerribleFire 536 (TF536) from Amigastore.eu and I'll be purchasing from them as # 1 priority as the service was incredible. Not more than 1 week before Christmas, and they still managed to get the accelerator to me before Christmas - best Christmas ever!!! Thank you Amigastore.eu!
68030-TK2
And now, starting with accelerator I chose to keep in my Amiga 1000.... The 68030-TK2 German design by Matthias Heinrichs AKA "Matze", you can find an interview with Matze here.
I purchased a TK2 from eBay. eBay Seller Kulamario appears to be building small batches and putting them up for sale (This is who I purchased mine from. Mariusz (AKA Kulamario, kulamario@yahoo.ie) is a great guy, struggles with English language, but tries really hard, and in my opinion builds excellent quality boards). Kulamario helped me a LOT, and I am very grateful as I now have a stable, reliable, very fast 68030-TK2 in my Amiga 1000 running at 40MHz CPU and 40MHz FPU (68882). For a while, I was using clock speeds of 56MHz CPU / 28 MHz FPU (FPU running at half speed of CPU), but the State-Of-The-Art Demo would crash, even though every other app worked flawlessly. I opted for a little speed and more compatibiltiy.
I purchased this one because it provides a Floating Point Unit (math co-processor) socket, where the TerribleFire 536 has forgone the FPU. The later CPU's (68040+) have a math co-processor built in to the CPU, so no need for a seperate chip, and therefore FPU communications are much faster than the CPU cycles lost sending data out to the FPU chip and getting them back again.
You do not need an FPU, there are no games that use it, there is very little, maybe no advantage, except for your own programming fun, and a few apps like fractint32, IBrowse, plipbox drivers to name a few. I wanted an FPU just to play with floating-point code.
 |
| Be sure to ask Mariusz (AKA Kulamario) for a vertical IDE connector for your Amiga 1000, as the default is a horizontal connector (See below) which is a very tight fit in the Amiga 1000. |
 |
| 68030@50MHz CPU, 64MB RAM, and IDE (this version has the horizontal IDE connector) |
 |
| I added a 40MHz Motorola 68882 math-coprocessor (FPU) |
 |
| I added heat sinks - probably not necessary and more bling than anything practical |
Adding Heat sinks reduced chip temperatures by about 2-3 degrees Celsius and were probably not necessary. The hottest chip was actually the Xilinx chip on the accelerator, when measured via a thermal camera. The following thermo-cam shots are taken with the heatsinks installed and after the A1000 had been running for a couple of hours playing Mods in Eagleplayer.
Unfortunately, I lost my "pre-heat sinks installed" photos due to a dodgy SD-Card.
 |
Xilinx Chip is the hottest chip on the TK2 Accelerator board @ 40.5 Celsius |
 |
| The 68030 CPU running @ 56MHz also showing 40.5 Celsius |
 |
| 68882 FPU running @ 28MHz @ 35.2 Celsius |
Ambient temperature was between 20 and 21 Celsius
 |
| The hottest component on the TK2 now IC5 @ 46.8 degrees Celcius |
 |
| IC5 is to the right of the solder blob near the bottom of this photo |
 |
The underside of the 68030-TK2 |
The 68030-TK2 has its own limitations, for example, after much trial and error and then later confirmed on the A1K forum, the TK2 will not work with 32GB CF-Cards (I tried 9 different 32Gb cards), and will also not work with a 64Gb SanDisk Extreme Pro card either.
16GB is the maximum. In my trials, any card larger than 16Gb that I tried to use would see the Activity LED light come on and stay on - the Amiga never booted or attempted to go through the colour cycles - just a black screen. However, 16GB is more than enough in my experience, capacity is not really the issue. The issue is what is available for purchase in your local shops, and around my area 32GB is the minimum size I can buy these days, that is when I can even find a store that still sells CF-Cards.
Purchasing CF Cards from eBay is a gamble, there are a lot of fake cards being sold, meaning you don't know what spec you will get. See my blog on SD and CF cards here.
The other constraint with the TK2, is that it uses a 40pin IDE connector, not 44pins like the TerribleFire 536. This means you will need to provide power to the CF card adapter from the floppy-drive power connector ( I needed to extend my floppy drive power connector on my A1000). You will also need to ensure your CF Card adapter has a 40 pin interface (most use a 44pin interface). The 44pin IDE cable will NOT fit in a 40 pin interface.
 |
| Floppy-drive power extender using solder splices to make the job easy. |
The 68030-TK2 states that it is compatible with the A1000, where the TerribleFire 536 makes no such claim. In real life, I found they all work with the A1000, but they all have the same problem - they suck a lot of power and suffer freezing, crashes, hangs when they don't get enough juice (See below).
The A500 CPU relocater came with both accelerator purchases and should work with the Amiga 1000, although I found both relocators made my system unstable and opted for some machined IC socket risers which were much more stable for me:
 |
| IC Socket risers, machined 32 pin single strips. These were the only reliable way I found to raise the height of my accelerator. Relocators did not work for me. |
 |
| Floppy Boot Selector mod. Lets an external drive be DF0: |
In fact it will be necessary if you have installed the Floppy Boot Selector mod. Neither the TK2 nor the TF536 accelerator boards will fit without risers/relocators (I used 6 of these IC-socket-strips to raise my accelerator 3 units high to fit it in over the Floppy Boot Selector mod. This also means I can't use my metal shield anymore as the accelerator now sits too high in the case), but I can put the plastic lid back on and that works fine.
Noting that using the relocater will require that you replace your floppy drive (the floppy drive and floppy drive shield will have to be removed to fit the accelerator card in).
Using a couple of risers to lift the accelerator will mean you can still use the RF Shield. But 3 risers high are needed to get above the Floppy-Boot-Selector mod, and then it is too tall to fit the RF Shield back on. Another advantage of using the IC Socket Strips - I found they protected my CPU legs and accelerator pins which was especially useful when testing and plugging in/out repeatedly.
Finally, some notes from the A1k.org translated to English on setting the jumpers on your TK2.
68030-TK2 Jumper Settings:
CPU frequency:
- 30Mhz = JP1 = 10Mhz, JP3 = 1x, JP2 open at the top / open at the bottom
- 35Mhz = JP1 = 7Mhz, JP3 = 1x, JP2 top open / bottom left
- 40Mhz = JP1 = 10Mhz, JP3 = 1x, JP2 top open / bottom to the right
- 42Mhz = JP1 = 7Mhz, JP3 = 2x, JP2 open at the top / open at the bottom
- 50Mhz = JP1 = 10Mhz, JP3 = 1x, JP2 top open / bottom left
- 56Mhz = JP1 = 7Mhz, JP3 = 1x, JP2 = top to left / bottom open
- 60Mhz = JP1 = 10Mhz, JP3 = 2x, JP2 open at the top / open at the bottom
FPU frequency:
- FPU synchronous with CPU frequency = CPU/2 inserted + option inserted or both open.
- FPU with double CPU frequency = CPU/2 plugged in + option open.
- FPU with half CPU frequency = CPU/2 open + option inserted.
 |
| JP1 and JP2 frequency jumper blocks are found in the upper-left of this photo |
 |
| Option jumper is the red jumper header between the Xilinx chip and the JTAG pinholes, on the right side of this photo. JP1 and JP2 are on the left of the board (diagonally opposite) |
TerribleFire 535 (TF536)
TerribleFire 536 accelerators were designed by Stephen Leary. You can find an interview with Stephen Leary here or even better, a YouTube presentation from The Cave here. TerribleFire 536 (TF536) support can be found on the Exxos site here.
 |
| I also purchased an A1K mousepad, and an amiga coffee mug...It just tastes better! |
 |
| Amigastore.eu even provide a small install manual! |
The Amigastore.eu TF536 is built in-store (from Lorca in Spain) and comes unbuffered, this is not an issue or any kind of disadvantage for any other Amiga, but I did find the Amiga1000 behaved better with the buffered version from Retrokit:
Retrokit is based in Western Australia, Australia and I like to support local where possible, so I purchased a TerribleFire 536 from here too. RetroKit cards are made by AlenPPC in Canada, and shipped to Retrokit. AlenPPC also provides support for his TF536 cards here. Reading the TF536 page BEFORE purchasing is recommended.
 |
| RetroKit TerribleFire 536 from AllenPPC and Stephen Leary |
The A500 CPU relocater came with both purchases and should work with the Amiga 1000, although I found both relocators made my system unstable and opted for some machine IC socket risers which were much more stable for me:
In fact it will be necessary if you have installed the Floppy Boot Selector mod, as the neither the TK2 nor the TF536 accelerator boards will not fit without risers/relocators (I used 6 of these IC-socket-strips to raise my accelerator 3 units high to fit it in over the Floppy Boot Selector mod.
The TF536 comes with a 44pin IDE interface, this means it will also supply power to your CF Card Reader or drive (great, no need to extend or split the internal floppy-drive power!). The downside is finding 44-pin IDE cables - no one has them around my area, I did find them on Aliexpress though.
The TF536 also worked with every CF-Card I threw at it, including a 32GB CF-Card which the TK2 won't work with.
 |
| Using the relocater moves the accelerator into the space your Floppy Drive used to occupy . You can see I used the floppy insertion faceplate to mount a CF -Card adapter. You can see the GOTEK version I did of this mod in my other GOTEK blog post. |
Without using the relocator board, you will need to use some risers to lift the accelerator just a touch above the CIA chips. This also highlights that if you ever need to replace your CIA chips, you'll also need to remove the accelerator board - just a small extra bit of labour.
One advantage of using the IC Socket Strips, I found they protected my CPU legs and accelerator pins which was especially useful when testing and plugging in/out repeatedly.
 | ||
Without using a relocater board, there is room to keep the Floppy Drive, but not the shielding
|
 |
| Maybe 1 or 2mm clearance, but it will do! |
The TerribleFire 536 does not like my Parceiro and complains that the RAM is BAD on reboot. There's nothing wrong with the RAM on the Parceiro, however, just like the TK2 (above), the TF536 auto-configures itself first and then won't let anything else auto-configure. The TK2 has the advantage here as it does NOT display this red screen and boots without having to hit ok.
I think the accelerator maps its RAM where the Parceiro would like to map RAM and the conflict results in this red 'BAD' screen. Safe to ignore, and just hit OK to keep booting.
The short version is, it works if you don't mind the red screen and hitting OK each reboot. The advantage is the 44-pin IDE connector, and it does work with 32GB CF-Cards. Support is also in English, which helps in pay part of the world.
Pi-Storm
PiStorm was created by Claude Schwartz, you can read an interview with Claude here.
This IS the pocket-rocket, if you want the fastest Amiga 1000 possible, this is the one! Or if you have a Daughterboard Amiga, I think this might be the only modern accelerator that might fit in the A1000 case.
 |
| PiStorm with Raspberry Pi attached |
Frontier runs super-smooth, and everything in Workbench is incredibly fast. On top of blistering speeds, you can also configure wireless networking and a share 'drive' on the Linux side which you can then FTP to, making file transfers a breeze.
I did not use the RTG feature as it requires a separate HDMI monitor and I really don't like the sharpness of flat screens on my Amiga. Weird maybe, but I prefer my 1081 CRT for the best image quality in my opinion, and how it was always supposed to look and play!
However, some games do not run well with the PiStorm, including Turrican II (intro music very slow), IK+ (game runs but intro is slow and distorted graphics), Xenon II (intro music very slow). There may be others.
A really amazing and cool feature is the ability to change memory and CPU type just by editing a config file and rebooting! Really great if you want to test an application and not need multiple Amiga's all setup ready to run! 68000, 68010, 68020, 68030, and 68040 were all configurable options, along with EC variants. Choosing a 68030 will also give you a 68881 FPU, and choosing 68040 will give you a 68882 FPU - however there is NO performance gain, but useful for developers or hobbyists.
In the same way, you can also change the kickstart rom in the config file and by supplying the desired ROM, reboot and tada - you're running your chosen kickstart! Very versatile, almost a dream Amiga.
Woah!
But wait, there's more - after installing the pistorm apps, you can run executables on the Linux/pi side from your Amiga CLI!!! It's really the most feature rich and very cool accelerator option! PiStorm lets you use the SDCard in the Raspberry Pi as a super-fast and convenient hard drive, using a real partition or a HDF file (Emu68k uses a partition only).
The PiStorm is also much smaller than other accelerators, so easier to fit into a case, especially if you own a piggy-back Amiga 1000 (the daughterboard version of the earlier Amiga 1000). Which means you can probably still use your RF-Shielding.
 |
| This is the Pi-Storm card without the Raspberry Pi attached, very slim! |
You can read more about the PiStorm on the GitHub page here or I like this setup guide on Retro32.
There are two CPU emulators you can use, Musashi and Emu86k, I only used the Musashi emulator because as at time of testing and writing this blog, Emu68k (while much faster again than Musashi) lacked the networking and share folder abilities. Musashi is already much faster than even my 68030-TK2 @56Mhz (+28Mhz FPU). Musahsi was about double the speed, making it faster than a stock '040@25MHz!!
 |
| Ultimate Power! Itty-bitty little space |
I wanted to love and keep the PiStorm, the networking, share drive, running Linux commands on the pi Side from the Amiga CLI....the only thing not to love was the slight compatibility issues with some of my favourites! I don't even play games much, but not having the option to play them was a bridge too far for me. Hence I settled on the 68030-TK2 for now. Further development of the PiStorm could easily tempt me to swap my TK2 for the PiStorm, it is really amazing!!
Troubleshooting
A further clue that I had power issues came from noticing the video seemed to be having trouble syncing via the OSSC with the ‘030 installed, just coincidence? It was fine once I switch the OSSC off and back on.
Again, David Dunklee was very generous in providing encouragement and tips to get me going, I had spent 3 days testing and trying to isolate the problem and was about to give up:
"I wouldn’t necessarily rule out the IDE interface or the CFCard as the culprit. I was having similar issues with timing on the SD card. I guess something to look at is whether the errors are more prominent when loading/reloading code or when executing code. Subtle difference there. If code is read from the CFCard but gets jarbled during the I/O, then eventually the code it reads is going to be executed and since the code is jarbled, you’ll get an illegal instruction… sometimes.
Alternatively, if the CPU or memory on the accelerator is bad then running the same code over and over again may cause an error.
A quick way of testing the CPU and memory is to load a test program or script into the RAM: drive and run it over and over again in a loop… infinitely. I like running AMNESIA (a memory check program) in a loop. If it never crashes, then you know there’s no issue with the CPU or RAM. (Since it’s running from RAM: the CFCard isn’t a culprit).
As for the OSSC… there may be a clue here. It’s riding a different set of signals that shouldn’t affect the CPU. But, perhaps there’s some unbalanced power draw or noise generated by one of the devices. Maybe reducing the number of connected devices may yield a different result… maybe more reliability.
Power and Noise were a common issue for the A1000. It wasn’t designed for high expansion and the power bus is rather limited. I suspect the TF is pulling a good amount of power. Likewise, the OSSC could be taking up some precious milliamps."
I unplugged everything extra, reduced the CF Card to 3.3v rather than 5v, and the miracle occurred! My Amiga was working and playing mods again - a few hours ago it would crash within 15 seconds of starting!!! Sure enough, power was the issue, but before then:
 |
| Troubleshooting the instability gave me an excuse to use the O-Scope, woohoo! |
Regardless of the card you pick, troubleshooting saw so many insets into the CPU socket and removals that I started to worry about my CPU socket on the mainboard - the CPU socket survived and is fine, phew!
Recapping I think is a must if you want to use a 68030 accelerator, See my recapping blog entry for the recap fun.
 |
| Pin 15 (CPU Clock) from the CPU socket should look something like this. 7.09MHz on my PAL A1000, with around 3.6V peak-peak. A more square shape would be better. |
 |
| Pin 20 is the E-Clock for external peripherals, and it should look like this. 709KHz square wave, and around 3.6V peak to peak. Mine is showing 3.52V. |
Checking that the clock cycles were correct, and that the Amiga would boot, but fail soon after, and that it worked without failure with a 68010 CPU started to point to a possible power issue.
I started testing demos and games. I found even with a minimal boot and nothing else loaded, some games and demos just would not work. I started looking at options to boot to OS 1.3 with the accelerator as a work around. The TerribleFire 536 will drop to 7MHz when using Kickstart 1.3, and I think the 68030-TK2 will do the same.
The issue is, I would need to find a way for WorkBench 1.3 to recognise the FastRAM and the CF-Card Hard Drive before I could get anywhere. There was some promise from creating a hacked Kickstart 1.3 with scsi.device embedded. However...
The Kickstart 1.3 hack will not work on an A1000 - it is meant for A1200/A600 users who want to use Workbench 1.3. The process fails when trying to patch the scsi.device into a rom - the archive only provides patches for A1200 versions of SCSI.device, ugh! Even if I got past that, I have also learned that the rom needs a further hack with a hex editor to fool ithe Amiga/Kickstart into thinking there is a Gayle chip - scsi.device looks for Gayle, and if it can’t find it, it quits. The effort is not worth the result for me - I still have incompatibilities, dang it!
I could not find an alternative that would recognise the CF-Card in HD ToolBox or HDInstall, and had to give up on this. The Parceiro works because it uses its own device driver written by David Dunklee, however because these accelerators won't allow any other device to auto-configure, this is also not an option.
With all the accelerator boards, they auto-configure themselves and then prevent anything else from configuring - so you are stuck with what the accelerator provides, no other devices on the expansion port will be recognised.
The 68030-TK2 won't complain about the Parceiro being plugged in, the Terriblefire 536 will present a auto-config red screen advising the RAM on the Parceiro is BAD. There is nothing wrong with the Parceiro RAM, this can be safely ignored, just click 'Continue' to make it go away and continue booting.
Testing and troubleshooting let me come across a LOT of Software Errors/Guru Meditations. AmigaLove was a great source for deciphering 'what the hell does that mean? :)
https://www.amigalove.com/viewtopic.php?t=500
Also, note that neither of these accelerators will fit in a Piggyback (Daughterboard) Amiga 1000 - even with an A500 relocated they physically clash with the daughterboard:
 |
| The relocator hits the daughterboard and will not go in any further |
 |
| A post under the daughterboard prevents the accelerator going any further in |
Repeating from my Parceiro upgrade blog post:
Boot Colour Codes from Classic Amiga Wiki
- Red - An error in the Kickstart rom as detected.
- Green - An error in the Chip Ram was detected.
- Blue - An error in the custom chip set was detected.
- Yellow - The CPU encountered an error before the system's error-trapping code (the code the calls up the Guru) was in place.
- Black - No CPU detected
- Grey - CPU Passed the test
- White - CPU failure
- Purple - Kickstart ROM error - Parceiro ROM switch not positioned on a ROM bank correctly, or set to no ROM when using an '030 accelerator (I've tested with a TerribleFire 536 and a 68030-TK2 - more on those in a later blog)
From Lemon Amiga: Amiga Boot Power LED Blinks
(A1000) - Fast steady power LED blink; dark screen. 74S51 (U9I) & 74F74 (U8I) damaged from expansion port.
(A1000) - 4 Blinks then a 5 second pause - This is normal and part of its boot sequence, but can also indicate a bad Kickstart disk. If there is no Kickstart image appearing after the blinks, check and replace the disk drive.
6 or 7 Blinks is usually broken tracks around the battery area after an acid leak, or battery issues with an expansion.
10 Blinks - System is waiting to connect to a remote debugger or terminal.
10 Short + 1 Long Blink (with Green Screen) - Faulty Agnus Chip (try clean and re-insert)
Constant Blink (with Yellow Screen) indicated either faulty capacitors on the main PCB, or a general issue with the +5V power or power supply.
Or check out the code definitions on amigalove.com here.
Or the Colour codes, blink codes and Guru codes on LemonAmiga here
Conclusion:
Keep your Amiga 1000 close to stock unless you have a real reason to spend money on acceleration. Get a Parceiro and a 68010 and leave it there - everything works just like it should! David Dunklee is always working on upgrades to the Parceiro which you can send your board back and have it upgraded for just a handover/upgrade fee!
I was happy back in the euphoric blue of Workbench 1.3 and the best of the late 1980's, early 1990's. Actually I don't really like the grey of OS 2 and later, but I do like the internet access, especially UHCTools, having an FTP Server with rc-FTP and built-in hard drive recognition and access.
So was there a speed increase? Absolutely, SysInfo reported processing speeds of 17 times and more faster than a stock A500, 3 x A600 Chip speed, and hard drive read/write times of 3.5 to 6.6MB/sec - a huge speedup from even the Parceiro at around 500-600KB/sec.
 |
| Image from the 68010 and Parceiro - decent increase in t's own right! |
 |
| To the extreme from a 1985 Amiga 1000 |
However, in real life - most software did not really get much from the accelerator. Surprisingly, connecting to a BBS via Telnet and either a WiMODEM232 or Plipbox showed the most noticeable increase. It went from (a little painfully) drawing lines row by row, to rendering whole screens in a second! Wow! It was super-lightning fast! I kept the accelerator in place just for this!
Workbench 3.2 is snappier and felt more responsive, everything else was the same. HippoPlayer could play and still leave enough bandwidth to do other things, like opening a CLI shell etc, but played just as well with the quad scope dancing around - just like when it had a 68010.
