Gazoo

Probably an issue with the ROM, then. That type of chip is very sensitive to pin bending and flaky contacts, it could even be the 74LS378 causing the issue. I can do a stand-alone checksum program for that, or maybe even stuff it into that >0798 bytes of Grom I have left. Gazoo

Yes, and I don't anticipate adding anything else. There's >0798 bytes at the end of the TI Diagnostics code that I overlooked while doing the last upgrade, but I don't have any ideas as to what else could be added. Gazoo

050615XB27.dsk The cartridge Grom verifier program is embedded in this version. Flash the cartridge as before. Press F6 to check the integrity of the Grom code. Date is updated on F7 screen, and edge is changed from black to dark blue. Your TI must be working absolutely perfectly for the flash process to work correctly. I got the red screen several times before I succeeded. I had to reseat all the connectors in the system - cartridge, side port, and pbox cards to get everything working properly. Now I get the green screen every time. Gazoo

Well, I like being clear. Some people are colourblind (< spelling ), or don't pay attention unless you SHOUT AT THEM! I'll make it fit. Gazoo

It works quite well. I've been using it for some testing. I've NOT been overwriting TI Basic with the moved EA cart, but rather using the BASICLOAD program in TI Basic to load GROMCFG. That way I still have TI Basic loaded, and it better simulates the XB v2.7 Suite cart. It is a pain to have to reload the Ubergrom Grom data every time I start Classic99, though. Gazoo .

I just discovered that the newest version of Classic99 can write to disk. Cool! Now I can finally assemble code with Classic99, thanks Tursi! Gazoo

If Bert&Ernie and/or Decimal-To-Hex don't run, then the cartridge Grom is corrupted. Both of those are Extended Basic programs, so other Extended Basic programs probably won't run either. And... there's probably other problems with your cart. Check here for the next upgrade in a day or 2. It will have a built in checksum program to see if you've flashed the cart correctly. If you are unable to flash the cart correctly, you'll need to send it to someone who can. Gazoo

The program works, now I just have to find a place in Grom to stash it. There's precious few bytes left, I may have to use the EEprom space... Gazoo

I'm starting on a self contained crc check, I think there might be enough room. That ought to tell those that are having problems whether the problem is in their flashing of the cartridge, or somewhere else in their system. Until that's completed, it's hard to guess as to where the problem some of you are having is. The process works, because many more have succeeded than not. Gazoo

Back when I was doing the 80 track upgrades for the TI Disk Controller, I used the machined sockets. If you look at the board, there are traces that run between the pins. If you push the socket all the way in, it will short some of the socket pins to those traces. You'll never find that with an ohmmeter if you just check the socket pins. The tip I gave to everyone doing the upgrade was to leave the socket up off the board a little, don't push it all the way down. That way you'll avoid shorting the socket pins to the in-between traces. Gazoo

DEC2HEX.dsk Not that I recall, it's an old file. But anything's possible. In deference to Texas Insanity, here's a new disk image to try. The file is shortened by 6 bytes, but still works ok. Apparently that data from >FFFA to >FFFF doesn't matter a whole helluva lot. Gazoo

There's no reason it shouldn't load, as it's a normal EA5 image. Can you load other EA5 files? Gazoo

[DELETEDattachment=390216:DEC2HEX.dsk] Here's something to try if you're one of the people that weren't successful in upgrading your XB v2.7 Suite cart and now you can't run Dec-To-Hex. On the disk is the EA5 program that is executed from cartridge Rom when Dec-To-Hex is selected. Run the file DEC2HEX from TI Writer/Assembler option 6. Does it work? If not, you might not have Extended Basic (Grom page 1) flashed correctly. You may want to try some other Extended Basic programs to see if they work correctly. If it does work, then the Menu page (Grom page 4) wasn't flashed correctly. If you find that you didn't successfully flash your cart, I would suggest you try it with a stock system with original TI cards, and a real floppy drive. Gazoo

Never mind, I found it. Gazoo

How is an entry for a simulated Ubergrom cart in the ini file defined? I think I may have seen an example somewhere, but can't find it now. Gazoo

050315xb27-128kFLASH.bin Programming file with CALL DM2 fix. Gazoo

I'm betting it's the Foundation card that's the problem in the other system. Like the Myarc memory cards, the timing's just a little bit off of the TI 32k card. I've run into that problem before. I'll bet if you swap out the Foundation card for a TI card, it'll work on the other system, too. Probably the same explanation goes for the Nano/CF7 devices. I wonder if Tursi can tweak GROMCFG to allow a little more leeway so the other devices will work... Gazoo

GROMS.dsk Here's another way to upgrade your cart with GROMCFG. I just tried it and it's tedious, but it works. There are 15 Grom files on this disk, numbered GROM0 through GROME. You have to load one Grom at a time through the viewer. The first 5 Groms are at Grom base >9800, the next 5 are at Grom base >9808, 3 are at >980C, 1 at >9810, and 1 at >9814. Note that the last 2, 'GROMD' & 'GROME' are reversed, make sure you put them in the right place. This method might work where the 'whole cart at a time' method failed for you. Gazoo

For those not being able to program their cartridges correctly, here's something you may want to try to see if the data's getting in there right. After you've programmed it, do a ctrl-s and save it. You might have to use another disk if your disk isn't large enough. Save to a differently named data file. Then use Disk Utilities to compare the saved file to the original data file. I'm betting that you're going to find that they're not identical. Gazoo

050215XB27.dsk CALL DM2 fixed. This error must have been present for quite some time and not noticed until now. VDP register 1 was set incorrectly. Cart was reprogrammed on a real TI (stock). All other reported issues were tested and found to be working correctly: - DM2K - Decimal-to-Hex - Catalog from main menu with number keys - Enter key loading of BOOT with powerup hook into 15k of Gram area Gazoo

The image is stable. Apparently everyone with a stock TI system is able to do an upgrade. BASICLOAD has always worked fine for me regardless of whether the 1284p was 'blank' or programmed, so I can't agree with your assessment. Everything points to non-standard hardware interfering somehow with the programming of the device. Perhaps it's a timing issue introduced by the non-standard hardware that is affecting it. Gazoo

It can't be the image as I get identical cartridges using both methods. I've been testing using a stock TI system - TI 32k, TI disk controller (with 80 track mod), Speech synth, stock console (with reset switch). It's always worked fine with this setup, and been confirmed by others to work with a stock system. So maybe GROMCFG doesn't get along with any hardware not stock? Gazoo