Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!mit-eddie!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ames!ucsd!nosc!helios.ee.lbl.gov!pasteur!cory.Berkeley.EDU!koster
From: koster@cory.Berkeley.EDU.UUCP
Newsgroups: comp.sys.amiga.tech
Subject: Re: Trackdisk
Message-ID: <4212@pasteur.Berkeley.Edu>
Date: 1 Jul 88 20:12:20 GMT
References: <734@applix.UUCP>
Sender: news@pasteur.Berkeley.Edu
Reply-To: koster@cory.Berkeley.EDU.UUCP (Kevin Oster)
Organization: University of California, Berkeley
Lines: 21

In article <734@applix.UUCP> scott@applix.UUCP (Scott Evernden) writes:
>I am having a most difficult time trying to TD_RAWREAD and WRITE whole
>tracks from/to the trackdisk. ... 

  Could you have set the IOTDB_INDEXSYNC flag some how and set it up to
for a pattern that doesn't exist on the disk? How are you setting up
the iorequest block?

  I've never used those routines. Maybe your write protect tab is set on
df1:. You seem to be able to do something to DF0:.

  Maybe you cannot just do a rawread then a rawwrite. THere is the gap
between sectors to worry about. When trackdisk reads a track in, it
starts anywhere at a 4489 sync word. This could be any sector. Then it
does a block move to get rid of the gap and put all 11 sectors together.
Maybe you have to clean up the raw data before you can do a write.
  Cleaning up could be repairing missing 4489's at the start of each
sector, re-aligning the sectors, patching the byte that tells sectors to
gap, etc. In short, just what trackdisk must do.
  Tell us more about how you are setting things up. These are general
suggestions and may not be of use.