CompuServe Thread

#A386BB Software

3 messages in this thread
#125549From: David KayDec 19, 1993 1:04 PM
I have just purchased a used 2386BB. I have an A2000HD with an A2630 board and one standard floppy drive. Installing the card went OK, but the AmigaJanus software is giving me a problem. Using the supplied install I get all the way to the end, then the machine locks up. I have traced the problem to the Binddrivers command. If I comment this out of my startup I can boot (but a few things don't work). If I leave in Binddrivers and comment out the "PRODUCT=513/1|513/103" in the Janus.library.info I can boot, but not use the BB. Can anyone out there offer any help. Thanks Dave Kay Flying in from Montreal.
#125674From: Steven D. KapplinDec 20, 1993 3:39 PM
Dave, My first guess is that you want to do the following in your startup: RUN >NIL: Enforcer QUIET Binddrivers If you don't run Enforcer, the Janus stuff usually won't work. Once you get to that end of the startup for the BB, you need to run PCPrefs and be sure that it's setup properly. The Janus memory segment should be set to D000. Also be sure you have the floppy drive setup done correctly and the desired video mode. If you use an external video card, you need to turn both mono and color video OFF in PCPrefs. When that's done you need to do a PCReset. Once the BB boot begins you will need to get into the CMOS setup on the BB side. You can do that by waiting until the memory check is complete, then press CTRL-ALT-ESC. When the setup screen appears, set the parameters you need for floppies, hard drives, video, memory, etc. If it isn't set correctly, the BB will tell you when it reboots. You must get everything set correctly for your system hardware. Hope this helps.
#125826From: daniel stripesDec 21, 1993 10:13 PM
Are you using a peripheral which uses cache memory (accelerator, hard disk controller, etc.)? The BB uses dual ported RAM and if this RAM is changed without the knowledge of your cache device, it can upset the applecart in your system and cause lock-up (probably messes up the stack but I don't know the exact details). You can check this out by disconnecting or disabling the suspect peripheral(s) and then rebooting the bridgeboard (binddrivers) and using PCReset and then opening the PC Window corresponding to your default mode (color or mono). // daniel on autopilot in paradise \X/ powered by intel and motorola