Wanting to check out if my Peg drive is working so I downloaded this little device driver:
http://mos.aminet.net/package/driver/media/trackdisk

that brings my Peg disk drive into the MOS world (thanks to Phantom).

The main device driver file has to be copied into the Devs directory and this is what I simply did. Then a mountlist text file got to be written that would include some instruction to the system for the driver. Following the instructions of the developer I wrote the mountlist text file and placed also into the Devs directory.

When I am running the preferences program of the device driver the drive seems to work. But I get no auto mounting of a disk -probably this should bring an icon into desktop like the old Amiga?- and when I am trying to mount by command line usage, I am taking those error messages:

mount df0: from mountlist <enter>
Device df0: not found in file mountlist


mount 0 form mountlist <enter>
Object not found

Only when I type:
mount from mountlist <enter>
I take no error message but still the drive is not reachable after a df0: <enter>.

Has any one tried this and can give a help.

*I used the mount command and the mountlist text file remembering that back in 1.3 days such file was important for device drivers to be recognised. Since the readme was asking for something similar I decided to handle that way.

Bellow follows part of device?s readme plus the mountlist file example.

1. Description
------------------
This is a MorphOS-native driver for built-in Pegasos floppy drive.

2. Usage.
------------------
In order to use this driver copy it into DEVS: directory and write a mountlist
for the device. Here is an example for fat95 filesystem:

/* MS0: fat95 PC file system for floppy #0 */
/* $VER: fat95 file system 3.06 (08-Aug-2002) by Torsten Jager */

FileSystem = l:fat95
Device = trackdisk.device
Unit = 0 /* change drive number here */
Flags = 0
LowCyl = 0
HighCyl = 79
Surfaces = 2 /* bootblock values have priority over these */
BlocksPerTrack = 18
Buffers = 20
BufMemType = 1
BootPri = 0
Stacksize = 4096
Priority = 5
GlobVec = -1
DosType = 0x46415400

This driver comes with the preferences program which allows you to set number of
track read retries and turn on "No click" mode.

NOTE: Remember that in "No click" mode you need to issue a DiskChange command on
the drive in order to detect disk insertion! You can turn on and of this mode
using the supplied preferences program. The only exception is complete
(non-quick) formatting a blank disk - the driver will forcibly check for the
disk presence before formatting.

NOTE 2: This driver is intended to operate Pegasos hardware. It will not work on
classic Amigas with MorphOS!

3. Limitations
------------------
1. Unfortunately Pegasos has the same floppy controller as common IBM
PC-compatible computer so it can't read native Amiga-formatted floppy disks.
Only standard PC format is accepted (1.44M for high density disks).

2. "NoClick" mode requires to issue DiskChange command on the drive after you
insert a disk for the driver to detect it. Automatic insertion detection in
this mode is impossible with this floppy controller. However you don't need
to issue DiskChange command before Format command when doing full format.

3. Raw encoded track reading and writing is also impossible. So you'll be unable
to read and write for example old Apple GCR-encoded disks.

4. Reading and writing sector label area with ETD commands is impossible,
supplied sector label buffer will be ignored.

5. Precompensation values and step delays specified in unit structure are
ignored.
Making use of these values is impossible.

6. Only high density (1.44 mb) disk format is supported.


[ Edited by CountRaven on 2008/1/26 3:25 ]

The example you show has no references to DF0, so it obviously wont work trying to mount DF0. You can rename your mount list to DF0 and put it in Devs/DOSDrivers or Storage/DOSDrivers if you don't want it mounted on startup. If you prefer to use Devs/Mountlist you need to put a header on the mount entry, ie. a line with "DF0:" before the rest (IIRC).

Thanks for the answering. I did what you suggested. I renamed the
moountlist to DF0 and copied to Dh0/MorpOS/Devs/DOSDrivers as well as
in Dh0/Devs/DOSDrivers. Still got no reply when I type df0: on CLI
-would get Insert volume Df0 in any drive... message-. But strangly
when I open DOPUS the led of the drive would turn on and the drive
seem to work with no stop asking for a disk -like in Amiga- but when I
put one inside nothing happends. I think that I am on the end of the
road but still something is missing. Any suggesitons? (please not that
I have copied trancedisk.device file to Dh0/Morphos/devs directory.
Should I copy it anywhere else?

[ Edited by CountRaven on 2008/1/27 15:31 ]

update: I also add the df0: line in the beginning of the DF0 -pre
mountlist- file.

Well all I want is a disk drive detection. Hopefully an icon on the
desktop when I insert a disk and if this is too much, a detection of
df0 from programms and CLI.



[ Edited by CountRaven on 2008/1/28 0:53 ]

Well... I'm not sure what you're doing... it's not entirely clear from your messages. Maybe someone else who actually used the thing can help you. I'm guessing you're not too familiar with mountlists etc.

Thanks for the reply. Well to put it simple when I refer to mountlist I basically mean a text file in which I have pasted the example given by the driver author. I copied the file in all my Devs/DOSDrivers folder -both in dh0 and dh0/Morphos-.

After your adivce i renamed the text file from mountlist to df0 and I add the df0: line in the beginning of the file like you pointed.

The drive seems to work but sitll no way to view an 1.44mb disk by typing df0: from CLI or by waitting an auto mount on the desktop when I insert it.

Thanks for all the kind help. I do not weant to confuse people with my messages and I always try to explain thing clearly. No I am not familliar with mount lists. Hm I think it would be a good idea to dorp an email to the driver author as well.





[ Edited by CountRaven on 2008/1/28 0:57 ]

Let me clarify, if you use DEVS:Mountlist and not a mount file in DOSDrivers you need the device name before each entry (and a # after I see now :)). This is not needed (allowed?) for mount files in DOSDrivers since they only contain the single entry, and the file name == device name. Also until you actually verified the device is working you should probably keep it in Storage/DOSDrivers, then move it to DEVS:DOSDrivers once you got it working.
Oh... and don't put 3rd party stuff in MOSSYS:, it'll be found just fine in SYS:, also there's definitely no reason to have duplicate files in SYS:/MOSSYS:.

1. Don't put the same stuff in both MOSSYS:DEVS and DEVS:. Put it only in one place. The proper place is DEVS:, MOSSYS: is intented for MorphOS components and not for 3rd party things. Avoid modifying it as long as possible.
2. Forget about DEVS:Mountlist. It's obsolete thing and it's still there for legacy purposes only.
3. Do you have 'NoClick mode' activated? If so, the driver won't detect disk insertion by itself, you'll have to kick it using 'DiskChange DF0:' command after you insert a disk. It's hardware limitation, there's no way to implement silent autodetect.

1. Removed the driver and the df0 textfile everything from MOSSys and
MOSSys devs

2. Copied the Driver on DH0/Devs and the DF0 text file on
DH0/Devs/DOSDrivers

3. Mounted the drive once from CLI moving to DH0/Devs/DOSDriver
Directory and typing "mount DF0" got no error message. DF) text file
includes EXCACTLY the example list if I add DF0:# on the very first
line -like adviced- would get error message after the mount DF0
command.

4. Disable NoClick Mode from Drivers PRef programm to avoid DiskChange
DF0 command ussage in any case command would not detecd DF0.

5. DF0 is not detected -still- after a simple DF0: command on CLI.
Drive would only again work only after the launching of DOPUS but
sitll no DF0 button anywhere.

6. Prefs software works fine setting on/off the noclick mode. This is
the seocnd case where I get the drive working.

7. I guess there must be somethign wrong with the naming. I mst
specify somewhere in the DF0 text file the Df0 naming. But where? And
how?

8. Perhaps someone could please send me a correct and working
mountlist text file -the one I have renamed to DF0- email @
chris.countraven@gmail.com I also emailed to the author but got no
reply.

I would try a little more if it would not wokr I would simple put away
the driver.

Note that the text file mountlist ha sbeem rename to DF0 and ha sbeen
put to DH0/Devs/DOSDrivers

Sorry for the info bombing and for my sticking to this topic. Those
are my last tries. Then I would simply erase the driver.

I see there are still some comprehension issues, it seems you even missed the reply from the author in this very thread. Well... if you're lucky, someone else might manage to help you :)

Oh ! I apologise! I did not realise that there was a reply from the
author! I simply do not know who is who in here! So I am kindly taking
back the "I emailed to the author but with no reply" line. Actually in
my email I gave the excact link in here trying to describe the
problem.

Anyway! Kindly thanks for everything !!!! Would stick on it trying to
fιnd the current way to define the drive name. In the file!
Thanks!


[ Edited by CountRaven on 2008/2/3 17:45 ]

[ Edited by CountRaven on 2008/11/25 22:34 ]