Re: [real coding] DOS2 and Memory...

1999-02-25 Thread Laurens Holst
>Hi people, > >Thinking that you should set the interruptvector at #C000 when you set I to >#C0 is a commonly made mistake in the MSX world. You should set your >interruptpointer at address #C0FF instead. As some of you might know, the >databus in the MSX is connected to VCC with pull-up resistors

Re: [real coding] DOS2 and Memory...

1999-02-23 Thread Maarten ter Huurne
At 10:13 PM 2/22/99 +0100, you wrote: [about using IM2] >You should set your >interruptpointer at address #C0FF instead. As some of you might know, the >databus in the MSX is connected to VCC with pull-up resistors. As a >consequence the Z80 will always fetch the value 0xFF when reading from

Re: [real coding] DOS2 and Memory...

1999-02-23 Thread Alex Wulms
] This is true on a standard MSX with correct devices connected to it. If on ] the other hand a device only checks IORQ and not M1, it might put data on ] the bus when it is read at interrupt-time (In this mode IORQ and M1 are ] both active). A device which ignores M1 does not respect the Z80 nor

Re: [real coding] DOS2 and Memory...

1999-02-23 Thread shevek
On Mon, 22 Feb 1999, Alex Wulms wrote: > Thinking that you should set the interruptvector at #C000 when you set I to > #C0 is a commonly made mistake in the MSX world. You should set your > interruptpointer at address #C0FF instead. As some of you might know, the > databus in the MSX is connec

Re: [real coding] DOS2 and Memory...

1999-02-22 Thread Alex Wulms
] You probably won't get problems. ] However, in Dos it is easiest to replace the bytes at adress #38, for ] example putting a JP Interrupt there. In Basic, it is -to my opinion- better ] if you swith away the ROM, however you could also set the other interrupt ] mode (mode 2?) in which the high b

Re: [real coding] DOS2 and Memory...

1999-02-20 Thread Laurens Holst
>I read (nearly) all the messages from the last time... >- Oh my god! I really miss mails refering to (program-) technical thingies... > >So - lets start a "serious" thread... ;cP **Great** >DOS 2 & memory >-- >I found out that the DOS2 page-switch routines are >kinda slow. Does

Re: [real coding] DOS2 and Memory...

1999-02-07 Thread Maarten ter Huurne
Hi! I've got a mistake to fix... I wrote: >Did you know that you shouldn't put the MoonSound volume too high? If you >do, it will clip the sound and it will sound bad. >I made a single channel that plays a sample which uses the full amplitude >range. I put the volume for that channel on maximum

Re: [real coding] DOS2 and Memory...

1999-02-06 Thread Alex Wulms
] I've been wondering. Except for the opcode and the timing, is there a ] difference between RET and RETI? I know RETN does iff1=iff2, RET. But my ] documentation on RETI only says that the program knows the interrupt is ] finished. Quoted from a book about the Z80, describing the RETI instruction

Re: [real coding] DOS2 and Memory...

1999-02-06 Thread shevek
On Fri, 5 Feb 1999, Maarten ter Huurne wrote: > The default MSX interrupt handler pushes all registers (normal and > alternative) to the stack. This is safe, but slow. > If you choose not to use the alternative registers in your program, and not > to use them and IX and IY in your interrupt routi

Re: [real coding] DOS2 and Memory...

1999-02-06 Thread Maarten ter Huurne
At 08:31 PM 2/5/99 +0100, you wrote: >DOS 2 & memory >-- >I found out that the DOS2 page-switch routines are >kinda slow. Does anybody know a simple, "legal", and >compatible way to speed up those bottlenecks? Slow? This is what PUT_P2 does on my GT: jp #EE3A #E

[real coding] DOS2 and Memory...

1999-02-05 Thread john . j
Hi! I read (nearly) all the messages from the last time... - Oh my god! I really miss mails refering to (program-) technical thingies... So - lets start a "serious" thread... ;cP DOS 2 & memory -- I found out that the DOS2 page-switch routines are kinda slow. Does anybody know a