Winbuilder Version Differences

I downloaded the complete lx78sp6cxw.exe project and successfully ran it. But if I attempt to build it with Winbuilder 082, an error occurs and the build halts.

With the 082 WB the following error occurs:
Run - Processing section: [CopyToTarget] From file: [%BaseDir%\Projects\LiveXP\Basic\Build\3 - hivesFactory.Script]
> with parameters: [software],[0409XPSP2R#2]
X Retrieve - Failed to retrieve the file size from: [%BaseDir%\Workbench\LiveXP\Cache\Prebuild\software#2] - File does not exist:
> Halt

With the 078 WB, the script is successful:
Run - Processing section: [CopyToTarget] From file: [%BaseDir%\Projects\LiveXP\Basic\Build\3 - hivesFactory.Script]
> with parameters: [software],[0409XPSP2R%2]
>Retrieve - Successfully retrieved the file size from [%BaseDir%\Workbench\LiveXP\Cache\Prebuild\software0409XPSP2R%2] to variable: [%var%] with result [786432]

One line uses #2 and the other line %2. Not being a script programmer, please give me some insight on the difference between the two AND why one version of Winbuilder works and the other doesn't.

I downloaded the complete lx78sp6cxw.exe project and successfully ran it. But if I attempt to build it with Winbuilder 082, an error occurs and the build halts.

That is one of amalux's frozen builds, isn't it?

If yes, they are called "frozen builds" exactly because they include a given Winbuilder with which they should be run, the whole idea being that of having NO problems if there is an incompatibility with a newer or older version of Winbuilder.

You are seemingly using the thingy outside it's designed scope of application.


Wonko

You would have to go back further in the log for more information on how the script line in question occurred - which is why we always ask for a FULL, DEBUG log...

...The longer (but still short) answer is that there were changes after 78 was released in the way quotes were handled. There were also some other changes in the way variables were processed.

Full change log information is available in the docs on the wiki and in the chm...but just to echo the above...Projects that are tested and released as a UNIT were tested and work with the version of the tools it was released with. Stick to that version - OR be prepared to do some detective and debug work to correct ambiguities and account for other changes...

Thanks to Wonko and sbaeder for replying. Yes, this is amalux's frozen build, and I realized changes may mess it up. My main concern is to understand some of the workings of Winbuilder and understand why things go wrong. Sbaeder helped there in reference to the quote handling changes. Also I appreciate the change log wiki info that I wasn't aware of. I've wondered if anyone has ever written a general paper on how Winbuilder works and the required blocks to build a working project. The tutorials take one through the steps to get the parts and then "hopefully" get a working project, but the why's about details are a mystery to some of us lacking in scripting ability.

I am not aware of any "internals" doumentation - other than tribal knowledge and lot of reading through all the many years of posts here (scattered thru many sub-sections. This is a relatively "mature" (i.e. has been around a long time by internet standards) and has continued to evolve.

The issue (as I see it) is that there are two basic parts to your request. One is the internals of WinBuilder (the engine), and the other to making a working PE project. It's kind of like wanting to understand the C++ compiler and how a compiler works vs. how the program written in C++ to process a payroll (or any other application) works. With WinBuilder, they are often linked together, but are still two different things...
My best suggestion would be to ask when you don't understand the "why" on something and while even I myself haven't been hanging out here too long, someone will know...


Scott