[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello HaukeRun, Blaustein / Klaus, WolWer / WoWe,

Thank you for your message and results which do contain useful information:

Results indicate despite reference to ANIMATION.dll within Buzzer.dll, there is either no such file, and it may be the end point of a redirection to it or an obscuration, or it is an actual file, albeit not readily accessible or ordinarily available to an end user on a Medion S3857 by ordinary means. If the latter is the case, at that stage it is advisable for an ordinary user to stop. There are further methods, both software and hardware diagnostics, by which the potential existence of ANIMATION.dll in that case could be pursued if necessary, although generally these are not suited to anyone inexperienced, ill equipped, or unwilling to risk potential damage to a device, which without ready ability to repair, and invalidated warranty if applicable, can be essentially permanent or semi permanent. The full registry and file list of what is ordinarily accessible are awaited with interest and may provide clues as to the nature and function of ANIMATION.dll

Results indicate the reason TaskMgr does not run on the S3857 is because one or more dependencies is incorrect, and one of these is the aygshell.dll in use. When used with the Emulator, 'TaskMgr is not a valid WinCE application' error occurs. When aygshell.dll native to the Emulator is used, TaskMgr runs without issue. Unfortunately the native version matches non I already have a copy of, nor were initial extraction attempts successful. Even when extracted, there is no guarantee it would function other than within the Emulator from which it originated for similar reason to why XIP ROM files do not work elsewhere as previously detailed. It is a case of sourcing the correct aygshell.dll, which may not be correct for all devices. It serves as an example of why unnecessary dependencies should be avoided for software actually intended to readily run on a wide range of devices. GCC dependence on aygshell.dll is entirely unnecessary and it is rightly scheduled to be eradicated at some point, serving as a stop gap in the interim with all the inherent issues it brings with it.

Your sentiments are entirely understandable.

It is not essential to use TaskMgr. If needs be, any utility or method, or separate utilities or methods, that provides details of Devices and Services, creates a usable full registry file, allows registry editing, and creates a full file list, could be used to achieve the objective. Exactly how any other utilities or methods are operated will vary from the instructions given which are very specific.

As a starting point, CERegEdit can be attempted for creating a suitable full registry file, and making the required edit to enable CMD.exe to function. Instructions can be provided if necessary. Then from the command line, full file list can be created as previously detailed. Unfortunately I am not presently aware of any working command line equivalent for devices information. However, services information, albeit less detailed than from TaskMgr, can be obtained using the command: services list

Note: CERegEdit installs to the PC, and accesses the device via an ActiveSync connection. Having used this successfully with other devices, it does work, as always however without access to a S3857, compatibility with it is unknown.

Note: REGEDIT.EXE provided with Ralf 25 Start Menu does not produce a registry file suitable for analysis.

I will be glad to lend any further assistance as required in obtaining devices and services information, and the full registry and file list of those ordinarily available and accessible, and the analysis of those. An assessment can then be made at that stage as to how best to proceed.

Thank you for the kind words of appreciation. I look forward to your future feedback with interest, as with that of all users that take the time to positively contribute.

low.flying.pigs