GIF viewer for ZX.

Hello, Alexandr! 22 Oct 02 02:29, Alexandr Tkachev -> Valerij Kozhevnikoff: VK>> Here's a trick. Your 8259 is in 8086 mode (determined by 0 VK>> bit AT> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AT> After studying the docks, I tried all the options for any value AT> mPM,ICW2,ADI,A5-A7 ICW1 with IM2 the result is the same SD = #BF, with IM0 complete AT> stupor can only be treated with power off, apparently this is the implementation of the control panel in gusto AT> you can make sure by digging into the PROM, page 7. Yeah. What if you tear off the 26th leg of the PCP and put a normal INTA there? You can do it on 1533LL1 or like this: /M1 ───.|──┬───┬───── /INTA │ █ 1kOm /IORQ ───.|──┘ │ ─┴─ "edit OR" Diodes - KD522. IMHO, altera only lets the first INTA through to the control panel, it issues a CALL opcode, The Z80 issues a second INTA and that's where it stops. Or is it not? Probably not yes. Most likely, during development, SMUC was jammed into IM0, due to the fact that frame interrupts cannot be canceled, and with IM0 the handler will always be address #0038. It didn’t work out well in IM2, so something was done8086 emulator, which adds a second one to each INTA from Z80, so that the vector is the tire was issued. But I don’t understand why it’s always #BF? Look at the diagram, you can see that the tires data 8259 and Z80 are connected only through a buffer on AP6, which means this #BF is from it himself comes. Where does he get it from? By the way, even in IM0 you can do something good. You program the watch to they generated an interrupt 50 times per second (in SMUC this is IRQ0), for this interruption you hang up the keyboard and so on, but for the entire time you work with the modem (when the INT flag is raised in the SMUC system register) keep a jar of TRDOS below. She has at #38 is a simple plug from EI:RET. And modem ports are at your fingertips. How as soon as the modem buffer is full - pause the port, remove the INT flag, you write the buffer to disk and fill it again... * Originally written in REAL.SPECCY *also sent to CODE.ZX *also sent to HARDWARE.ZX WBR, Jason. /*e-mail: jason2000(scary dog)yandex.ru ICQ: 62235830*/ /np:/ *silence*

Hello Valerij! Thursday October 24, 2002 at 03:22:57, Valerij Kozhevnikoff => Alexandr Tkachev: VK>>> Here’s a trick. Your 8259 is in 8086 mode (determined by 0 VK>>> bit AT>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AT>> After studying the docks, I tried all the options for any value AT>> mPM,ICW2,ADI,A5-A7 ICW1 with IM2 the result is the same SD = #BF, with IM0 complete AT>> stupor can only be treated with power off, apparently this is the implementation of the control panel in Smak in AT>> as you can see by digging into the PROM, page 7. VK> Yeah. What if you tear off the 26th leg of the PCP and put a normal INTA there? [skip] In fact, all my curiosity is tempting me to solder INTA and apply SD directly bypassing AP6, I wonder what will happen? I'm too lazy for now. VK> Most likely, during development, SMUC was jammed into IM0, due to the fact that VK> frame interrupts cannot be canceled, and with IM0 the handler will always be on VK> address #0038. So what? in the control panel, the address for placing the interrupt vector depends on the level interrupts plus a programmatically specified value (call xxxx himself said).VK> But I don’t understand why it’s always #BF? Look at the diagram, you can see that the tires VK> data 8259 and Z80 are connected only through a buffer on AP6, which means this #BF is from VK> himself comes. Where does he get it from? Probably from a very cunning alter ;) Alexandr.

Hello, Alexandr! 05 Nov 02 19:53, Alexandr Tkachev -> Valerij Kozhevnikoff: AT>>>>> After studying the docks, I tried all the options for any value AT>>>>> mPM,ICW2,ADI,A5-A7 ICW1 with IM2 the result is the same SD = #BF VK>>>> But I don’t understand why it’s always #BF? Look at the diagram, you can see that VK>>>> data buses 8259 and Z80 are connected only through a buffer on AP6, which means VK>>>> this #BF comes from himself. Where does he get it from? AT>>> From a very cunning alter, probably ;) VK>> She’s not cunning at all. Emulator of powder. Look at the diagram. SD k VK>> the alter is not attached at all. Damn. I didn’t even think that it’s quite possible to replace signals from other devices... I was confused by the fact that the 19th leg of AP6 (which is the strobe) is planted on the ground. And on the 1st leg (which is DIR) I assumed was /RD (or inverted /WR) from processor. So. Let's try to figure out why the 3,6,7 SD bits are used on the alter's legs. AT> DB3, input System register INT flag AT> DB6, SCL input for NVRAM output 1. Bit 6 of disk status port 2. SDA from NVRAM 3. Vector = #BF on interrupt AT> DB7 input register set switchingoutput Bit 7 of disk status port Apparently, all these bits can be used to identify the controller (number versions and all that). How to find out the version number is the only thing that remains unclear in smuc. AT> are set to altera, SD=#FF DB6=0 here's #BF, besides AT> AP6 bidirectional buffer who knows what is there on the 1st leg in the right one AT> moment? Exactly... So this #BF is the only possible vector. Work in IM0 It’s impossible (CP A doesn’t do anything worthwhile). AT> INTA I soldered the same song, I think that the control panel is all that comes from him AT> is required, does it, but the question is whether it gets on the bus. There is simply nothing else left. That's all true. I need to add to the document. And your DOSX Probably it’s already possible to release it to the people. WBR, Jason. /*e-mail: jason2000(scary dog)yandex.ru ICQ: 62235830*/ /np:/ *Aria - Paradise Lost* [paused]