comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » more on opening IDL files in WIN-NT
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: more on opening IDL files in WIN-NT [message #12227 is a reply to message #12135] Fri, 03 July 1998 00:00 Go to previous message
menakkis is currently offline  menakkis
Messages: 37
Registered: June 1998
Member
lbryan@arete-az.com (Lisa Bryan) wrote:
> Just wanted the group to know we figured out the problem I was having
> opening IDL files from Windows NT Explorer. When I double-click on a
> *.pro file in Windows Explorer a new session of IDL comes up, and I
> get an error message which says Windows NT can not find the file or a
> component and that I need to check the path name and make sure all
> required libraries are available. This was due to the fact that IDL
> is installed in the directory C:\Program Files\ RSI rather than C:\RSI
> We have reinstalled IDl in C:\RSI, and opening files works fine.
> Could anyone explain why this would be the case? Is this a bug? My
> System Administrator is unhappy that he can't put IDL in the Program
> Files directory so I told him I'd ask on the newsgroup about it. Any
> thoughts?

Yes, I'd guess that this is a bug in IDL - they may have some "old fashioned"
code somewhere that doesn't take kindly to spaces in directory names or
something.

I'll tell you how to hack things so that you will at least be able to get
some action from double-clicking .pro file icons. It's not ideal because
each file you open like this will incur a new IDL session. (Not to mention
that RSI'll shake its collective head on account of the crudeness of this
hack ;-)

It involves editing the registry. Start regedit.exe (in the WinNT subdir).
Go into the "HKEY_CLASSES_ROOT" tree. Find the key "IDLprogramFile" (quite a
long way down, past all the file-extension entries). Go into "shell" and
then "open", then click on the "command" key. Its default value should give
the path to your idlde.exe. Edit this value by double-clicking on
"(Default)" - append " %1" to it. (The value should now be something like:
"c:\Program Files\rsi\idlde.exe %1".) Finally, delete the "ddeexec" key
(below "command") altogether.

What this does is it replaces RSI's more sophisticated (but apparently buggy)
shell open method with a straightforward one.


Cheers

Peter Mason

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum
[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: Re: problem with corrupted pix-maps
Next Topic: Multiple Gifs

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Tue Dec 02 06:08:46 PST 2025

Total time taken to generate the page: 2.16429 seconds