Anyone using X3 or X2 and a Faderport?

This was one of my Christmas gifts from my wife I wonder how she knew I wanted it!?  haha
In any case, I got it hooked up and ran the installer, it works fine in S1, the problem is S1 so far just pisses me off as a DAW (we'll save that for another thread sometime)
I want to use this cool new toy in Sonar but sonar does not recognize the Faderport.  That is to say it does not show up in the drop down list to choose it as a controller.  I have done the research 1st and found the issue & the subsequent fix I found was that you had to copy the faderport.dll into C:\program files (x86)\cakewalk\shared surfaces  then run a windows command prompt to register that by typing:
regsvr32 C:\program files (x86)\cakewalk\shared surfaces\FaderPort.dll
 
All over online I can find people who had this problem , did this procedure and it fixed it for them.... I have no such luck.
I get the error//response/message  * The module "C:\program files (x86)\cakewalk\shared surfaces\FaderPort.dll" was loaded but the entry-point DllregisterServer was not found.   Make sure that "C:\program files (x86)\cakewalk\shared surfaces\FaderPort.dll" is a valid dll or OCX and then try again.
 
Any ideas guys?  I am lost at this point and don't want to keep poking around in admin mode and mess something up.
 

 
works perfectly but a little tricky to install....follow these instructions using latest driver (in any version of sonar)
 
http://www.sweetwater.com...t-to-work-in-sonar-x1/

I had a similar problem that I couldn't fix until I enclosed the file location completely in double quotes.
regsvr32 "C:\Program................ \faderport.dll"

Looks like you're either registering the 32 version of the faderport dll if you're trying to register C:\program files (x86)\cakewalk\shared surfaces or you're placing the 64 bit version into the wrong directory. The right folder for Sonar x64 should be C:\program files\cakewalk\shared surfaces.
FWIW, faderport works great here under both x86 and x64 versions of Sonar X3d but I had to hack the one of the dll's to get it to work in both, before hacking it, it would only work in one or the other because both versions of the dll are named the same thing.

SuperG
Also, just to be sure, you indicate you're using the 32-bit version of Sonar by virtue of the sharedsurfaces directory location.

I thought (see I am soooo not a tech guy when it comes to computers)  the x86 denoted 64 bit (which I never understood anyway) and that the 32 bit was under the general file.?  For instance
64 bit = c:\Program files (x86)\cakewalk\ yada yada.....
32 bit = c:\Program files\cakewalk\ yada yada....
Right?  or are you telling me I have that backwards? 
 
to that end.... where we have to type regsvr32....  Does that need to be regsvr64 or regsvr86 for the 64 bit version?   I at this point have no intention of even loading the 32 bit version of X3 on my computer at all.
 
PS.  this forum rocks and you guys are awesome!  ...Just so you know.  Thank you all.

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

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!

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?