Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
Hello again, 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? Lisa Bryan Arete Associates Tucson, AZ P.S. As soon as I get this figured out I have a very juicy question about curvefit. Arete Associates Tucson, Arizona
menakkis@my-dejanews.com wrote in message <6nhca5$g9d$1@nnrp1.dejanews.com>... > 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.... > > ... > 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. For file & directory names with spaces in them to be handled properly, each name needs to be surrounded by quotes. Many installation programs do not do this--this is probably the original cause of the problem. Peter's command should be "c:\Program Files\rsi\idlde.exe" "%1" where the quotes are part of the string to be entered into the registry value. [Well, I tried posting this but my server refused because there is more included text than new text. Yes, I knew that & it was deliberate. Anyway we'll soon fix thatAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAren't computers stupid!] -- Mark Hadfield, m.hadfield@niwa.cri.nz http://www.niwa.cri.nz/~hadfield/ National Institute for Water and Atmospheric Research PO Box 14-901, Wellington, New Zealand > > > 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
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