Forum unknown
· Programming
#WB1.2
11 messages in this thread
Maybe the driver itself. But what if a runaway program trashes a floppy's
track buffer just before it gets written out. Its already assumed to be
in MFM format; its just sitting there, in the 30K or so track buffer,
waiting for a Paula DMA to dump it out to disk. With a few floppies,
you've got a pretty big target for a runaway program to hit. But yea, it
would be really weird for anything to successfully change the driver
program to become destructive — kind of like the chance of a lifeform
living successfully with a major mutation. -Dave
Ahh… never thought about the track buffers themselves. That's 5K per drive,
average system being a 10K target. Now that can definitely be a problem. Now
where did I put that MMU?
Larry, aren't track buffers 11K/track for 3.5 drives? (That is the full
track buffer) plus the actual data buffers.
I guess they are Brian, though if so, they should properly be called
"cylinder buffers", as there are two tracks per cylinder. If they are true
track buffers, then they will be just over 5K. Anyone know for sure?
The trackdisk buffers are 512 x 11 = 5632 bytes in length.
Thanks Rick. So they are true "track" buffers and not "cylinder" buffers.
Thanks Rick. So they are true "track" buffers and not "cylinder" buffers.
The trackdisk buffers are 512 x 11 = 5632 bytes in length.
I guess they are Brian, though if so, they should properly be called
"cylinder buffers", as there are two tracks per cylinder. If they are true
track buffers, then they will be just over 5K. Anyone know for sure?
Larry, aren't track buffers 11K/track for 3.5 drives? (That is the full
track buffer) plus the actual data buffers.
Ahh… never thought about the track buffers themselves. That's 5K per drive,
average system being a 10K target. Now that can definitely be a problem. Now
where did I put that MMU?