Jump to content
IGNORED

Setting up a 512k cart


Gazoo

Recommended Posts

Really? Parsec too? Cool! Didn't know so many of them were made into EA/5 executables. I'm sure we can shoehorn the GROM only ones in there too with that "GPL simulator".

 

Are there any Grom-only game carts? I thought they were all converted. Maybe I'm wrong, I haven't seen VIDEO CHESS anywhere. :)

 

Gazoo\

Link to comment
Share on other sites

 

If they all were, I sure would like a complete set of them... :)

 

I've asked this question (as have others) over the years and it seemed folks didn't know or couldn't be bothered to answer.

I for one would also like to know how GROM was converted to assembly/memory image :-)

Link to comment
Share on other sites

I for one would also like to know how GROM was converted to assembly/memory image :-)

My GPL HOW2 Series shows how to do that.

 

I even included the software used and you can convert any cart that does not have a ROM but even that is possible to do with much more effort.

 

http://atariage.com/forums/topic/153704-ti-994a-development-resources/

 

GPL HOW2A shows using the GPL Compiler and Linker.

If you copy a cartridge as DATA then convert that to a GPL Source file you can create a GPL LINKER that runs it from Assembly by making that GPL run like Assembly.

 

Of course if a ROM is needed then it gets much more complicated to do.

  • Like 1
Link to comment
Share on other sites

My GPL HOW2 Series shows how to do that.

 

I even included the software used and you can convert any cart that does not have a ROM but even that is possible to do with much more effort.

 

http://atariage.com/forums/topic/153704-ti-994a-development-resources/

 

GPL HOW2A shows using the GPL Compiler and Linker.

If you copy a cartridge as DATA then convert that to a GPL Source file you can create a GPL LINKER that runs it from Assembly by making that GPL run like Assembly.

 

Of course if a ROM is needed then it gets much more complicated to do.

 

Nice! So it's a linker that really loads and runs the GPL. Is it actually translating once you link it? Or is the stub (I noticed the 1 sector file) actually the part that intercepts and translates? Is this also how that XB "GPL Simulator" worked? I remember eons ago how Jim Lesher had given me this "translate to GPL" disk called DUMPIT. It had detailed instructions on BUGOUT on how to use the cartridge expander to dump GROM only carts and then sector edit something in them, tack on this XB loader (or load in E/A5 and voila - it would load it to 32K. I think the limit was 4 GROMs, I remember seeing something about Tunnels of Doom not working since it was 5 (30K).

          &GROM^MODULE^DUMP^PROCEDURE.
          .
          .
          Put Bugout, the Editor/Assembler Save utility, Disko and the two
          loaders on one disk.  Insert the module to be dumped and the
          Editor/Assembler in a widget..
          .
          .NF.
          Load Bugout.
          .
          E/A #3 - DSK1.BUGOUTO.
          .
          Switch to the module to be dumped and check the grom addresses..
          .
          MG>6000   GROM ADDRESSES 1 - >6000-7800
                                   2 - >8000-9800
                                   3 - >A000-B800.
                                   4 - >C000-D800.
                                   5 - >E000-F800.
          .
          Transfer the chip to be dumped to high memory..
          .
          TR.G6000.E000.6144     Note: 6144 = 6K.
          .
          Load the Save utility..
          .
          LO  Enter  -   DSK1.SAVE.
          .
          Change the load pointers for the Save utility..
          .
          MEC>2CA4                  New Value       Address for 2CC4
                    SLOAD  -  2CC4  -  A000    Chip 1 - A000 - 87FF
                    SFIRST -  2CCC  -  E000    Chip 2 - B800 - CFFF
                    SLAST  -  2CD0  -  F7FF    Chip 3 - D000 - E7FF
                                               Chip 4 - E800 - F7FF.
          .
          Run the Save utility..
          .
          EX.SAVE   Enter  -  Type DSK2.NAME2.
          .
          Switch to the Disk Manager and copy a load program to the dump
          disk as NAME1.  If the module has more than one chip you must use
          the Disko program to change the first two bytes of the dumped
          chips to FFFE except for the last chip.   The first area of each
          dump should look like:.
          .
          00001805A000AA01 ect.   Disko changes a sector by pressing fctn 8.
          .
          Do a seperate dump for each chip..
          .
          Run the program with E/A #5.  If it doesn't work, try a diferrent
          loader..
 
......................
             SUPPLEMENT TO MODULE GROM-DUMP PROCEDURE
 
 
*STEP 1*
     Place the following all on one disk:
          -BUGOUTO
          -DISKO
          -YLOAD
          -LOADER/A
          -LOADER/B
          -SAVE
.
*STEP 2*
     Install Navarone's Cartridge Expander ("widget") into computer console
     with the following:
          -Editor/Assembler cartridge
          -cartridge to be dumped
          -Disk Manager cartridge (or Extended Basic if using another disk
           manager such as DM1000)
.
*STEP 3*
     Select Editor/Assembler with slide switch on widget.  Turn computer on.
     When the main screen shows on monitor, press any key to get to the option
     screen.  Press <2> to select Editor/Assembler.  When the option screen
     appears for Editor/Assembler, press <3> for "LOAD AND RUN".  The screen
     then shows:
 
     *  LOAD AND RUN *
     FILE NAME?
 
     Make sure the disk you made above is in disk drive 1, then type in the
     following:
                DSK1.BUGOUTO
     Then press <ENTER>.  The computer then proceeds to load "BUGOUTO" from
     your disk in drive 1.
     The screen now shows the following:
 
            THE BUGOUT MACHINE LANGUAGE MONITOR
 
                     COPYRIGHT 1984
 
                           BY
 
                     GREGG WONDERLY
                                             3.0
              PRESS <ENTER> TO START MONITOR
 
     Now select the cartridge you want to dump by sliding the switch on the
     widget to the spot that corresponds to the place on the widget where that
     cartridge is installed.
     Then press <ENTER>.
..
     You will then see the following on the screen:
 
           0000=83E0 0024 83C0 0900           $
           0008=83C0 0A92 30AA 0460          C 0  \
           0010=02B2 0008 1E00 0460               \
           0018=007A 1E00 0460 0078         Z    \X
           0020=0460 04B2 020D 9800         \
           0028=020E 0100 020F 8C02
           0030=0200 0020 1013 1000
           0038=1E00 02E0 280A 0380            <C
 
           >0000 C    @>0024,R15
           >0004 C    R0,R15
           >0006 SRL  R0,0
           >0008 C    R0,R15
           >000A SLA  R2,9
           >000C LDCR @>0460(R10),2
           >0010 DATA >0252
           >0012 DATA >0008
           >0014 SBZ  >0000
 
     At this point, we are now about to check to see which of 5 possible chips
     in the cartridge are installed with programming that must be dumped.
 
     Type in: MG>6000
     Press <ENTER>
 
     The top section of the screen will be changed.  Below is an example of
     what will be displayed:
 
           6000G=AA01 0100 0000 6010          \
           6008G=0000 0000 0000 0000
           6010G=0000 601F 0A45 4152      \DcEAR
           6018G=4C59 204C 524E 4739    LY LRNG9
           6020G=0007 018D 4786 7486        G T
           6028G=7ABE 737E 3100 38A7    Z S~1 8
           6030G=8097 8DBE A300 D006
           6038G=6A6C 066B D108 5F20    JL K  _
 
     The "MG>6000" still remains at bottom of screen.  The new information
     displayed in the above example indicates that chip 1 has programming to be
     dumped.
 
     Now type in: MG>8000
     Press <ENTER>
 
     The top section of the screen will again be changed.  Similar information
     may then be displayed.  If so, then we would know that chip 2 must also be
     dumped.
 
     We likewise proceed with chips 3, 4, and 5.
 
     *WHEN CHECKING CHIP NUMBER*        *TYPE IN*
                 1                       MG>6000
                 2                       MG>8000  *NOTE: These grom addresses
                 3                       MG>A000         are in hexadecimal, so
                 4                       MG>C000         "0" is zero, not the
                 5                       MG>E000         letter "O".
..
     If any of the chips is either empty or nonexistent, you would get a lot of
     zeros on the screen.  An example is given below where chip 3 was checked
     and no information was found to be present.
 
 
 
           A000G=0000 0000 0000 0000
           A008G=0000 0000 0000 0000
           A010G=0000 0000 0000 0000
           A018G=0000 0000 0000 0000
           A020G=0000 0000 0000 0000
           A028G=0000 0000 0000 0000
           A030G=0000 0000 0000 0000
           A038G=0000 0000 0000 0000
 
     These zeros indicate that we do not need to attempt to dump this chip.
 
     You must check all five possible chips, even if you come to one which has
     no information on it, since a subsequent chip may be found to have
     information on it.  WE ONLY DUMP THOSE CHIPS THAT WE FIND HAVE SOMETHING
     ON THEM.
 
          In addition to checking the 5 GROM chips you must also check to see.
     if the cartridge being dumped has a ROM chip in use..
.
     Type in:  ME>6000.
     .
     If you see anything other than zeros as in the above example, a ROM chip.
     is in use.  If a ROM chip is being used you CANNOT dump the cartridge to.
     disc with this program..
 
*STEP 4*
     This step involves the dumping of each chip, one at a time, to disk.
      (1) First, transfer the chip to "high" memory.  This is done by first
          typing in the expression listed below for the particular chip being
          dumped.
              *CHIP BEING DUMPED*        *WHAT TO TYPE IN*    NOTE: Again, the
                       1                 TR.G6000.E000.6144      "0" is the
                       2                 TR.G8000.E000.6144      number "zero",
                       3                 TR.GA000.E000.6144      not the
                       4                 TR.GC000.E000.6144      letter "O".
                       5                 TR.GE000.E000.6144
 
          So, if Chip 1 is being dumped, just type in: TR.G6000.E000.6144
 
          Next, press <ENTER>.  The computer then copies the information (from
                                whatever chip is being dumped) to "high"
                                memory.  (Note that the screen appears
                                unchanged.)
 
      (2) Press the <FCTN> key and the number <3> key at the same time.  This
          erases the last line you typed in.
 
      (3) The SAVE utility must now be loaded.  Make sure that the disk you
          started with is still in drive 1.
          Then, type in:
                           LO
 
          Then, press <ENTER>.
          The computer then shows the following :
                                                    ENTER DEVICE.FILENAME
 
          Type in:   DSK1.SAVE
 
          Then, press <ENTER>.
          The computer now loads the SAVE utility from your disk.
..
      (4) Next, the "load pointers" for the SAVE utility must be entered.
          These pointers vary for each chip dumped.
          First, type in:
                          MEC>2CA4
 
          Then, press <ENTER>.
          The following is then shown on the screen:
 
          2CA4=286E 16FA C203 0648    (N     H
          2CAC=0204 2B32 60C4 C103      +2\
          2CB4=0603 0283 0003 11D4
          2CBC=06C3 D803 2B31 0206        +1
          2CC4=0000 C806 2BD4 0206        +
          2CCC=0000 0207 0000 61C6          A
          2CD4=115B C087 0287 1FFA     [    [
          2CDC=1102 0202 1FFA C282        [
 
          >0000  C    @>0024,R15
          >0004  C    R0,R15
          >0006  SRL  R0,0
          >0008  C    R0,R15
          >000A  SLA  R2,9
          >000C  LDCR @>0460(R10),2
          >0010  DATA >02B2
          >0012  DATA >0008
          >0014  SBZ  >0000
 
 
 
 
 
       -->MEC>2CA4
 
          There are 3 separate sets of "0000"; the first set of "0000" is found
          at the blinking cursor.  The second "0000" is directly below the
          first.  The third "0000" is located to the right of the second "0000"
          and is separated from the second "0000" by "0207".  Note where these
          3 sets of "0000" are; you must change each of them as indicated in
          the following chart:
 
          CHIP BEING DUMPED:               1      2      3      4
          NEW VALUE FOR FIRST "0000":    A000   B800   D000   E800
          NEW VALUE FOR SECOND "0000":   E000   E000   E000   E000
          NEW VALUE FOR THIRD "0000":    F7FF   F7FF   F7FF   F7FF
 
          Change the first "0000" now by typing in the "new value for first
          '0000'" from the chart above.  The cursor will then be over the "C"
          of the "C806" found to the right of the first "0000", but the first
          "0000" has been changed to whatever value you just typed in.
 
          Then, press the <FCTN> key and the <E> key at the same time (but just
          press them once and do NOT hold them down).  This will move the
          cursor to the second "0000".  (If you press these two keys more than
          once or hold them down too long, the cursor will pass the second
          "0000".  If you do so accidentally, you can move the cursor back up
          to the second "0000" by pressing the <FCTN> key and the <X> key at
          the same time as necessary.)
..
          Now that the cursor is at the second "0000", change it by typing in
          the following:  E000
 
          The cursor will now be flashing over the "0" of the "0207" which is
          to the right of the second "0000" (which you just changed to "E000").
 
          Move the cursor to the third "0000" by pressing the <FCTN> key and
          the <D> key four times, or just until the cursor is directly over the
          first "0" in this last set of "0000".
 
          Now change this "0000" by typing in:  F7FF
 
          Then, press <ENTER>.
 
          The cursor is now over the "M" of "MEC>2CA4".
 
          Erase the "MEC>2CA4" by pressing the <FCTN> key and the <3> key at
          the same time.
 
      (5) Now, all is ready to dump the selected chip.  To do so, the SAVE
          utility must be run.  Do so as follows:
 
          Type in:  EX.SAVE
 
          Then, press <ENTER>.
 
          The screen changes to the following:
 
                                            SAVE M
          EMORY IMAGE
                           1. PROGRAM TO BE SAVED
          MUST        ALREADY BE LOADED.
                                           2. THE
          FIRST WORD IN THE           PROGRAM MUST
           BE EXECUTABLE.
                   3. PROGRAMS WHICH ARE BIGGER
              THAN 8K WILL CREATE NEW         FILE
           NAMES BY ADDING A ONE      TO THE LAST
          BYTE OF THE         CURRENT FILE NAME.
 
           CURRENT FILE :
                                   STATUS:
 
 
                                    ENTER FILE NAM
          E?
 
 
 
          -->EX.SAVE
 
          Before proceeding from here, choose a file name for the cartridge
          being dumped.  For example, if the cartridge is called "Cartridge",
          you might abbreviate it to "CART" when choosing a file name.  But
          each chip dumped for the cartridge must have identical file names
          except for the last digit, which must be a number.  See the following
          chart for an EXAMPLE.  (Note that the first chip dumped ends in a
          "2".)
..
             *CHIP DUMPED*               *FILE NAME TO BE TYPED IN*
                 First                          DSK1.CART2
                 Second (if any)                DSK1.CART3
                 Third (if any)                 DSK1.CART4
                 Fourth (if any)                DSK1.CART5
 
          Type in the file name you chose as exemplified in the above chart.
 
          Then, press <ENTER>.
 
          The computer saves the file to disk.  After it does so, the computer
          may freeze up (e.g. the screen may go haywire and you might hear a
          long single tone coming from your monitor or TV).  Press the reset
          button on the "widget" or turn the console off then on.
 
          Repeat steps (1) through (5) until all the chips have been similarly
          saved to disk.
 
*STEP 6*
     This step involves making a small correction in each "dumped chip" except
     for the last one you dumped to disk.  (If only one chip had to be dumped,
     then no changes need to be made.)  Each "dumped chip" is a separate file;
     the corrections you make in these files enable the computer to link them
     when you eventually try to run them.
 
     Each file is made up of sectors; it is the first sector of each file that
     you are concerned with.
 
      (1) To first find these sectors and then edit them, you will need to load
          the "DISKO" program.
 
          Press the reset button on the "widget".  Your selector switch on the
          "widget" should still be at the position for the Editor/Assembler.
 
          Press any key to get to the selection screen.  Then, press <2> to
          select Editor/Assembler.
 
          Then, when the Editor/Assembler option screen appears, press <3> for
          "LOAD AND RUN".
 
          The screen then shows:
 
                 * LOAD AND RUN *
 
                 FILE NAME?
 
          Remember, here the "O" in "DISKO" is the letter "O".
 
          Type in:  DSK1.DISKO
 
          Then, press <ENTER>.
 
          The computer then loads the program from your disk in drive 1.
..
          The screen then shows:
 
                 * LOAD AND RUN *
 
                 FILE NAME?
 
          Press <ENTER>.
 
          The screen then shows:
 
                 * LOAD AND RUN *
 
                 FILE NAME?
 
                 PROGRAM NAME?
 
          Type in:  DSK
 
          Then, press <ENTER>.
 
          The screen then shows:
 
                 1. DISK SECTOR EDITOR
 
                 2. SEARCH FOR EXISTING FILE
 
                 THIS VERSION OF "DISKO" WILL
                 HANDLE DOUBLE-SIDED,
                 DOUBLE-DENSITY DISKS.
 
      (2) Now you are ready to find where the first sector of each file is.
          Again, you need only to find the first sectors for all files except
          for the last one (which represents the last chip dumped).
 
          Press <2>.
 
          The screen then shows:
 
                 DRIVE NUMBER: 1
 
          If your disk (which contains the dumped-chip files) is still in drive
          1, just press <ENTER>.  (Otherwise, press the number that corresponds
          to which drive your disk is in.)
 
          The screen then shows:
 
                 DRIVE NUMBER: 1
 
                 FILE TO BE FOUND?
 
          Now type in the file name for the first chip you dumped, but without
          the "DSK1." part of it.  (For example: CART2 )
 
          Then, press <ENTER>.
..
          The screen then shows something like this:
 
                 DRIVE NUMBER: 1
 
                 FILE TO BE FOUND?
 
                 CART2 (or the name of your file)
 
                 FILE HEADER AT SECTOR 00B
 
                 FILE TYPE:        PROGRAM
                 RECORD TYPE:      FIXED
                 WRITE PROTECTED:  NO
 
                 START SEC  END SEC  FILE OFFS
 
                    10F       127       018
 
          It is the (hexadecimal) number found under "START SEC" that tells you
          which sector is the first sector for the file you are looking for.
          Write this number down.
 
          Press the <FCTN> key and the <9> key at the same time.
 
          The screen again shows:
 
                 1. DISK SECTOR EDITOR
 
                 2. SEARCH FOR EXISTING FILE     [etc.]
 
      (3) Now you are ready to edit this sector you found.
 
          Press <1>.
 
          The screen then shows:
 
                 DISK EDITOR UTILITY
 
 
                 DRIVE NUMBER: 1
 
          If your disk is in drive 1, just press <ENTER>.  (Otherwise, press
          the number that corresponds to which drive your disk is in.)
 
          The screen then shows:
 
                 DISK EDITOR UTILITY
 
 
                 DRIVE NUMBER: 1
 
                 SECTOR NUMBER:
 
          Type in the (hexadecimal) number you wrote down.  (Remember that the
          "0" here, if any, is a "zero" and is not the letter "O".)
 
          Then, press <ENTER>.
..
          The screen then shows something like this:
 
                             HEX     10F
 
                 00001805A000AA01010000006010
                 0000000000000000000060261142
                 5544474554204D414E4147454D45
                 4E54BE3103BE3304BE3507BE3708
                 390002038F3BBEA300D0BF4A0400
                 0600183436A380A37FBFA382FFFF
                 3034A32294AF310010A5D88F4534
                 36A5E8A850BEA310FC0684A5FF35
                 0100A600AA00BEA318153430A319
                 A318310020A7008F55BFA31C159C
                 BEA748FF3434A749A74807340405
                 0881B4C25B8083FB6098FB066183
                 0190014A01F4020C00F201C8011A
                 021C020401D800A2008E010600D6
                 08C603E8E8E9E9FB60C081FB0661
                 9C06947F0682E1D67DE460E5BDE0
                 400EE0200EBDE0200EB00ED67F1C
                 40CE35001EEFFFE40EEFFFC40ECA
                 7E074101
 
          The top line shows "HEX" and the sector number you typed in.
 
          Below that is a block of hexadecimal numbers.  The top line in that
          block of numbers starts with "0000", the first "0" of which is
          underlined in red.  This "0000" must be changed.
 
          First, press the <FCTN> key and the <1> key at the same time.
 
          Then, type in:  FFFE
 
          The "0000" will have changed on the screen to "FFFE", and the red
          underline will be under the number to the right of the "E" of this
          "FFFE".
 
          Press the <FCTN> key and the <8> key at the same time.
 
          A new line appears at the bottom of the screen. It says:
 
                 REWRITE THE SECTOR (Y/N)?
 
          Press the <Y> key.
 
          The computer then accesses the disk drive and changes that sector the
          way you changed it on the screen.
 
          Press the <FCTN> key and the <9> key at the same time to get back to
          the previous screen.
 
          Repeat steps (2) and (3) until all of the files have been likewise
          changed (except for the file which represents the last chip dumped).
 
          When done, press the <FCTN> key and the <=> key at the same time to
          leave this "DISKO" program.
..
*STEP 7*
     Select the Disk Manager cartridge (or Extended Basic, if using DM1000).
     with the widget.  Look up the directions that accompany the disk manager
     for changing the name of a file from one name to another.  Change the name
     of "LOADER/B" to the file name you first selected for you dumped chips,
     but change it so that the name ends in the number "1".  For example, if
     your dumped files were CART2, CART3, etc, then rename LOADER/B so that its
     new name is "CART1".
 
*STEP 8*
     This is the LAST step.  This step involves typing in a short Extended
     Basic program and then saving it to your disk.  The program should be
     typed in as follows below, except that you must substitute the new name
     for LOADER/B (that you made in STEP 7) for the "CART1" in line 20.
 
     10 CALL INIT :: FOR X=1 TO 4
      :: CALL LOAD(-6144*X,0):: N
     EXT X
     20 CALL LOAD("DSK1.YLOAD")::
      CALL LINK("LOAD","DSK1.CART
     1")
 
     Note that, in line 10, the "0" (that is in the parentheses after "CALL
     LOAD") is the number "zero" and not the letter "O".
 
     Save this program to your disk by typing in:  SAVE DSK1.LOAD
     then press <ENTER>.
 
     The program will now automatically load in Extended Basic.
 
 
 Please note that I have never been able to successfully dump and then run a
 cartridge that has more than 4 chips.  Also, some other cartridges will not
 run properly.  Good luck in your endeavors....
......................

This is actually pretty cool stuff. I'll have to watch more of your GPL videos.. thanks for doing those!

DUMPIT.DSK.zip

Link to comment
Share on other sites

Really? Parsec too? Cool! Didn't know so many of them were made into EA/5 executables. I'm sure we can shoehorn the GROM only ones in there too with that "GPL simulator".

 

There are problem with missing graphics in the EA5 version of Parsec. Probably because it was difficult to fit in 8K ROM + 24K GROM in RAM.

Link to comment
Share on other sites

 

There are problem with missing graphics in the EA5 version of Parsec. Probably because it was difficult to fit in 8K ROM + 24K GROM in RAM.

 

I didn't notice anything like that. But I can't get very far in the game, either.

 

Parsec.zip

 

 

Gazoo

Link to comment
Share on other sites

 

If they all were, I sure would like a complete set of them... :)

 

I've asked this question (as have others) over the years and it seemed folks didn't know or couldn't be bothered to answer.

 

Look around on whtech, that's where I got almost everything I have.

You've got to be patient enough to look through the zips and dsk files.

Downloading the whole site makes it a lot easier, too.

 

Gazoo

Link to comment
Share on other sites

 

Look around on whtech, that's where I got almost everything I have.

You've got to be patient enough to look through the zips and dsk files.

Downloading the whole site makes it a lot easier, too.

 

Gazoo

 

As a first shot on WHTech, sitelist.txt in the FTP root is your friend. Don just updated it a couple of days ago. Likely due to Ernie's disk image additions, sitelist.txt has doubled in size.

 

...lee

Link to comment
Share on other sites

When the AMS and later the SAMS came out we discussed GROM Emulatin using the RAG GPL LINKER to convert all the GROM games to run from the SAMS.

 

As many of these games use almost the same ROM routines and some the same GROM routines we thought it would be possible to make one DSDD Foppy with many many games for loading and running.

 

The Atari Games for example have much of the code exactly the same and in the same place.

  • Like 1
Link to comment
Share on other sites

That's actually a very nice idea, Rich--something like that would have been the killer app to get folks to switch over to AMS/SAMS memory cards. Utilities get programmers and geeks to switch over--but games, those speak to the masses. :) :) It would actually make sense to do that even now--as you could also put your resulting files into one of the 512K carts and run everything from there (in addition to a disk-based option)--with both media feeding the files into AMS memory to execute.

 

I suspect that you, Gazoo , and Tursi are the only GPL programmers left who could pull it off though.

Edited by Ksarul
  • Like 1
Link to comment
Share on other sites

Does anyone know of an easy way to invert a 512k Rom file in 8k chunks?

 

There should be a way to make a batch file to accomplish the task instead of having to do it manually, which is a major PITA.

 

Gazoo

Link to comment
Share on other sites

Here's the game cart, both forward and backward Roms.

I haven't tested it other than to select a few games, and they seemed to work.

 

Let me know if there are any bugs.

 

Thanks,

 

Gazoo

 

 

[deleted attachment=340004:Gamecart.zip]

Edited by Gazoo
Link to comment
Share on other sites

I downloaded the file and programmed it into a PLCC. When I select ANY of the games, I get a blank cyan screen. When I programmed the chip, it erased OK, programmed OK, and verified OK. Ideas?

 

Try the backwards file in Classic99. The file without the backwards in the name should be programmed for a cart with a 378 chip.

The games do come up in Classic99, I have no other way to test at the moment.

 

Gazoo

Link to comment
Share on other sites

Gazoo,

 

The Backwards file works fine in Classic99. The other one does on real TI gear. I programmed a second chip to make sure with the same results.

 

So the non-backwards one works on your physical cart? I'll try it on mine and see what it does. If Gazoo put the first/last bank the same (or did a "write to >6000 header") it should come up on either variant of 378.

Link to comment
Share on other sites

The non-backwards file does NOT work on real TI gear. The menu screen comes up but when you select a game all you get is a blank cyan screen. The fact that there are two different files leads me to believe that he didn't duplicate the menu in both the first and last bank.

 

That's not the reason why I'm supplying two files.

 

The entire menu doesn't need to be duplicated, that's not how it works. The file header in the last bank throws you into the first bank, as I described in a previous message.

 

There are two files because Classic99 requires the 8k blocks to be in a backwards order from a cart with a 378 bank select chip in it. Hence the 'backwards' in the reverse order file. The 'backwards' file is provided for testing in Classic99. The file without the 'backwards' in it should be used to burn a chip for use with a 378 bank select chip.

 

The Game Rom works in Classic99 as do the previous 2 Roms I created, the program menus with and without Groms included. I have no explanation as to why you are having trouble getting this Rom to work on a real TI, as it is set up the same.

 

Gazoo

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...