Dandy,
Some great information here.
I agree with your boot sequence (my system was similar).
Fine.
- Amiga Booted Intially from A WB disk (I still have 2 WB disks from the past) But don't boot (all files intact on WB disks). Assumption is OS is corrupt on Floppy.
OK.
What WB disks do you have?
For example - the complete set of "Workbench" disks of OS version 3.1 consists of 6 DD floppy disks wich are labeled as follows:
1) Install - Version 3.1 (contains the installer to install the complete OS on HD)
2) Workbench - Version 3.1
3) Extras - Version 3.1
4) Locale - Version 3.1
5) Storage - Version 3.1
6) Fonts - Version 3.1
Initially I had to boot my Amiga from the WB floppy disks.
Then I had to prepare the drive(s) with the Boil3 software (from a backup copy of the Boil3 floppy disk - entering drive geometry data & saveing, mounting the drives).
Then I had to install the OS on the HD from the "Workbench" floppy disks.
As I already mentioned, my RLL HD setup had no autoboot option - so I had to boot from a "special bootdisk" floppy.
As I had booted the OS (from the floppies), I could insert a blank DD floppy disk into a floppy drive and format it as bootable disk from the Workbench. This way the my "Bootdisk" was for the same OS version that I used to boot from the floppy disks, e.g. "HD-Bootdisk 3.1".
First I created the necessary directories on this Bootdisk:
c
devs
l
libs
s
system
t
Then I copied all the system files to this "special bootdisk" floppy into the relatred directories required to "boot" the Amiga to such a degree ("minimum system") that it could load the required Boil files, mount the HD(s) and finally move the system was over to DH0: and the startup-sequence on DH0: was executed.
The startup-sequence of this "special bootdisk" floppy for OS 3.1 looked like this:
;run system/cli
;add32bit-special resetfest
;setcpu cache burst fastrom config 2 trap 2
fastmemfirst
addbuffers >nil: df0: 35
addbuffers >nil: df1: 35
boilexists
IF WARN
boilchipmodule devs/boil.device 1 > nil:
boilchipmodule devs/nucleus003.device 1 > nil:
ENDIF
boilmount
addbuffers >nil: dh0: 35
;addbuffers >nil: _dh0: 35
addbuffers >nil: dh1: 35
movesys dh0:
dh0:c/execute dh0:s/startup-sequence
When I switched on the Amiga with the Bootdisk in a flppy drive, it started to boot the floppy and after a few seconds the HDs spun up and the complete Amiga operating system booted from HD.
- WB DISKS (Startup-Sequence) in those disks shows a mount of JH0: (vi DJMOUNT) and all directories (Mapped to JH0:xxx) which means the Amga then booted off the Image of AmigaOS (off the PC Hard Drive thru the Bridgeboard/Janus)
- JANUS (is in the Expansion Folder) of the WB DISK
So far it seems to work analogue to my setup.
- How the PC side worked is a mystery (Maybe I only used floppies, or maybe there is also a MDOS partition on the PC Hard Drive)
Have you already tried to find documentation/manual of your bridgeboard on the web?
There the "mystery" should be explained...
--------------> or it worked like your setup (the C: HARD drive DOS Partition on the PC side just booted)
- I'm not sure how things happened exactly (BOIL doesn't sound familiar at all)
- Biggest OBSTACLE is that (Hard Drive Controller and Hard Drive) COMBO are (c: PHYSICAL DISK) not seen by the PC Side (via FDISK or ADISK)
--------------> I can talk to the Controller via DEBUG
--------------> Controller appears to be talking to the HARD DRIVE
--------------> Perhaps the Level Format using (DEBUG) is required for that C: drive to be seen (doesn't seem right, but who knows)
As we don`t know how your bridgeboard works all we could do is guessing, which mostly leads to nowhere.
Best idea is to get the manual and see if and how the HD can be used from the PC side.
In my setup, the Vortex ATonce 286 classic software had to be installed on the Amiga side. In its Preferences, you could select the boot method (IIRC, M$-Dos formatted HD partition or HD-file in Amiga format, or floppy disks) and then all you had to do to start the PC (in my case from M$-Dos formatted HD partition) was double-clicking on the ATonce icon on the WB.
My comment about the 486 was that I wanted to use it to get the WD-HardDrive-Controller working on it to get access to the Hard Drive. (Similar to the setup on the A2000/PCside)
IF there really is a M$-Dos formatted partition on the HD, then you could see it this way.
But as your setup seems to work similar to my setup, I would assume there`s already an Amiga partition on it. And if you succeed to boot that, I`m quite confident you can start the pc from there.
I think the trick is to get the Amiga to boot from the HD (which possibly requires a "special HD boot disk" similar to what I used on my setup.
If you could find the installation files for your bridgeboard, it could be that it offeres the option to create such a bootdisk.
I have some ideas, and thanks for the DOPUS program, that might be handy.
You`re welcome!