Jump to content

snume

Members
  • Posts

    91
  • Joined

  • Last visited

Posts posted by snume

  1. 15 hours ago, jedimatt42 said:

    The initial device not found error is not impactful. I should hide that message.. 

     

    FCMENU <menu-file>

     

    What output do you get when you try to run it? What does your menu data file look like? 

     

    If you run ENV, what does your PATH look like? Does it include the directory that has FCMENU in it?  Are you using a full path name to the menu file? Or is it in the current directory?

     

    I wasn't even able to get it started. I think I just jumped in with both feet before fully understanding HOW it worked.

     

    14 hours ago, jedimatt42 said:

    I use an AUTOCMD file in TIPI. 

     

    https://github.com/jedimatt42/fcmd/wiki/Scripting#autocmd---running-a-script-on-startup

     

    With something like this in it to set the PATH:

     

    PATH=TIPI.FC.BIN.;TIPI.BIN.

     

    https://github.com/jedimatt42/fcmd/wiki/Variables#path

     

    If I remember correctly, without a PATH set, executables are only looked for in the current directory.

    Thank you so much Matt for the gentle nudge. Knowing the device error is not something to worry about and using this info has got me rolling. Still kinda bummed I couldn't figure it out on my own.

     

    I've still got a lot to learn and look forward to it but at least I can save myself from spinning my wheels.

     

    Great work on all of this (TiPi, Force Command, FCMENU, etc) by the way.

    • Like 2
  2. So I have had my FinalGROM for a couple weeks and now just got my TiPiPEB and have it set up with s Raspberry Pi Zero 2 W. When I try to run Force Command I get a "device not found" error and I can't run FCMENU. I have read through all the documentation and I  think I have the FC directory in the correct spot but I feel like a total Noob on this and I know I'm missing something so gosh darned obvious it's driving me insane. Any help anyone can provide would be greatly appreciated.

  3. 1 hour ago, acadiel said:

    I’m the only one so far that I’ve heard about where the ELPAC has done that.  At least, nobody else has said so in the forums in the past 10-15 years that I’ve noticed.  About the C64 saver - I don’t know - without looking at how one of those works, I’m unsure if the pinout would protect the correct pins.

     

    The new bricks do work great, though.  I also bought a switch in-line to an IEC cord to turn the power brick off when I’m not using it.

    And yes, it’s going to be fun making a duplicate board and testing it!  I don’t remember if I put the BOM for the upper board here on AtariAge yet, but I do have a copy of it.  I’ll even make a Mouser BOM for the common stuff.  The GALs, 9901, TMS4500, and WD1773 will likely need to be eBay finds.

    Very cool. And the C64 saver has a circuit that cuts off the 9V rail if the power supply fails which usually causes a spike that kills one or two of the main chips, I think the video one which is getting very hard to find a replacement for, unless someone has finally developed a replacement. I was thinking the design would just be modified to work with ELPAC supply, though I do believe it is a 5 pin din as well. It was just a thought. Wasn't very expensive to build one either. 

  4. On 4/2/2022 at 6:34 PM, acadiel said:

    My ELPAC went poof one day - and took out a 9901 in the Corcomp - so that’s why I replaced it.  I’m thinking one of the passives inside decide to take a permanent vacation.

    So, I am one of the unfortunates that will benefit greatly from the board you are developing and it is greatly appreciated. Mine also didn't come with a power supply and I have an ELPAC replacement on the way. Do you think it would be of benefit to install a version of the C64Saver in line with it to prevent a POOF situation? I built one to use with my Commodore 64 as those original power supplies are almost guaranteed to go and kill some of the hard to find chips. 

    • Like 1
  5. 19 hours ago, arcadeshopper said:

    did you design this? is there a stl somewhere?

    I got the original design off thingiverse but it was for a 128x64 OLED whereas I had the .91" 128x32 one so I modified it (poorly I must say) by adjusting the led window/mount, adding 2 holes for the leds and one for the rotary encoder. Here's the link to the original design. Mine is not one worth sharing.

     

    https://www.thingiverse.com/thing:4237727

     

    He really did a bang-up job with his design.

    • Like 1
    • Thanks 3
  6. Yeah, I just couldn't bring myself to pull the trigger on a Lotharek with the exchange and postage but as soon as they released an HXC firmware for the gotek I hooked it up. Found a model and 3D printed a mount that let's me have a 5 1/4, a 3 1/2 and a gotek all in the original opening of the PEB. Loving it. 

    IMG_20210129_154658.jpg

    • Like 10
  7. On 8/30/2020 at 9:47 AM, acadiel said:

    That reminds me that we need to make some new disk controller boards for the Mini PES systems - a lot of them are missing the disk controller boards because they weren’t ordered with them.  

    Yeah, I'm definitely in for a new one for a CC9900 sidecar. Mine never had the disk controller and I was just happy to get one fairly cheaply at all.

    • Like 1
  8. On 2/12/2020 at 2:03 AM, InfernalKeith said:

    I was loading a BASIC program from cassette tonight, but had my PEB with 32K plugged in and turned on as well.  As soon as the initial tone on the cassette ended and the first data was encountered, it kicked back ERROR DETECTED IN DATA and stopped.  I tried it on two different tape decks.

     

    Once I shut off the PEB and unplugged it from my console, restarted in TI BASIC, and typed OLD CS1, that program loaded with no issues at all.

     

    I expected the program not to run, given the small amount of memory the disk system uses up, but for it to not even load the program in?

     

    Is that just a weird quirk, or some normal procedure I've just never seen happen before?

     

    On 2/12/2020 at 3:56 AM, blackbox said:

    Memory limitations can hit in two places when loading from tape- the tape file may be bigger than the VDP memory you have  when the disk controller is attached - your problem here I think.  With a disk system attached you lose some VDP memory for disk buffers. You may not have enough vdp to hold the cassette file.
    Then when you RUN a program, and prescan takes place, arrays dimensioned, and so on, more memory is required which can result in a run time error.
    Although you may have 32k ram attached, the tape is always first loaded into VDP memory but may then run from 32k ram.
    With the PEB attached  you can free up memory with CALL FILES(1) then NEW. This reduces the VDP memory used by disk buffers and also limits you to one disk file open at a time.  Some XB versions permit CALL FILES(0) or there is a CALL LOAD available.
    s

     

    Well after another hiatus, a new wave of nostalgia has hit and I fired up the 99/4A, the CF7+ and the cassette drive to transfer some of the tapes I got in a batch of stuff a few years ago and Iran into the same issue as Keith. And the CALL FILES(1) and NEW - in TI Basic did the trick. Anything over 23 or so blocks wouldn't fit. The work around wouldn't work in Extended Basic either, just TI Basic.

     

    Well it only took me a couple of hours plugging and unplugging, running around until I found this thread and I want to say a huge thanks to you Black Box.

    • Like 2
  9. Can add my appreciation to the list as well. Cartridges and controller were VERY well packed and stuff was here very quickly. Highly recommended and will do business with again.

  10. Alright I have made the plunge.

     

    All of you who are hemming and hawing over whether to go for it or not just buck up and send Rey the funds so he can get these babies rolling. I know not a single one of use will fail to be satisfied.

     

    Rock on Rey.

     

    Steve

    • Like 2
  11. Well I initially formatted my 1TB WD My Passport with 32K allocation sectors and I noticed some significant slowdown in loading and occasionally in the first few games I tested but I re-formatted it with 64K and I only noticed a tiny bit of slowdown in opening cinematics in the same games I tested but the games play fine. I love this thing. Does it have an easy way to get to the menu where I can check what's on my VMU's? So far I've had a second DC hooked up to do it but I also discovered if I try to load a game that won't work with VGA it defaults back to the DC menu (the DC I am installing this on is modded for VGA).

     

    I was also wondering what format of ISO will work with this device? I had a Nero disk image and it wouldn't work. Just wondering.

  12. Sorry if this is not the right place but I couldn't think of anywhere better to post this.

     

    I've finally got the all clear from Texas Instruments to publish my Parsec WP8 remake (first mentioned here) and now looking for a few brave beta testers. If you have a Windows Phone 8 device, a Microsoft mail account and want to try it out then please drop me a PM with your e-mail. I'll send instructions on where to download the beta in a few days.

    I am in. I have a Samsung Ativ and spent many hours playing Parsec on the TI back in my youth

×
×
  • Create New...