Reply 20 of 27, by mrau
well, if the manual is right then you should already have it, the only conclusion is - what You have is not kit-256 compatible
well, if the manual is right then you should already have it, the only conclusion is - what You have is not kit-256 compatible
You're likely right. I've been scouring the internet for more than a week trying to even find a picture of a KIT-256 and have come up empty.
Did you find a compatible stick? I have the same problem with my ATC-1020. My system hangs on ”Verifying DMI Pool Data.......” with floppy led on. I have pulled jumper JP17 to disable onboard tag.
Not sure if you read the manual, but you can not use the on-board cache and a module at the same time. If you want 512 kb cache, you need a 512 kb cache module. The 256 kb cache module was for versions without on-board cache.
wrote:Not sure if you read the manual, but you can not use the on-board cache and a module at the same time. If you want 512 kb cache, you need a 512 kb cache module. The 256 kb cache module was for versions without on-board cache.
I might have misunderstood the manual a bit. This is what it says:
"ATC-1020 is built in 256KB or 512KB Sync. Pipeline Burst SRAM on board and provides a COAST slot for further expansion."
"For upgrading you Sync. SRAM from 256KB to 512KB by using COAST Module, you should plug-in the KIT-256 module, then set JP17 to "open" (disable the original TAG on board). You must use KIT-256 for upgrading your system to 512KB Sync. SRAM, please contact your system dealer about its information. It does not need any BIOS value adjustments for upgrading the SRAM size."
I guess the "KIT-256" is a 512KB module and that the motherboard disables the on board cache when it's used? I have a 512KB module on the way so maybe that will work better.
wrote:Did you find a compatible stick? I have the same problem with my ATC-1020. My system hangs on ”Verifying DMI Pool Data.......” with floppy led on. I have pulled jumper JP17 to disable onboard tag.
I have JP17 closed on my 1020+. 256k "Pipeline burst" COAST for a total of 512k cache. I wonder if the manual is correct.
It is a bit unclear what COAST revision your module has and what COAST revision the mainboard expects.
Retronn.de - Vintage Hardware Gallery, Drivers, Guides, Videos. Now with file search
Youtube Channel
FTP Server - Driver Archive and more
DVI2PCIe alignment and 2D image quality measurement tool
I have tried with the jumper on as well but Windows wont boot and BIOS still reports 256k cache. This is the module I have been trying with:
Edit: The chips on the module appears to be pipeline burst sram but since the module is HP maybe it's not standard?
https://www.idt.com/products/memory-logic/sra … ined-burst-sram