[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FocusDrive and Interrupts
- Subject: Re: FocusDrive and Interrupts
- From: mdj <mdj.mdj@gmail.com>
- Date: Sun, 31 Oct 2010 19:38:54 -0700 (PDT)
- Complaints-to: groups-abuse@google.com
- Injection-info: s4g2000yql.googlegroups.com; posting-host=165.228.177.83; posting-account=gKwMEAoAAACgdZoRArZlfcCSOA8KWMxg
- Newsgroups: comp.sys.apple2
- Organization: http://groups.google.com
- References: <dog_cow-1288547750@macgui.com>
- User-agent: G2/1.0
- Xref: g2news2.google.com comp.sys.apple2:20796
On Nov 1, 3:55 am, dog_...@macgui.com (D Finnigan) wrote:
> Is it OK to use the FocusDrive in an interrupt-enabled environment, such as
> a multitasking OS?
Should be fine. If you're using it through ProDOS everything should
'just work', and ditto if you're accessing the device through its
SmartPort firmware (assuming there's no bugs in the firmware that
remain undiscovered).
Of course, if you're accessing the cards IDE registers yourself
(though I can't imagine why you would) then everything is on you to
ensure things are done 'right'.
Are you using ProDOS's interrupt calls to register handlers, or
bypassing them ? The only code I've written myself that does this
bypasses ProDOS and access the interrupt vector directly Any Disk IO
is subsequently done with interrupts disabled, primarily due to my own
paranoia at what might happen; ProDOS may or may not have a built in
capability to postpone an interrupt if it occurs during its own
execution in certain states.
Are you multitasking using bankswitching on a RamWorks card perchance?