heya...
well..
LD B, 255
Loop: CALL$FD9F
DJNZLoop
does the trick, but this is much faster:
xor a
ld ($f1c1),a
It's like this..
Every time a disk-operation is done, the address $f1c1 is filled with
255 because of the fact if it's not done, and e.g. the end of
There is a new MSX Fair added to the MSX Fairlist.
See:
www.msx4ever.demon.nl/fair.htm
for more information!
Excuse me, it's my error ... bye,
Stefano
-Messaggio Originale-
Da: Ricardo Jurczyk Pinheiro [EMAIL PROTECTED]
A: [EMAIL PROTECTED]
Data invio: venerdì 9 luglio 1999 17.16
Oggetto: Re: R: UZIX betabetabeta test
At 20:18 07/07/99 +0200, you wrote:
I've tryed with NMS8280 of my
Maarten ter Huurne wrote:
At 11:06 PM 7/8/99 +0200, Jon wrote:
2. a way to figure out of which type a connected drive is and to figure
out if a diskrom supports this standard.
If the DiskROM doesn't support a drive,
??
a diskrom does support at least one type of device. That's why
[EMAIL PROTECTED] wrote:
heya...
well..
LD B, 255
Loop: CALL$FD9F
DJNZLoop
does the trick, but this is much faster:
xor a
ld ($f1c1),a
Ooooh no!!!
that will only work if the internal floppydrive is the only diskrom
present in your system. In
Then ... Graphic board on Z380 is really powerful. It's a VDP capable of
set
any screen mode (software programable) at any resolution and colors, and
it's
ultra-fast. It works as a V9990/V9958 perfectly.
Other boards on the Z380: the internet board (mpeg decompressing and
others)
and a
well..
LD B, 255
Loop: CALL$FD9F
DJNZLoop
does the trick,
Perfect. You don't need speed that much after loading from disk so this
little delay to stop the drive doesn't matter.
but this is much faster:
xor a
ld ($f1c1),a
No!!! I know that it works,
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,
hmmm... seems dangerous to me: some hardware drivers can be installed in
this area at startup. (example: workspace of diskroms). MSX system area
is from #F380...#. Below that area, the DOS kernel area; from #F1C9
to #F37F for the DOS2.x kernel (probably the same for DOS1 kernel).
Yes, but MSX has "power-horse" to decompress data and maintain
synchro?
I don't think so.
Maybe it can be done using a special video compression algorithm.
FLI files, for example, uses an algorithm where they have the 1st frame
stored and the differences between the 1st and
By the way, I think your routine contains a bug. This is what you posted:
ld a,e
ld b,e
sub 1 ;If 0, then set carry
ld a,d
sbc 0 ;if B=E=0 then A=D-1 (for fast loop)
But if you run this with DE=#0103, the output is B=#03 and A=#01. This
means the outer loop won't loop, while it should
What's the actual effect of setting both pitch registers of a channel to 0?
A "frozen" wave or a "supersonic" pitch wave?
I'd like to stop a sound without dropping volume to 0 (resulting in a
"pop!"), and I've discovered setting both pitch regs to 0 stops the sound
smoothly.
But... if it
Some days ago, somebody asked me to upload the Z-machine source code to
funet. I have readed that in funet there is an IF directory. In
pub/misc/if-archive , but I can't acces to it. Somebody can?
In /pub/misc/if-archive, there is a file README, which explains. I'll
copy/paste:
--
You may
At 07:27 AM 7/10/99 -0400, you wrote:
xor a
ld ($f1c1),a
This will turn off the floppy drive on a standard system, but I'm not sure
it will work on any system. The address #F1C1 is in a data structure that
doesn't have a fixed address, although it seems to be assigned the same
address on many
At 05:13 AM 7/10/99 +0200, you wrote:
What's the best system-friendly way to stop floppy disk (or whatever
spinning device) motor before taking over system?
Generally, calling #FD9F 256 times works very well.
If for some reason you want to stop drives directly, use these DiskROM
routines:
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
At 07:06 PM 7/10/99 +0200, you wrote:
Your way is faster, but it doesn't preserve the DE-register and it's only 4
T-states faster...
About the T-states, here is my code again:
;DE = number of bytes
dec de
inc e
inc d
ld b,e
ld a,d
;B =
At 10:55 PM 7/10/99 +0200, you wrote:
You raise a very interesting question there. Where is the line between an
MSX and other computers?
The answer to that question is in the charasterics of an MSX I think. So any
new machine with the name MSX should in the first place run most of the msx
At 07:37 PM 7/10/99 +0200, you wrote:
What's the actual effect of setting both pitch registers of a channel to 0?
A "frozen" wave or a "supersonic" pitch wave?
You could find out by sampling the sound output of your MSX. Even if it's
frequency is higher than the sampling frequency of the
At 06:49 PM 7/10/99 +0200, you wrote:
Another option: use UZIX drivers for every hardware device.
For example FastCopy also uses drivers to support different types of FDCs.
MAARTEN!!!
Are you really suggesting this?
If something will result in incompatibility...
No, I haven't gone mad. Not
20 matches
Mail list logo
