mizapf

Even I uploaded some videos on that topic. (The latter two are MAME emulation runs.)

You have to load a copy of GROM0 into every bank that you intend to activate. Otherwise the console will lock up. The banks are numbered 0-15 for the GROM; 16 and 17 for GRAM. Saving cartridges usually involves saving the occupied GROMs and ROMs; saving more will do no harm. You can only load one cartridge into a bank, because cartridges may use the same GROMs and then overwrite each other. Extended Basic and TE-II: in two separate banks But you can use all devices and subprograms from another bank. I just tried to open SPEECH in Extended Basic, and it worked. Here is a disk image with GROM 0-2 (BASIC), Extended Basic, and TE-II. contents.dsk

Hmm, I only know about DSSD (180K) and DSDD (360K) disks that are used with PC99 (but as track dumps instead of sector dumps).

I remember well how tedious it was decades ago to have calls blocked. Today, another unknown call from some weird number, added it to the block list in my Fritzbox (DSL/tel router), press OK, done. Can even use wildcards.

I always believed that you just need a source of Brownian motion, preferably a cup of hot tea.

@DavidCChanging disks or cartridges is done via the on-screen display menu (OSD). Switch to "partial mode" by pressing ScrlLock, then hit TAB. When you are done, return to "full mode" by pressing ScrlLock again after leaving the OSD. If you are not familiar with the OSD yet, take some time for a walk through it.

No, it's just a choice - as with your real TI and PEB. Use HFDC or BwG.

HFDC BwG and once you upgrade to post 0.220: DDCC-1 CorComp

This is a DSDD disk, and you tried to read it with a TI FDC. Please use another controller.

Batch files, those with .bat extension? I suppose this is still common Windows terminology. Scripts, in the Unix world.

Could you post a dsk image that fails with your MAME installation?

The older MESS 0.140 is, I can say, another piece of software compared to the current MAME 0.225. The only advice I can give you is to upgrade to the recent release. For instance, none of the path specifications will work on MESS 0.140.

If someone could do a good photograph of a QI board, we can add that to Ninerpedia with the appropriate chip numbering.

No, as it seems. Maybe it was just enough for me to disassemble without hints.

The lack of RBW is what boosts the Geneve speed considerably, although it only has 8 data bus lines. By the way, the TMS9980A also has only 8 data bus lines, but its microprograms are the same as the ones in the TMS9900. Hence, it does RBW. The 9995 seems to be a thorough redesign. I had a look at the TMS99000; it seems to do RBW again. But there are some optimizations; the MOV instruction does not fetch the destination operand.

The 9995 does not have a read-before-write, as its data bus has only 8 lines. And it only transfers single bytes with a byte instruction. Do you mean the 9900?

Note that he refers to a QI board.

You know, the "abuse" of country code TLDs is not what worries me. I'm writing in quotes because I'm not to tell a country how to manage its domain. Tuvalu, Tonga, Vanuatu - all mini-states in the Pacific ocean - just don't have so many inhabitants to make good use of their domain, and when there are people who pay, well. What worries me is the inflation of TLDs. "Clever" people seem to have discovered a business model by promoting new TLDs ... to make you look more important. Why do cities have a need for an own TLD? Or companies? What was wrong with the hierarchy concept? This reminds me of my late father who always struggled with the concept of directories on a drive. For me, it was nothing to discuss - files should be organized in a hierarchical structure, just like we put paper sheets in a binder, the binder on a shelf etc. Our mind works with hierarchies. But it seems to me that people don't get this concept any longer. My father always asked me (in DOS times) whether I could not just drop everything in the C:\ directory, and I started to argue with file name clashes and so on. Have a look at this list: https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains This does not make sense.

Also have a look at Raphael Nabet's work in MAME: https://github.com/mamedev/mame/blob/master/src/mame/drivers/tutor.cpp

If I may add some more confusion: The two-letter TLDs designate countries. At least, it was intended that way. be = Belgium de = Germany (Deutschland) fr = France it = Italy us = USA ... io = British Indian Ocean Territory gl = Greenland tv = Tuvalu ly = Libya to = Tonga However, the countries that own their TLDs are more or less restrictive when you try to register a domain in their TLD. Some of them developed a business of selling domains in their country domain (e.g. Tuvalu or Tonga) because their TLD makes it easy to create "domain puns" - and people pay for it.

There is another interesting point about this LIMI 2/0 and the VDP interrupt. You know, they just did not tell us the whole story ... 🙂 When I learned assembly language programming, I learnt that I have to do this LIMI 2/0 in a loop for interrupt-driven function, and that it works. But why does it work? My concern was that these LIMI operations ran in a couple of microseconds, and why should the VDP just raise its interrupt line in between? Wouldn't I miss a lot of interrupts? Much later (actually, when I worked in MAME) I understood what happens. The interrupt input of the 9900 is level-triggered; that is, the interrupt service will start as soon as the processor detects INTREQ*=0 (and the level indicated via IC0-IC3 is higher than the LIMI mask). The VDP interrupt output is latched inside the VDP. That is, when an interrupt occurs, its INT line gets active and stays so, until you clear the interrupt in the VDP. This can only be done by reading the status register. If you look inside "TI Intern" you see that at address 094A, the SBO 2 instruction first disarms the interrupt trigger in the 9901 (Heiner Martin's comment was wrong at that point), and at 0A84, the status is read, which clears the interrupt again. Thus, when LIMI 2 is executed, the latched VDP interrupt will make the CPU jump to the interrupt service immediately. BTW, the 9995 has its own latches which can be queried via CRU addresses 1EE4/6/8.

Isn't that just Rayleigh scattering? (which makes our sky blue) I think you can get the same effect with a thin emulsion, like milk in water.

Yes, the hardware reset also goes to the VDP and to the I/O port.

I have had several disassembly tasks in the past done on my own. If there are several people who are interested in analyzing the code, maybe one could do that on a collaboration platform where you can edit in parallel. The results should be stored at some well-accessible position, Ninerpedia, WHTech, etc.

Can help you with that; I already disassembled it because I had to find a bug in the 9995 emulation. There are only very few comments, some in German. tutor1.tis tutor2.tis