I connected with bluetooth to external printer within sunmi v2 pro. Bluetooth works okay. Application stop when I print with that connected external printer.
My external printer is TSP143IIIBI. Star
Can I connect and print with that printer in sunmi v2 pro?
It causes because of sunmi SDK version.
Not work in 1.1.0 of Sunmi SDK Version.
It will work the upper version of that.
Thanks.
Related
I'm currently working to integrate the DigitalPersona U.are.U 4500 Fingerprint Reader with our FileMaker application. I installed the DigitalPersona SDK 1.6.1 on my system (Windows 10 Pro x64, 1904 Build 18362). However, the SDK samples do not seem to work while launching the scanner window. It gives the error: "ERROR: The RPC Server is not listening (0x800706B3)". I checked the 'Remote Procedure Call' and 'DCOM Server Process Launcher' but they're already running.
I then installed the SDK on an older Windows 10 installation (64 bit, 1709 Build 16299). The sample applications ran, but when the scanner window launches, it does not detect the connected fingerprint reader. I tried switching the device driver from "U.are.U 4500 Fingerprint Reader (WBF)" to the normal "U.are.U 4500 Fingerprint Reader" but it didn't help.
I tried the Biometric Fingerprint Plugin (by Productive Computing) for FileMaker and installed version 2.0.1.2. It comes with a sample FileMaker application for enrolling fingerprints and searching them. The plugin installed correctly, however, it also gives me the same issue upon scanner Window launch. The error message says "The fingerprint reader is not connected. Connect the reader." A screenshot is shown below.
DigitalPersona U.are.U 4500 Fingerprint reader not detected
As a result, I am neither able to use the code samples given with the SDK, nor able to use the demo file provided by the plugin, because the plugin isn't getting detected. I thought maybe the device was faulty, but it is working fine with Windows Hello fingerprint sign-in (using the WBF driver), as well as with the TimeDrop software (using the simple, non-WBF driver). The SDK is working with neither of these drivers.
Any help would be greatly appreciated.
I found the solution.
Go to the Device Manager and locate the fingerprint device. Then Right Click >> Update Driver >> Browse my computer for drivers >> Let me pick from a list of available drivers.
Select a driver that does not have the term "WBF" in it. Windows Biometric Framework (WBF) drivers seem to be incompatible with the SDK.
Also, SDK version 2.2.3 works with Windows 10. Older SDKs are incompatible.
I am developing a cross platform Bluetooth library for Node.js. I am using a MacBook Pro with built in Bluetooth and now I need to make sure my library works on Windows. I am trying to use VirtualBox to run Windows but that Windows cannot find my system's Bluetooth.
Is there a way to make my Mac's Bluetooth work on a Windows running inside VirtualBox?
I have a single board computer running Windows CE 5.0 that's connected to a desktop via serial. I'm updating the desktop from Windows 2000 to Windows 7 and as a result need to update from ActiveSync to Windows Mobile Device Center. With WMDC, I am no longer able to make a partnership with the device or connect.
My question is - are there any known changes to how repllog.exe (device side) interacts with WMDC vs ActiveSync (host side)?
Maybe a better question - will WMDC even work with with Windows CE 5.0? The system requirements listed here don't show CE 5.0 as supported.
Nothing else in the setup has changed and the only thing I can guess is that the single board computer is no longer 'answering' or handling the connect event properly.
I don't have access to the build tools for creating the WinCE 5.0 image unfortunately, so I'm not sure if I can easily update to WMDC on the device side.
Also, the current registry values:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services]
"RasTimeoutResponseWait"=dword:00000032
"RasTimeoutPause"=dword:00000005
"ConnectTypesAllowed"=dword:00000008
"CheckPasswordTimeoutSeconds"=dword:00000014
"WaitV2TimeoutSeconds"=dword:00000004
"SerialPort"="COM1"
"HasUsbDevice"=dword:00000000
"SerialBaudRate"=dword:0001c200
"DeviceType"=""
"DeviceOemInfo"=""
"DeviceVersion"=dword:04401504
"DeviceProcessorType"=dword:00000000
"DeviceProcessor"=""
"DTPTNetworkType"="{0}"
"DisableIr"=dword:00000000
"GuestOnly"=dword:00000001
"InstalledDir"="C:\\Windows\\WindowsMobile"
"Dual-Home"=dword:00000000
"DisableCredentialSave"=dword:00000000
"MajorVersion"=dword:00000006
"MinorVersion"=dword:00000001
"CurrentPartnershipProtocol"=dword:00000003
"MinimumPartnershipProtocol"=dword:00000002
#=""
"BuildNumber"=dword:00001b35
"EulaRequired"=dword:06010000
My environment is Windows 7 Pro x64 + WMDC x64 + WinCE 5/6 and it works fine. So I believe that WMDC does support WinCE 5.0.
As I remember WMDC can conflict with MS Outlook, try to google this, this is probably your case.
If connecting through a serial port, you may have to modify the registry on the host PC to allow serial connections.
Change this key to the name of the serial port, e.g. "COM1". Then reboot your PC and do not change anything in the WMDC settings dialog after that.
HKLM\SOFTWARE\Microsoft\Windows CE Services\SerialPort
I was working on my windows 8.1 OS on my Virtual Box running Visual Studio 2012. Yes I am working on an 8.0 with a feature and after planned on migrating everything to 8.1 since it can be integrated more easily with PC And tablet. Everything was working fine and my windows phone 8 was connected via my virtual box via USB and showed up in VS2012. My Virtual Box did 2 random shutdowns and now my VS2012 only shows an option to use an emulator. This was never working before which is why I always debugged via my windows phone. Hyper-V and all of that stuff specified it was installed using a CoreInfo.exe file I got off the web to check to make sure the appropriate stuff was enabled. Now after the 2 random virtual machine shutdowns the emulator is the only option showing when I want to debug.
Things checked:
Restarted both phone and virtual box OS.
Uninstalled device driver on the virtual box machine.
The 2.0 option is checked in the settings for the virtual box OS and can see the windows phone connected on the virtual machine via the device manager.
It mysteriously started working again where the windows phone was connected instead of to a 7.1 emulator. I wish I could give a reason or an explanation to what I did to fix it but I didn't do anything to create this specific issue nor to fix it. I put this up just in case anyone was reading it.
I am developing Qt application for Windows CE 5.0 device.
My setup is:
Qt 4.7.3 compiled with Visual Studio 2005 using Windows CE 5.0 Standard SDK.
Everything works OK on real device, though I would like to test software "locally" in an emulator.
Visual Studio 2005 provides Pocket PC 2003, Windows Mobile 6 emulator images but no Windows CE 5.0.
Windows Microsoft CE 5.0 Emulator does that, but its sample device is based on i486, so this doesn't work for me...
I found some kind "Plaftorm Builder" and "ARMV4i BSP for Windows CE 5.0", but I am not building device or it's SDK, and I am not interested in specific device at all. All i need is "generic" AMRv4 WinCE 5 image for basic testing...
So what is possible outcomes for me?
Microssoft stopped providing Windows CE OS images for the emulator after the x86 emulator was abandoned, and for good reason. Windows CE is a modular OS so it's not possible to create an Emulator OS image that matches what all devices are and my guess is that there were too many support calls and complaints about how the emulator either contained something unwanted or didn't contain something that was wanted. The point being that there is no "generic Windows CE device" so there's no way to create an emulator of one.
The response from Microsoft was to provide the ARM-based Device Emulator 3.0 (available as a Standalone Release) and a BSP for the emulator so developers can create their own OS images that match their actual target hardware OSes.
So your options are to either create an OS yourself or find an OEM that provides an emulator image for their device (I'm not aware of one offhand, but I very, very rarely use the emulators so I've never bothered to look).