MSI Star Key 2.0 & Windows XP x64

Hi,
I have Star Key 2.0 and it's working fine with Windows XP x64. I'm using Microsoft's Bluetooth Stack and it's not supporting Headset profile for example. I can use Widcomm stack with my dongle when using Windows XP, 32-bit version, am I right? Is it possible to use Widcomm stack with x64?
- Matti P

Ok. I found 64-bit Widcomm stack (5.0.1.2500). I installed it, but it won't work with my dongle. Stack tells me the following message "Your Bluetooth software license does not include use with this Bluetooth device.[6]". So, I tried to use license file which is located install CD and got the following message "You cannot install an older version of Bluetooth Software over a newer version of Bluetooth Software. [-349]" I suppose that the license file is for Widcomm 4.0 stack, and it is not working with the 5.0 stack. I did a fast search and did not find 64-bit version of the 4.0 stack.

Similar Messages

MSI Star Key on Windows 7

Hello!
I have a bluetooth usb device since 2005, back then I used to have windows xp and it worked very well, now I have win7 32 bits and I'm having troubles with the installation, driver is not supported.
The device is the MSI star key v 1.0. How can I get the right drivers??
Regards!

Topic split and renamed.
This is a very old device now, and MSI does not provide Windows 7 drivers.
Its possible that drivers are already included with Windows 7, have you tried letting Windows Update find drivers for you?
Alternatively you could give the Vista 32bit drivers a try, they may just work (Windows XP drivers won't):
http://eu.msi.com/product/net/STAR-KEY.html#/?div=Driver&os=Vista%2032

Msi star key 2.0 3x faster wireless network adapter with windows 7

Hi,
I have msi star key 2.0 3x faster wireless network adapter product. Could anyone please provide me information whether it is compatible with both 32-bit and 64-bit Windows 7 operating system? Thanks in advance.

Quote from: tempaccount1234 on 05-April-11, 19:27:06
Could anyone please provide specific information? Will the Vista drivers work for Windows 7. I am not able to use them. Is there any setting required? Please help......
No Vista drivers often do not work in W7.
You better buy a new device that has W7 drivers.

MSI Star key 3x fatser, license does not include device !!!

Dears,
I have my MSI star key bluetooth device from 1.5 years, it was working perfect on my windows XP SP2. Then I had some problems with my windows, and I wanted to re-install again the driver (after de-installing the current driver) but I found myself getting the following message, when I try to start the bluetooth device:
"your bluetooth software license does not include use with this bluetooth device. [6]", and when I point out to my CD for the license file, I get this message "Bluetooth software license file not found. [2]".
I have tried the driver coming with the device CD WIDCOMM version 4.0.1.2101 and was working for more than 1 year, and also I have tried the new driver on http://global.msi.com.tw/index.php?func=downloaddetail&type=driver&maincat_no=131&prod_no=101 WIDCOMM version 4.0.1.2900 several times with lots of combination and nothing is working, the bluetooth is still red and refuse to start.
I found the same issue is posted too much over the web regarding the WIDCOMM software in general and solution with something as patch I could not find.
I checked the fixed posting on this forum, but it seems all included URLs in the posting are not working.
It seems that contacting MSI support is a waste of time. Could anyone provide guidance or help for me.
Thanks in advance

Quote
It seems that contacting MSI support is a waste of time.
Have you even tried? Visit http://ocss.msi.com.tw, enter your email address and open a new ticket.

Registration and MSI Drivers for MSI STAR KEY 3

First of all for some strange reason i cannot register my star key 3 which i bought at 23/03/2010 from www.e-shop.gr, i have send to MSI the photo with the serial number.Second, clearly in the manual refers about a software driver CD which was not included in my package! I have searched the MSI site for an MSI driver and it has only for STAR KEY 1 and 2 ,not for STAR KEY 3! Currently i have the driver that Windows XP service pack 3 installed but as i saw from previous models STAR KEY 1 and 2 ,the MSI driver has more features.To anyone who has MSI STAR KEY 3, did MSI included a driver CD in the package?

Even though I can understand your frustration, you need to understand a few things in order to take the next steps in this matter:
First:
The BlueSoleil package is not an MSI Product but a piece of bundled third party software that comes with the package. It is kind of like buying a CD/DVD Burner and getting a CD that contains Nero Burning ROM and a valid license for the particular Nero Version on that CD. Now let's say: That this "older" Nero Version does not work very well with Windows 7 64bit (because it was concipated for older Windows Versions). Who do you blame for that? The manufacturer of the optical drive? When you contact the software company behind Nero about that, they will tell you exactly the same thing as BlueSoleil did: Buy a newer version! Now, please don't tell me, that will start complaining about the manufacturer of the optical drive about an outdated Nero Version.
Second:
Quote
I bought this device a couple of months ago, so its not even a very old one!
Just because you bought this device only recently in some shop, that does not mean that it is brand new (the shop could have had that thing in stock for a couple of years already).
In fact, the device is at least 3 years old (if not older) and is officially advertised as supporting the 32bit versions of Windows 2000, Windows XP and even Windows Vista. Windows 7 was not even on the market back then and therefore there was also no possibility of including a copy and a license for a Windows 7-ready Bluesoleil version. There is an old version of the bundled/third party BlueSoleil Software on there because the product was put out on the market more than three years ago. In case the people in that shop you bought the device in told you any different, they did not really provide very good advice.
Quote
the ability to contact the real MSI Support
... exists here: http://support.msi.com/
However, MSI will most probably be able to help you with getting your hands on a free up-to-date Bluesoleil version (just like the optical drive manufacturer who will not provide you with a free copy/license of the latest Nero Release).
Quote
I also tried to register the product but the registration page says: "not MSI product" BAHH!!! WHYY??
What page exactly? Do you have a link?
Quote
I have the serial number
Did you enter the serial number of the device or the serial number for the BlueSoleil Software Version that came with it?

Msi star key 2.0

I have bluetooth dongle MSI Star Key 2.0 with original Widcomm drivers. By which functions and how can I find devices in range of dongle and connect to it by using this driver through SPP prifile. I am creating my aplication in Visual C++. Can anybody help me with this?

Quote from: tempaccount1234 on 05-April-11, 19:27:06
Could anyone please provide specific information? Will the Vista drivers work for Windows 7. I am not able to use them. Is there any setting required? Please help......
No Vista drivers often do not work in W7.
You better buy a new device that has W7 drivers.

Star Key 3.0 max current

Hi there,
Does anyone know what the maximum current of the Star Key 3.0 is? I'll be needing to use it on an extremely low power system (5V 3A) and need to verify power consumption on any components I use on it.

Quote from: badboy2k on 16-November-12, 13:18:56
MSI Star Key 3.0
Power Consumption from 5V input:
Tx Typical: 128mA (.128A)
Rx Typical: 68mA (.068A)
Standby Mode: 52mA (.052A)
That's it! Thanks so much! :-D

[GeForce 6] nx6600gt-vtd128 vivo driver for windows xp x64 edition?

Are there any (beta or release) wdm driver for this msi's nx6600gt-vtd128 for windows xp x64 edition? If not, are there plans to make an x64 driver in the near future?

I have the same card, and i can't find ANY capture driver for it. Not even the WindowsXP 32-Bit.
Could you enlighten me on where exactly did you see the 32bit capture drivers? (Other than the MSI CD)
EDIT:
Now I noticed you said NVDIA's Website, they're even older than the ones MSI provided on the CD. Older by like 2 years.
What I'm looking for, is a place where I can find fresh new WDM drivers. Or at least an online package of what's on the CD
Drivers should not be availiable only on a CD.

MSI MEDIA LIVE (ATI HD 3200) - Flickering/unstable in Windows 7 (x64?)

I am having a new virgin install problem (after upgrading the processor) the problem may be x64.
Story: Well, this is a MSI Media Diva motherboard MS-7411 and I had to install Windows 7 x86 (32-bit) in order to be able to update the BIOS to 1.3 to accept the new AMD quad processor (Phenon II X4 905e) that I was contemplating for the build.
Windows 7 x86 showed cleanly and stable with no video flicker. The BIOS update went smoothly, and then I did a clean install of Windows 7 but installed x64 (64 bit) his time instead of x86 (32-bit).
At first the boot screen seemed stable, but on the desktop it flickered constantly (with black lines). I did some updates and installed the ATI driver software and the correct monitor profile and it seems to flicker less, but it still seems like an unstable image at a minute level (that is the screen is not solid, there are little jaggy flickers throughout like radio interference).
When there were black bar flickers swore it flickered in response to some interference from another device - or at least that's what it seems like to me.
Set-Up:
MSI Media Live DIVA MS-7411 motherboard
. North Bridge: AMD® 780M
. South Bridge: AMD® SB700
ATI Mobility Radeon HD 3200
Phenom II X4 905e Processor
G.Skill F2-640-CL4D-4GBPK PC2-6400 (2 x 2GB DDR2-800) Dual Channel Memory
BIOS AMI 1.34 (most recent) - Optomized Defaults
Intel 40GB SSD is the main HD with the OS (SATA), + 1TB WD Green HDD (for media) (SATA) + LG DVD Multi-drive (SATA)
Monitor Samsung SyncMaster 215TW (same flicker whether I use VGA or Component Out)
ATI Catalyst 10.1 for Windows 7 (x64) Suite installed.
There was a point where it seemed more stable and was giving me a dialogue saying that the Catalyst Control Panel was not for my version video driver (and that may have been with the Windows 7 default driver install.
I would prefer to run x64 for personal reasons and to take advantage of more RAM.
I may try doing a fresh install of Win7 x86 32 bit and see if the problem goes away again
- but I hate having to do this experimentaiton on my SSD.
Any ideas or similar experiences? Thank you in advance.

64bit Windows not some logical step to follow if you don't have 64bit software that you need to run.
64bit CPU's have been around for a long time, yet Microsoft never bothered to do anything with it, with as result it's just starting where Linux/Unix started 20 years ago.
That is why they are stable with it and Windows is not, also they maintain a completely different OS model and they have 99.99% of the source-code of all programs.
And it's still not a priority for Microsoft, as they maintain 32bit versions just the same, but no software in 64bit versions that is worth switching for.
32bit has trouble free drivers and software, no wonder, they had decades to perfect 2000, XP, (Vista)W7...however, 64bit Windows is a wormhole, best left to be untouched until you explicitly need it.
As for running 64bit Windows with 32bit software it's NOT faster, NOT as stable and NOT as compatible.
Looks enough reason for me....

MSI GE60 2OC Windows 7 x64 USB 3.0 eXtensible Host

Hi,
I have another problem with my MSI GE60.
I have installed Windows 7 x64, updated everything and installed driver.
At last I installed the USB 3.0 eXtensible Host Controller driver from the msi homepage. But now my usb ports aren't working anymore!
I tried different driver and deleted them in safe mode from windows.
Help? ...
Thanks in advance

I just posted a similar issue on the same machine, except my USB ports will only work under certain circumstances. It's very odd and it sounds like a driver issue... Did you ever get it sorted out?

MSI 785GT-E63 & Windows 7 x64 : Cool'n'Quiet

Hello,
Can you help me to configure my mainboard to active Cool'n'Qiet and Windows 7 x64.
I have Cool'n'Quiet : Enable in my Bios.
I have follow this method for Windows : http://www.vista4beginners.com/power-management
But my problem is that my CPU fan isn't lower.
I have try with "Dual Core Center" and it's work in "Silence mode" but i don't know how configure it to auto launch in "Silence mode"
I will prefere using Cool'nQuiet without other software like "Dual Core Center" but if there aren't other solution i will use it.
Thanks for reply.
Excuse me for my English : a litthe frenchy
Config :
MainBoard : MSI 785GT-E63
CPU : AMD DUAL CORE - X2 7750 oem 2.7GHz L2 1Mo et L3 2Mo 95Watts socket AM2+
CPU FAN : ZALMAN - CNPS9300 AT
Mem : 4 Go ( 2x KINGMAX - DIMM - 2 Go - PC - 8500 1066 MHz - KLEE88F-B8KB5 )
Disk : Raid1 : 2x HITACHI DESKTAR - P7K500 - 500 Go IDE - 7200t - 8 Mo cache
OS : Windows 7 x64

Quote from: Bas on 23-October-09, 20:14:59
Go into the BIOS and look for Smartfan or SmartFantarget, something like that.
Enable it and set the right values.
That does normally the fan controlling.
Thanks but, what are the right values ?

Crystal Reports 2008 in Windows Vista x64 + IIS7 DOESNT WORK!!!!!! HELP!

Hi,
I´m developing an application with Microsoft Visual Studio 2008 and Crystal Reports 2008 Professional
(i´m not using the Crystal Reports 2008 for .Net basic)
As I have Windows Vista x64, my ASP.NET applications run under IIS7, but for my surprise, Crystal doesn´t work under Vista x64 + IIS7. I got the following error:
An error has occurred while attempting to load the Crystal Reports runtime. Either the Crystal Reports registry key permissions are insufficient, or the Crystal Reports runtime is not installed correctly. Please install the appropriate Crystal Reports redistributable (CRRedist*.msi) containing the correct version of the Crystal Reports runtime (x86, x64, or Itanium) required. Please go to http://www.businessobjects.com/support for more information.
When I run the same routine in an Windows Application the error doesnt occur. It only happens under Web Applications.
I tested in a Windows Vista 32 bit and there´s no error....
Crystal Reports 2008 does not work in II7 x64 ?
Is there any solution?
Please.... help me!!!!!

Hi Fernando,
Please read and follow the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] for future topic posts as yours violates the current policy.
You will need to build your application to run in 32 bit only mode. This note explains how to do it:
[Set app to 32 bit mode|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do]
Jason

Is AIR 3.3 compaible with Windows 7 x64?

I downloaded AIR 3.3 and installed it. from the downloaded site, it says that a version is available for windows 7 x32. I have extensions in dreamweaver that won't work and AIR is the suspected cause according to the developer. I have windows 7 x64 and using CS5.5. I can't get the sample extensions off of the Adobe website to work either. Adobe tech support denies that it might be a problem with their software. I have also tried to run it in compatibility mode and tested the extensions, but can't complete those installs without a properly functioning AIR. The extensions are Zpose photo gallery and TourDeFlex. Anyone else having the same issues?

Not sure how to do that. I tried to follow the instructions on the link that you provided, but it doesn't tell me how. I search the Adobe site for AIR Installer Log. I tried to follow the instructions for creating and copying the log, but it tells me to type in cd\documents and settings\userName. I am using windows 7 x64. documents is one folder and settings is another. I keep getting an error message in DOS that says "cannot find the path specified. I also did a search for AIR 3.3 on my system and the only place that it shows up is in the downloads folder. I would assume that if it were installed correctly, it would show up in either program files or program files (x86) folders. Is there another wahy to create and copy an installation log?
I don't know if this is what you are looking for or if this helps, but this temp file was created when I tried to instal AIR 3.3. I found the "setup" file. When I clicked on it, It says "Could not access network location (computed)." Here is the log file that was created:
=== Verbose logging started: 8/8/2012 23:10:07 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\System32\msiexec.exe ===
MSI (c) (34:20) [23:10:07:720]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (34:20) [23:10:07:720]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (34:8C) [23:10:07:806]: Resetting cached policy values
MSI (c) (34:8C) [23:10:07:806]: Machine policy value 'Debug' is 0
MSI (c) (34:8C) [23:10:07:806]: ******* RunEngine:
           ******* Product: C:\Users\STEWAR~1\AppData\Local\Temp\AIRFCB1.tmp\setup.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (34:8C) [23:10:07:810]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (34:8C) [23:10:07:940]: Cloaking enabled.
MSI (c) (34:8C) [23:10:07:940]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (34:8C) [23:10:07:961]: End dialog not enabled
MSI (c) (34:8C) [23:10:07:961]: Original package ==> C:\Users\STEWAR~1\AppData\Local\Temp\AIRFCB1.tmp\setup.msi
MSI (c) (34:8C) [23:10:07:961]: Package we're running from ==> c:\Windows\Installer\3a8771b.msi
MSI (c) (34:8C) [23:10:07:990]: APPCOMPAT: Uninstall Flags override found.
MSI (c) (34:8C) [23:10:07:990]: APPCOMPAT: Uninstall VersionNT override found.
MSI (c) (34:8C) [23:10:07:990]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (c) (34:8C) [23:10:07:990]: APPCOMPAT: looking for appcompat database entry with ProductCode '{65CB4C08-C47B-4A7E-A6A4-50C06ADA5FC6}'.
MSI (c) (34:8C) [23:10:07:990]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (34:8C) [23:10:08:010]: MSCOREE not loaded loading copy from system32
MSI (c) (34:8C) [23:10:08:013]: Machine policy value 'DisablePatch' is 0
MSI (c) (34:8C) [23:10:08:013]: Machine policy value 'AllowLockdownPatch' is 0
MSI (c) (34:8C) [23:10:08:013]: Machine policy value 'DisableLUAPatching' is 0
MSI (c) (34:8C) [23:10:08:013]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (c) (34:8C) [23:10:08:013]: Enabling baseline caching for this transaction since all active patches are MSI 3.0 style MSPs or at least one MSI 3.0 minor update patch is active
MSI (c) (34:8C) [23:10:08:014]: APPCOMPAT: looking for appcompat database entry with ProductCode '{65CB4C08-C47B-4A7E-A6A4-50C06ADA5FC6}'.
MSI (c) (34:8C) [23:10:08:014]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (34:8C) [23:10:08:014]: Transforms are not secure.
MSI (c) (34:8C) [23:10:08:014]: Note: 1: 2205 2: 3: Control
MSI (c) (34:8C) [23:10:08:014]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Users\STEWAR~1\AppData\Local\Temp\MSI905e5.LOG'.
MSI (c) (34:8C) [23:10:08:014]: Command Line: CURRENTDIRECTORY=C:\Users\STEWAR~1\AppData\Local\Temp\AIRFCB1.tmp CLIENTUILEVEL=0 CLIENTPROCESSID=6964
MSI (c) (34:8C) [23:10:08:014]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{6FD5434C-027F-46C2-9662-0F725FC2454D}'.
MSI (c) (34:8C) [23:10:08:014]: Product Code passed to Engine.Initialize:           '{65CB4C08-C47B-4A7E-A6A4-50C06ADA5FC6}'
MSI (c) (34:8C) [23:10:08:014]: Product Code from property table before transforms: '{65CB4C08-C47B-4A7E-A6A4-50C06ADA5FC6}'
MSI (c) (34:8C) [23:10:08:014]: Product Code from property table after transforms: '{65CB4C08-C47B-4A7E-A6A4-50C06ADA5FC6}'
MSI (c) (34:8C) [23:10:08:014]: Product registered: entering maintenance mode
MSI (c) (34:8C) [23:10:08:014]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (c) (34:8C) [23:10:08:014]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (c) (34:8C) [23:10:08:014]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (c) (34:8C) [23:10:08:015]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (34:8C) [23:10:08:030]: Specifed source is not already in a list.
MSI (c) (34:8C) [23:10:08:030]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (34:8C) [23:10:08:030]: Machine policy value 'DisableBrowse' is 0
MSI (c) (34:8C) [23:10:08:030]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (c) (34:8C) [23:10:08:030]: Adding new sources is allowed.
MSI (c) (34:8C) [23:10:08:037]: Package name retrieved from configuration data: 'setup.msi'
MSI (c) (34:8C) [23:10:08:037]: Note: 1: 2205 2: 3: Error
MSI (c) (34:8C) [23:10:08:038]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (c) (34:8C) [23:10:08:038]: Machine policy value 'DisableMsi' is 0
MSI (c) (34:8C) [23:10:08:038]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (c) (34:8C) [23:10:08:038]: User policy value 'AlwaysInstallElevated' is 0
MSI (c) (34:8C) [23:10:08:038]: Product {65CB4C08-C47B-4A7E-A6A4-50C06ADA5FC6} is admin assigned: LocalSystem owns the publish key.
MSI (c) (34:8C) [23:10:08:038]: Product {65CB4C08-C47B-4A7E-A6A4-50C06ADA5FC6} is managed.
MSI (c) (34:8C) [23:10:08:038]: Running product '{65CB4C08-C47B-4A7E-A6A4-50C06ADA5FC6}' with elevated privileges: Product is assigned.
MSI (c) (34:8C) [23:10:08:038]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\Users\STEWAR~1\AppData\Local\Temp\AIRFCB1.tmp'.
MSI (c) (34:8C) [23:10:08:038]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '0'.
MSI (c) (34:8C) [23:10:08:038]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '6964'.
MSI (c) (34:8C) [23:10:08:038]: TRANSFORMS property is now:
MSI (c) (34:8C) [23:10:08:038]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
MSI (c) (34:8C) [23:10:08:038]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '200'.
MSI (c) (34:8C) [23:10:08:039]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\AppData\Roaming
MSI (c) (34:8C) [23:10:08:039]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\Favorites
MSI (c) (34:8C) [23:10:08:039]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (c) (34:8C) [23:10:08:039]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\Documents
MSI (c) (34:8C) [23:10:08:039]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (c) (34:8C) [23:10:08:040]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\Recent
MSI (c) (34:8C) [23:10:08:040]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\SendTo
MSI (c) (34:8C) [23:10:08:040]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\Templates
MSI (c) (34:8C) [23:10:08:040]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (c) (34:8C) [23:10:08:040]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\AppData\Local
MSI (c) (34:8C) [23:10:08:041]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\Pictures
MSI (c) (34:8C) [23:10:08:041]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (c) (34:8C) [23:10:08:041]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (c) (34:8C) [23:10:08:041]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (c) (34:8C) [23:10:08:041]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (c) (34:8C) [23:10:08:041]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (c) (34:8C) [23:10:08:042]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (c) (34:8C) [23:10:08:043]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (c) (34:8C) [23:10:08:043]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (c) (34:8C) [23:10:08:043]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (c) (34:8C) [23:10:08:043]: SHELL32::SHGetFolderPath returned: C:\Users\StewartElectricAdmin\Desktop
MSI (c) (34:8C) [23:10:08:044]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (c) (34:8C) [23:10:08:044]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
MSI (c) (34:8C) [23:10:08:045]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (c) (34:8C) [23:10:08:050]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
MSI (c) (34:8C) [23:10:08:050]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
MSI (c) (34:8C) [23:10:08:050]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (c) (34:8C) [23:10:08:050]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (c) (34:8C) [23:10:08:050]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'StewartElectricAdmin'.
MSI (c) (34:8C) [23:10:08:050]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (c) (34:8C) [23:10:08:050]: PROPERTY CHANGE: Adding COMPANYNAME property. Its value is 'Hewlett-Packard'.
MSI (c) (34:8C) [23:10:08:050]: PROPERTY CHANGE: Adding Installed property. Its value is '00:00:00'.
MSI (c) (34:8C) [23:10:08:050]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'c:\Windows\Installer\3a8771b.msi'.
MSI (c) (34:8C) [23:10:08:050]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'C:\Users\STEWAR~1\AppData\Local\Temp\AIRFCB1.tmp\setup.msi'.
MSI (c) (34:8C) [23:10:08:050]: Machine policy value 'MsiDisableEmbeddedUI' is 0
MSI (c) (34:20) [23:10:08:072]: PROPERTY CHANGE: Adding VersionHandler property. Its value is '5.00'.
MSI (c) (34:20) [23:10:08:073]: Note: 1: 2205 2: 3: ControlEvent
MSI (c) (34:20) [23:10:08:073]: Note: 1: 2205 2: 3: ControlCondition
MSI (c) (34:20) [23:10:08:073]: Note: 1: 2205 2: 3: EventMapping
MSI (c) (34:20) [23:10:08:073]: Note: 1: 2205 2: 3: UIText
MSI (c) (34:20) [23:10:08:073]: Note: 1: 2205 2: 3: TextStyle
MSI (c) (34:20) [23:10:08:076]: Note: 1: 2205 2: 3: Dialog
=== Logging started: 8/8/2012 23:10:08 ===
MSI (c) (34:8C) [23:10:08:076]: Note: 1: 2205 2: 3: PatchPackage
MSI (c) (34:8C) [23:10:08:076]: Machine policy value 'DisableRollback' is 0
MSI (c) (34:8C) [23:10:08:076]: User policy value 'DisableRollback' is 0
MSI (c) (34:8C) [23:10:08:076]: PROPERTY CHANGE: Adding UILevel property. Its value is '5'.
MSI (c) (34:8C) [23:10:08:077]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (c) (34:8C) [23:10:08:077]: Doing action: INSTALL
MSI (c) (34:8C) [23:10:08:077]: Note: 1: 2205 2: 3: ActionText
Action 23:10:08: INSTALL.
Action start 23:10:08: INSTALL.
MSI (c) (34:8C) [23:10:08:079]: UI Sequence table 'InstallUISequence' is present and populated.
MSI (c) (34:8C) [23:10:08:079]: Running UISequence
MSI (c) (34:8C) [23:10:08:079]: PROPERTY CHANGE: Adding EXECUTEACTION property. Its value is 'INSTALL'.
MSI (c) (34:8C) [23:10:08:079]: Doing action: FindRelatedProducts
MSI (c) (34:8C) [23:10:08:079]: Note: 1: 2205 2: 3: ActionText
Action 23:10:08: FindRelatedProducts. Searching for related applications
Action start 23:10:08: FindRelatedProducts.
MSI (c) (34:8C) [23:10:08:079]: Skipping FindRelatedProducts action: not run in maintenance mode
Action ended 23:10:08: FindRelatedProducts. Return value 0.
MSI (c) (34:8C) [23:10:08:079]: Doing action: ValidateProductID
MSI (c) (34:8C) [23:10:08:079]: Note: 1: 2205 2: 3: ActionText
Action 23:10:08: ValidateProductID.
Action start 23:10:08: ValidateProductID.
Action ended 23:10:08: ValidateProductID. Return value 1.
MSI (c) (34:8C) [23:10:08:079]: Doing action: CostInitialize
MSI (c) (34:8C) [23:10:08:079]: Note: 1: 2205 2: 3: ActionText
Action 23:10:08: CostInitialize. Computing space requirements
Action start 23:10:08: CostInitialize.
MSI (c) (34:8C) [23:10:08:080]: Machine policy value 'MaxPatchCacheSize' is 10
MSI (c) (34:8C) [23:10:08:080]: Baseline: Sorting baselines for {65CB4C08-C47B-4A7E-A6A4-50C06ADA5FC6}.
MSI (c) (34:8C) [23:10:08:080]: Baseline: New baseline 3.3.0 from transaction.
MSI (c) (34:8C) [23:10:08:080]: Baseline: Sorted order Native: Order 0.
MSI (c) (34:8C) [23:10:08:080]: Baseline Data Table:
MSI (c) (34:8C) [23:10:08:080]: ProductCode: {65CB4C08-C47B-4A7E-A6A4-50C06ADA5FC6} Version: 3.3.0 Attributes: 0 PatchId: Native BaselineId: -2147483648 Order: 0
MSI (c) (34:8C) [23:10:08:080]: Baseline File Table:
MSI (c) (34:8C) [23:10:08:134]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is 'C:\'.
MSI (c) (34:8C) [23:10:08:134]: PROPERTY CHANGE: Adding CostingComplete property. Its value is '0'.
Action ended 23:10:08: CostInitialize. Return value 1.
MSI (c) (34:8C) [23:10:08:134]: Doing action: FileCost
MSI (c) (34:8C) [23:10:08:134]: Note: 1: 2205 2: 3: ActionText
Action 23:10:08: FileCost. Computing space requirements
Action start 23:10:08: FileCost.
MSI (c) (34:8C) [23:10:08:135]: Note: 1: 2205 2: 3: MsiAssembly
MSI (c) (34:8C) [23:10:08:135]: Note: 1: 2205 2: 3: Class
MSI (c) (34:8C) [23:10:08:135]: Note: 1: 2205 2: 3: Extension
MSI (c) (34:8C) [23:10:08:135]: Note: 1: 2205 2: 3: TypeLib
Action ended 23:10:08: FileCost. Return value 1.
MSI (c) (34:8C) [23:10:08:135]: Doing action: CostFinalize
MSI (c) (34:8C) [23:10:08:135]: Note: 1: 2205 2: 3: ActionText
Action 23:10:08: CostFinalize. Computing space requirements
Action start 23:10:08: CostFinalize.
MSI (c) (34:8C) [23:10:08:136]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.
MSI (c) (34:8C) [23:10:08:136]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.
MSI (c) (34:8C) [23:10:08:136]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.
MSI (c) (34:8C) [23:10:08:136]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.
MSI (c) (34:8C) [23:10:08:136]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.
MSI (c) (34:8C) [23:10:08:136]: Note: 1: 2205 2: 3: MsiAssembly
MSI (c) (34:8C) [23:10:08:136]: Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Component_` = ?
MSI (c) (34:8C) [23:10:08:136]: PROPERTY CHANGE: Adding Version property. Its value is 'c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0'.
MSI (c) (34:8C) [23:10:08:159]: PROPERTY CHANGE: Adding Resources property. Its value is 'c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Resources'.
MSI (c) (34:8C) [23:10:08:159]: PROPERTY CHANGE: Adding AIR property. Its value is 'c:\Program Files (x86)\Common Files\Adobe AIR'.
MSI (c) (34:8C) [23:10:08:195]: Note: 1: 2205 2: 3: Patch
MSI (c) (34:8C) [23:10:08:195]: Note: 1: 2205 2: 3: Condition
MSI (c) (34:8C) [23:10:08:200]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'C:\'.
MSI (c) (34:8C) [23:10:32:394]: Note: 1: 1314 2: (computed)
MSI (c) (34:8C) [23:10:32:394]: Note: 1: 1606 2: (computed)
MSI (c) (34:8C) [23:10:32:394]: Note: 1: 2205 2: 3: Error
MSI (c) (34:8C) [23:10:32:394]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1606
MSI (c) (34:20) [23:10:32:424]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Error 1606. Could not access network location (computed).
MSI (c) (34:8C) [23:10:43:185]: Note: 1: 2205 2: 3: Error
MSI (c) (34:8C) [23:10:43:185]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (c) (34:8C) [23:10:43:185]: Product: Adobe AIR -- Error 1606. Could not access network location (computed).
MSI (c) (34:8C) [23:11:09:514]: Note: 1: 1314 2: (computed)
MSI (c) (34:8C) [23:11:09:514]: Note: 1: 1606 2: (computed)
MSI (c) (34:8C) [23:11:09:514]: Note: 1: 2205 2: 3: Error
MSI (c) (34:8C) [23:11:09:514]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1606
MSI (c) (34:20) [23:11:09:517]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Error 1606. Could not access network location (computed).
MSI (c) (34:8C) [23:11:12:466]: Note: 1: 2205 2: 3: Error
MSI (c) (34:8C) [23:11:12:466]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (c) (34:8C) [23:11:12:466]: Product: Adobe AIR -- Error 1606. Could not access network location (computed).
MSI (c) (34:8C) [23:11:38:756]: Note: 1: 1314 2: (computed)
MSI (c) (34:8C) [23:11:38:756]: Note: 1: 1606 2: (computed)
MSI (c) (34:8C) [23:11:38:756]: Note: 1: 2205 2: 3: Error
MSI (c) (34:8C) [23:11:38:756]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1606
MSI (c) (34:8C) [23:11:38:756]: Note: 1: 2205 2: 3: Error
MSI (c) (34:8C) [23:11:38:756]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (c) (34:8C) [23:11:38:756]: Product: Adobe AIR -- Error 1606. Could not access network location (computed).
MSI (c) (34:8C) [23:11:38:778]: Note: 1: 1606 2: (computed)
MSI (c) (34:8C) [23:11:38:778]: Note: 1: 2205 2: 3: Error
MSI (c) (34:8C) [23:11:38:778]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1606
MSI (c) (34:20) [23:11:38:782]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Error 1606. Could not access network location (computed).
MSI (c) (34:8C) [23:11:41:206]: Note: 1: 2205 2: 3: Error
MSI (c) (34:8C) [23:11:41:206]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (c) (34:8C) [23:11:41:206]: Product: Adobe AIR -- Error 1606. Could not access network location (computed).
Action ended 23:11:41: CostFinalize. Return value 3.
Action ended 23:11:41: INSTALL. Return value 3.
Property(C): SHAREDADDINFOLDER = (computed)
Property(C): UpgradeCode = {8DA920D5-C41C-42E0-BF31-87BA49984EE4}
Property(C): Resources = c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Resources
Property(C): Version = c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0
Property(C): AIR = c:\Program Files (x86)\Common Files\Adobe AIR
Property(C): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(C): TARGETDIR = C:\
Property(C): Manufacturer = Adobe Systems Incorporated
Property(C): ProductCode = {65CB4C08-C47B-4A7E-A6A4-50C06ADA5FC6}
Property(C): ProductLanguage = 1033
Property(C): ProductName = Adobe AIR
Property(C): ProductVersion = 3.3.0.3670
Property(C): REINSTALLMODE = amus
Property(C): ARPSYSTEMCOMPONENT = yes
Property(C): REBOOT = Suppress
Property(C): ALLUSERS = 1
Property(C): SecureCustomProperties = ARPSYSTEMCOMPONENT;REINSTALLMODE;SHAREDADDINFOLDER;UC8DA920D5C41C42E0BF3187BA49984EE4
Property(C): MsiLogFileLocation = C:\Users\STEWAR~1\AppData\Local\Temp\MSI905e5.LOG
Property(C): PackageCode = {6FD5434C-027F-46C2-9662-0F725FC2454D}
Property(C): ProductState = 5
Property(C): ProductToBeRegistered = 1
Property(C): CURRENTDIRECTORY = C:\Users\STEWAR~1\AppData\Local\Temp\AIRFCB1.tmp
Property(C): CLIENTUILEVEL = 0
Property(C): CLIENTPROCESSID = 6964
Property(C): PRODUCTLANGUAGE = 1033
Property(C): VersionDatabase = 200
Property(C): VersionMsi = 5.00
Property(C): VersionNT = 601
Property(C): VersionNT64 = 601
Property(C): WindowsBuild = 7601
Property(C): ServicePackLevel = 1
Property(C): ServicePackLevelMinor = 0
Property(C): MsiNTProductType = 1
Property(C): MsiNTSuitePersonal = 1
Property(C): WindowsFolder = C:\Windows\
Property(C): WindowsVolume = C:\
Property(C): System64Folder = C:\Windows\system32\
Property(C): SystemFolder = C:\Windows\SysWOW64\
Property(C): RemoteAdminTS = 1
Property(C): TempFolder = C:\Users\STEWAR~1\AppData\Local\Temp\
Property(C): ProgramFilesFolder = C:\Program Files (x86)\
Property(C): ProgramFiles64Folder = C:\Program Files\
Property(C): CommonFiles64Folder = C:\Program Files\Common Files\
Property(C): AppDataFolder = C:\Users\StewartElectricAdmin\AppData\Roaming\
Property(C): FavoritesFolder = C:\Users\StewartElectricAdmin\Favorites\
Property(C): NetHoodFolder = C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(C): PersonalFolder = C:\Users\StewartElectricAdmin\Documents\
Property(C): PrintHoodFolder = C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(C): RecentFolder = C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\Recent\
Property(C): SendToFolder = C:\Users\StewartElectricAdmin\AppData\Roaming\Microsoft\Windows\SendTo\
Property(C): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
Property(C): CommonAppDataFolder = C:\ProgramData\
Property(C): LocalAppDataFolder = C:\Users\StewartElectricAdmin\AppData\Local\
Property(C): MyPicturesFolder = C:\Users\StewartElectricAdmin\Pictures\
Property(C): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
Property(C): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
Property(C): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(C): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
Property(C): DesktopFolder = C:\Users\Public\Desktop\
Property(C): FontsFolder = C:\Windows\Fonts\
Property(C): GPTSupport = 1
Property(C): OLEAdvtSupport = 1
Property(C): ShellAdvtSupport = 1
Property(C): MsiAMD64 = 6
Property(C): Msix64 = 6
Property(C): Intel = 6
Property(C): PhysicalMemory = 1979
Property(C): VirtualMemory = 19757
Property(C): AdminUser = 1
Property(C): MsiTrueAdminUser = 1
Property(C): LogonUser = StewartElectricAdmin
Property(C): UserSID = S-1-5-21-3850065278-1543369702-2637889638-1002
Property(C): UserLanguageID = 1033
Property(C): ComputerName = STEWARTELECTRIC
Property(C): SystemLanguageID = 1033
Property(C): ScreenX = 1366
Property(C): ScreenY = 768
Property(C): CaptionHeight = 22
Property(C): BorderTop = 1
Property(C): BorderSide = 1
Property(C): TextHeight = 16
Property(C): TextInternalLeading = 3
Property(C): ColorBits = 32
Property(C): TTCSupport = 1
Property(C): Time = 23:11:41
Property(C): Date = 8/8/2012
Property(C): MsiNetAssemblySupport = 4.0.30319.1
Property(C): MsiWin32AssemblySupport = 6.1.7601.17514
Property(C): RedirectedDllSupport = 2
Property(C): MsiRunningElevated = 1
Property(C): Privileged = 1
Property(C): USERNAME = StewartElectricAdmin
Property(C): COMPANYNAME = Hewlett-Packard
Property(C): Installed = 00:00:00
Property(C): DATABASE = c:\Windows\Installer\3a8771b.msi
Property(C): OriginalDatabase = C:\Users\STEWAR~1\AppData\Local\Temp\AIRFCB1.tmp\setup.msi
Property(C): VersionHandler = 5.00
Property(C): ROOTDRIVE = C:\
Property(C): EXECUTEACTION = INSTALL
Property(C): ACTION = INSTALL
Property(C): UILevel = 5
Property(C): CostingComplete = 0
Property(C): OutOfDiskSpace = 0
Property(C): OutOfNoRbDiskSpace = 0
Property(C): PrimaryVolumeSpaceAvailable = 0
Property(C): PrimaryVolumeSpaceRequired = 0
Property(C): PrimaryVolumeSpaceRemaining = 0
=== Logging stopped: 8/8/2012 23:11:41 ===
MSI (c) (34:8C) [23:11:41:228]: Windows Installer reconfigured the product. Product Name: Adobe AIR. Product Version: 3.3.0.3670. Product Language: 1033. Manufacturer: Adobe Systems Incorporated. Reconfiguration success or error status: 1603.
MSI (c) (34:8C) [23:11:41:231]: Grabbed execution mutex.
MSI (c) (34:8C) [23:11:41:231]: Cleaning up uninstalled install packages, if any exist
MSI (c) (34:8C) [23:11:41:258]: MainEngineThread is returning 1603
=== Verbose logging stopped: 8/8/2012 23:11:41 ===
Hope this helps. Thanks.

Star Key 2.0 trouble

(Tried to reach customer support over the phone. They put me on hold for about 30 mins. and afterwards I got an answering machine. Way to go MSI! Tried submitting my support request via the MSI website. After half an hour of filling out the damned form in all the details, click submit and get some website error. Way to go MSI!)
Anyway, I bought a Star Key 2.0 dongle to listen to music in stereo with my new Jabra stereo headphones. Only trouble so far! Let me start with one isue, particularly disturbing. After connecting the Jabra headphones to the dongle/computer, the default Audio device in Windows' "Sounds and Audio Device Properties" does not automatically switch to Bluetooth High Quality Audio, so I have to do this manually all the time. There are also other problems, but so far I'd appreciate some help in order to solve this one.

Quote from: Tiresmoke on 20-September-06, 19:19:50
So if I had to guess the key and the headset may not be fully compatible.
Well, as I was saying, I have tried the dongle with three bleeding edge stereo headsets from three top of the line companies (among them Jabra and Plantronics). Doesn't get any better than that, trust me. It would be really weird for a commercial Bluetooth dongle to be incompatible with that.Quote
There may be something else but the USB2.0 does not seem to be mentioned in the manual at all. You may want to ask the tech if he has ever seen this device himself or ask if he is guessing. Then ask for a tech to respond that has used the device.
Yep, they say they tried it with their own MSI FS300 stereo headset and it works fine. (Yeah, what else could they say, right?) Now, everybody seems to be missing the point that I came across precisely the same issues with my Belkin dongle, and they were solved after I installed some obscure patch I found on Belkin's website (no thanks to Belkin tech support though!). It's gotta be that this is also fixable via some firmware update. I do not think this is a hardware issue. At any rate, they told me that there is no such firmware update available, nor is there any in the works. Also, interestingly enough, they say they can only test the dongle with their own headset. My thinking is that anyone that claims compatibility with a standard as widespread like Bluetooth, should do everything possible to ensure that their device works indeed with other Bluetooth-compatible devices.Quote
I haven't so this is all the help I can be.
Thanks for the replies though. My only hope is that others will come across the same issues with this dongle. Until then, I will most likely be springing for a Jabra dongle: that one, at least, should work with their own headset.

Windows 7 x64 on 2009 MB, step-by-step instructions and solutions

ok, after spending days on this with about 10+ clean installs on 2 different machines and searching forums about various problems, i'm going to go step by step in a flow-chart like manner to describe the steps and various pitfalls in getting windows 7 ultimate 64 bit installed correctly on a macbook (late 2009)...most of this i didn't figure out on my own, this is a compilation of solutions found by others. i'll try and link or credit anyone i can, but honestly can't remember where i saw all of this. part of this is to share my days of frustration to try and save someone some time. also, in case i have to do this again, i want a record of it so i don't have to start from scratch next time.
i don't have everything working perfectly, but i have wireless and sound, but not sure if all the drivers are up to date. i'm still working on the headphone issue, i don't have sound yet with headphones, but i got the speakers to work.
i'm going to preface this by saying that windows 7 is a horrible piece of software, i'm only helping a friend do it because she's an architect and needs autocad, but she wants a mac for daily use. also, i'm doing this from a spanish install of windows 7 (here in south america), so it's a pain to translate this cruddy convoluted OS into english as i'm not familiar with windows 7 anyway, so i'll do my best. i'm not a pc expert. also going to say that the windows 7 x86 and x64 installs i've done on a couple macbook pro 15's seems to work much better (full trackpad functionality, expose works) and without as many problems...i don't know why it doesn't seem to work as well in x64 on the macbook, i'm still investigating.
also, i want to say that a fresh (first-time) bootcamp partition with windows install after a clean mac os x install seems to produce the best results. i say this because i wasn't happy with all the hacks in my first couple attemtps, so i erased the bootcamp partitions and re-created them to re-install windows 7 again. but i started experiencing some peculiarities that never happened in the first install after a clean Mac OS X install. it's as if the computer leaves artifacts from previous installs and acts funny. also, reboots and start-up times seem to be slower now than when it was a first-time fresh install. anyway, i'll try and outline all the weirdness here, indicated by asterisks *
SO, HERE GOES:
1) Go to Bootcamp Utility > Create Bootcamp partition
2) Afterwards, this should take you to a restart into the windows install dvd....if install dvd boots fine, skip to step 3
** if you get a gray screen (happened to me after subsequent re-install attempts), you have to power off and reboot holding down "C" key to boot from the dvd...or you can hold down alt/opt key to get the icons of bootable volumes, at this point it should be mac os x and the windows dvd. the point is, force it to boot from the dvd if it hangs on re-start.
3) Windows install should start. Select language, etc....You should then get to a screen listing all the partitions (should be 3 of them). Choose the Bootcamp partition and format (erase) it to proceed with the install.
4) Windows should start installing all the files and will reboot a couple times, here's where things get weird possibly. On the first attempt at installing Windows 7, the install went smoothly on restart.
** some of you might get a blinking cursor and a black screen that goes on forever. Supposedly this is a bug in Windows 7, having to do with video drivers or something. I don't understand because my first install attempt, it rebooted just fine and the installation continued.
anyway, what you have to do here if you get the forever-black screen is power down the machine with the power button and restart holding the alt/option key. this time when you get the bootable volumes on the gray screen, choose the Windows partition, which will now appear. DON'T boot up from the DVD. upon restart into Windows, you should be back in the installation process and it will attempt to finish the install here.
it might be my imagination, but once i had to reboot into the dvd here to actually finish the install. technically Windows is not finished installing at this step, you just have to figure out how to get past the black screen to finish the install. try both.
5) Windows should go back to where it left off before the restart, then finish the install.....and restart AGAIN. On my first attempt, the restart went smoothly and started the "first time user" process...
** some of you will get the black screen YET AGAIN, this happened to me on my subsequent attempts at re-installing Windows. again, you need to power off and start up holding the alt/option key, choose the Windows partition and it should take you to the "first time user configuration" process....since at this point, windows is indeed installed.
6) Here you will fill out all your information, product key, etc...and get into Windows. Here you will have some other problems.
Problem #1: you have no drivers to run Windows on your Mac, so you will need to install Bootcamp in windows from your Mac OS X install dvd
Problem #2: you have no "right click", because you don't have drivers, so you might not be able to eject the Windows dvd to put in the Mac dvd
Solutions: you can't control-click or right click, BUT YOU CAN hover over the DVD drive ( "D:" in your computer, my PC or whatever it's called in english) and see if there's an "eject disc" option.
for some reason, my Windows dvd was spinning and not being recognized, so i just rebooted (alt/option) into Mac OS X and ejected the disc there. the point is, you need to eject the Windows disc and put in the Mac OS X install disc to access Bootcamp for Windows.
7) Reboot into Windows (if you had to boot into Mac to eject the disc). Insert Mac OS X install disc. Navigate to BootCamp setup.exe and run it.
** the first time i did this, it ran no problem. but in subsequent attempts, it gave me the "x64 not supported by this computer" message that everyone seems to encounter. there is a bypass for this outlined here:
http://www.techulous.com/hardware/how-to-apple-boot-camp-64-bit-for-windows-7-on -unsupported-macs.html
8) Ok, so now you should have Bootcamp 3.0 installed. Now you need to update it with Bootcamp 3.1 update. Download it here and run it. This is required for 64 bit support, I believe this is the link:
http://support.apple.com/kb/dl979
** hopefully you don't have problems, i didn't, so you might have to search the forums since i can't anticipate what might happen here, it worked for me every time.
9) Ok, i think it might reboot after the update install. Now you have Bootcamp installed and most of the drivers you need, however not everything works. Some of the drivers will be out of date.
Problem #1: you may or may not have updated nvidia drivers. mine are ok, but check nvidia website if you have doubts. most of their drivers are for PC hardware, however, so the ones on the bootcamp disk and update should be fine.
Problem #2: almost everyone has wi-fi connectivity problems. it has to do with the wrong/outdated broadcom drivers from bootcamp. i will outline how i got it to work (based on someone else's solution i found in some forum or other).
Problem #3: almost everyone is having sound issues. i'll explain what i did. i still have no sound coming out of the headphone jack, i'm working on that next. but i have speaker sound and no red light coming out of the headphone jack.
** first of all, you should probably download firefox from internet explorer in windows, then update adobe flash, it's a pain....i used another computer to download the drivers, then transfered them by USB drive, but you can do it however u want.
Solution to wi-fi: ok, not sure where i got this information, but i downloaded HP drivers in a file called "sp45524.exe"....here's the link:
http://www.wireless-driver.com/download/hp/hp-broadcom-wireless-lan-windows7-dri ver-v560188.htm
apparently the broadcom drivers in Bootcamp 3.0 and 3.1 update won't install on Windows 7 x64 for some reason, lot of people are getting "code 10".
what i did is this:
9a) run the .exe file, it will create a folder called SWSetup\SP45524 that will house the drivers. there's a setup file in that folder, i didn't try it. perhaps it will install from there, but everything i read suggested a different step. ** if you run the set up file, you may have to run as administrator, or use the "troubleshoot compatibility" trick to get it to work.
9b) Go to Control Panel > Hardware and Sound > Device Manager > Network adapters
you should uninstall or deactivate any drivers you have. if it's not showing any wi-fi adapter, right click and "check for new hardware" (not sure how it's translated into english from spanish)....you should have an unknown device pop up with the yellow icon and exclamation mark. double click on that, assign it as a network adapter.
when you get to the driver tabs, you can install it from there. this is where it gets tricky. click "install driver", "check drivers on this computer", "choose from a list of drivers on this computer", "use disc", and in the dialogue box ("install from disc" that says "copy manufacturers files from", navigate to the C: SWSetup|SP45524 folder and click until you can accept. this will load up a different list of drivers.
(sorry, i'm translating the Windows from spanish to english, and i'm not familiar with exactly what they say in english, so you'll just have to use your imagination)
you should now have a small list of drivers. personally, i chose the first one on the list "Wi-Fi adapter Broadcom 43224AG 802.11a/b/g/draft-n", but the second one worked also. again, i'm doing this on a late 2009 white macbook (6.1) and it works. according to the date of the driver, it seems like it might not even be the most current and might be older than the one that's on the MAC OS X install disc, but none of the ones on the disc work. this one does. (thanks to whoever found this out, i can't find the original link of the post with this driver reference).
Solutions to sound: ok, there are multiple posts on this, everything from updating realtek to sigmatel...personally what worked for me was to download the most current Cirrus Logic drivers.
everyone has been pointing to this post:
http://www.stuffedcow.net/macbook_audio
it doesn't really tell you what to do exactly. i'm not even sure what to do, but here's what i did. actually, i downloaded what was supposed to be the CS4207 driver here:
http://www.cirrus.com/en/products/pro/detail/P1233.html
then i followed the same procedure as before with the network adapter driver...."install driver", "check drivers on this computer", "choose from a list of drivers on this computer", "use disc", and in the dialogue box ("install from disc" that says "copy manufacturers files from", navigate to the folder you just downloaded from the above link.
you should have an updated list of drivers. what i don't understand is that the Cirrus site lists the most current driver as CS4207, but the only thing that has 4207 in it starts with CDB. in any case, i chose the last one on the list, CS4206A (AB 99).
i have no idea why i chose that, it just seemed to be the most current. in any case, sound works now.
Ok, i tested all this stuff in skype. wifi, microphone and speakers work, isight works. however, still no headphone sound. so if anyone knows how to fix that, please let me know. i haven't gotten to that part yet. but i've spent like over a week trying to figure this out. windows 7 is so horrible that there seems to be so many steps to getting it just right, and i just found myself starting all over (i didn't mention the nightmare with license breaks with AutoCad due to windows reading the clock differently...that's another hack that i had to deal with...and failure meant re-installing everything).
ok, off to bed now....

Windows 7 x64 all updates
Just doublechecking. Does that include the recent chkdsk hotfixes?
[The Chkdsk.exe program does not start correctly on a Windows 7-based computer|http://support.microsoft.com/kb/975778]

MSI Star Key 2.0 & Windows XP x64

Similar Messages

Maybe you are looking for