#Another BB problem
11 messages in this thread
I've had an ongoing problem with my Bridgeboard which I've never been able to
get resolved. About a year and a half ago I corresponded with Commodore's
online help; after following a couple of suggestions which didn't work, I
wasn't able to get any further responses from anyone. So, here I go again… My
bridgeboard problem involves the communication between the IBM and Amiga when
the hard disk is mounted. I have an Amiga 2000 with Amiga 2090 hard disk, 2088
Bridgeboard, Workbench 1.3 and Janus 2.0. The only add-on I have is an 8-up
memory board with 3 meg (plus the 1 meg that came with the 2000.)
I should point out to begin with that if I boot up with a Workbench disk that
includes Janus 2.0 but doesn't mount the hard drive, everything works OK. The
jlink commands, etc are fine. I can set up virtual disks on the Amiga floppy
drives and RAD: and access them with no problem. On a reboot of the PC, I get
the "Janus Handler Version 2.63, Janus Library 33.1" message that you're
supposed to get.
However, when I install the Janus software on the hard disk, none of this is
true! I can run the bridgeboard, but once I enter "jlink", the 'a' drive on the
PC cranks for a moment, and then the PC "dies": nothing more happens, it
accepts no more input. The rest of the Amiga is unaffected. When I reboot the
PC, either with cntl-alt-delete or PCHard, the PC reboots, but I do NOT get the
handler/library messages.
I've tried all of the following without success:
1. I've compared the installed files on the hard disk with those of the Janus
installation disk. Everything appears to be in the correct directories.
2. I've removed all of the Janus software from the hard disk, booting from a
floppy containing the Janus software – but if the hard disk is mounted, the
same problem…
3. Going thru "appendix 5 – troubleshooting guide" from the Janus
2.0 manual: BindDrivers is included (after setpatch) in the startup-sequence;
The memory window in PCPrefs is set to E000 – I've tried D000 and even A000;
PC.boot and 2500 prefs are in the (apparently) correct directory; I've included
PCDisk in the startup sequence, and also tried removing it, clicking on before
entering PC, or even after entering PC; I've added "Mask=0" to the Mountlist
entry for the HD, and also removed it. One thing I HAVEN'T tried is copying
Janus to the non-FFS partition of my hard disk – but it's only 1 track and I
don't want to reformat the HD; besides, there's the same problem when Janus is
only on the floppy, and since the HD and BB are out-of-the-box Commodore
anyhow, I don't see that as changing anything.
4. Following a suggestion from Marion in the CPS Bridgeboard forum, I added
'wait 20' after the BindDrivers. Also tried a 'wait 200'.
5. I've tried disconnecting the extra memory.
6. Using the "snoopdos" utility from the Amigatech lib, I traced all of the
function loads for PC access both with and without the hard disk mounted.
They're identical.
7. I've ensured that the bridgeboard hardware is firmly mounted.
8. From an earlier suggestion from Commodore on-line help, I added a second
Binddrivers in my startup-sequence, after everything is assigned to my FFS
partition. The Janus.library is in the Expansion drawer of my boot disk. The
BB hanging occurs even when NO BB software is installed on the hard disk… It
would seem that not getting the version message upon reboot of the BB would
indicate that the wrong library is getting picked up, but I've verified several
times that there's no old libraries hanging around on the hard disk. With the
original Janus (1.0?) and Workbench 1.2 the BB was inconsistent (it was
well-known for its bugs), but I was able to get things to work (although often
losing the virtual disks). When I went to WB 1.3 this problem cropped up (it
had occasionally w/ 1.2). By including all of the Janus files on the WB disk
(following a suggestion found in "dos1.3.tips" in the amigatech lib), it sort
of solved the problem (though the virtual disks would still sometimes 'go
away'). When I went to Janus 2.0, though, I never did solve it. I installed WB
1.3 in March 90, Janus 2.0 in Nov 90. My neighborhood Amiga dealer doesn't have
any experience with the BB, and I don't know anyone else who has one – since
I've gotten things to work in a non-HD environment (and up til recently it
hasn't been a high priority), I've kept hacking away for a solution that should
have revealed itself by now.
Any assistance would be greatly apreciated!!!
Damon Short
Damon,
After exiting your startup-sequence, from a CLI type the following two
lines (or put them in a script file):
PCHard
BindDrivers
(or PCReset…depending on which version of the Janus software you have
)
Don
Don: > After exiting your startup-sequence, from a CLI >type the
following two lines (or put them in a script file): > PCHard >
BindDrivers > (or PCReset…depending on which version of the Janus software
>you have )
Thanks for the suggestion. Unfortunately, this doesn't work either. I've
even tried putting janus.library on the non-FFS partition of my HD, assigning
sys: to that partition and running binddrivers. "Snoopdos" shows that
janus.library is being loaded from that partition, but… no luck. –Damon
Damon,
then my last suggestion is to remove ALL of you Bridgeboard related
software from the Amiga AND the BridgeBoard…and then re-install both sides
from scratch. You don't need to remove MS-DOS or other files, just the JANUS
related file (such as AREAD/AWRITE/AMOUSE, etc.) on the IBM side.
On the Amiga side…I'd rename the SYS:PC directory to something else
and get rid of the janus.library and janus.library.info files from your
Expansion drawer(s).
Then…reinstall the Amiga side BB software, boot the BB and re-install
the janus related files on the IBM side.
Don
Damon,
To expand on Don's suggestion: from my experience you seem to have to wait
UNTIL the BB boots up BUT BEFORE any calls are made to the Janus system
(ie, AMouse, etc) What I did with mine is put a PAUSE in my autoexec.bat
BEFORE calling Amouse. In my user-startup I have a second script which is
RUN >NIL: (this allows the CLI to close) and in the script there is a 60
second delay which gives the BB time to boot. Then I do the PCHard &
Binddrivers commands.
I hope this helps:
Line in User-Startup
RUN >NIL: EXECUTE S:ResetPC
In s:ResetPC
WAIT 30 SEC
SYS:PC/PCRESET
BINDDRIVERS
In AUTOEXEC.BAT
@ECHO OFF
PAUSE
AMOUSE
ATIME
…
Andrew
Andrew, >>>>>>To expand on Don's suggestion: from my experience you seem to
have to wait UNTIL the BB boots up BUT BEFORE any calls are made to the Janus
system (ie, AMouse, etc) What I did with mine is put a PAUSE in my
autoexec.bat BEFORE calling Amouse. In my user-startup I have a second script
which is RUN >NIL: (this allows the CLI to close) and in the script there is a
60 second delay which gives the BB time to boot. Then I do the PCHard &
Binddrivers commands. I hope this helps: Line in User-Startup
RUN >NIL: EXECUTE S:ResetPC In s:ResetPC
WAIT 30 SEC
SYS:PC/PCRESET
BINDDRIVERS In AUTOEXEC.BAT
@ECHO OFF
PAUSE
AMOUSE
ATIME
… Andrew >>>>
Thanks for the suggestion. Unfortunately, this doesn't work either. I've
even tried putting janus.library on the non-FFS partition of my HD, assigning
sys: to that partition and running binddrivers. "Snoopdos" shows that
janus.library is being loaded from that partition, but… no luck. –Damon
Damon,
Hmmm. Sorry, I can't think of anything else for you to do. Have you had
the H/W checked to make sure everything is ok? How about testing it in
another Amiga? Unfortunately that's all I can suggest.
Andrew
I am coming in on this thread late but here goes: I get the message that Amiga
amouse and atime will not load. A reboot at this time gets thru OK. So I tried
a PAUSE statement at the beginning, pressing a key to continue after waiting
for up to a minute or so. My guess is that CONFIG.SYS is the culprit by
activating before the Amiga side has fully completed its machinations. Question
is: is there a way to delay config.sys from running? Repeating: a reboot of the
IBM side at anytime after opening the window runs OK. Any help is appreciated.
Ed,
Simply move the BindDrivers that activates the BB to the end of your
startup-sequence.
Don
Damon,
Why don't you remove Binddrivers from your startup sequence and let the
Amiga boot normally. Then run Binddrivers after and see if that solves the
problem. If it does, then you can use a script to start up the bridgeboard. I
use an ARexx script to manage the bridgeboard which is only run when I plan to
use the BB. I don't run Binddrivers during the Amiga boot.
damon,
Would you consider updating Workbench 1.3 to 2.0? Perhaps that'll
work!
via AutoPilot 1.03a