SB didn't use the latest file?

[NewsArchive]

I'm trying to determine what happened yesterday.

I have a Build.cmd that takes a batch number on the command line. It
writes it out to an INI file, an EQU file, then calls an exe that
writes it to a TPS file. Then it calls SB to build the install, and
the install includes the TPS file. Normally this works just fine.

However, yesterday the TPS was updated, and SB build the new install,
yet it has the previous builds TPS within it.

Is that even possible?

Mike Hanson
www.boxsoft.net

[NewsArchive]

Mike,

> I'm trying to determine what happened yesterday.
>
> I have a Build.cmd that takes a batch number on the command line.
> It writes it out to an INI file, an EQU file, then calls an exe
> that writes it to a TPS file. Then it calls SB to build the
> install, and the install includes the TPS file. Normally this
> works just fine.
>
> However, yesterday the TPS was updated, and SB build the new
> install, yet it has the previous builds TPS within it.
>
> Is that even possible?

No, this is not possible. SB does not use any "cache" when compiling files.
It's always a new fresh compile. It packages what is available at compile
time from the provided location. What does the compiler HTML report say?
It lists the CRC32 and date/time stamp of the packaged file(s).

Friedrich

[NewsArchive]

It doesn't make any sense to me either. I thinking that perhaps the
utility that runs creates the Version.sys is being run, then SB is
called before it's done and ready. That should happen only if you use
CALL in your CMD file, though, which I'm not doing.

I suppose I could delete VERSION.SYS before recreating it, then loop
until it exists before proceeding.

Mike Hanson
www.boxsoft.net