Fonzie

Thanks Harry. Once I put the Juwel4 folder into the classic99 folder alongside DSK1 ,2, and 3, it all worked perfectly.

Don't know if this means anything but immediately after the error message:**DSR Error:00f4 DSK!.runtime1.txt (there is a space followed by 2 or 3 jibberish characters). Also, checking the Juwel folder there is no file listed as runtime1.txt. There are ,however, several files named runtim(1-9) -s.

Yes, I double checked. All boxes are checked as shown in the image on the pdf.

I love tinkering on real iron. Today, on a whim I decided to try to compile a simple xb using Classic99 and the latest XBGDP. Downloaded and installed Classic99 Q1399.663 and Juwel4 +GEM. I put the Juwel99 folder in with DSK 1,2 & 3 of CLASSIC99. Configured Disk 1 to .\Juwel99\ and checked the appropriate boxes as shown in the XBGDP.pdf. I ran Hello slow & fast and saved it. Everything seemed to run ok. Xb, compiler, assembler until the R underscore. Hitting enter brings up **DSR ERROR:00F4 DSK1.RunTime1.TXT. I’m embarrassed to tell you how many times I’ve blown away both programs re-downloaded them again and tried many variations to no avail. Any Ideas?

Successfully went to XB from force command once I understood that TIXB_G didn’t exist but was just a renamed XB bin on the fg sd card. Duh. There were several XB versions on the fg download. I experimented a bit, renamed the bins for ease and speed and loading XB from fg worked. Thanks. Additional features are still a wip.

Where is TIXB_G and related ROM files alluded to in the force command wiki? I would love to be able to drop into XB or use a call function or… anything. As it stands now FC is almost useless to me because of my inability to use it to its full capability. I’ve been lurking for a long time, watched and rewatched several ti videos read the force command wiki many times and still I am not able to make much use of force command. If only there were a Dummy’s Guide. It doesn’t help that I am rapidly approaching the precipice of ARD (age related dementia). Not there yet but on my way.

Today was the first time I did access the web-ui. I did notice that you can shut down the rpi from there. Had I connected here before it might have saved me from all of the re-installation fiasco. You see previously I always went to basic called tipi and pressed H to halt the rpi. But the console screwed up and I wasn't able to get basic going again to properly shut down the rpi. So, I just unplugged it without halting it first. Anyway, the next time I booted I had trouble getting tipi to run and when I did get it running the blank PDFs showed up. I thought I had compromised the sd, and well you know the rest. Anyway, I opened the tipi log and copied it to a Word file. It is 7 pages long did you want me to try to attach it here in this forum? It's all Greek to me.

Success! I finally got TIPI back to running the way it used to for me. PDF’s are no longer blank; I can actually read them. Long story short: I used one of the 64gb sd’s that Etcher would not burn the image and tried Win32DiskImanager which did work. Then installed back in the pi, I reinstalled tipi. All is good again. I can’t begin to remember all the re-formatting, programs and trials I used on the sd to get some program to accept it. When WIN32Imager said it had successfully burned, I was still skeptical, but (fingers crossed),I installed it anyway. Now, to try to remember what I did to resuscitate the other two 64gb sd’s. Thanks to all for your help and advice.

SD CARD FORMATTER successfully completed the re-format back to exfat: File system: exFat 59.45 GB. For the record, I have always used Etcher for image burning, all sd cards were SanDisk, and with sidecar instructions in hand I followed all instructions explicitly. Now Etcher will not burn the Buster image to the re-formatted exFat card. And to complicate matters further, I have never been able to pull up the web-ui. All I get is a...Hmmm...can't reach this page. I always just copied and dropped files from explorer. So, I am going to wait until my 8gb card gets here and use TIPI with the 64gb in the meantime knowing that PDF doesn't work for me. I'm done for a while. "Not following the instructions and advice of the designer is not a supported method and will waste everyone's time." Trust me, it was not my intention to waste anyone's time and I'm sorry if this problem caused you any grief. I was just stating what I experienced and hoped there was a simple solution. My solution will be the smaller sd card.

Now that I think of it, the card I retrieved from the tipi (thinking it was pooched) was a 64gb and I had not reformatted to fat32 first. It ran perfectly with the old image. I was unaware that my pi 3b card was not supposed to exceed a 32gb limit. Now, however, I've got 3 64gb cards with buster 2.28 on re-formatted fat32 cards. I am in the process of attempting to use SD Card Formatter to completely overwrite a card to retry installation. It doesn't tell me what format it is using. I'm hopeful it is exfat. This still doesn't answer the question about Buster 2.28 and a 64gb sd card.

Went to Basic, typed in just like you: 10 PRINT "HELLO", LIST "PI.PIO" and produced another PDF in TIPI. Opened PDF and no joy. It was totally blank like all my other PDFs. It must have something to do with my 64gb card and formatting it to fat32. I had read on the internet that the pi could accept a card larger than 32gb only if formatted to Fat32. Unfortunately, I burned all 3 of the only sd cards I had (all 64gbs) with the image for backups. I may try to reformat to xfat if possible and try again. An 8gb card that I ordered is a week or so away.

Help wanted! Printing Problem. After more than a year of using tipi and printing out PDF’s, I pooched the sd card (maybe I didn’t but I thought I had) so I downloaded the latest 2.28 Buster image GUIFORMATTED a 64gb card to Fat32 and burned it to the card and installed it into the PI of my sidecar TIPI. I went through the installation process and all seemed ok. I can access several writer programs (FW, BA Writer, TI-writer) save and re-load the files but every Print File: PI.PIO has resulted in a blank page in the resulting PDFs. I’m at a loss. Where’d the print go? It used to be like clockwork. I cleaned the cart port and FG99 contacts. Re-booted and tried different programs with the same result. Totally blank PDF’s. Any suggestions???

Thanks all. I found a mix (5- 15’s & 3- 20 nls) in a screeching banshee console. So, I don’t know if the video ever worked okay. I may install a 20nl chip or two into a working console just to see…No I don’t think so.

Any problem with using 4116-15nl chips with 4116-20nl chips in the same console?

Got er done. Thanks. As long as I’ve been using TiDir, I never realized that a right click would bring up a much needed menu.

I have successfully downloaded dsk’s from ftp.whtech.com, extracted the files and transferred them to a nanoPEB using HDXS. That is, as long as filenames do not contain an “@“ or similar character. If they do, transfers stop and I get a file error. Changing filenames or eliminating the offending character(s) on the PC does not work. After changing filenames and entering HDX1. in source, the original file names appear like magic although with regards the “@“, it has been replaced by a forward slash,/. Is there a way around this problem? On another note, the link to download version 2.0 CfHdxS1.-CfHdx serial nanoPEB version on Fred Kaal’s Project Page leads to Not Found in this server.

Ebay has several nx1000 printers listed now that work great with the TI-99/4a. I have used one for years.

Was unable to pull up RXB 2015...message said There was a problem with the preview.

I have a couple of spare Mitsumi keyboards. Although the keys are not black they both a white sticker with Mitsumi on them on a brown back plate. I’d be wary.

I sent Custodio (Jaime) both of my nanoPebs to fix the printing problem, one in late December 2019 and the other in early January 2020. Both have been returned and work perfectly now. Custodio rocks.

I tried using 2 stop bits in Putty to see any changes and got the same output as 1 stop bit. But I did learn one thing. The extraneous characters are not random. I had typed a few lines of 80 columns text and then copied these until I had about 15 lines to print. Every line had an extraneous first character but the same character appeared on every line that contained the exact same text. As I wrote earlier, Custodio Malilong made contact with me. However, most references about fixes in this and other threads mentioned Jaime. Could he be one and the same person? I guess I should ask him. Anyway, Ksarul generously offered to supply an XB 2.7 cartridge to allow testing. I’ll contact Custodio in the next day or two with all the information I have gathered relative to my problem and let him know of the offer of the XB 2.7 cartridge for testing.

Editor Print File Device Name: RS232.BA=1200.DA=8.PA=N (If this setting isn’t correct for STOP BITS = 1, then I don’ t know how to type it in correctly to get it to print anything). Putty Setting: Speed (baud) 1200 Data Bits 8 Stop Bits 1 Parity None Flow Control XON/OFF

Does anyone with a Nanopeb V1 use the editor in TI-Writer found in the Extended Basic V.2.7 Cartridge Suite to print to Putty or another Terminal program on their PC via the serial null modem cable without getting a single random character at the beginning of each line? Here is why I ask. I bought 2 Nanopebs, 1 in in late 2017 and the other in early 2018. It took a long time reading forum threads before I was able to successfully transfer DSKs back and forth from console to PC over a serial null modem cable to USB connection at the PC. Eventually, thanks to guidance from several forum members, I started printing volume catalogs to Putty using DM3 and printing my own catalog of volume files in Excel. Things seemed golden. Flash forward to a couple days ago. I fired up my Extended Basic v2.7 Suite cartridge, chose Writer/Assembler and then text editor. On a whim I decided to see if Nanopeb could print to Putty like a word processor for any text I typed. So I typed an article from a magazine I had been reading, chose PF Print File and set the serial parameters to: rs2232.ba=1200.da=8.pa=n. Then I set Putty to the same configuration and hit enter on the console. Text immediately appeared on my PC in Putty and I thought, “wow, It works.” Well not exactly. You see at the beginning of every line an extraneous random character appeared (e.g. 2HAD…,OGIVES… etc.) A little research in the forum turned up another Nanopeb user in 2017 that had described the same problem. Apparently, back then Jaime Malilong had left out some reference, (which I am not clear on) to SIO or the serial connection in the DSR of one or more of his Nanopeb batches. The user sent back his device. The DSR was updated, Nanopeb returned and the user did not experience any more extraneous characters at the beginning of lines. Here is where it really gets confusing. So, I sent an email to the contact given at www.nanopeb.com. I explained my problem, the identical or nearly identical problem in 2017 fixed by a DSR change and asked how I might get my problem resolved. I received a speedy reply from Custodio Malilong. He said, “I’d be glad to help. I don’t have TI-Writer, but can you tell me where I can get FunnelWeb? I’ll load it up and see if I can solve the issue. I have Putty. Just a follow-up. I’m using the print option on Editor/Assembler and I see a “P” at the beginning of each line. Is this what you are seeing?” He also told me he was using a CF7 to print to his parallel printer. Apples and oranges?. No! my characters are random. And just to muddy the waters further I dug out an Editor/Assembler Cartridge loaded some text and used the print function to print to my TI serial printer. I got text with the same “P” at the beginning of each line as he had. I emailed Custodio and emphasized to him random characters when using TI-Writer/Putty or when using TI-Writer directly to my serial printer. I told him of the consistent “P” when printing out of EA. I also said I was going to take a few days and do further research. Hence, my first line question. I am going to see what other information I can provide him to assist in my problem. I welcome any further guidance I might supply to him.

Today I changed my router’s SSID from one which had a space in the name to one without spaces. I immediately descended into the basement where Tipi is located to see if this change would allow me to connect to the internet. SUCCESS!!! I connected to Heatwave bbs and created an account profile. Now I am in the middle of re-connecting all devices for the 4 users in this multi-generational household. Counting all computers, laptops, Amazon dots, kindles, iPods, iPads, printers, chrome book, ring doorbell, security camera, WIU, PS4, I’m nearing 30 devices (really). A change to the Tipi’s confit might have been easier. Count one damaged pi3 (my mad) also. Now to try and figure out the quickest way to make full use the Tipi, with only console, no F18a.

Received a new pi3 yesterday from Amazon identical to the other except this one was manufactured in China and not the UK. Proceeded to test if Tipi would work. Here's what I did: 1. Re-flashed mini sd with Tipi sdimage 1.41. and inserted into pi3. 2. Cut a small thin piece of plastic from a sandwich bag and inserted it between the (2) 5-pin cables ends that abutted with metal connectors face-to-face at the back end of Tipi. Then correctly oriented and connected the other cable ends to pins 31-40 on Tipi. I hoped this would eliminate any possibility of shorting that I raised. 3. Powered up Tipi and waited for it to boot. 4. Powered up 32k sidecar and monitor and waited for monitor to warm. 5. Turned on console and chose TI Basic. 6.Typed CALL TIPI (enter) 7.Tipi screen appeared in seconds. Yeah!! 8. Typed S (enter) and Tipi screen when to SSID: and waited for input. 9. Typed my SSID and pressed enter. Typed P and entered. 10. Tipi screen went to PSK: and waited for input. 11. Typed my password (upper and lower case as necessary) and entered. 12. Pressed W to write the configuration. I waited but an IP address never showed up. So I quit (Q enter) tried again re-flashing sd card and once or twice more (but not always re-flashing card) even substituting my 1st pi to see if the plastic barrier between cable ends would allow Tipi to get to that first screen. But before I wear out the sd card and my legs (Tipi in basement, re-flashing computer on 1st floor) I thought I would ask for advice. My SSID consists of upper and lower case letters with one space: e.g. Xxxxxx Xxxxx_5G, and my PSK: e.g. XxXxxXxxxxxXxxXxxxxxxxx, 23 characters, upper and lower case letters, the at symbol and several digits. Anything unusual, length? that might be causing a problem? Anything else I might try before I send Tipi off for possible repair?