Amiga.org
Amiga computer related discussion => General chat about Amiga topics => Topic started by: sim085 on April 10, 2010, 10:48:30 AM
-
Hi,
Whenever I install some program I first check where this is installed on ClassicWB to see if I am putting it in the right place (at least from a philosophical aspect). Lately I was told to install FullPalette and in ClassicWB this was placed in the Expansion directory. In ClassicWB the Expansion directory also has FBlit, TMeter and other.
However on another thread I read that the BindDrivers command will load drivers from this location!! So does this mean that this is not really the place for such application (ex: FBlit, TMeter, etc?). If not then what goes in this directory? I know that mostly anything works anywhere, but what really should go here?
Regards,
Sim085
-
Lately I was told to install FullPalette and in ClassicWB this was placed in the Expansion directory. In ClassicWB the Expansion directory also has FBlit, TMeter and other.
This is wrong and has been fixed in the latest ClassicWB downloads. In the Expansion drawer only drivers to be loaded by the BindDrivers command may be stored. It's not a place to install programs to.
For example the XSurfIDE driver belongs into Expansion.
-
I never ever had anything in the Expansion folder on any of amigas, guess I've just been lucky with hardware.
-
The early version of prometheus.library was loaded by binddrivers. Then they moved to 21th century.
-
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).
-
Thanks for the replies. So basically this directory is mostly related with hardware rather then software. I just downloaded the last version of ClassWB lite and I see that now all programs that where in Expansion directory are now in System directory. Is this ok?
I know that everything works everywhere, but philosophically shouldn't tools like FullPalette and FBlit be in prefs?
-
I know that everything works everywhere, but philosophically shouldn't tools like FullPalette and FBlit be in prefs?
yes, probably. Maybe yes for Fullpalette but I can't say for FBlit ...
Btw, I'm one of the dim people who never got the difference between a 'tool' and a 'utility' :angry: can someone enlighten me ? :hammer:
-
My friend, the difference from tools and utilities are next to nothing at all.
Tools are used to modify something (like HDToolBox or Prepcard), utilities are things like screen savers, calculator, etc.
-
and what about the Libs directory? isn't that also for hardware drivers?
-
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.
-
FBlit should go in Workbench:C/
FullPalette is made up of a few parts. The main program "FPPrefs" goes in Workbench:C/, and the preferences tool "FullPalette" and its icon "FullPalette.info" go in Workbench:Prefs/
-
Thanks :) all the replies are helping me to learn a little bit more about Workbench. In the past I always used my Amiga to play games and now would like to explore a little more the reason why Workbench is structured as it is. Thanks again.
I am just realizing that Devs and Storage are practically the same. Is Storage use to backup stuff which otherwise would go to Devs?
-
Storage is intended to keep drivers and such that are no need to access at boot times.
Example: move to Storage/Monitors all the screen modes your monitor can't handle. If some day you got another monitor you can just move the new modes to DEVS:Monitors.
-
On a related note ... SYS:Storage/DOSDrivers is also part of the path where C:Mount will look for mountlist files, meaning you can type "mount mydevice:" in the CLI if you have a SYS:Storage/DOSDrivers/MyDevice mountlist file, and C:Mount will find it.
-
Correct!
-
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?)
-
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).
-
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
-
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. ;)
-
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.