Your work-around is pretty neat Ingo, though all of these are probably
the shortest lived work-arounds in history. Guess we'll never see Rons.


ingo wrote:
> 
> Thanks Bob,
> 
> In the meanwhile I found an other way to get both versions running. I've Put
> all the patches in a separate directory (D:\POV-Ray-Patch) with a complete
> copy of the subdirectory's bin, help,ini,insertmenu,renderer. Then I use a
> batchfile to start a patch, before that the batchfile changes the registry
> setting. For this I use an utility REG.EXE from
> http://www.mindspring.com/~dgthomas
> 
> Here is the (ugly) batchfile:
> reg -set
> HKLM\Software\POV-Ray\CurrentVersion\Windows\Home="D:\POV-Ray-Patch"
> reg -set HKLM\Software\POV-Ray\v3.1\Windows\Home="D:\POV-Ray-Patch"
> D:\POV-Ray-Patch\bin\uvpov.exe
> reg -set HKLM\Software\POV-Ray\CurrentVersion\Windows\Home="D:\POV-Ray"
> reg -set HKLM\Software\POV-Ray\v3.1\Windows\Home="D:\POV-Ray"
> 
> after closing uvpov the registry is changed back.
> 
> ingo
> 
> Bob Hughes heeft geschreven in bericht <36FF2858.13F820B2@aol.com>...
> >The following works in Win95 anyway, so should be pretty much the same
> >for 98 or NT I would think. Only a suggested possibility here.
> >Make a sub-folder for the patch or patches in the bin folder, I used
> >Photon and Super for names....
> > snip
> 
> --
> Met dank aan de muze met het glazen oog.

-- 
 omniVERSE: beyond the universe
  http://members.aol.com/inversez/homepage.htm
 mailto:inv### [at] aolcom?Subject=PoV-News

Post a reply to this message

Tried but failed here.
Is there a need for a re-boot first?
I just did the d/l, Run... pve31up.exe, it installed okay and I ran the
patch executables direct from there bin\Photon or bin\Super sub-folders.
The older cmedit.dll and cmax101.dll files are in both.
Hope to find after I sign off, shutdown, and restart that it will be
okay. Let you know in a few.


"povray.org admin team" wrote:
> 
> par### [at] my-dejanewscom (Ron Parker) wrote:
> 
> >There probably is, but it will require changes to the code.  If Chris
> >doesn't end up creating a version that looks in the current directory
> >for the codemax DLLs, I'm sure I could add a command-line parameter or
> >something to the Superpatch to change the default behaviour.
> 
> Please try downloading
> 
>   http://www.povray.org/temp/pve31up.exe
> 
> and install that. It's a new way of installing the update that I want tested
> (other users please try it as well). It sets the 3.1e variable in the registry
> (textureview wants this).
> 
> In addition, however, the exe included (3.1e.watcom.win32.r1) will load
> cmedit.dll from the current directory if it is found there ; otherwise it loads
> it from the path shown in the directory.

-- 
 omniVERSE: beyond the universe
  http://members.aol.com/inversez/homepage.htm
 mailto:inv### [at] aolcom?Subject=PoV-News

Post a reply to this message

Seems I may have misunderstood that update, sorry if I was confusing
others about it. I took it to mean the patches could now be run as usual
just by installing the pve31up.exe, not that it might be a new
executable and registry update for later patch updates to be created
from, etc.
Am I making sense?
In any case, a "no go" on the patch runs after install of this. Same
editor DLL error occurs.

-- 
 omniVERSE: beyond the universe
  http://members.aol.com/inversez/homepage.htm
 mailto:inv### [at] aolcom?Subject=PoV-News

Post a reply to this message

Bob Hughes <inv### [at] aolcom> wrote:

>I just did the d/l, Run... pve31up.exe, it installed okay and I ran the
>patch executables direct from there bin\Photon or bin\Super sub-folders.
>The older cmedit.dll and cmax101.dll files are in both.

I'm not sure I follow you ... from my reading of your message, it seems that
you are expecting the patch executables to suddenly start acting differently as
a result of updating the official PVENGINE.EXE ?

If that's not what you're saying, the please explain it to me a little more.

If it is what you're saying, then it's not possible - the official POVWIN
update won't affect the way that the patched versions work. The change allows
PVENGINE.EXE to load its own editor DLL from the current working directory
(whatever that happens to be when it is loaded - typically the same one as the
EXE is in).

The patches will - of course - continue to load the DLL from wherever they are
currently loading their DLL's. We can't magically influence their operation.

So, put the new PVENGINE.EXE and the new DLL's into their own directory (e.g.
bin\official or something). Copy the old editor DLL's into bin. That should
work (though I haven't tried it so your milage will vary).

Post a reply to this message

I see, I misunderstood, which I started to grasp right away when the
patches failed to run the editor, obviously.
I was thinking the Windows registry was being changed in order to allow
an external patch version, such as the Super and Photon ones, to operate
after the "update" installation.
My humble apologies for stirring up any possible confusions.


"povray.org admin team" wrote:
> 
> Bob Hughes <inv### [at] aolcom> wrote:
> 
> >I just did the d/l, Run... pve31up.exe, it installed okay and I ran the
> >patch executables direct from there bin\Photon or bin\Super sub-folders.
> >The older cmedit.dll and cmax101.dll files are in both.
> 
> I'm not sure I follow you ... from my reading of your message, it seems that
> you are expecting the patch executables to suddenly start acting differently as
> a result of updating the official PVENGINE.EXE ?
> 
> If that's not what you're saying, the please explain it to me a little more.
> 
> If it is what you're saying, then it's not possible - the official POVWIN
> update won't affect the way that the patched versions work. The change allows
> PVENGINE.EXE to load its own editor DLL from the current working directory
> (whatever that happens to be when it is loaded - typically the same one as the
> EXE is in).
> 
> The patches will - of course - continue to load the DLL from wherever they are
> currently loading their DLL's. We can't magically influence their operation.
> 
> So, put the new PVENGINE.EXE and the new DLL's into their own directory (e.g.
> bin\official or something). Copy the old editor DLL's into bin. That should
> work (though I haven't tried it so your milage will vary).

-- 
 omniVERSE: beyond the universe
  http://members.aol.com/inversez/homepage.htm
 mailto:inv### [at] aolcom?Subject=PoV-News

Post a reply to this message

Bob Hughes <inv### [at] aolcom> wrote:

>I see, I misunderstood, which I started to grasp right away when the
>patches failed to run the editor, obviously.
>I was thinking the Windows registry was being changed in order to allow
>an external patch version, such as the Super and Photon ones, to operate
>after the "update" installation.

NP. Just do what I suggested about putting the new PVENGINE and its DLL's into
its own dir, and put the old ones back into the bin dir. I tried that here and
it worked.

Post a reply to this message

povray.org admin team wrote:
> 
> 
> NP. Just do what I suggested about putting the new PVENGINE and its DLL's into
> its own dir, and put the old ones back into the bin dir. I tried that here and
> it worked.

Is it possible to update VC++ 6.0 version to grab dll's from current
directory, before looking into registry (same way as with watcom
version)? I can run superpatch and official version (watcom's one) , but
have problems with VC version (complaining about wrong editor). I guess
that it looks still from registry dll files path.

Post a reply to this message

Vahur Krouverk <vah### [at] fvaetecee> wrote:

>
>Is it possible to update VC++ 6.0 version to grab dll's from current
>directory, before looking into registry (same way as with watcom
>version)? I can run superpatch and official version (watcom's one) , but
>have problems with VC version (complaining about wrong editor). I guess
>that it looks still from registry dll files path.

It's too much trouble to do another full release just to fix this problem.
We'll probably be doing a 3.1f someday which will have it.

Post a reply to this message

>Please try downloading
>
>  http://www.povray.org/temp/pve31up.exe
>
>and install that. It's a new way of installing the update that I want
tested
>(other users please try it as well). It sets the 3.1e variable in the
registry
>(textureview wants this).
>
>In addition, however, the exe included (3.1e.watcom.win32.r1) will load
>cmedit.dll from the current directory if it is found there ; otherwise it
loads
>it from the path shown in the directory.

I just tried getting that file today. Got a 404 not found instead. Is it
available
somewhere else, or does the 3.1e on ftp.povray.org include that now?

Gail
*******************************************************************
* gsh### [at] monotixcoza              * ERROR: COFFEE.COM not found  *
* http://www.rucus.ru.ac.za/~gail/ * Insert cup and press any key *
*******************************************************************
   My Software never has bugs, It just develops random features
*******************************************************************

Post a reply to this message

>I just tried getting that file today. Got a 404 not found instead.
>Is it available somewhere else, or does the 3.1e on ftp.povray.org
>include that now?

Yes.

Post a reply to this message