Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by danwinslow

  1. I can download it, but when I view it it's blank.
  2. I bet Albert would have some input on that.
  3. I was mostly the money, Mark Dusko was the actual hardware guy. He has his design up on his website, though. I am sure he would have no problem if someone wanted to make another run. I have not heard from him in some time, but his atariage handle is puppetmark. I would imagine that dropcheck or one of the other folks still producing boards would be able to handle it. I think a pass-through cart would be much better, and/or a PBI device. The CS8900A is hard to source in 5 volts. Lots of people seem to think that a 'all in one' with its own TCP stack is the way to go, but unless it has a memory mapped transfer bus it won't work very well. SIO is not capable of handling it. And, as you've seen, a dedicated single purpose stack is very doable on the eight bits, especially to support UDP.
  4. That looks awesome. Does the Altirra DC emulation work with it? Also, I have about 5 original DC's left.
  5. So, I have a functional falcon motherboard, but the floppy connector has been pulled off of the MB. It doesn't look like a normal connector...it has a bunch of little teeth that look like they are supposed to pierce the flat cable, possibly with a bar or other fastener along the top side clipped into place. What kind of connector is this, and is it possible to reconnect a floppy cable to the motherboard? Thanks Dan
  6. My very first computer was a zx80. I wrote my very first program on it too, a BASIC version of "Lunar Lander" with an 'M' for the lander and a landscape of periods and dashes. Makes me mist up just thinking about it. Fast forward to now - alongside all my atari stuff I have a giant box filled with Sinclair/Timex stuff.
  7. I recently had responses delayed by 2 months or so. They weren't important, just questions...but I had kind of given up on getting a response. On the other hand, I've had about 10 or so transactions involving services over the last 5 years, and while they weren't particularly speedy, they were no where near that slow and they all wound up great.
  8. Yes, he's right. Abstraction has a cost. Taken too far it's often worse than the original problems. Unless you know you will be working with a team of programmers on a large project it's mostly not worth taking it too far.
  9. The essence of encapsulation is that everything is done via interface specification. If your code in one spot 'knows' anything about how code in another spot does something, you are not doing it right. For instance, your getsuit call is a mapper. It maps an integer onto a symbolic value expressed as a string. It may or may not use an array internally to do a lookup, but as long as external code doesn't have to know about that detail, your encapsulation is good. You could swap out the lookup array with a read from a file, and you wouldn't have to change anything else in the program. The simple act of putting it behind a function instead of leaving it as a bare global array is doing it right. Your TYPE declaration is extra points. You also seem to be thinking about exactly how to represent the thing that holds the keys (integer) and values(string suit name). An array is the natural way to do this, but there are some options. I am rusty on my Pascal, but there is an Enumeration type, which you could use (http://wiki.lazarus.freepascal.org/Enumerated_types) that comes with the ability to get the string form of the enum value...but I don't know if the pascal you are using has that. Anyway, so you have to init this array somewhere, and that's just a fact. If your pascal supports it, that's what the implementation and initialization sections of a unit is for: unit advancedunit; interface implementation initialization begin (* here may be placed code that is *) (* executed as the unit gets loaded *) end finalization (* code executed at program end *) end. That makes a 'private' unit level var and a chance to run code against at startup. In your case you could just put your array in the implementation section and use an array initialization literal. If your pascal does not support this, then my advice is to not worry about it being 'global'. You have the concept down, so whether or not you leave a global in your code or not doesn't matter unless you expect teams of programmers using your code in the future to create large systems. In this case, they will make fun of you. The other option is to use a function level declaration to 're init it every time'. It's probably not that much impact on runspeed unless you call getsuit constantly. Many compilers are smart enough to realize that they can make that kind of completely static initialization something that just happens once.
  10. I really liked Ada, I was in the DoD world when it got started. In fact, I participated in the Ironman tests on the Honeywell/Bull team. Most people wound up not liking it, mostly because the compilers just could not handle it very well, it was WAY ahead of it's time. Turbo pascal eventually turned into Delphi I think, but that's not used much anymore.
  11. If you mean in the modern development industry, then no, nobody really uses it for new development. There are nooks and crannies doing legacy maintenance that might have some pascal, but it would less than 1% of the market, probably much less.
  12. I am interested in 2 full builds. I assume we are still waiting a bit on those?
  13. In another thread: http://atariage.com/forums/topic/267084-understanding-and-using-graphics-mode-with-cc65/ tschak909 said: The (only?) ways to get a 'fifth color' are all using the ANTIC char modes 4 and 5. It's a GPRIOR bit setting as I recall, but as advised you might want to check out the Atari system docs. Your quest to write for many computers using CC65 TDI is probably not going to work out very well. You should design your own version of a TDI-like interface and do special implementations for each computer. If you must stay in mode 1 then check out PMG overlays for more color.
  14. Wow, this is the most successful trolling I've seen in a while. OP is winning by a mile, not because they are right, but because you guys are all excited about it.
  15. I get it, but I don't agree. It's not about what's easy or safe, it's about understanding. I've been a professional developer for almost 40 years, and this is my opinion.
  16. Yeah, I expected someone to say this. You're not wrong in fact, but I personally feel like Java and the other OO languages can put a burden of extra complexity in when all you are doing is just to try and learn programming basics, especially when your stated target is 2600 programming. I figured BASIC would be a good way to prepare for Batari. BASIC has this rep for 'spaghetti code' but let me assure you you can freely create pasta in any language, and people often do. Using a language that doesn't prevent you from doing it in fact is a good way to learn the importance of certain hygienic programming practices. Use of goto is not in and of itself bad, and there are situations even in modern languages where it is an appropriate choice. Actually, I always recommend plan ANSI C as the proper introductory language for a serious computer education. If you learn C well, you will learn everything you'll ever need to know and stuff that most people don't ever know, and you will appreciate the modern languages much better.
  17. Well, Java is a fine language in general, but it is not applicable hardly at all to 2600 programming. As was mentioned, the very basic rock-bottom concepts like data, if/then,looping, etc. are able to be learned in any language. If that's the only course you have, then sure give it a shot, but keep in mind that Java is NOT an introductory language, no matter what the colleges seem to think. It is an advanced subject, so if you find yourself baffled and overwhelmed it does not mean that you have some kid of problem understanding, it means that even basic Java it really hard without any prior experience programming. Or, maybe you have a knack for it and you'll do great, I don't know, but I expect you'll have some trouble. I do have some other suggestions for you: 1. Google for online courses. There are probably some free ones even, like 'introduction to programming' on you-tube or whatever. 2. Learn BASIC instead. BASIC was created to be easy to learn ( Beginners All-purpose Symbolic Instruction Code). If you have an actual 8-bit Atari, you can use that, or you can grab the Altirra emulator and use that. 3. You can grab tons of different kinds of BASICS for use on your home computer. This, for instance : http://www.nicholson.com/rhn/basic/. Assuming you're on Windows, you could even download the free Visual Basic Express stuff (which I think is now called 'Visual Studio Community' or something dumb like that). Tons of on-line course material on all of the BASICs. I would not try Batari first unless you are a genius. The language is fine, but that 2600 machine is so bizarre and restricted and low-level it's like trying to program a toaster.
  18. OK, thanks. Just read up on ZPU, interesting. I assume vexriscv is a similar situation? Well, that would put it into address space at some spot, so yep as long as the device has a memory mappable command/data bus. PBI would also work.
  19. On the Ethernet subject, I can recommend one if you get to that point. Most convenient would be a CS8900A compatible as I already have a driver, but anything with an 8-bit mode would be fine. You may want to consider a chip that has its own TCP stack already on it, too, although that would be a big change. The crucial point there is that it's got to be interfaced via PBI or something, or even mapped in memory. Reading from SIO serial won't work well.
  20. OK, Thanks Santos. So. Santos or foft- 1. Will I need a JTAG cable? Can I upload through the serial port? 2. Is there a native OS or something on this board, like a linux or whatever? 3. What dev tools will produce the correct binaries? GCC? Visual C++? Either? 4. Any docs that relate to the process of getting new firmware onto the board? If the board is an FPGA, and that only, I assume the only way to get new firmware on it is with the JTAG or serial? 5. Besides JTAG, do I need any special hardware/software to upload or talk to the board? 5. Is it too late to talk you into adding a cheap Ethernet solution to the board?
  21. I doubt if any one person would be able to take all of this up. Phaeron, Flashjazzcat, the many excellent german & polish coders, all come to mind. I am actually very experienced with C and I've done some simplistic USB HID work before, so I might be able to help with item i. I would need a lot more details about the USB input architecture and probably would eventually need a test system.
  • Create New...