Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

446 Excellent

1 Follower


  • Rank

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2,117 profile views
  1. Dragonstomper! I didn't notice, I'd been promoted. Don't be too troubled... Sometimes, things like this are hit or miss. If the fan alone works, I would think that a good heat sink should as well! Se la vie. Does the socketed I.C., ending in 4624N, near the cartridge port, get hot? It would likely be the most intolerant of over-voltage.
  2. I had wondered recently myself how to best troubleshoot these... I have one board "down" and suspect these to be a possible cause.
  3. The fan is blowing on the power supply too. I've never had an issue running w/o the heat sync on VDP. If the VDP is overheating, the issue could still be elsewhere...
  4. My third party floppy drive controller is also a CorComp. I have the original ROMS and two broken(heads) TEAC drives. But I can still, READ somewhat. Guess I'm just cantankerous!
  5. I've had a bad experience operating w/o shielding... ...on some case bottoms there is a steel leaf-spring that helps support the shielding and thus the main-board, near the expansion port. There can be a bit of play on the main-board when connected to that giant, heavy P-BOX connector! This can cause contact between the leaf-spring and the main-board, resulting in a short! So if you do remove the shielding, remove the leaf-spring as well, before reassembling the case, then be careful to check alignment when using the expansion connector.
  6. Yea! Tursi, I spent as much time or more fooling with my, somewhat forgotten, page switcher code ...as did you, with your own tools. From my perspective at the time, it seemed likely that the issue related to EASY BUG having a somewhat different "hand-off". When I got there... I realized I should have saved the R11 return address... So I went back to fix this first... You should have tried it from where I had left off in EASY BUG... you would have probably solved it in a couple minutes! However your video is inciting ...in more ways than one! The Cart Make/Save feature, in Classic 99's Debugger looked good, but did need some explaining. Maybe I should have read the manual. So, armed with your advice, I added four bytes(LWPI >8300)... that did the trick! E7A30 to execute from EASY BUG. Converting EA3 to SSS cart(runs).zip Next, I copied the header from AMBULANCE, than edited it appropriately. The phm3058C.BIN(ok to rename), can be used stand alone or with MINI MEMORY's phm3058G.BIN. Note that, if you load the game directly from FG99's selection list, the GROM will be ignored. Converting EA3 to SSS cart(successful).zip.zip Finally, if you get stuck and want to debug on real hardware, instead of on the PC, EASY BUG and the LINE by LINE ASSEMBLER are at least second or third best. So... Here I have returned the MINI MEMORY's ROM and RAM images, preloaded with LINE by LINE ASSEMBLER and LINES. There are also 56 bytes of boot code to get the game going... The utils load from PAGE 2, the game from PAGE 3, E7FCO does it all automatically. MINIMEM, L by L, and Astiroids.zip Maybe I'll replace LINES, with a small program to move code from CPU RAM to different pages in the MINI MEMORY's image, so that, programs and data can be written with the LINE by LINE ASSEMBLER and then moved easily. P.S. Tursi, nice job trimming the game program down. I missed that. ...Have fun -Alex
  7. Hi Tursi! I've been fooling with this today myself... ...I could use a good walk. I tried setting the breakpoint at the entry address(A000), it helped a little, before that the games entry screen wouldn't even come up! I think the OBJECT file is compressed, just a little extra challenge for me! I'm starting execution from EASY BUG (E7A30)... this switches to page 2, loads utilities to LOMEM, switches back to page 1 and copies the game program up to HIMEM, then executes. Still the game crashes! arrrg. I'm losing patience with this! astiroids.dsk Converting EA3 to SSS cart(BAD).zip
  8. I'm afraid that I'm not yet familiar with Mister or the other tools you've mentioned. I usually try to do things manually, or write my own tools. Since you want to run from 32k anyway, best to load the program there initially... Then if you don't have the source code, you can look it up in the REF/DEF table. The E/A and MM loaders both load to >A000 by default. The entry address could be poked into the header by using EASY BUG and the FG99's MM save option. Alternately, you could use a HEX EDITOR on a dump from Classic99. Do you have an example program?
  9. And still... ...I hate it when that happens!
  10. One issue is that, unless the program was written to run from ROM, it likely wont, because many 9900 instuctions manipulte their destination operand. The FG99 can provide some RAM, but only 4K blocks, from >7000 thru >7FFF. If your programs are small and you load them into that RAM space, using the MINI MEMORY .bin file, you can than look up the entry address in the REF/DEF table, erase all else and write your own header. Alternately, if you have the SOURCE file, you can use AORG to choose your exact load destination.
  11. Have you fired it up? The variable choke coil and xtal, near the VDP, look like an elephant bumped them a little!
  12. no, no, no, not Virtual Reality... ...VOICE RECOGNITION!
  13. I really could have used this around '83... But even now, would be quite welcome! P.S. any thoughts on the V.R. front.
  • Create New...