Cafepay Virtual Printer Driver cannot be closed from the tray icon, it's got something to do with the registry, how do I close it and remove it from auto startup?
There is a fix for that, Officially released from the CafePay company.
Open task manager and end process any cafepay-printer-driver.exe that you see
Delete the folder from C drive
Extract and run the new CafePay application
Now you have control from the Tray icon
If the problem persists, call Qioo sales support. They will find a way to uninstall CafePay!
Related
Image of Random black box
Started up my computer and have this random black box on my desktop.I can only move it around and have no way of closing it. Anyone know how what the cause it and how to remove it.
Update display driver
Windows Key+X (Or right click on Start)
Click Device Manager
Expand Display Adapter
Right click on entry below
Click Update Driver Software
Click Browse my computer for driver software
Click Let my pick from a list of device drivers on my computer
Choose the driver
Click Next to update
If this does not work, select Search automatically for the updated driver in place of Browse my computer for driver software
Restart your computer
OR
Update driver from manufacturer's website
Go to the website of the display adapter's manufacturer or computer's manufacturer
See if some driver is released for your model and OS
If yes, download that
In Option 2, you click Update Driver Software, in place of this, click Uninstall
Install the downloaded driver
Restart your computer
This is my screenshoot for Next Button not turn on when i am trying to create Virtual Device in AVD Manager but system image cannot be selected and next button not turn on.
I am running Android Studio using 32bit computer with 1GB RAM and everything is okay, except its AVD Manager cannot be selected system image. Do you know what should i do, so the Next Button on this image below can turn on?
I think I found the problem - expand the column where the names of the images are - then, all of the sudden the "download" link appears.
Go through the download process and accept the license if you have to.
and it should work from there.
Stupid idiotic problem to have, found the solution by accident.
You should be having at least 4gb RAM.
I have been trying for days to get a simple app any app made in livecode to display either on my tablet, smartphone or emulator. It just doesn't work. Here is what I have done:
I have installed my sdk and pointed livecode to it in preferences.
Picked 2.3 as my version
Check my google usb drivers and they are up to date.
I followed live code's step by step and no success. I am thinking that since I am running windows 7 not a Mac, maybe this cant be done. It seems all the developers run Mac's?
I even tried to make a .apk, It made the file but " There was a problem parsing the package" once I got it on my Galaxy tab. I made sure that I checked the box to allow programs to run on my tablet. So I am still stuck.
To see if the SDK is working correctly you could try to use the Android SDK emulator first.
Open the Android SDK Manager and select the menu Tools->Manage AVDs.
There you can create a virtual Android device and run it.
If the virtual device is running you can see the virtual device under "Development->Test Target in Livecode. Select it and either select "Test" under "Development" or press the "Test" button. Does this work?
That error message means that the operating system on your device is preventing the app from being installed. The most likely reason for this is that you haven't changed the "Allow installation of apps from Unknown Sources" setting on your Galaxy Tab. There are other reasons and solutions for this error message - to see them visit Panagiotis's excellent blog post on the LiveCode website, your error message is in the fifth example
https://livecode.com/how-to-deploy-apps-to-android-devices/
This question already has answers here:
adb cannot start daemon, CreateProcess failure, error 2
(7 answers)
Closed 4 years ago.
i got this problem that is annoying me after updating to 1.3 , i fired up Android Studio and got a message saying :
***Unable to establish a connection to adb
This usually happens if you have an incompatible version of adb running already.
Try reopening Android Studio after killing any existing adb daemons.
If this happens repeatedly ,please file a bug at http://b.android.com including the following :
Output of the command 'C:\Users\username\AppData\Local\Android\sdk\platform-tools\adb.exe devices'
2.you Idea.log file (Help |Show log in explorer)***
Whats the solution ,i'm running Win7 32bit
You need to kill the adb process that is running, to do so,
Go to Spotlight search, open Activity Monitor,
Loop for adb under CPU tag,
Now Select it and Force Quit the process.
You can kill adb process through Terminal command too, by simply typing Kill -9 adb
Note: Sometimes When u tried to force close them they kept restarting. Make sure you quit any emulators and disconnect any devices to avoid any mistake.
I spent around a complete day to look for the solution but couldn't find an exact one.
Finally what i did was that I uninstalled my antivirus and after that it worked like a charm.
So, here I shortlist the steps to check whether you are solving for the correct problem or not:-
Run command prompt and set path to where adb.exe file is present. (In most of the cases it's found at C:\Users\YOUR_USERNAME\AppData\Local\Android\Sdk\platform-tools)
Type adb start-server and press enter.
If there is an error displayed saying something like "Cannot connect to daemon" , then you must look in your antivirus for firewall settings and add the path to its exceptions or you can simply uninstall your antivirus.
In tools menu,Android->
untick enable adb Integration
and Then
OPEN widows task manager n manually end process adb.exe This also solved my issue as der were multiple adb.exe running.
Restart the computer. Now, disconnect the device, connect it, Make sure USB debugging Option is enabled. Now, pull navigation drawer and select the option USB for file transfer. In the dialog; there are few options such as ;
Transferring media files
Transferring images
Connecting MIDI devices
None
select None and now select Transferring media files.
Now, check Android studio, and select Android Monitor and check whether device is attached or not.
Thank you !! I hope it helps for your problem.
This happened to me after upgrading to Windows 10. I got the same error you did, but what was helpful was the extra message about not finding the adb version in the very bottom left corner of the Android Studio screen. That led to this: Solution: How to Fix Android Studio’s ‘Unable to Obtain Result of Adb Version’ Error
In short, it was a problem with my Avast firewall blocking the connection. I added the sdk and Android Studio paths to my firewall exception list and it worked!
I would like to know if there is a tool simillar to mymobiler for Wince 5.0 which I can use to control the device from my desktop.
I use mymobiler (v1.25) but I believe it controls only devices running on WM5 and above.
Any help would be highly apprecited as the screen of my device has stopped working.
I use MyMobiler myself when I am coding for WinCE5.0 (not very often but I do know that it works.)
In your extracted MyMobiler zip file is three versions of remote.exe.
remote.exe
remote.exe.50
remote.exe.40
The only one I have gotten to work on wince5 is remote.exe.40
Just rename the existing remote.exe file (remote.exe.wm) [you may have to click tools, folder options, and uncheck hide extensions for known file types]
Next rename remote.exe.40 to remote.exe.
After that you are good to go. Copy remote.exe to the device through activesync (xp) or WMDC (>XP) and launch it on the device. It was a bit funny connecting for me the first time - I click connect on pc, then had to click the tray icon on the device, and click connect.
Good Luck!
Link to Video Showing it Running 1
This does work, the auto-install doesn't seem to work but if you copy the remote.exe over as mentioned (any location will do), then start remote.exe, click on the MYMobiler icon in the tray and select Connect, it will attach to your PC like the WinMobile version does.
Also, check the ini files in the MyMobiler directory. There's some details on the features/options.
I can confirm that Dave and Mike's solutions work on Windows CE 7 as well.
I was getting an error with the AYGSHELL.dll library when starting My Mobile after the gun was connected.
Run Mymobiler.exe before you connect the scanner to the PC and then connect to the PC using the tray icon from the gun. No error.