Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


mizapf last won the day on August 31 2016

mizapf had the most liked content!

Community Reputation

4,514 Excellent


About mizapf

  • Rank
  • Birthday 09/24/1969

Profile Information

  • Gender
  • Location
  • Interests
    MAME, TIImageTool, Ninerpedia
    Linux advocate (openSUSE/KDE)

Recent Profile Visitors

17,872 profile views
  1. This is my concern that I expressed a while ago when people designed labels for self-made cartridges. The TI-like labels and the manuals look really neat, but at the same time they show why there is something like copyright: You make them look professional - because TI made them this way. It might be about time to design something new like a "TI veteran style" or whatever we'd like to call ourselves.
  2. A list of speech phrases in Moon Mine: https://www.ninerpedia.org/wiki/Moon_Mine As a starter ...
  3. The euro symbol was included in Iso-8859-15 as a 1-byte character, but in this case it is unicode. Of course, it is not included in ASCII (character codes 32-127).
  4. You may even play it on Spanish. Felicitaciones Capitán!
  5. I sometimes take some notes of things I discovered. One says about GenASM: Might have a problem with BYTE without following EVEN. Creates ILLEGAL TAG.
  6. Understood, but since the subprograms don't have names, it will become a bit difficult to find e.g. the sector I/O subprogram of a given card, don't you think? Any program that intends to make use of level-2 subprograms would have to include some knowledge what number the sector I/O has on which card. In fact, I faced this question just when I wrote the custom OS loader: If I don't assume a CRU address for the SCSI controller, how do I find its >24 program? My solution is a special DSRLNK that first searches for the name "SCS1" and then, in that very card, looks up the subprogram. So may I assume that >84 does the same as >24? I'm using it to load the plain sectors.
  7. Yes, and the Genmod could only achieve that by tampering with the PAL connections. I added the Genmod expansion to the Geneve schematics to make it clear:
  8. What I noticed is that in the IDE DSR, the >24 subprogram is not available but instead >84. I do not know whether it is fully compatible - Fred should be able to tell. It must deliver the file information but also the contents of the specified number of sectors at a given start location.
  9. Here is a tool that I wrote during the last days, but which I wished to have for decades (at least since I have a SCSI controller). Don't ask me why I did not think about it earlier. If you have a Geneve with Swan EPROM (0.98) and a modern card like SCSI, you had to use drive A: to boot the Geneve, even though your SCSI drive works perfectly after booting. The old EPROM could only detect different floppy controllers (TI, Myarc, and CorComp), the HFDC, and the Horizon card. So your way would be to burn the 1.00 EPROM. If you don't feel like swapping your EPROM, this program will be the alternative. It is a boot loader that can also be adapted to other devices if desired. I added the source code on the disk image. You need GenASM/GenLink to build it; just call "MYMAKE". Copy the resulting SCSILOAD on A: as "SYSTEM/SYS". You also need a AUTOEXEC on A:, since it is still loaded from there. I also found that I have to add a "PDMA ON" to make the SCSI card work. The idea is that the EPROM will attempt to load this very small SYSTEM/SYS and run it. Then, this program searches the DSR space for a SCSI card (by the name "SCS1") and the subprogram >24 (direct file input). Having found them, it loads a file "@SYSTEM" from the SCS1 drive into pages 0-15 and then starts the loaded program. This happens to be the real GeneveOS kernel file (originally named SYSTEM/SYS). Here is a short video that shows the program in action: http://www.mizapf.eu/files/genboot.mp4 The flashing border is just a way for me to see whether all pages (each 8K) are loaded. As you can see, the load time is really cool. (The SCSI drive is a SCSI2SD.) scsiload.dsk
  10. The wait state behavior is buried inside the Gate Array and the PAL. On the board, there is not even a place for a memory expansion; you cannot solder DRAMs on top of each other. So the "future expansion" was meant to be in the infinite future, or possibly in another time line. Or, in other words: These things may have been planned originally, but the eventual design of the board and the custom chips made them moot. But obviously, no one cared to rewrite these items in the specifications.
  11. Depends on the country. In Germany, any works lose their copyright* 70 years after the death of the author, and there is no fair use clause. Many thanks to the publishers for their persistent lobbying. 😞 For that reason, I did not put my name in the HFDC manual rewrite. *There is another term for it, "Urheberrecht", which is not exactly the same, since the author cannot give away his rights but can allow certain ways of distribution.
  12. While you're talking about it, I should really continue on my Arkanoid clone. 🙂
  13. I do appreciate Rasmus' work, and the achievements with the F18A are really stunning. As I said, my concerns are much smaller today than in the past when some people already claimed this to be the "new standard".
  14. I believe that Fabrice just wanted to express our latent concern that with all those exciting new features, we gradually lose contact to our good old TI-99/4A, with its potentials and its limitations. Since we have had quite many developments for the normal console, in particular from you, my personal concern is not as high today as it was when the F18A showed up.
  15. I removed both PDFs. I believe there is no other way but to re-scan the documents, so this won't infringe CaDDs copyright on the scanned documents. As for the TI copyright this is somewhat unfortunate, but I don't believe that TI would try to enforce their original copyright from 197x or 8x. Two years ago I had a short conversation with Mike concerning the TI-99/4A User's Guide that also appeared on WHTech since 2006. It was also taken from the Cyc, and he asked to take it down. Once I started a rewrite of the Editor/Assembler manual from an own scan (similar to the HFDC rewrite that I did some time ago). I learned that there was already a typeset version by CaDD, but this would be available via the Cyc only, too. Hence, it makes sense to recreate the manual. I appreciate all of Mike's work with CaDD, but the last thing we need is a monopolized source of manuals. My 2 ct.
  • Create New...