Run-time error, looking for \".dfm\"
Run-time error, looking for \".dfm\"
I don't know what caused this, but while my program continues to compile OK, I have suddenly started getting a run-time error even before my setup program shows its first dialog. The dialog that says "InstallAware is preparing the InstallAware Wizard" is still showing, when suddenly its progress bar stops and an error dialog is displayed with the caption "InstallAware Wizard" and the text "Runtime error in install: Cannot open file C:\\[temp folder path]\\mia1\\.dfm". Do you know what could be causing this? Exiting/restarting and rebuilding my project don't help.
-
- Posts: 904
- Joined: Thu Dec 22, 2005 7:03 pm
- Contact:
It would appear you removed a reference to a .dfm file in the Project Manager for your project. Add the file back under the Dialogs node.
Candice Jones
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
The error message turns out to be a red herring. It has nothing to do with a DFM file. Here's the problem: my installer needs to fetch a value out of the registry, and the key name is "$InstallRoot$". Yes, it has dollar signs as part of the name. I was concerned that simply setting a string to "$IntallRoot$" would be interpreted as trying to dereference a variable. So what I tried was this:
This code causes the installer to blow up when it's unpacking the files prior to showing any dialogs, with the "missing .dfm" message I referred to in the original message in this thread.
Turns out I don't need this approach at all, since the scripting engine is smart enough to treat the dollar signs as literals if they surround text that isn't an actual declared variable name. But I thought you should know, since the error message was so extremely misleading.
Code: Select all
Set Variable DOLLAR to $
Set Variable REGKEYNAME to $DOLLAR$InstallRoot$DOLLAR$
This code causes the installer to blow up when it's unpacking the files prior to showing any dialogs, with the "missing .dfm" message I referred to in the original message in this thread.
Turns out I don't need this approach at all, since the scripting engine is smart enough to treat the dollar signs as literals if they surround text that isn't an actual declared variable name. But I thought you should know, since the error message was so extremely misleading.
Who is online
Users browsing this forum: No registered users and 18 guests