wont compile

[t0ddie]

FileInstall (@ScriptDir & "\test.exe",@SystemDir & "\test.exe")

this works when its just a script

why wont it compile? says invalid fileinstall() function

[Valik]

Read the FileInstall documentation closer.

[emmanuel]

  Larry said:

in particular the error is around the red portion

FileInstall (@ScriptDir & "\test.exe",@SystemDir & "\test.exe")

<{POST_SNAPBACK}>

reverse that larry... it's the source that can't be variable...

damn, I said it.

[emmanuel]

  Larry said:

in particular the error is around the red portion

FileInstall (@ScriptDir & "\test.exe",@SystemDir & "\test.exe")

<{POST_SNAPBACK}>

I looked in the helpfile, you got me that confused....

  Larry said:

notice the edit:... I should have left it alone... I had it right the first time... I'm tired... Unemployment is draggin' me.

<{POST_SNAPBACK}>

I'm tired too, employment's getting to me;) or at least starting at 4:30 and ending at 4-5 two days in a row followed by another 6:30 to 5... yeah... why am I awake again?

t0ddie, here's a hint, what you're looking for in the helpfile is in big bold letters.

Edited September 17, 2004 by emmanuel

[t0ddie]

i read it, but i thought it was the ENTIRE path... AND file that couldnt be a variable.....

i thought you could use a variable for part of it

my mistake, but it works before you compile it.. maybe fix that? it shouldnt work uncompiled if it doesnt work compiled.

or is there a reason for this that i am unaware of? or is it something that just isnt worth time to correct, because its not a huge deal?

either way, thanks for the help

~Todd

Edited September 17, 2004 by t0ddie

[ezzetabi]

Try...

FileInstall ("test.exe",@SystemDir & "\")

The destination must be a folder with trailing backslash.

The source can't be a variable, but it maybe a absolute path or a path relative to the @scriptdir, but in this second case you should not use any macro or variant, just don't begin the path with a slash or a drive letter...

'\test.exe' is not from @scriptdir, 'test.exe' is.

In your case your script works before compiling just because the file is already in the script dir. If you move the script in an other folder it wont work anymore.

[Valik]

No... it works before compiling because running non-compiled uses FileCopy() to simulate FileInstall() so the script can be tested. Also, since it's being run through a live script, it's able to resolve any variables/macros. When the compiler encounters that, however, it doesn't have any of the parsing/lexing capabilities and knows nothing of macros, so it can't find the file/directory.

Also, the destination can either be a directory or a filename. If it's a directory, it does have to have a trailing slash, otherwise, an attempt to create a file with no extension occurs.