**Need Setup HELP** with Classic Amiga 2000 HARD DISK (Bridgeboard)

[paul1981]

Have you tried all this with your old ROM chip? Maybe parts of the software aren't working correctly with 3.1...perhaps DJMount isn't. I don't have such a setup but perhaps others can answer this.

[paul1981]

I just thought about what I wrote above.

It's a Chicken before the Egg thing.

I can't make a 3.5" disk to boot on the Amiga PC Side, because I would need to boot off that 3.5" DOS disk to load the driver, to recognize the card, to boot off that floppy to recognize that other Controller to get access to the Hard Disk I want to see.

But maybe there is something along that line that you guys can think of.

It's all very painful when you don't have a hard disk in your Amiga. When they boot to Workbench in a few seconds it just makes any Amiga complete, it's a transformatiom. like an entirely new computer. Should you decide to keep the 2000, I'd certainly pickup a A2091 controller or one of those GVP ones with FastRAM too.

WinUAE can now emulate bridgeboards too. Would that help any? If you attach the controller card to your 486 with drive attached would that not enable you to read the drive? I'm not very experienced with DOS, but isn't there a driver on the card firmware or  I a few years ahead? If not, there has to be a driver out there somewhere.

Apologies if I'm saying things that have already been said. Did you get any further with making that Amiga disk to replace the damaged one? Have you considered imaging the disk for us and sending it to one of us so that they may reconstruct your disk?

[paul1981]

http://grandis.nu:81/eabsearch/search.php?_search_=1&search=a2088&category_id=&exclude=&limit=

The server seems down at the moment but it should be back on soon. I see install disks here. I think they moved the server or something recently.

[paul1981]

Indivision is not an RTG card.  It's ability to work with some 24-bit screenmodes is more of a curiosity than a functional option.  See my previous posts about what additional screenmodes you'll be able to utilize with Indi ECS - although they, too, will be pretty slow at 7MHz.  :lol:

These snazzy 256 colour modes etc, aren't they just for the A600 for some reason? I have been told in the past put I can't remember now and if so I can't remember the reason why.

[paul1981]

Indivision is not an RTG card.  It's ability to work with some 24-bit screenmodes is more of a curiosity than a functional option.  See my previous posts about what additional screenmodes you'll be able to utilize with Indi ECS - although they, too, will be pretty slow at 7MHz.  :lol:

These snazzy 256 colour modes etc, aren't they just for the A600 for some reason? I have been told in the past put I can't remember now and if so I can't remember the reason why.

[paul1981]

Now that is SUPER COOL!!!

I must be the only person in the AMIGA Universe that didn't know that.

So when did Early-Start-UP BIOS-screen get enabled?  Kickstart 1.3 (Part of AutoBoot, or as Rafaelle mentions OS2.x)?

This is great, since I assume I can make multiple Partitions on my GVP-SCSI HD and pick which one I wish to boot from.

OS2.x. With regard to your autoboot jumper, it might be like my Megabody IDE controller whereby disabling autoboot disables the device driver (probably gvpscsi.device or something like it) and so to get the drive(s) to then show you'd have to load the driver fron a script or the shell with binddrivers or similar.

With softkicking 1.3, I use this:
http://m68k.aminet.net/package/util/boot/skick346

Personally I use it in my startup-sequences so that holding down a mouse button when booting brings the Kickstart selection screen. You could select 1.3 from there, where it will then reboot with KS1.3. Holding no mouse button upon booting will continue to load Workbench 3.1 or whatever your startup-sequence does. It detects left mouse button, right, or both and the other port too, so there's no shortage of options. There's plenty of these mouse input-read commands on aminet. Off the top of my head I don't know which one I use...but it's normally the one with the least bytes providing functionality is there.

[paul1981]

Paul,

Thanks.  More Tools for my SW Toolbox.

I peeked at Sidekick.  Sound like it's for ROM2.0 (which I don't have).
I not getting any more ROMs at this point. I'll have (1.2,1.3,3.1).
Also I looked at the SideKick Package and No A2000 on the list.

Since I will have a ROM switcher, I'll be able to craft something together.

I honestly don't know whether it works with an A2000, but I do know you can use it from Kickstart 3.0/3.1/3.9 and softkick 1.2/1.3/2.x/3.x with it (doesn't require a 2.0 ROM chip exclusively). It's a fantastic tool! I think it was programmed in the 2.0 days initially, so I'd be very surprised if it didn't work with the A2000. There's plenty of A2000 users around so they should be able to tell you what they use.

EDIT: I forgot to mention MKick to you. MKick works under Kickstart 1.3, and people us it to softkick 3.1 on 1.3 systems. I haven't used it myself yet, but I plan to do so later this year when I get around to finishing my A500 project. So you could use your 1.3 ROM chip if you wanted to and then softkick 3.1. Perhaps you can softkick 1.3 from your 3.1 system too.

MKick:
http://aminet.net/package/util/boot/MKick19