#386BB Software
3 messages in this thread
Steven: I have RUN >NIL: Enforcer QUIET and then Binddrivers on the next
line.
If I comment out Binddrivers and run it later from the shell, the BB
speaker chirps and everything locks up! I've tried everything Ican think
of.
Thanks for your suggestion.
Dave Kay
Flying in from Montreal.
Dave,
Next time you run binddrivers, use any of the snooping utilities to
check and see if janus.library has been loaded into memory. The speaker chirp
is normal at the point in time when the BB starts the normal boot sequence.
You might check the version of Enforcer you are using. Don't use the one
that's on the Janus disk. Use a more recent one which you can download from
CIS. The latest is 37.52, I believe.
Have you been able to check the CMOS setup to be sure it conforms with
your BB hardware setup? That's important. Also be sure to run PCPrefs and be
sure everything there is set correctly. If so, then check your cabling to disk
drives, etc. Under normal circumstances there shouldn't be any problem with
the BB coming up. I've installed and used them in 2000s and 3000s without a
problem, so usually when something like this happens, it more often than not is
because something wasn't setup correctly or the BB itself is faulty.
PMFBI, but if the system is locking up before it completes booting, then I
don't think he has the option of getting to the CMOS setup on the BB side
(in the PC Window) 🙂
I believe that lock-up would be caused by a hardware conflict or
fault…probably a conflict with some cache or DMA peripheral…at least
that is what I've gleaned from the user's guides for the BB and other
peripherals (accelerators and hard disk controllers) and my own experience
with same 🙂
// daniel on autopilot in paradise
\X/ powered by intel and motorola