Conference hydra::amiga_v1

    It all depends on the type of device you are using -- ST-506 or
    SCSI.

    One or the other or both would be just fine!!! :-)
    
    Trying to get a "feel" for what types of entries are in Mountlists
    for different hard drive configurations.
    
    Thanks again...

>    Fast File System?  If so, would you be kind enough to post it in


Why does the drive interface type matter for FFS? This should be transparent.
The file system talks in logical blocks, right? It's the device specific driver
that handles interface details (or am I missing a key point to mount lists?)

John

    
    
    /*  C Ltd  ST-277 N  32 Meg Hard Disk Drive */
    
             DH0:       Device = SCSI.device
                        FileSystem = l:FastFileSystem
                        Unit   = 1
                        Flags  = 17424434
                        Surfaces  = 6
                        BlocksPerTrack = 26
                        Reserved = 2
                        Interleave = 0
                        LowCyl = 0  ;  HighCyl = 405
                        Buffers = 9
                        GlobVec = -1
                        BufMemType = 0
                        #
    
    
    
             /*  C Ltd  ST-277 N  32 Meg Hard Disk Drive */
    
             DH1:       Device = SCSI.device
                        Unit   = 1
                        FileSystem = l:FastFileSystem
                        Flags  = 17424434
                        Surfaces  = 6
                        BlocksPerTrack = 26
                        Reserved = 2
                        Interleave = 0
                        LowCyl = 406  ;  HighCyl = 811
                        Buffers = 9
                        GlobVec = -1
                        BufMemType = 0
                        #
    
             SPEAKER:   Handler = L:Speak-Handler
                        Stacksize = 6000
                        Priority = 5
                        GlobVec = -1
                        #
    

Ed,  Seeing how you have a (insert-greek-letter-here) version of V1.3,

Hows the new SPEAK: device?  Does the translator speak english as we all
know it?

Joh

    SPEAKER: is now a physical device.  You can speak any text file
    quite easily by using the standard AmigaDOG redirection symbol...
    
    	'Type >SPEAKER: FILE.TXT'
    
    Maybe it's my imagination, but it does sound quite a bit better
    than the old 'SAY' command.  The voice still has a foreign accent,
    but I think they may have modified the phoenomes or whatever it
    is that needed to be modified.  My wife can clearly understand every
    word spoken, whereas she had trouble under 1.2.  She used to use
    'SAY' to proofread her documents.
    
    Being an engineer, I'm expected to be illiterate, so I haven't much
    need for proofreading.
    
      //
    \X/  Ed.
     

    Ed ---
    
    Did you have to run "prep" on your C Ltd hard drives?  If not, why
    not?  If so, how can you specify LowCyl = 0 when prep supposedly
    uses the first couple of cylinders for the old file system (as I
    understand it, anyway :-)
    
    Thanks,
    Kip

    My Seagate has an imbedded SCSI controller, making it a so-called
    'intelligent' drive.  Only ST-506 type drives require the small
    partition.
    
    Ed.

    Sorry, I used a misnomer in .8; my Seagate has an imbedded SCSI
    interface, not controller.  I use the standard C Ltd SCSI board.
    The main difference is that I don't need the OMTI adaptor.
    
    By the way, the model drive I have is ST-277N.  In Seagate-ese,
    the N standed for imbedded SCSI interface.
    
    Ed.

Actually, drives which have a 50 pin SCSI connector on them, have embedded
SCSI.  The interface type is SCSI, but the "controller" is also "embedded" or
Built-in.


John

Re: .7

>    If so, how can you specify LowCyl = 0 when prep supposedly
>    uses the first couple of cylinders for the old file system (as I
>    understand it, anyway :-)

Only the Commodore disk controller requires that the first partition
of device 0 (but numbered 1 in the mountlist, sigh!) be used with the
old file system.

The Commodore controller as a "feature" automounts the old file system
on the first partition.  I have a suspicion that this feature may have
been part of an early attempt at supporting boot from the hard drive.

Anyway, the old file system restriction only applies if you have the
Commodore controller and then only on the first partition of device
0.  So, if you use the Commodore controller with a SCSI disk, and you
set the SCSI disk's id to be drive 1, you can use all of the drive
with the fast file system.  Unfortunately, you can not do the same
trick with an ST-506 disk.  I think the problem is that you can not
have a ST-506 disk drive 1 without having a ST-506 disk drive 0.

So, the requirement that the slow file system be mounted on the first
partition is not a SCSI versus ST-506 issue, but a Commodore controller
versus somebody else's controller.  The issue seems to be a SCSI versus
ST-506 issue because there is a workaround for the Commodore controller
if you use SCSI disks.

    re: .11
    
    I have a hard time understanding this.  Do you mean that the Commodore
    controller (A2090) "knows" about the SFS disk format, and automatically
    "mounts" the disk without assistance from the operating system?
    
    If this is what you mean, I have a hard time believing it.  Various
    manufacturers (including IBM and DEC) have been making "smart"
    controllers since at least 1964.  Many of them have had autoboot,
    but none of them, even the smartest, have known anything about the
    file system.  Autoboot controllers know enough to read the header
    block (usually block 0) and find in it a pointer to the primary
    boot image, which must be in a set of contiguous blocks.  Non-autoboot
    controllers (like tha A2090) don't even know that much.
    
    There may be some reason why the first partition of unit 0 has to
    be formatted SFS, I don't deny that.  I just dispute the reason
    for it.
        John Sauter

    Does anyone know offhand which types of memory (CHIP, FAST, PUBLIC
    or whatever) correspond to the numbers you can specify in the
    BUFMEMTYPE field?
    
    (Presupposing one does not have access to /exec/memory.h)

Re: .13

>    Does anyone know offhand which types of memory (CHIP, FAST, PUBLIC
>    or whatever) correspond to the numbers you can specify in the
>    BUFMEMTYPE field?

	BufMemType=5		For fast, public memory
	BufMemType=3		For chip, public memory

Buffer memory should always have the public bit set, but current hardware
and software can't tell the difference.

    hi, i would like to know if anyone has a mountlist for an 
    NEC DEM-204N harddisk around.  i got the disk from a friend
    with no documentation, so i am not sure how to mount it.
    
    thanks in advance
    
    	jj
    

    I have a NEC hard disk, but I'm not opening up my case to read the
    model number. Is yours a 40 Mbyte? If so, I can give you the info.

    no, unfortunatley, i was told it is a 20MB.
    
    thanks
    
    jj