Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

129 Excellent

About Kchula-Rrit

  • Rank
    Chopper Commander

Recent Profile Visitors

323 profile views
  1. The image I am using is of a 128MB CF, it is 63MB in size. Sector 63FF9C1 is 104,856,001 decimal. Dividing by 1600 sectors per disk-image gives a disk-image number of 65,535. Looks like I'm trying to access something that is not there, or my CF board is bad, or maybe the board exceeds the NanoPEB's capacity. Oops. More info: When I back-up the CF board using, TI99Dir v8.2a-20210101, the sector-count is 250368, which gives 156 images of 1600 sectors each. This is what I remember when using CF2K to mount and format images. Have to look through my code a bit more closely to see where it may be going awry. Forgot to mention that, so far as I know, I'm only Level 3 file I/O. I open a text file and read it, then call TI's LOADER routine. K-R.
  2. I was just going on my experience with TI994w, where both FIAD and CF7 worked. Silly assumption on my part. K-R.
  3. I thought it was strange (actually shocking), too. It's been many years since the incident, so I do not remember the details. Not even sure which vendor, or where they were. I'm thinking British Columbia but the memory is so hazy. Just remember it seemed excessive. I really needed the parts and could not find them anywhere else. Also, I agree with you and TI99ER about not making the board open-source. You put a lot of work into that board and it would be seriously wrong for someone else to grab it for profit. K-R.
  4. It assembles and runs in Classic99 using TI (FIAD) disk emulation. Haven't tried CF7+ yet, but I bet it will work. I'm trying some creative things to minimize Low RAM usage, which may be stepping on some addresses the NanoPEB uses. The screen prompts are at the start of the program. They get copied to the upper end of VDP RAM, then the Low RAM that the prompts use gets freed (LSTLOW gets set to just below the first instruction). I'm also working with the PABs directly in VDP RAM to read the batch file and call LOADER. Of course, I update >8370 when I grab VDP RAM and restore the original value when I exit. I haven't done these kinds of things before, so I might be trying to get too "fancy" all at once. K-R.
  5. I have a tower case from a deceased PC that is just begging for that board! Cannot say I've ever seen a 9958 VDP; I take it the RGB output is not composite? Looks like no sidecar port, so I guess I'd have to replace my NanoPEB with an IDE controller. Shudder to think what import duty from France to US would be, though. Some parts I ordered from Canada a few years ago had a >100% duty added at the border. K-R.
  6. Update: My loader runs in TI994w, with FIAD or CF7 emulation. It still fails (hangs) in my real TI, so now I get to figure out what I am doing wrong. K-R.
  7. I'm doing disk-reads through Level-3 DSR calls, plus calling TI's LOADER program in low RAM. All my screen messages and user prompts are stored in VDP RAM, to save space in CPU RAM. I set the VDP free-space pointer at 0x8370 appropriately when loading, then restore it upon exit. I don't think that should matter. I tried v5.4c this morning and my loader did not hang, and the test file ran without problem, using FIADs. After switching to a CF7 image of my NanoPEB compact flash, my loader and the test file ran successfully. It occurred to me that I had not turned off FIAD (top entry on the DSR menu) to use the CF7. When I did so, the debug window halted with the line Cf7a+Features : Value = 0x81 Status=0x00 : Ok Cf7a+ReadSector : Sector=0x00000000 Status=0x00 : Ok Cf7a+WriteSector : Sector=0x00000000 Status=0x00 : Ok Cf7a+ReadSector : Sector=0x063FF9C1 Status=0x04 : Sectornumber to big I turned off the TI disk controller (CRU addr 0x1100) and go the same message. When I turned on FIAD, everything worked, with or without the TI disk controller. Looks like the CF7 needs the FIAD to work. K-R.
  8. Forgot to say, I'm using v5.4b in a Win98 system. I already have 5.4c downloaded, but have not loaded it yet. K-R.
  9. Anyone know how "faithful" the NanoPEB emulation in TI994w is? Or, would a better question be, how close is the CF7+ emulation to the NanoPEB? I've been working on a new version of my batch loader, using TI994w to debug it while my TI has been in pieces. After getting the TI back together, the loader hung when I tried running it. The loader ran under TI994w without problems. My TI994w configuration uses FIADs, where the files are in DSK1-3 directories in TI-FILES format. Then I switched the configuration to use a CF7 image, and used TI99-Dir to make an image of the Compact Flash board in my NanoPEB. The batch loader appeared to hang, but when i showed the CPU window I could see that the program appeared to be stuck in a loop in the >4XXX range, presumably in the emulated disk DSR. K-R.
  10. That is so cool! Are you going to offer these for sale? That would be so neat to get one! I have a motherboard, that died from a previous attempt at modification, that I would like to resuscitate. 32K on the 16-bit bus is something I would love to have. I assume the video output is composite. Is the output improved over an original? K-R.
  11. Ksarul, what's a saddle connector? I cannot say I've heard of one. Sounds like you were talking about the female side, like on the Nano or the fire hose. I was talking about the contacts on the console edge connector being worn down from being plugged and unplugged. After all, they are just very wide/thick traces on the motherboard. K-R.
  12. My Nano's edge connector appears to have some shave/sanding marks that would indicate it was cut down from a larger one. I think ISA (PC/AT style) boards had two connectors. I just wonder about the reliability of the forty-year-old edge connectors on our consoles. I was toying with the idea of soldering a wire-wrap pin-header to the console edge connector to make a more secure connection, like on IDE disk drives and some floppy disk drives. Don't want to do anything irreversible, though. K-R.
  13. Sounds like the Nano is rather touchy about power, given Schmitzi's experiences. I suppose it doesn't help the CF board contacts that I have to remove the CF to plug it in to my PC to transfer files. After I adapted my console to run on batteries (see the BATcomputer article in the main forum) I put the Nano's brick "away", which means I cannot locate it. I found one from a dead router, +5V, 2.5A, to power the Nano, and it worked okay. The +5V supply noise at the Nano's power plug was about 100mV p-p using the brick, similar to the noise when I used the battery supply I had built. While I'm beefing-up the power cable I'll add a 470uF cap to add some more filtering. My original battery set-up assumed that the console has lots of filter/bypass caps. I know about "assume", and I took a short cut... At the title screen it says NANOPEB-SIO V1, and the label on the EPROM says V.1. Thanks, K-R.
  14. My response is a bit late, but that makes sense. I'd wondered about the read-before-write. Thanks, K-R.
  15. Another one of my pesky questions-- My NanoPEB lately seems a bit "iffy," giving "DSR error 6" upon loading the second file of large programs like CF2K, or just locking up. My thoughts are: The NanoPEB is touchy about its supply voltage. My set-up has the console and NanoPEB running from the same supply, a battery supplied DC-DC converter. There was lots of power-line noise before I added filters. The voltage at the "navel" power connector is 4.84V. Haven't checked noise levels. The EPROM in the NanoPEB is losing its data. I remember, in the 1980s, hearing of EPROMs being erased by sunlight from friends who had their home-made systems near outside windows. My system sits near a window and I wonder if the label on the EPROM is letting some UV from outside to get in, which could slowly erase the DSR. I need to beef-up the power wiring from the supply to the console/NanoPEB. I originally used 22 gauge wire in the power supply; the charts I read said it should handle three amps, which I figured was enough for the system. The supply-to-console power cable is doubled-up because it is about three feet long. The NanoPEB edge connector is touchy. After I re-seated the NanoPEB I was able to run CF2K without failure, but I'm not sure I trust it. I've had to re-seat the edge connector before. I wonder if I replaced the edge connector with something like the header connectors on IDE drives, or that Arduinos use, if it might not be more "stable" for the long term. Ideas? K-R.
  • Create New...