[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:	AMIGA NOTES
Notice:	Join us in the NEW conference - HYDRA::AMIGA_V2
Moderator:	HYDRA::MOORE

Created:	Sat Apr 26 1986
Last Modified:	Wed Feb 05 1992
Last Successful Update:	Fri Jun 06 1997
Number of topics:	5378
Total number of notes:	38326

608.0. "mount and mountlist params" by LAUSAN::BLANC (Phil Lausanne-CH 22-JUL-1987 14:57) Wed Jul 22 1987 13:04

    Hi,
    I need some infos about the MOUNTLIST file you can create to mount
    drivers(for foreign disks..for example) and its parameter
    I understand parameter such HEAD
    				MAXCYLINDERS
    but what about these:    FLAG
    			     GLOBVEC
    			     MEMBUFTYP
    
    Where or who can give me infos..??
    Thanks		Phil

T.R Title User Personal
Name Date Lines

608.1 Off the top of my head TLE::RMEYERS Randy Meyers Wed Jul 22 1987 19:25 22

T.R	Title	User	Personal Name	Date	Lines
608.1	Off the top of my head	TLE::RMEYERS	Randy Meyers	`Wed Jul 22 1987 19:25`	22
	Re: .0 MEMBUFTYP is I believe the flags to feed to the Exec memory allocation routines to specify what type of memory is desired (chip v. fast v. public, initialized to zero or left as junk). You can get the values of these flags from <exec/memory.h>. For example, if you had a mountlist for the built-in floppy, it would specify the buffers were to go into chip memory because the blitter is used to decode the information. GLOBVEC is for the BCPL global vector needed by the process. I think only device drivers written my Metacomco require their own global vector. (Global vectors are BCPL's version of the Exec's shareable libraries.) The ASDG Recoverable Ram Disk just didn't specify GLOBVEC. I think you shouldn't either. FLAGS I have no idea about. The ASGD RRD set it to zero. Seems like a safe value. All of these answers are nothing more than educated guesses. The following replies may show me not to be very educated.

Re: .0

MEMBUFTYP is I believe the flags to feed to the Exec memory allocation
routines to specify what type of memory is desired (chip v. fast v. public,
initialized to zero or left as junk).  You can get the values of these
flags from <exec/memory.h>.

For example, if you had a mountlist for the built-in floppy, it would
specify the buffers were to go into chip memory because the blitter is
used to decode the information.

GLOBVEC is for the BCPL global vector needed by the process.  I think only
device drivers written my Metacomco require their own global vector. 
(Global vectors are BCPL's version of the Exec's shareable libraries.)
The ASDG Recoverable Ram Disk just didn't specify GLOBVEC.  I think you
shouldn't either.

FLAGS I have no idea about.  The ASGD RRD set it to zero.  Seems like a
safe value.

All of these answers are nothing more than educated guesses.  The following
replies may show me not to be very educated.