We are using MC9090's running CE 5.0. We are using a program called Wavelink Studio Client to access our scan application. Studio Client is different and not the same as Wavelink Telnet CE. Wavelink Studio is only a "Go Between" and does not hold any settings. The Wavelink Studio basically looks at the scanner .dll and pulls settings from that.
My problem is that I have an Interleaved 2 of 5 barcode with 16 length. The MC9090 comes with two demo programs ScanWedge and ScanSamp. I can modify the length for int 2 of 5 in either of these programs and my barcode will scan through Wavelink Studio Client. However, after a warm boot I lose all my settings since these are just demo programs.
So, I turned to DataWedge. Which uses its own config folder to store settings, but I assume loads the settings into the scanner .dll. My barcode scans perfectly in Studio Client when DataWedge is installed only after the DataWedge process has been "Stopped" then "Started". If perform a warm boot and DataWedge starts... my barcode will not scan through studio client until DataWedge has been Stopped, then my barcode will scan through Studio Client whether DataWedge is Started or Stopped.
My question is: Is there a script/command line/bat/etc. that I could use that would "Stop" DataWedge, then "Start" DataWedge after a warm boot? This is one way to solve my problem.
If anyone has any other suggestions, please let me know. I have repeatedly been told that the settings from ScanSamp and ScanWedge (demo apps) are not stored anywhere on the device. I believe they are stored somewhere though. Because, when I make a change on DataWedge, I can open ScanWedge and the settings happen there to. So there must be some central location where the hard scan settings are stored? I just need to be able to edit the settings in this location and have them stay there. I don't even need DataWedge if the scanner would hold the settings in the .dll that I specify from ScanWedge. With datawedge uninstalled, I tried changing my settings in ScanWedge then using RemCapture to capture all the settings from the device.. I then loaded those settings onto another device to see if it would load the scan settings, but it did not.
Set the options in ScanWedge. Then Use "Remote Registry Editor" that comes with Visual Studio 2008 and go to this path: [HKEY_CURRENT_USER\Software\Symbol\ScanWedge]
There you will see the various settings for ScanWedge. To persist these settings over warm & cold boot do the following:
Open Notepad on the PC.
Type the following registry entry:
[HKEY_CURRENT_USER\Software\Symbol\ScanWedge]
"AutoEnter"=dword:00000000
"AutoPIE"=dword:00000000
"AutoTab"=dword:00000000
"Binary"=dword:00000000
"Data"=dword:00000001
"Escape"=dword:00000001
"Prefix"=""
"Suffix"=""
Save the file as scanwedge.reg
Place the file on your Terminal in the \Application Folder using ActiveSync.
Cold boot the terminal.
NOTE: A cold reboot will erase all files, except the application and platform folder. Save your files before cold booting.
Hope this helps.
Related
I develop an app that communicates to an external database. I have recently started working from home. For development purposes, both the database and Android Studio are on the same workstation, but the access has to be done via URL, so when the app goes into production the only change is the address being accessed.
Back in the office, my company had a DNS to resolve local addresses for us, so my experience with Android Virtual Devices (AVDs) was seamless. But now that I'm at home I need to set the /etc/hosts file on the virtual machine (and the machine in question uses Googles API, not Google Play, otherwise this would never work).
Following the steps on this awesome thread allowed me to set this up with no problem via command line using the steps below (Linux system):
start emulator on tools folder with writable permissios
tools/emulator -avd <avdname> -writable-system
use adb to remount the file system and push a prepared hosts file into place
platform-tools/adb root
platform-tools/adb remount
platform-tools/adb push <local>/hosts /etc/hosts
This gets the hosts file where it needs to be, and through Android Studio I can confirm that the file has been edited through File Explorer, and from this point on, development is seamless again.
However, when I close and restart the same virtual machine, now using Android Studio's Device Mananger Play button, the hosts file resets to what it was previously on the AVD. Also, the file system is no longer writable. As a result, I always have to start the AVD via command line.
I wonder if there's a solution to either:
save the new hosts file permanently on that particular machine so when Android Studio starts it his way the configuration is already there; or
set the -writable-system flag to Android Studio's own play button command somehow, so the changes I made in the hosts file appear again.
I appreciate in advance any thoughts.
You can set the studio.emu.params environment variable to -writable-system.
Something like set studio.emu.params=-writable-system on Windows, or launchctl setenv studio.emu.params -writable-system on MacOS.
Related: https://stackoverflow.com/a/64696876/2924547
How can I change settings.json (or whatever) so that when I launch VSC, that a workspace (or literally just a directory) opens up automatically.
I have already reviewed this other great answer How to open a default workspace when launching Visual Studio Code?
However I need to do this on brand new, newly provisioned machines that are ephemeral (meaning they get destroyed and recreated from scratch). That means that simply memorizing what I did once, does not help.
Also.... is there a way to do the same thing where the integrated terminal is already open as well? I can't seem to find knobs for either of the above in the settings.json.
This is on linux servers that students will open in their web browser using vs code server.
We have more than one programmer here working on Android code in Android Studio 2.2.2. We're working in debug mode because the code is still in development but we periodically load our latest work on various other employees' devices for them to test with, from the menu bar using Run > Debug 'app'
If I load code onto a device that another developer had previously put code on, Android Studio won't let me, saying there's an incompatibility ([UNINSTALL_FAILED_UPDATE_INCOMPATIBLE] and that I have to uninstall the old code first. I don't want to because I want to retain the old data since we collect debugging and performance data during test runs. (we're developing an industrial process-control app)
Looking on Stack Overflow I find two solutions to this but they are both from the Eclipse era: Using the same debug keystore on multiple computers and Share debug.keystore The files referenced in the solutions seem unique to Eclipse - specifically there seems to be no file called "debug.keystore" anywhere on my development PC.
How do I do a debug 'app' onto a device containing code from another Android Studio without having to erase the previous installations storage?
To avoid the uninstall-install cycles, share the same debug.keystore across the devices.
The location of debug.keystore depends on the value of environment variable $ANDROID_SDK_HOME. debug.keystore can be found in the subfolder .android at the location specified by the environment variable.
However, in case of variable not being defined :
By default, it is stored in the same directory as your Android Virtual Device (AVD) files:
macOS and Linux : ~/.android/
Windows Vista and Windows 7 : C:\Users\your_user_name\.android\
as stated here .
I am attempting to launch the windows phone 8 SDK emulator on my Mac so that i can do simple web testing of mobile websites i build.
I have followed several guides and they all say the same thing.
Such as:
6. Once the content (list of files and folders) is displayed, find the VMware virtual machine configuration file – the file with the .vmx extension.
hypervisor.cpuid.v0 = “FALSE”
And this guide proved to be quite useful to get it setup:
http://developer.nokia.com/Community/Wiki/Windows_Phone_8_SDK_on_a_Virtual_Machine_with_Working_Emulator
I was able to get Hyper-V support enabled and I have even managed to open the Windows Phone 8 Emulator directly from the Hyper-V Manager. But in this state it is missing the chroming, the buttons, and when the mouse goes across the screen it disappears. The solution to this is said to be launching the emulator directly from Visual Studio.
My problem is when ever i try to launch the emulator from Visual Studio it creates a new image and then goes into a boot look where it keeps crashing and restarting over and over again.
When viewing the Hyper-V event logs i see this error:
'WP8SDK720P' has encountered a fatal error. The guest operating system reported that it failed with the following error codes: ErrorCode0: 0xC000021A, ErrorCode1: 0x88EB9150, ErrorCode2: 0x0, ErrorCode3: 0xC0000022, ErrorCode4: 0xD203BC. If the problem persists, contact Product Support for the guest operating system. (Virtual machine ID 50607D9A-6E23-4369-9D89-2730614219BA)
How can i get past this error?
In the end I found a solution, I managed to launch the original Windows Phone VM image directly from the commandline with this command:
"C:\Program Files (x86)\Microsoft XDE\8.0\XDE.exe" /vhd "C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Emulation\Images\Flash.vhd" /name WP8SDK720P
I created a new text file with notepad and put this command in it and saved the file on my desktop as a .bat file. This way i can just double click the shortcut and launch the sim.
Hopefully this helps someone else out there. In this way, you don't even need to start visual studio to run the emulator, it makes it much simpler if all you are using the emulator for is testing web-apps.
N.B. if you press FN+DOWN-ARROW you can enable the keyboard to work in the sim.
Follow these steps and see if it might help you to fix the problem.
Step 1: Shut down the Guest operating system (Windows 8 in this case).
Step 2: Open the settings for the VM and select Processors. Look at the left pane and see if you have CHECKED the option "Virtualize Intel VT-x/EPT or AMD-V/RVI" under the Virtualization engine section.
Step 3: Open the configuration file (Windows 8 x64.vmx) for the VM and check if you had added the following line of command (hypervisor.cpuid.v0 = "FALSE") to it as shown in the screen shot. You will generally find the file at the location where the virtual hard disk is placed.
If every thing is right, check to see if you had installed Visual Studio 2012 Update 3 (if you are using Visual Studio 2012 as your IDE).
Hope this helps to fix the issue. If you need more information on how to create a VM for developing windows phone 8 apps, there is a great article on nokia developer forum. You can find it here
Happy Coding!!
After I installed Windows 8 perfectly legit statement like this doesn't work anymore:
#if DEBUG
Debugger.Launch();
#endif
Service starts ignoring that thing.
Yes, I am building the project in a debug mode.
if I change that to a Debugger.Break() - the service just fails, and still there's no dialog for attaching a debugger.
The secret lies in changing the registry key for the Visual Studio JIT debugger via the following:
reg add "HKCR\AppID\{E62A7A31-6025-408E-87F6-81AEB0DC9347}" /v AppIDFlags /t REG_DWORD /d 8 /f
Before making this change the value on my machine was 0x28. The above changes it to 0x8. In essence it removes the 0x20 flag.
If you search the Microsoft include files (WTypesbase.h) then you find the following:
#define APPIDREGFLAGS_IUSERVER_ACTIVATE_IN_CLIENT_SESSION_ONLY 0x20
Once you make this change then the JIT debugging window is displayed again. I believe that all of this relates to various session 0 security changes made by Microsoft.
Sourced from this post:
http://forums.arcgis.com/threads/69842-Debugging-your-SOE-on-Windows-8
Debugger.Launch would launch an application with a visual GUI. By default services do not interact with a desktop and thus anything they do cannot be "seen".
Support for interacting with the desktop has slowly been removed from Windows services ("Interact with the desktop" option has been removed from some Server versions for example). I would imagine they've continued this trend.
Windows Services by nature are not GUI applications, they can run before and after a user logs into a desktop and thus cannot show a GUI all the time. It's not generally a good idea to depend on an ability to have a GUI in a Service.
If what you want to do is debug a service, I suggest running it as a regular application so that you can do things like Launch and Debug. Shameless plug: you can see Developing Windows Services in Visual Studio for a way to write a service that supports that.
Is this a Windows Store app or a desktop app?
Try right-clicking on your project (the C# executable project if that's what you have) and selecting "Properties". Then in the left sidebar of options, click "Debug". In the "Start Action" section, check the box for "Do not launch, but debug my code when it starts".
Now you can hit F5 and run Visual Studio with breakpoints in your code, and it will sit and wait for you to fire up the process. Then run your application (outside of Visual Studio), and Visual Studio will attach the debugger.