Windows CE application disappears after device restart - windows-ce

I have wrote an application for Datalogic Falcon X3 terminals. The devices runs Windows CE 6 Proffesional.
Application is deployed on devices, and everything works fine, except one thing - every time, when the battery in device depletes, the application files disappears.
I suppose, that this is some sort of factory reset.
Notably, not everything is wiped - i.e. WiFi setting remains unchanged.
Is there a way, to keep my application on device, when the battery power is off?

If you are copying your application file to RAM (i.e. folder other than SD card / NAND flash or any ROM based directory), then the application won't persisted after power off or restart.
But the registry settings such as WiFi settings are persisted, because, these are saved to ROM based hive registry in your OS.
So, If you want to have your application for next boot-up, you must save the application file to any ROM based directory.

Check out the device data sheet. Probably Falcon X3 have RAM-based file system. In this case you need to copy your application to ROM-based directory (see the manuals, again, to find the name of ROM-directory).

Related

Is there a manual way to roll back an Update on Windows 10?

Long story short, windows 10 is utterly broken on my laptop after it automatically installed some updates. It's now stuck in a loop which always ends up saying "Undoing changes made to your computer"
I can't get into the BIOS.
I can't get into the Windows Recovery Environment.
Been talking to MS support for far too long so far, so I'm wondering if it's possible to add it as a secondary disk drive to another machine that does work, and manually remove any updates that were installed directly through the filesystem?
The only solution MS were willing to offer was to format the whole drive and re-install windows.
When I moved the HDD into a working windows 7 machine it actually prompted a chkdsk to run over the disk.
It found a whole load of orphaned files, not sure if that was really the cause, but after backing up as many files as I had access to, I put the drive back into the other machine and now it boots.
tl;dr, chkdsk fixed it.
I was stuck in this loop last night
machine configuration : Dell Inspiron
windows 10 (original)
What the one thing you can do is to use an application name Dell usb recovery tool. You will have to format you whole computer be it c:// or any other. You will need an extra hard drive to make a backup.
the process goes like this.
You will have to install the above application on other computer and open it and fill your service tag and make that pen drive bootable with that application.
Now plug in that pen drive to the laptop.
Go for troubleshoot.
Repair.
Install new original os.
It will ask for backup make a backup to other HDD.
Install and recover your backup.

Can you think of a reason why windows might not enable audio if noone is logged in?

I'm having a bizarre problem with some virtual servers created to record podcasts. They run on amazon AWS as windows server 2012 instances and a small c# app tells FFMPEG to do the heavy lifting of capturing from the virtual screen and reading from the virtual sound card (Virtual Audio Cable: https://en.wikipedia.org/wiki/Virtual_Audio_Cable) via DirectShow filters
The problem I have is if I leave the machine to do its stuff unattended, the recordings are sometimes silent. If I log in via VNC and watch it doing its stuff the audio is recorded just fine. All other aspects of the test op are the same, and the virtual machine is shut down between successive recordings so each one should theoretically be a clean slate. The app runs under a logged in session (hence the use of VNC rather than RDP)
I'm now wondering if there is some optimisation of the windows sound engine whereby it doesn't bother playing audio if it thinks noone is listening. The confusing thing to me is that not every virtual machine suffers these problems; some of them record fine (and they're all created from the same seed virtual hard disk image) in unattended mode
I'm asking this question with the aim of getting together a list of things I can check/look into/debug.. I don't have much knowledge of how MME/DirectSound/WASAPI work internally...

What makes a background downloading task suspicious and how to make it less so?

Short question:
I have an application that fetches files from a cloud host. It looks suspicious to the security software and treated is as a virus.
What shall I do it make it get around the anti-virus software?
Longer story
I have a USB device and I need the firmware on it to be automatically updated.
When the device is connected to a computer, it presents itself as two removable USB mass storage devices.
The first one stores the application in question, the second is the place to put the upgrade package.
The user would go to the first partition and run the application, and while the user is doing his/her job with the application (like processing data collected by the device), the application fetches the upgrade package from an URL hosted in the cloud and places it in the second partition.
The device will upgrade itself when it's disconnected from the computer.
During this process, the application is isolated by the security software installed on the test machine.
Problems
This application raises a lot of red flags:
It runs from a removable USB drive
It starts downloading files from the internet without notifying the user.
The downloaded file is placed into another removable USB drive.
The operation, defined by the requirement, is suspicious itself. So I can imagine that an answer to this question is basically an answer to "how to get around a security software".
If this is the case, how shall I get the operating system or the user involved in the operation to make the application less suspicious?
Background
The application is written in C++/Qt.
The file being downloaded file is a linux opkg package with -rw-rw-r-- permission.
The file is fetched from an HTTPS URL hosted on Amazon S3.
The test machines runs Windows 10.

Does uninstalling Raspberry Pi GUI speed up the device when used via SSH?

I'm using my Raspberry Pi 2 Model B as a small and super simple LAMP development server. However it is on the edge of acceptable performance, especially when it comes to bulk copying or handling large MySQL databases.
The set-up:
The Pi has no display attached
I access the device via SSH and WinSCP
I changed the GUI boot behavior via raspi-config to command line only
What makes me curious is that whenever I connect to the Pi via the Windows Remote Control tool I still get a GUI.
Therefore I'm wondering whether if there are any negative performance implications or if Raspbian does not load the GUI until explicitly requested from the remote control tool.
If there are negative implications, what configurations should I change? (PS: I like to have a GUI from time to time but I could do without it.)
Unless the RPi is very starved of memory, there will be no performance difference as long as the graphical interface isn't actively being used.
Having said that, I would not try to run a large database on it unless I was using a class 10 card or better and the database configuration was heavily tuned.

Adding drivers to already built CE 6.0 image

Is this possible? I am using a CE image from a manufacturer that won't release a custom image with an extra driver I need.
Give me some good news!
Yes, there is a possibility that you can add your driver over an existing image. You just need to place your driver dll(s) in the required folder (generally Windows folder) in your device where you want it to be and make some registry entries for it. If you already have a .reg file for the driver then you just need to import it on your device.
You can also make a CAB file to avoid the manual work.
It depends. You need to have permanent registry and storage. If you have, then you can configure registry entries to load your driver (at boot or when is detected by USB, SD, PCI etc.) and store it on the device. In some cases drivers are loaded from the image before any storage is mounted and this may prevent you from being able to load your driver at boot (or having your device detected if it's plugged in at boot).

Resources