Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Tursi last won the day on September 7 2019

Tursi had the most liked content!

Community Reputation

4,890 Excellent


About Tursi

  • Rank
  • Birthday 11/29/1971

Contact / Social Media

Profile Information

  • Custom Status
  • Gender
  • Location
  • Interests
    Buy me a Kofi! https://Ko-fi.com/tursilion

    Or fill in my 'SurveyWalrus' and help choose my next task!
  • Currently Playing
    Current Project: Update TI and Coleco VGM compression and playback tool (Project 'ballp'). (and.. lots of RL work... ;) )
  • Playing Next
    Next project (per survey): Fixing up my Genesis bartop

Recent Profile Visitors

29,665 profile views
  1. Classic99 doesn't care what the extension is, so you can happily use .TIDisk there. It might not show up by default if you browse, but you can change the type to All Files, or just type the path in manually. I think only Win994a cares, doesn't it?
  2. Hmmm... the PAB at >1000 MIGHT be an issue, but that's strange because you load the pattern table first, and it doesn't appear to be corrupt when you load the color table. Classic99 will also tell you the actual PABs in use in the log. The DSRLNK settings are for the subprogram call (instead of a file I/O call). The next step if the debug log offers no clues is to breakpoint after the load and see where it's stuck.
  3. Do they get corrupt in real life, or only Classic99? The two disk corruption bugs I recently fixed would definitely corrupt any disk that was writing two output files.
  4. You can check in the Classic99 debugger what the CALL FILES(1) sets the top of VDP RAM to -- if it's lower than >3800 then the disk buffers are being corrupted by the image load. Normally 1 is enough, but maybe Fortran does things differently. Classic99 tries to complain about situations like the disk buffers being corrupted, so it may give you a clue if that's it.
  5. If I'd actually any kind of skill, maybe my words would mean something. This is not aimed at you, just general grumbling. There is nothing about software development that should involve tricking the computer or the compiler. If you are trying to be more clever than your tools, then eventually, your tools won't be able to help you debug the crap your wrote... It's a bad attitude that too many people have, and I'm personally tired of always being called to fix it. Anyway, on to your issue, I don't have source code to PREditor nor do I use it, but a quick test shows that Classic99 can tell the difference between Q and Control-Q, so the issue probably lies in PREditor. The PC remap is no big deal, both keyboards have a control key, and control has no special meaning on the TI, so the map is pretty direct. In short, without deep diving into the assembly code, there's nothing I can do. Is there anyone still offering support on that editor?
  6. hehe, glad you got it working! I like watching TI Bitmap mode draw, but dang!
  7. I thought I hacked this for you years ago to work with DSK1 instead of DSK.MULTIWHATEVER, anyway? MultiplanDSK1G.zip
  8. Two limitations - One is that as shipped, it deliberately prevents you from programming that range for a variety of reasons. Two is that the address counter readback code is not in that version (I didn't have it working right at that point in time, although at some point I did), so you would still need at least one real GROM somewhere in the system to run. Mostly I was worried that when I released MPD, two TTL GROM replacements both fighting for the console address space would damage one or the other. The source code shows you what to change to enable the space, though.
  9. My first time playing. 8500. I had to use the Classic99 TV controls to tweak the hue and tell the red and the green/yellow apart... Really thought I was going to clear that stage till I accidentally rotated twice and blocked access on the left.. (Edit: started at level 1, slowest speed )
  10. My understanding was the QI machines lack it. Haven't personally tested that.
  11. There's not much it can do (with existing software) that the FinalGROM can't, save the projects that make use of the serial port. But, you could use the ones you have to make some permanent cartridges - the XB2.7 suite and RXB are good ones to have.
  12. So now I've done plenty of debugging write access and apologizing for corrupt disk images... Classic99 399.020 - disable the DAC buffer overflow warning during overdrive - return PRG for program type in disk file type identification debug - add sector bitmap debug to disk images (probably temporary) - rewrite the cluster output routine to fix corruption of output fragmented files Highly recommended to upgrade if you ever save on image disks - another file corruption issue fixed. This one has been pretty well exercised, but be aware I haven't tested the extreme failure cases of disk full, directory full, or cluster list full. They should work in theory, but if you are going to rely on them then test them yourself. https://harmlesslion.com/software/classic99
  13. Sadly, Voyager 1 turned off its cameras many years ago. That's Earth from 3.7 billion miles, the bright at the bottom is light from the sun. it IS from Voyager 1 though. Looks like someone tweaked the contrast. https://solarsystem.nasa.gov/resources/536/voyager-1s-pale-blue-dot/
  • Create New...