I have an application that uses the PC/SC API to communicate with smart cards. On Windows 7, I get strange results: the data returned from the cards is inconsistent and invalid with certain commands. If I disable the Smart Card Plug and Play service in group policy then everything works fine. Has anyone experienced anything similar? Is there any way to get the smart card plug and play service to play nice? It would be nice to not have to disable it...
This is happening because you are using a smart card that supports "plug-and-play" under windows 7. In this situation, Windows 7 will automatically attempt to download and install a "Card Mini Driver" for the card when it is inserted. It sounds like the Card Mini Driver that is getting installed is causing the inconsistent behavior.
The obvious workaround is to use a card that doesn't support "plug-and-play" under windows 7. If this isn't possible, you will need to post additional details about the problems you are seeing, specifically what kind of smart card are you using, and what commands are breaking after the card mini driver is installed?
Technet details on Smart Card Plug and Play in windows 7 can be found here:
http://technet.microsoft.com/en-us/library/dd979547(WS.10).aspx
Related
I have a question to you and I really hope you can provide me some information.
I wish to build a media center because I have not found any possibilities to cast my stuff straight to the big screen from my Windows mobile phone.
Off course there is the wireless display adapter from Microsoft but I wish not to cast my whole display to my tv.
After testing a few product (Amazon fire tv box, apple tv 3, display dock and the wireless dock) I came to the conclusion that I can not have an all in one solution which fits my perceptions.
From that point I thought that I have to build my own "tv application".
Ok ok... There is kodi(xbmc) and so on... But I think this is just making a detour.
Following features must be included:
running on Windows 10
Cast music, videos and pictures.
Ability to launch and download windows store apps.
Project Rome implementation to share data across devices.
Seems possible but here´s one big problem...
If we are talking about mediaboxes, we do talk about those small boxes besides your tv. Instead off building a micro ATX setup, I want to take this to the next level... using IoT (Raspberry Pi 3).
Using IoT may have some advantages but there are a few disadvantages I have to worry about.
Will Windows 10 work properly on IoT (advantages - disadvantages)
Media streaming?
ARM architecture
Bluetooth, WIFI, Ethernet connectivity
I have never ever worked on IoT before, so I am kinda noob again. I´am asking for some advices to make this possible.
[UWP] How can I stream data (e.g. video, music, images) to another application?
[UWP] Implement a remote control - just like the amazon fire tv controler ?
Advantages - Disadvantages of using Windows 10 on a Raspberry Pi ?
Using windows 10 default applications (Groove Music, Images, Videos - Application) to play incomming data?
What do you think? Is it possible to create a Mediacenter which is running on a raspberry pi using windows 10?
Thank you in advance.
The most straightforward idea would be to create an always-running app with a MediaPlayerElement with a Source property that can be set programmatically by a remote control app. A remote control app could also control the pause, play, next, previous actions.
Be aware that there is no hardware video acceleration support for Raspberry Pi on Windows IoT Core yet, and probably that also won't come soon. There are other devices that do have proper video drivers (look at the hardware support page of Windows IoT Core).
Also be aware that there is no Windows Store on Windows IoT Core, unless you are an OEM (then you can publish your properly signed apps in an official way to devices that are managed by you).
A simpler way would be to buy a Windows 10 box from aliexpress. Then you can use Miracast to stream your screen, install apps from the App Store and play films directly on it, for example using Kodi for which remote control apps exist.
I am looking to implement the use of a Bluetooth 4.0 Smart Ready device (Polar H6/H7 Heart Rate Sensors) in my application. I am forced to target Windows 7 OS. However, I'm only seeing Windows 8 support for Smart Ready devices. I will not be able to upgrade clients to windows 8 in order to use these devices.
The first problem I found is that Windows 7 does not even see the device in order to pair with it. This might be the dongle I'm using. I have tried 2 different ones. The first is a CSR V4.0 (I'm not sure the actual model number). The second is StarTech USBBT1EDR4. Both seem to be using a CSR chipsets. Maybe I should try a different chipset based dongle? Such as Broadcom or TI?
I do see and can pair with the device with my Windows 8.1 Surface Pro.
Is there no way to get Bluetooth Smart implementation for Windows 7 OS platform?
I've recently faced the same problems! I need to run an application in o older version of windows (win xp) and I cannot find any support to that with my dongle (one based in broadcom bcm20702).
What I've found is that windows prior to windows 8, has no bluetooth low energy support, so you would not be able to use the windows bluetoth stack, and broadcom doesn't have a sdk for BLE (I've contacted them, and they said it).
So I've looked for other alternatives and BlueGiga bluetooth 4.0 dongle has a C SDK that you can use to develop your applications in Windows XP and 7. In that page (after register) you can find all the documentation you need.
I've also found a C# Wrapper and a Java Wrapper to its API.
Hope it can help.
[EDIT] : just received my dongle, tried it with win XP and it worked. Guess this is a solution for you also!
Strange thing is, I installed windows 10 and I could use bluetooth smart from my Logitech MX master mouse, but I had to go back to windows 7 because of display drivers and now it does not support it anymore. Windows 7 does not support smart bluetooth. It's just a driver I would presume, but Logitech does not provide it.
I find it realy strange that the old bluetooth device in my laptop worked fine with bluetooth smart devices in Windows 10 but in windows 7 it can only connect to plain old bluetooth devices.
I recently acquired a Bluetooth headset (Philips SHB9100) for my smartphone, but also wanted to use it with my Windows 7 PC, so I bought a cheap USB Bluetooth adapter without noticing it was a v2.0 adapter, while the headset is v2.1 + EDR.
The USB Adapter installed correctly on Windows 7, and I am able to discover my headset, but when they try to pair, an ugly Error 0x80004005 appears, never asking me for a PIN.
After some googling, and founding many people had this pairing problem, I read that the major improvement in Bluetooth v2.1 is SSP, which permits pairing without the need to enter a PIN, and also that Windows 7 chooses the "best pairing mechanism" automatically. And so I started to suspect that this is what's happening:
Windows discovers a SSP capable device.
Windows tries to pair with that device using SSP.
The USB Adapter, being v2.0, is unable to permit pairing with the headset via SSP.
Windows does it's best showing a 0x80004005 error.
I searched for a v2.1 or superior USB Bluetooth Adapter in my city but couldn't find any (I'm from La Plata, Argentina) and even though I think I'll end buying one, I'd like to make this work, or at least know for sure why the devices aren't pairing.
And so my question is (and I swear I did some more googling before asking here):
Can I force Windows to try a legacy pairing with my headset?
Any info on the subject is welcome.
Thanks!
I recently faced a similar issue and after a lot of trial and error together with research, I finally fint a compatible driver. I downloaded a few drivers from the intel site and tried it with each one of them. Finally I was able to fix my issues with the driver below.
https://communities.intel.com/thread/103579
https://downloadcenter.intel.com/download/26191
This link can also help with the issue, worth sharing.
https://superuser.com/questions/471767/bluetooth-headset-pairs-and-appears-in-sound-devices-but-shows-as-disconnected
I'm trying to test out the new Host Card Emulation features in KitKat, but the only KitKat device with NFC that I have at the moment is a 2012 Nexus 7. It does support card emulation through Google Wallet, and I can send and receive data to the two Master Card AIDs that it uses.
However, when I try to implement my own HostApduService to handle communications with my own custom AID, Android doesn't route any APDUs to my service. I then tried to call CardEmulation.isDefaultServiceForAid to see if my service is the one that should handle my custom AIDs. When I include the CardEmulation class in my code, the application crashes.
Looking at logcat, there's an entry that says "this device does not support card emulation." Is there a reason why the 2012 Nexus 7 does not support this? It has all the necessary hardware and does emulate cards when using Google Wallet.
Card emulation for Google Wallet on the Nexus 7 (2012) is done using an embedded "Secure Element" (essentially a smart card chip). However, the NFC controller on that Nexus 7, unfortunately, does not support HCE under Android 4.4 Kitkat.
I have been able to build PJSUA. The softphone runs perfectly on Windows XP, but on Windows 7 but it gives me the following error
It seems to be an issue with PJSUA on Windows 7. Has anyone been able to resolve this?
If you look into the code you will see that PJSUA is looking for a default device that has both input and output (mic and speakers) - such as headset. Just output or just input will not work...So if you plug in a headset you may eliminate your error. It works great on Win7.
The audio part of PJSIP is quite complicated IMO. Although I have it working now I am myself researching how to implement giving user a choice. That is, the user will have a choice of using headset or mic/speakers built-in combo.
Seems it is incompatible with windows7, and so is Sipek, because of some library which is no longer present in Windows7 (libwavemixer, ...).
I went on to use the Java-based Peers SIP Phone.