Welcome, Guest. Please login or register.

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

Description:

0 Members and 1 Guest are viewing this topic.

Offline rkauer

  • Hero Member
  • *****
  • Join Date: May 2006
  • Posts: 3263
    • Show only replies by rkauer
Re: Workbench 3.1: Expansion Directory
« Reply #14 from previous page: April 12, 2010, 05:55:29 AM »
Correct!
Goodbye people.

I\'ll pop on from time to time, RL is acting up.
 

Offline sim085Topic starter

  • Hero Member
  • *****
  • Join Date: Aug 2008
  • Posts: 958
    • Show only replies by sim085
Re: Workbench 3.1: Expansion Directory
« Reply #15 on: April 12, 2010, 08:49:31 AM »
So just to be sure, does it mean that 'devs' is for drivers that are for hardware that auto configure, while 'expansion' is for drivers that are for hardware that do not auto configure? (such as some accelerator cards?)
 

Offline Thomas

Re: Workbench 3.1: Expansion Directory
« Reply #16 on: April 12, 2010, 11:40:01 AM »
Quote from: sim085;553106
So just to be sure, does it mean that 'devs' is for drivers that are for hardware that auto configure, while 'expansion' is for drivers that are for hardware that do not auto configure? (such as some accelerator cards?)



No. The Devs directory is for files ending in .device, just like Libs is for .library. Expansion is for drivers which *could* be in an autoconfig ROM but aren't. For example the XSurfIDE driver contains 2nd.scsi.device which would normally go into Devs.

Drivers in Expansion *do* autoconfig, just not automatically through a ROM, but started manually by the Binddrivers command.

Drivers in Devs never do autoconfig. In order to use them either a program has to call them through OpenDevice() or a Mountlist specifying Device=name.device has to be created and mounted.

Files in subdirectories of Devs are not drivers in the narrow sense. They are just "descriptors" which are activated during startup. Most of them don't even contain code (like DosDrivers and KeyMaps).

Offline scuzzb494

Re: Workbench 3.1: Expansion Directory
« Reply #17 on: April 12, 2010, 01:28:31 PM »
Hi

Sorry if this has already been mentioned but,  I suggest you get a text editor like Cygnus ED [ CED ] and view the contents of your startup and user startup in S ... You will get a good feel of what is going on on your machine. You can also use CED to edit files generally and you will get a lot more information than the .info file. Make a back up of your S drawer and try not to mess with anything. DOpus is also very useful for viewing, copying etc drawers, tools etc.

scuzz

Offline Zac67

  • Hero Member
  • *****
  • Join Date: Nov 2004
  • Posts: 2890
    • Show only replies by Zac67
Re: Workbench 3.1: Expansion Directory
« Reply #18 on: April 12, 2010, 06:50:35 PM »
Quote from: Matt_H;552730
Yeah, Expansion is for soft-loading drivers for cards that don't Autoconfig.


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. ;)
 

Offline Matt_H

Re: Workbench 3.1: Expansion Directory
« Reply #19 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.