Re: Upgrade to IDL 6.3 breaks IDLtoAVI [message #48547] |
Tue, 02 May 2006 06:30  |
Chris[2]
Messages: 39 Registered: August 2003
|
Member |
|
|
Hi Mark,
In IDL6.3, the "idl32.dll" was renamed to "idl.dll" so that both the 32-bit
and the 64-bit Windows would have the same DLL name (same thing for
"idl.lib"). This makes it simpler for someone to have a makefile that they
can use to compile their own DLL on both 32-bit and 64-bit Windows, and not
have to change the IDL library name. This change is documented in the IDL6.3
release notes.
In any case, the entry points have changed enough between IDL6.2 and IDL6.3
that a previously-compiled dll will not work, even if the library names
hadn't been changed. So really, someone needs to recompile the avi.dll and
link it against IDL6.3.
-Chris
<badjelly.witch@gmail.com> wrote in message
news:1146515445.899454.35570@v46g2000cwv.googlegroups.com...
> I knew it was going to happen eventually... I have just upgraded to IDL
> 6.3 (Windows 32-bit) and the IDLtoAVI DLM no longer works.
>
> I did the same thing I have done for several version upgrades now. I
> copied IDLtoAVI.dll and IDLtoAVI.dlm from IDL62\bin\bin.x86 to
> IDL63\bin\bin.x86, started the new version and tried to run the DLM. I
> got a message about IDL32.dll not being found on the path. I noted that
> there is a copy of IDL32.dll in IDL62\bin\bin.x86 but not in
> IDL62\bin\bin.x86, so I copied that over too, restarted and tried
> again. I didn't seriously expect that this would work, and it didn't:
> IDL gave and error message about a bad entry point and crashed. I
> presume this is related to the introduction of 64-bit Windows.
>
|
|
|
|
|
|
|
|
|
|
Re: Upgrade to IDL 6.3 breaks IDLtoAVI [message #48639 is a reply to message #48551] |
Tue, 02 May 2006 14:59  |
Mark Hadfield
Messages: 783 Registered: May 1995
|
Senior Member |
|
|
Haje Korth wrote:
> This is exactly the reason why I never adopted the new DLM version. Little
> changes in the API and DLMs simply won't work anymore. I had to recompile
> all my DLMs for use with IDL 6.3 beta back then. I hope Oleg will provide an
> updated version. If not, someone (if it has to be me I will) can supply a
> recompiled version of the old source. However, this is just a temporary
> solution. In the long run, RSI really needs to support AVIs in IDL. I have
> been trying to push for that but if you want this to happen, they will need
> your input as well!
Hear hear!
--
Mark Hadfield "Kei puwaha te tai nei, Hoea tahi tatou"
m.hadfield@niwa.co.nz
National Institute for Water and Atmospheric Research (NIWA)
|
|
|
Re: Upgrade to IDL 6.3 breaks IDLtoAVI [message #48641 is a reply to message #48548] |
Tue, 02 May 2006 14:46  |
badjelly.witch
Messages: 27 Registered: May 2006
|
Junior Member |
|
|
Thanks Ronn
I tried out the new 6.3 version. It is not writing AVIs properly. As
you know, your test program aviKRtest.pro calls avi_openw with the
OPTION keyword set, so that it shows a "Video Compression" dialog for
setting the AVI format etc. If I accept the default (Full Frames
Uncompressed) then an AVI file is produced, but it is not readable,
either by the IDL code later in the routine or by an external
application. If I change the AVI format to Microsoft Video 1 (an oldie
but a goodie) then I get an error: "AVI_OPENW: Unable to avi stream
format".
BTW: at your leisure, perhaps you could clarify the relationship
between your DLM and Oleg's DLL and your plans for the DLM. Is there
any chance of merging some of Oleg's 2005 improvements into your
version? Also, do you intend to keep upgrading your DLM for new
versions of IDL. (I presume you do, as you have just done it for 6.3!).
And does/could your DLM work with 64-bit Windows? As I have said, I
find your DLM extremely useful and am keen to see it continue. I would
be willing to pay money to ensure this happens.
BTW 2: receiving new IDL versions Here in NZ *before* everyone else is
a new experience. IN the good old days we were weeks behind. They must
be feeding the carrier pigeons extra rations!
Mark
|
|
|