Gaulish Gaming Banquet: general

pegperegogaucho

But what is the ID? :Obelul:

hesopesomeso

{ EF985E71 - D5C7 - 42D4 - BA4D - 2D073E2E96F4 }

hesopesomeso

If you're asking what's used for, I guess for getting COM registered objects?

hesopesomeso

I'm not a windows programmer, I don't know :KEKW:

pegperegogaucho

I'm not familiar with COM, but I just researched that the mapping CLSID <=> COM Class is stored in the registry, for me it looks like this: Maybe someone affected by the bug can check the registry if the entries exist? Unless you already tried that, Heso

hesopesomeso

I did, checked both 64 & 32 registry locations. In fact, they are mapped to system32 (even in the case of the 32-bit version). I tried changing it to sysWOW64, to no avail (changing that for wine worked ok).

pegperegogaucho

pegperegogaucho

Super issue

hesopesomeso

This one might top the amdgpu issue, eh :KEKW:

pegperegogaucho

That at least gives an error :KEKW:

pegperegogaucho

hesopesomeso

That's accurate as hell haha

hesopesomeso

Anyways here's the same location (the registry is a total mess :KEKW:

there's *Classes/WOW6432Node/CLSID*, but there's also *WOW6432NODE/Classes/CLSID*)

pegperegogaucho

Does Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{EF24F689-14F8-4D92-B4AF-D7B1F0E70FD4} exist?

hesopesomeso

Right here

pegperegogaucho

Damn, what could the error be? :PogelixWeird:

pegperegogaucho

Maybe you have to debug the windows functions as well :Obelul:

hesopesomeso

I assume either they changed the behavior (most likely), or a bug :Obelul:

hesopesomeso

naaah im fed up with this os :KEKW:

hesopesomeso

when i say they changed the behavior, i mean they broke backwards compatibility... so either way a potential bug? might be a good idea to file it

#general