atrax27407 Posted August 24, 2016 Share Posted August 24, 2016 With all of the new hardware coming out, it might be nice to put together a list of "what does play well with what" (Schmitzi?). For example, the FR99 doesn't like a Vn 2.2 console which is something most us old-timers knew (but probably forgot. I think one of the nanoPEBs had some problems as well. I don't have any of the exotic gear or I would do the testing and listing myself.. 1 Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted August 24, 2016 Share Posted August 24, 2016 hmmm, nice idea, but, for "the list", it has to be planned well, not to "inflate" it. At the moment, I use the column "House, Box, Requirements" to add some compability requirements, i.e. voltages on power supplies, entries like "XB" or TiB" for basic programs, "Plato" if the cartridge is needed, "AMS" if AMS-cards are supported. All in the same column. On the v2.2-console example, here the question is, what to enter.... to enter what IS running with the v2.2, OR what is NOT running with it. I think, the latter is less data to enter ? (is it ?) This should be discussed, to minimize the input of data, and keep the viewability of the lists. And, the "v2.2" is only one issue of incompability, crossing the FR99, and maybe there are more, from a totally other point of view. Maybe it ends up in adding a new column to the table, next to the mentioned "Requirements"-column, called "incompatibility" ? This depends how much incompabilities there are, and we are planning to enter. I think, an extra column is a good way. (although, I prevent from new columns every time ) xXx Quote Link to comment Share on other sites More sharing options...
atrax27407 Posted August 24, 2016 Author Share Posted August 24, 2016 It used to be, in years gone by, that you could simply slide a card into your PEB and everything "played nicely together". That included the original 32K in-console mod. That is because they respected the original TI architecture. That appears to be no longer the case. For example, I'm sure the installation of the F16A precludes an in-console 32K mod if only for lack of space and maybe even one of the sidecar versions being developed. What about a PEB? How does it function with the F18A and the newer 32K mods? What does the CF7 not work with? What about the nanoPEB? Since I don't have any of the above hardware, I can't test it. Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted August 24, 2016 Share Posted August 24, 2016 One of my Nanos boots up with "F18A" text in the startscreen. I think it is the V1, and it is for F18A-compability The PEB should normally run with F18A About the 32KB-things, I don´t know..... Quote Link to comment Share on other sites More sharing options...
Tursi Posted August 24, 2016 Share Posted August 24, 2016 It used to be, in years gone by, that you could simply slide a card into your PEB and everything "played nicely together". That included the original 32K in-console mod. That is because they respected the original TI architecture. That appears to be no longer the case. For example, I'm sure the installation of the F16A precludes an in-console 32K mod if only for lack of space and maybe even one of the sidecar versions being developed. What about a PEB? How does it function with the F18A and the newer 32K mods? What does the CF7 not work with? What about the nanoPEB? Since I don't have any of the above hardware, I can't test it. The F18A takes up less than a square inch more space than the original 9918A, it leaves plenty of room for other in-console mods, including 32k (Which doesn't take much space either). The "original 32k in-console mod" did not respect TI specifications and could not be used with a memory expansion card in the PEB - modern in-console 32k mods are no different in that respect. Both old and new simply drop onto the memory bus and do their thing. (For that matter, the PEB 32k card didn't do anything special, either, and would not be compatible, for instance, with a second 32k card or other memory expansion in the PEB.) All the TI specifications dictated for that sort of card was buffering of the signals, desirable because of the long run to the PEB and potential number of taps. The CF7/NanoPEB take up the side port and don't allow anything to run past them. You can't run 32k, RS232/PIO or disk systems with a NanoPEB attached, because it provides all of these. You also can't run a PEB, except maybe with a splitter, but the above cards will not work. I've read some versions don't like the speech synthesizer either (was that only very early versions?) I think you are remembering with rose colored glasses... there were lots of things that didn't work together in the PEB, even if they did follow the specs. An AMS card wasn't compatible with the 32k, either. Quote Link to comment Share on other sites More sharing options...
+adamantyr Posted August 24, 2016 Share Posted August 24, 2016 The CF7/NanoPEB take up the side port and don't allow anything to run past them. You can't run 32k, RS232/PIO or disk systems with a NanoPEB attached, because it provides all of these. You also can't run a PEB, except maybe with a splitter, but the above cards will not work. I've read some versions don't like the speech synthesizer either (was that only very early versions?) I have two versions of the CF7, both worked with my synthesizer without issue. I can add this though... if you have it plugged in, you HAVE to turn it on, otherwise your console flat out won't work. Which is annoying because the uncovered electronics make for a VERY nasty feedback buzz on the monitor. Quote Link to comment Share on other sites More sharing options...
Tursi Posted August 24, 2016 Share Posted August 24, 2016 I have two versions of the CF7, both worked with my synthesizer without issue. I can add this though... if you have it plugged in, you HAVE to turn it on, otherwise your console flat out won't work. Which is annoying because the uncovered electronics make for a VERY nasty feedback buzz on the monitor. Yeah, that was why I asked, mine works with the synth as well. I also see the same issue with it locking the console if it's not powered on. Quote Link to comment Share on other sites More sharing options...
RXB Posted August 25, 2016 Share Posted August 25, 2016 The F18A takes up less than a square inch more space than the original 9918A, it leaves plenty of room for other in-console mods, including 32k (Which doesn't take much space either). The "original 32k in-console mod" did not respect TI specifications and could not be used with a memory expansion card in the PEB - modern in-console 32k mods are no different in that respect. Both old and new simply drop onto the memory bus and do their thing. (For that matter, the PEB 32k card didn't do anything special, either, and would not be compatible, for instance, with a second 32k card or other memory expansion in the PEB.) All the TI specifications dictated for that sort of card was buffering of the signals, desirable because of the long run to the PEB and potential number of taps. The CF7/NanoPEB take up the side port and don't allow anything to run past them. You can't run 32k, RS232/PIO or disk systems with a NanoPEB attached, because it provides all of these. You also can't run a PEB, except maybe with a splitter, but the above cards will not work. I've read some versions don't like the speech synthesizer either (was that only very early versions?) I think you are remembering with rose colored glasses... there were lots of things that didn't work together in the PEB, even if they did follow the specs. An AMS card wasn't compatible with the 32k, either. Hmm why would you need the old 32K with a SAMS?? One has only 32K and the other 1Meg? What possible reason could anyone have for having both? (Unless it is a 32K installed in the console on bus.) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.