Jump to content

a8isa1

Members
  • Content Count

    1,844
  • Joined

  • Last visited

Everything posted by a8isa1

  1. sorry, unable to build the fujinet_flasher on this old system. I update the firmware with esptool.py. -SteveS
  2. I can no longer boot XEX files after this update. -SteveS
  3. [EDIT] I was typing this before I retested. Sorry, for the initial contradictory statements. [Correction] Also sounds similar to when my cell phone is within 1 foot of my A8 speakers. Record-2.wav For my sound it does not matter whether my Atari or the #FujiNet are powered. Only the speakers need be powered. The speakers don't need to be connected to anything. This is a sound I have had for years, across ownership of 3 cell phones. -SteveS
  4. Are you pressing START at the Bosconian screen and again at the "GAMER" screen? -SteveS
  5. The 128K version loads OK here with NTSC 800XL, Rambo XL, Fujinet (Feb 6, 2021 firmware) 64K version at that post is PAL-only so I can't use it. Did you remember to disable BASIC? -SteveS
  6. 17 year, 6 month, 15-day necrobump? Nice! -SteveS P.S. I guess that would be 14 days.
  7. Coincidentally, Yesterday I tried Telelink with Fujnet. I hadn't used that cartridge in 40 years and I was feeling nostalgic. I saw "RS232 ERROR: 130" and no typed characters. I tried this with zero device slots mapped on fujinet to mimic how I used Telelink which was with an just 850 and a Novation D-CAT modem. I next tried a disk image with an 850 boostrap file. This got me into the Telelink program but acting only as a terminal with local echo enabled. I think the driver is downloading. However, within the Telelink program there wasn't a response from Fujinet's modem emulation. -SteveS
  8. Back in business! Thanks! Never would have tracked down that offset for SPIFFS on my own. Regards, -SteveS
  9. I don't have the ability to run the Fujinet-Flasher. Laptop is crippled so I'm running live with RAM file system and I don't have the necessary resources. This is also why I am using ESPTOOL.PY. Where does SPIFFS.BIN belong? What offset? -SteveS
  10. Unable to build Fujinet-Flasher I had been using manual flashing with esptool.py using the following command line which had been provided to me: python esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 460800 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x1000 bootloader.bin 0x8000 partitions.bin 0xe000 boot_app0.bin 0x10000 firmware.bin With firmware for 2/4/2021 I thought I had a success but discovered the new "COPY" feature was not available. I confirmed from the web interface that an update to the firmware had been completed. Looking at the command I realized the spiffs.bin wasn't being updated. I tried to add it. not knowing where it belonged I tried adding to the end. Had insufficient twice. One time this didn't happen but neither was the COPY function available. After a few more attempts something seriously went wrong. After flashing the 3 LEDs blinked for 1 second then my #FujiNet went dark. I tried the update as done above. Still dark.I I tried to restore the original firmware with which my #FujiNet had been supplied. Restore was from a backup which I had made first thing. Still dark I feel as though I have wiped SPIFFS and just don't know where it belong but perhaps I have done worse. Is my error recoverable from here. I mean my location? Did I brick my #FujiNet? -SteveS
  11. Didn't know where to post this. This thread seems to be the catch-all. To my surprise my new TBA #FujiNet 1.0 is perfectly happy with my SWP ATR8000. I mean seemless cooperation of the two devices. Either can act as D1:. Although the ATR8000 is strictly a 1X SIO device neither it nor the #FujiNet get confused while the #FujiNet is running divisor 0, via Hias Reichl's patched (in RAM) OS or his MyPicoDOS. P: device acts as expected. I get an error 140 if using LPRINT while #FujiNet is set as default. If I set it to use P2:, thus both P: devices have unique IDs, then I don't get an error. LPRINT output would be going to ATR8000's printer spooler and no error generated. Opening a channel to P2: works great and #FujiNet's logical printer gets any ouput. No problems accessing #FujiNet's R: device. I did not attempt to use the ATR8000's R:. I don't have a modem or cable for its RS232 port. I did have one issue with my #FujiNet. Most of my SIO cables will not stay attached to my TBA #FujiNET but I found two that have no problem at all. The usable cables have the connector shown below. (Sorry but I always have been a terrible photographer). I'm very happy with #FujiNet. Congratulations to Thom, Mozzwald and everyone else involved in the project, and to the community for supporting the project so enthusiastically. -SteveS
  12. [NTSC] -SteveS [EDIT] 40 Colors a8isa1_horses1.xex
  13. I hope ebiguy can provide a fix for you, Stuart. In the meantime try typing RAMDISK.SYS to start it manually. -SteveS
  14. Gouldian Finch [NTSC - 78 colors] -SteveS a8isa1_gouldian_finch.xex
  15. You hear the drive home and then advance one track. Drive select light won't go out. -SteveS
  16. My first attempt at making a bootable double sided disk went well. I just sector copied my image to a formatted floppy, ran CPMBOOT. Disk worked great. All the files were acessible. I didn't need to start with a bulk erased disk or a flippy disk. The ATR8000 always wants to see a valid disk when first powered but other than that no tricks or hoops to jump through. The next attempts did not go well. For the next two I get only as far as the "C" being echoed in Atrmon. On the third attempt I got to the CP/M splash but then greeted with sector errors. I cannot proceed past that point. I decided to redo CPMBOOT on the very same disk just above. I got a different result. At first It looked the same but this time after responding ENTER to the sector errors the directory listing appeared and the A> prompt came up. Further, I could access every program on the disk. Some worked without any problems. Some worked but I would get 2 sector errors again before return to the A> prompt. XSUB didn't work at all. Sector errors and it kicked me to the A> prompt. I should mention that all the above attempts were done after error free formatting and sector copying. The difficulties occur only when I try to start CP/M. Anyway, I'll leave the ATR. Perhaps someone else would like to try to generate a working double sided disk. I'm also enclosing an image of what I saw in my last go. (Sorry about the image quality. LCD doesn't work well at all with my scan converter and I still haven't repaired/replaced my svideo cable. Software 80 columns, 'nuff said). -SteveS a8isa1_cpm_files_raw.atr
  17. Necessity had me make a few back in the day. It was convienient to have ATRMON on one side of a disk and CP/M on the other side, because I could not seem to keep both disks together! My problem is nearly all of my disks have been reused time and time again. Had a box (of 5) new old stock manufactured *flippy disks* but the one I used Yesterday is the only one I could find. -SteveS
  18. I wasn't asking if I could copy a system disk to an image. I was asking if [EDIT] an image of the newly created double-sided disk of files can be used along with CPMBOOT to make a new bootable disk. There is no need to answer my earlier question. It worked! -SteveS
  19. Question: Will your CPMBOOT then work on a new disk created from my new ATR? ATR could be a while in coming. First attempt generated sector error(s) on the copy. CP/M DDINIT formatted without bad sectors being detected. -SteveS
  20. Jeff, not since I acquired the ATR8000 in 1983 do I recall trashing a disk by cycling the power of the ATR8000. I often cycle the power to register a disk. Oddly RESET on the ATR8000 [edit] doesn't always do it.. I have occassionally trashed a disk by cycling the power on the disk enclosure with a disk still in the drive. Even that is a rare happening. But ATR8000s are tempermental. Sometimes they just don't want to format in the density I want. This is especially true if using the ATR8000 as the boot drive. Things go smoother if something else is D1 with the ATR8000 acting as D2: through D4: [EDIT] But yeah. Formatting from SDX doesn't ever seem to work unless the ATR has D1: defined and there was already a formatted disk in it at the start.
  21. sorry, I only have the ATR8000. I've never had any other disk drives for my A8s. -SteveS
  22. @Jeffrey Worley I finally got this process to work! It *did* require formatting both sides of a *flippy* (I have some disks with 2 notches and 2 index holes which work on the ATR). Trying the same method with a bulk erased disk was not successful. I got the same "C" response that moonlight_mile got. I now have the 27-Apr-84 release of CP/M 2.2. I don't know if it's an different than the Mar-82 version that came with my ATR8000. Thanks for this!
×
×
  • Create New...