Socket on this CT63 allows the 060 to be placed in any position (didn't try to "seat it" though).
Noted on the underside of the CPU, near the "gold" square area a dot indicator.
This places the CPU same as on the CT60.
Unless seeing things, the CT63 photo (posted here) on Rodolphe's site shows the CPU Mask stencil toward the keyboard side of the CT
(grabs the photo), which is opposite the 4 CPU here.
Looking close at the photo, can see the "T1" CPU pin location at the bottom left corner of the socket/CPU.
Just used to seeing a corner blank on the socket where the "no pin" area of an IC goes.
But, now that I have your attention
Both the CT60 and 63 have been safely stored since purchased.
The CT60 installed and booted without incident.
The CT63 however did not boot.
Did a visual, the two are quite different without the F030 bus booster circuit and CT63 having the programmable clock, for that to be any indicatior to me.
Here's where we got to.
Placement and connections are the same as how the working CT60 set up is.
With the powersupply up, power indicator LED connected to the CT63 is lit.
When the momentary switch connected to the CT63 is depressed, nothing happens. Can hear the fan in the powersupply start.
The IDE drive does not spin up.
(concerned look occurs)
Rechecked connections, reseated SDRAM and tried again, same result.
Jumped the CT63 (off) for Falcon mode, IDE drive spins up and Falcon boots normally.
Remember reading through many CT post over time, recall one where either there was a missing resistor or cap on the (powerside?) CT63.
Does that ring any bells?
The Falcon does have the reset capacitor modification.
One contact on the SDRAM socket came a little buggered. Looks to be making contact. Rang it out, it's a ground contact, with continunity to the rest.
Also, can the programmable clock module be removed, or is it soldered in place? Don't want to force it.
If it comes out, will a "can" oscillator work in it's place?
TIA for the help
You do not have the required permissions to view the files attached to this post.