Conference hydra::amiga_v1

    Hi Gary ,
    		I use Crossdos Ok .  Can you give us more details of
    your mountlist, and startup-sequence.... i.e upload them.
    
    
    				Pete

    
    There is a file called MSDosFileSystem that must be placed in the libs:
    directory of your Workbench disk.
    
    Can you post a printout of the contents of your WB disk?
    
    Ed.

Here is my startup-sequence and my mountlist.msodsfs.

As to contents of Workbench I used the INSTALL procedure so I assume 
everything is there.

Greg

Startup sequence

c:SetPatch >NIL: ;patch system functions
Addbuffers df0: 10
cd c:
Sys:System/FastMemFirst ; move C00000 memory to last in list
resident CLI L:Shell-Seg SYSTEM pure add; activate Shell
mount newcon:
SYS:System/SetMap gb ;Activate the ()/* on keypad
LoadWB delay  ;wait for inhibit to end before continuing
path c: sys:utilities sys:system s: sys:prefs add
MOUNT_JDS DI0: FROM DEVS:mountlist.msdosFS
MOUNT_JDS DI1: FROM DEVS:mountlist.msdosFS
endcli >NIL:

Mountlist.msdosFS

DI0:
    Device = mfm.device
    Unit   = 0
    Flags  = 1                      /* Allow 5 1/4" drives */
    Surfaces  = 2
    BlocksPerTrack = 9
    Reserved = 1
    Interleave = 0
/*    SecOrg = 1 */
    LowCyl = 0;  HighCyl = 79     /* 80 track drive */

    FileSystem = L:MSDOSFileSystem
    Buffers = 5
    BufMemType = 0 
    Stacksize = 4000
    Priority = 5
    GlobVec = -1
    DosType = 0x4D534400
    Mount = 1;
#
DI1:
    Device = mfm.device
    Unit   = 1
    Flags  = 1
    Surfaces  = 2
    BlocksPerTrack = 9              /* 9 sectors per track */
    Reserved = 1
    Interleave = 0
/*    SecOrg = 1 */
    LowCyl = 0;  HighCyl = 79     /* 80 track drive */

    FileSystem = L:MSDOSFileSystem
    Buffers = 5
    BufMemType = 0 
    Stacksize = 4000
    Priority = 5
    GlobVec = -1
    DosType = 0x4D534400 
    Mount = 1;
#
DI2:
    Device = mfm.device
    Unit   = 2
    Flags  = 1
    Surfaces  = 2
    BlocksPerTrack = 9
    Reserved = 1
    Interleave = 0
/*    SecOrg = 1 */
    LowCyl = 0;  HighCyl = 79

    FileSystem = L:MSDOSFileSystem
    Buffers = 5
    BufMemType = 0 
    Stacksize = 4000
    Priority = 5
    GlobVec = -1
    DosType = 0x4D534400 
    Mount = 0;
#
DI3:
    Device = mfm.device
    Unit   = 3
    Flags  = 1
    Surfaces  = 2
    BlocksPerTrack = 9
    Reserved = 1
    Interleave = 0
/*    SecOrg = 1 */
    LowCyl = 0  ;  HighCyl = 79

    FileSystem = L:MSDOSFileSystem
    Buffers = 5
    BufMemType = 0 
    Stacksize = 4000
    Priority = 5
    GlobVec = -1
    DosType = 0x4D534400 
    Mount = 0;
#
DHI0:
    Device = scsidev.device
    Unit   = 1
    Flags  = 0
    Surfaces  = 6
    BlocksPerTrack = 26
    Reserved = 1
    Interleave = 0
/*    SecOrg = 1 */
    LowCyl = 732  ;  HighCyl = 811

    FileSystem = L:MSDOSFileSystem
    Stacksize = 4000
    Priority = 5
    GlobVec = -1
    DosType = 0x4D534400
    Buffers = 5
    BufMemType = 1 
#

    The symptoms you have described sound as if you have a one drive system
    and have not applied the TrackDisk.device patch. There is a Raw R/W bug
    in the 1.2 and 1.3 versions of Kickstart that only affects one drive
    systems.
    
    If you are on a one drive system use the TDpatch13 image to apply the
    patch (execute this progam in your startup). I have also heard that the
    SetPatch that comes with the 1.3.2 Workbench update fixes the trackdisk
    problem. The fix I use is a program called TrackSalve that came off the
    Usenet a short while ago that will also stop drives from clicking when
    empty as well as applying (what the author claims) the only patch that
    totally fixes all the things wrong with TrackDisk.device.

    Early on in my experiances using crossdos I had problems. What I
    found out is you want to put the command 
    		Mount_jds di1: from devs:mountlistmsdosfs BEFORE you
    encounter the loadWB command.Now this assumes you have the proper
    files in the devs:,and the libs: directory. In later commercial
    versions of CrossDos you have utilities like diskchange etc to make
    things nicer.OH! don't forget to format any floppies you want to
    use with Crossdos to reflect the file system you wish to use.
    							bill

    I know this may be silly , but I assume you have a 720k formatted
    MS-Dos disk in DI1: when you try to dir it.
    
    	TDPATCH13 is definitely NOT in your startup sequence.
    		( I suspect this is the problem )                            
    
    
    
    	I load in CrossDos after the WorkBench has loaded without any
    	problems.
    
    Check LIBS: also 
    
    			Regards
    
    				Pete

    re the patches.
    
    I have a TWO drive system, and the docu's supplied state that:
    
    a) Patches not needed for a two drive system
    
    b) The install procedure will install any necessary patches.
    
    I'll try moving the mount command tonight.....
    
    Greg

    I sent to the CrossDOS people for their latest update, and when it came
    it recommended (contrary to their earlier recommendations) that you
    install TDpatch1X even if you have a 2-drive system.  I have done this,
    with no observed ill effects.
        John Sauter

    Well last night I had another go, and it seems that the install program
    did not copy the msdosfilesystem file and the mfm.device file. I copied
    these and it still didn't work, I got an error message:
    
    Could not get information for di1:
    Error Code 218
    
    BUT!!
    
    This morning I deleted and recopied the files, rebooted and it seems to
    work. The only explantion I can think of is when I first copied the
    files, perhaps I removed the disks before all activity had stopped. I
    noticed that after doing a copy to my external floppy, after the prompt
    comes back, then a little more disk activity carries on, after a pause.
    I have corrupted one or two files by removing the disk before this has
    finished!!
    
    Just to wrap this up what do I have to do to install the patches?
    
    Many thanks for your help and suggestions, 
    
    Greg

    Hi Greg,
    		just add the line 
    TDPATCH13 >nil: to the startup-sequence after initial patch.
    
    By the way have you read about MSH discussed elsewhere in this
    conference . It's two way MS-Dos as I understand.
    
    			Pete