 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
POV-Ray 3.1e runns well and fast, but the patches based on 3.1(a) don't like
the new codemax dll's. There is an error" wrong dll version". I tried put
the patches together with the old dll's in a different directory, but this
is does not work.
Is there a way to get the patches to work with the old dll's and 3.1e work
with the new one's under winNT4? I can do without, but the editor makes life
a little easier.
ingo
--
Met dank aan de muze met het glazen oog.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"ingo" <ing### [at] ingo demonnl> wrote:
>POV-Ray 3.1e runns well and fast, but the patches based on 3.1(a) don't like
>the new codemax dll's. There is an error" wrong dll version". I tried put
>the patches together with the old dll's in a different directory, but this
>is does not work.
The error you get is not related to the codemax dll - it is in fact cmedit.dll
that is giving you the error message.
>Is there a way to get the patches to work with the old dll's and 3.1e work
>with the new one's under winNT4? I can do without, but the editor makes life
>a little easier.
cmedit.dll is located using the path given in the registry for POVWIN. there's
nothing that you can do (short of either swapping the files in the bin dir back
and forth, or editing the registry) to change which one it loads.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team heeft geschreven in bericht
<36ffebc7.5772406@news.povray.org>...
<snip>
>>Is there a way to get the patches to work with the old dll's and 3.1e work
>>with the new one's under winNT4? I can do without, but the editor makes
life
>>a little easier.
>
>cmedit.dll is located using the path given in the registry for POVWIN.
there's
>nothing that you can do (short of either swapping the files in the bin dir
back
>and forth, or editing the registry) to change which one it loads.
Ok, I see. Was afraid this would be the answer,
Thanks,
ingo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 27 Mar 1999 14:37:33 GMT, new### [at] DESPAMpovrayorg
(povray.org admin team) wrote:
>"ingo" <ing### [at] ingodemonnl> wrote:
>
>>POV-Ray 3.1e runns well and fast, but the patches based on 3.1(a) don't like
>>the new codemax dll's. There is an error" wrong dll version". I tried put
>>the patches together with the old dll's in a different directory, but this
>>is does not work.
>
>The error you get is not related to the codemax dll - it is in fact cmedit.dll
>that is giving you the error message.
>
>>Is there a way to get the patches to work with the old dll's and 3.1e work
>>with the new one's under winNT4? I can do without, but the editor makes life
>>a little easier.
>
>cmedit.dll is located using the path given in the registry for POVWIN. there's
>nothing that you can do (short of either swapping the files in the bin dir back
>and forth, or editing the registry) to change which one it loads.
So... could one set up a batch file which "merged" the right registry
line in before running POV?
I've not tried this with WindowsNT but certainly you can export just a
single line from the registry editor in Win95, and it should be simple
enough to set-up a a couple of batch files - one which re-instates the
old .dll (at some new location, presumably) and then load POV and a
second which changes the registry back to pointing to the new DLL in
it's default location before loading POV.
a couple of shortcuts on the desktop (one for the registry patch and
POV, one for the other registry patch and SuperPatch POV).
I'm about to look at Superpatch (and have been for some weeks) so it'd
be quite nice if POv3.1e and SuperPatch could co-exist :)
Cheers,
Cliff Bowman
Why not pay my 3D Dr Who site a visit at
http://www.geocities.com/Area51/Dimension/7855/
PS change ".duffnet" to ".net" if replying via e-mail
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I just posted this question about the patches not working in conjunction
with the new 3.1e. I was hopeful there was an answer here that didn't
mean changing the registry or cmedit.dll back and forth.
Oh well, at least I found the registry entry in need of modification so
I could save new pov scripts into the scenes folder instead of
C:\WINDOWS.
At least I'm hoping so, I will need to restart Windows first to be sure
of that.
I tried the exchange of the two different cmedit.dlls using a batch
file, goes okay. Better that than registry changes.
Cliff Bowman wrote:
>
> On Sat, 27 Mar 1999 14:37:33 GMT, new### [at] DESPAMpovrayorg
> (povray.org admin team) wrote:
>
> >"ingo" <ing### [at] ingodemonnl> wrote:
> >
> >>POV-Ray 3.1e runns well and fast, but the patches based on 3.1(a) don't like
> >>the new codemax dll's. There is an error" wrong dll version". I tried put
> >>the patches together with the old dll's in a different directory, but this
> >>is does not work.
> >
> >The error you get is not related to the codemax dll - it is in fact cmedit.dll
> >that is giving you the error message.
> >
> >>Is there a way to get the patches to work with the old dll's and 3.1e work
> >>with the new one's under winNT4? I can do without, but the editor makes life
> >>a little easier.
> >
> >cmedit.dll is located using the path given in the registry for POVWIN. there's
> >nothing that you can do (short of either swapping the files in the bin dir back
> >and forth, or editing the registry) to change which one it loads.
>
> So... could one set up a batch file which "merged" the right registry
> line in before running POV?
>
> I've not tried this with WindowsNT but certainly you can export just a
> single line from the registry editor in Win95, and it should be simple
> enough to set-up a a couple of batch files - one which re-instates the
> old .dll (at some new location, presumably) and then load POV and a
> second which changes the registry back to pointing to the new DLL in
> it's default location before loading POV.
>
> a couple of shortcuts on the desktop (one for the registry patch and
> POV, one for the other registry patch and SuperPatch POV).
>
> I'm about to look at Superpatch (and have been for some weeks) so it'd
> be quite nice if POv3.1e and SuperPatch could co-exist :)
>
> Cheers,
>
> Cliff Bowman
> Why not pay my 3D Dr Who site a visit at
http://www.geocities.com/Area51/Dimension/7855/
> PS change ".duffnet" to ".net" if replying via e-mail
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/homepage.htm
mailto:inv### [at] aolcom?Subject=PoV-News
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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.
Put all the patch files into their respective folders, NOTE: uvpov.exe
will need the cmax101.dll dated 9/9/98 [170K] in its folder as well (I
don't know about povray.exe SuperPatch or others), then copy and rename
the original 3.1e cmedit.dll to cmedit.dlo and the older cmedit.dll to
cmedit.dlp (make another copy cmedit.dls for SuperPatch though it is the
same just to be orderly). Here's the batch files written out using
Notepad that I'm using to switch between these:
Put this one into bin folder, saved as 31e.bat (or whatever).
@echo off
:. Version 3.1e batch
cd c:\progra~1\pov-ra~1.1\bin
copy /y cmedit.dll cmedit.dlx
del cmedit.dll
copy cmedit.dlo cmedit.dll
pvengine.exe
exit
Put this next one into bin\Super sub-folder, name it Super.bat(?)
@echo off
:. Super Patch batch
cd c:\progra~1\pov-ra~1.1\bin
copy /y cmedit.dll cmedit.dlx
del cmedit.dll
copy cmedit.dls cmedit.dll
povray.exe
exit
And put this one into the bin\Photon sub-folder, naming it photon.bat(?)
@echo off
:. Photon Map batch
cd c:\progra~1\pov-ra~1.1\bin
copy /y cmedit.dll cmedit.dlx
del cmedit.dll
copy cmedit.dlp cmedit.dll
uvpov.exe
exit
Make shortcuts to the Desktop for these and right-click on their icons,
go into Properties/Program tab and check the "Close on Exit" box.
This will keep separate copies of the dll and allow the switching to be
possible but you will have to use these new shortcuts only since the dll
may not be the right one next time you try a different POV-Ray. Also,
you can not have two different ones open at the same time or a sharing
violation occurs. I would have made the cmedit.dll return to the
original each time but I couldn't get it to work, the batch seems to
complete and then the POV-Ray program errors due to a wrong DLL when run
all at once.
Hope this helps the few who want to do such a thing as this. If you know
how to do this better than me, great, however I've got a working system
going for now so I won't need to change.
Directory/file structure for the inept ;-)
C:\Progra~1\POV-Ra~1\bin
pvengine.exe
cmax101.dll...180K...3/7/99
cmedit.dlo ...683K...3/20/99
cmedit.dlp ...680K...2/15/99
cmedit.dls ...680K...2/15/99
\Photon
uvpov.exe
cmax101.dll ...170K...9/9/98
\Super
cmax101.dll ...170K...9/9/98
others *.dll ...?K ...10/28/98(?)
ingo wrote:
>
> POV-Ray 3.1e runns well and fast, but the patches based on 3.1(a) don't like
> the new codemax dll's. There is an error" wrong dll version". I tried put
> the patches together with the old dll's in a different directory, but this
> is does not work.
> Is there a way to get the patches to work with the old dll's and 3.1e work
> with the new one's under winNT4? I can do without, but the editor makes life
> a little easier.
>
> ingo
>
> --
> 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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 28 Mar 1999 19:16:57 -0600, Bob Hughes <inv### [at] aolcom> wrote:
>I just posted this question about the patches not working in conjunction
>with the new 3.1e. I was hopeful there was an answer here that didn't
>mean changing the registry or cmedit.dll back and forth.
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.
It doesn't seem like this would be a long-term problem, at least not
with the superpatch and UVPOV, because I would wager that as soon as
the new source is made available, new binaries of those two patches
will also be made available.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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.
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.
Works great, thanks,
ingo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
