Author Topic: FileIconInit ...cant call directly?  (Read 5191 times)

xandaz

  • Member
  • **
  • Posts: 129
  • I luv you babe
FileIconInit ...cant call directly?
« on: July 10, 2013, 07:56:04 AM »
   How is it done?
Quote
FileIconInit is not included in a header file. You must call it directly from Shell32.dll, using ordinal 660.

   has anyonne done this?
   ty
nothing to report.

xandaz

  • Member
  • **
  • Posts: 129
  • I luv you babe
Re: FileIconInit ...cant call directly?
« Reply #1 on: July 10, 2013, 07:58:38 AM »
   oh yeah... GetProcAddress. ooops thanks
nothing to report.

xandaz

  • Member
  • **
  • Posts: 129
  • I luv you babe
Re: FileIconInit ...cant call directly?
« Reply #2 on: July 10, 2013, 08:47:18 AM »
how about SHGetImageList? anyone ever used it? i'm having trouble declaring that GUID. I've seen this form on the web.
Code: [Select]
IID_IImageList TGUID <46EB5926h,582Eh,4017h,9FDFh,0E8998DAA0950h> but it shows too much initial values. Aaarg,
nothing to report.

jj2007

  • Member
  • *****
  • Posts: 10094
  • Assembler is fun ;-)
    • MasmBasic
Re: FileIconInit ...cant call directly?
« Reply #3 on: July 10, 2013, 03:41:08 PM »
http://www.masmforum.com/board/index.php?topic=15414.0

Faiseur asked the same question - and got no reply...
No C++ code around? PowerBasic maybe?

Yuri

  • Member
  • **
  • Posts: 175
Re: FileIconInit ...cant call directly?
« Reply #4 on: July 10, 2013, 07:35:13 PM »
The last two numbers are actually a byte array.
Code: [Select]
<46EB5926h,582Eh,4017h,<9Fh,0DFh,0E8h,99h,8Dh,0AAh,09h,50h>>

xandaz

  • Member
  • **
  • Posts: 129
  • I luv you babe
Re: FileIconInit ...cant call directly?
« Reply #5 on: July 12, 2013, 10:30:59 AM »
   yeah yuri. took a while to understand how to declare to GUID correctly. The answer is of course:
Code: [Select]
invoke GetModuleHandle,str$("Shell32")
invoke GetProcAddress,eax
call eax
ty guys and regs
nothing to report.

xandaz

  • Member
  • **
  • Posts: 129
  • I luv you babe
Re: FileIconInit ...cant call directly?
« Reply #6 on: July 12, 2013, 10:32:05 AM »
oops.
Code: [Select]
GetProcAddress,eax,660sorry typo forgetful mind
nothing to report.

TWell

  • Member
  • ****
  • Posts: 748
Re: FileIconInit ...cant call directly?
« Reply #7 on: July 12, 2013, 02:02:38 PM »
Look here

jj2007

  • Member
  • *****
  • Posts: 10094
  • Assembler is fun ;-)
    • MasmBasic
Re: FileIconInit ...cant call directly?
« Reply #8 on: July 12, 2013, 04:15:46 PM »
   yeah yuri. took a while to understand how to declare to GUID correctly. The answer is of course:
invoke GetModuleHandle,str$("Shell32")
invoke GetProcAddress,eax
call eax

ty guys and regs

chr$("Shell32") might work even better ;-)

xandaz

  • Member
  • **
  • Posts: 129
  • I luv you babe
Re: FileIconInit ...cant call directly?
« Reply #9 on: August 22, 2013, 07:15:59 AM »
  hi... sorry for replying so late. Im a little past that. And sorry for the str$ - i dont really use those macros. i kinda guessed from my BASIC memories.
nothing to report.