+Atari2600PAL Posted May 16 Share Posted May 16 If this is the wrong thread for this query, my apologies and mods please delete I've copied the force command bin files to my fg99 and the FC folder to my tipi (via the tipi web interface) but have a few issues If I choose the auto version it just cycles me back to the 99 start up menu If I choose the force version I can do things like DIR ok though But if I try fg99 ALPINER (for instance) the screen changes colour and the 99 hangs Likewise if I try something like load TIPI.FC.BIN.TELNET it just hangs EDIT: sorry, load telnet (or anything else in the bin folder) just causes the 99 to return to the start screen (I should say my 99 currently boots to the CC9900 start up screen, in case that could be an issue) Am I just being stupid please? Many thanks Quote Link to comment Share on other sites More sharing options...
+Atari2600PAL Posted May 16 Share Posted May 16 The fg99 problem was because I was using the cart name as it appears in the menu, when fg99 actually wants the filename on the SD (so BIGFOOT should have been bigfootG). Maybe time to rename the files on my SD. But I do notice it takes me back to the start screen and I have to select the cart from the cc9900 menu, so am wondering if this is also why the AUTOCMD just seems to loop around Maybe this will all be resolved once I change the EPROMS on the CC9900 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted May 16 Author Share Posted May 16 I've used this with a Corcomp floppy controller, but not with the Corcomp eproms... The 'auto' cartridge menu item run the GROM powerup routine to launch into the cartridge rom. Sounds like there are some conflicts with the Corcomp powerup routine and my cartridge powerup routine. ForceCommand is fully functional without the GROM, as it only provides that powerup routine to auto-run the cartridge ROM. Be careful renaming binaries on the FinalGROM99 SD card. The filename is used to determine the emulation type for the file. Instead of renaming my files, I create list scripts in a directory on my PATH that I can run to go to the desired cartridge. Then I can name the script whatever makes more sense to me. The other thing, the binaries in TIPI.FC.BIN. are ForceCommand executables. The LOAD command is for EA5 PROGRAMS. To run a ForceCommand executable or script, Just enter the filename, or directory and filename if it isn't on your path or in the current directory. 1 Quote Link to comment Share on other sites More sharing options...
+Atari2600PAL Posted May 17 Share Posted May 17 7 hours ago, jedimatt42 said: I've used this with a Corcomp floppy controller, but not with the Corcomp eproms... The 'auto' cartridge menu item run the GROM powerup routine to launch into the cartridge rom. Sounds like there are some conflicts with the Corcomp powerup routine and my cartridge powerup routine. ForceCommand is fully functional without the GROM, as it only provides that powerup routine to auto-run the cartridge ROM. Be careful renaming binaries on the FinalGROM99 SD card. The filename is used to determine the emulation type for the file. Instead of renaming my files, I create list scripts in a directory on my PATH that I can run to go to the desired cartridge. Then I can name the script whatever makes more sense to me. The other thing, the binaries in TIPI.FC.BIN. are ForceCommand executables. The LOAD command is for EA5 PROGRAMS. To run a ForceCommand executable or script, Just enter the filename, or directory and filename if it isn't on your path or in the current directory. Many thanks for the info & advice. Will give it all a try thanks Quote Link to comment Share on other sites More sharing options...
+Atari2600PAL Posted May 17 Share Posted May 17 I decided to create an AUTOCMD which just contains PATH=TIPI.FC.BIN. When I load Force cmd it's running the script as it's setting my path as specified (can see it with env) and I can simply type TELNET (or whatever) and it runs ok However, since making the AUTOCMD it gives me a continuous beep on startup until I issue a tipibeeps command which then stops the noise Would this just be because I created the file using echo PATH=TIPI.FC.BIN. > AUTOCMD from terminal on my Macbook please? (I don't have an editor on the 99 yet) Many Thanks Quote Link to comment Share on other sites More sharing options...
+Atari2600PAL Posted May 17 Share Posted May 17 Managed to use the Editor/Assembler editor (using fg99, and creating floppy disk part A via force command) and that has resolved the beeping issue Thanks Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted May 17 Author Share Posted May 17 (edited) The beep is a bug. I thought I fixed a while ago, but I guess I missed something. Placing tipibeeps in the AUTOCMD script likely works around the issue. I'll have to reinvestgate. There is an editor built into ForceCommand, try 'help ed' and from within ED, try FCTN-7 (AID) Apparently I forgot to add ED to the wiki documentation. Oops. (update: added ED to wiki: https://github.com/jedimatt42/fcmd/wiki/Commands#editor) Edited May 18 by jedimatt42 added ed docs to ForceCommand wiki Quote Link to comment Share on other sites More sharing options...
+Atari2600PAL Posted May 17 Share Posted May 17 5 minutes ago, jedimatt42 said: The beep is a bug. I thought I fixed a while ago, but I guess I missed something. Placing tipibeeps in the AUTOCMD script likely works around the issue. I'll have to reinvestgate. There is an editor built into ForceCommand, try 'help ed' and from within ED, try FCTN-7 (AID) Apparently I forgot to add ED to the wiki documentation. Oops. Many Thanks, that's a lot easier Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
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.