I want to make a registry filter driver specifically for Windows XP.
I know there is an example in the official WinDDK but it only works
on Windows 7.
Is it even possible to develop a registry filter driver for windows xp ?
Any kind of code/pointers will be highly appreciated.
You can also hook the registry API functions using Microsoft Detours (or similar package). This is no easy task to get correct (still finding the bugs) but if you are up for writing drivers then this is no different in complexity. Just less blue screens. Look at hooking the Nt or Zw functions in ntdll.
No this is not possible. For Windows XP you need to hack the kernel API table. This is not recommended, but for windows XP it is the only option. This is how the Sysinternals RegMon program used to work.
Yes, it is possible altought I would not recommend it.
First, you have to hook SSDT. Please notice that hooking SSDT is not supported in XP 64 bits (Patch Guard), you have to understand what are you doing (BSOD hook), is not portable and your software can be marked as malware.
Second, you need to do reverse engineering of Key Control Blocks. When two different apps open the same key, they get two different handles but they KCB is unique for both threads. KCB is an opaque structure so WinDbg is your friend here.
Related
I have searched high and low for installers to customize after creating my applications (small, medium, and much bigger) in size. Yes, portable apps great but most people just want to install and also have it just update when updates are available and install and restart the next time or at least warn the user to save the work before the Application can reopen.
Yes, I have looked at NSIS and other installers, but they are merely for windows and not for both windows and Linux. Some of these installer projects have been discontinued. Most people who use Linux don't like to always build from the source.
I was wondering how I can create a POSIX compliant installer that my software can install on both Windows and Linux. What are the steps involved? I assume most or all installers use C++ to do all of the grunt work. I am interested in creating my own to fully understand C++ and how it works. This why I really need to know how an installer is made. Any helpful advice is welcomed.
Thanks in advance.
"Mainstream": A shared packaging format seems elusive. However, there are a few multi-platform deployment tools available. Installsite.org has a list towards the bottom here. I guess the two most commonly used tools are (both are commercial):
Advanced Installer for Java / Advanced Installer Enterprise (Windows and Mac, no Linux)
Flexera InstallAnywhere (Windows, Mac, Linux)
From this answer:
I am sorry if this question is too local or duplicate. I searched in google but not got any idea.
I recently heard about SourceMonitor. I have downloaded SourceMonitor3.3 and I am using it in Windows.
I have heard SourceMonitor works on only windows. So to know about it I ma asking here.
Does it works on all all OS platforms? If not is there any code analyzer that works on all platforms?
The only available downloads for Source Monitor are for Windows. SOURCE: Source Monitor v3.4
Depending on what you need to analyze, some of the tools the Static Code Analysis Wikipedia list may work for your application. We have used FxCop for production and CodeRush in testing but we are a pure Microsoft shop.
I have a POS software and need to develop a collecting module for windows CE to run on a Honeywell Dolphin 6100 device.
I need to develop a simple application to run on a Honeywell 6100 device. This application should:
Get a list of products (code, description and price) from my POS software
Process Sales reading product's barcode showing Total due and number of items
Upload that sale to my POS software (via network, files, or something like that)
What are my options? Are there any Application builder for Windows CE? If not what could I use to develop such application?
You have a few options, but few (if any) of them will allow you to create the application without writing code. I'm aware of no "application builder" products that will get you there in Windows CE, and I've been working with CE for some time. That's not to say some obscure thing might not exist, but I am not aware of one.
You can write your application in .NET - either C# or VB.NET are supported - using the .NET Compact Framework (CF). For that you will need Visual Studio 2008 Professional and really little else, other than a device. There are lots of tutorials and online resources for CF development, so I won't put in a list of them here.
You can write your application in C/C++. For this, again you'd want to use Visual Studio 2008 Professional. Yes, there are options that use other compilers, but if you want to spend time actually writing the app and not building up a development tool chain and figuring out how to get it connected and debugging, then Visual Studio is the route you want.
If you'd like a non-Microsoft solution, there are others that are supported to more or less of a degree. NS Basic has been around a long time, so it's probably pretty robust and has reasonable support. I've never used it, but I've heard good things about it from those who have.
Anything else and you're a bit off the reservation. Support will likely be minimal at best, tooling will likely not be robust, support, tutorials and all of the other goodness that developers often rely on to move forward will be scant. You can likely get any language working under CE, given enough time and resources, but the options above are the most likely to lead to success.
Since you said you know Delphi and didn't want to learn another language, you can use Delphi Prism to write a client app to run on windows CE, pull the data you need, and post it to a webservice:
Is Delphi Prism a new version of Delphi .net?
http://en.wikipedia.org/wiki/Oxygene_(programming_language)
(edit) Just checked and it's now a part of this package:
http://www.embarcadero.com/products/rad-studio/faq
I would like to use dockpanel suite in Linux or Mono platform. I heard that there is some methods to modify the source code of dockpanel so that it can be used in Linux platform with all its features like drag and drop and all.Can anyone guide me to achieve that?
Due to its close bindings to Win32 API/PInvoke, currently it is impossible to use full features on Mono. You probably misinterpreted others' words.
Edited: DockPanel Suite 2.6 and above contains Mono support that I developed, http://dockpanelsuite.com
Yes and No.. You can write a silverlight 4.0 program and run it in a browser window on linux you can use silverlight controls.
If you are feeling really brave you can use MoonLight (silverlight by mono) to write full desktop apps on linux. One helpful set of tools (shameless plug) for doing this is MoonBase
But.. Generally, No, if you mean the WPF DockPanel control, you can't use that on top of Mono.
I know you've used WPF tag, but what you heard indicates rather winforms. In such case you may be interested in this. If you really had WPF in mind, look at the IanNorton's answer.
Anyone have experience with OPOS? I can't get my app to recognize the LDNs for the devices running on a 64 bit machine.
I've got down to the point where I know that the OleforRetail stuff is now under Wow6432Node in the Registry. I suspect the common controls can't find the LDN because of this. Is there any kind of workaround?
Failing that, is there a centralized OPOS development forum somewhere?
BTW: I work with the common controls supplied by Monroe Consulting.
Thanks!
What are you using to develop your application?
If you are using .NET you need to set it to be compiled as a 32-bit version.
Platform target: x86 on the c# project settings.
If a program is 32 bit or 64 bit decides where in the registry it looks for values.
All the OPOS com objects are 32-bit, so if you use a 64-bit program it will not find any information about them.
The biggest problem that I had is that the LDNs weren't being found by my app. Well it turns out that you have to run the OPOS driver configuration software as administrator to get it to manipulate the 32 bit section of the registry properly. The LDNs just weren't being written in the right place in the registry so my app couldn't find them.