CompuServe Thread

Bnd Sgt

2 messages in this thread
#28427From: Dennis DranJan 2, 1989 1:19 PM
Don, The problem doesn't seem to on powerup. I took binddrivers out of the startup script. The Seagate autoboots Amigados ok, but I still get a crash when I execute binddrivers from a shell prompt long after Amigados is up and running (This is of course before I access the PC side, in which the first step would be binddrivers). As I understand it from the CBM rep, the wait problem is the Seagate delaying, and the Amiga not waiting, at the execution of binddrivers. Which I guess is why binddrivers boots the PC ok with a floppy as sys:. Also, binddrivers works ok from the Seagate if the Janus devicKf not in the expansion drawer. I guess ths, its not really doing anything. Somehow this must be related to the inability to jlink to the Seagate. The drive is powered by the Amiga and I do have the autoboot ROM. After crashing, if I wait at the guru screen the PC floppy light does come back on again ( I guess that's the completion of the Bridge diagnostics?). However a reset with CTL=Amiga=Amiga, apparently resets the Bridge connection also (When I come back up, and try to open the PC, I get a "couldn't find library" error). I'm going to get back to GVP, they seemed to be familiar with this drive. Happy New Year. Dennis
#28555From: Don Curtis/SYSOPJan 3, 1989 1:45 AM
Dennis, If the Seagate is already running (since you seem to have booted from it)…there would be no delay. What files are in your expansion drawer? Also, make sure they are correct…that is, re-copy the 2 files (that's all there should be Janus.library and Janus.library.info) into that directory. The drive is not your problem…JLINK doesn't even try to link up until the PC side boots…and as you've noted, that happens after your crash. Try this, boot up, but don't issue the binddrivers command. Then, from a CLI, type LIST SYS:SIDECAR See which drive is accessed, and which files are listed. There are 2 that must be there…they are called PCBoot and 2500Prefs. Don