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

[Dandy]

Part II:

Original by wbrejnia:

*** Is that incopatibility with KICKSTART 3.1 ROM? Older workbench?

Hummm - I would definitely only use Kickstart and Workbench with the same version number...

Original by wbrejnia:

*** I want to clone those original disks somehow. Make a new BOOTABLE and copy everything off the original disks (different DJMOUNT, etc, etc)

XCopy (http://aminet.net/search?query=xcopy) is good for such tasks...

Original by wbrejnia:

-IS THE BRIDGEBOARD FAULTLY? (Why no error messages)?

That's a possibility, but at this point I don't think so...

Original by wbrejnia:

-IS my Bridgeboard Workbench disk wrong? (why no error message)?

Does it also have read errors?
If so, --> DiskSalv is your friend...

Original by wbrejnia:

-IS that Kickstart ROM I upgraded the problem?
---->(Should I put back the KS1.2 like the Amiga used to be ?)

As I said above, I would definitely only use Kickstart and Workbench with the same version number...
So, to avoid any incompatibilities, make sure WB and KS are the same version.

Original by wbrejnia:

*** IS THE autoBoot feature in Kickstart 3.1 a problem for Bridgeboards?

You will have to try if KS 1.2 makes a difference...

Original by wbrejnia:

*** Did Amiga Developer take something out since who would use a 8088 for Hard Drive access.

To find out, you would have to read & compare the change logs of both...

Original by wbrejnia:

---->(Should I go back to Workbench 1.2 like the Amiga Used to be?)

I would definitely try at first to get it all working properly with v1.2 and later try it with v3.1 ...

Original by wbrejnia:

---->(I'm using DOS6.2 on PC side, Maybe go DOS 3.1. Manual talks just DOS, and windows 1/2

Have you tried to find out on the web which M$-Dos version is best suited for  8088 "stoneage" cpus?
What's "windows 1/2"?
The oldest Windows-version I know is "Windows for 286" - I don't even know if there was a version that runs on 8088 cpus (predecessors of the 286 cpus)...

Original by wbrejnia:

I really don't know what to do next to complete a flexible Dual Booting Hard Disk Driven system (which would be Nice!! and worth loading SW on)

Well, I can understand that making this old stuff work again is a nice challenge.

But I cannot decide for you if it's worth the hassle.
Keep in mind that in 2017, a 8088 cpu is of very limited use.
It might turn out that it is really hard nowadays to find software to run on it.
I have thrown out my Vortex 286 harware add-on because of that already a long time ago.
I even doubt that a 386 or even a 486 bridgeboard is of much use in 2017.

If you're after a "flexible Dual Booting system", the best I can do is to suggest to make your Amiga network capable and network it with an cheap up-to-date WIntel box using "RDesktop" and "smbf".
Today, most of the classic Amiga hardware (including all existing PC bridges) is so far behind that running actual Win versions on it is either impossible or at least incredibly slow.

Furthermore, if you want to make your Miggy a "Hard Disk Driven system", there are much better solutions available at relative low prices (faster, higher capacity, higher flexibility, more reliable, sparepart supply etc.). I'd say it's worth considering a modern solution rather than using a 30 year old MFM/RLL solution, where no-one can predict WHEN the drive will start to fail. It WILL fail, the question is WHEN...

Original by wbrejnia:

I could give up and just go ahead with the GOTEK install which would leave me with a pretty good setup.
A) Workbench used to Boot from slow unreliable Floppies
-----> Replaced by GOTEK
B) PC Boot used to boot from Floppy and that's all I had
-----> Now I have a hard drive, so floppy is just needed to Boot "Command.com",
-----> the C:config.sys, and C:autoexec.bat and everything else could be on C: drive (I tried it, it works)
-----> Kind of sucks,that I have a working DOS Bootable 5.25" disk in the drive. ((*MUST BE FIXED*), Maybe Compact Flash when it comes.
Any ideas? (contact that German Bridgeboard expert?)

As I just said - I cannot decide for you if it's worth all the hassle. All I can say that there are better solutions available today.

Original by wbrejnia:

 #440 wbrejnia
I just got an IDEA (that won't work because I tested part of this before)
Let's reverse things!! (To solve the 5.25" boot disk requirement)
- In the bridgeboard manual (if you have an Amiga hard disk, but no PC hard disk), you can boot the PC from a Virtual DISK files on the AMIGA HD.
In a normal situation the VIRTUAL FILE would be a WHOLE PC C: Drive parition. But a 3.5" 880K Workbench Floppy doesn't have room.

No.
You just said "if you have an Amiga hard disk". If you have an Amiga hard disk and it is a modern one with several gB in size, you're NOT restricted to 880 kB for your VIRTUAL C:-FILE.
And best of all:
You can have several partitions on such drives and some of them can be PC formatted - no problem at all.

Original by wbrejnia:

a) I create a small file on my WORKBENCH DISK (could be a file on DF0: or even a file on my external DF2
BB-Manual says file can be anywhere. DISK, RAMDRIVE, so long as the file is permanent, and Read/Writeable.
b) inside that FILE is JUST enough to have a C: drive partition (bootable with A)
c) I re LL-FORMAT the RLL drive as a D: drive with DOS files (but not bootable)
Here is how things would work: (if my bridgeboard and setup is ok)
A) I put in the WORKBENCH DISK
B) AMIGA BOOTS UP with the VIRTUAL C: Drive File on it.
C) PC Boots C: drive from that VIRTUAL DRIVE
d) But after command.com load (D: drive is used for everything else)
This would eliminate the 5.25" Bootable Floppy drive in the AMIGA PC.
*** BUT THIS WON't Work, because something is wrong with BRIDGEBOARD (AMIGA-PC and PC-AMIGA) Communication.
*** SOMETHING TO DO WITH JANUS
I am putting this Link I got above since it talks about JANUS versions, and tools to setup the CROSDOS.
(Plus a mention what files have to be where for Janus to work)
(and mention of some new Janus Setup Tool)
http://members.quicknet.nl/rhm.herol...eboard_faq.htm

Forget a) to d).
My suspect still is that you somehow misunderstood the underlying working concept of PC bridgeboards and therefore make mistakes.

I still think you have to have a booting Amiga harddrive first and then to install the bridgeboard soft on that. This allows you to start the bridgeboard from Workbench, when you need to, just by double-clicking the related icon. Normally this is not very complicated.

Once the bridgeboard started, the PC-side boots automatically - either from a "VIRTUAL C:-FILE" on the Amiga partition, or from an "PC formatted partition".

And then you can switch forth and back between the Amiga and the PC and work on both sides simultanously (nah - rather alternating).

Phew - what a lengthy answer...

[Dandy]

Dandy,

If you have a copy of SYSINFO, can you run it an see if there is some process running on AMiga Side related to Bridgeboard, like JANUS or DJMOUNT.
...

I'm afraid I have to disappoint you here.
My old A500 is partly taken apart and stored in the cupboard since 1999.
"Partly taken apart" means I have thrown out my Vortex ATOnce 286 classic decades ago, replaced the 68000 cpu with an Viper 520+hd and so on...

Haven't looked at it since 1999 - not sure if it still works at all...

[Dandy]

Hi Dandy,

Welcome back, it's been a while.

Thanks!

I am going to start from Scratch on my WOrkbench Disk for my bridgeboard.  (NOW THAT ALL HW is working)

That might be a good idea...

All the Software JAnus etc is old stuff I played with two years ago.
...

:laughing::roflmao:
Initially I overlooked the "J" in "JAnus" and was just starting to think "What the f..."...
:rofl::biglaugh:

I think this may be the final missing piece.


Here are all the DISKS in one place.
http://amiga.resource.cx/exp/a2088xt
I am gong to get them ALL, and start a fresh Workbench DIsk Build

Good idea.
Make sure all disks you have to use for this are good. (DiskSalv)

Also make sure you're using the same version of Kickstart and Workbench.
Furthermore, all the floppy disks you have to use in the process should be formatted and created with the same version of Kickstart and Workbench you are working with. This way I avoided running into version probs back in the days.

[Dandy]

[HOW TO (Solve/Determine/Isolate) why C: drive Doesn't Boot in AMIGA PC]

Hummm - when you prepared the drive with "fdisk" - did you chose the "primary DOS partition" (PRI DOS) for your boot partition (most likely c: )?
And it also seems to be better to boot the PC not from harddrive for this, but from a bootdisk, which was created with the same DOS version.

...
Hey, I'm just guessing, since I have no hard facts to go on.
 

Try to get all necessary "hard facts" on the web - "Google is your friend!"...

[Raffaele]

Part I:

With KS 1.2 you need a "HD-Boot" floppy disk. This must contain the necessary Amiga files to mount the harddrive and to move the system/control over to it (e.g. with the command "movesys dh0:").
What this "HD-Boot" floppy disk does is a "minimum boot", so to say.
The "full boot" into Workbench is then done from the harddrive.

Of course it does. I omitted the HD Floppy Boot part you added at is seems me obvious. At least i remember how worked Kickstart 1.2.

Also if I remember well Movesys command was good utility from Fish Disks, either you must do all Assigns by adding it on S:Startup-Sequence (and Startup-Sequence only as User-Startup did not exist in 1.2).

[Raffaele]

@ Wbrejnia

Now we have some scenarios:

Scenario A

1) Boot Amiga from floppy and run PCDISk

2) it initializes Bridgeboard ad activate ISA Slots

3) PC boots from PC Floppy A. or B:


Scenario B:

1) Boot Amiga from floppy and run PCDISk

2) it initializes Bridgeboard ad activate ISA Slots

3) PC boots from C: partition on Hard Disk mounted on ISA Controller

Does it or Are there any issues?


Scenario C:

1) Boot Amiga from Floppy, Initialize Bridgeboard, Initialize Amiga HD DH0:

2) Floppy movs all System to Amiga Hard Disk (running but no booting)

2) On Amiga Hard Disk or other Amiga Partition RAM:, Df0:, etc., you can put Virtual C. File and make PC boot from it.

It should be made visible to PC with an option of JDisk (if I remember well)


Scenario D

1) Boot Amiga from floppy and run PCDISk

2) it initializes Bridgeboard ad activate ISA Slots

3) PC boots from C: partition on Hard Disk mounted on ISA Controller

4) JDisks make Amiga aware it exists virtual partitions files JF0: JF1: Etcetera upto 7 on PC Hard Disk partition C:


Scenario E

1) Boot Amiga from floppy and run PCDISk

2) it initializes Bridgeboard ad activate ISA Slots

3) PC boots from C: partition on Hard Disk mounted on ISA Controller

4) JDisks make Amiga aware it exists virtual partitions files JH0: JH1: Etcetera upto 7 on PC Hard Disk partition C:

5) Amiga can transfer system from Floppy to JH0: as Dandy says, just as like any other Amiga real Hard Disk DH0: but it requires some time to boot and make all virtual partitions JF-X: visible back to Amiga side

6) Amiga will use JH0: As any normal real Hard Disk for the entire time of the session (remember it requires partitioning and formatting).


Scenario F

1) Boot from Gotek Floppy Drive Emulator

2) Gotek ADF 1 virtual Amiga Floppy boots the Amiga computer, initializes Bridgeboard with PC Disk and activate ISA Slots so then PC Hard Disk becames visible

Unfortunately Booting from Gotek does not makes the CF Card visible as an Amiga Hard Disk. It mounts upto 999 Floppy drive images ADF visible to Amiga as if were 999 separate floppies each of one visible at a single time...
So you csan only boot from ADF 1 and then mount and make visible files present on another ADF like when Amiga prompts INSERT DISK Name_XXX.

So then...

3) You can put Virtual C: partition on a file on ADF 2 or above numbering SLOT on your Gotek virtual drive, but you have to do lots of assigns and joking with inserting/removing virtual floppy ADF and made right instructions to JDisk command.


If you want to use your Amiga-PC in a different way, please explain better what you want to do.

[Raffaele]

Part II:

Original by wbrejnia:

*** IS THE autoBoot feature in Kickstart 3.1 a problem for Bridgeboards?
You will have to try if KS 1.2 makes a difference...

I would definitely try at first to get it all working properly with v1.2 and later try it with v3.1 ...

WARNING!


Bridgeboard Software works well with Kickstart and Workbnch 1.2, 1.3, and if I remember well, it works also with Kickstart 2.0.4.

It has some issues with 2.1 and does not work at all with Amiga Kickstart and AmigaOS 3.0 and 3.1 (could generate lots of Guru Meditations at any moment)

I don't know why Commodore abandoned Bridgeboard users at their own destiny.
Any other firm like ATARI or Apple had had acted seriously for their users supporting bridgebard software for at least 10 years.

Unfortunately advancement of Amiga, transforming original OS from Disk labeled "Workbench" to proper AmigaOS made Commodore assuming Bridgeboard are no longer useful and deprecate them, not developing any software updates valid running with 3.0 and 3.1.

What a Pity.

I remember my bridgeboard Amiga buddy Giuseppe was forced to bought a Multikickstart card with 3 roms space, putting Kickstart 1.3, 2.0.4 and 3.0 kickstart versions on his A2000.

When he wanted using Bridgeboard he booted from 1.3 or 2.0.4.

When he wanted modern Amiga system he booted from 3.0 kick rom.

[wbrejnia]

WOW!!  All the feedback and ideas.

Dandy, you will be on next Cover of Bridgeboard for Dummies Book Version 1.2.

You guys are amazing.
I have so much to think about, but my next step after being busy last 2 days is.

1) GET OLD KICKSTART 1.2 ROM back into Motherboard.

What kept me busy is.....

- I took apart the whole system, and rebooted things to see error messages
- Like what happens when no bridge board (Janus.library Error)
- Like when no 5.25" disk on Amiga PC (won't boot, from external 3.5")
- I left HD Controller in but didn't hook up Hard disks.
- etc etc (many combination tried to see things broken on purpose)

What I learned is EVERYTHING is working when I put everything back.
*** NO ERROR MESSAGE *** Means Good.

Now I started having some very particular issue with the Hard Drive.
** THIS IS THE ROOT CAUSE OF ALL MY PROBLEMS **

Sometimes the MBR (Master Boot Record of Hard Drive) doesn't get picked up.
->IT IS NOT THE RLL HARD DRIVE (itself)
->IT IS NOT THE Western Digital RLL Controller

->Basically it is intermittent.   The MBR is on the DISK but it doesn't alway get picked up by DOS.
-> DOS loads the MBR into memory ONCE and never goes for it again (based on my reading)
-----> That is why disk will continue to work, even if you wipe out, destroy the MBR.  It is in DOS memory.  JUST DON'T Reboot.
-----> That is why you have to reboot after FDISK Partition Change.  Same for ADISK.

So before when I thought I had a Hard drive problem, I wrote back to MBR and messed it up.  Maybe two years ago and certainly early a few weeks ago.

SO I HAVE EXTENSIVELY TESTED THE HARD DRIVE

First I did a low level format with optimal parameters.
Not a single back sector!!
I learned this because at end of LL Format there is a list of errors and you can format again. List was empty.  RLL drive is ZERO ERROR FREE!!

Norton Disk Utilities (PASSED 100%)
The Norton Tests are very VERY thorough.   Some test (like Calibrate) are very aggressive and make the head go back from First to Last Cylinder very quickly to test response. BOY that make the table shake, but drive passed with high rating.
It checked many many things.  Memory, speed, interleave, Controller Response, etc ,etc ,etc
ALL tests passed 100%.

Next I ran Spinrite
Many similar tests,  even recommended drive is safe for low level format and gave me recommendation to change Interleaving from 4 to 5 to get 560% throughput improvement.  Same recommendation as Norton did.
I even ran the 5 pattern read write test that would run for 6 hours on 32 MB of disk (After 1 hours I stopped it).
Disk and Controller came back PERFECT all tests 100% pass!!
Not a single bit of error anywhere for a 25 year old disk (but used so little.  I probably used it over last two weeks than 20 years).


So it's not the controller, not the Hard drive.
Could it be the cable?  What else to have a MBR intermittently not pick up.
The MBR is in the first sectors of the drive where it was LL-Formatted and extensively tested.

The behavior of the AMIGA PC IS this.
a) Drive light flashes long and slow many times after hard boot and initialization of PC.  
b) Then it give up on C: drive boot and goes to Floppy
c) If MBR is picked up.  The computer is PERFECT
d) If MBR is not picked up, NO MBR means no Partitions, no C: drive nothing
e) I even did a FISK /MBR to write a MBR back.  That works.
g) I made a Norton DiskTOOL rescue disk. I saved MBR, BIOS, and Partitions to a floppy.  So anytime I can load everything back (so don't have to partition, format, install software all over again)

I think this intermittent MBR is also the reason why the ISA/IDE Adapter doesn't work properly.
I think this intermittent behavior is a conflict of some kind.   Again the Wrong Kickstart?  Maybe.
I think why AWRITE and Aread don't work is related
I think why FORMAR JH0: doesn't work is related.
Dandy's many points above make sense.  

I was thinking borrow ribbon cables from 486.  But these cable work fine during hours of DISK Analysis.

WHAT COULD AN INTERMITTENT MBR load be caused by?


IS IT THAT KICKSTART CHIP I bought (EBAY) two years ago just for FUN to Try WORKBENCH 3.1 (that is when I first tried to fix the A2000)
I put it in after I gave up on Hard Drive (two years ago, but now I know my cables were reversed!!)

IS THIS MY PROBLEM (O.S 3.1 Version 40.63)?  
What kickstart is this?  (I just googled "Kickstart version 40.64 O.S 3.1 and nothing comes up  "V40" is Kickstart 3.0 )

https://en.wikipedia.org/wiki/Kickstart_(Amiga)

Released FOR AMIGA 1200, 4000T (NOT FOR A2000)
I just read that they needed to support SCCI and IDE in the rom so the moved out "workbench.library" from 512K ROM and it has to been on OS Hard drive.
but Amigakit.com sell them for A2000 http://amigakit.leamancomputing.com/catalog/product_info.php?products_id=157


Could explain why some of older disk INSTANTLY CRASH COMPUTER AND go into GURU error.  INSTANTLY as soon as disk goes into drive.

I am putting back original KICKSTART 1.2!!!  TODAY (and since all taken out, I'll put in that Replacement battery I bought)

Then I do more things.

[wbrejnia]

WARNING!


Bridgeboard Software works well with Kickstart and Workbnch 1.2, 1.3, and if I remember well, it works also with Kickstart 2.0.4.

It has some issues with 2.1 and does not work at all with Amiga Kickstart and AmigaOS 3.0 and 3.1 (could generate lots of Guru Meditations at any moment)

I remember my bridgeboard Amiga buddy Giuseppe was forced to bought a Multikickstart card with 3 roms space, putting Kickstart 1.3, 2.0.4 and 3.0 kickstart versions on his A2000.

When he wanted using Bridgeboard he booted from 1.3 or 2.0.4.

I just read this..... THIS IS MY PROBLEM!!!

[wbrejnia]

Now we have some scenarios:
Scenario A/Scenario B:/Scenario C:/Scenario D
Scenario E (wins)
1) Boot Amiga from floppy and run PCDISk
2) it initializes Bridgeboard ad activate ISA Slots
3) PC boots from C: partition on Hard Disk mounted on ISA Controller
4) JDisks make Amiga aware it exists virtual partitions files JH0: JH1: Etcetera upto 7 on PC Hard Disk partition C:
5) Amiga can transfer system from Floppy to JH0: as Dandy says, just as like any other Amiga real Hard Disk DH0: but it requires some time to boot and make all virtual partitions JF-X: visible back to Amiga side
6) Amiga will use JH0: As any normal real Hard Disk for the entire time of the session (remember it requires partitioning and formatting).

Scenario E is what would make me happy for many reasons.  Overcoming challenge is #1 priority.

But right now I want things to work, so I have choices for Final setup.

I haven't installed Gotek yet since too busy playing with RLL HD, ISA-IDE.

What I want is a Hard Drive on the Amiga 8088 PC side to Boot DOS from ISA-IDE /IDE-Drive (I want to sell the RLL&Controller).  Run Windows 2.0 (Real old Retro Feel) and maybe some MS DOS whatever (a classic DOS game or two).

BUT NO 5.25" Floppy needed for DOS PC boot.  Maybe even Amiga Explorer running from my ISA Serial Card to Amiga Serial Port (Null Modem) to demonstrate ADF extract/Import and Serial communication.

Then on Amiga Side, Gotek is good enough for Booting games.
For Amiga Workbench it could be Gotek but access to Amiga PC Hard drive would be a nice (BUS-to-BUS BRIDGING WORKS) demonstration.

All above just working to show a Demo of Old Technology, but still used basic concepts/principles of serial/parallel communication, bit, bytes, handshaking, interfacing, etc.

I might donate A2000 to my sons High School they have a computer/robotics lab and learn basic concepts in Grade 10 which he is in.

Kind of like when they do Photography course they start with taking Film Photography and developing their own Paper B&W photos.

I could always come by a visit the A2000, seeing the kids amused by the A2000 and taking 20-Mpix Photos of it.
(Each photo on their Pocket phones a big as my Whole Hard RLL Hard Drive which holds 2 Operating systems and some SW proven useful years ago).
The Amiga 8088 screen PC resolution equivalent their photo thumbnail on their phone.
As they laugh at A2000, push the Gotek selector and run a Copy of Galaga or Galaxian with the Epyx Joystick (That will stop them laughing and appreciate Gaming History).

If RLL drive doesn't sell then donate it too,  Remove HD Top Metal Coverbox and put a Plexiglass shield replacement on it to see it Disks Spin an Heads move, just like the robots they build in class.

BUT FIRST I Have to swap the Kickstart ROMs while I pray.

[wbrejnia]

Starting take apart A2000 for ROM chip swap, and Battery Install.

Here is one of RLL Drive Analysis Reports.  All the other passed just as well.

[ Norton Calibrate ] One test scared me, since so aggressive with the Head Motion Rapid swings!!

                             Norton Utilities, 6.01
                   

                            *************************
                            *  Report for Drive C:  *
                            *************************

                               LOGICAL DISK INFORMATION
                     -----------------------------------------
                        Media Descriptor:  F8
                         Large Partition:  No
                                FAT Type:  16-bit
                           Total Sectors:  63,336
                          Total Clusters:  15,794
                        Bytes Per Sector:  512
                     Sectors Per Cluster:  4
                       Bytes Per Cluster:  2,048
                          Number of FATs:  2 (PCdos) (AmigaDOS)
                     First Sector of FAT:  1
               Number of Sectors Per FAT:  62
                First Sector of Root Dir:  125
           Number of Sectors in Root Dir:  32
           Maximum Root Dir File Entries:  512
               First Sector of Data Area:  157


                            PHYSICAL DISK INFORMATION
                     -----------------------------------------
                            Drive Number:  80
                                   Heads:  4
                               Cylinders:  609
                       Sectors Per Track:  26
                           Starting Head:  0
                       Starting Cylinder:  5
                         Starting Sector:  1
                             Ending Head:  3
                         Ending Cylinder:  613
                           Ending Sector:  26

                                RELIABILITY TESTS
                     -----------------------------------------
                      System Memory Test:  Passed
                       Controller Memory: Passed
                  Controller Reliability:  Passed
                            Disk Mapping:  Passed
                    Allocation Integrity: Passed
                     Diagnostic Cylinder:  Passed
                        High Speed Timer:  Passed
                               CMOS Test:  Passed

                                   SEEK TESTS
                     -----------------------------------------
                      BIOS Seek Overhead:     5.44 ms
                          Track-to-Track:    13.90 ms
                             Full Stroke:    92.51 ms
                            Average Seek:    51.91 ms

                               ENCODING TECHNOLOGY
                     -----------------------------------------
                              Drive RPMs:   3,612
                            Sector Angle:   13.45ø
                         Controller Type:      XT
                           Encoding Type:     RLL

                                 INTERLEAVE TEST
                     -----------------------------------------
                          Interleave        Revolutions
                         ------------      -------------
                              1:1               26  
                              2:1               27  
                              3:1               28  
                              4:1               28  
                              5:1                5 (Optimal, and Tool Auto Adjusted the Hard Drive)  
                              6:1                6  
                              7:1                7  
                              8:1                8  

                            Current Interleave is 4:1
                            Optimal Interleave is 5:1

SURFACE TEST STATUS
                     -----------------------------------------
                                  Test Summary
                             ----------------------
                   Pattern Testing Level:  Standard Testing (40 patterns)
                          New Interleave:  5:1
Correctable Sectors:  0
                   Uncorrectable Sectors:  0

                      No Errors encountered in Surface Test
--------------------------------------------------------------------------

[wbrejnia]

Dandy,
I have comments and answers to all your detailed points.
I will hold off for now till I get that original KS1.2 ROM back in.
I'm hoping my answers will change.
I took screenshots of every test and procedure like Lo format.
EVen short movies of the boot behavior of HD.
So I will be able to clearly compare things.
One more day for downgrade I don't want to rush battery replacement install.

Wally

[leofoe]

WARNING!It has some issues with 2.1 and does not work at all with Amiga Kickstart and AmigaOS 3.0 and 3.1 (could generate lots of Guru Meditations at any moment)

My A2000 with Kickstart 3.1 rom and Workbench 3.9 works fine with it's Bridgeboard.

[wbrejnia]

My A2000 with Kickstart 3.1 rom and Workbench 3.9 works fine with it's Bridgeboard.

Maybe matching kickstart to workbench is the key.

I am running 3.1 kickstart and 1.3 workbench.

And does you setup work with access to HD on ISA slot side.
Does Aread and Awrite work from one side to other?

[wbrejnia]

Before I start the A2000 take apart I am going to try the copy of workbench 3.1

When i tried it only once two years ago I didn't set up things for Bridgeboard like including JANUS.library in the EXPANSION folder.

I just wanted to see the new Kickstart RoM working. I already gave up on the hardrive.

I am not even sure

Could it be possible that the removed libraries from ROM are on wORkbench 3.1 to make things work?

We'll see.

[wbrejnia]

I booted WB 3.1, and put in BB install disk.
A simply drag and Drop of JANUS.library wasn't possible since no space on WB3.1 disk.
Too complicated and I'm asking for Trouble.
Getting WB 3.1 working with Bridgeboard will be later.

Best just to take apart A2000 and put in Kickstart 1.2 ROM (Much safer from a OS perspective, [compatibility]).