Very Computer

Huh?  I didn't have to rename powerview to anything after installing
LW4, and I don't get any error codes.  I must be missing something here.

  - steve

The renaming is really a matter of restoring the correct name, which
someone at some site changed without realizing it would have an effect.

This problem isn't unique to PowerView.  A lot of Windows LW plug-ins
are going to be calling the Windows function GetModuleHandle() to get
access to the Windows resources (e.g. dialog box templates) stored in
the binary.  GetModuleHandle() takes the name of the plug-in file as an
argument, and if this doesn't match the actual filename, the call fails
because the requested file doesn't exist.  The plug-in then can't tell
Windows where to look for its resources.

It's just occurred to me, though, that Fori may be in a unique position
to avoid the problem with the OpenGL version of PowerView.  NT DLLs can
have an entry point that Windows calls when the DLL is first loaded, and
one of the things passed to this entry function is the instance handle
normally obtained by calling GetModuleHandle().  This isn't part of the
Win32s subset, so you sacrifice compatibility with Win 3.x, but that's
okay in this case, since OpenGL won't run under Win 3.x either.

I haven't tried it, so it's possible this approach isn't compatible with
the way LW attaches to plug-ins.

- Ernie

Just thinking out loud again...

Quote:

>This problem isn't unique to PowerView.  A lot of Windows LW plug-ins
>are going to be calling the Windows function GetModuleHandle() to get

Uhm, I use GetModuleFileName( NULL, buffer, sizeof(buffer) );
which doesn't require the hard-coded filename in a program.

In a DLL, just make nearly the same call in your DLL_PROCESS_ATTACH,
using the HANDLE hDLL passed in your DllMain() instead of NULL.

- John

        I've been meaning to post too.  I haven't renamed it all but
I always get some error opening module or something like that when it
starts.  This is on 4.0 Intel.  I will have to get the exact error
msg and post it here.  I also found it didn't run in anything lower
than 16bit color.  I was hoping it would work in 256.

mbc

--

| http://inswww.ins.cwru.edu/php/comet/
| LW FAQ, 3D Graphics & Animation and more!

This won't work for plug-ins, since what gets returned is the filename
of the *calling process*, which is the LW .EXE and not the plug-in.

Quote:> In a DLL, just make nearly the same call in your DLL_PROCESS_ATTACH,
> using the HANDLE hDLL passed in your DllMain() instead of NULL.

NT only.

- Ernie

Quote:> Interesting.  Mine's called "PowerView.p".  Seems to work fine.

That's the Amiga version.  The name problem is specific to the Windows
version.

- Ernie