The guy who wrote the book the Power in Cakewalk Sonar has a video that gows over setting up faderport in detail

I feared the other day that something like that might have been the case however.... The faderport currently doesn't run in the 32 bit version of X2 either.  I will try again tomorrow.  
 
  I know everyone here is always ready to help and I really appreciated it a few years back as I was learning basic function/methods etc.  I haven't needed as much help (good lord I am not trying to sound cocky, as I know I have much more to learn....) in the past year or two and have found myself in the "happy to help" camp more often that the "guys please help me" camp far more often than not...  So it's easy to loose sight of how freaking great the members of our little forum are to each other.  It's a cool community and I am happy to be a part of it!

dubdisciple
The guy who wrote the book the Power in Cakewalk Sonar has a video that gows over setting up faderport in detail

I finally found that post and the video you mentioned above.  http://forum.cakewalk.com/Faderport-not-working-with-X1-Cannot-complete-regvrs32-m2935732.aspx  That guy "benduncan" was having the same exact problem and getting the same exact errors I am getting right now so this leaves me hopeful!  I will give it a shot in a little bit.  I will update later on my progress.  Thank you!

Update - With Some help from Chris over at ADK:
I have gone through and uninstalled the faderport, Started over, Ran the installer, copied the sonar x64 dll into the correct folder (c:\program files\cakewalk\shared surfaces) I then went into admin mode again and I finally got a successful registration! I was happy and thinking I was almost done.... I open Sonar X3 I go into devices and assign the faderport I/O, I then go under control surfaces.... and get everything assigned as required, Channel aftertouch/key aftertouch etc... The Fader port jumped to unity gain and lights came on & as though it was being feed by sonar (like it does when I open S1) and I was happy to see that. Then I open an existing project and Sonar goes grey..... Perpetually (thinking) trying to open the project. Any project (doesn't matter which), I have to then Control+alt+Delete and use the task manager to end sonar.... If I remove the faderport dll file from the c:\program files\cakewalk\shared surfaces directory I can then open sonar, and load any project in seconds and work straight away... but no faderport.... Put the DLL back..... Sonar won't load any projects, it just seems to lock up. Oh and at this point S1 isn't picking up the faderport anymore either.? Sonar see's it but is getting Fubar'd by it somehow and S1 no longer Sees it at all. Maybe a bad Dll file? or driver?
This thing is a monstrous PITA to get working in Sonar!  Giving yourself a root canal would be easier and more fun.  

Log entry, star-date .....
  Adam at ADK helped me out a ton because those boys are the bomb, and got my faderport up and running like a champ in X3 64 bit, x2 32bit, studio one etc. but no motorized fader at all now.
  Presonus support sent me the link to a page in their knowledge  base about the known issue of the most recent firmware taking out the motorized fader.  I down load and install the alternate firmware update and largely she is good to go, fader is back, and it all works as expected in most projects.
 
I have 1, a rather large project in Sonar containing around 31 or so tracks, a bunch of plugs, and existing automation etc. When I try to open this recently finished project (which I'll be honest ... it always takes sonar a minute or so to get that one open because of it's size) it starts to do it's typical load procedure, and the faderport starts jumping up and down to various seemingly random spots.... and this seems to go on indefinitely.... the track never opens, Sonar keeps on thinking away, and the faderport is going nuts but it doesn't open. I then have to Cntrl-Alt-Delete my way out of there after waiting 4-5 minutes for it to load in vain.
Is that typical behavior? IS the Faderport just reading information in the project before it opens? I have searched the knowledge base and forums and haven't found anything on it?
I then opened a small project with 3 or 4 tracks in it and noticed on start up the faderport hoped to about 4 spots as it opened so my suspicion is that it's trying to read through all that freaking automation first?