At 09:29 AM 07/24/99, you wrote:
This is not feasable. During sector I/O from floppy you can't miss a
single
byte. Even a trivial interrupt routine which returns immediately with a
reti
instruction takes too long during diskload.
Even if you have a good CRC error detection-routine so that
At 13:08 13/07/99 +0200, you wrote:
] 1. Write your own diskroutines directly accessing the FDC, which leave
the
] interrupts enabled.
This is not feasable. During sector I/O from floppy you can't miss a
single
byte. Even a trivial interrupt routine which returns immediately with a
reti
]
] ] 1. Write your own diskroutines directly accessing the FDC, which leave
] the
] ] interrupts enabled.
] This is not feasable. During sector I/O from floppy you can't miss a
] single
] byte. Even a trivial interrupt routine which returns immediately with a
] reti
] instruction takes too
] 1. Write your own diskroutines directly accessing the FDC, which leave
the
] interrupts enabled.
This is not feasable. During sector I/O from floppy you can't miss a
single
byte. Even a trivial interrupt routine which returns immediately with a
reti
instruction takes too long during
] Yes, it's true that the sector I/O would fail. But if you automatically
] retry, disk I/O will only slow down, but still work. As long as a single
] sector can be located and transferred in an interrupt period.
Transferred: yes. Located: no
With the datatransfer rate, physically limited by the
] ??? At least my BERT disables the interrupts, I'm afraid...
]
] I made some screen 0-overscan TSR, working on the interrupt, and while
] executing DIR the screen flashed... Also when I play music using the
] Multi-Mente MGS-driver or the MBWAVE Dos driver and I execute a DIR-command
] the
MkII kissed:
Also, I'm planning to play background music while loading, so I need
standard
interrupts enabled.
Forget about that. During the disk access, the interrupts are switched off
and
on time and again. So, no nice 50/60 Hz interval - no nice music...
Eric
MSX
Also, I'm planning to play background music while loading, so I need
standard
interrupts enabled.
Forget about that. During the disk access, the interrupts are switched off
and
on time and again. So, no nice 50/60 Hz interval - no nice music...
There are three solutions:
1. Write your
] 1. Write your own diskroutines directly accessing the FDC, which leave the
] interrupts enabled.
This is not feasable. During sector I/O from floppy you can't miss a single
byte. Even a trivial interrupt routine which returns immediately with a reti
instruction takes too long during diskload.
At 10:22 PM 7/12/99 +0200, you wrote:
] 1. Write your own diskroutines directly accessing the FDC, which leave the
] interrupts enabled.
This is not feasable. During sector I/O from floppy you can't miss a single
byte. Even a trivial interrupt routine which returns immediately with a reti
My loading routine was OK! I've just tested in my NMS 8250 and it's really
fast. Less than 6 sec per screen 8 where basic takes almost 10!
Basic, 10 seconds??? Using BLOAD??? I guess using COPY, which is very slow.
Use BLOAD and it will load in 1 or 2 seconds. Use my routine (however, fix
the
Oh my!
My loading routine was OK! I've just tested in my NMS 8250 and it's really
fast. Less than 6 sec per screen 8 where basic takes almost 10!
Basic, 10 seconds??? Using BLOAD??? I guess using COPY, which is very slow.
Use BLOAD and it will load in 1 or 2 seconds. Use my routine (however,
At 04:40 AM 7/10/99 +0200, you wrote:
The problem is with my F700!!! It takes 400% more time to load!!!
It has something to do with the interrupt routine of the DiskROM. You can
avoid this slowdown either by writing "RET" to #FD9F or by telling the VDP
not to generate interrupts (a bit in reg 0
Oh my!
My loading routine was OK! I've just tested in my NMS 8250 and it's really
fast. Less than 6 sec per screen 8 where basic takes almost 10!
*BUT*BUT*BUT*BUT*
The problem is with my F700!!! It takes 400% more time to load!!! The drive
LED even turns off when feeding data to VRAM!!! Cannot
14 matches
Mail list logo
