Archive

Archive for January 18th, 2015

TMS 9900 CPU Key Ring

January 18th, 2015 1 comment
TMS 9900 CPU Key Ring

TMS 9900 CPU Key Ring.

CBM prg Studio v3.2.1 released

January 18th, 2015 No comments

CBM prg Studio Version 3.2.1 is released. There are a lot of new features in this version. I’d really appreciate it if you report any bugs you find or have any suggestions/comments.

CBM prg Studio allows you to type a BASIC or Machine Code program in using a nice Windows environment and convert it to a ‘.prg’ file which you can run on an emulator, or even a real C64 / VIC20 or PET if you’re feeling brave and have the right kit.

CBM prg Studio is the result of merging C64PrgGen and VIC20PrgGen. Adding new features and fixing bugs in two apps which were 95% similar was a bit of a nightmare so merging them made sense.

It was also a good opportunity for a face lift and to add some new features, such as:

  • Programs are project based, meaning all related source files, sprite files etc. are kept in one place and multiple source files can be linked more easily.
  • Tabbed MDI.
  • Syntax highlighting.

What CBM prg Studio isn’t is a front-end for tok64, cbmcnvrt, bastext or any other tokeniser / detokeniser / assembler. It’s all been written completely from scratch.

New features:

  • Screen designer speed up.
  • Speed up of switching/adding/opening files and projects.

Bug Fixed:

  • Assembler:
    • Duplicate labels not detected in projects.
    • SYS call always created at start of file.
    • Build order not correct.
    • Assembly dump showing both parts of the code within conditional assembly statements.
    • Code reformatting issues.
    • Negative numbers in BYTE and WORD sequences not assembled properly.
    • Numbers in strings in BYTE sequences not assembled properly.
    • Numbers in TEXT sequences not assembled properly.
    • Arithmetic in WORD sequences not assembled properly.
  • General:
    • Sprite Designer grid glitches.
    • Exception thrown when generating .prg with the output window closed.
    • Code indent/outdent/comment/uncomment would add extra carriage return.
    • Code comment/uncomment would add extra REM statements.
    • Problem adding existing files to a project.

Download: CBM prg Studio v3.2.1 (1081)

source: ajordison.co.uk

A couple of Texas Instruments TI-99/4A Home Computer repaired

January 18th, 2015 3 comments

I have repaired nine motherboards of the Home Computer Texas Instruments TI-99/4A for a dear friend. Below the description of each repair.

Texas Instruments TI-99/4A Repair (1 of 9)

Defect:

  • Blue Screen with tiny Vertical lines and deafening sound … and then garbage screen.

Replaced parts:

  • 1 x 1501392-27 ROM (U611)
  • 2 x 4116 RAM (U102 / U105)
  • 1 x 74LS245 OCTAL BUS TRANSCEIVER (U614)
  • 1 x 74LS03 QUAD 2-INPUT NAND GATE (U506)

Texas Instruments TI-99/4A Repair (2 of 9)

Defect:

  • Blue Screen with tiny Vertical lines and deafening sound.

Replaced parts:

  • 1 x CD3227A ROM (U611)
  • 1 x CD3226A ROM (U610)

Texas Instruments TI-99/4A Repair (3 of 9)

Defect:

  • Garbage Screen.

Replaced parts:

  • 4 x 4116 RAM (U105 / U106 / U108 / U109)

Texas Instruments TI-99/4A Repair (4 of 9)

Defect:

  • Blue Screen with tiny Vertical lines and deafening sound.

Replaced parts:

  • 1 x MCM 6810P RAM 128×8 (U609)

Texas Instruments TI-99/4A Repair (5 of 9)

Defect:

  • Blue Screen with tiny Vertical lines and deafening sound.

Replaced parts:

  • 1 x MCM 6810P RAM 128×8 (U608)
  • 1 x 1501392-27 ROM (U611)
  • 1 x 74LS138 1-OF-8 DECODER/DEMULTIPLEXER (U504)

Texas Instruments TI-99/4A Repair (6 of 9)

Defect:

  • Blue Screen with tiny Vertical lines and deafening sound.

Replaced parts:

  • 1 x CD3226A ROM (U610)
  • 1 x 74LS138 1-OF-8 DECODER/DEMULTIPLEXER (U504)

Texas Instruments TI-99/4A Repair (7 of 9)

Defect:

  • Blue Screen with tiny Vertical lines and deafening sound.

Replaced parts:

  • 1 x TMS 9900-NL CPU (U600)

What happened to the other two motherboards ?

  • The eighth motherboard was used for spare parts.
  • The ninth motherboard has all components burned (Power Supply problem?)