JJB
-
Posts
110 -
Joined
-
Last visited
Recent Profile Visitors
2,829 profile views
JJB's Achievements
Chopper Commander (4/9)
258
Reputation
-
Cool that we both had the same idea of replacing the C64 inversion capability with a char definition.
-
Yes that looks great. Shame the TI doesn't have several shades of gray
-
I was intrigued too and had a go with green instead of red 🙂: 100 CALL CLEAR 110 CALL SCREEN(3) 120 CALL COLOR(9,4,13) 130 CALL CHAR(96,"FFFEFCF8F0E0C080") 140 CALL CHAR(97,"0103070F1F3F7FFF") 160 CALL CHAR(98,"80C0E0F0F8FCFEFF") 165 CALL CHAR(99,"FF7F3F1F0F070301") 170 RV=INT(RND*4) 180 PRINT CHR$(96+RV); 190 GOTO 170 Definitely needs work
-
Totally forgot to mention that APEDSK99 now includes: double density / 80 tracks (max 1440 AU's) directory support: with NDIR command you can change the working /folder DOAD rename (NDSK). The DOAD (MSDOS) name is also used to set the TI DISK name. more detailed info in LDIR / SMAP / LDSK. Includes indicating BASIC files as BAS instead of PRG in LDSK. load real lower case (ACHR). As EXBAS doesn't allow external CALL's in programs I am currently coding to use CALL LINK (which can be used in programs) to enable the relevant CALL's in EXBAS programs through a separate LOADable object file.
- 21 replies
-
- 8
-
-
- apedsk99
- expansion card
- (and 5 more)
-
Thanks! I did very much enjoy developing it. BTW the Italian review post above mentions that it's still evolving but I am pretty much finished with the core development and consider it a fully usable peripheral: - 1 unified DSR binary, no need to use a particular version depending on your GROM 0 - APEDSK99 configuration (network, time zone etc) through a TI BASIC program instead of changing/compiling/uploading an Arduino sketch - no need for soldering on the Ethernet shield anymore; replaced by a simple set of small patch cables that can be installed by anyone In short, much more user friendly I will update the GitHub page / Youtube channel in the next week or so.
- 21 replies
-
- 4
-
-
- apedsk99
- expansion card
- (and 5 more)
-
WARNING!!! on an unmodified console pin 1 carries 12V, you don't want to connect that through! Make sure it's properly disconnected in the console; I am not responsible for blowing up your TI / Scaler / both or any other precious equipment 🙂 I think ideally you should have a separate ground for audio (I have a faint audio hum from supposedly a ground loop) but with only 5-pin connector choices are limited. I guess PAL machines have 6 pins so easy to add a separate ground. My first cable used standard wiring and I did get some interference. I made a 2nd cable using an old VGA cable (COAX based), it did make a difference. It is fiddly to say the least to try to fit such a cable in a DIN harness, but it can be done. TIP: secure the DIN internals with hot glue (after testing ).
-
Let me check
-
Just adding info to this topic as I have just replaced my QI 4116's with 4164's. I had given my non-QI console the same treatment in the past but found removing the original RAM's and replacing them with sockets a royal pain the backside. This time I decided to snip a couple of 4116 pins and piggyback the 4164's on top: - snip 4116 pin 1, 8 and 9 as close to the chip as possible and bend the PCB side remnants out of the way - fold 4164 pins 1, 8 and 9 back on the top of the chip - lightly tin 4116 pins with fresh solder, making sure the pad solder melts too - lightly tin 4164 pins - piggyback a 4164 on 4116 (this is the fiddly bit) and when you're happy with its position, solder 1 4164 pin to its 4116 mate. - solder the remaining pins; with a little bit of fresh solder on your iron, start from the PCB pad and work your way up. - solder a small length of stiff connecting wire to the PCB remnant of pin 9 - connect the other side of the wire to pins 8 and 9 on top of the 4164, taking care the wire doesn't touch any other pins. I did 1 chip at the time, checking for the familiar start screen in between to see if all pins were properly connected (giving the 4164's a little twist at the same time). Jochen
-
... and updating the AVR the normal way now works fine?
-
If I put just one cart image on the SD, it is listed directly as choice 2. What do you see then: nothing, the FG99 choice with just one cartridge, anything else etc? On a separate but related topic: you were going to program the AVR in 2 FG99's out of circuit to see if it would enable the normal AVR update process (a la Geoff's approach); curious if you have any results to share?
-
@Geoff Oltmans I have sent you a message
-
Yes I will upload when home from work
- 126 replies
-
- 1
-
-
- finalgrom99
- fg99
- (and 1 more)
-
I guess your experience is similar to some other members experiencing FG99 instability / random behavior at times. Your marginal comment triggered me as well; although I can't speak for the FG99 I have designed a sideport peripheral myself with an initial batch of 5 working right of the bat after assembly (the hardware isn't overly complicated). 8 months later, I am now building a second batch of 5 with the initial 2 displaying weird timing behavior. I can only conclude that some of the IC's I ordered recently are either marginal or fake. And yes most of them come from reputable sources although for some I can't avoid Ebay. Still curious if the updated AVR would work through your programmer ;-)
- 126 replies
-
- 2
-
-
- finalgrom99
- fg99
- (and 1 more)
-
Hi Geoff, This is puzzling; you say the out of circuit programming went OK (presumably with 1.3?) but when you tried to update the AVR it screwed things up and you had to get out your programmer again; but for the 2nd screw-up you were able to update the AVR normally? Did you try to load the updated AVR firmware at all through the programmer? What about the updated CPLD?
-
@dhe any update on your FG99's you sent off?
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord