Stuck on loading ADTPro - failing IIc memory chip(s)

[ThoRenn]

Hi, young retro tech enthusiast here.
Recently found myself a barebones IIc and am trying to get it operational.

I have wired a null-modem cable myself but find myself stuck on the bootstrapping process.
Using the windows version, I tried Speediboot first; It seems to get stuck on 'loading ADTPRO'
Then I tried the older scheme; Sending ProDOS works, sending ADTPro gets stuck at the end. The application tells me the file has been sent but my IIc does not boot up ADTPro.

Any help is appreciated!

[david-schmidt]

Welcome to the journey - this project is aimed squarely at you.

So the inability to start after sending the ADTPro payload could mean the last byte isn't received; you might try the older scheme again, and after you witness it hang, hit ctrl-reset (don't reboot, just reset) and then see if you can start it manually:

]CALL 2048

It could also mean that all of your memory isn't up to snuff; a self-test would help, but they're not great on early IIc models. Chicken-and-egg situation here; lots of great diagnostics are available on disk. :-/

Have you tried any of the other booting options to see if the machine is operational overall - like booting DOS and sending just ADT? Or speedibooting to vsdrive?

[ThoRenn]

Thanks for the swift response!

I tried the older scheme again, and it seems to do the same thing. One exception is that after a second time the red disk light turned on and made some noise. This kept going until I hit ctrl-reset. (I assume it's trying to read a disk?)

After hitting ctrl-reset I tried ]CALL 2048 (although instead of the BASIC ']' prompt I got a '*' prompt?)
It resulted in a bunch of characters, similar to sending ADTPro from the software, but other than that no action.

Regarding your last option; I rebooted, tried sending just ADTPro Serial Client. (if this is what you meant?) It seems to yield about the same result as before. (bunch of text, hangs afterwards)
Tried VSDrive + Speediboot; Not sure what the result of this should be, but this seems to end on a rather cryptic line starting with "100C-", giving me the * prompt afterwards.
Other bootstrapping options besides ProDOS I have not touched yet as I'm unsure of what they do.

As you can tell I'm not very knowledgeable about this yet, so I'd like to learn more. Could any screenshots be of help?

[david-schmidt]

Ok, I think what might be happening is that ADTPro is actually starting up, but it's hanging on trying to send a "hello" packet out your null modem. You might try ticking the "Apple IIc with Imagewriter cable" box on the serial communications dialog box under the "Port" tab. The VSDrive situation should end up with a BASIC prompt, so that doesn't sound like it's working for you either:
https://adtpro.com/bootstrap.html#Starting_with_Virtual_Serial_Drive

For the simpler download situation - this is what I mean:
https://adtpro.com/bootstrap.html#Bootstrapping_DOS

[ThoRenn]

Hi, sorry for the super late reply, had my hands full.
I'm currently stuck on the simpler download situation, sending EsDOS part 1: After sucessfully sending part 1 and trying to format a disk using "INIT HELLO" (like my apple told me to) I get an awkward syntax error, but one I can't seem to figure out nonetheless..

[david-schmidt]

A little video showing the details of what you're doing might reveal some clues. "Awkward syntax error" specifics are significant; it could be code didn't transfer successfully, or it could be a hardware problem, or maybe you're trying to format high density floppies..

[ThoRenn]

As you might've noticed, it took very long to get my hands on the right floppies, my apologies and thank you for the wait.
While I believe what I had before were also double density, double sided, they were unmarked so I'm unsure.
That being said: I now have some clearly marked DD/DD floppies, but they produce the same result.

[david-schmidt]

On the first line where you got the syntax error from INIT HELLO, that could be because there was a stray control character on the line. Another attempt at INIT HELLO on a new line could help. Neither "NIT" nor "INIT" are valid commands, so those responses are reasonable. Try another INIT HELLO on a clean line here.

[ThoRenn]

As you can see on the image, the 1st INIT HELLO didn't return anything. The attempts after that are met with SYNTAX ERROR.
I also tried rebooting the floppy using PR#6 in the hopes the first line did do something, but to no luck.
A 2nd attempt yields me the same results, except for the 1st line also giving a syntax error.

[david-schmidt]

Ok, let's back up and look at "DISK ERROR: NDC". If you turn your Apple II off and back on again, does the floppy drive try to boot (it should give a rattling or possibly a chugga-chugga noise) and spin for a bit. Does it?

[ThoRenn]

When turning on the Apple IIc, the floppy drive makes a sort of clattering noise, the red disk indicator turns on and I believe i hear it it spin for a bit. After a few seconds the red indicator turns off and the sounds also cease. The screen also shows a header text 'Apple //c' and a footer 'Check Disk Drive.'
The same thing occurs when a floppy is in the drive.

[david-schmidt]

Ok, perfect - the drive is up and running. So if you do that and then hit reset to get to the "]" prompt, what happens when you do a "PR#6" ?

[ThoRenn]

When typing PR#6 in the ] prompt after hitting CTRL+RESET (reset alone didn't do anything), it repeats the same disk-reading cycle as on booting the device.
I also get the message 'Check Disk Drive' again.

[david-schmidt]

Ok, I don't suspect there is any problem with the drive and controller, then. I'm back to suspecting your memory. Let's start with the built-in system test. From google:

1. Power on your Apple IIc.
2. Hold down the Open-Apple and Closed-Apple keys simultaneously during power-up or a warm reset (Ctrl + Open-Apple + Closed-Apple + Reset).
3. For most ROM versions (except the very first ROM 255), a checkerboard pattern will appear, and the screen should display "System OK" after about 34 seconds if the basic memory and soft switches are working.

If that doesn't work or is inconclusive, there is a type-in memory test for the normal user area of memory (takes many minutes to run):

10 HIMEM: 4096
20 S = S - 1:R = RND (S)
30 PRINT "FILLING MEMORY WITH PSEUDORANDOM BYTES"
40 FOR A = 4096 TO 49151: POKE A,256 * RND (1): NEXT A
50 PRINT "READING AND COMPARING MEMORY"
60 R = RND (S)
70 FOR A = 4096 TO 49151: R = ABS ( PEEK (A) - INT (256 * RND (1)))
80 IF R = 0 THEN NEXT A: GOTO 20
90 PRINT "BIT MISMATCH ";
100 FOR B = 7 TO 0 STEP -1
110 PRINT INT (R / (2 ^ B)); CHR$ (32);

[david-schmidt]

[ThoRenn]

The built-in system test does show a checkerboard-like pattern that shifts a bit every so often, but it seems to be running forever. At least, it surely isn't done within 34 seconds.
Is it safe to power off while this test is running?

Also, how do I run the type-in memory test?