CompuServe Thread

#386 BB boot problems

12 messages in this thread
#95583From: Steve SetzerApr 14, 1993 8:34 PM
I have just recieved a new 386SX bridgeboard and am having trouble right off the bat. I have installed everything 4 times just to make sure everything went right with the install and get the same problem each time. My system: A2000 w GVP Combo 030 accelerator, running a 105 meg quantem from the combo board. (there is more in the system but this is all that seems relevent ie syquest, flicker fixer, another hd contoller with hd.) First I deleted all my old Janus files and virtual c: drive (fakec), ran the install program and let it build me a new virtual drive (DriveC), let install add enforcer, rebooted, installed MSDOS (all defaults), set up PCSETUP, added the Janus files in their own directory, added it to the path in autoexec.bat. All goes fine for this session BB boots up, does what it is suppose to, no error messages, it will also reboot fine, BUT when I reboot the amiga, the BB will not boot. I get the C= copyright and all ram is properly configuired but it stops cold right there. It will not recognize ctrl-alt-del, rebooting with PCReset starts it all over again and it stops right there again, tried rebooting with MSDOS in drive A same thing. It will only reboot correctly if I have DOS in drive a: the FIRST TIME after rebooting the amiga, then after that it seems to work fine, it will even boot off of the C: drive. There also seems to be a problem using amouse with dosshell, but that is minor, I just want to get this where I can boot without jumbing thru hoops. Is this some simple goof on my part or some glitch in the install program? Any help is greatly appreciated! …Steve ====>>> Motorola 68030 Inside <<<====
#95607From: Dave CinegeApr 14, 1993 10:24 PM
Sounds like you need to reseat your 386 board. What REV MB do you have? If you are still having problems call me tomorrow. Elite MicroComputers – Flying high on AutoPilot
#95706From: Steve SetzerApr 15, 1993 2:11 PM
As an addemdem to my other message: I also have a rev 4.4 motherboard, and the problem is sporadic sometimes it will boot, sometimes it will not, it doesn't always need the DOS disk in drive a:. ====>>> Motorola 68030 Inside <<<====
#95846From: Paul LakeyApr 16, 1993 10:20 AM
Steve, I had the same problems for quite a while, one thing that does help is to run a script which will run BINDDRIVERS and PCReset. Strangley the problems with my BB went completely after I installed a Cyrix co-pro to the BB, wierd I know but it now boots everytime without fail. It is possible that I had a seating problem with the board, but removing the BB and reinstalling it with the Co-Pro has solved ALL of my bootup troubles. Paul Lakey (UK) Enjoying AutoPilot!
#95889From: Steve SetzerApr 16, 1993 7:09 PM
Paul, Thanx for the tip! Are you saying run pcreset from the startup-sequence or just set up a script that will invoke bindrivers and pcreset each time I want to use pcreset? I have tried reseating the BB a couple of time already, am going to try moving the BB to the next slot over and see if that makes a difference (it is a pain in the @$$ to open my machine though). I do plan on getting a co-proc soon to but I have really overstretched my limits in the last few weeks (New syquest, 386 BB, DCTV, more RAM, and getting Imagemaster and VGA card this coming week!). Ao that is one thing going on hold for the time being. …Steve ====>>> Motorola 68030 Inside <<<====
#95932From: Don Curtis/SYSOPApr 17, 1993 1:16 AM
Steve, A script: pcreset binddrivers That's it. For whatever reason, it doesn't work if run from a startup script, but works fine if run by itself from a CLI. It's only needed ONCE, after that…everything seems fine…even with subsequent PCRESETS or CTL-ALT-DEL's on the PC side. Don
#96148From: Steve SetzerApr 18, 1993 6:18 PM
Don, Thanx for the reply, I have been trying that script althoug it is backwards from what I have ie binddrivers then pcreset, with no help at all. Will try reversing it to see if it works any better. …Steve ====>>> Motorola 68030 Inside <<<====
#96201From: Don Curtis/SYSOPApr 19, 1993 12:36 AM
Steve, Yes, it needs to be reversed, reset then binddrivers.
#95950From: Paul LakeyApr 17, 1993 6:05 AM
Steve, Yes set up a script that will invoke Binddrivers everytime you click on the PCReset Icon. I really wish I knew what I had done to my BB, I had just about given up getting it to boot reliably, until I fitted the Co-Pro. At least the Co-Pro is a cheap add-on, I got mine here in the UK for equiv $60 (Cyrix 387sx/25), I expect you can get them even cheaper stateside. Best of luck….. Paul Lakey (UK) Enjoying AutoPilot!
#96401From: Marion J DelandApr 20, 1993 6:58 PM
Steve… You added RAM? How much? You can't add a full 8 megs of Autoconfig RAM if you have a Bridgeboard..it needs some for itself. Also, did you maybe add a 68030? If so, you need to add ENFORCER QUIET to your startup-sequence before BINDDRIVERS. Also, did you maybe enter your C: drive in the hard drive setup? A MAKEAB drive goes in as "none"–like an 8-bit controller. I doubt that's the answer, since you said you can sometimes get to the CcC: drive, but I thought I'd ask. Marion CROSSINGS Newsletter for the Bridgeboard, etc.
#96450From: Nancy DevittApr 20, 1993 10:56 PM
A silly question…. What do you mean about not being able to add a full 8 megs of autoconfig RAM if you have a BB? I did. Or is 32 bit RAM not autoconfig RAM? I just ordered the card from the States with 4 meg, then decided on the additional 4 meg up here; went to the store and picked it up; popped the whole thing in. (These fine distinctions escape me. If I really get into trouble, I call "help" on CI$ and someone can usually come up with the answer.) Also, I have a 68030, but no ENFORCER QUIET in the startup-sequence. Could that be why I have to do a reset? (See – we need your book!) …..Nancy From Edmonton, AB, Canada
#96593From: Steve SetzerApr 21, 1993 8:26 PM
Marion, Thanx for the reply! Yes I have additional ram but only 3 megs in the autoconfig space, the rest is expanded 32 bit ram on the GVP board mapped high. The Janus 2.1 software added the enforcer quiet to my SS script, so that is not it…it really has me stumped, it seems to be working more often now than when I first installed it, the script Don Curtis recommended seems to help some but not all the time ie pcreset, binddrivers. I have checked everything but to no avail yet. Lat thing to check before I give up and try another board is to move it (BB) to the next slot. If I do this, can the first slot be used for the BB or will it be relegated to Amiga use only? Any advice or tips on anything else to try? thanx, …Steve ====>>> Motorola 68030 Inside <<<====