[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: DSK to NIB Instruction
- Subject: Re: DSK to NIB Instruction
- From: "josephoswaldgg@hotmail.com" <josephoswald@gmail.com>
- Date: 14 Oct 2005 13:09:25 -0700
- Complaints-to: groups-abuse@google.com
- In-reply-to: <diotta$b1o$1@unlnews.unl.edu>
- Injection-info: o13g2000cwo.googlegroups.com; posting-host=198.51.251.199; posting-account=EurUTAwAAADX_MeBnNBWXs4UUtudFXxU
- Newsgroups: comp.sys.apple2
- Organization: http://groups.google.com
- References: <eKW1f.1556$B14.1455@newssvr11.news.prodigy.com> <wc02f.8681$oc.149@newsread2.news.pas.earthlink.net> <dianp2$ttn$1@merope.saaf.se> <3YSdnSFo3q8SZdXeRVnzvA@telenor.com> <did6vk$1qul$1@merope.saaf.se> <434e6cf5$0$10226$9b4e6d93@newsread2.arcor-online.net> <T6v3f.2269$Aw.40724@typhoon.sonic.net> <434e8419$0$24162$9b4e6d93@newsread4.arcor-online.net> <5NmdnXI18fFPC9PeRVnzvA@telenor.com> <Ddz3f.2305$Aw.41344@typhoon.sonic.net> <434f8fd9$0$24165$9b4e6d93@newsread4.arcor-online.net> <diobqt$6h8$1@unlnews.unl.edu> <434fd743$0$10235$9b4e6d93@newsread2.arcor-online.net> <diotta$b1o$1@unlnews.unl.edu>
- User-agent: G2/0.2
- Xref: g2news1.google.com comp.sys.apple2:6134
Ed Eastman wrote:
> Linards Ticmanis wrote:
> > Actually judging by the source code, most emulators seem to "nibblize"
> > the .dsk image internally and then feed it to the emulated controller.
>
> Interesting. The Emulator takes the sector data and converts it into a
> byte stream to feed the controller? I guess it feeds standard sector
> headers and the like then, eh? Probably doesn't feed any sync bytes then...
I think they include a few FF bytes just for kicks. (You need the
spacing between the address & data fields to allow time for the address
to be decoded.)
They don't feed the controller so much as feed the read data register
address. This allows them to support the RWTS code (remember also that
many DOS 3.3-compatible programs use their own stripped down version of
DOS) which reads disks; the code keeps looking at $C0E8, the simulator
changes to a new NIB data byte every 32 simulated cycles, and RWTS
finds all the markers it is looking for.
One could write a circuit-level simulation that took read pulses at
arbitrary points in time, and drive the Disk-II controller with the
low-level bus signals, and then you would have to include sync bytes
with extra zeros and the whole bit. I've done this, but I've only run
it for a few simulated bytes to make sure I understand the Disk II
design. Using it for a simulator is serious overkill---you'd have to
translate to even a lower level than NIB data, for no real gain.