Jump to content

a8isa1

Members
  • Content Count

    1,844
  • Joined

  • Last visited

Everything posted by a8isa1

  1. I'm revisiting your six-pack. I'm using AVGCart to load the each ATR (in non-SIO mode, for speed). The cart has the ability to mount multiple ATRs. I noticed it's possible to save to the program disk instead of the save game disk. I don't plan to do this but it's easy for me to make a mistake. Would accidentally saving to the program disk corrupt said disk? Regards, SteveS p.s. Still loving these Quads! Thanks! p.p.s. I can't believe 8 years have passed!
  2. I don't recall if I ever tried to use the serial port of the ATR8000 with DOS 2.5 so I wanted to test. Unfortunately I no longer have a null modem or a PC with a real serial port with which connect. I decided to cobble together a NodeMCU dev board into a wifi modem for the ATR8000 for testing. It took me quite a bit of time because I am still bad at soldering and made many mistakes. Not even sure how it started working. The build would have been simple for anyone else. Only a small piece of prototype board, a MAX233 IC, and a card edge connector is all I used. And, a last minute decoupling capacitor. Too late to make a long story short. The driver I had on my work disk (ATR) for a couple decades or more does not work under Does 2.5 or 2.0 (S?). It does work with MyDOS 4.53/4. The driver seems limited to 4800 bps. I thought (but am not certain) at some point I had found a driver that worked with the ATR8000 at 9600 bps. Hopefully one day that driver will resurface. Sorry, none of this fills erichenneke's request but perhaps the driver is one that hasn't been archived. I'm posting a ZIP with ATR8000.SER and some other drivers. -SteveS A8SerialDrivers.zip
  3. Sorry, I didn't say that very well. when I said "derailed" I meant by *me* making my request of you.
  4. I don't want stay off topic for long but a whole new thread would seem out of context just for this question. Does Axlon upgrade only require 2 16K RAM boards be in the system to get the full 48K base memory? I had always thought 16K + 32K boards were required. would have deterred me from buying axlon in the early '80s. I can blame only procrastination from then on.
  5. I get that same screen booting my stock 800 with AVGCart. Press RESET. AVGCart menu should appear. Please let me know how well SDX and Side 2 emulation (via AVGCart) works with the Axlon upgrade. I basically only use the 800 for some games when the 800XL is doing something else. I'd love to put Axlon "some day". (I've been saying "some day" for Axlon upgrade since the day it was announced)
  6. Hi, luckybuck! Great to see you are still around! This is the first I've heard of Turbo BASIC XL 2.11. Before this thread gets further derailed I urge you to start a new thread and provide a brief description of where Turbo BASIC XL stands now and where future development might be headed. Thanks!
  7. SJCarden dropped me a note last night in chat (currently at ##atari channel on Freenode but the users are are likely moving 100% to Libera Chat). SJCarden probably intended the message to be in response to this thread. He said, "Please pas it along that TDline2 will work with sd2.2c,d,m sd3.3a,b,c,d all versions of RealDOS" I'm pretty sure TDLINE2 has a fixed DOW function. I don't use it myself because my DS1307/DS3231 non-driver conflicts with TDLINE2 and I can't code my way out of a paper bag. -SteveS
  8. My 800 records 55 degrees almost immediately after program loads via SIO2PC-USB. My 800XL never changes from 15 degrees. Thanks to my RTC module, a DS3231, inside the 800XL I know the ambient temperature is 89 degrees F (31.67 C).
  9. a8isa1's 800 shifts to bar 6 in 50 seconds from a cold start <-- click here to view
  10. You can see what happens if you click my link. I don't know how to embed videos. Sorry.
  11. a8isa1's 1981 800 <--click me Takes only 1:15 for all the test segments to black out from a cold start. I needed to flash a cartridge with drpeter_Artefact_Test_3.1.xex otherwise the machine would be mostly warmed up before the test started.
  12. Yes, 800XL display appears as in your photo except with the NTSC palette.
  13. Sorry, no scanlines. My display these days is limited to a pretty basic and now old scan converter and a low end VGA 4:3 LCD. Scanlines get filtered out. These are the best pictures I can manage.
  14. On my 1981 NTSC 800 the line appears at marking 6, whether cold or warmed up. My 800XL cases and motherboards have been swapped so many times I cannot say the age of the system. Current incarnation has a second revision NTSC Antic if that matters. Line always appears at marking 5. Regards, SteveS
  15. That drive is configured for use on a PC. IBM originally set both floppy drives to DS1 and used a *flip* in the cable for the second drive. You could desolder the holes and install dip switches. The ATR8000 designates the drive with DS0 selected as Atari D1: -SteveS p.s. The drive after the flip in the cable was probably the first drive on a PC. (It's been a long time. Memory sketchy)
  16. Yep, 1.2 MB drives on the ATR8000 format to 4004 sectors. I tried to write a procedure to make it easy to setup a 1.2 MB drive but the ATR8000 is so quirky in a single drive configuration that I didn't come up with instructions for all the things that can and often do go wrong. Below is basically what happens if the process goes smoothly. I'm using FujiNet in this example because nothing else I still own wanted cooperate, not SDrive-MAX (homebrew), SIO2PC cable, swapping drive mechs It's easier if one is able to change the drive the drive select but hopefully this will work for your situation Leave the drive and the ATR8000 powered off. Boot Atari w/ MyDOS 4.53/4 using FujiNet. My was plugged directly into the ATR8000 because cables won't stay plugged into the fujinet 1.0 passthru SIO port. While the Fujinet is still attached use MyDOS option O - Change Config. Use it twice (because it works more reliably). Once to remove drive 1 then again with the 1.2MB drive parameters which are: Drive Number: 1 Remove Drive: N Is drive configurable? Y High capacity drive: N I drive double sided? Y Tracks/side? 77 Step rate: 3 When I hit enter I should se under the MyDOS title the following: Disks 1S= '=' signifies a double sided disk. 'S' signifies Single density. Disk is not formatted yet so 'S' is assumed UNPLUG FUJINET. Power up disk. Insert diskette. Power up ATR8000. I try to change density with command 'P' 'P' and then '1,D' which is drive 1, double density If it works then great but ften the density won't change. This seems to be one of those ATR8000/MyDOS quirks. I go ahead and format the disk. If it formatted in single density I use the 'P' command again. Density should change this time. Format the disk again. If while formatting I hear the stepper motor has a regular cadence then all is well. If there's one sound and very long pause before the next sound then something is not right. Probably have to start over If formatting, in double density, is successful then write DOS to the disk, MyDOS option 'H' Test by booting the computer. No need to reset the ATR8000. Hang onto that disk. Note: I had to unplug my FujiNet 1.0 during the process. With FujiNet version 1.4 and up perhaps one can just switch it off. Configuring a drive is much easier if the drive select of the ATR8000's drive can be set to DS1 (aka D2:). Usually I can just set the drive parameter and format. No issues at all or far fewer issues at least. Well, that's it for my re-visit to setting up a 1.2 MB drive on the ATR8000. Eric, I hope it works for you as well. Regard, SteveS
  17. I'm going mad! Someone please try this: Make sure FujiNet is powered externally. Make sure webui has Config Boot set. Boot Atari to CONFIG Mount from ATARI-APPS.IRATA.ONLINE/DOS/Atari DOS 2.0s.atr Press OPTION to boot Atari DOS Press FujiNet Button C *RESET* Try to get a directory listing. You should get Error 138 <------- Do NOT skip this step Try to reboot your Atari. Do an atari RESET. Turn off the machine then on. Try FN Reset more times. Just don't unplug Fujinet's power cable *YET*. For me CONFIG will never boot again. I'm stuck until I unplug FujiNet's power cable. Regards, SteveS
  18. I see. Here's my 2 cents: Configured as I described. I press FN Reset. Now my ATR is no longer mounted. Config disk is not mounted either. I shut off my Atari and turn it back on. I don't get into CONFIG and I don't boot a mounted disk. I have nothing available. I can only get back to operational if I remember to pull the plug on FujiNet. I have to do this to physcially reach the power switch on Fujinet 1.0 as the cable end partially blocks access to the switch. No, I don't offer a solution. I'm just venting. SteveS p.s. Done venting. Perhaps yet another button mode that forces CONFIG disk to be mounted. [EDIT] Once FNC-TOOLS are available I can help myself of out my mess.
  19. I don't know if I've encountered a bug, two bugs, or I'm misunderstanding how this is supposed to work. I'm running Fujinet 1.0 hardware. It's externally powered plugged into my 800XL. FN firmware is 0.5.879c407c 2021-04-02 01:14:21. WebUI has CONFIG Boot set. I've mounted Atari DOS 2.0S ATR from ATARI-APPS.IRATA.ONLINE. It boots OK. When I press FujNet Reset I expect to see the Config disk appear as D1:. However, when I try to get a directory listing the activity light flashes brightly then goes to dimly lit for a couple of seconds. I get Error 138. If I then do a coldstart (FN is still powered) the activity light flashes once dimly then the 800XL reboots itself, over and over again. I'm providing a debug trace. It begins when I try to get that directory listing. Regards, SteveS FN_reset_capture.zip
  20. This turns out to be a user problem but it was one of years of bad habits in the making. I some distant past I had appended RVerter/Bobverter drivers to most of the terminal programs I had been using on the disk that I use for everything. A few years ago I started using SpartaDOS X and the newest updates/betas of ICET XE. By this time I had dropped the habit of attaching the driver to the executables. I don't need such a shortcut. SDX has batch files. Now FujNet comes along and I need the 850 driver loaded. No problem with this. Later on I decide to test FujiNet on my 800. Unfortunately, I can't use SDX or my CF card or ICET XE on my stock 800. This forces me to dig my old and small collection of terminal programs. I load the 850 driver and whichever terminal program I wish to use not realizing a driver conflict was waiting for me, Well, at least that's what I assume was happening. I don't see the Bobverter splash notice on my 800. (It does appear now when I repeat the exercise on my 800XL). I don't have debug tools on 800 and I don't have the know-how to recreate the problem in emulators. So, yeah. Just an assumption of what happened. Sorry, for the false alarm! Regards, SteveS
  21. It runs on my stock 48K 800 but it will not accept any keystrokes which means I can't select Forecast. Console keys do work. I'm running firmware 0.5.879c407c 2021-04-02 01:14:21 on a FujiNet 1.0. I love your program BTW (when using my 800XL)! Regards, SteveS
  22. Someone asked in IRC about 80 column terminal programs for 800. I could not recall if Omnicom works on the 800 or not. Apparently it doesn't, however when the program crashed I tried Flickerterm 80 which I know should work. After I load the 850 handler and start Flickerterm 80 it comes up in ASCII mode and at 1200 baud. However, the keyboard does not respond. After about 5 seconds the emulation switches to VT100 and baud rate is now at 19,200. The keyboard still will not respond and now the FujiNet activity LED is flashing brightly with about 3 pulses per second. It never stops flashing. Pressing button C resets Fujinet but the LED continues to flash. I next tried Bobterm but it halts while loading some module. I then tried AMODEM 4.2. I'm able to enter an ATDT sequence and connect but the keyboard stops responding here as well. Fujinet is not flashing. I recently updated the firmware. Fujinet works fine on my 800XL I'm providing fujinet debugging data. It begins at the point I started the 850 handler. Below are some excerpts that I thought odd. They occured with no intervention from me. The keyboard remained non responsive the whole time. set_baudrate change from 19200 to 1200 Modem streaming at 1200 baud Modem was active - resetting SIO baud set_baudrate change from 1200 to 19200 set_baudrate change from 19200 to 1200 Modem streaming at 1200 baud Modem was active - resetting SIO baud set_baudrate change from 1200 to 19200 set_baudrate change from 19200 to 19200 Modem streaming at 19200 baud Modem was active - resetting SIO baud set_baudrate change from 19200 to 19200 set_baudrate change from 19200 to 19200 Modem streaming at 19200 baud Modem was active - resetting SIO baud set_baudrate change from 19200 to 19200 Regards, SteveS atari800_fujinet_debugging.zip
  23. There were two separate issues as far as I can tell. 1) A binary load file I hadn't used previously used on FujiNet didn't work then 3 more files also did not work 2) Something happened to my TNFS server and nothing was loading. I did not realize this at the time and thought this was a continuation of the issue above. Mozzwald suggested I restart the server. The file that was queued was a binary file that did have an .XEX extension. I thought issue #1 had been solved. However, the next file I tried was Galactic Chase. This did not load. I queued up each of the files that hadn't loaded the first time and once again none of them would load. I thought nothing had been resolved. I kept trying. A new file, perhaps Bosconian, then worked. At this point I had learned how I can obtain the debug data which I did and passed it on to Thom. I subsequently learned that binary load files need an extension that FujiNet firmware can parse. 'XEX' was mentioned. I was not previously aware of this requirement but now I am. Problem solved. I've never needed to do this for any other disk emulation, disk emulation hardware, or Atari emulators but now I know it's needed for FujiNet. The collection from sourced my files from was originally derived from someone else's disk set. None of the file names have extensions. Not knowing I needed file extensions I simply copied the files to the TNFSD folder. -SteveS
  24. Still having problems. Many XEXes will no load from my local TNFS server. No activity light on FujiNet. I'm providing a debug trace of the game Galactic Chase. Captured with mincom terminal emulator -SteveS CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ignoring status command CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ignoring status command CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ignoring status command CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ignoring status command CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ignoring status command CF: 31 53 00 00 84 FujiNet CONFIG boot disk sio_process() ACK! disk STATUS response: 0x00, 0xff, 0xe0 ->SIO write 4 bytes COMPLETE! CF: 31 52 01 00 84 FujiNet CONFIG boot disk sio_process() ACK! ATR READ ->SIO write 128 bytes COMPLETE! CF: 31 52 02 00 85 FujiNet CONFIG boot disk sio_process() ACK! ATR READ ->SIO write 128 bytes COMPLETE! CF: 31 52 03 00 86 FujiNet CONFIG boot disk sio_process() ACK! ATR READ ->SIO write 128 bytes COMPLETE! CF: 31 52 04 00 87 FujiNet CONFIG boot disk sio_process() ACK! ATR READ ->SIO write 128 bytes COMPLETE! CF: 70 fa 00 00 6b sioFuji::sio_process() called ACK! Fuji cmd: GET WIFI STATUS ->SIO write 1 bytes COMPLETE! CF: 70 d7 00 00 48 sioFuji::sio_process() called ACK! ::mount {5} "192.168.1.188" ::mount_local Attempting mount of "192.168.1.188" ::mount_tnfs {5:0} "192.168.1.188" Calling TNFS::begin Resolving hostname "192.168.1.188" Resolved to address 192.168.1.188 TNFS mount 192.168.1.188[192.168.1.188]:16384 TNFS mount successful. session: 0x23c6, version: 0x0102, min_retry: 1000ms vfs_tnfs_register "/tnfs0x3fff9c98" @ 0x3fff9c98 = 0 "ESP_OK" Selecting '/Galactic Chase (1981)(Spectrum)' from host #5 as r on D1: fujiHost #5 opening file path "/Galactic Chase (1981)(Spectrum)" TNFS open file: "/Galactic Chase (1981)(Spectrum)" (0x0001, 0x01b6) File opened, handle ID: 0, size: 15898, pos: 0 ::get_filesize tnfs_lseek currpos=0, pos=0, typ=1 tnfs_lseek success, new pos=0, response pos=0 tnfs_lseek currpos=0, pos=0, typ=2 tnfs_lseek success, new pos=15898, response pos=15898 tnfs_lseek currpos=15898, pos=0, typ=0 tnfs_lseek success, new pos=0, response pos=0 disk MOUNT ATR MOUNT tnfs_lseek currpos=0, pos=0, typ=0 tnfs_lseek success, new pos=0, response pos=0 ATR header missing 'NICKATARI' ::mount {1} "fujinet.online" ::mount_local Attempting mount of "fujinet.online" ::mount_tnfs {1:0} "fujinet.online" Calling TNFS::begin Resolving hostname "fujinet.online" Resolved to address 157.245.127.133 TNFS mount fujinet.online[157.245.127.133]:16384 TNFS mount successful. session: 0x9f99, version: 0x0102, min_retry: 1000ms vfs_tnfs_register "/tnfs0x3fffa9e4" @ 0x3fffa9e4 = 0 "ESP_OK" Selecting '/cassette/O_Rileys_Mine.cas' from host #1 as r on D8: fujiHost #1 opening file path "/cassette/O_Rileys_Mine.cas" TNFS open file: "/cassette/O_Rileys_Mine.cas" (0x0001, 0x01b6) File opened, handle ID: 0, size: 11891, pos: 0 ::get_filesize tnfs_lseek currpos=0, pos=0, typ=1 tnfs_lseek success, new pos=0, response pos=0 tnfs_lseek currpos=0, pos=0, typ=2 tnfs_lseek success, new pos=11891, response pos=11891 tnfs_lseek currpos=11891, pos=0, typ=0 tnfs_lseek success, new pos=0, response pos=0 disk MOUNT Cassette image filesize = 11891 tnfs_lseek currpos=0, pos=0, typ=0 tnfs_lseek success, new pos=0, response pos=0 FUJI File Found COMPLETE! CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84 CF: 31 53 00 00 84
×
×
  • Create New...