JEDI Windows API » JWA Downloads

Releases for Delphi 2010

Christian Wimmer — Tue, 22 Sep 2009 22:07:07 +0000

JEDI Windows API (JWAL) and JEDI Windows Security Library (JWSCL) are now available in version 2.3 and 0.9.3. They support Delphi 2010.
You can download them or use the new Subversion branches.

If you find bugs, have questions, hints or want to participate: just mail us.

Downloads

Download from one of the Sourceforge mirrors at:

https://sourceforge.net/projects/jedi-apilib/files

(The download has Subversion folders .SVN which you can use to get updates through a Subversion Client. See below.)

AND do not forget to read:

How to Setup the JEDI Windows API Library (JWA).
and
How to Setup the JEDI Windows Security Code Library (JWSCL).

Subversion Access

You can use a Subversion client, like TortoiseSVN, to download the sources directly.
Advantage: You can easily get updated sources.

JWA

https://jedi-apilib.svn.sourceforge.net/svnroot/jedi-apilib/jwapi/branches/2.3

JWSCL

https://jedi-apilib.svn.sourceforge.net/svnroot/jedi-apilib/jwscl/branches/0.9.3

Click on the turtle to get the source if you have installed TortoiseSVN.

Remaining Issues

22. August 2009

There is an issue left with D2010:
The interface IXMLElement is no more available in file msxml.pas (MS XML Version 1). So the file JwaUrlMon.pas has been changed to use a Pointer instead of the IXMLElement interface. Unfortunately, the new IXmlDOMElement (MS XML Version 2) is not compatible with the old interface.
If you have an idea how to fix that, please mail to us.

Pre-Release of JEDI API 2.2 & WSCL 0.9.2

Christian Wimmer — Sat, 30 Aug 2008 19:23:31 +0000

JEDI API and JWSCL compile with Delphi2009 and also the examples work as far as I could test it.

I’ve created a Subversion branch for each project:

JEDI API Version 2.2 pre-release

https://jedi-apilib.svn.sourceforge.net/svnroot/jedi-apilib/jwapi/branches/2.2a

JEDI WSCL Version 0.9.2 pre-release

https://jedi-apilib.svn.sourceforge.net/svnroot/jedi-apilib/jwscl/branches/0.9.2a

Download a ZIP package with both projects from SourceForge. Always update this package with a SVN client to get best quality.

As you can see we abandoned the revision numbers and instead use simple version numbers (as people are more used to those).
These pre-releases won’t be available as packages from sourceforge.net!

Please!
We encourage you to use, test and check the released projects!

If you find errors, have problems or questions don’t hesitate to ask them in the mailinglist, newsgroup, JEDI IssueTracker or send it to mail[at)delphi-jedi.net .

Regards
Christian Wimmer

Winlogon Notification Package

Christian Wimmer — Tue, 27 May 2008 18:07:05 +0000

What is that? MSDN say’s: A Winlogon Notification Package is a DLL that exports functions that handle Winlogon events. For example, when a user logs onto the system, Winlogon calls each notification package’s logon event handler function to provide information about the event.

So you might know, the mechanism of Winlogon Notification Package is available in Windows 2000, Windows XP and Windows 2003 Server. In contrast to Windows Vista, it is completely different, maybe I’ll come back with separate tutorial describing how to build a notification package for Windows Vista.

I’m going to demonstrate here, how to create such a notification package and as a special gift, we will learn how to create a PNG image with drop shadow effect, which we will use later to draw a transparent window inside the Winlogon Desktop.

It’s time for our Winlogon Notification Package. Start Delphi and create a new DLL project.

What we need to do next is to define the Message Callback and the WLXNotificationInfo, as described in MSDN

Type
// this callback function does not return a value as described on mdsn.

TFnMsgeCallback = function (bVerbose: Boolean; lpMessage: PWideChar): Cardinal; stdcall;

// this structure stores information about a Winlogon event.

TWlxNotificationInfo = record
Size: Cardinal;
Flags: Cardinal;
UserName: PWideChar;
Domain: PWideChar;
WindowStation: PWideChar;
Token: Cardinal;
Desktop: Cardinal;
StatusCallback: TFnMsgeCallback;
end;
PWlxNotificationInfo = ^TWlxNotificationInfo;

{ winlogon can inform about the following events:
Lock,
Lockoff,
Logon,
Shutdown,
StartScreensave,
StartShell,
StartUp,
StopScreenSaver,
Unlock

For a complete describtion of those events look at:

http://msdn.microsoft.com/en-us/library/aa380544(VS.85).aspx
}

// example of handling the Logon Message

procedure LogonHandler(Info: PWlxNotificationInfo); stdcall;
begin

end;

// the entrance function for DLL

procedure EntryPointProc(reason: integer);
begin
case reason of
DLL_PROCESS_ATTACH: //1
Begin
// Disable DLL_THREAD_ATTACH & DLL_THREAD_DETACH
// notification calls. This is a performance optimization
// for multithreaded applications that do not need
// thread-level notifications of attachment or
// detachment.

DisableThreadLibraryCalls(hInstance);

end;
DLL_THREAD_ATTACH: //2
begin

end;
DLL_PROCESS_DETACH: //3
begin

end;
DLL_THREAD_DETACH: //0
begin

end;
end;

end;

// define the exports for the DLL

exports
LogonHandler;

begin
DllProc := @EntryPointProc;
DllProc(DLL_PROCESS_ATTACH);
end.

Our Prototype, is ready to use. The compiled DLL has to be in the following folder:

C:\Windows\System32 (adapt it to your environment)

Now we can inform the operating system that we created a Winlogon Notification Package. This step will be done in the registry under the following key:

HKey_Local_Machine\Software\Microsoft\WindowsNT\
CurrentVersion\Winlogon\Notify\YourNotification

Name	Type	Value
DLLName	REG_SZ	C:\Windows\System32\YourDLLName.dll
Asynchronous	REG_DWORD	0
Impersonate	REG_DWORD	0
Logon	REG_SZ	LogonHandler

The valid values are described in this MSDN article.

Creating the PNG Image

For completing this Project you will need to download the following:

Graphics32 Library
Graphics32 is a graphics library for Delphi and Kylix/CLX. Optimized for 32-bit pixel formats, it provides fast operations with pixels and graphic primitives. In most cases Graphics32 considerably outperforms the standard TBitmap/TCanvas methods.

PNG Components
Delphi VCL Components with PNG Image support.

What you’ll need is an already exisiting PNG or a new one. I’ll use with the Jedi Api WSCL Logo.
Open the Logo in Photoshop but remember this can be done in almost any other Graphic Application which supports PNG and layer based drawing.

The Logo from this site is already a PNG, so you will see a transparent background when it is opened in Photoshop. If you like to add a drop shadow style to it, you won’t see it,because of the mentioned transparent background. It is also a problem on a black background, btw. So first thing to do is to add a temporary background layer into the Logo. To do so, click on the “Create New Layer Symbol” in the layer palette (indicated as a small notepad icon).

Now select the new created layer by clicking on it and drag it behind the Logo layer. With the new layer still selected, switch to the “Tools Window” and select the “Paint Bucket Tool“. Select white as your foreground color. If you have another color as foreground color, simply press d and then x. In this way it will reset the foreground and backgound colors. Now click inside your image on the transparent part and you’ll see the Logo with a white background applied.

Switch to your layers palette and double click on the Logo layer. The “Layers Styles Dialog” should be visible now. Select “Drop Shadow” and you can adjust the angle of the drop shadow and its size. While you adjust it, also watch the Logo. Photoshop shows you a preview of the changes. If you’re satisfied with your settings hit ok.

At this time, we don’t need our white background layer anymore, so select it and drag it to the trash can symbol in the layer palette. It will be deleted then. Afterwards save the Logo, select PNG as the file format and a new window will appear (PNG Options). Select none and hit ok.

There also exists a small video presentation which will help you.

Drawing the PNG onto the Form Canvas

The following source is kindly provided by Coder90. He wrote a nice example in a german delphi forum

The Sources
I won’t go into any details here, basically the procedure will load the PNG into a Bitmap32 Object and blends it to the forms canvas.

Type
interface

uses
Windows, Messages, SysUtils, Variants, Classes, Graphics, Controls, Forms,
Dialogs, ExtCtrls, StdCtrls, GR32;

public
{ Public declarations }
BMP32 : TBitmap32;
BlendF: TBlendFunction;
P: TPoint;
Size: TSize;
procedure BlendIt;
end;

procedure LoadPNGintoBitmap32(DstBitmap: TBitmap32;
Filename: String;
out AlphaChannelUsed: Boolean); overload;

procedure LoadPNGintoBitmap32(DstBitmap: TBitmap32;
SrcStream: TStream;
out AlphaChannelUsed: Boolean); overload;

procedure LoadPNGintoBitmap32(DstBitmap: TBitmap32;
szSection : PChar;
szName : String;
out AlphaChannelUsed: Boolean); overload;

uses PNGImage;

procedure LoadPNGintoBitmap32(DstBitmap: TBitmap32;
SrcStream: TStream;
out AlphaChannelUsed: Boolean);
var
PNGObject: TPNGObject;
TransparentColor: TColor32;
PixelPtr: PColor32;
AlphaPtr: PByte;
X, Y: Integer;
begin
PNGObject := nil;
try
PNGObject := TPngObject.Create;
PNGObject.LoadFromStream(SrcStream);

DstBitmap.Assign(PNGObject);
DstBitmap.ResetAlpha;

case PNGObject.TransparencyMode of
ptmPartial:
begin
if (PNGObject.Header.ColorType = COLOR_GRAYSCALEALPHA) or
(PNGObject.Header.ColorType = COLOR_RGBALPHA) then
begin
PixelPtr := PColor32(@DstBitmap.Bits[0]);
for Y := 0 to DstBitmap.Height – 1 do
begin
AlphaPtr := PByte(PNGObject.AlphaScanline[Y]);
for X := 0 to DstBitmap.Width – 1 do
begin
PixelPtr^ := (PixelPtr^ and $00FFFFFF) or (TColor32(AlphaPtr^) shl 24);
Inc(PixelPtr);
Inc(AlphaPtr);
end;
end;

AlphaChannelUsed := True;
end;
end;
ptmBit:
begin
TransparentColor := Color32(PNGObject.TransparentColor);
PixelPtr := PColor32(@DstBitmap.Bits[0]);
for X := 0 to (DstBitmap.Height – 1) * (DstBitmap.Width – 1) do
begin
if PixelPtr^ = TransparentColor then
PixelPtr^ := PixelPtr^ and $00FFFFFF;
Inc(PixelPtr);
end;

AlphaChannelUsed := True;
end;
ptmNone:
AlphaChannelUsed := False;
end;
finally
if Assigned(PNGObject) then PNGObject.Free;
end;
end;

procedure LoadPNGintoBitmap32(DstBitmap: TBitmap32;
Filename: String;
out AlphaChannelUsed: Boolean);
var
FileStream: TFileStream;
begin
FileStream := TFileStream.Create(Filename, fmOpenRead);
try
LoadPNGintoBitmap32(DstBitmap, FileStream, AlphaChannelUsed);
finally
FileStream.Free;
end;
end;

procedure LoadPNGintoBitmap32(DstBitmap: TBitmap32;
szSection : PChar;
szName : String;
out AlphaChannelUsed: Boolean);
var
Stream: TResourceStream;
begin
Stream := TResourceStream.Create(hInstance, szName, PChar(szSection));
try
LoadPNGintoBitmap32(DstBitmap, Stream, AlphaChannelUsed);
finally
Stream.Free;
end;
end;

{ Works only Win2000_Up }

procedure TForm1.BlendIt;
var
Alpha: Boolean;
begin
BMP32 := TBitmap32.Create;
{Load PNG from File
LoadPNGintoBitmap32(BMP32, ExtractFilePath(ParamStr(0)) + ‘WSCL.png’, Alpha);
}
// Load PNG From Resource
LoadPNGintoBitmap32(BMP32, PChar(‘PNG’), ‘WSCL’, Alpha);

setWindowLong(Handle, GWL_EXSTYLE,
getWindowLong(Handle, GWL_EXSTYLE) or WS_EX_LAYERED {or WS_EX_TRANSPARENT});
// WS_EX_TRANSPARENT makes the Window for MouseClicks transparent…

BlendF.BlendOp := AC_SRC_OVER;
BlendF.BlendFlags := 0;
BlendF.SourceConstantAlpha := 255;
BlendF.AlphaFormat := AC_SRC_ALPHA;
P := Point(0, 0);
Size.cx := BMP32.Width;
Size.cy := BMP32.Height;

UpdateLayeredWindow(Handle, 0, nil, @Size, BMP32.Handle, @P, 0, @BlendF, ULW_ALPHA);

// Set Window on Top
SetWindowPos(Handle, HWND_TOPMOST, Left, Top, Width, Height,
SWP_NOACTIVATE or SWP_NOMOVE or SWP_NOSIZE);

// Set Parent to Desktop
SetWindowLong(Handle, GWL_HWNDPARENT, 0);

// Hide Window from Taskbar
SetWindowLong(Handle, GWL_EXSTYLE,
GetWindowLong(Handle, GWL_EXSTYLE) or
WS_EX_TOOLWINDOW and not WS_EX_APPWINDOW);
end;

Call it in the FormOnCreate handler and don’t forget to free the Bitmap32 Object, a good place e.g. would be on the FormOnDestroy Handler.

Additional informations for you

I have to tell you that the first version of this package was slightly different than the one I’ll post here.
Well I used an external executeable which was called from my DLL when the LogonEvent was called.

But I encountered a big problem with that technique. One of the biggest problems were that my external application was executed more then once. Additionally I wasn’t able to close it. Neither Application.Terminate nor Application.Mainform.Close worked here. I did some experiments with a mutex which worked in some cases, but then, Christian Wimmer gave me many good ideas and suggestions.

So the improvements were:

The transparent Window is now directly created inside of the Winlogon Process by creating a new thread object.
Christian implemented an TApplication.OnIdle handler inside the thread object which will safely close the transparent window when it isn’t needed anymore.

Prerequisites:

The following Delphi packages are necessary. They are not included and must therfore downloaded and installed (if necessary) separately. Please, also recognize the license of these packages. The winlogon examples does only have a Copyright and no Warranty license.

Download:

3rd Party Components and Library’s you need to download:
Graphics32
PNG Components

Jedi Tutorial Files:
Photoshop Tutorial
(dowload size: 2.12 MB Format: AVI)
winlogon
(dowload size: 82.2 KB Format: ZIP)

Warning:

If you want to use such a Winlogon Notification DLL in a productive system you have to make sure that the wrong person can’t manipulate the DLL file. This can be done by setting the file’s access control list to allow only write access to SYSTEM and Administrators. There is no need for other users to have even read access, since the DLL is only used by winlogon. Furthermore you should save this file in a save place like the System32 folder.

Conclusion:

I hope you learned something new and had as much fun as I had writing this little tutorial for you!
My biggest thanks fly out to Christian Wimmer for all his support and help for making me finish this project.

Kindest regards
stOrM!

(contact by comments or mail @ JEDI)

The Delphi JEDI Project needs your help

Remko — Sun, 20 Apr 2008 20:16:40 +0000

The JEDI API Library project (JWA) has been successfully revived from a sleep status to an active project with lots of ambitions. Some recent achievements are the new include model of JWA, the release of JWSCL (the Security Library) and of course the “birth” of this blog.

We made a roadmap for JWA and JWSCL which includes “unicodifying” (Nick Hodges gave birth to a new word, meaning making the code ready for the next Delphi) and converting new Vista/Server 2008 API’s.

To help us fullfill these ambitions and continue contributing to the Delphi Community, we are looking for experienced Delphi developers to help us with the following tasks:

Maintaining and extending the Jedi API Library (convert new header files, fix errors in existing code).
Maintaining and extending the Jedi Windows Security Code Library (use and test the library, contribute new code, maintain documentation, Active Directory).
Create examples and write blog posts about using JWA and/or JWSCL.

NTStatus

Christian Wimmer — Fri, 04 Apr 2008 14:22:00 +0000

NTStatus converts an error number into a NTStatus error message.
It is very helpful if you encounter error numbers in debugging sessions but cannot comprehend its sense.

This application was written by Assarbad. Get the application written in Delphi and using non-VCL at these locations (including source):

http://assarbad.net/stuff/ntstatus.rar
http://assarbad.net/stuff/ntstatus.zip

All the error messages – but no warranty

Christian Wimmer — Mon, 24 Mar 2008 16:00:39 +0000

There are many error messages in a Windows System. Actually a MSDN article describes them – or better: part of them. However they weren’t enough for me, so I decided to get all of them.

FormatMessage is the way to convert between the error number and the error text. So why do not simply go from zero to 4294967295 (high(Cardinal)) and convert all these possible error numbers to an error text by using FormatMessage? I did. And you know what? It works. I got all the possible error numbers in only 6 hours and 33 minutes.

Here you can download the code tables (retrieved from a Windows Vista)

Use them for your joy. However I cannot grant any guarantee for correctness, completeness or anything else. It is even possible that error codes and messages are going to change in future. This data comes straight from a Vista system and is not altered in any way but only for formating purposes.

How to submit header conversions

Christian Wimmer — Thu, 13 Mar 2008 21:38:34 +0000

Please read this “How to” before submitting any Header Conversions to us.

Then you can submit the headers to us by mail.

JEDI Windows API Release 315

Christian Wimmer — Sun, 21 Oct 2007 13:25:16 +0000

The JEDI Windows API Download Revision 315 is now available on SourceForge.

Direct link (4,5mb)

Changes:
+ Many bugfixes
+ additional terminal service functions (jwaWinsta.pas)
+ added JwaWinInet.pas