Sign in to follow this  
Followers 0
supraspecies

Creation of DB file on error

6 posts in this topic

Here's the situation:

I have a program, I packed it and a DLL (runtime) it needs to run within a script. Script unpacks my program and DLL into TEMP, installs program, then finds program's installation directory via registry and copies the DLL there.

Problem: I execute the script, program's installation wizard comes up, I cancel the installation, and then a file named DB is created in my script directory. This DB file is the DLL I mentioned above. As I understand it, script fails to determine where to copy the DLL, and simply dumps it into it's own directory in DB form. How can I avoid that? I don't want any dumps.

Basically, all I want to do is disable the creation of this DB file. Or, if that is impossible, have this dump created in TEMP instead of script directory.

Share this post


Link to post
Share on other sites



Right, I solved the problem by simply making FileCopy execute only if the registry key is present, somehow it didn't come to my mind right away. Still, I would like to have more info about this DB file, why is it created in script directory, and how to disable the creation of this dump.

Share this post


Link to post
Share on other sites

Something wrong with FileInstall() ?


Common sense plays a role in the basics of understanding AutoIt... If you're lacking in that, do us all a favor, and step away from the computer.

Share this post


Link to post
Share on other sites

FileInstall puts file into TEMP, out of which im using FileCopy to copy it to program directory. FileCopy fails because it doesn't find the path in the registry. So yes, something is wrong. But I resolved the issue.

Right now I'm looking for more info, documentation on this dump-creation feature. Google didn't turn up anything. I'd like to know why is there a dump, under which circumstances it is created, why in script directory. Yes, copying failed, but why dumping the file in DB form in script directory?

Share this post


Link to post
Share on other sites

FileInstall puts file into TEMP, out of which im using FileCopy to copy it to program directory.

FileInstall puts files wherever you specify. If you need to put the file in a specific directory, just put that in as your desination parameter. There should be no need to FileInstall to TEMP and then copy to the directory (unless you haven't created said directory yet).


√-1 2^3 ∑ π, and it was delicious!

Share this post


Link to post
Share on other sites

I clearly realize all that, thank you. My question is unrelated: why does FileCopy generate a dump in script directory when it fails to find destination path? That's all I want to know. Call it curiosity. It's some undocumented feature, or something I haven't come across in the Help file.

I can understand the reason why would it create a dump, is it an intended behavior? Where can I read more about it? Upon which circumstances this dump gets created?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0