david__schmidt
-
Posts
163 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Gallery
Events
Store
Posts posted by david__schmidt
-
-
Never having owned an Apple II, I've got a few questions - what cards should I track down (or make sure it has already) to get this thing into the ideal game playing shape for its type? How can I figure out what RAM configuration it is? My understanding is that it maxes out at 64k of RAM with the language card in slot 0, though there are third party cards that go beyond that - is that the case, and do they work with the last batch of games that require that much memory?
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
-
-
Any chance or consideration of porting ADTpro over to something more well-received? Something other than Java? Java, to me, is a dotcom era language.
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.
-
1
-
-
I'm rather disappointed that ADT Pro for Windows doesn't work on 98SE.
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.
-
Maybe WAITING, or LISTENING, or something else would be more appropriate.
Perhaps "Ready." With a blinking block after. :-)
-
Well, clicking on the SERIAL button and the server responding with CONNECTED means it is connected to the Apple II and ready to roll.
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.
-
I tried old ADT for DOS and it didn't seem compatible with the ADT Pro disk I have for Apple //e.
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
Can you please tell me what the minimum Java version is needed for Win32 ADT Pro? I think the final Java update for Windows 2000 is Java 6 update 27, will that work?
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).
-
1
-
-
The audio transfer may be slow, but it's also awesome.
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.
Thanks so much for making this great utility!
Sure thing. I made it because I wanted it. I'm happy others find it useful.
-
1
-
-
Maybe changing it to say Serial Port Open or something like that would be more appropriate.
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.
-
1
-
-
I can't get ADTPro working on Windows 98SE, something about Java being out of date. Anyone here know if Windows 2000 will work?
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:
-
1
-
-
here is the challenged. If you already knew how to make transfer ProFile 5 Mb ( SOS format) on Apple /// from my PC to my Apple /// ? Because I do NOT know how to installing complex SOS system on ProFile alone. It would be much easier to transfer ready disk image 5 Mb SOS format ready with ready system and software. Will it works ?
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.)
-
Now that ADT is pretty well seasoned and all, have you thought about developing some diagnostics to help newcomers narrow down problems? Cable/connectivity tests and maybe other stuff I'm too lazy to think about right now.
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.
-
I can't understand why it would say connected if it didn't think it was working.
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.
-
What's your conversion pinout from 25-pin to 9-pin?
-
I looked at the batch file that starts it on the PC but I haven't tried typing the launch command directly.
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!
-
1
-
-
Yeah, I ran into the Oracle 32 vs 64 bit issue myself.
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.
-
perhaps I need a custom 25-pin SSC to 9-pin serial converter, or the card is partly toast.
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.
(No, I'm not yet a converted all-praise Apple guy, quite far from it to be honest but I will want to give it a fair try as far as possible)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.
-
I recently download your newest version 2.0.2 instead of 2.0.1
It seems not work. I believe I downloaded a newest version of Java Script.
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).
-
I tried to use It with my Apple III this afternoon. I dies without giving an error when I try to connect,
*edit*
I think it's an uncaught exception.
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.
-
But I'll try to wire my own DE9F-DB25F adapter to eliminate at least one of the unknown cables, and keep the gender changer.
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.
Actually I'm wondering if I can remove the 2x5 pin IDC cable that ends with a DB25F from the SSC, and instead put a 2x5 pin IDC cable from a newer PC that has a DE9M instead, if the two tend to have the same pinout to the board.
The pinouts are definitely not the same.
-
I believe you need a null modem adapter in the chain somewhere and you currently don't.
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.
-
Sigh. I thought this was supposed to be easy. Perhaps the problem is that I'm using an Apple clone that has its own, unaccessible serial port, or that my cable has too many unknown parameters and I'd be better off soldering my own DB25M - DB9F cable that I know for sure is correctly wired.
It's your wiring.
-
I already have that. But it's just a disk image and I need to boot the real hardware.
I had been running off of the CFFA.
Can't you boot from a floppy disk in the mean time? That's what you need to do.
The problem may be that the CF card is damaged.That is almost certainly not the case.
-
ftp://ftp.apple.asimov.net/pub/apple_II/images/masters/prodos/ProDOS_2_4_1.dsk
is the ProDOS you are looking for.
is a utilities disk.
-
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.
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Looking for Retro Game Programming Tutorials
in Apple II Computers
Posted
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: