- Wine-Devel - list.winehq.org

Re: shell shortcuts
by Martin Fuchs Jan. 10, 2004

Jan. 10, 2004

Hello again, I just had a look at some WIN98 shortcut files. They are also in ANSI format, not 16 bit Unicode: 00000000: 4C 00 00 00-01 14 02 00-00 00 00 00-C0 00 00 00 L ☺¶☻ └ 00000010: 00 00 00 46-1B 00 00 00-00 00 00 00-00 3E EA 22 F← >Û" 00000020: 0F 7D BD 01-00 98 32 60-C0 14 C2 01-00 3E EA 22 ☼}¢☺ ÿ2`└¶┬☺ >Û" 00000030: 0F 7D BD 01-00 D0 00 00-00 00 00 00-01 00 00 00 ☼}¢☺ ð ☺ 00000040: 00 00 00 00-00 00 00 00-00 00 00 00-61 00 14 00 a ¶ 00000050: 1F 0F E0 4F-D0 20 EA 3A-69 10 A2 D8-08 00 2B 30 ▼☼ÓOð Û:i►óÏ◘ +0 00000060: 30 9D 19 00-23 43 3A 5C-00 00 00 00-00 00 00 00 0Ø↓ #C:\ 00000070: 00 00 00 00-00 00 00 00-00 51 4D 17-00 31 00 00 QM↨ 1 00000080: 00 00 00 CF-2C 4C 27 10-00 57 49 4E-44 4F 57 53 ¤,L'► WINDOWS 00000090: 00 00 1B 00-32 00 00 D0-00 00 AB 24-20 98 00 00 ← 2 ð ½$ ÿ 000000A0: 4E 4F 54 45-50 41 44 2E-45 58 45 00-00 00 00 67 NOTEPAD.EXE g 000000B0: 00 00 00 1C-00 00 00 03-00 00 00 1C-00 00 00 32 ∟ ♥ ∟ 2 000000C0: 00 00 00 36-00 00 00 53-00 00 00 16-00 00 00 03 6 S ▬ ♥ 000000D0: 00 00 00 07-0D 2B 3E 10-00 00 00 57-49 4E 39 38 •♪+>► WIN98 000000E0: 00 43 3A 5C-00 1D 00 00-00 02 00 00-00 14 00 00 C:\ ↔ ☻ ¶ 000000F0: 00 00 00 00-00 00 00 02-00 5C 5C 4D-56 39 38 5C ☻ \\MV98\ 00000100: 43 00 57 49-4E 44 4F 57-53 5C 4E 4F-54 45 50 41 C WINDOWS\NOTEPA 00000110: 44 2E 45 58-45 00 0E 00-2E 2E 5C 4E-4F 54 45 50 D.EXE ♫ ..\NOTEP 00000120: 41 44 2E 45-58 45 0A 00-43 3A 5C 57-49 4E 44 4F AD.EXE◙ C:\WINDO 00000130: 57 53 00 00-00 00 - - WS -- Martin Fuchs martin-fuchs(a)gmx.net

1 0

Re: shell shorcuts
by Martin Fuchs Jan. 10, 2004

Jan. 10, 2004

> Hmm..., I KNOW 'SCF_UNICODE' is NOT 0x1000 in the first place, but why do > you say it's 0x80 ? > > Going by the copyrights, Marcus Meissner and Juergen Schmied did the initial > job, and perhaps one of them put this value. > I don't know about Juergen, but I have tremendous faith in Marcus (I use > SuSE you see ;) ), and there MUST have been some reason why 'SCF_UNICODE' > got the value 0x1000, although it seems to be wrong ! I looked into the CVS history logs and found, when SCF_UNC (rev. 1.21) and SCF_UNICODE (rev. 1.54) have been introduced: ---------------------------- revision 1.21 date: 1999/08/15 14:31:36; author: julliard; state: Exp; lines: +23 -15 Juergen Schmied <juergen.schmied(a)metronet.de> More use of rc files for strings and menus, fixes. First internal icons. ---------------------------- revision 1.54 date: 2003/05/21 18:50:53; author: julliard; state: Exp; lines: +701 -846 Mike McCormack <mike(a)codeweavers.com> Remove code that starts wineshelllink, instead create a windows compatible shortcut (*.lnk) file. After creating that file, start a link processor (winemenubuilder) on it, which reads it back then calls wineshelllink. Rework CreateStreamFromFile to create an IStream object that is writeable. ---------------------------- Perhaps we should ask Juergen Schmied and Mike McCormack where they got their defintions from. But I think SCF_UNC = 0x80 is the right one. > Hence, please consolidate your assigning it 0x80 with some examples/hexedits > so that I can answer when I get grilled ;) OK, you want to see some hex dumps. Here ist one for notepad.exe on WIN95: (sorry for the likely unreadable formating) 00000000: 4C 00 00 00-01 14 02 00-00 00 00 00-C0 00 00 00 L ?¶? ? 00000010: 00 00 00 46-0B 00 00 00-20 00 00 00-00 92 6A 89 F? Æjë 00000020: 12 9B BB 01-00 58 E5 4E-04 D7 C3 01-00 92 6A 89 ?ø?? XÕN?Î?? Æjë 00000030: 12 9B BB 01-00 8A 00 00-00 00 00 00-01 00 00 00 ?ø?? è ? 00000040: 00 00 00 00-00 00 00 00-00 00 00 00-5F 00 14 00 _ ¶ 00000050: 1F 00 E0 4F-D0 20 EA 3A-69 10 A2 D8-08 00 2B 30 ? ÓOð Û:i?óÏ? +0 00000060: 30 9D 19 00-23 43 3A 5C-00 00 00 00-00 00 00 00 0Ø? #C:\ 00000070: 00 00 00 00-00 00 00 00-00 F1 8A 15-00 31 00 00 ±è§ 1 00000080: 00 00 00 2A-30 9D 64 10-80 57 69 6E-39 35 00 00 *0Ød?ÇWin95 00000090: 1B 00 32 00-00 8A 00 00-25 21 60 59-20 80 4E 6F ? 2 è %!`Y ÇNo 000000A0: 74 65 70 61-64 2E 65 78-65 00 00 00-00 48 00 00 tepad.exe H 000000B0: 00 1C 00 00-00 01 00 00-00 1C 00 00-00 32 00 00 ? ? ? 2 000000C0: 00 00 00 00-31 47 00 00-00 16 00 00-00 03 00 00 1G ? ? 000000D0: 00 04 13 5F-37 10 00 00-00 57 49 4E-39 35 00 43 ??_7? WIN95 C 000000E0: 3A 5C 57 49-4E 39 35 5C-4E 4F 54 45-50 41 44 2E :\WIN95\NOTEPAD. 000000F0: 45 58 45 00-00 0E 00 2E-2E 5C 4E 4F-54 45 50 41 EXE ? ..\NOTEPA 00000100: 44 2E 45 58-45 - - D.EXE Here is the dump of a XP shourtcut file: 00000000: 4C 00 00 00-01 14 02 00-00 00 00 00-C0 00 00 00 L ?¶? ? 00000010: 00 00 00 46-9B 02 00 00-80 00 00 00-A0 A6 B2 00 Fø? Ç áª? 00000020: 9B C8 C3 01-76 98 AB AD-7D D7 C3 01-00 C8 2F B0 ø???vÿ½¡}Î?? ?/? 00000030: E5 27 C1 01-00 02 01 00-00 00 00 00-01 00 00 00 Õ'?? ?? ? 00000040: 00 00 00 00-00 00 00 00-00 00 00 00-F3 00 14 00 ¾ ¶ 00000050: 1F 50 E0 4F-D0 20 EA 3A-69 10 A2 D8-08 00 2B 30 ?PÓOð Û:i?óÏ? +0 00000060: 30 9D 19 00-2F 45 3A 5C-00 00 00 00-00 00 00 00 0Ø? /E:\ 00000070: 00 00 00 00-00 00 00 00-00 00 00 3C-00 31 00 00 < 1 00000080: 00 00 00 21-30 DC 73 10-00 57 49 4E-44 4F 57 53 !0?s? WINDOWS 00000090: 00 26 00 03-00 04 00 EF-BE 3C 2D 98-18 2A 30 11 & ? ? ´¥<-ÿ?*0? 000000A0: 6A 14 00 00-00 57 00 49-00 4E 00 44-00 4F 00 57 j¶ W I N D O W 000000B0: 00 53 00 00-00 16 00 40-00 31 00 00-00 00 00 25 S ? @ 1 % 000000C0: 30 47 BE 10-00 73 79 73-74 65 6D 33-32 00 00 28 0G¥? system32 ( 000000D0: 00 03 00 04-00 EF BE 3C-2D 98 18 2A-30 11 6A 14 ? ? ´¥<-ÿ?*0?j¶ 000000E0: 00 00 00 73-00 79 00 73-00 74 00 65-00 6D 00 33 s y s t e m 3 000000F0: 00 32 00 00-00 18 00 48-00 32 00 00-02 01 00 12 2 ? H 2 ?? ? 00000100: 2B 00 68 80-00 6E 6F 74-65 70 61 64-2E 65 78 65 + hÇ notepad.exe 00000110: 00 2E 00 03-00 04 00 EF-BE 96 2F 5C-76 2A 30 99 . ? ? ´¥û/\v*0Ö 00000120: 6B 14 00 00-00 6E 00 6F-00 74 00 65-00 70 00 61 k¶ n o t e p a 00000130: 00 64 00 2E-00 65 00 78-00 65 00 00-00 1A 00 00 d . e x e ? 00000140: 00 54 00 00-00 1C 00 00-00 01 00 00-00 1C 00 00 T ? ? ? 00000150: 00 33 00 00-00 00 00 00-00 53 00 00-00 17 00 00 3 S ? 00000160: 00 03 00 00-00 04 5D C9-28 10 00 00-00 53 79 73 ? ?]?(? Sys ... (snipped here) Look at the dword from 0x0014 to 0x0017. It is 0xB ("0B 00 00 00") for WIN95 and 0x29B ("9B 02 00 00") for XP. Please don't ask me for the meanging of this 0x200 - I just don't know it. But believe me - this bit with value 0x80 has been zero in any WIN95 created .lnk file I saw. And it has been set in all .lnk files of XP. As you know, WIN95 uses ANSI strings and XP uses UTF16 strings. Bit "0x1000" was never set in any OS's shortcut files. If you double-click a WIN95-link on XP it also works. You can even edit its properties. When saving it using XP, it get overwritten with the new format. The bit in question is now set! However Windows itself seems to ignore the bit when reading shortcut files. It can successfully read them regardless of me having changed the bit before. This is some kind of "file recovery" if you ask me. > However, I think that we should ALL handle strings as Unicode internally, > and convert to ANSI when required, and NOT the other way round. > Hence, we will be compatible with Win98/ME/2K/XP, as that's what M$ does... > If you see my code carefully, you will notice that EVERYTHING is handled as > Unicode internally. Of course. Shell link objects in memory should store the strings in Unicode format. > The flag 'SCF_UNICODE' is used to test the bit mask and determine if the > .lnk is serialized in Unicode or not... > I am pretty sure that Windows >95 handle EVERYTHING in Unicode, and thus a > wrong value of 'SCF_UNICODE' will ONLY mess up Win95 .lnk files ! > > If you can consolidate your defining 'SCF_UNICODE' as 0x80, I will ONLY be > too happy to incorporate that, else those still using Win95 (?) may suffer, > as Win95 handles strings as ANSI and not Unicode... Regards, Martin

1 0

Key signing party at wineconf
by Shachar Shemesh Jan. 9, 2004

Jan. 9, 2004

Hi all, I'm organizing a key signing party at wineconf. Anyone who wishes to participate, please email me the following details: Your full, real, name. It is not possible to participate in a key signing party using a nickname or a virtual identity. Sorry. Your key's fingerprint. Your actual key. Again, the key must have your real name on it (I am talking public key, of course. You should never send your private key to anyone). I am going to compile the list of names into a keyring and post it to a public key server. If, for any reason, you wish your key to remain unpublished (highly unrecommended), please note so in your mail. For more info about GPG key signing parties, check out the howto at http://www.cryptnet.net/fdp/crypto/gpg-party.html Shachar -- Shachar Shemesh Lingnu Open Systems Consulting http://www.lingnu.com/

1 0

Compilation broken in CVS
by Paul Millar Jan. 9, 2004

Jan. 9, 2004

Hi everyone, Looks like one of the patches broke compiling last night: http://www.astro.gla.ac.uk/users/paulm/WRT/buildinfo.php?id=472 I get error messages like: gcc -shared -Wl,-Bsymbolic,-z,defs,-init,__wine_spec_init,-fini,__wine_spec_fini winearts.drv.spec.o arts.o audio.o winearts.drv.dbg.o -o winearts.drv.so -L../../../libs/wine -lwine -L/usr/lib -ldl -lartsc -lpthread -L../../../libs/uuid -lwine_uuid -L../../../libs/port -lwine_port -lm -lc audio.o: In function `wodPlayer_WriteMaxFrags': /scratch/lilith1/paulm/wine/dlls/winmm/winearts/audio.c:722: undefined reference to `HeapRealloc' collect2: ld returned 1 exit status make[2]: *** [winearts.drv.so] Error 1 Anyone else get this? Cheers, Paul. ---- Paul Millar

3 4

Fwd: Re: [Discuss] Crossover Office with Microsoft Publish '97
by Jesse Hammons Jan. 9, 2004

Jan. 9, 2004

Does anybody know the basic problem with Microsoft Publisher '97 not working with wine? I'm willing to debug it a bit, but I want to find out how big of a project it is first. Or maybe somebody else is working on this already? Publisher '97 loads files and seems to almost complete functionality on my system. Unfortunately I can't click on any UI elements and keyboard events aren't processed. Someone seems to have even gotton Publisher 2000 to work (there is a workaround posted in the application database). However this fix doesn't work on Publisher '97. I would like to patch this, especially if it is relatively straightforward to do so. What kind of logging can I turn on to find out what is happening to the mouse/keyboard events, etc. Thanks, -Jesse --- Jeremy White <jwhite(a)codeweavers.com> wrote: > Subject: Re: [Discuss] Crossover Office with Microsoft Publish '97 > From: Jeremy White <jwhite(a)codeweavers.com> > To: discuss(a)crossover.codeweavers.com > Date: 09 Jan 2004 08:58:30 -0600 > > Hi Jesse, > > This is a great question, and the answer is to a Wine hacker -- > we'd love to have your help! > > The full set of resources for hacking on Wine are at www.winehq.org; > I know that's intimidating, but there are friendly folks > on irc at #winehq. If you show that you're willing to do > the elbow grease (and are a bit patient), I think you'll find > that folks will jump to help you. > > Finally, it's fairly straightforward to configure CrossOver to > use Wine from CVS; look in the config file in the cxoffice/etc > directory. > > Good hunting, and welcome! > > Cheers, > > Jeremy > > > On Thu, 2004-01-08 at 15:32, Jesse Hammons wrote: > > > > I have downloaded and installed the Crossover Office trial version > on > > my debian GNU/linux system (sarge, kernel version 2.4.20). I used > the > > Crossover setup program to install MS Publisher from the Office '97 > CD. > > > > Setup installs MS publisher with no errors. Publisher starts up, > and > > displays the initial dialog (where you can choose a template or > open an > > existing file). After cancelling this initial dialog, publisher is > > aware of the mouse location (it updates the rulers when you move > the > > mouse) but no mouse clicks or keyboard presses are processed. > > Something wrong with window modality? > > > > Is there anything I can tweak to try to get MS pub to work? How > about > > a way to log the translation of X events to windows events, so I > can > > try to trace where they are going? > > > > PS This behavior in crossover is the same behavior as when I tried > with > > wine-030618. > > > > Thanks, > > -Jesse > > > > __________________________________ > > Do you Yahoo!? > > Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes > > http://hotjobs.sweepstakes.yahoo.com/signingbonus > > _______________________________________________ > > discuss mailing list > > discuss(a)crossover.codeweavers.com > > http://crossover.codeweavers.com/mailman/listinfo/discuss > > > _______________________________________________ > discuss mailing list > discuss(a)crossover.codeweavers.com > http://crossover.codeweavers.com/mailman/listinfo/discuss __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus

1 0

Re: #6 - Add delay loading to rundll32
by Dmitry Timoshkov Jan. 9, 2004

Jan. 9, 2004

"Steven Edwards" <steven_ed4153(a)yahoo.com> wrote: > I hope my formatting is right. I use EditPlus to do my development and > it tends to not agree with Wine sources sometimes so I have to go back > to notepad to clean it up. With this patch I can compile rundll32 on > Mingw now. > > Changelog: > Delay load Wine16 APIs for Win16 dlls. Your patch is not only formatted badly, but it also does things not allowed in plain C - places variables in the middle of the function body. Please fix. -- Dmitry.

2 1

WWN broken
by Mike Hearn Jan. 9, 2004

Jan. 9, 2004

XML error: not well-formed (invalid token) at line 104 Looks like it contains a typo. I thought only 1 item was a bit strange :)

2 1

Re: #6 - Add delay loading to rundll32
by Andreas Mohr Jan. 9, 2004

Jan. 9, 2004

On Fri, Jan 09, 2004 at 07:14:07AM -0800, Steven Edwards wrote: > Hello, > I hope my formatting is right. I use EditPlus to do my development and As soon as you have to resort to phrases like "I hope...", you already know that you're in troubled and boiling water. ;-) - HeapFree( GetProcessHeap(), 0, dllA );^M - return ret;^M Andreas Mohr

1 0

Re: shell shorcuts
by Subhobroto Sinha Jan. 9, 2004

Jan. 9, 2004

One day thus spake Martin Fuchs: >I am working on the ReactOS Explorer, which uses Wine's shell32 implementation. >We already have made many bugfixes and estensions to the shell link and other >shell32 code. One of those extensions is the implementation of control panel in >shell namespace I am already aware of that (thanks to Steve), and I would appreciate if someone could send me the changes/patches to shell32 by the ReactOS team (even if the source does not compile) so I can have a look.. Perhaps you can send me a zip of the ReactOS shell32 directory (keep the makefiles and .defs out - send just the real source :) ) ? That will be nice >Well, I think it's because it has been defined wrong. I am currently using this >definition: >#define SCF_UNICODE 0x80 (instead of 0x1000) >This is at least compatible to links of WIN95 (ANSI strings) and WIN XP (UTF16 strings). >I did not yet test any other operating system versions. With this corrected >defintion and a few more extensions Stream_LoadString() works pretty well >on ReactOS. Hmm..., I KNOW 'SCF_UNICODE' is NOT 0x1000 in the first place, but why do you say it's 0x80 ? Going by the copyrights, Marcus Meissner and Juergen Schmied did the initial job, and perhaps one of them put this value. I don't know about Juergen, but I have tremendous faith in Marcus (I use SuSE you see ;) ), and there MUST have been some reason why 'SCF_UNICODE' got the value 0x1000, although it seems to be wrong ! Hence, please consolidate your assigning it 0x80 with some examples/hexedits so that I can answer when I get grilled ;) However, I think that we should ALL handle strings as Unicode internally, and convert to ANSI when required, and NOT the other way round. Hence, we will be compatible with Win98/ME/2K/XP, as that's what M$ does... If you see my code carefully, you will notice that EVERYTHING is handled as Unicode internally. The flag 'SCF_UNICODE' is used to test the bit mask and determine if the .lnk is serialized in Unicode or not... I am pretty sure that Windows >95 handle EVERYTHING in Unicode, and thus a wrong value of 'SCF_UNICODE' will ONLY mess up Win95 .lnk files ! If you can consolidate your defining 'SCF_UNICODE' as 0x80, I will ONLY be too happy to incorporate that, else those still using Win95 (?) may suffer, as Win95 handles strings as ANSI and not Unicode... Will send Alexandre my patch within the next few days as no one has objected to it being messy, so take the last chance ;) BTW Martin, great work with ROSExplorer, keep at it, and one day WINE will have a complete Desktop with shell namespaces ! Regards Subhobroto Sinha

2 1

reading relay log
by Ferenc Wagner Jan. 9, 2004

Jan. 9, 2004

Hi, I feel rather stupid, but need help understanding this. I managed to screw up winetest so that it runs into trouble. The relay trace goes like (indented by examine-relay) -------------------------------------------------------------------- 000a:Call comctl32.InitCommonControls() ret=40593c29 000a:Ret comctl32.InitCommonControls() retval=40def6d4 ret=40593c29 000a:Call kernel32.GetModuleHandleA(00000000) ret=40593c3c 000a:Ret kernel32.GetModuleHandleA() retval=40540000 ret=40593c3c 000a:Call user32.CreateDialogParamA(40540000,00000064,00000000,40593b4c,00000000) ret=40593c42 000a:Call kernel32.FindResourceA(40540000,00000064,00000005) ret=407aa47f 000a:Ret kernel32.FindResourceA() retval=405954f8 ret=407aa47f 000a:Call kernel32.LoadResource(40540000,405954f8) ret=407aa48a 000a:Ret kernel32.LoadResource() retval=40590d20 ret=407aa48a 000a:Call kernel32._EnterSysLevel(40810b00) ret=407c21b8 000a:Ret kernel32._EnterSysLevel() retval=00000008 ret=407c21b8 000a:Call kernel32._LeaveSysLevel(40810b00) ret=407c21dc 000a:Ret kernel32._LeaveSysLevel() retval=00000000 ret=407c21dc 000a:Call kernel32._EnterSysLevel(40810b00) ret=407c21b8 000a:Ret kernel32._EnterSysLevel() retval=00000008 ret=407c21b8 000a:Call kernel32._EnterSysLevel(40810b00) ret=407c21b8 000a:Ret kernel32._EnterSysLevel() retval=00000008 ret=407c21b8 000a:Call kernel32._LeaveSysLevel(40810b00) ret=407c21dc 000a:Ret kernel32._LeaveSysLevel() retval=00000000 ret=407c21dc 000a:Call ntdll.RtlAllocateHeap(40300000,00000000,0000001c) ret=407a6047 000a:Ret ntdll.RtlAllocateHeap() retval=40347998 ret=407a6047 000a:Call gdi32.CreateDCA(407f0e04 "DISPLAY",00000000,00000000,00000000) ret=407a6066 000a:Call ntdll.RtlCreateUnicodeStringFromAsciiz(40def3e8,407f0e04 "DISPLAY") ret=408994dd 000a:Ret ntdll.RtlCreateUnicodeStringFromAsciiz() retval=00000001 ret=408994dd 000a:Call kernel32._CheckNotSysLevel(408cf320) ret=408a56e8 000a:Ret kernel32._CheckNotSysLevel() retval=0000000a ret=408a56e8 000a:Call ntdll.RtlEnterCriticalSection(408cf400) ret=408ae109 000a:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=408ae109 000a:Call ntdll.RtlLeaveCriticalSection(408cf400) ret=408ae1d9 000a:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=408ae1d9 000a:Call kernel32._EnterSysLevel(408cf320) ret=408a50cf 000a:Ret kernel32._EnterSysLevel() retval=0000000c ret=408a50cf 000a:Call ntdll.RtlAllocateHeap(40300000,00000000,00000138) ret=408a5215 000a:Ret ntdll.RtlAllocateHeap() retval=403479c0 ret=408a5215 000a:Call x11drv.CreateDC(403479c0,403479d8,40def15c L"DISPLAY",00000000,00000000,00000000) ret=40899405 000a:Call ntdll.RtlAllocateHeap(40300000,00000008,0000008c) ret=409ee0de 000a:Ret ntdll.RtlAllocateHeap() retval=40347b00 ret=409ee0de 000a:Call gdi32.GetObjectType(0000007c) ret=409ee125 000a:Call kernel32._EnterSysLevel(408cf320) ret=408a5527 000a:Ret kernel32._EnterSysLevel() retval=0000000c ret=408a5527 000a:Call kernel32._LeaveSysLevel(408cf320) ret=408a56c3 000a:Ret kernel32._LeaveSysLevel() retval=00000000 ret=408a56c3 000a:Ret gdi32.GetObjectType() retval=00000003 ret=409ee125 000a:Call ntdll.RtlEnterCriticalSection(40a20700) ret=409fe8b0 000a:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=409fe8b0 err:ntdll:RtlpWaitForCriticalSection section 0x40334040 "?" wait timed out in thread 000a, blocked by 0009, retrying (60 sec) -------------------------------------------------------------------- which I don't understand given the definition -------------------------------------------------------------------- HWND WINAPI CreateDialogParamA( HINSTANCE hInst, LPCSTR name, HWND owner, DLGPROC dlgProc, LPARAM param ) { HRSRC hrsrc; LPCDLGTEMPLATEA ptr; if (!(hrsrc = FindResourceA( hInst, name, (LPSTR)RT_DIALOG ))) return 0; if (!(ptr = (LPCDLGTEMPLATEA)LoadResource(hInst, hrsrc))) return 0; return CreateDialogIndirectParamA( hInst, ptr, owner, dlgProc, param ); } -------------------------------------------------------------------- After LoadResource returns, I would expect a call to CreateDialogIndirectParamA instead of the SysLevels etc. Could somebody explain this, please? Thanks a lot, Feri.

7 19