Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!unido!mpirbn!p554mve
From: p554mve@mpirbn.mpifr-bonn.mpg.de (Michael van Elst)
Newsgroups: comp.sys.amiga
Subject: Re: Make Disk Bootable & My HD Bug
Message-ID: <1417@mpirbn.mpifr-bonn.mpg.de>
Date: 6 Dec 90 23:55:42 GMT
References: <1990Dec4.132125.1351@vax5.cit.cornell.edu> <615@cbmger.UUCP>
Reply-To: p554mve@mpirbn.UUCP (Michael van Elst)
Distribution: comp
Organization: Max-Planck-Institut fuer Radioastronomie, Bonn
Lines: 17

In article <615@cbmger.UUCP> peterk@cbmger.UUCP (Peter Kittel GERMANY) writes:
>Binddrivers looks into the expansion drawer. It only activates drivers
>for which it also finds a .info file (don't know whether it also draws
>any information from the .info's or looks just for their existence, hmm
>but then it wouldn't really need info.library...).

Binddrivers searches the sys:expansion directory for all icon files and
looks at the tooltypes. The tooltypes contain the vendor/product code
of the board which should be associated to the driver. Binddrivers will
search the expansion board list and pass a list of the appropriate boards
which aren't configured yet to the driver program.

-- 
Michael van Elst
UUCP:     universe!local-cluster!milky-way!sol!earth!uunet!unido!mpirbn!p554mve
Internet: p554mve@mpirbn.mpifr-bonn.mpg.de
                                "A potential Snark may lurk in every tree."