Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Tursi last won the day on December 22 2018

Tursi had the most liked content!

Community Reputation

4,047 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: Dragon's Lair for TI-99/4A. See http://atariage.com/forums/topic/287760-dragons-lair-is-now-available/
  • Playing Next
    Next project (per survey): Update TI and Coleco VGM compression and playback tool (Project 'ballp').

Recent Profile Visitors

28,581 profile views
  1. I used to love me some Qix.. I'd have to save that waiting for a character boundary would be awkward. When the sparks are closing in you want to move out of the way "now". The way I'd do it, draw your lines solid but use a sparse fill, like a hash pattern. That way the visible effect of color clash would be minimized.
  2. I haven't tried it, but I wouldn't be too worried. The PS/2 spec is pretty straight forward and works pretty well. I implemented a PS/2 adapter for the TI-99/4A and once I actually understood the specification and implemented it properly (ie: operating at the right clock edge), it worked with everything I threw at it. I tested against old AT keyboards, cheap PS/2 keyboards, and even one rather pricey PS/2 keyboard. Dozens of people since have used it without any comments about keyboards that don't work. The extra keys will either have unique scan codes, or show up out of band, but they shouldn't impact the base protocol (the ones I tested were unique scan codes). The only place you might have issues is internationalization. The keyboards will still work, but the keys may expect a fixed layout (such as US), meaning that whatever is on the keycap, you're going to get the US meaning. Not saying this is how Phoenix works, I don't actually know, but it's my experience with PS/2.
  3. Ooooh... okay. This is actually nothing to do with emulation. "Open DSKx" in the menu does nothing but tell Windows to open the selected file. When it's a folder, Windows Explorer takes the request and opens the folder. If it's a disk, you need to have registered a program to handle the file extension (DSK, TIDISK, etc). I use ti99dir, but anything that can open a disk image on the command line will work - you just have to tell Windows to "always open this file type" with that program. The error message when nothing is registered is a weird one (unless there's something wrong with the registration)... but that's outside of my scope. Unless I actually want to parse the registry (I don't), there's no way for Classic99 to know. At any rate... if it works for you to double-click a DSK image in Windows explorer, then it should work from Classic99.
  4. Any time you see strange behaviour with disk, don't guess. Go read the debug log. In this case, it says: My stance is that you should use Windows file manage to manage Windows files, the TI side is just capable of using the Windows file system. With filename remapping etc (particularly for V9T9 files), if you want to delete something I want to make sure it's the file you intended. So FIAD does not support delete. This one I WOULD be interested in understanding, as it should be fairly transparent. Classic99 can read/write both V9T9 and PC99 style disk images. It should simply be a matter of changing the type to "Image (DSK)" and browsing for the path in the Path dialog. Again, after a failed operation, open the debugger and read the debug log. Classic99 should tell you exactly why it returned an error code.
  5. (scratch) Sorry, I'm a step behind. At this point everyone is guessing. Can you just post your makefile (at minimum, but a full project, even just a hello world, would let others help to solve the full issue)?
  6. Yeah, that's a lot more cheating than Dragon's Lair. Not to say I wouldn't do that, I've been thinking about it for a long time. But we can't get images to the TI screen that quickly - we don't have direct access to any part of the video system. :/
  7. Looks like your crt0 is trying to do set up the C runtime, but can't find the labels. Where did you get this crt0? In mine, which is admittedly quite old, the only startup label is _init_data (which has a table after it). If the toolchain has changed someone who's up to date may need to step in
  8. Someone needs to make libgcc build for the TI before that can happen - I've not been able to do it either. You don't explicitly call the linker (tms9900-ld) anywhere? You can try adding "-nostdlib" to your build line to make it not pull in the standard libraries. The odds are you'll then get a bunch of unresolved references, which unless you succeeded at building any of the GCC libs, you'll have to provide.
  9. Ti wanted third parties to license titles through them, so that put a big damper on development. The 2.2 console with the ROM lockout was released in '83, and they left the market in '84, so Short Circuit would have been pretty late.
  10. To be clear, he's talking about Pitfall, not Dragon's Lair.
  11. I used to say I could have shipped bricks to the Jaguar community for the number of Skunkboard owners who said that...
  12. I'm going to need to take a look at your photo pass... I'll put the Beta up on EBay in about a week when I get back from overseas, it's been long enough.
  13. I did a lot of work with flicker too... it can look decent on a CRT if the contrast between the two colors isn't too high, but modern displays are so fast and/or try to deinterlace, all of which renders flicker colors less effective.
  14. I found in assembling my shells that some were wider than others, too. Not much - just enough to stick out if you joined mismatched ones together.
  15. I spent a bit of time looking at that part of the NanoPeb when I needed to program Dragon's Lair from CF. When it boots up, the DSR reads from the Compact Flash card. If it has a PC-style signature in block 0 (I didn't check exactly how it determines this), it /overwrites/ it with a fixed pattern. The mount information for the three disks is saved in this block, so that's probably why (but it does mean that if you power up with a card in the CF that had PC or camera files, the format of that card will be corrupted). Anyway, there's no timeout on that test - if the card doesn't respond, it will sit there forever. The IDE to CF adapter that the NanoPeb uses is fairly standard, I had a couple in my parts bin some time back. Oddly, though, not just /any/ adapter works, and I wasn't sure why. But there's very little to them - schematics are available online.
  • Create New...