Welcome, Guest. Please login or register.

Author Topic: Workbench 3.1: Expansion Directory  (Read 5387 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Matt_H

Re: Workbench 3.1: Expansion Directory
« on: April 10, 2010, 02:45:31 PM »
Yeah, Expansion is for soft-loading drivers for cards that don't Autoconfig. XSurfIDE, as mentioned, goes in there, as do Bridgeboard drivers and some SCSI controllers (such as the C= 2091 and GVP cards with the autoboot jumper disabled).
 

Offline Matt_H

Re: Workbench 3.1: Expansion Directory
« Reply #1 on: April 11, 2010, 11:52:26 PM »
Quote from: sim085;553052
and what about the Libs directory? isn't that also for hardware drivers?


Nope, that's Devs:.
Libs: is for .library files - shared collections of functions to support programs. GUI toolkits (Gadtools, Triton, MUI), the standard file requester, the AmigaGuide logic, the ARexx internals, those are all libraries.

That being said, some hardware manufacturers did use Libs: for software support (toccata.library), but it's a software interface to the hardware in a slightly different way then a .device, I think.
 

Offline Matt_H

Re: Workbench 3.1: Expansion Directory
« Reply #2 on: April 12, 2010, 08:55:59 PM »
Quote from: Zac67;553174
Actually, it's not a question of AutoConfig (apart from a few exception ALL Zorro cards do), rather whether the driver is provided by a BootROM or via BindDrivers. ;)


Doh! Of course! Thanks for the correction.