Unfortunately, I have only one Windows 7 / 64bit machine to try it on, but I confirm that the prescription I described worked fine for me (and I tried my phone on this laptop just now, to see if it still works). I will try to elaborate on the subject of this problem with 64 drivers below, however, please keep in mind that mine is not a professional opinion / advice, but, rather, a description of a successful experience, where I could have done something else (in addition to installing the drivers) that I didn't even realize having done. I will try now to do some diagnosing on my machine / will try to recall what else I had done before installing the drivers:
1) when Windows 7 complains about not having successfully done something, relatively often you can ignore this, as such msg could mean many things, and now, after having moved a large number of software packages from XP to 7 on many machines (sadly, only one is W7/64), I am used to this. I even got LOTR2/BFME working on W7/64bit!
2) now, assuming the drivers actually GOT installed, connect your M500 to a USB
port using the cable that came with the phone (I didn't try connecting to my phone
from W7/64 using BT, as I gave up on BT a few years ago: it's too slow, so I use cables only). See if the phone shows "USB connected" on its display.
2a) If it DOES, the drivers got installed, you can check this by going to Device Manager, which should show a new modem: see a1.jpg in the attachment
2b) if it does NOT (show the drivers), the drivers did NOT get installed. While the phone is connected, try to direct the system to locate the drivers. According to my cygwin-based search, the drivers actually came from this place in the unzipped installation graph: see a2_jpg in the attachment (btw, as is the case with non plug-and-play devices, you will have to repeat this procedure for every single USB port, in case you don't want to remember which one you used the first time you connected the phone).
Now, either you had the drivers installed already (scenario 2a)), or, if you didn't until now, you should be able to force-feed them to Windows (scenario 2b)).
3) however, to connect to SPRINT network (3G or the older one) the drivers are not enough. You need some connection manager software. Here is what I use: see attachment a_3.jpg : SPRINT connection manager 3.07.045
This utility comes from
Sprint_Broadband_Mobile.exe I found somewhere on SPRINT's web site
two years ago
Notice that the snapshot shows my phone as "disconnected" - it's because it was found being connected to a USB port, but NO modem connection was established yet (as I did not yet hit).
In case Sprint connection manager does not find your phone (i.e. if the drivers have not been successfully installed), it would show "Connect your phone or card.." msg in the same box where you see "Disconnected" in the snapshot.
4) Finally, I now vaguely recall that, before I successfully installed the drivers from the Galaxy64 package, I played with Sprint_PCS_CM_v044.msi that I found somewhere - I have no idea if that played any role in all this, because, I think, it's 32bit drivers only, however, if 1 through 3 (see above) fail, try this step 4) and then 1 through 3.
Please report back here with your experiences, as we would all greatly benefit from more info.
I downloaded usb_drives_GalaxyS_x64.zip from the Softpedia website.
Then I run the setup.exe and get a window saying "Samsung USB Driver for Mobile Phones V1.3.450.0 - MSS Install Wizard.
It gets part way through the install process and then says the install wizard was not successful. It doesn't give an error number or any indication of what the problem is.
My phone is also a M500.
Would appreciate any help.
Brooks
========
QUOTE=Masketeerion;64112]I solved the same problem by
1) downloading 64bit drivers for Samsung Galaxy from Softpedia.
2) unzipped them and then
3) told Windows 7 where to search for the drivers for both new devices
(Windows 7 / 64bit was unable to find these drivers, as my phone is Samsung M500)
In the past I successfully used this phone (as modem) with 32bit Windows 7 and 32bit XP on many computers, but had to spend several hours today trying to understand the problem (64bit system needs 64bit drivers, dude! stupid me!).
[/QUOTE]
