home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!kithrup!hoptoad!decwrl!deccrl!bloom-beacon!eru.mt.luth.se!lunic!sunic!chalmers.se!dtek.chalmers.se!d1wzm
- From: d1wzm@dtek.chalmers.se (Kristian Wiklund)
- Newsgroups: comp.sys.amiga.hardware
- Subject: Re: Very strange DF0: problem
- Message-ID: <13522@chalmers.se>
- Date: 19 Aug 92 12:22:58 GMT
- References: <Krzysztof.05qi@netxsys.guild.org> <1992Aug16.165727.1629@posthorn.informatik.uni-kl.de> <1992Aug19.111330.20838@odin.diku.dk>
- Sender: news@chalmers.se
- Organization: Chalmers University of Technology, Gothenburg Sweden
- Lines: 34
-
- thomas@diku.dk (Thomas Nikolajsen) writes:
-
- >jmayer@bloch.informatik.uni-kl.de (Joerg Mayer (HiWi Buhler)) writes:
-
- >>> Here's an odd problem: a few days ago my DF0: stopped reading, writing, and
- >>> formatting Amiga disks. However, it still reads and writes MS-DOS disks
- >>> using MessyDOS.
- >..
- >>A reason I can imagine is, that the drive recognition at system startup time
- >>fails (i.e. trackdisk doesn't recognize unit 0 is present). I don't know how
- >>MessyDOS works, but if it doesn't use trackdisk (RAW-commands of course) and
- >>relies on the information provided in the mountlist it will simply try to use
- >>it.
- >..
- >>Joerg
-
- >MessyDOS' messydisk.device DOES use trackdisk.device,
- >it is used for reading (RAWREAD) and stepping (SEEK).
- >So, the problem could be other parts of trackdisk.device, the filesystem or..
-
- >- thomas
-
- Could it be the drive identification procedure?
-
- (*I* don't know, but the hardware ref. manual says that an
- Amiga drive is supposed to be able to identify its type
- when it recieves some special signal sequence)
-
- greetings from
- K. Wiklund / d1wzm@dtek.chalmers.se
-
- --
- ------------------------------------------------------
- This is a stupid signature.
-