Jump to content

GreyHobbit

Members
  • Posts

    78
  • Joined

  • Last visited

Everything posted by GreyHobbit

  1. I went back to check and can hardly get it to fail now! I have the Sophia2 output going through a DVI to HDMI cable through an HDMI splitter and it only failed when the PC was also sending a signal to the HDMI splitter. But there was no sign of the usual boot sounds from the XL, it just freezes on the blank screen until Reset is pressed. With the PC off (or suspended) the Atari seemed to work every time. I did see it fail with the PBI HDD both enabled and disabled, but I'll try again tomorrow and see if I can see a pattern. I should have said up front, the new firmware is amazing, I've especially been enjoying the ability to tweak the Sophia2 settings. Thanks for all the hard work you've put in. Sent from my AC2003 using Tapatalk
  2. Thanks for the quick and helpful replies @flashjazzcat and @DrVenkman. I left the 800XL powered on for a while as I was distracted by something shiny elsewhere, and just power-cycled it a few minutes ago only to see it work perfectly a few times and fail on others. I assume this is going to be one of those intermittent things that depends on the alignment of the stars, but I'll keep an eye on it over the next few days and see if it reoccurs. I think I should have a spare 6502C I can try swapping in, not sure about the 74F08, but I'll track one down if necessary I am sure. I'll search for the fix by @tf_hh, hopefully I have a few capacitors that will match what's needed for that if I have to go there. As I said, it was happening with or without the Side3, but seems sporadic.
  3. I've flashed the U1MBS3.ROM and SOS3P2.ROM plugin so I have control of my Sophia2 on my 800XL, and flashed the new S3 Loader and SDX image to my Side3 cart. When I power the 800XL up, I just get a black screen until I press System Reset, then the U1MB splash screen is displayed and the computer boots into SDX. Everything seems perfectly ok apart from the power on black screen issue. It happens with or without the Side3 cart plugged in and with or without my FujiNet plugged in. Has anyone else seen something like this? Geoff
  4. I uploaded the Atari 400/800 dump to the A8 Preservation site a few months back, I've had the cassette since the early 80s. There was already a version for the XL/XE OS and I was sent a copy of that dump. I'll attach them here, but if there's a reason I shouldn't be sharing the XL version that was sent to me, let me know and I'll remove this post. The manual is available here https://archive.org/details/ACE_Atari_Cassette_Enhancer_manual Geoff A.C.E. - The Atari Cassette Enhancer (1983)(English Software Company)(GB)[!][BASIC].cas A.C.E. The Atari Cassette Enhancer (1983)(English Software)(GB)[ver2.0][OSB][Load with BASIC].cas
  5. If a UK-based seller is handier for you, you can get the AVG Cart from retrolemon.co.uk. I bought one from them a couple of weeks ago. They also sell the SIO cable to let you plug it into the SIO socket for ATR support if you ever wanted to do that. I think there's an EU supplier as well. Sent from my AC2003 using Tapatalk
  6. The full A.C.E. manual is at the Internet Archive... I mean, of course it is, where else would it be? I can't believe I didn't look there before now! https://archive.org/details/ACE_Atari_Cassette_Enhancer_manual Geoff Sent from my AC2003 using Tapatalk
  7. Must be lots of changes, hopefully for the better! Definitely worth a visit. You take care too Paul Sent from my AC2003 using Tapatalk
  8. I'm originally from a few miles east of Armagh, my wife grew up in Ravenhill area and we now live just off the Castlereagh Road in the east of the city. Only been here 9 years so I'm still a 'blow-in' Geoff Sent from my AC2003 using Tapatalk
  9. The manual on the preservation page is actually the cassette inlay from my tape version. I remember having a printed 'manual' that was a couple of A4 pages stapled into the form of an A5 booklet that explained the commands that were available. Unfortunately I haven't seen it in years, it might be in a box in the attic but it's probably lost Sent from my AC2003 using Tapatalk
  10. I uploaded a dump to the A8 Preservation site a few weeks ago. They already had an XL version, my cassette was an earlier 400/800 version. http://www.a8preservation.com/#/software/title/1492 Sent from my AC2003 using Tapatalk
  11. I think the editor didn't like my last message! I was trying to say I missed one of the argc loop typos in NREN.COM. I submitted a new pull request. Geoff Sent from my AC2003 using Tapatalk
  12. @tschak909 I just noticed that I missed one of the 'i<=argc' typos in NREN.COM. I have submitted another pull request. I think I got the hang of it this time Geoff
  13. That was my first submission to an open source project. I'm used to owning the repo in work! I'll get better at it... [emoji16] Sent from my AC2003 using Tapatalk
  14. Sorry for submitting those pull requests one file at a time, I couldn't get my IDE to push them all to a new branch in one go!
  15. Thanks Thom I had a look at the code and the main.c source for fls, fnet, ndel, ndir, nmkdir, nren & nrmdir all have a loop for (i=1;i<=argc;i++) which should be for (i=1;i<argc;i++) This tries to process an extra parameter that causes corruption at the end of the argument string being stored in buf[]. What is the proper way to submit code changes to the project? Do I commit them to a new branch and push that to the github repo, then raise a pull request to get it approved? Geoff
  16. I'm in the UK and received #143 about a week ago. #141 arrived today with my membership card. I got #142/#52 last October/November, I think. Thanks Sascha.
  17. Which reset button should we use on the FujiNet during these operations? The right-hand button, or a long-press on button B? I saw an earlier post saying the right-hand button was a hard reset of the ESP32 and might cause problems, is that still the case? Thanks Geoff
  18. I'm having an interesting time experimenting with the F*.COM tools in SDX. I've spotted what appears to be a symptom of the issue with FLS.COM when viewing the contents of subdirectories, as mentioned by @MrFSL. If I run FLS 1 I get the top-level directory listing from my SD card, but FLS 1,ROMS gives an SIO ERROR instead of the list of files in the ROMS directory. Looking at the serial output, the subdirectory name in the FLS command has an 0x01 character appended. [20:30:49]CF: 70 f7 00 00 68 [20:30:49]sioFuji::sio_process() called [20:30:49]ACK! [20:30:49]Fuji cmd: OPEN DIRECTORY [20:30:49]<-SIO read 256 bytes [20:30:49]ACK! [20:30:49]Opening directory: "ROMS", pattern: "" [20:30:49]::dir_open {0:1} "ROMS", pattern "" [20:30:49]::dir_open actual path = "ROMS" [20:30:49]ERROR! [20:30:49] [20:30:49]CF: 70 f7 00 00 68 [20:30:49]sioFuji::sio_process() called [20:30:49]ACK! [20:30:49]Fuji cmd: OPEN DIRECTORY [20:30:49]<-SIO read 256 bytes [20:30:49]ACK! [20:30:49]Opening directory: "ROMS", pattern: "" [20:30:49]::dir_open {0:1} "ROMS", pattern "" [20:30:49]::dir_open actual path = "ROMS" [20:30:49]ERROR! If I append a ctrl-A character right at the end of the ROMS subdirectory name in the FLS command, I get a subdirectory listing and no error. But there are now obviously two control characters appended to the ROMS directory name. [20:31:10]CF: 70 f7 00 00 68 [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: OPEN DIRECTORY [20:31:10]<-SIO read 256 bytes [20:31:10]ACK! [20:31:10]Opening directory: "ROMS", pattern: "" [20:31:10]::dir_open {0:1} "ROMS", pattern "" [20:31:10]::dir_open actual path = "ROMS" [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 f6 24 00 8b [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36) [20:31:10]::dir_nextfile {0:1} [20:31:10]::read_direntry "Action! (1983)(ACS).car" [20:31:10]->SIO write 36 bytes [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 f6 24 00 8b [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36) [20:31:10]::dir_nextfile {0:1} [20:31:10]::read_direntry "Atari LOGO (1983)(Atari).car" [20:31:10]->SIO write 36 bytes [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 f6 24 00 8b [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36) [20:31:10]::dir_nextfile {0:1} [20:31:10]::read_direntry "Basic XE v4.1 (1985)(OSS)(US).car" [20:31:10]->SIO write 36 bytes [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 f6 24 00 8b [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36) [20:31:10]::dir_nextfile {0:1} [20:31:10]::read_direntry "Basic XL v1.03 (1983)(OSS)(US).car" [20:31:10]->SIO write 36 bytes [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 f6 24 00 8b [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36) [20:31:10]::dir_nextfile {0:1} [20:31:10]::read_direntry "Homebase (1982)(Citibank)(US).car" [20:31:10]->SIO write 36 bytes [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 f6 24 00 8b [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36) [20:31:10]::dir_nextfile {0:1} [20:31:10]::read_direntry "MAC-65 v1.01 (1984)(OSS)(US).car" [20:31:10]->SIO write 36 bytes [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 f6 24 00 8b [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36) [20:31:10]::dir_nextfile {0:1} [20:31:10]::read_direntry "OSS Cart Bundle &amp; SDX AtariMax.rom" [20:31:10]->SIO write 36 bytes [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 e4 06 00 5b [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: SET DIRECTORY POSITION [20:31:10]::dir_seek {0:1} 6 [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 f6 80 00 e7 [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=128) [20:31:10]::dir_nextfile {0:1} [20:31:10]::read_direntry "OSS Cart Bundle &amp; SDX AtariMax.rom" [20:31:10]->SIO write 128 bytes [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 f6 24 00 8b [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36) [20:31:10]::dir_nextfile {0:1} [20:31:10]::read_direntry "PILOT (1981)(Atari)(US).car" [20:31:10]->SIO write 36 bytes [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 f6 24 00 8b [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36) [20:31:10]::dir_nextfile {0:1} [20:31:10]Reached end of of directory [20:31:10]->SIO write 36 bytes [20:31:10]COMPLETE! [20:31:10] [20:31:10]CF: 70 f5 00 00 66 [20:31:10]sioFuji::sio_process() called [20:31:10]ACK! [20:31:10]Fuji cmd: CLOSE DIRECTORY [20:31:10]COMPLETE! I also tried appending a ctrl-A and ctrl-B to the subdirectory name in the FLS command and still get a successful directory listing. In fact, FLS 1,ROMS <followed by all 26 ctrl-A to ctrl-Z characters> still results in a successful listing of the ROMS subdirectory. [20:48:52] [20:48:52]CF: 70 f7 00 00 68 [20:48:52]sioFuji::sio_process() called [20:48:52]ACK! [20:48:52]Fuji cmd: OPEN DIRECTORY [20:48:52]<-SIO read 256 bytes [20:48:52]ACK! [20:48:52]Opening directory: "ROMS [20:48:52]", pattern: "" [20:48:52]::dir_open {0:1} "ROMS [20:48:52]", pattern "" [20:48:52]::dir_open actual path = "ROMS [20:48:52]" [20:48:52]COMPLETE! [20:48:52] [20:48:52]CF: 70 f6 24 00 8b [20:48:52]sioFuji::sio_process() called [20:48:52]ACK! [20:48:52]Fuji cmd: READ DIRECTORY ENTRY (max=36) [20:48:52]::dir_nextfile {0:1} [20:48:52]::read_direntry "Action! (1983)(ACS).car" [20:48:52]->SIO write 36 bytes [20:48:52]COMPLETE! [20:48:52] [20:48:52]CF: 70 f6 24 00 8b [20:48:52]sioFuji::sio_process() called [20:48:52]ACK! [20:48:52]Fuji cmd: READ DIRECTORY ENTRY (max=36) [20:48:52]::dir_nextfile {0:1} [20:48:52]::read_direntry "Atari LOGO (1983)(Atari).car" [20:48:52]->SIO write 36 bytes [20:48:52]COMPLETE! <etc> Also, I have just noticed that running the command as FLS 1,ROMS/ appears to result in future FLS calls giving a 138 error until an FMALL is called to remount the drives. Geoff Edit: Annoyingly, all the ctrl-characters that were in the code snippets seem to have been purged when I submitted the message. But they are clearly visible in the serial out log in the flasher utility. Now it looks like I've just pasted lots of ordinary looking log output just for the sake of it!
  19. I've sent you a PM with the link, let me know if there are any problems. Geoff
  20. I have a copy of Thorn EMI Super Cubes and Tilt on cassette that is listed on the A8SP site as having no media dumps. I have zipped up the .wav and .cas files for both sides of the cassette, scans of the box (front and back) and the manual, but I don't know where to submit it. Is it ok to upload the 50MB zip file to this topic or is there somewhere to send submissions to? Thanks Geoff
  21. Thanks for responding, I will send you a reminder later in September. Enjoy your vacations.
  22. I'm trying to resurrect some almost 30-year-old Action! code I was last working on around 1991, and I'm running Action! from my SIDE2 cart with @ebiguy's OSS cart images in @flashjazzcat's firmware. To compile my source code, I first need to run the BIGST.ACT program from the Runtime disk to increase the symbol table size. Unfortunately the BIGST.ACT program must rely on the banking scheme in the original Action! cart to reset the system and it locks up the computer when I run it. BIGST.ACT writes a zero byte to $D503 and calls a coldstart routine at $A326 to reboot the cartridge. Has anyone had any success creating the big symbol table using the SIDE2 Action! implementation, or knows what bank address should be used in place of $D503 to reboot the Action! cart? Some of the previous posts about the SIDE OSS cart implementation mentioned the bank layout having to be changed. Thanks Geoff For context, the source code for BIGST.ACT is: ; BIGST.ACT ; copyright (c) 1984 ; by Action Computer Services ; All Rights Reserved ; This program will create a big ; global symbol table (max 510 ; entries, normally 255) when run. ; It will boot the cartridge as well, ; so you must not have anything in ; the Editor that you want. It does ; not increase the space used to ; store variable names. If you want ; to increase this as well, you will ; have to 'SET $495 = #' in the ; monitor after running this program. ; # is the number of pages you want ; to be used for name storage (each ; page is 256 bytes, default is 8). ; You must use the correct version of ; Cold below: ; version 3.0 ACTION! ROM ;PROC Cold=$A323()[] ; version s 3.1 to 3.6 ACTION! ROMs PROC Cold=$A326()[] PROC BigSymbolTable() CHAR bigST=$4C4 BYTE EBank=$D503 Zero($480, 255) ; following statement causes all ; variables starting with uppercase ; letters to go into one half of the ; global symbol table and variables ; starting with lowercase letters to ; go into other half (255 entries in ; each half). If you use mostly ; uppercase variable (this includes ; PROC/FUNC names) use 'M. If you ; use mostly lowercase variables then ; use 'm. bigST = 'M ; boot cartridge with big S.T. ; Will not return. EBank = 0 Cold() RETURN
  23. Hi, I'm interested in purchasing at least 1, possibly 2. Geoff
  24. Just missing those two vital GPIOs. Thanks for checking. It is tiny though, it looks like it's not far off being able to fit into an SIO plug!
×
×
  • Create New...