Jump to content

david__schmidt

Members
  • Content Count

    163
  • Joined

  • Last visited

Everything posted by david__schmidt

  1. If you want to make arcade-quality games, your learning curve will be steep. The bitmapped graphics system in the Apple II is among the most complex out there, with no built-in circuitry like those fancy Commodore or Ataris to help you. I don't know what you've seen and consider "Crrrrrrraaaaaaaap," but there's this:
  2. You want to be sure it has a 16k memory ("language") card in slot 0. That gets you up to 64k, and is the max requirement any game that will run on a II+ has. While you're there, turn it on and make sure you hear a "beep" - that will indicate it's alive. No beep (assuming the speaker is good and connected) is a bad sign. As is a loud bang and smoke coming from the power supply - which is altogether likely to happen if it's been sitting all this time.
  3. That's the downside of you getting to use something that I built because I want it. I use Java daily at work - so it's very comfortable for me. It's very much a "today" language for me. I get threats from time to time that folks are going to port it to [insert your favorite language du jour here] but it never quite happens. So... no.
  4. It's a matter of it being able to have prereqs enough to support Java (which isn't too hard) and the rxtx serial library (which is a little more OS-specific). Back in the olden days of yore, Sun maintained serial comms libraries for wherever their JVM ran. Now, we're not so lucky.
  5. Perhaps "Ready." With a blinking block after. :-)
  6. Except it doesn't. It means the server established a good connection to a serial device (at the host end) and it's ready to talk to that. There's no way to know if you're "ready to roll" unless/until a command comes through that connection. The server is just that - a server. Commands come in from a client attached to the server. When you mash the button, it doesn't magically make an Apple II appear at the other end.
  7. Do you have any other means of using ADTPro? If so, you can build yourself a DOS-based ADT disk to bootstrap with: http://adtpro.com/bootstrap.html#Bootstrapping_DOS Good question. I can't, definitively. Java 6 should be OK, though. I would only expect the rxtx library to run on an NT kernel (i.e. not Win 9x).
  8. There is some chatter over on comp.sys.apple2 on (vastly) speeding up audio encoding; if they settle on a reliable rate, and I get ambitious - I'll incorporate that and we should benefit. Sure thing. I made it because I wanted it. I'm happy others find it useful.
  9. One thing I've learned about wording in general - someone, somewhere will always misinterpret it, no matter how much sense it makes to you. It is the way of things.
  10. Regardless of OS - you'll need a fairly recent version of Java on the host. A 32-bit Windows is a base requirement for the serial libraries. Windows 2000 may work - XP is a better bet. If you want to go all the way back to Windows 98, you might want to look at using the old ADT (not ADTPro) server: https://github.com/david-schmidt/adt/releases/tag/v2.4
  11. Yes, that would work. It would take a long time to transfer 5MB (though a lot of it would probably be blank, so maybe it wouldn't be so bad). But remember: you aren't installing SOS on a ProFile; SOS really only lives on the boot floppy! All you need to do with a ProFile is format or erase it and lay down the SOS (which is identical to ProDOS) filesystem structure. (Which any formatting utility, including SOS Utilities, would do for you.)
  12. Maybe you mean ADTPro? It's different than ADT. There is an audio tester because it lends itself to sending continuous 'pings' until the other side can hear while you fiddle with volume settings, etc. that makes it useful for tuning. But Serial is kind of binary in this regard: either you've got the right cable wiring, or it won't work. Also, you've got to use the right operating system-level hardware abstraction (COM port or /dev/xyz device) that maps to your physical port, or it won't work. From either client or server perspective, there's no way to see into the physicality of the connection in between to do anything meaningful. "(D)IR" remains a canonical test for serial connectivity. And when you get "host timeout," that means the connection isn't correct yet.
  13. The "Connected" indication is meaningless in this context. It simply means that the hardware serial port is available and engaged from the server's perspective, and it can start pushing/pulling bits on it. It doesn't indicate that there's something on the other end of that serial port that it is talking to.
  14. What's your conversion pinout from 25-pin to 9-pin?
  15. I hadn't even thought of that - I was having trouble finding a cross-platform way of checking bit width of the OS from within Java. Moving that out into the Winders batch file solves that problem right there!
  16. I'm now printing out the equivalent of the commands I mentioned above to the console when ADTPro starts so in the future I can just ask folks to paste in what the console says on startup. If I gain some confidence in the ability to test bitness on all platforms, I'll be able to put up a dialog box or even quit, complaining that the environment is incorrect.
  17. Is the pigtail you have today (the IDC-10 header to DB-25F) a standard issue for the SSC, or is it a PC-based one? Because they're different, and the PC-based one won't work. Apple doesn't need any more "all-praise Apple guy"s. My advice to you is just do what interests you. Sometimes hardware goes bad. Sometimes folks have bad luck. Spares help, but if you're not replacing the thing that is actually hindering progress, you're not going to progress. Right now, none of us knows exactly what that is in your situation.
  18. Does this mean that 2.0.1 still works for you, but 2.0.2 fails? You don't need JavaScript - you need Java. They are completely different languages. Can you provide the output of this command: java -version And also this command: wmic OS get OSArchitecture I'm concerned if you changed the level of your Java at the same time. Oracle does a bad job of deciding if you're 32-bit or 64-bit (or has in the past, anyway). So the thing to look for is the bit-width of your Java installation vs. the bit-width of your Windows 7 Pro installation (which could either be 32 or 64 bit).
  19. Older versions of ADTPro client for SOS did not catch an exception thrown when some connection states changed. That was fixed in 2.0.0.
  20. I'm worried about the gender changer too - unless you can verify it extends the pins one-for-one, I'd want it gone too. The pinouts are definitely not the same.
  21. No, he's got the jumper block set correctly if is frankencable his all straight through: http://adtpro.com/connectionsserial.html#Super_Serial_cabling But the problem is, he doesn't know what the pedigree of the pinouts are. Most importantly, how the handshaking wiring is configured - which is why the "//c with Imagewriter cable" suggestion is a good one. It will make different assumptions about how handshaking makes its way through the cabling. There's also an outside chance the USB-serial adapter is marginal, makes marginal connections, or has a bad driver. But we don't know any details about that either.
  22. Can't you boot from a floppy disk in the mean time? That's what you need to do. That is almost certainly not the case.
  23. ftp://ftp.apple.asimov.net/pub/apple_II/images/masters/prodos/ProDOS_2_4_1.dsk is the ProDOS you are looking for. ftp://ftp.apple.asimov.net/pub/apple_II/images/masters/prodos/Apple%20II%20System%20Utilities%20v3.2%20(ProDOS8%20v1.9%201990).dsk is a utilities disk.
  24. Simplest is probably just to use ProDOS utilities and format the volume. In terms of "installation," all you really need to do is copy the files from (say) a 2.4.1 disk.
×
×
  • Create New...