[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

4868.0. "MOUNTLIST SCSI Entries, anyone?" by XSNAKE::WILSONTL (Lead Trumpet (Read that...LEED!)) Wed Jul 03 1991 00:56

    Are MOUNTLIST entries used for the SCSI drives on AmigaDOS 2.0 at all? 
    Mine came without any entries at all for the two partitions, but it
    seems to work just fine.  I am curious...SID is not the happy camper
    without those three character device names to open.  (You have to click
    VOL and allow it to display them.)
    
    I did remove my ST277N from my A500 and plugged it into the 50 pin SCSI
    cable underneath the case of my 3000.  It booted up without a hitch and
    shows the two partitions on the ST277N as well as the original
    partitions. 8^)...Yes, indeed.... Oh, Joy! Four partitions, 116M (a
    veritable disk wasteland!)
T.RTitleUserPersonal
Name
DateLines
4868.1Rigid Disk BlocksTLE::RMEYERSRandy MeyersWed Jul 03 1991 01:4216
Re: .0

>    Are MOUNTLIST entries used for the SCSI drives on AmigaDOS 2.0 at all? 

Starting with AmigaDOS 1.3, mountlist entries are unneeded for any type of
bootable device under a controller that supports the rigid disk block standard.

Part of the information contained in the rigid disk blocks (the partition
information stored on cylinder zero of the disk) is all of the information
needed to construct a mountlist entry.  During the autoconfig process,
the controller reads that information and does the equivalent of a Mount
command.

That is why you can move a formatted and partitioned disk from one
disk controller to another and have the system recognize the partitions
automatically when the system boots.
4868.2IAMNRA::SULLIVANRed hair & black leather: my favorite color schemeWed Jul 03 1991 12:256
Only one small problem can creep up... what happens when the RDB gets blown?

A mountlist can be a wonderful backup...

	Thanks,
		-SES
4868.3Use Mr. Meyer's "MountList" program to make a backup!CRISTA::CAPRICCIOStuck in the H�2�WhoaWed Jul 03 1991 15:1213
� Only one small problem can creep up... what happens when the RDB gets blown?

� A mountlist can be a wonderful backup...

    That's where Randy's excellent MOUNTLIST program comes in handy.
    Discussed elsewhere, it will create a "mountlist" after reading the
    information in the RDB for a given device (that's been previously
    mounted).

    Question is, will it work under AmigaDOS 2.0? (or will the updated
    readme.txt explain that? ;^)

    Pete
4868.4The Mountlist ProgramTLE::RMEYERSRandy MeyersWed Jul 03 1991 16:1128
Re: .3

To save some people some time:

Mountlist is available from TLE""::UPORT$:[RMEYERS.TRADE.AMIGA]MOUNTLIST.ZOO;1

The Mountlist program writes to the the standard output a mountlist
entry for any device.  For example, if you say:

	mountlist dh0:

It will display a mountlist entry for dh0:.  In order to have the
security of having a mountlist for my hard disk, I gave the command

	mountlist >>devs:mountlist dh0: dh1: dh2: dh4:

And the additional entries were appended to my mountlist file.


>    Question is, will it work under AmigaDOS 2.0? (or will the updated
>    readme.txt explain that? ;^)

I'd like to be able to find out.  I suspect that the system data structures
that I am relying upon are fairly stable.  The only problem I would anticipate
is that AmigaDOS 2.0 might have some additional mountlist parameters that
my program doesn't know about.  Commodore did design the "environment
vector" for devices to be able to grow with additional information at the
end.
4868.5BAGELS::BRANNONDave BrannonWed Jul 03 1991 16:179
    the other way is to have the disk controller software write the RDB
    info to a file (assuming it will do that).  The Hardframe software
    can write a mountlist with the extra info it needs to create an RDB.
    That way you can use it as a mountlist for manually mounting the
    partitions or to recreate the RDB.
    
    I use Randy's program to sanity check that it did that correctly.
    
    Dave