My A2000 so far.

[rkauer]

I can post the ROM image to the Zone, but you have to burn the pair of EPROMs yourself (or ask nicely to a friend who have a programmer).

If you are an electronic able person, is better to make the Ralph Babel's Guru ROM instead. Or buy the adaptor from Amigakit or Vesalia.

[EDIT] Too late, they don't sell the Babel's adaptor anymore... sigh...

[sbeehre]

unfortunately i dont know anyone who has an eeprom burner also do you know where to get a2000 3.1 kickstart roms?

[rkauer]

I think you know by now...

[sbeehre]

Also my a2091 has had all the memory taken from it! can you still buy those ram chips today?

[rkauer]

Originally Posted by sbeehre

Also my a2091 has had all the memory taken from it! can you still buy those ram chips today?

Yes, you can.

Only in 80ns "flavour", I'm afraid. Farnell, Digikey (expensive! Be warned!) and lots of places have those little buggers to sell.

Mine A2091 is full populated with the (now rare) 70ns variant (minus one chip with a broken leg, replaced with a 80ns, works OK).

Our niponic friend is cooking the v7.0 ROM for SCSI to me.

[sbeehre]

Originally Posted by rkauer

Yes, you can.

Only in 80ns "flavour", I'm afraid. Farnell, Digikey (expensive! Be warned!) and lots of places have those little buggers to sell.

Mine A2091 is full populated with the (now rare) 70ns variant (minus one chip with a broken leg, replaced with a 80ns, works OK).

Our niponic friend is cooking the v7.0 ROM for SCSI to me.

i found these are they ok?

[rkauer]

Originally Posted by sbeehre

i found these are they ok?

Nope, wrong chip. You are looking for 514c256 or 53C104 (20 pins). 70ns are preferred, 80ns and even over (up to 120ns) are OK.[EDITED]

Those 70ns are rare beasties nowadays.

[Secret Vampire]

No, they need to be 256kx4 (1Mbit), those are 32kX8.

The best sources I've found are some old PC graphics cards, and later (I think rev 6.x) A500 motherboards. Some A500 trapdoor expansions probably use the same chips too (Look for ones with 4 chips). The only problem is that salvaging chips from old hardware requires some soldering skill.
I personally wouldn't bother to buy the chips new, for the price you'll spend, you could probably find a better SCSI controller which accepts SIMM memory, like the GVP, or a Zorro RAM card with some memory on it.

one final option http://cgi.ebay.co.uk/1-MB-DIP-Ram-f...d=p3286.c0.m14 60ns too, top quality stuff.

[Fingerlickin_B]

Originally Posted by Secret Vampire

one final option http://cgi.ebay.co.uk/1-MB-DIP-Ram-f...d=p3286.c0.m14 60ns too, top quality stuff.

And cheap too...not a single bid at this point!

PZ.

[Zetr0]

Hello there my friend,

I bought some of those chips a while back from www.futurlec.com and have been plesantly pleased with the fact that they were 60ns flavour

and at 90cents (50p a chip) one cannot argue to much... there is a $5 delivery charge but NO minimum order! whoohoo

on the bottom of the page here http://www.futurlec.com/ICRAM.shtml

[FrenchShark]

Originally Posted by rkauer

Thanks, TC!

So if a newer version of the GVPAT.device can be used without physically fit it onto the board that will be marvellous!

Now I need to grab another "brand new" 1080Mb SCSI HD (or wait until I can use a GURU ROM onto the 2091 and then a 9.1Gb one, or even both)

Good suggestion about the PSU, but I have a lot of those older AT around. I just need to take one with good +5V regulation and solder it to the A2000 wires plus a nice triplet of Molex connectors for everything else (3 HD, 2 floppies, 1 CD-RW and maybe an IDE ZIP drive).

Back in the days, when I had my A2000, I have ported my work on the AT-Apollo.device to the A3001. I was able to support ATAPI devices such as CD-ROM drives. I also remembered that my LS-120 drive did not work because of an HW incompatibility with the A3001.

I just digged into my archives and found out that I wrote a gvpat.device v4.00 in 1998! There is also a NoIDE_A3001 tool to install a resident program to kill the original gvpat.device and an AtaInfo tool that shows the capabilities of the IDE device.
EDIT : IIRC, gvpat.device v4.00 does not support a 4-port IDE but is NSD/TD64 compliant with LBA addressing (up to 128GB hard-drive).

I give no WARRANTY on these tools since I do not remember what I have done (10 years ago already !) but I used them for a while on my A2000 without any issue.

Regards,

Frederic

[rkauer]

Great!

Do you remember the maximum size of IDE HD? I think I'll give it a go.

[TheCorfiot]

@Frenchshark

I thank you for your very kind generosity in sharing this gvpat update
If it was possible to put this device into an Eprom to fit directly on the board & provide autoboot too that would be fantastic

TC

[rkauer]

I was thinking on the same thing!

Freddie, tell us that is possible. Pleeease?

[sbeehre]

Originally Posted by Zetr0

Hello there my friend,

I bought some of those chips a while back from www.futurlec.com and have been plesantly pleased with the fact that they were 60ns flavour

and at 90cents (50p a chip) one cannot argue to much... there is a $5 delivery charge but NO minimum order! whoohoo

on the bottom of the page here http://www.futurlec.com/ICRAM.shtml

thanks Zetr0! is that the 1Mb video RAM right at the bottom?

[Zetr0]

@sbeehre

its one of the last two, send them an email you need the 20 pin varient not the 18 pin

[FrenchShark]

Originally Posted by rkauer

Great!

Do you remember the maximum size of IDE HD? I think I'll give it a go.

It supports 28-bit LBA addressing that means :
(2^28) * 512 bytes = 137,438,953,472 bytes.

The NoIDE_A3001 command is a little bit hacky : it does not exit.
You have to run it this way : RUN NoIDE_A3001 >NIL:
I think I should improve it to make it startup-sequence compliant.

Regards,

Frederic

[FrenchShark]

Originally Posted by rkauer

I was thinking on the same thing!

Freddie, tell us that is possible. Pleeease?

I am wondering if the UVPROM is big enough to hold the new device.
Even if the UVPROM seems big, usually only one nibble per word is used in the UVPROM because of a bug in expansion.library in KickStart 1.3.
IIRC, the A3001 has a 32KB UVPROM -> 8KB of useful storage.
There are two ways of overcoming this issue :
- Having a small routine nibble-encoded, loaded by the expansion.library, that then load the rest of software, word-encoded.
- The UVPROM just contains a routine that loads the gvpat.device from the hard-drive. Does someone remember if HDInstTool supports custom code configuration on the RDB?

Regards,

Frederic

[rkauer]

Hmm...

The A2000 ROM is 2.04 (37.175), dunno if it is au pair of the task. 1Mb Agnus, ECS Denise.

If I remember correctly, HDInstTools have custom boot code support (I used it in the ADD_SCSI controller for my A500 ¹/2 ECS - 1Mb Agnus, OCS Denise).

[FrenchShark]

Originally Posted by rkauer

Hmm...

The A2000 ROM is 2.04 (37.175), dunno if it is au pair of the task. 1Mb Agnus, ECS Denise.

If I remember correctly, HDInstTools have custom boot code support (I used it in the ADD_SCSI controller for my A500 ¹/2 ECS - 1Mb Agnus, OCS Denise).

No plan to have 1.3 (softkicked or with a switcher) for backward compatibility on the A2000 ?

It is good to know for HDInstTool.

BTW, the AT-Apollo 2000 and the A3001 have the byte order reversed in comparison with A600/1200/4000 IDE port or even Buddha card. The gvpat.device v4.0 is able to detect byte-swapped HD if a RDB with "DRKS" ID is found instead of "RDSK".

Regards,

Frederic