Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!rex!spool.mu.edu!cs.umn.edu!msi.umn.edu!math.fu-berlin.de!mailgzrz!opal!fauern!forwiss.uni-passau.de!platon.fmi.uni-passau.de!burkert1 From: burkert1@platon.fmi.uni-passau.de (Klaus Burkert) Newsgroups: comp.sys.amiga.hardware Subject: Re: A3000 and AT Bridgboard Message-ID: <1991May15.162316.26908@forwiss.uni-passau.de> Date: 15 May 91 16:23:16 GMT References: <21523@cbmvax.commodore.com> <1991May15.093100.10112@cc.newcastle.edu.au> Sender: usenet@forwiss.uni-passau.de (USENET News System) Organization: University of Passau, W-Germany Lines: 66 Nntp-Posting-Host: cicero.fmi.uni-passau.de In article <1991May15.093100.10112@cc.newcastle.edu.au> birjt@cc.newcastle.edu.au writes: > > >Hello, > I have just put a '286 bridgeboard in the A3000 here at work. Their >idea not mine! The set up included a hard disk controller as well which >had to go in the slot below the BB. This works fine except that the floppy >controller on the BB itself seems to be unavailable while the controller This is totally normal, since AT-HD-Controllers are usually Combicontrollers, i.e. they combine a HD- and a FD-Controller on one board. Because the PC does no AutoConfig (TM?) :-), each device must be jumpered to it's own address: If you have two floppy-controllers, you _must_ switch one of them to FDC#2 or disable it. >card is in place. This was no real problem as the controller card had its >own floppy controller as well, which I used. > You've done it right! > Now my main problems are: > 1) I can't get windows to install, although I hear there is > way to get aroung the keyboard.drv problem. This doesn't particularly > bother me as it was not one of the software items I guaranteed would > work. Windows 2.11 /286 works just fine, but it is not too useful... :-( Windows 3.0 has one problem: It's not the keyboard.drv (in my case), it's the lack of a suitible mouse-driver, because the C-A-supplied AMOUSE.DRV works only with Windows 2.11. Since there is no amouse.drv for Win30 available yet, you have two choices: - use Windows without mouse (very bad ) - use a MS-compatible serial PC-mouse with a serial Board. There are IDE-controllers with serial and parallel ports on board available. I don't know what type of HD you're using, but if it's not IDE you're lost until C-A releases a new amouse.drv. > 2) I can't get PCColor to work. If I follow the manual and > type mode etc. the whole machine hangs. If I change the jumper on > the BB (J14 from memory) then click on PCColor the machine crashes. > From what I can gather around here this is not normal behaviour, so > if there are no more hints from here I will return it to the dealer > for possible repairs. > I think you used the "save settings"-option of the PCWindow-Menu at PCMono. There should be a file named "SYS:PC/System/sidecarSettings" or similar. Erase it, open PCMono and PCColor _SIMULTANIOUSLY_, choose your options, and the SaveSettings. This should fix it. The problem is that SaveSettings sets the depth of the other screen to zero, when only one window is open and the file is newly created. Try opening a screen with depth zero and see what happens ... bang!!! > The A3000 works flawlessly, same as mine at home. > My A2000B too. > Thanks, have fun, > Russell > > BIRJT@cc.newcastle.edu.au ------------------------------------------------------------- Klaus Burkert email: burkert1@platon.fmi.uni-passau.de Brandweg 11 voice: +49-851/83993 D-W-8390 Passau / Federal Republic of Germany