Jump to content

sanny

Members
  • Content Count

    424
  • Joined

  • Last visited

Everything posted by sanny

  1. Were there two different versions of the Pole Position cartridge released by Atari? Background: I bought a Pole Position cart in 1984 or 1985. I seem to remember that I had to press the button to accelerate. Releasing the button would brake/slow down. On the versions from the internet I've tried tried, the controls are reversed: accelerate by default, brake with button. Were there two versions or is my memory playing tricks on me? My cart came in a box with the XL design, but in the size of the 400/800 cartridge boxes. Sadly, I gave my cartridge away at the end of the eighties. Some years ago I bought a boxed version again from Ebay, but the box is smaller (like the newer XL and XE boxes), and the controls are the same as in the images on the internet. regards, chris
  2. If it's a 6501, maybe that is helpful: http://e4aws.silverdr.com/hacks/6500_1/
  3. Do these programs work with a P:R:? (Disclaimer: don't know about this device). Sorry, not my native language. I don't really understand what you want to say :-) regards, chris
  4. If no bootable floppy is present, or it gets downloaded later in (e.g. via AUTORUN.SYS in DOS25). From the SIO sound it appears that also SpartaDOS's RS232.COM just downloads the builtin driver. IDK, if there are programs which use their own driver, or if always the downloaded driver gets used. If programs are using their own driver, it could (I guess) still be made backward compatible. Means this stupid "concurrent mode". But it wouldn't be real concurrent mode, the device would still do its RS232 handshaking and only serve the contents of the input buffer in concurrent mode. regards, chris
  5. While I do understand your pain, Thom (and I'm feeling the same pain currently white trying to improve the cc65 serial driver), a new 850 "compatible" SIO device sounds like a good idea. Since it provides it's own driver which gets downloaded at boot time, it can work totally different to the 850 under the hood. Imagine a device with 64k input/output buffers which autonomously handles all the RS232 details. The serial line would be disconnected from the SIO bus, and the computer would just read/write the device's buffers. No "concurrent mode". We could go up to 115200 baud or whatever. regards, chris
  6. What is, and where can I find, "Jon's BIOS"?
  7. Yeah, that's what I figured, too.
  8. I found my version. It's 1.05, so your link is helpful (it has a 1.07 version), thanks. But it's still from 2001, so I thought maybe there's something newer. But, ok, I haven't encountered problems with my version, so why update something that's already working? :-) Do you (or anybody else) know if Jindrich Kubec is still active? Emulators might be able to do this, but I'm looking for a command line tool, in order to be able to run it over a collection of files and change them to ATRs in one run. regards, chris
  9. Hi all, what is the latest and greatest command line tool on Linux to convert DCM disk image files to ATR? I was using "acvt" from Jindrich Kubec in earlier times. I should still have it somewhere, but I figured I'll ask if there's something newer and still maintained. regards, chris
  10. Who is admin here, btw? Unless funkheld doesn't get a grip, I'd suggest to disable his account for posting new threads.
  11. Very nice video. Only now I found out that I can hit "SELECT" to quit the program Probably should have read the instructions before... regards, chris
  12. I'm using IDA 5.6 from 2009. Got it from work where we mostly (in fact, exclusively) use the X86 and ARM backends. I never encountered a crash or other problems there. When I had the crash with the 6502 backend I just figured that 6502 is a rather exotic backend for a professional tool, and it might not be that thoroughly maintained as X86 or ARM. But when you say you didn't have problems, I might try to disassemble the C64 program again and report the problem to Hex-Rays if it happens again. Maybe the support has bit-rotted. And I could check if we still have an IDA 4.x somewhere and try whith that version. From what I remember I was fiddling with a jump table. The SMON program is just 4K (for the $C000..$CFFF area on the C64) and contains a jump table where (destination address - 1) is stored. In order to push the two bytes on the stack and then RTS. IDA wasn't detecting this as jump table as such and I wanted to force it into, so I don't have to manually assign the destination addresses. But my memory is hazy. regards, chris
  13. Hmm. The map file shows that highest address used by the program is $8E49. (Program file size is $63C5 [25541].) Adding $2000 for __RESERVED_MEMORY__ and $800 for stack, gives $B649. $5D7 (1495) bytes available for heap with $BC20 upper limit. How much memory do you need for things you removed in order to fit into the available memory? Depending on your C-stack usage, you could also try lowering __STACKSIZE__. Be careful there, a too small stack can result in hard to debug problems. regards, chris
  14. How would you assess IDA's 6502 support? I tried to use it to disassemble a C64 program (SMON), and it crashed at some point. This was three to four years ago, maybe it has been improved in the meanwhile. regards, chris
  15. Yes, I understand your question. But why didn't you post that as follow-up on the other thread, as it apparently is related? You're creating an inflation of threads which becomes over time quite confusing ("unübersichtlich" in German, if that's your native language). Why don't you settle down on one thread each for fastbasic questions, compy-shop questions, madpascal questions, etc.? Then all the answers would be in one thread and would potentially help other people with similar problems. regards, chris
  16. Why didn't you post that as follow-up here: http://atariage.com/forums/topic/284144-have-now-tried-with-the-compy-ram-256kb-made-with-fastbasic/ ???
  17. Here's a simple scrolling example. Ok, not so simple since it can be compiled to a COM file or a cart image. The cart image is intended for a MaxFlash 8 cart. It's in assembler, though. regards, chris hitobi.zip
  18. > I can only 8x pixel hscrol. To scroll more that eight pixels you have to modify the screen memory start address of the line to scroll in your display list. Like I said before: Please read the documentation. You said before that you are retired and have much time to ask questions. How about using your time to learn about the system? Asking questions for every simple thing wastes the time of everyone, and they (me at least) don't have that much time... regards, chris
  19. What is wrong with dir2atr? I don't understand what you mean with "but it should not produce a finished dosdisk." dir2atr creates an ATR image file with the files in the source directory. regards, chris
  20. Hello funkheld, Ok. I'm 51, so age-wise nearer to you than to my children :-) I guess most of the folks here are at or around my age... I didn't want to offend you with my post. It's just that some of your posts (e.g. http://atariage.com/forums/topic/283680-i-would-like-to-use-please-the-memory-in-the-atari800xl-of-c000-cfff-with-m/ or http://atariage.com/forums/topic/283774-as-i-find-in-fastbasic-a-startaddress-from-a-proc-for-a-vbi/) appear to me that you want us to do your homework. In the former example you should be aware what it means to turn off ROM to use the $C000..$CFFF area before you try to do that. That's why I said, "read documentation". In the latter one you seemingly use assembly language, again with apparently just cursory knowledge. Read docs about 6502 assembly language programming. So, what are you trying to do? Are you "playing around" with ACTION, MadPascal, and Fastbasic? To decide which one to use for "going into depth"? Or "go into depth" with each of them? regards, chris
  21. funkheld, can't you think and research a little bit yourself, before you are posting a question? There's information about all aspects of Atari programming available on the internet. Read the manuals of the tools you are using (e.g. Fastbasic) and hardware and system docs. Then, if you still can't find a solution, post your question. You are currently coming around like someone who has no idea what he's doing, but wants to create a super-duper program. Start small and build up on it... regards, chris
  22. Yaron, your posts aren't really helpful. What was the intention of your original message? Do you want any help? Answering to your initial post: Yes, -O can have problems. After all it generates different code. OTOH, many people seem to use it without problems. So no one can tell what is at fault. So, if you want to nail down the problem at hand, either debug it yourself (the second bullet in my last post), or give us something that doesn't work so we can debug it. Everything else is just blahblah... regards, chris
  23. Still, could be a problem in the compiler or a problem in your code. Now, that you can reproduce it again, you could try to remove parts of your program to get a really simple example code where the problem happens. So small, that you don't publish IP when you send it to the cc65 developers. That's btw. the preferred way to send compiler bug reports. Use the debugger of an emulator (Altirra or Atari800) and set a breakpoint to memory write to the memory of the display list. When the bp triggers, use the map file to figure out where it happens. Send me the source code (or link to it) and I'd take a look. I won't share your source code to anyone else. regards, chris
  24. This could be interesting for more support in other DOSes. Is there information available about how to access the Z: device, and do all Z: handlers follow that interface?
×
×
  • Create New...