Why isn't my A2000 loading Janus.library? (A2286 board)

[klokwirk]

I’m trying to get my A2286 MSdos card to fire up in my Amiga 2000 but it just aint talking to Ami. Pretty sure this was working nicely a year or so ago but I haven’t used it since then.


My Amiga2000 cold boots to WB no problems. Then about 30 seconds later the a2286 boots too. I can see it boots correctly from A: to the a DOS prompt as the display is on via its own VGA card and monitor. All looks fine until I enter a command but there is no response from the A2000 keyboard. Not even Ctrl Alt Del. Just to cover all bases, I removed the VGA card, cleaned card contact and inserted the A2286 in another slot. Made no difference.


On the Amiga side I tried loading PC Color, Mono and PCreset (PCprefs doesn’t open at all.)


And get the error “Could not open Janus.library ‘
So I downloaded the latest version of Janus and installed it using the second option A2088 or A2286 – no go.


SYSINFO Reports : Kickstart 40.3 , PAL -, ECS Anus – 2 meg – CPU 68030, FPU 68882, MMU 68030 (in use)
Boards report: 512K Zorro II A2288 Bridge Commodore 0
And if I check Devices there is no sign of Janus.


I’m stuck. Grateful for any help. What am I missing?

[Matt_H]

Are you 100% sure you have the latest Janus? The installer should have put Janus.library into Sys:Expansion. I believe you also need to be running Enforcer in order for it to work on your configuration.

[Gilloo]

Hello,
have you try with the command CPU NODATACACHE in the startup-sequence, before the binddrivers command ?

Take care that the janus.library is not in libs:, but sys:expansion, with its icon.

[klokwirk]

Sure as I can be. I searched the internet yesterday and downloaded Commodore Amiga Bridgeboard Janus Software 2.1 which I installed today with Enforcer selected. Also just to make absolutely sure, I have a copy of janus.library in Sys:Expansion as well as DH0: Devs , L and Libs.


Interesting though that Amiga says it ‘ Could not open’ NOT that it couldn’t find janus.library


Since I have an 030 processor I have made sure the DataCache is disabled as per install instructions


But now CLI says AmigaJanus is mounted so some progress I think.



I also tried Enforcer Version 37.73 from Aminet - no change.

[klokwirk]

Originally Posted by Gilloo

Hello,
have you try with the command CPU NODATACACHE in the startup-sequence, before the binddrivers command ?

Take care that the janus.library is not in libs:, but sys:expansion, with its icon.

OK - just tried this and removed janus.library from all directories except SYS:EXPANSION . Sadly no difference.

[Thomas Richter]

There is no need to disable the data cache completely. It is sufficient to load the mmu.library, potentially via the 68030.library. That is, either use the latest setpatch, put the 68030.library, the 680x0.libray and the mmu.library to libs: Or put the mmu.library to Libs: and run MuLockLib in the startup-sequence.

The data cache can remain on.

[SpeedGeek]

I already released a better performing alternative solution here:

https://eab.abime.net/showthread.php?t=113480

...and as I also explained here:

https://eab.abime.net/showthread.php?t=108534

An executable tool provides the ability to enable or disable the MMU as needed.

[Matt_H]

I think Commodore published several versions of Janus with the release name 2.1. In the latest version, Janus.Library should be v36.83.

[klokwirk]

Originally Posted by Matt_H

I think Commodore published several versions of Janus with the release name 2.1. In the latest version, Janus.Library should be v36.83.

I've installed every version of 2.1 including
CBM-AmigaJanus21-3683
CBM-PCInstall-322
CBM-PCInstall-331
CBM-PCInstall-334


No difference - Ami still says it cant load the janus.library


The A2288 bridge card is working but A2000 just cant communicate with it. This is Soooooo frustrating

[Thomas Richter]

Please provide an output of SnoopDos, ShowConfig, and also an output of MuScan.

[Matt_H]

@ klokwirk

This looks more like the data cache / Enforcer issue that others have provided more info on. As a reminder, if you try one of the old-fashioned solutions (i.e., turn off CPU caches or run Enforcer), remember to run those commands in the startup-sequence BEFORE BindDrivers. Also make sure that Janus.Library in SYS:Expansion has its accompanying .info file, which includes tooltypes that BindDrivers needs.

[klokwirk]

Originally Posted by Thomas Richter

Please provide an output of SnoopDos, ShowConfig, and also an output of MuScan.

Ran PC Colour and it gives me an error named PC Window 2.411 - which says it Could not open Janus.Library


SnoopDos output.....



Count Process Name Action Target Name Options Res.
----- ------------ ------ ----------- ------- ----
130 WBL OpenLib workbench.library Ver 0 OK
131 WBL ChangeDir DH0:PC
132 WBL Load SYS:PC/PCWindow OK
133 WBL ChangeDir SYS:
134 SYS:PC/PCWindow ChangeDir DH0:PC
135 SYS:PC/PCWindow OpenLib intuition.library Ver 0 OK
136 SYS:PC/PCWindow OpenLib graphics.library Ver 0 OK
137 SYS:PC/PCWindow OpenLib layers.library Ver 0 OK
138 SYS:PC/PCWindow OpenLib diskfont.library Ver 0 OK
/139 SYS:PC/PCWindow OpenLib janus.library Ver 0
140 ramlib Load LIBS:janus.library OK
141 ramlib OpenLib expansion.library Ver 0 OK
142 ramlib Open sysc/system/2500prefs Read OK
\139 SYS:PC/PCWindow OpenLib janus.library Ver 0 Fail


No install in my version of so still working on that


and ShowConfig.....


Date: 27/12/2019
Time: 1:9:52 pm
Day: Friday
Gfx Chipset: ECS
Processor: MC68030
Free Chip RAM: 789320
Free Fast RAm: 801560
Free Total RAM: 1590880
Overscan: 640*256
WBviewMode: -16384
WBcolours: 4 (2)
Mouse Coords: 11169


and if this helps, here is the startup-sequence


set echo on

; $VER: Startup-Sequence_HardDrive 40.2 (25.2.93)
; Startup-Sequence for hard drive systems

C:SetPatch QUIET

C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21

C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE

Assign >NIL: ENV: RAM:ENV
Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER

BindDrivers
;C:Mount >NIL: DEVSOSDrivers/~(#?.info)

;IF EXISTS DEVS:Monitors
; IF EXISTS DEVS:Monitors/VGAOnly
; DEVS:Monitors/VGAOnly
; EndIF

; C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s"
; Execute T:M
; Celete >NIL: T:M
;EndIF

SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart

C:AddDataTypes REFRESH QUIET
C:IPrefs
C:ConClip

Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities

;IF EXISTS S:User-Startup
; Execute S:User-Startup
;EndIF

Resident Execute REMOVE
Resident Assign REMOVE
Assign DOPUS: DH1opus
C:LoadWB
;EndCLI >NIL:

[Thomas Richter]

According to this output, the janus.library is present, but the bridge board is not showing up as a separate board in ShowConfig. This is the official ShowConfig, correct? If this is the case, then the autoconf logic of either the bridge board or the system installed in is defect as the board is never found.

Also note that the output of MuScan is missing, but this is probably secondary at the moment.

[klokwirk]

Originally Posted by Thomas Richter

According to this output, the janus.library is present, but the bridge board is not showing up as a separate board in ShowConfig. This is the official ShowConfig, correct? If this is the case, then the autoconf logic of either the bridge board or the system installed in is defect as the board is never found.

Also note that the output of MuScan is missing, but this is probably secondary at the moment.

Yes - I downloaded ShowConfig from Aminet yesterday. Also Sysinfo sees the cards including Bridgeboard card so it is recognised by Amiga.....

[SpeedGeek]

Originally Posted by klokwirk

Yes - I downloaded ShowConfig from Aminet yesterday. Also Sysinfo sees the cards including Bridgeboard card so it is recognised by Amiga.....

This Aminet ShowConfig tool is not reporting the Auto-Config Boards in the system. If you had used the AmigaOS ShowConfig tool it would do this.

It looks like you are missing the Binddrivers Janus start tool or icon from the Expansion directory. This tool typically binds the Auto-Config manufacturer and product number specified in the icon's tooltype to the Board. Otherwise, the janus.library can't find the Board. Also, I don't know why janus.library is located in the Expansion directory when it should be in LIBS: ?

[klokwirk]

Originally Posted by SpeedGeek

This Aminet ShowConfig tool is not reporting the Auto-Config Boards in the system. If you had used the AmigaOS ShowConfig tool it would do this.

It looks like you are missing the Binddrivers Janus start tool or icon from the Expansion directory. This tool typically binds the Auto-Config manufacturer and product number specified in the icon's tooltype to the Board. Otherwise, the janus.library can't find the Board. Also, I don't know why janus.library is located in the Expansion directory when it should be in LIBS: ?

The reason it's in expansion - See response 2 by Mat H above. In any case I have now copied janus into libs as well. Didnt help.

[Matt_H]

@ klokwirk

So, you’re saying that you have Janus.library and Janus.library.info in SYS:Expansion? That’s good.

But from the startup-sequence you posted, I don’t see the workaround commands necessary for Bridgeboard 030 compatibility. Remember to put either CPU NODATACACHE or Enforcer >NIL: before the BindDrivers line.

[Toni Wilen]

Expansion is correct, bindrivers loads all *.info files from expansion and then loads and initializes each resident file. Both janus.library and janus.library.info must be in expansion.

(Binddrivers method is basically "manual" autoconfig ROM emulation)

It returns confusing "could not open" because library init fails, init routine starts bridgeboard CPU, then it polls memory address in bridgeboard's shared RAM, if memory content does not change soon enough -> fail and exit.

But if VGA card shows activity, it probably means PC CPU did start properly and something prevents library init code to detect the changed memory address that PC CPU modifies very soon after it has been started. Perhaps there is something wrong in Amiga<>Bridgeboard VRAM communication? (or that 68030 cache bug..)

[SpeedGeek]

@ Thread

The SnoopDos report in post #12 shows janus.library loading from LIBS:

But I would check the Janus tools installer script to see what the default directory actually is just to be sure.

[Toni Wilen]

The SnoopDos report in post #12 shows janus.library loading from LIBS:

It makes sense because only binddrivers loads it from expansion and then if it succeeded, library stays in memory.

Which means: if any Bridgeboard utility program loads it from LIBS:, it means initial initialization (binddrivers) failed.

Binddrivers stuff is "different".

--

Better way to debug this is to remove binddrivers from startup-sequence. Boot normally, open shell window, start snoopdos, run binddrivers.