Thank you for the answer. Unfortunately my knowledge about Windows API is very restricted. If I would try to help, I would make it more unstable than Windows already is...
May I gently ask you where I can download the dlls? I wasn't able to find the how to document. Last time I copied the dlls to the windows\system directory, but the programs weren't able to find them.

Regards,
Daniel Ferber

Hi,
�
I am new to Lazarus. Yesterday I was making my
first attempt to run the examples.
I already had success in making�the units and
demos, but they require some dlls to emulate the GTK windgets under Windows. Unfortunately I had similar troubles as "mooseman". <FONT face=Arial size=2>If I understood right, I�may define "Win" and undefine "GTK" in the interfaces.pp file to solve this problem. When doing so,�the<FONT face=Arial size=2> following error message appears while recompileng Lazarus:
...
Target OS: Win32 for i386Compiling
mwkeycmds.pasCompiling C:\command\pp\lazarus\lcl\intCompiling C:\command\pp\lazarus\lcl\intCompiling
C:\command\pp\lazarus\lcl\intFatal: Can't find unit WIN32INTmake.exe[2]: *** [mwkeycmds.ppw] Errormake.exe[2]: Leaving directory `c:/commmake.exe[1]: *** [mwedit_all] Error 2make.exe[1]: Leaving directory `c:/comm
�
Any help or advices? The win32int file is in the
.lcl\interfaces\win32 directory. I suppose I am doing something wrong.
�
Regards,
Daniel Ferber

AM Ferber wrote

If I understood right, I may define "Win" and undefine "GTK" in the interfaces.pp file to solve this problem. When doing so, the following error message appears while recompileng Lazarus:

That is the intent, however, no work has been done on implementing native windows components in a long time. I should know, I believe I was the last to even try, and I only got as far as a form and a button that didn't quite work right. For now, all components are GTK based, even under windows, so you will need the windows GTK dll's. If you would like to jump in and work on the native windows components, feel free. I can give you a few pointers to get started, but for the most part, you'll need to know how to create the components from scratch, then look at the GTK code for the LCL interface, and write the code to translate one set of methods to the other. It looks clunky and slow, but it's a good way to make sure the LCL is truly cross platform.

Jeff.