PDA

View Full Version : Fixed Problem with Installation and usage of 64bit SST in VISTA!!!


deifier
13th April 2007, 04:09
Hi everyone I guess it's time for me to work my miracel again.

Sorry for the delay had some problem getting a 64-bit Version of Vista.

Note! if you've tried the vista drivers you'll need to unplug PGCU and plug it back in, when asked for installation of new device just cancel so it won't install vista driver version or workaround won't work. Just figured this out!

Download these installations to get you PGCU working. Sorry everyone else but I'll get working on the rewrite to other Joysticks and such. Respond to this Message with what units are most commonly bought.

1.
http://www.dlldump.com/download-dll-files_new.php/dllfiles/D/d3drm.dll/5.1.2600.0/download.html Place this dll file in C:\Windows\SysWOW64 and C:\Windows\System32

2.
ftp://ftp.saitek.com/pub/software/pgcu/pgcu_151205_64.exe Download this PGCU software NOTE! save and not run
ftp://ftp.saitek.com/pub/software/x52pro/x52pro_171006_64.exe Download this x52Pro software NOTE! save and not run
ftp://ftp.saitek.com/pub/software/sst_171006_64.exe Download this SST. found by Seires NOTE! save and not run

3. Start installation for x52pro_171006_64.exe abort when it's been loaded. 1st cancel avalible with other words.
4. Start installation for pgcu_151205_64.exe it will say it only works with xp64.
5. Go to C:\windows\temp\saitek\ and take the Setup.exe file from the x52pro installation folder and replace the one in the PGCU folder. Erase the x52pro Folder unless that's the stick you want to install.
6. Run setup.exe which you replaced, run it from the PGCU folder at C:\windows\temp\saitek\
7. Install sst_171006_64.exe Enjoy! or Hopefully! you'll enjoy another flawless solution.



NOTE! Remember to place the d3drm.dll files before trying to install the drivers.

/Regards Deifier.

P21121970
13th April 2007, 16:41
Hi everyone I guess it's time for me to work my miracel again.

Sorry for the delay had some problem getting a 64-bit Version of Vista.

Download these installations to get you PGCU working. Sorry everyone else but I'll get working on the rewrite to other Joysticks and such. Respond to this Message with what units are most commonly bought.

http://www.dlldump.com/download-dll-files_new.php/dllfiles/D/d3drm.dll/5.1.2600.0/download.html Place this dll file in C:\Windows\SysWOW64 and C:\Windows\System32

Extract and Run setup of Saitek_PGCU_Vistax64_Hotfix then do the same with Saitek_SST_Vistax64_Hotfix and you're set :D

NOTE! Remember to place the d3drm.dll files before trying to install the drivers.

/Regards Deifier.

Damn it I have the solution but I can't give you the files because attachments can't be bigger then 1mb :( when saitek gives me and ftp to upload to or more attachment space the files will be yours.

Ouch! seemingly I jumped to the guns yesterday before having Profiled the profile I made and saved, only to find out that the file I stole to make it work made the softwares versions differ, on the problem now :(

Hi,is it worth to try this?Ore is the new 64bit Vista Version ready next days?I wait for sst 64 bit vista.

Seires
17th April 2007, 17:47
I got the SST thing working on my computer half using what Defiler had posted and browsing their support website.

I had the d3 file copied into both directories, installed the Vista 64-bit driver, but then i couldn't get the xp SST software to work on my stuff so i went playing around their FTP server and found this

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

It looks like the vista 64-bit SST software. After i installed that I was able to upload a Profile into it after the install and seems to be working flawlessly sofar.

I'm using the Saitek Gaming Keyboard, but i believe it's fully universal software. Any questions or whatever send me a PM :)

EDIT: i guess i was wrong about the software, it would work for the X36/X45, P880, P2500 and P3000, PC Dash 2/P8000 Only :/

Will still keep looking around, but seems those people with those controllers should be good...maybe :)

deifier
21st April 2007, 02:02
Now the solution on this thred WORKS :D enjoy

/Regards Deifier! :cool:

Seires
21st April 2007, 05:27
Defiler, got any tips on how i might be able to get my control pad on my Gamers Keyboard to work? I'm outta ideas but too impatient to just wait lol

DasDing
21st April 2007, 12:17
Hi Seires,
deifier edit his thread and explained his workaround.
But in my case it does not work.
I can install it.
All seems to be good i can assign a key.
But to activate the profile for an aplication in german menu "profile nun"
there is a mistake.
I can not use it
regards

DasDing
21st April 2007, 15:06
Hi deifier,
thank you for your work.
I try this but I have the same mistake.
I deinstall and make your work around withe the same result.
Your command unit works?
you try it in the editor?
Thanks

deifier
21st April 2007, 15:44
Yeah mine works perfectly. :D Flawless!

To bad your doesn't that's a consern, would like everyone else whom it doesn't work for to post here aswell because then it might be one step which I left out or something, not that I can figure out what it is now :( Keep me posted on faliure and sucess stories on this workaround.

Is your problem that you still can't profile the profile made ? or you can't make a profile without crash ? or you can't run the SST setup at all ?

/regards Deifier

DasDing
21st April 2007, 16:11
Thank you Deifier for your work.
I can not profile the profile i made.
No crash but the message in german "test.dat beinhaltet kein profil
für das Gerät"
I try to translate "test.dat is not a profil for this device"
All other works fine, but without profiling i can not use it.
Thanks

deifier
21st April 2007, 16:21
Look at this screen for proof of this solution working!

DasDing
21st April 2007, 16:40
Hi Deifier ,
i believe that your command unit works.
But I do not know why my does not work.
I see you edited your post with point 9.
I do point 9 with the same result.
I cannot profile the profile i made.
I see in my device manager an error
Thank you for your work deifier I hope that other command units also work.

Thanks

deifier
21st April 2007, 19:21
The problem as it seems to me is this that the version of the SST software and the Drivers are not compatible, this makes the SST profiler not being able to Profile the profile made... don't know why it works for me. Have you tried the lastest solution I brought ? I've edited the main post 4 times.

IST_KeleSSaR
21st April 2007, 22:08
don't work for me too

project6
21st April 2007, 23:17
Can't get it to work following this guide either... :( Hats off for Deifier though, I'm really glad it works for you mate.

If the entire Saitek team worked with half your skill we wouldn't be sitting on this forum waiting for the new SST everyday; we could've used a "temporary patch" like this one until new and updated software is out.

Edit: "The device has not been profiled" error is what I'm getting in case you're debugging... The install steps work fine, but it can't apply a profile I created.

deifier
22nd April 2007, 02:39
Do something for me, check to following. right-click your profiler, go to control panel, and press about.

Versions should be the following:

Driver Version: 5.5.0.82
Software Version: 4.3.4.17

Report back.

Note! if you've tried the vista drivers you'll need to unplug PGCU and plug it back in, when asked for installation of new device just cancel so it won't install vista driver version or workaround won't work. Just figured this out!

/Regards Deifier

spads
22nd April 2007, 03:51
Just installed as per instructions above, and works perfectly :D

Thanks Deifier
:D :D

deifier
22nd April 2007, 04:40
Now that this Post is proven working, HASTA LA "VISTA" Baby :cool:

project6
22nd April 2007, 12:22
Yep, works great now. Just removed everytrace of my PGCU before I followed this guide.

(Plug in your PGCU, go to the devicemanager and delete everything that says something with Saitek. Also check "remove driver" when prompted.)

Don't know what's left to say... Deifier > Saitek

IST_KeleSSaR
22nd April 2007, 13:14
i did this too,but don't work.......What i am doing wrong?:mad:


P.D:hay alguien que hable español y me lo pueda explicar¿? gracias

deifier
22nd April 2007, 13:28
Sorry ist, but my spanish isn't that good so I can translate the steps for you. :( Going to work on it though once in the US.

IST_KeleSSaR
22nd April 2007, 13:39
ok

in the step 5 (and take the Setup.exe file from the x52pro installation folder and replace the one in the PGCU folder. Erase the x52pro Folder unless that's the stick you want to install.)

I do this but driver does not install it

if I have driver that it installs Windows to me says to me that it is not possible to be installed and if I do not have driver of Windows has left the congealed screen

I have windows vista 64 bit ultimate edition intel pentium dual core 2 duo E6400 3 gb ram and 8800gts 640mgb and pro game comander unit

deifier
22nd April 2007, 14:08
Why you need to take the setup.exe file from the x52pro installation in the C:\windows\temp\saitek\

is the following.

The setup.exe file from the original PGCU installation won't work with Vista-64bit.

This was why I put this thread to rest in the begning btw.

but it's just a setup.exe which install files so you take it from it's files in the x52pro folder and replace the setup.exe that won't start in your PGCU unit folder. then delete the x52pro folder so it won't mix up the files, which i prob. wouldn't anyway but to be on the safe side i wrote that. the when you run the setup.exe that we stole from the installation meant for x52pro flight stick we now use it to install the files for the Pro Gamer Command Unit. Simple :D

IST_KeleSSaR
22nd April 2007, 14:24
ok i understood you but whe i do this don't leave me install the drivers


i do this

i go C:\WINDOWS\Temp\Saitek\Saitek_X52Pro_Flight_Contro ller_Drivers\00000012\setup.exe

get this archive and replace in

C:\WINDOWS\Temp\Saitek\Saitek_Pro_Gamer_Command_Un it_Drivers\00000013\here replace the setup.exe

and erase x52 pro folder this way¿?



C:\WINDOWS\Temp\Saitek\ becase in this folder there isn't any setup.exe:confused: :confused:

project6
22nd April 2007, 15:45
You should have two folders in c:\windows\temp\saitek.

One x-52 and one PGCU. Take the setup.exe from x-52, and place in pgcu.

If you dont have two folders there, just delete c:\windows\temp\saitek and start the guide from scratch.
Remember to place the .dll files in windows' folders as well.

You shouldn't be placing anything in c:\windows\temp\saitek. It's just a pointer to where the two folders are located.

Also make sure you removed any trace of old drivers and/or SST software before you attempt this guide. It wont work with the Vista drivers preinstalled, for example.

This thread should be sticky, cause it provides a complete working solution for the PGCU in Vixta x64 enviroment.

IST_KeleSSaR
22nd April 2007, 16:07
thank you for all but not work's for me

I eraser all drivers and all sst programing in my cp
I place .dll in folder SysWOW64 and system32
I do step by step this guide

but nothing I can't make work it :(


thank you for all

DasDing
22nd April 2007, 21:19
Hi deifier,
thanks a lot.
I read the post from project.
I deinstall all saitek drivers and then I try the workaround.
But I have a problem when I try point
6. Run setup.exe which you replaced, run it from the PGCU folder at C:\windows\temp\saitek\
I have a mistake by the installation
I try to install manual the driver in the device manager
You see the result
I can change the HID driver to versions "vista" 6.0.2.123
then i can start SST but i cannot profile the profil i made
or i can use HID xp 64 5.5.0.82
with the result you see below.
maybe it is my usb mouse
regards

deifier
23rd April 2007, 00:18
unplugg your PGCU to get Rid of you Vista version drivers it's of no use so far. then try to workaround again. driver versions are to be

Driver Version: 5.5.0.82
Software Version: 4.3.4.17

When you right click your joystick icon at your taskbar. then go to controlpanel then about. to check it.

Unless your driver versions are these following you've failed, and failed good on applying the workaround, either by forgetting to unplugg the usb PGCU cord to erase all drivers version after having tried to install "saitek's official vista drivers" or others. Or messing up the placing of the d3drm.dll files,

or not being able to understand that the setup.exe file that can be extracted from the x52pro installation folder after having it cancelled the installation at first possible cancel point, so that it leaves an installation catalog in c:\windows\temp\saitek\ directory, to then copy the setup.exe file to replace the setup.exe file that exists in the pro_gamer_command_unit folder made by trying to use the installation that wouldn't go through because of it not being compatible with vista64.

/so there are a few pointers.

/Regards Deifier

Athalus
23rd April 2007, 09:37
When i install i get SAI3DVIEWER.dll could not self-register. or missing


when i try to do anything with the Profiler editor it just shouts down and massage "Profile editor is not working" bad translation from swedish


EDIT: Got it to work now. Deifier ur a god in fixes

fatty84
23rd April 2007, 12:25
Thanks, Deifier, for trying to help. I followed the instructions (after removing every trace of old drivers of course) but installation freezed in the middle as it could not regconize my P2500 Rumble Pad. So I started it all again, this time used the XP64 driver for the P2500 (p2500_151205_64) instead of the XP64 PCGU one (pcgu_151205_64). Now the installation went okay and everything but I could not profile the profiles I made. Error message received is: "xxxx.dat does not contain a profile for this device. Device has not been profiled".
Have you any suggestions of what went wrong?
Q.

IST_KeleSSaR
23rd April 2007, 15:51
this is what it happens to me


if install it x52 pro driver in folder PGCU, the version driver is 5.0....but I go the device manager in saitek pro gamer comand unit(HID) it apears an icon yelow and not detectec the gamepad



if I install the SST software says to me that it does not find the device



there are several versions of Vista ULTIMATE 64 bit?
it can be that the WINDOWS version influences ¿?

deifier
23rd April 2007, 16:33
fatty48 the profiling issue comes from a version differ between drivers, and sst software.

note' why this software version differ works when i comes to the fix for PGCU is because the SST programing and the x52pro installation files setup.exe do not differ. altough what it installs differs.

And as far as I've seen on their ftp there is not P2500 driver version that matches the SST program I provided, however.

try using this old SST and maybe it will work
ftp://ftp.saitek.com/pub/software/sst_151205_64.exe
this sst will say it doesn't work to install in vista as it is meant for XP64
however it leaves an installation catalog in C:\windows\temp\saitek\somthing? and if you go to the core catalog of that catalog you'll be able to use the setup.exe there to install it.

and if this doesn't work I'm out of guesses :( another thing did you need to replace the setup.exe for the P2500 to be able to install it (with the one from x52pro installation)?

DasDing
23rd April 2007, 20:27
Hi folks,
I tried the workaround several times without success.
Perhaps it is my vista version.
The saitek usb driver is ok but the saitek hid driver cannnot work.
regards.

fatty84
23rd April 2007, 23:17
deifier, in my previous post I failed to mention that I had also tried the old SST with no luck. I used the same method for both driver and SST i.e. used the setup.exe extracted from Vista64 files to install the XP64 version. Same error message received.

Well, I guess I will have to wait for the official release then.
Thank you anyway.

project6
24th April 2007, 12:30
I couldn't get it to work at first either, I went into device manager and selected every Saitek bit in there and pressed DELETE. Then I rebooted, and went from scratchfollowing the guide. Works well.

So basicly I didn't unplug my controller - I left it plugged in and went into device manager (so I can see the units in there) and manually deleted them all. Then I rebooted and started over.

I'm sorry I can't be of more assistance, but that's all I did. I can't stress enough how important it is to remove earlier installations.

I doubt the differences in Vista versions has anything to do with it... Basicly, it's the same software with different "unlocked" services and applications.