Fixed Problem with Installation and usage of 32bit SST in VISTA!!!

[deifier]

Download d3drm.dll and place it in your C:\Windows\System32 catalog and then install joydrivers followed by your identical SST Programming 32bit XP drivers (note I restarted computer btw placing the missing dll file and installing the software, don't know if it's needed)

P.S the self-registation faliure of SAI3DVIEWER.dll shouldn't appear if it works, as it did for me :D

/Regards Deifier

,sorry for posting another thread but I thought it was needed, it's a big issue for some this problem.

Since seemingly this poster is more viewed since I screwed the 64 one up in the begining I just wanted everyone watching this one to know that the 64bit is fixed aswell :D CHEERS!

/Regards Deifier

[skylaw]

where do you find thoses files? and what about 64bit?

[deifier]

http://www.dlldump.com/download-dll-files_new.php/dllfiles/D/d3drm.dll/5.1.2600.0/download.html

This is the .dll file you place in you c:\windows\system32

Restart computer and then install the SST Programming 32bit Software for XP along with the identical Joystick 32bit XP Drivers. Found here on Saitek under drivers for XP.

Problem with file requests/self-registration during installation and crash during using the software (aka the click and crash) will now be gone.

As for the 64-bit Version haven't installed 64-bit OS on any of my computers because I'm using a music production software that doesn't support 64-bit yet, so I need to keep to 32-bit for a bit longer. Sorry. How ever if someone can't solve this issue I'm more then glad to install 64-bit OS and give a shot at solving the problem.

[CoNa]

Tried this fix, but it did not work for me :(
I'm not able to upload any profiles on my x52.

[deifier]

So what happens when you try to upload your Profile ? Upload as in load a profile or upload as upload to the internet ?

I've got 10 Profiles for diffrent games. I've edited them, swapped btw them and used em' and it works just fine for me. However this is just a temporary solution I've come up with that worked for me and I wanted everyone to have a shot at it working for them until Saitek solves the real issue and updates the original software needed.

So sorry for it not working out for you :(

Tip read through error message thorough when it appears and find a solution. That's what I did... It was a 1 minute figure :P

[CoNa]

It's when I try do upload an allready existing profile through the profiler to the x52 I get this message:

Lomac F15.dat does not contain a profile for this device.
The device has not been profiled.

I get the same error when using the clutch.

It was worth a try if it would get me flying again this weekend.
your effort is greatly appceriated.
Any ideas on what I'm doing wrong ?

[UKSupport]

It sounds like you're trying to use the Vista drivers with the old SST software and this won't work. I believe deifier is using the XP drivers and software.

[skylaw]

The users on this forum brings more solutions to problems then saitek... how queer!!!

[CoNa]

It sounds like you're trying to use the Vista drivers with the old SST software and this won't work. I believe deifier is using the XP drivers and software.

OK, that would possibly explain it.
Going to give it a second shot tomorrow.
Will let you know the outcome.

[Insidian]

Sweet man, works great for me. Now, where can I get some good profiles? I need one for IL2 1946 and Pacific fighters standalone.

[psxwizz]

Worked for me great with my PGCU, For some reason i had to install the drivers twice, then it worked fine, Great fix, Shame saiteks programmers are asleep, otherwise they could have given us this quick fix ages ago.
Thanks :)

[grosboeuf]

works perferctly!
thanks a lot!
:D
(and shame on saitek!)

[sboub22]

Deifier,

I don't know how you came with this workaround, but it works perfectly.
This should be sticky or something, at least while we're still waiting for SST for vista. Thank you, I can use my PGCU :p

[keyfreak44]

It didn't work for me:( I could get the profiler to come up, could rotate in 3d view my gamers keyboard gamepad, and could programe it and everything. When I would click on the profile for the game I wanted it would just give me the error: BF2142dat.does not contain a profile for this device
The device has not been profiled.

I tried the Total Game Control software mentioned in another thread and it works and the latest build of it is from Sept.05!!!

It is my firm belief that after the final version of Vista has been out for 2 months there should be sst compatible software by now. Theres nothing for them to gain by putting the effort into updating software for saitek controllers you already own. So their solution is to come out with the vista compatible software,logos, etc. with their next line of controllers. That way they can cash in on the effort that goes into programing Vista compatible software. Hoping you'll ditch what you've already puchased and buy new.

Thats what I think all these vendors are doing Nvidia, Saitek, ATI, etc. They all want Vista to be their next 'Cash Cow' so their vista software coinsides with their latest hardware. They don't want to pay a programmer to re-programe software for old hardware.

[grosboeuf]

did u use xp SST AND XP drivers? the message u're getting is when using vista drivers with XP SST

[cehoyjt]

So what happens when you try to upload your Profile ? Upload as in load a profile or upload as upload to the internet ?

I've got 10 Profiles for diffrent games. I've edited them, swapped btw them and used em' and it works just fine for me. However this is just a temporary solution I've come up with that worked for me and I wanted everyone to have a shot at it working for them until Saitek solves the real issue and updates the original software needed.

So sorry for it not working out for you :(

Tip read through error message thorough when it appears and find a solution. That's what I did... It was a 1 minute figure :P

May I just say that you are the man. You should be collecting money from Saitek for fixing their problem.

[keyfreak44]

Got it working! It was the vista driver/xp sst driver conflict. What happened is after I read this post I deleted the keyboard and everything rebooted and put my original install disk in that came with the keyboard, and it would not install the drivers for some reason iI kept getting an error and so I just went back to the vista drivers.

So I deleted everything again only this time I used winxp drivers and software downloaded from this site then it worked.

[Stanger]

No go For Vist 64 bit. Dang

[UKSupport]

It is my firm belief that after the final version of Vista has been out for 2 months there should be sst compatible software by now. Theres nothing for them to gain by putting the effort into updating software for saitek controllers you already own. So their solution is to come out with the vista compatible software,logos, etc. with their next line of controllers. That way they can cash in on the effort that goes into programing Vista compatible software. Hoping you'll ditch what you've already puchased and buy new.

Thats what I think all these vendors are doing Nvidia, Saitek, ATI, etc. They all want Vista to be their next 'Cash Cow' so their vista software coinsides with their latest hardware. They don't want to pay a programmer to re-programe software for old hardware.

Hi,

Well that's a nice conspiracy theory but that's all it is I'm afraid. There's everything for us to gain by making sure that existing owners of hardware are supported - if you suddenly cut off your customer base then you will be left without a business.

We're going further than any other gaming peripheral manufacturer to support older products. Logitech, for instance, introduced a hard "3 year" rule where anything older than that will not be receiving Vista support and they've clearly stated that they won't have programming software for those products that are supported until June. When our software is released there will be products supported in there that are 5 years old.

Just to also stand up for nVidia and Ati who you mention there, they both had drivers available for Vista before launch. Yes, they weren't perfect but they've made efforts since then to ensure that owners of existing hardware are supported (in Ati's case that's all they have got as they still haven't released their DX10 cards).

As I've mentioned elsewhere on the forum, the software would have been available today but a large part of the software team is off ill thanks to this nasty 'flu virus that's still going round. As soon as we have some more of the team back in work we'll be able to get an idea of the new potential release date and I will of course let you all know.

[MoonDoggie]

Going to try and use this technique to get me up and running, certainly hope it works!

[mrm0508]

SWEET...Nice Job, works great for me.

[schubring]

Clever Consumer 1 Saitek Team 0

[MoonDoggie]

Works great! just like you said

[AgtSmith]

Hi,

Well that's a nice conspiracy theory but that's all it is I'm afraid. There's everything for us to gain by making sure that existing owners of hardware are supported - if you suddenly cut off your customer base then you will be left without a business.

We're going further than any other gaming peripheral manufacturer to support older products. Logitech, for instance, introduced a hard "3 year" rule where anything older than that will not be receiving Vista support and they've clearly stated that they won't have programming software for those products that are supported until June. When our software is released there will be products supported in there that are 5 years old.

Just to also stand up for nVidia and Ati who you mention there, they both had drivers available for Vista before launch. Yes, they weren't perfect but they've made efforts since then to ensure that owners of existing hardware are supported (in Ati's case that's all they have got as they still haven't released their DX10 cards).

As I've mentioned elsewhere on the forum, the software would have been available today but a large part of the software team is off ill thanks to this nasty 'flu virus that's still going round. As soon as we have some more of the team back in work we'll be able to get an idea of the new potential release date and I will of course let you all know.

Problem with your well stated comments on this is that it is not any different than how Saitek bungled XP so many years ago. It was due the January just after release that become March then it was summer than it was on and on and in the end allot of months (I think a year) before it was out. You guys should have known then to be ready, you should have respected your customers enough to get started early enough to be done. When you fouled it up and took a bunch of heat you should have definitely figured that for Vista an early start with plenty of resources was called for but you again didn't do that and again it is the missed dates and screwed customers.

I don't think it is a conspiracy as the one guy suggests (although many companies are clearly prioritizing new stuff over old) it is just the result of a company that by its actions shows it has little respect for its obligation to support its customers.

The flu excuse is just that, an excuse - had Saitek taken their customers loyalty and purchasing choices seriously and truly appreciated them they would have committed enough resources to this early enough so that a flu bug breaking out 3 months AFTER the deadline of when it should have been done would not cause a delay. The only alternative to this is that Saitek does take us seriously and respect and appreciate us but they have a staff on the job that is so incompetent as to have been given the resources (time, personnel, etc) but they botched it anyways. Only one of the above two scenarios is the case - it wasn't important enough to commit the proper resources or Saitek simply has morons working for them - neither is a good reason to continue purchasing Saitek products.

Just FYI - I have no doubt the people at Saitek working on this are dedicated and probably quite competent - perhaps even brilliant. I am not calling the Saitek SST team any names. But it is an either or scenario in so far as either talented people didn't get the resources that where needed or the needed resources and commitment where in place but incompetents fouled it up.

Either way - the entity to hold accountable is Saitek and as neither of the possible scenarios bode well in terms of supporting Saitek the choice is clear to me. You guys should have learned your lesson with XP, this time around with Vista there is just no excuse, no acceptable one anyways.

P.S. i will give Saitek points for one thing - having a guy on these boards to deal with community issues is a good move and they seem to have a good guy here in 'UK Support'. Unfortunately, good soft support doesn't make up for horrid hard support.

[MarioV]

All very good points AgtSmith... Saitek had months to develop the SST software for Vista. I believe Microsoft released Vista to software developers and hardware manufacturers in November. I own four Saitek Cyborg Evo joysticks and two Logitech Extreme 3D Pro joysticks, for my LAN parties, and I may rethink from whom I am going to purchase my replacements. That fix mentioned in this thread does not work for my Cyborg Evo.

The UK Support stated that Logitech will not release their programming software until June, but when I checked the Logitech website for their Vista downlaods, it's already up there.

And AgtSmith, you stated that Saitek should have been ready for the Vista release based on their XP debacle... XP came out over five years ago... how many of those programmers do you think are still on their payroll?

Anyone up for bets when this thing will finally post for downloading? With that flu outbreak, I'm shooting for June.

[99nomad]

I did waht you said and it did not work for me, I can see the SSt program in my programs list but it will not launch. Any ideas?

I already had the X45 drivers installed and did not know how to remove them so I just downloaded and installed the XP drivers I asume it installed the drivers over the existing copy.

[MoonDoggie]

While this fix does work if you follow his directions, it does not give you too much flexibility with the Pro Gamer Command Unit, working fix, but not 100%, I appreciate you figuring it out, but I'll still be waiting for the SST drivers to get the most out of my unit.

-Colin

[Khenke]

Thank you VERY much, I can finaly use my command unit after owning it for almost 4 month...

Shame on you Saitek for not fixing this. This will probably be the last time I buy a Saitek produkt.

[BenHur74]

I did waht you said and it did not work for me, I can see the SSt program in my programs list but it will not launch. Any ideas?

I already had the X45 drivers installed and did not know how to remove them so I just downloaded and installed the XP drivers I asume it installed the drivers over the existing copy.

I have the X52 controller with Vista 32 Ultimate. I´ve installed the Vista Drivers for X52 first...now i´ve got the same problem. I uninstalled the vista drivers via Hardware Device Manager. Then i installed the xp drivers with sst (this one: sst_151205_32.exe). Now SST don´t launch for me and the pop up says: no saitek controller plugged!?! Also, the led of the throttle controller doesn´t work. I´ve tried it several times with the vista and xp drivers. But SST isn´t working for me. Maybe there are some vista drivers rest in the registry? Is this the correct install "sst_151205_32.exe" for vista sst?
Please help, ms flight sim x is waiting for me...

Thanks, BenHur.

[LARSA]

My Pro Gamer Command Unit works for me in 32 bit Vista using the XP driver pgcu_151205_32.exe (ftp://ftp.saitek.com/pub/software/pgcu/pgcu_151205_32.exe) and XP SST sst_151205_32.exe (ftp://ftp.saitek.com/pub/software/sst_151205_32.exe).
Combined with the d3drm.dll (http://www.dlldump.com/download-dll-files_new.php/dllfiles/D/d3drm.dll/5.1.2600.0/download.html) in the system32 folder.
Just put the d3drm.dll in the system32 folder. Then reboot and install the drivers and SST.

[potskomtar]

Hi , I use the vista x64 driver and XPx64 SST ,i put d3drm.dll in \windows\system32 , installed the vistax64 drivers ,tryed to install xp x64 sst ... when i see the window about "this program only works on XP64" i find in \windows\temp\saitek\saitek_blablabla_software\000 00015\installshield\setup.exe (run this , not the setup.exe in parent directory) , e voila... it works.

Sorry for bad english , bye.

[Paul_Yorks]

Has anyone got this fix working with a X52 Pro?

I can't. I get the same message re: no profile, as mentioned above. That is after uninstalling the Vista driver, then installing XP driver & SST software (with the dll in the system32 folder). The 3d model works, and I can even edit a profile - but the stick won't work with one.

Ho hum. Looks like we'll get Vista SST soon, so patience is probably the best way.

[project6]

I'm afraid it wont be released in another, say, two weeks... According to latest post they just entered the transition phase, testing and fixing bugs... It's usually quite timeconsuming, but on the other hand they probably have much fixed already since it's only an update of current software... I still think it will take about another week at least. It's great that people with driverskills hop in and ease things up for the rest of us.

Just bought my PGCU and I'm gonna try the 64-fix while waiting, cause the usability of it without SST software equals zero.

Edit: The above fix works to install the SST software, it does not however work when I try to apply a profile I made. I get a message telling me the file doesn't contain a profile for this device. *snap* so close ;)

[ThomasE66]

I'm afraid it wont be released in another, say, two weeks... According to latest post they just entered the transition phase, testing and fixing bugs... It's usually quite timeconsuming, but on the other hand they probably have much fixed already since it's only an update of current software... I still think it will take about another week at least. It's great that people with driverskills hop in and ease things up for the rest of us.

Just bought my PGCU and I'm gonna try the 64-fix while waiting, cause the usability of it without SST software equals zero.

Edit: The above fix works to install the SST software, it does not however work when I try to apply a profile I made. I get a message telling me the file doesn't contain a profile for this device. *snap* so close ;)

It's not an update, it's a complete rewrite which is why it's taking so long. Testing may take longer due to this fact, but only they know for sure.

[BeerOnIce]

I can't. I get the same message re: no profile, as mentioned above. That is after uninstalling the Vista driver, then installing XP driver & SST software (with the dll in the system32 folder).

The 3d model works, and I can even edit a profile - but the stick won't work with one.

I have PGCU and Cyborg evo and can not get them to work on the 64-fix

Edit: The above fix works to install the SST software, it does not however work when I try to apply a profile I made. I get a message telling me the file doesn't contain a profile for this device. *snap* so close

[project6]

I'm curious if potskomtar actually got it ALL working, even the applying-profile part? If anyone can get that part to work on Vista x64 please post how here.

[UKSupport]

I'll be very surprised if he did get it working. Vista 64 is the real sticking point with all of this as it absolutely requires signed drivers and has a bunch of other restrictions that make developing for it really nasty sometimes. Or to put it another way, for our software team the phrase "Vista 64" is becoming almost as much of a dirty phrase as "Windows ME" :D

[deifier]

Seemingly my 3-5 minute solution for the problem with SST Prog. in Vista 32 wasn't enough. Now I've been challenged to do the same for Vista 64

I humbly except your challange. All though I still haven't figured out which comp to reinstall Vista 64-bit on so I can get started.

This will be how I figure it out :confused: :eek: :cool:

Get back to you guys if I'm dumb (with no solution) or if I'm smart (then with the solution to the problem)

/Regards Deifier

[Shamrock_Don]

Deifier -- Thank you so much for this. Worked like a charm on my Dell XPS laptop with Vista Home Premium.

[project6]

I'm holding my breath, and thumbs, for you Deifier. I tried around myself a bit with this since I have Vista x64, and managed to install an older SST version, however the profiles can't be applied once you're done with em. I think the problem is in the .dat files that are created, so I've been editing them a bit as well... No solution though, so far.

If you need anything I'll gladly help out, I'm checking this forum a few times every day. Good luck, and may the force be with you.

Edit: There's a software availible called Total Game Control that works OK with Pro Gamer Control Unit, in 'blue' mode. The only fallback with it is you can't save your profiles (which means you have to re-configure every time) and the Shift key is not recognized by the software. It's still a good way to try out the feel of your gamepad if you (like me) only used it as a paperweight/dustcollector so far.

[IST_KeleSSaR]

sorry for my english is to bad , i am spanish....i am user vista 64 and pro comander unit i have istalled in my cp drivers vista 64 and i have installed this program in my cp .really it,s works!!!but i don,t save my profile because is a trial version :( :(


sorry for my english


bye

[project6]

sorry for my english is to bad , i am spanish....i am user vista 64 and pro comander unit i have istalled in my cp drivers vista 64 and i have installed this program in my cp .really it,s works!!!but i don,t save my profile because is a trial version :( :(


sorry for my english


bye

Yeah, Total Game Control works, just as I stated above. A friend has a license for the software, and we tried with it on Vista and the profiles don't save there either. So it's a no go if you want to use it effectivly. Works to test the controller tho, and play around with it a bit...

[_VR_Melcron]

Ok,

First thanks for all the pointers. I managed to get X-52 working and SST profiler working using the XP 32 driver and XP 32 SST.. Had to make sure that i dumped all ref to the vista 32 driver and Vista 32 SST everywhere and reboot to make sure. Also made sure saitek folder was deleted...

So i installed the XP stuff even though i am running Vista 32 home premium with a X-52 attached.

The profiler worked in all aspects..
created file
saved file
and most importantly the file ran....and i flew 1946 with the stick
WOW....lol..
Did not happen on first attempt.
Took several tries to make sure all ref to Vista drivers was Purged.

Should not have to try this hard to get a product to function however being a telecoms engineer of several years i have totally given up on anyone releasing a product that is not bugged in some way... ;)

HOWEVER... I still trust that a vista fix is just around the corner...

2nd HOWEVER. One bug that is most probably driver/me being an idiot. related. Can anyone help.

With any driver XP/vista 32 installed. The control section when activated shows movement on the throttle and and all buttons correctly. 'But' when i run my sim the throttle control does nothing. 'I mean nothing' the slider on the top of that module with the volume inc/decr type logo acts as a throttle. I am really hoping that this is just because i'm using the XP ddrivers / sst etc... and when we all get a vista fix this will be cured.. But my gut feeling says i've got some sort of conflict because a throttle is a throttle is a throttle and should always work............

Sorry for the extended rant.. Can anyone check my sanity on the throttle thing though. Ok flu break over Saitek techie/dev team back to work please... ;)

Cheers 'Hic'

Melcron


Almost forgot .. Yup i added the DLL file as instructed after searcing for it on the net...

[BEWARRE]

Hello all,

Does anyone know where I can find this file? SAI3DVIEWER.dll it is specified as a missing module during installation of the SST for Vista-64 bit? After much toiling I found the drivers and SST for Hasta La' "Vista-64". SST starts up, but I get no 3D view and all profile files display as blank sheets in the software file. They load into the SST, but no 3D view, the key commands on the right are displayed, but they can't be modified worst of all X52 crashes when a profile is selected as stated in other's post. I'm still grounded :( Any assistance would be greatly appreciated.

Regards,
BEWARRE[/B][/B]

[UKSupport]

As I mentioned above, you won't have any luck with Vista 64, I'm afraid.

@Melcron - Which sim are you running where you have the problem with the throttle not working?

[project6]

After much toiling I found the drivers and SST for Hasta La' "Vista-64".

Uhm, where did you find the SST for Vista64? It aint out yet.

[_VR_Melcron]

~S~

Ok yup figured out the throttle issue... Twas me and my stupidity.. So just waiting on SST now...;)

[Oskitz]

I tryed to follow advices from this topic, but my Pro Gamer still dont want to save/loads profiles in Vista-32. :\

[Devastador]

THX THX deifier!!!! work very very fine in Windows Vista!!!!:D

Although it is certain that there is to have the game to driver and correct SST so that works. Mine they are:

sst_151205_32.exe
x52_151205_32.exe

THX Again! Deifier!!! for your work!!!;)

[Adamski]

THX THX deifier!!!! work very very fine in Windows Vista!!!!:D

Although it is certain that there is to have the game to driver and correct SST so that works. Mine they are:

sst_151205_32.exe
x52_151205_32.exe

THX Again! Deifier!!! for your work!!!;)

I'm intrigued - I couldn't get this pair to work :(

Did you install/run them with any XP compatibility settings - or just straight in?

Thnx,
Adamski.

[Devastador]

Adamski greetings! the installation method is very simple:

First you install driver x52_151205_32.exe

Soon you install the soft sst_151205_32.exe

And soon you place the file d3drm.dll in

c-->windows-->system32 restart and but gives no error you loaded the profile correctly that you wish

I do not use at any moment the way of compatibility for win XP

GL

PD: I hope to have been able to be of aid

[Adamski]

Adamski greetings! the installation method is very simple:

First you install driver x52_151205_32.exe

Soon you install the soft sst_151205_32.exe

And soon you place the file d3drm.dll in

c-->windows-->system32 restart and but gives no error you loaded the profile correctly that you wish

I do not use at any moment the way of compatibility for win XP

GL

PD: I hope to have been able to be of aid

Thanks, Devastador ... but still no go with me :(

The 3D thing works - I can define keys, load & save profiles to HD, but can't actually download to the X52. Unprogrammed, the X52 works fine - the Control Panel calibrates as usual.

Are you running as administrator? My default login isn't admin, but I have full rights - I just have to OK things before they run. I wonder if that's the problem.

Thnx,

Adam(ski).

[Adamski]

Adamski greetings! the installation method is very simple:

First you install driver x52_151205_32.exe

Soon you install the soft sst_151205_32.exe

And soon you place the file d3drm.dll in

c-->windows-->system32 restart and but gives no error you loaded the profile correctly that you wish

I do not use at any moment the way of compatibility for win XP

GL

PD: I hope to have been able to be of aid

Devastador .. you're a STAR!!! ;) :cool: :D

It *does* work!! For the benefit of others, here's what I did (I'd already copied over the d3drm.dll file) :

1) Disable the control account security thing in Vista. Not sure whether this is necessary, but I wondered whether the drivers were installing properly. Anyway - make sure you're logged in as administrator.

2) Unplug the X52. In Device Manager, remove the entries for the Saitek devices - including the Magic Bus - and choose to uninstall the drivers as well.

3) Delete any Saitek related stuff in Windows/temp and any redundant installs of SST in Program Files.

4) Run the driver install: x52_151205_32.exe (no compatibility set for any/all users). Plug in the X52 when prompted and check all OK.

5) Run sst_151205_32.exe - with no compatibility defined.

I suspect the problems occur because of previous [failed] driver installs - it appears that actually uninstalling them may be what's needed.

My system is Vista Home Premium, 32-bit.

YAY!!!!!!!!!!!

Adamski.

[gporto]

Was wondering if anyone can help. Hopefully, I'm just doing something wrong.

I successfully moved to dll to windows/system32 and re-installed the XP drivers under Vista. Then I used the SST software to successfully download the profile. Everything looks great!

When I go into Flight Simulator X, the assignments aren't recognized. Just the basic buttons work.

Any ideas?

[Adamski]

Was wondering if anyone can help. Hopefully, I'm just doing something wrong.

I successfully moved to dll to windows/system32 and re-installed the XP drivers under Vista. Then I used the SST software to successfully download the profile. Everything looks great!

When I go into Flight Simulator X, the assignments aren't recognized. Just the basic buttons work.

Any ideas?

Does the taskbar Profile icon turn green? Does the profile name show on the MFD? Does the X52 generate keypresses in something like Notepad (for example?). If yes to all those, then the problem must be in FSX :-(

Adamski.

[katoman1932]

I tried your "fix" and it worked PERFECTLY. I run Vista Ultimate 32 bit. I can now fly the fighthing skies once again thanks to your genius.

If you ever get into Chambersburg, PA USA I will be pleased to feat you at our favorite local watering hole.

Gratefully,
Dick Brown

[Adamski]

I tried your "fix" and it worked PERFECTLY.

Good news, Dick! All credit to Devastador - he's the one that got "the fix" working in the first place ;) - I just documented what I did as I went - though I must admit I wasn't very hopeful. I'm as delighted as you are to have it working.

If you ever get into Chambersburg, PA USA I will be pleased to feat you at our favorite local watering hole.

That's a helluva bus ride from Auckland NZ - so I'll raise a "virtual" glass to you instead :p

I think I'll post the Devastador's fix in the other thread(s) - it doesn't look like Richard has seen this.

Adamski.

[katoman1932]

As you can see there are over 5,000 views of this strand!

This should come to the attention of the head of Saitek software and driver development. They have been catching "what for" since their first announcement of an available update back in January 2007.

I know they will GLADLY issue a banner posting to get all of the nay sayers off their backs until they can distrubute the Vista upgrade!

Yes, you are correct that is one heck of a "drive" from your location! One day my wife and I will go to your part of Mother Earth with our local tour group. At the moment most of us older retired trekers are reluctant to fly since 9/11.

Cheers from PA - USA
Dick

[UKSupport]

That's why I stuck the thread when it was created, katoman ;)

It still doesn't help the 64-bit users though, unfortunately.

[katoman1932]

Richard,

First, let me again express gratitude to one and all on this EXTREMELY active and client oriented forum. If it weren't for the collective genius of the members [NOT including myself] I would still be mumbling under my breath about having either my Saitek OR my Cougar able to function in the new Vista world.

Second, I have learned the "hard" way that for 90% of the installations of Vista one would be best served by using Vista 32 bit rather than the Vista 64 bit. I installed the 64 bit first and most of my peripherals either worked less effectively or not at all. I next installed the 32 bit and EVERYTHING worked as well as or better than before.

One of my most useful digital gadgets is my Garman Street Pilot. When I discovered it would not function within the Vista 64 bit environment I contacted Garman about drivers. Their reply was immediate and direct. They had no intention of EVER developing drivers for the 64 bit OS. Period.

Third, there is only one way to install Vista and why that is not printed on all of the Vista packages in huge letter is beyond me. One must use a "clean" install, i.e., a full version and not an upgrade.

I pray this is not too far off topic. I just want to urge one and all to give up on using Vista 64 as the foundation for a happy gaming experience. My local computer guru advises me that the only good reason to use Vista 64 rather than Vista 32 is the possible need for intense security within a business enterprise; however, even in that environment he was having a difficult time upgrading all of the business world's connected hardware. This included our local hospital whose critical diagnostic machines were not cooperating at all with Vista 64.

In summary: run Vista 32 and be a happy home owner.

I do hope you can find a way to "professionally" present this wonderful "fix" in proper computer language with clear step-by-step instructions. Perhaps the home web page could have a hyper link your "professional" procedure. This will certainly keep the nay sayers [one of which was me up until this fix] off this fourum AND the return for your investment of time should be a number of positive comments. Of course that is all up to you. For me, I couldn't be happier. Now I can sit back in the rocking chair that is as old as me [76] and truly enjoy my IL-2 Complete Edition!

Cheers from the USA.

Apologetically,
Dick Brown

[gporto]

Wondering if anyone can help me. I followed the fix by putting the dll in windows/system32 and re-installing the old XP drivers under Vista. It actually now downloads the profile to the joystick. So I thought I was out of the woods.

When I go into FSX, only the basic functions and buttons work. It doesn't seem to recognize most the buttons. What am I doing wrong? I hope the answer isn't to wait for SST for Vista to come out!

Any help would be appreciated.

[ThomasE66]

Wondering if anyone can help me. I followed the fix by putting the dll in windows/system32 and re-installing the old XP drivers under Vista. It actually now downloads the profile to the joystick. So I thought I was out of the woods.

When I go into FSX, only the basic functions and buttons work. It doesn't seem to recognize most the buttons. What am I doing wrong? I hope the answer isn't to wait for SST for Vista to come out!

Any help would be appreciated.

You're using a kludge to try and address software that is not compatible with Vista. That's the only thing you're doing wrong. It might work for some people, might not for others.

[Devastador]

Greetings gporto! you considered to as much use the same version of software (SST) like of drivers? But you have the same version of both does not work, or that is my experience at least. Test to unload the SST and drivers of the same version, previous uninstall any to driver that you have previous. It installs driver again and later the soft, if there are no errors must work correctly

Good Luck!:cool:


Wondering if anyone can help me. I followed the fix by putting the dll in windows/system32 and re-installing the old XP drivers under Vista. It actually now downloads the profile to the joystick. So I thought I was out of the woods.

When I go into FSX, only the basic functions and buttons work. It doesn't seem to recognize most the buttons. What am I doing wrong? I hope the answer isn't to wait for SST for Vista to come out!

Any help would be appreciated.

[mrsemi]

Anyone been able to get this to work. I did pay for the software but I can't get it to work on Vista. I'm certain it's some small detail I'm not getting right.

The trigger keys are assigned to the x and y axis on the pro gamer pad but the game pad still does not respond to moving the thumb pad which is the most crucial function and the only thing I need to operate. The game pad works in my game but I can't get the triggers to fire.

Any tips?

And to the mods, I know this isn't their forum but I'm crippled playing the game without the updated sst for vista and I need some help. I tried the workarounds using xp software to no avail. 4 hours of deleting and reinstalling.

[Adamski]

Wondering if anyone can help me. I followed the fix by putting the dll in windows/system32 and re-installing the old XP drivers under Vista. It actually now downloads the profile to the joystick. So I thought I was out of the woods.

When I go into FSX, only the basic functions and buttons work. It doesn't seem to recognize most the buttons. What am I doing wrong? I hope the answer isn't to wait for SST for Vista to come out!

Any help would be appreciated.

Does it work with any other game (or sim)? Try opening Notepad and see if the X52 is sending the correct keypresses. Obvously none of the programmed sliders or rotators will show in notepad, but *buttons* should show.

Have you tried any of the [MS] Flight Sim forums? It may be an FSX issue. I only have FS2004 but haven't reinstalled it on my new Vista system (yet).

Adamski.

[gporto]

Unfortunetly, I think Thomas is right. I'm trying to use XP drivers in Vista and it's simply not working. I went into Notepad and none of the buttons are sending commands even in Notepad. It's not FSX, it's the drivers.

Damn, I guess I'm going to have to wait for the SST for Vista. Obviously, I wouldn't be screwing around with half-baked solutions if it were out.

Thanks anyway.

[Adamski]

Unfortunetly, I think Thomas is right. I'm trying to use XP drivers in Vista and it's simply not working. I went into Notepad and none of the buttons are sending commands even in Notepad. It's not FSX, it's the drivers.


For some reason, I feel convinced that you *can* get it working - probably because I'd almost given up hope myself.

Did you uninstall all the [failed] drivers using device manager? Have you tried with User Account Control turned off? They're the two things I did that made it all happen for me. I forgot to check in the thread - are you 32-bit Vista?

Adamski.

[schubring]

@gproto
"When I go into FSX, only the basic functions and buttons work. It doesn't seem to recognize most the buttons. What am I doing wrong?"

I dont use a profile!

Others that got it fix?

....but it should type out numbers/ letters in notepad.

I'm sure you can get it going.....find UKSupports awesome Saitek Driver uninstall post...
try that then the fix. Thats what I did.

[deifier]

See my solution for 64bit Vista aswell as it now works :D however these instructions are harder to get as Vista 64 bit is a totally diffrent story just like UKsupport mentioned.

[gporto]

For some reason, I feel convinced that you *can* get it working - probably because I'd almost given up hope myself.

Did you uninstall all the [failed] drivers using device manager? Have you tried with User Account Control turned off? They're the two things I did that made it all happen for me. I forgot to check in the thread - are you 32-bit Vista?

Adamski.


Yes, I fully unstalled the drivers from device manager. I'm using 32-bit Vista. I did not turn Account Control off. I guess I will try that. Thanks for the help.

[Ice2007]

Hi all,

so Ok we got a workaround by installing the drivers and sst software for XP.
But i see Saitek delivered drivers for Vista 32 and 64 bit
I understand the 64bit is giving the necessary problems and i saw there is even a SST dowload for the 64bit version.
ftp://ftp.saitek.com/pub/software/sst_171006_64.exe

what about the SST software for the Vista 32 bit that is sitting on the FTP site from Saitek but that you can't find on the website ?

ftp://ftp.saitek.com/pub/software/sst_171006_32.exe

May be this is an old tread but is this Vista 32 bit SST software and the Saitek drivers for Vista 32 bit for my Cyborg Evo force working or do i still need to do use the XP drivers and XP SST software?

I am a bit confused here....:confused:

[sharkb8st]

ok so we know now that the new windows vista driver doesnt work with the windows xp programming software and you cant load your profiles. so when are they going to have a fix that wroks both the driver and the programmer together? im realy wanting to play flight sim and use some settings.

[Adamski]

ok so we know now that the new windows vista driver doesnt work with the windows xp programming software and you cant load your profiles. so when are they going to have a fix that wroks both the driver and the programmer together? im realy wanting to play flight sim and use some settings.

The "fix" (posted earlier in this thread) *does* work. Follow the steps - give it a try! I've been happily "flying" LOMAC, Falcon4 and IL-2 with profiles for esch :)

Adam(ski).

[sharkb8st]

the way it worked for me is:

1. un install allllllll drivers. (vista or xp) by going to your control pannel, device manager, open the "human interface devices", un-install all the saitek ones.

2. un-install the SST Programing software

3. just use your Saitek software cd that came with your controler
to install all the drivers and sst software.



it worked for me. :cool:

[Scrubby]

FYI, it turns out that Total Game Control just needed to run in administrator mode under Vista. They have a new update online now (3.5.2), but it doesn't appear that they updated their web site... anyway, new version they sent out on the 19th runs in admin mode and seems to work fine.

BTW, Saitek is great! Love your hardware! Thanks for putting TWO shoulder triggers on your game pads!

[22GCT_Yoghi]

Gentlemen...and what about drivers to use with Vista 32bit and the PCdash2...?

[indie24]

I have the saitek all working with this fix. However I cannot get the imfd to show fsx. Any ideas. Im running windows Vista.

[UKSupport]

@indie24

What other peripherals do you have on your PC? Do you have any Go Flight Panels at all? Also, are you using the fix in this thread to load the old XP drivers into Vista or have you tried the beta drivers and software from the Announcments section of the forum?

[indie24]

Hi

I have installed latest drivers for xp (year 06 i believe). I have no other saitek products just the x52 pro. Everything work i can profile etc. I have done the fix here where i put the dll file in the system32 folder in vista. I cannot get the in flight system to show up on the imfd. It does show my profile name but thats it.

[GoNz0]

click here and make sure your up to speed on the BETA, (ie not being able to use any old profiles with the beta) http://www.saitekforum.com/showthread.php?t=11552

[DZII]

I have installed the XP Drivers and the XP sst software and copied over the d3drm.dll on my vista pc this workaround does work but my issue is when the pc has been shutdown for a while then rebooted it seems vista defaults back to vista drivers for my x52 I am able to reinstall the xp drivers for the x52 and everything works fine again is this normal for this workaround or should the xp drivers stick ?

[MarioV]

Wow.. it's June now and still no software updates for Vista. Sounds like the competition has beat Saitek to it... That flu from late March is really hanging around.

[Adamski]

Wow.. it's June now and still no software updates for Vista. Sounds like the competition has beat Saitek to it... That flu from late March is really hanging around.

I'm getting quite frustrated - as my original XP-converted-to-Vista solution has just barfed.

I moved the USB connector into a different socket on the machine and now I just get a BSOD every time I try uploading a profile to the stick.

I'm beginning to get a little tired of waiting for Saitek and may go for a CH setup. I just haven't got the time available, these days, to spend hours getting expensive kit to work. I've been pretty patient up to now, but this latest BSOD is really pi**ing me off.

Adam.

[UKSupport2]

The last update of the beta drivers on the site was May 1st, and the stable release should be days away. It was going to be yesterday, but the team is just finishing up on fixing the 'on the fly profile switching' bug.

Also bare in mind that windows VISTA ties in the drivers you install with the USB port that the device is plugged into, meaning you might have to install the drivers again if you change ports. Nice one Microsoft!

Blue screens of death are commonly associated with hardware problems. In the case of VISTA, its USB support is far from stable. Latest news on VISTA shows yet more security holes in the 'most secure operating system yet' according to microsoft.

A clear example that if you want to use VISTA without any trouble, wait 6 - 9 months for it to become stable, along with everything else that has to work on it!

[Adamski]

Thanks Sean - great news - would you do us a favour and post the announcement in this thread as well?

Thanks also for the USB tip. I think Micro$oft's implementation of USB has always been flaky. But then, it's even worse in Linux :p

[waddaa]

I have a big problem with my saitek P2500
the driver dosent work correctly with windows vista
i use windows vista home basic 32bit
in control panel when i change the bad to digital and i press right it make that i press down right on the stike

the bad is work great in windows xp
but in vista dont work

also in fifa 2007 its not read the name of the bad its read it as its name is controller no saiteK P2500

PLZ Help fast


i tried the new software nothing change!!

[Adamski]

Firstly - Sean - reinstalling *both* the drivers *and* SST software did the trick (thanks). May be helpful to others to know that just re-doing the drivers only won't do it.

Waddaa - I don't know your controller - but here's a couple of hints for you:

1) Do you have the control account warning disabled? I turned mine off so I always have full admin rights. It may be that it's preventing drivers or software installing properly because of read/write permissions.

2) When re-installing my X52 drivers + SST just the other day, I made the mistake of keeping my controller plugged in when upgrading. You really need to unplug it, remove all the drivers etc. then reinstall - only plugging in the control when specifically asked to do so. It's a common USB driver procedure, but I keep forgetting to do it myself.

Hope this helps ...

Adam.

[admin]

waddaa, on top of Adamski's advice, can you post the driver and software versions you have installed, which can be found by going to:

Start
Control Panel
Game Controllers
Properties (of the pad if present in the list, is it listed as P2500?)
About tab.

Next, go to the device manager:

Start
Computer
System Properties
Device Manager

And expand the entry that says 'Human Interface Devices' and let me know what entries you see here.

[1990GT]

I registered just to say thanx to the person who got this thread going (DEIFIER), I had to go into safe mode to delete the Vista drivers in device manager because when I did it normally, vista would crash and I would get the blue screen of death every time! The XP drivers and the XP software worked perfectly with my X52 in Vista after I took and put the D3Drm.dll into the windows\system32 folder and deleting every trace of the vista drivers. (UKSupport) Bless your heart, if your software team was as good as your Products theirs no place you guys couldn't go!!!

[Riftcloud]

I cant get it to work for me... this is so frustrating

[dommafia]

So a stable release was only a few days away from being done last month, where is it? :mad:

[BUFF]

from what Richard was saying the other day it looks like they may have decided to hold off on the release to add in many of the extra features that were originally planned.

[ramstein]

more stuff that I need that isn't being fixed/released soon enough :(
I am waiting for several patches and addons for things, this summer is coming up dry for this stuff...

[dommafia]

from what Richard was saying the other day it looks like they may have decided to hold off on the release to add in many of the extra features that were originally planned.

Wouldn't it make more sense to release the stable version with less features while they work on the other features? Sounds like excuses to me. All this waiting is getting annoying.

[abaris]

So, does that mean, that I can merely watch my new X52 Pro under Windows Vista without being able to use any of its advanced features?

Great, should have known before forking out the money.

[UKSupport]

Hi,

No, you can use the beta just fine and get all the advanced features and more than was available with the driver/software that it ships with.

http://www.saitekforum.com/showthread.php?t=11552

[kosikatze]

Hello, tried to download from the linked page, but the system asked me for a name and password. My saitek login data don´t work - what do I wrong?

Stefan

Edit: Now it workes without Password. :-)

[fraboh]

Hello,
what are the further plans to release official Drivers for the X52 Pro for Vista?
Since May nothing much happened.
This is 3 month ago!
Best regards
Fraboh

[Rune]

No, you can use the beta just fine and get all the advanced features and more than was available with the driver/software that it ships with.
I am assuming that this answer is meant for Vista 32...:? The question was not for Vista 32 exclusively though.

Beta 2 in Vista 64 gives me the two "advanced features" of having the Saitek driver use 100% of the CPU on the core it runs and the driver software being unable to do the pretty basic funtion of loading a profile. I have a functioning STT though - which infortunately is useless for me at the moment :-(

This all makes me wonder about something. I see a specific link to a Vista 64 beta("X52 Pro Flight Controller 64-bit drivers") in the beta thread, but why post a beta that does not have any usable functionality :?

I think it is a tad sad that these drivers are not usable yet, especially after expecting them any day for several months now :-( Having bought a new system with many new components from known "dodgy support" companies(in the terms of driver support) I find now that Saitek(which is not known as a dodgy support company) is the absolute last remaining company to deliver a working driver to get my complete system running as intended :-( I really miss flight simming and I can't wait to get started flying with my new PC. I find it very annoying that I have not been given better information than I have. Had I known it would take this long I might have sold my HOTAS and bought one that works for me, instead I have been checking back here a hundred times because I am promised that the next version is only days away. So I must ask, should I sell my HOTAS? is there ever going to be a (working) Vista 64 driver?

[UKSupport]

Hi Rune,

I think you must realise that your experiences are far from the usual; most people are able to get the beta working just fine.

Let's get things completely uninstalled and then see if that helps:

Go to Device Manager, click the plus sign next to Human Interface Devices and you should have the two entries for your controller. Right-click the first one and choose Uninstall from the drop-down list of options. One the window that comes up, tick the box that mentions removing the files for the controller and then OK.

Now uninstall the SST software using the Add/Remove Programs in Control Panel and restart the PC.

Try reinstalling the 64-bit beta 2 drivers and software only and then see if it helps.

If it doesn't then I also need to know if you ever tried installing the old SST that's for Windows XP users - a lot of people with Vista did try it and if things are still hanging around from that then that could cause issues.

[wabash10]

I downloaded the dll, and will install it, I just need to know if I am supposed to use the vista sst and install or the xp disk,
I appreciate any help you can give me
thanks

[UKSupport]

You only need to use the .dll if you're not going to use the Vista drivers and software from us.

I would recommend trying the Vista beta drivers and software first and therefore ignoring the .dll as this was only a temporary fix whilst we were still working on our Vista support.

[Rune]

I think you must realise that your experiences are far from the usual; most people are able to get the beta working just fine.Ok then I may have misread or read posts out of sequence on these forums, because I got the destinct impression that no-one had a working X52 Pro in Vista 64 at this point...But any hope is an improvement for me by now :)
Let's get things completely uninstalled and then see if that helps:

(...)Did that today and it still does not work. It does however fail in new ways...

With drivers alone(as instructed) I can load a profile, but it does not output keypresses(seems to be stuck with clutch on since the MFD gives me the label of the button no matter what I do, 'i' button held or not / latched clutch or not) and infact any button that is 'held down' causes the cpu use to go to 100% - this includes the center position of a hat, so the first time the hat is moved I have to unplug the HOTAS...

Installing then STT on top of this makes it still load a profile and the keypresses even go through, but then the cpu problem occurs even without attempting to load a profile if I just randomly push some buttons and move the hat and axes.(...)then I also need to know if you ever tried installing the old SST that's for Windows XP usersI did so many different things that I can't remember if I did or not, but I guess assuming I did is the sensible route in this case. So how do I clean such a mess up?

[UKSupport]

Okay,

I'm a little confused because if you had drivers-only installed then there shouldn't have been an editor to load any profiles with... This could indicate that things are indeed in a bit of a mess!

Do that uninstall I mentioned above again and also Uninstall the Saitek Smart Technology software from the Add/Remove Programs in Control Panel then do the following:

Now browse to your C:\Windows\Inf folder (if you can't see an Inf folder then click Tools>Folder Options at the top of the window, then click View at the top of the window that comes up. In there click the dot next to the Show Hidden Files and Folders option and then click OK - you should now be able to find an Inf folder in the Windows directory) and look for the OEM0.inf file. Find the highest numbered OEMXX.inf file and double click on it - a Wordpad screen will open up with information in it. You're looking for any lines that refer to Saitek (usually at the top of the window). If you don't see any such info close that window and open the next OEMXX.inf file - so if you started on, say, OEM30.inf then you'd now open OEM29.inf.

If you find any that refer to us then close the window and delete that OEMXX.inf file along with its accompanying OEMXX.pnf file. Go through all of them until you have deleted any files that mention us.

Now do a search for files in Windows using the following search string:

sai*.*

Once it's finished finding any files delete them - files only though, don't delete any folders.

Finally, do a similar search in your Windows registry and delete any keys that you find in there (you'll need to keep hitting F3 to search for the next item after you've deleted each one).

Once you've done all that, give the machine a restart and then try again installing the beta driver and software again.

[Rune]

Okay that was quite a bit of work, took me several hours to do, among other things, because I had to wrestle Vista for control over files and registry entries many times over stuff that an adminitrator is apparently not granted control over by default :? Snd even after all that it still does not work any better :(

The profile loading I am talking about is by using the clutch function, and it still works now after doing the cleanup and installing nothing but what I have downloaded under the title "drivers"("Saitek_X52Pro_Flight_Controller_SD6_64_beta2.exe"). So either it is in the driver install or the cleanup was not good enough. I assume by "installing the beta driver and software" you don't mean to install the SST software, but just to run the "driver" .exe . I never see the task-icon that makes me able to select a profile using the mouse when I install the "drivers" only, if that explains things better.

Only deviations from the instructions were a registry key branch that I could not delete for the life of me: HKEY_LOCAL_MACHINE/SYSTEM/ControlSet03/Enum/SaitekMagicBus...I deleted much or maybe all of the data in it and its subkeys but I could not delete the keys or subkeys themselves, or infact even view the Property keys, gave an error like "SaitekMagicBus cannot be deleted: an error occured while trying to delete the key", similar errors occur if I try to change ownership of the key and I have no clue how to delete them. Also I have deleted a few of the directories along with the files in them trying to get this done before New Years, if either of those two deviations are critical I'll have to try again I suppose - sigh :|

[Spksh]

I assume by "installing the beta driver and software" you don't mean to install the SST software, but just to run the "driver" .exe .

He means both the driver and software (i.e. the driver and SST software). You won't see the icon to load profiles without installing the SST.

[UKSupport]

Clarification: when I say 'drivers' I mean exactly that - the drivers file for your controller. When I say 'software' I mean exactly that - the programming software, which is a separate download, as you know.

So are you now reinstalled with the software but still getting the 100% CPU usage etc.?

[Rune]

Installed the SST, got an error titled "InfStall" with the message "Error 1168 in UpdateDriverForPlugPlayDevices: Element not found". Install proceeded after clicking "OK" and gets me back where I started with no keypresses coming out and having to reset or disconnect the controller every other minute if I load a profile...

[UKSupport]

Hmmm - I'm wondering if there's a problem with that key for the Magic Bus which is causing the error in the installation. The problem is that it's one of the registry files which Windows won't let you touch (which is why you're having trouble removing it) and we're trying to think of a way that you can remove it so that a fresh install might work.

Could you look back in your C:\Windows\Inf folder and find the oemxx.inf file that references the Saitek Magic Bus? Make a note of the name of the file and then do the following:

Click Start and type

cmd

in the run box - DON'T press enter yet though! Look up and you should see it as an icon - right click on that and click Run as Adminstrator.

pnputil -f -d oemxx.inf

and press Return (oemxx.inf is the name of the oem file that you found with the info for Magic Bus earlier).

This should remove that oemxx file and, we're hoping, that registry entry for the Magic Bus.

Now restart and try reinstalling just the software again.

[Rune]

After the pnputil and restart I checked the registry and found the key still in there and acting as before. I then installed the SST and got no error :? ...and now I get keypresses from programmed buttons - so that is at least an improvement...but the CPU thing is still there :|

[UKSupport]

Is the 100% CPU problem occuring only when a profile is loaded? If so could you zip and attach your profile so I can check it out please?

[Rune]

After a second reboot, after SST install, the whole thing fell apart and stopped working again :( the profiler cannot be seen in the task icon list and the controller does not have a clutch function anymore when I plug it in. It is back to DirecX only functions.

Previously I had the CPU problem without profiles loaded and with two other profiles loaded than this one, but this profile seems to be the quickest one to cause it. It happened also with a profile that was a completely new one created with 'new' only with a single key output added for testing it with notepad...But I did not test those other profiles for the 10min it seemed to be heading in the right direction...:/

[UKSupport]

Well there is a known issue in this beta where if you have an Advanced Command that has no keystroke entered in the Repeat row then activating that command will 100% your CPU. The fix for this is to put a keystroke in the Repeat row for the time being and that profile certainly has a lot of buttons that fit this description.

But it still happened with a single keystroke-enabled profile so something more is happening here. Unfortunately, I don't have anything else to suggest at the moment, short of a roll back using the System Restore function in Windows. However, this is likely to undo a lot of other stuff that you've done since you originally installed the stick under Vista and it's not guaranteed to fix the issue.

How long have you been running this Vista install and how far can you roll it back?

[Rune]

The PC and OS are a couple of months old and I have plenty of restore points from that period. Unfortunately I have done quite a few other critical changes from the time when I first tried to install the X-52 Pro. Rolling back would be about as bad for me as a complete reinstall of Windows, so I will only do either one if and when my frustration level is a lot lower than now and that may take a while.

I think for now I will not do too much about it, except not use the HOTAS. But since the problem looks exactly the same from my point of view when it happens without a profile or with the single key profile I have hopes that once the repeating key thing is fixed my problem will be fixed too, and that hope might give me the energy to roll back or reinstall once there is a new driver/software version, if I absolutely have to.

Thanks for guiding me through all this, I appreciate it :)

[Adamski]

Do we have an ETA for the 32-bit Vista drivers & software (full release - NOT beta)? Some time way back in May (I think) these drivers were announced as "any day now".

[Kavak]

Do we have an ETA for the 32-bit Vista drivers & software (full release - NOT beta)? Some time way back in May (I think) these drivers were announced as "any day now".

^^^^^^^^^

?

[UKSupport]

They're with the test team at the moment. Assuming there's no bugs, then it should be available soon, but there's a lot of devices to test so it's not as quick as you might think.

[IsmirQuismik]

At first I thought I was supposed to download the vista drivers and the XP software, so I downloaded and installed both, did the dll fix and it looked like it worked, but I got another error, so I checked back, saw I needed them to be the XP drivers, so I downloaded the file and installed those, thinking it would erase the old files like it says it's going to and fix the problem like it did for everyone else, but now I'm recieveing the 'no profile' message again as though I had never done the dll fix. The 3d view doesn't show up properly either, even after I've replaced the dll again to make sure I was doing the right thing. Anybody know what's up?

[lumor_]

They're with the test team at the moment. Assuming there's no bugs, then it should be available soon, but there's a lot of devices to test so it's not as quick as you might think.

After all this we assume that there will be lots of bugs, that the installation will be awkward as always, that you will continue to assure us that everting is fine or will be fine soon. We don't expect anything to happen soon. We don't think anything will be quick at Saitek. We don't think you even care. Only the length of this thread is enough of a warning sign for anyone who thinks of buying a flight control from Saitek.

You say that there is a lot of devices to test. Fine, but hey this is not rocket science and your staff should be pros that are familliar with your line of products. Your programmers should be able to build a converter for the profiles in no time. The release of Vista cuold not have came as a surprise for them and you have had _plenty_ of time since then to make things work.

Your hardware shines but your software makes it unusuable. When people buy a product they expect it to work smoothly. Saitek X52 isn't in the vincinity of smoothness. The support is better from the community than from the company. Scandalous!

I will never buy a product from you again. I will warn others from doing it.

Thrustmaster, Logitech, Microsoft or others would never treat their customers like this. :(

[UKSupport]

Thrustmaster and Logitech didn't have Vista software available for their products until June or July and some people do have problems with them, just like some people have problems with our software.

You don't state what problems you're having exactly with the beta drivers and software - having not had a post from you on here before, I can only assume at the moment that you haven't attempted to fix those issues that you do have.

Perhaps if you do state what issues you're having then I may be able to help you out?

[chrisgoddard]

Keep usiing latest drivers and they seem to install but then Windows says unsuccessful. Anyone any ideas

[chrisgoddard]

Tried various vista versions. Same result most times. Also no sign of the Profiler either - I thought that was supposed to be part of a single install. Cannot see a simple walkthrough of what to do,

I really need the X52 working as I have a lot of games using it

[Spksh]

Have you tried the Beta Vista drivers linked in the Announcement forum?

SST and Drivers are separate downloads, not the same install.

[VSkwidd]

Vista 64:

From what I have read there are no solutions official or unofficial.

Controllers work fine;
SST does not work what so ever. It runs... when I click on something - it stops working.
Magic bus- nothing. :(

Magic bus installs (or seems to) correctly, no error messages or anything.
During SST installation you get the error :
"The following files did not Self-Register or Unregister:
1. C:\Program Files (x86)\Saitek\Software\SAI3DVIEWER.dll

The specified module could not be found.

'ok' 'cancel'
"

If you have any questions or tests you'd like for me to perform on this issue-
give me input (thorough input :p ) and I shall give output and await further input :]

if you need I could post the general information about my computer. (edit: woops thats all in my sig)

-VSkwidd

[UKSupport]

That's correct - for 64-bit there's no solution with the XP drivers and software. You would need to use the beta drivers and software from there on the forum.

[VSkwidd]

so then is there any release date expected for the release of a compatible version of SST and Magic Bus?

[UKSupport]

Like I said, they're already here on the forum:

http://www.saitekforum.com/showthread.php?t=11552

[VSkwidd]

Hmm, ok, It uninstalled the SST version that was not working but did not install a working version... also, magic bus still does not work :(

Don't get me wrong I'm glad that Saitek has been working that hard (quite the list of new drivers) and it will certainly take some time to get through the mess of security web inside MS Vista x64

Just to make sure though, were those beta drivers even meant to install a working version of SST and Magic Bus? Those were my two favorite features of the X52 pro :D

Much appreciated
-VSkwidd

[Spksh]

Just to make sure though, were those beta drivers even meant to install a working version of SST and Magic Bus? Those were my two favorite features of the X52 pro :D

SST and Drivers are separate downloads, not the same install. Beta SST is at the bottom of the list of drivers.

[VSkwidd]

Oh I just feel like a dumbass now :o
But thank you very much for pointing it out to me you'll have to excuse me I'm a bit blind :cool:
It seems to work though so I am a very happy man right now thank you saitek!

<S>
VSkwidd

[john lacante]

Like I said, they're already here on the forum:

http://www.saitekforum.com/showthread.php?t=11552
OK Thanks
But must I use the cd rom and install the software from it
Before installing
X52 Pro Flight Controller 64-bit
and
SST Programming Software 64-bit

Sorry for this stupid question.

John

[BUFF]

No, just install the drivers & software from the link.

[jvile]

Gentlemen

x52pro Vista 32 version

Using the FSX Flight Simulator with the new SP2/Accel Pack. I cannot get SST to accept any keyboard input except as a Band.

Any programmed keyboard input defaults to a check mark for band. I don't think this is correct but could be wrong.

Is there something I am missing in the programming of the keyboard. I have tried both sets of SST drivers (forum listed and web site) and read the documentation for the X52Pro and what little bit is there on Bands vs every other check mark.

I am not new to Saitek and programming which goes back to the x45 on a Windows ME system. I have waited a year now to use my x52Pro with FSX but still can only use the Joystick based on the FSX default entries.

My newest computer (4 months old) is the highest end Alienware ALX Area51 running duo Intel processors OC and 2 Nvidia GTX 8800 768 MB cards. The computer was built for speed and runs FSX perfectly. I just wish I could get a Joystick to work. I have a x45, x52 and x52pro and no SST will program on this Vista 32 machine. Current saitek software is

Driver Version 6.02.123
Software Version 6.0.4.1

Any help would be greatly appreciated.

[jvile]

Just to update that I have SST now programming fine. The driver and the SST software were not the same versions as noted in my previous post. Once I corrected this problem and the versions match everything is working fine.

I am not sure if I have the lasted match but the About says

Driver Version 6.0.4.1
Software Version 6.0.4.1

These are listed in a post link as Vista 32 beta2

[msny]

Need help please

I've installed the beta2 drivers from the forum here.
They load and I can create profiles. But when i select that
profile for the Unreal Tournament 3 it does not work ingame?

Using Saitek keyboard with gamepad controller.

What should I check or try, to get it to work in game?

Thanks!

[Spksh]

What should I check or try to get it to work in game?

What version of the SST and Drivers show in Control Panel (click the Saitek icon in your system tray --> control panel)? If they're not both 6.0.4.1 then you've installed the wrong packages.

If you open notepad with the profile loaded, do you see keys being typed when you press buttons on the controller?

[msny]

What version of the SST and Drivers show in Control Panel (click the Saitek icon in your system tray --> control panel)? If they're not both 6.0.4.1 then you've installed the wrong packages.

If you open notepad with the profile loaded, do you see keys being typed when you press buttons on the controller?

I have installed 6.0.4.1.

The button keys do not work in notepad either?

Edit:
From the web page which files are required for the
Gamers keyboard and commmand pad?

http://www.saitekforum.com/showthread.php?t=11552

I want to make sure I've installed the right software.

Any ideas?

[Spksh]

I don't own either of those, so I can't tell you which drivers to use. I would guess "Gamers Keyboard 32-bit drivers" and "Pro Gamer Command Unit 32-bit drivers" (if that's what you mean by "command pad").

If the keys won't work in Notepad, they won't work in the game.

If you're sure you have the right stuff installed and the profile still isn't working, zip and attach the profile here so we can have a look at it.

[msny]

I don't own either of those, so I can't tell you which drivers to use. I would guess "Gamers Keyboard 32-bit drivers" and "Pro Gamer Command Unit 32-bit drivers" (if that's what you mean by "command pad").

If the keys won't work in Notepad, they won't work in the game.

If you're sure you have the right stuff installed and the profile still isn't working, zip and attach the profile here so we can have a look at it.

Thanks for your response.

I've downloaded and installed in this order

"Gamers Keyboard 32-bit drivers"
"SST Programming Software 32-bit"

The pro gamers driver will not install. I beleive it
does not recognize the game pad controller.
I've spent a lot of frustrating time trying to get this
simple controller to work. It should not be this difficult.

Things I've tried
1) started with the WinXP drivers they did not work
2) came to this thread and tried installing from first few posts with that work around - did not work - could not load profile gave error messages
3) removed older drivers, removed device manager drivers for keyboard reinstalled - started fresh -numerous reboots
4) tried to email support and the emial comes back as
undeliverable??
5) finally found beta drivers, installed them profiles now load and the software itself works, but the profiles do not.

I've attached a simple profile for anyone to test.

I could use Saitek supports help please!
I'm in IT myself and nothing should be this difficult.

Thanks for your time!

[UKSupport]

You've got the right files there (I'm assuming you have the Gamers' Keyboard with the command pad that attaches to it) so things should be working. Have you tried reinstalling the drivers and the programming software again to see if that helps?

[msny]

You've got the right files there (I'm assuming you have the Gamers' Keyboard with the command pad that attaches to it) so things should be working. Have you tried reinstalling the drivers and the programming software again to see if that helps?

Support-

Thank you for your help on this issue, much appreciated.

Yes, I do have the keyboard with it's attached keypad.
I have reinstalled everything at least a few times now.
Still does not work.

What should I see in device manager under "keyboards" or the gamepad?
I do not see any entries under keyboard and I think I should. There is a Saitek Magic
Bus entry, thats all.

The only thing I can think of, is my registry or loaded setup files are messed up from trying to use other XP versions. Dunno. What would I need to do return the system to clean state, then retry it again?

When rerunning any of the installers it prompts me to "overwrite" the current loaded files, which I do.

The Vista install box detail says
Magic Keyboard
Magic Mouse
Magic Hotkey Device

Does my sample profile I uploaded work at all for anyone else?

[Spksh]

I can't open your profile - I get "Failed to open file." When I open your profile in a text editor, I see references to SD5 (the old version of the SST software).

Please check the version numbers that show when you click the Saitek icon in your system tray --> Control Panel --> About, and tell us what the numbers are.

Please open Profile Editor, click the down arrow next to the Help icon, and select About. What version number shows there?

[Spksh]

If the above all checks out, it's probably an issue with the profile. Where did you get it from? Is this an old profile from before you upgraded?

SD5 profiles do not work with the new SD6 SST software - you have to rebuild them from scratch.

The profiles you can download from the Saitek website are all SD5, as far as I know. The forums here do contain some player created SD6 profiles, although I haven't seen one for the keyboard and UT3.

[msny]

If the above all checks out, it's probably an issue with the profile. Where did you get it from? Is this an old profile from before you upgraded?

SD5 profiles do not work with the new SD6 SST software - you have to rebuild them from scratch.

The profiles you can download from the Saitek website are all SD5, as far as I know. The forums here do contain some player created SD6 profiles, although I haven't seen one for the keyboard and UT3.

Hmmmm...The version is as I stated above is 6.04.1.
I created the profile myself in the default directory of
"Saitek SD6 Profiles".

I did not download any profiles?

I'm confused....

[Spksh]

I'm confused....

Yeah me too. It should just work.

Try creating a new profile, and just assign a single letter to one of the buttons and test that in Notepad.

[msny]

Yeah me too. It should just work.

Try creating a new profile, and just assign a single letter to one of the buttons and test that in Notepad.

Ya I tried that, same problem.

I may roll the system back and then try the install again, or try to figure out if some other driver versions got mixed into the install.

[msny]

I have rolled my Vist 32 back to yesterday just before trying the first install.

I then reinstalled the latest 6.04.1 software. No go, does not work. Just as before, I can create profiles but they do not work at all. If i can't get it to work, this thing goes to Ebay, its worthless.

Can any support folks give me a hand please?

Here is a new profile I just did.

Give it a try please. Thanks.

[UKSupport]

Well looking at that profile, you've only got three letters programmed to buttons 1, 2 and 3 in Mode A of the command unit - this means you would need to hold down the Mode A button on the command pad to then activate those programmed commands.

Try putting them in the Unshifted mode and then test it and see if it works.

[msny]

Well looking at that profile, you've only got three letters programmed to buttons 1, 2 and 3 in Mode A of the command unit - this means you would need to hold down the Mode A button on the command pad to then activate those programmed commands.

Try putting them in the Unshifted mode and then test it and see if it works.

OK that worked!

Now I feel real stupid. :eek:

Thanks so much!

[kaffee27]

I installed the new drivers and the sd beta.
P2500 pad is not responding on programmed buttons in word pad.
Please help.

[Spksh]

I installed the new drivers and the sd beta.
P2500 pad is not responding on programmed buttons in word pad.
Please help.

1. Click the Saitek icon in your System Tray --> Control Panel --> About. Tell me the version numbers of that show (they should both be 6.0.4.1, otherwise you've installed the wrong packages).

2. Create a new profile, assign a single letter to one of the buttons. Test that in wordpad.

3. Are you using XP or Vista?

[kaffee27]

Driver version: 6.0.2.123
Software Version: 6.0.4.1
I am using vista 32 bit

I used saiteks driver download page to identify the file for my p2500.
Saitek_P2500_Rumble_Pad_300107_32

That is misleading.

After installing the beta2 version from this forum, it worked.
The versions are now matching.
Thanks for your help.

Regards

Arno

[Desert Flyer]

This is the .dll file you place in you c:\windows\system32
.........

I don't register for forums very often to say thank you because I've not run into the need to do so usually.

But I felt compelled to register here just to say thanks to deifier, whom without his/her? post to this Saitek forum about how to get the software to install properly on vista I would certainly have either reformated and reinstalled XP again or I would have taken the X52 back to the store and told them that they are farfugnugen crazy and that it doesn't work with Windows Vista.

Saitek please take note of this, I WOULD HAVE RETURNED YOUR PRODUCT BECAUSE THE INSTALLATION MEDIA WOULD NOT INSTALL ON VISTA!

Thanks to deifier, your post is very much appreciated and it worked without a hitch! I am now flying my heart out in Flight Simulator X with my new Saitek X52 controller and lovin' it far more than trying to fly with my old logitech joystick.

[humps 1]

I'm looking for some guidance on how to install my x52pro SST as I have read most of this dating back to the begining and by now I would of thought Saitek would have a complete set of software and drivers that work. I seem to be missing the 3d model in the sst program and none of the profiles work. Could somebody point me in the right direction

[Spksh]

I'm looking for some guidance on how to install my x52pro SST as I have read most of this dating back to the begining and by now I would of thought Saitek would have a complete set of software and drivers that work. I seem to be missing the 3d model in the sst program and none of the profiles work. Could somebody point me in the right direction

This thread is how to hack the old SST to work with Vista.

Sounds like you've installed the new Beta2 software, which officially supports Vista. In my opinion, Beta2 SST is a better product for customising profiles than the old one.

Downside is that the 3d model is gone (because of a missing dll in Vista) and you can't use any of your old profiles - you need to recreate them from scratch.

Check the thread in the Announcements forum for more info on Beta2.

[Stinger22]

Follwed instructions in OP and in works great, got the 3D view once again.

[kingltj]

I am trying to install the x52pro on vista 64 bit, i downloaded the sd6_64 drivers but it wont install. What gives?:confused:

[Spksh]

I am trying to install the x52pro on vista 64 bit, i downloaded the sd6_64 drivers but it wont install. What gives?:confused:

What's the exact filename of the driver package you're trying to install? What's the exact text of the error message you're receiving?

[kingltj]

Saitek_X52Pro_Flight_Controller_SD6_64.exe , and there is no error message, it just wont install. it keep asking for drivers for unknown devices. And it leaves about four unknown devices in my device manager...

I am running vista 64 bit ultimate...

[Spksh]

Saitek_X52Pro_Flight_Controller_SD6_64.exe , and there is no error message, it just wont install. it keep asking for drivers for unknown devices. And it leaves about four unknown devices in my device manager...

I am running vista 64 bit ultimate...

That's odd. I'd uninstall both the SST and drivers from Add/Remove Programs and then start again. Make sure you're installing the drivers first.

[kingltj]

Yea thats what i do. when I get to the part where it says "Plug in the device you would like to upgrade" or something like that, I plug in the controller (X52PRO)
Vista Starts looking for drivers. For some reason reason, vista says it cant find drivers and i get stuck with 4 Unknown devices in my device manager...

Has anyone tried to install X64 Drivers for X52PRO on vista ultimate 64 bit?

For some reason, it aint working for me. I will most likely call saitek and I get the feeling that they aint gonna be any help...:mad:

[Spksh]

Yea thats what i do. when I get to the part where it says "Plug in the device you would like to upgrade" or something like that, I plug in the controller (X52PRO)
Vista Starts looking for drivers. For some reason reason, vista says it cant find drivers and i get stuck with 4 Unknown devices in my device manager...

Has anyone tried to install X64 Drivers for X52PRO on vista ultimate 64 bit?

For some reason, it aint working for me. I will most likely call saitek and I get the feeling that they aint gonna be any help...:mad:

You might want to do a search for your issue on this forum. I recall someone else having similar problems (turned out to be some missing/corrupt Vista files if I recall correctly).

Vista should be able to detect and use the stick without Saitek drivers, though. As a test, uninstall all the Saitek stuff again (drivers, SST and DirectOutput) and plug in the stick - what happens?

[Broner]

I purchased the X52 Pro two weeks ago and frankly I cannot believe the difficulties I have experienced (still experiencing) in attempting to get the thing working in MS FSX under both XP 32 bit and Vista 32 bit.

I have now managed to get it working fully under XP. After more wasted time and effort effort, including poring over forums, installing and unistalling drivers and programming SW, I have managed to get to the stage where it is working (up to a point) under Vista. I can edit and load profiles into the profile editor but they are not loaded to the controller and nor is the FSX plugin support (eg no radio stack in the MFD). I am using the latest Vista 32 bit drivers and SST (at least I am sure I am) - Driver ver 5.5.0.82 and SST ver 6.0.4.1. Somewhere I read that the versions should match? Is that not the case? Also given other ppls experiences, should I be using the XP drivers and SST in Vista until Saitek sort out the Vista SST SW?

I work in the IT industry and frankly I am amazed at the horrendously poor and inept support provided by Saitek. My experience to date appears to reflect of a product being pushed to market too soon resulting in the absence of a robust pre-release testing strategy, woefully inadaquate end user documentation and a poor understanding of the likely incident support requirements.

I am astounded at the amount of patience and dedication shown by some of Saitek's customers who frequent this forum. IMO Saitek do not deserve such levels of customer support because they have not earnt it; in fact it's a suprise to me that they have a customer base at all if my experience to date is mirrored across Saitek's product range!

So Saitek, you could start to help to improve the situation by implementing some simple measures to better support your customers:

1. Version control (eg date) your announcements and FAQs. Be more specific about what should be used when and what has been supersceded. Don't assume that customers understand your terminology and language or that they have the time or ability to follow weeks and months of support forum threads to get a comprehensive and up to date picture of the position surrounding their issue. Provide per product summary position updates from time to time.

2. Be more process driven. If the process is correct and people follow it then things do not go wrong. You (our) problem is that you have not made any of the processes clear for people. In fact you make the situation worse by putting out poorly documented ad hoc fixes and by making random comments in response to issues that are being raised. I recommend that you take the time to write basic install and setup processes containing straighforward step by step procedures for installing and setting up the joysticks. The time invested would be more than saved by lower support incidents in the medium term.

3. Put yourselves in your customers shoes when responding to issues and queries. Your whole approach comes across as 'tired' and gives the impression that you can't really be bothered - the term 'offhand' comes to mind. You should believe that your cusotmers are your number one priority. No satisified customers = no business; no business = no jobs!

Saitek - you need to get a grip! I will give this a couple more weeks to be sorted otherwise the X52 Pro will be going back to store for a refund on the basis that it is of non merchanisable quality - that translates to unuseable! The product is undoubtedly competent at the hardware level but is so poorly let down at the software and support levels. You have to address these issues urgently!

[Broner]

More tweaking and now I have this combo working (still no 3d of course) under Vista 32:-

Driver: 6.0.4.1
SST: 6.0.10.7

[kingltj]

the driver versions you posted earlier were incorrect, the new ones you posted are the correct ones. Under Vista, you have to go in your device manager and upgrade some drivers. if you see any unknow devices, right click them, click upgrade, browse my computer for drivers, "C:\Windows\System32\DriverStore\FileRepository\", make sure the option to look in subdirectories is enabled. do this for every unkown device and any that pops up during this process...
If you have any more problems, PM me. and post back if you were successful or unsuccessful...


And o yea, they removed the 3D modeling in the version 6 software/SD6. They couldn't model it in windows vista...

[marcadam34]

Hi all, dont get it to work! Tried everything written here!
Im desperate now...please help!!

Tried 2 versions:
A) the latest available download from Saiteksite that is SST software V6.0.10.7 (dated 2-10-2007) and driver V6.0.4.1 (dated 1-may-2007)... SST installs Magic bus etc under windows system BUT doesnt show up under installed software! Plus, even more important: the joystick icon doesnt show up in taskbar so I cant do anything with it to program the stick! Drivers install correctly as V6.0.4.1 and show also up under HID devices.

B) the SST and driver BETA2 versions both published and dated May first 2007 and both V6.0.4.1 :
Now SST icon shows up in taskbar plus under installed software but BIG problems after clean installing drivers and SST software...:
- VISTA reboots/resets time after time when having joystick connected...
if reboot without joystick connected if boots correctly all the way into Windows BUT when I then connect the joystick it fails to be programmed with the profile editor. Any assigned commands dont get through to the flightsim FSX!!

Im feeling hopeless now because when I had XP it all worked fine with FSX now Im a flightsimmer with a dead stick...Please Helpppppp! Thanks in advance for any help!!!!
:mad: :confused: :mad:

[UKSupport]

Hi,

Go back to the newer drivers and software from the website and use the fix at this link to make the software install correctly:

http://www.saitekforum.com/showthread.php?t=13835

[DarK_Knight]

suffering the same here..stick still shows up as a 6 axis 28 button with hat switch..this is drivin me nuts..it was workin yesterda

DK

[buddmeister]

Hi,

Go back to the newer drivers and software from the website and use the fix at this link to make the software install correctly:

http://www.saitekforum.com/showthread.php?t=13835

How the hell do you justify having a broken installer on your webpage and then have the solution posted in a thread that you need to register to be able to read? I payed for your keyboard, I shouldn't need to be registered in your supportforum to get your software to work! What are you? Two teenagers working out of moms garage? ANd the thread with the fix is posted february 1st, you should have f**king fixed it by now! Amateurs!

[x1myst]

Hi

Could someone please tell me if there is a definitive fix for the x52 and Vista 32?

Just got one today and found out i cant load any profile - i get the failed to open error message!

I have trawled through the 12 pages here and tried the various suggetions to no avail.

If there is a simple working solution i would be grateful if anyone could point me to it please.

I currently have the beta2 files installed but as i say have tried all the others suggested afaik inc main ones in the d/load section that are allegedly for Vista.

Thanks

[tkujala]

It worked just fine. Now all I have to do is figure out how to use it. Are there ant IL-2 Sturmovik profiles for an AV8R out there

[CobraDueCento]

Hi,

Go back to the newer drivers and software from the website and use the fix at this link to make the software install correctly:

http://www.saitekforum.com/showthread.php?t=13835

Hi all,

i tryed this and now I have back the Icons in the SysTray, but even now I can not start the Profile-Editor. After a reboot of the computer, the small windows to choose if I want do edit the X52Pro or the Rudder Pedals appears, but thats it. No Profile-Editor appears... whether the X52Pro Editor nor the Rudder Pedals Editor... and no error message or anything else... the choosing window disappears, and thats it... nothing more happens

Any news, how to get this fixed?

Best Regards
------------------------
Using Windows Vista Ultimate, X52Pro (6.0.4.1 / 6.0.10.7) and Rudder Pedals (6.0.8.1 / 6.0.10.7)

[UKSupport]

Does it not appear if you run the SST icon on the desktop? If not then does it appear if you run that icon with the controllers unplugged?

[CobraDueCento]

Hi Richard, hi all,

its indeed really, really embarassing... as a profesional software engeneer with more then 20 years computer experience and more then 20 years without a virus, just now a virus catched me... it's so painfull embarrassing...

Now, after desinfection, all is running as expected! Sorry for my overhasty post!


Best Regards
Franco
aka CobraDueCento

[LamPa]

Im smooth over behind his English bought am saitek for gamete unit, profile editor functional doesn't go replaced profile, error, please help

[MCES]

deifier, I folow the steps and it's work perfectly,
Thank you.
PS: I don't need restart PC. When i instaled again the software from the disk, it's works.
:)

[JohnMalcolm1970]

Any up to date news on when we Vista users can expect an SST program from Saitek that includes the 3d views of the controllers (x52)?

The 3d views not only made profiling easier, but being able to print out profiles with controller views made things much easier to refer to.

[Tazmadevl]

My X45 Calibration doesnt work. Tried calibrating thru FlightSim X. Plane keeps pulling to one side and can't pull up. Tried beta drivers Vista 32 bit and still doesn't work. Am I doing something wrong?: eek:

[wombat100]

Any up to date news on when we Vista users can expect an SST program from Saitek that includes the 3d views of the controllers (x52)?

The 3d views not only made profiling easier, but being able to print out profiles with controller views made things much easier to refer to.


I am also waiting for SST for Vista, when will it be out?

[jerry015]

Ok i have recently added the d3d file and ive got the software working good and everything but for some reason as long as the software is installed it lags my computer .

[wombat100]

Any up to date news on when we Vista users can expect an SST program from Saitek that includes the 3d views of the controllers (x52)?

[Darkcloud]

Any up to date news on when we Vista users can expect an SST program from Saitek that includes the 3d views of the controllers (x52)?http://www.saitekforum.com/showthread.php?p=75864#post75864

[wombat100]

Darkcloud,
thanks for the heads up on this one, downloading now.

[zmegis]

i downloaded the latest drivers for the cyborg keyboard and the cyborg mouse.
installed them... then i downloaded the software for cyborg keyboard and used winrar to extract the downloaded file "Saitek_Cyborg_Keyboard_SD6_32_Software_pfw.exe" to a random folder.
then i opend the folder and did run the file "software_loc_9.msi"
after that i ran the file setup.exe and installed SST. (after i ran the file "software_loc_9.msi" a checkbox and a text who said "run saitek smart technology or something like that did appear in last page of the install wizzard)

observe that i did not find this way to install SST i took it from this site: http://www.maxfps.se/forum/topic.asp?TOPIC_ID=1431 but it is in swedish so you will probably not understand a thing

sorry for my bad english.

if you did not understand and still want to know how i did plz pm me and i will try to make myself clear.

[Tistecose]

Ola, what's up amigos? :)
In first steps it's really good if someone supports you, so hope to meet friendly and helpful people here. Let me know if I can help you.
Thanks and good luck everyone! ;)