Jump to content

Tyrop

Members
  • Content Count

    114
  • Joined

  • Last visited

Community Reputation

9 Neutral

About Tyrop

  • Rank
    Chopper Commander
  1. Thanks, Jac! Java version says, java version "1.8.0_191" Java SE Runtime Environment (build 1.8.0_191-b12) Java HotSpot Client VM (build 25.191-b12, mixed mode)
  2. I wrote a simple BBS in Basic back in the day (written for an 850 interface module and Hayes Smartmodem). When a modem is connected, the BBS interfaces with the remote user using the R: device, and when a user logs on locally, it uses the E: device. Does anyone know if there is a utility that can be loaded into memory that can piggyback R: onto E: (or somehow merge the two) so that if I break into Basic or go to DOS, the operating system will use R: instead of (or in addition to) E:? If there is such a thing, I would love to be able to log into my BBS remotely, press a menu command that breaks me into Basic or DOS so I can remotely control my computer (like a gotomypc for the Atari), and then resume .
  3. I read Jac's website and also watched the installation videos. I downloaded Jac's pre-made installation into C:\jac\wudsn. When I run Eclipse, I get this error. I tried going to the Eclipse website to download Eclipse but there are so many choices, I don't know which to download. Can someone tell me what I'm doing wrong?
  4. That did the trick JAC! Thank you so much for showing me what to do. Your IDE is a tremendous piece of work. It and Altirra are of great help in debugging.
  5. Thanks, JAC! I removed the space in the path, and I think it works, though not exactly as in the videos tutorials. Here is a video. Is this working right? Also, the other samples have the same issues: space in the file name. ScreenCapture_1-24-2016 11.58.49 AM.wmv
  6. ScreenCapture_1-21-2016 10.43.49 PM.wmv Thank you, JAC! Attached is a video. I tried to show all relevant information. I can't figure out why Altirra is not breaking or giving me source level debugging.
  7. I'm hoping someone can help me with breakpoints. I installed Jac's zero installation and I set it up as in the videos. The default compiler is MADS and the default emulator is Altirra (version 2.7). All xex, lst, lab and atdbg files are set to "source" folder, not "temporary" and they are being created. I tried adding a breakpoint to the "Hello World" sample right at line 9 (sta $d40a) and when I select "compile and run," Altirra loads and runs the program but does not break into the debugger. The program just runs in its endless loop. When I go into the debugger, the disassemble window is empty and memory windows is set to $0000. If I hit break, then the disassemble windows shows the program with labels, but no source level window opens. Console window is empty. Also, if I keep hitting F8, Altirra only seems to stop at LOOP LDA VCOUNT. I don't see any breakpoint being set. What am I doing wrong? Is there something in Altirra I need to set?
  8. I seem to remember that Atari gave a reason for the large text modes, eg, Basic's graphics modes 1 and 2, in one of the manuals or maybe one of the books on Basic. If I remember correctly, Atari's reason was something to the effect of titles, banners and labels. I also remember an early article, maybe in Compute magazine, that explained that Atari was one of the few computer of the time (maybe the only one circa 1981) that allowed the programmer to redefine the character set to create a custom font. As someone mentioned above, this a powerful capability, particularly in the multicolor modes, to create playfields. Many games also used redefined characters as sprites.
  9. In the early 80's, my father worked at IBM and he told me that the system engineers said that blue background with white text was known to be easy on the eyes, and many set up their terminals with that color combo. In early versions of MS Word, Edit and similar Microsoft editing environments like Quick C, they defaulted to white on blue. Incidentally, my father bought us an Atari 800, and not an IBM PC.
  10. BTW, the SIZE command will give you 3 numbers, the first of which is the beginning of free memory (which I think is the first free byte after the end of DOS).
  11. You can also assemble your program to an object file and then binary load it in DOS to run it. To do this in MAC/65, you need to put .OPT OBJ at the top of your program listing (note - .OPT is preceded by a period). I usually put it on line 1. Then, use the command ASM ,,#D:OBJECT.OBJ. Note - 2 commas after ASM. This will compile the source code in memory into an object file called OBJECT.OBJ which you can then binary load, and I think it will just run. Don't forget to save your source file before you edit to DOS!
  12. On the disk version, BUG65 was a separate program. You had to exit MAC/65, go into DOS (or OS/A+ which is what came on the disk) and then go into BUG65. On the cartidge version, the debugger was DDT (Dunion's Debugging Tool) and you go into it from within MAC/65 by typing "DDT." There is a MAC/65 manual online somewhere. Try doing a google seach for "mac/65 manual." I think DDT was better than BUG65. There is also a standalone, more advanced version of DDT called EXDDT (also written by Dunion) which is more advanced.
  13. For MADS, the .lst file with the complete listing is used. What do you mean? ATASM creates the same kind of listing only via "-v" or ".OPT LIST" and is creates it on sdtout. That's why WUDSN IDE captures the output and converts it into an XASM compatible label file (for use in Atari800Win for example). Or dou you refer to the "-l" option with is there (only) in the most recent ATASM I am referring to the -l option in ATASM. I would love to use ATASM with WUDSN and be able to do source level debugging with Altirra, but I think it is not possible unless ATASM's author adds the ability to do a listing file similar to MADS. Your previous post showed me that it may not be too hard for me to use MADS if I already know ATASM, so I may just try to convert my source listing to MADS syntax so that I can get the source level debugging. BTW, I think WUDSN and Altirra are unbelievably amazing works. Once I used that combination, I could never go back to anything else for writing and debugging Atari 6502.
  14. There are some vendors that have replacement parts. B&C ComputerVisions comes to mind. If you search eBay for Atari 800 keyboard, you will see some new replacement keyboards. I'm not sure about the answer to your power brick question. Maybe someone else can answer. Atari disks will not work in any IBM disk drive. There was an old program called anadisk for the PC that claimed to be able to read ATari disks, but I read on forums at the time that it did not work. I tried it myself and I ruined an Atari disk. Then I read that it only worked on Atari disks formatted a certain way, possibly by a 1050 (which has the capability of formatting single density and enhanced density). However, you can copy files from an Atari to a PC over a special cable called an SIO2PC cable. You can buy one at atarimax.com. You can then create disk images on the PC, and using the software that comes with the cable, the Atari will think the disk image is just another disk in a disk drive. There is a lot of Atari software on the Internet that comes in the form of a disk image. They usually have the extension .atr.
  15. Altirra also does that for ATASM. Is there any difference in the the way it loads the labels in MADS that is different than ATASM? Thank you for you post, JAC!, I did not realize that it was that simple to go to MADS from Mac/65.
×
×
  • Create New...