Jump to content

Willie1914

New Members
  • Posts

    17
  • Joined

  • Last visited

Willie1914's Achievements

Space Invader

Space Invader (2/9)

11

Reputation

  1. Thanks, Tursi, for making Classic99 available -- it is greatly appreciated!
  2. Thanks, Lee. Those two addresses (>83D0 and >83D2) are exactly what I was looking for... I had assumed that they that they were the same, but wanted to be certain. Willie
  3. Hi everyone, I'm using the Warren/Miller General Purpose DSRLNK, and am trying to find out where the following values may be found after a successful call (for example, opening a file for read access from DSK2., etc., )? 1. Card CRU address 2. DSR address I know where these values are stored when using the Ti-DSRLNK (both for MiniMem and E/A), but I'm having trouble deciphering the GPL code. Thanks in advance, Willie
  4. Thanks for the replies, I think I have a handle on it... and, indeed, the tricky bit is getting the superspace.nv "ssram" configured properly to have addresses >6000 through >7FFF recognized as RAM. I'll let you know how it develops. Willie
  5. Thanks everyone for the recommendations. I was able to successfully get things working with the RAG Macro Assembler. On a side note, can anyone advise me on how to incorporate a MESS .rpk image of my SuperSpace II cartridge for use with Classic99?
  6. Thanks for the responses... I'll give it a try. Willie
  7. Hi everyone, I need to edit the listing options in my RAG macro Assembler (e.g., change default 'PIO' to a file) for use with Classic99 -- can anyone recommend a HEX editor that I can use under Windows 10 to accomplish this? Thanks in advance, Willie
  8. Thanks for the replies -- yes, I was referring to the "Enable 128k Hack" (page 20) feature of the TMS9938... any advice on where I may find more information? Bill
  9. Hi everyone, I'm interesting in using the expanded VDP addressing feature in Classic99 -- I've read the documentation, but am not clear on exactly how to access the VDP Ram using this feature (i.e., register usage, register setup, etc.) Can anyone direct me to further documentation or offer information? Thanks in advance, Bill
  10. I also run Classic99 from Downloads/Classic99 under Windows 10 without any problems.
  11. Thanks for the reply -- my s/w (running on an actual TI-99/4A) swaps in 8k chunks. At this point I think I'll abandon trying to get it to run in an emulated environment as is, and start re-writing to employ a MiniMem cart + 32k memory expansion. A bit more work, but it seems like that is the only option open to me. Thanks again, everyone, for your replies. Best regards, Willie
  12. Thanks for the replies everyone. Yes, I've written some assembly-code programs that take advantage of the SSII RAM configuration and would like to duplicate this functionality so that I can run my S/W via emulation. I was wondering what it would take to create a "module" that would be recognized by an emulator to let me run my S/W.
  13. Hi everyone, I'm new to these forums (joined within the past few months), and I have a SuperSpace II cartridge which I purchased decades ago and would like to create an image usable by a TI-99/4a emulator. Can anyone direct me to a tutorial on how to do this? My SSII cart is getting up there in age and I don't know how much longer it will continue to function. Thanks in advance, Willie
  14. Hello everyone, I've just downloaded the latest version of Classic99 and I'm getting a (generic, I believe) warning from Windows Defender. I think that that last version of Classic99 that I have running on my Windows 10 laptop is two version old, and it didn't spawn this warning. I assume that everything is fine with the download, and am hoping this has something to do with the last series of updates from MicroSoft. Has anyone else encountered this issue? Thanks in advance, Willie
  15. Thanks for the replies everyone. I'll follow-up on your recommendations. I appreciate the help! Regards, Willie
×
×
  • Create New...