Errors reading from file and debug seems out of sync with PC

[nikolai]

I'm trying to debug an install script and I'm getting a string of errors that report:

"Error

Error reading from the file c:\\DOCUME~1\\ALLUSE~1\\APPLIC~1\\OFFLINE\\A41D3282\\3A69AC2B\\(file to be installed). Verify that the file exists and that you can access it.

Abort, Retry, Fail."

This after the second time debugging the install, I believe. Perhaps it's looking for previous parts of the installation package that aren't there anymore?

I also notice that the debugger seems to be out of step with the cript's program counter. For example, it stepped right over a Run command without running the executable, and it's reporting the error above in an empty "If variable SUCCESS not Equals ERROR" statement.

Any help would be much appreciated!

EDIT: Note, the errors reported above occur while running or debugging.

Another addition, the debugger won't stop at break points that are unavoidable in terms of the script's control flow.

I'm also getting a "List out of bounds error" with a line number that's about twice as large as the number of lines in my script, if that helps. This error occurs at the completion of a debug.

[nikolai]

After working with this some more, I've noticed that the error messages I quoted up above don't always occur, or somtimes only occur for a subset of the files. And sometimes, the error seems to trigger when stepping through in debug mode, when it wouldn't if just running and not stepping.

[nikolai]

It's building now, I think it may have been issues with the debugger and/or repeated installs. Those error messages still appear in the debugger, but not in the build being used on other machines.