Jump to content

chue

+AtariAge Subscriber
  • Posts

    671
  • Joined

  • Last visited

Posts posted by chue

  1. Some guy named the "Curmudgeon Gamer" tested his library of 90 games on both the 60GB PS3 and 80 GB PS3:

     

    On the 60GB PS3, 84 of the 90 games worked perfectly fine, without any problems at all. 4 more had minor problems; 1 required a special controller that did not work with the PS3, and 1 suffered a show-stopping crash.
    On the 80GB version, only 50 of the games worked perfectly (just 56.67% of his library). 12 of them crashed completely, 1 doesn’t work online, and there’s the one that required the special controller.

     

    https://www.hardcoreware.net/playstation-3-80gbs-ps2-backwards-compatibility-sucks/

  2. I thought that the libc99 library from Insomnia Labs, which includes stdio, was actually a working implementation.

    Now that you mention it, you are right - there is an implementation out there. I am not sure how far along it is though.

  3. Does stdio actually work for the TI 99? How can I specify the AORG for the code? Can I also get other formats than EA5?

    .

     

    No, neither stdio nor stdlib are implemented. You will have to use Tursi's libti99, which has a usable printf.

     

    AORG - is this the location where the code resides when running? If so then you can specify it with a linker file. Again, see the samples in the first post. Some of those will specify >6000, as they are in the cart space. Data generally resides in 32k expansion at >A000.

     

    As for formats other than EA5, I am unsure. The only one that I use is a straight "bin" which targets the cart ROM space.

    • Like 1
  4. Ralph, I get the same error when I run your build command. I know for sure that my GCC environment builds. I've had better luck using a makefile - you can find examples of these in the samples in the first post of this thread. Those samples are however, geared towards building binaries that are run from the TI Cartridge ROM space.

     

    I can dig into it a little more later, I just don't have the time now.

  5. And how do I actually compile a C program?

    .

    arcturus ~/ti99/gcc > tms9900-gcc testprog.c -I libc99/include/ -std=c99 -Llibc99
    /home/ralph/ti99/bin/lib/gcc/tms9900/4.4.0/../../../../tms9900/bin/ld: cannot fi
    nd -lgcc
    collect2: ld returned 1 exit status
    

    .

    I searched my GCC hierarchy, but cannot find this library. I only have a directory called ti99/bin/lib/gcc/tms9900/4.4.0/, but this contains only include files.

     

    Could you post your testprog.c?

  6. What the exact installation steps?

     

    I see multiple patches for gcc and binutils. Do I need to apply all those patches or just the latest ones?

     

    It seems gcc patches are about a specific gcc version but which versions are the binutils supposed to patch?

     

    Last time I tried the compilation was impossible under Cygwin 64-bit. Is the compilation now possible?

     

    There is an archive file inside the first post in this thread called "gcc-installer.tar.gz". It contains a bash script that contains the "exact steps". The bash script downloads the proper gcc and binutils versions, and applies the patches. The needed patch files are in the archive as well.

     

    If you are trying to do it manually, you can figure out the versions of gcc/ binutils needed from the patch file names:

     

    binutils-2.19.1-tms9900-1.7.patch

    gcc-4.4.0-tms9900-1.18.patch

     

    The first patch file above has a name which indicates it requires binutils version 2.19.1. Likewise, the second patch file requires gcc version 4.4.0.

     

    As for Cygwin - sorry I have no idea.

    • Like 1
  7. As a 13 year old I took apart my TI because I wanted to see how it worked on the inside. I got it apart and thought I could make it go faster (don't remember how exactly). Anyway unbeknownst to me I ended up killing the power supply. I tried turning it on but the LED did not come on, and obviously neither did the TI.

     

    I was at Radio Shack some time later and noticed they were selling some kind of board that output the exact same voltages as the TI power supply. I didn't know this at the time, but I believe these were the QI power supplies that TI had sold to Radio Shack. I purchased the board and stuck it in the TI and it came back to life. I was super excited about my fix, and my hubris caused me to do some other things with the TI that killed it for good.

    • Like 5
  8. I've been considering doing a custom board that would replace a SNES joystick's (not NES) internal board. The board would not contain any electronics, other than perhaps diodes. It would simply map the directionals and fire buttons to the TI's 9 pin port.

     

    I'm sure you could do the same for an NES style controller.

  9. Losing code - It's happened to a lot of us, me included. Many years ago when I was a college student, I spent many a night in my campus computer lab writing code. On one occasion, I had been up all night doing one of my programming assignments and thought I should clean up my directories. This was all command line stuff back then, and I did a "delete *.*". I was horrified when I realized I was in the wrong directory. I managed to stop the deletion process, but lost a lot of my code.

     

    It was definitely a hard lesson. On the plus side, I learned to be more careful in the future. Also, since I had written the code once already, it was easier the second time.

     

    You can rebuild it Bucko!

    • Like 2
×
×
  • Create New...