Hi,
after installation of VX for the first test over a new installed 1.82 I
imported a small project. So after some problems because beeing not used
with this new VX-feeling all was running OK.
Now I had to do some urgend changes and I decided to do them in the old and
long time used way using my good old DOS-Fileeditor to change the Source und
using the pbuild command to compile and link. This I did on another PC on
which my usually used Xbase++-installation (1.82). Though I now used the new
XPJ-file with all the changes and new settings coming from VX there was no
problem to pbuild the whole project with the old 1.82 version. So there is a
good compatibility downstairs. But I was very surprised that the same
handling on the other PC, where VX is installed, was not possible. Using the
command PBUILD myProject /A gave me the following error message:

arc -v LB.ARC
Name               Length    Stowage    SF   Size now  Date       Time
CRC
=================  ========  ========  ====  ========  =========  ======
====
             ====  ========            ====  ========
     Total      0         0              0%         2

There were no file entries selected.


Processing time:      0.09 secs.

Please be aware: VX within the IDE compiles and runs and debugs the project
with no problem. The old XBase++ without VX over it pbuilds and runs and
debugs the prject without problems. The VX at commandline pbuilds with the
above problem. Unfortunately I am unable to see what this error is. The
.ARC-file is as following:

#Include "LB.CH"

BITMAP

5001 = "basket32.bmp"
5101 = "basket16.bmp"
5002 = "drucker32.bmp"
5102 = "drucker16.bmp"
5003 = "Finanzen32.bmp"
5103 = "Finanzen16.bmp"
5004 = "Werkzeug32.bmp"
5104 = "Werkzeug16.bmp"
5005 = "windows32.bmp"
5105 = "windows16.bmp"

The includefile LB.CH is as following:

#define BMP_BASKET32      5001
#define BMP_BASKET16      5101
#define BMP_DRUCKER32     5002
#define BMP_DRUCKER16     5102
#define BMP_FINANZEN32    5003
#define BMP_FINANZEN16    5103
#define BMP_WERKZEUG32    5004
#define BMP_WERKZEUG16    5104
#define BMP_WINDOWS32     5005
#define BMP_WINDOWS16     5105

Any Idea whats wrong? Or is it forbidden to use this version from
commandline?
Klemens

"Klemens Lichter" <csl@lichter.de> wrote in Message
news:G$s6iqNzDHA.1972@S15147418...

(...)
> Now I had to do some urgend changes and I decided to do them in the old
and
> long time used way using my good old DOS-Fileeditor to change the Source
und
> using the pbuild command to compile and link. This I did on another PC on
> which my usually used Xbase++-installation (1.82). Though I now used the
new
> XPJ-file with all the changes and new settings coming from VX there was no
> problem to pbuild the whole project with the old 1.82 version. So there is
a
> good compatibility downstairs. But I was very surprised that the same
> handling on the other PC, where VX is installed, was not possible. Using
the
> command PBUILD myProject /A gave me the following error message:
>
> arc -v LB.ARC
> Name               Length    Stowage    SF   Size now  Date       Time
> CRC
> =================  ========  ========  ====  ========  =========  ======
> ====
>              ====  ========            ====  ========
>      Total      0         0              0%         2
>
> There were no file entries selected.
>
> Processing time:      0.09 secs.
>
> Please be aware: VX within the IDE compiles and runs and debugs the
project
> with no problem. The old XBase++ without VX over it pbuilds and runs and
> debugs the prject without problems. The VX at commandline pbuilds with the
> above problem. Unfortunately I am unable to see what this error is. The
> .ARC-file is as following:

(...)

> Any Idea whats wrong? Or is it forbidden to use this version from
> commandline?

Klemens,

both PBUILD and ARC can still be used as commandline tools. My
(off-hand) guess is that it wasn't the resource compiler that produced
this message. Could it be that something else named ARC is located
within the (commandline) path on that particular machine? Something
like "ARChive" perhaps? What happens if you call ARC manually using
the parameters specified above? Or with the /? parameter? Normally,
ARC should reveal its true identity via a prompt such as "Alaska Resource
Compiler".

Some shells come with utilities that allow you to locate a certain file
within the current PATH setting. If you have one of these, have it locate
the executable that might get called by PBUILD. Is this the correct one?

HTH,
  Till
  [Alaska Research & Development]

Hi Till,
thank you, thats it! Because I never used ARC compression utility I did not
realise that a very old version of it was in some directory only on that PC
and this directory was in the path. After deleting it all is OK.
Klemens

"Till Warweg" <till.warweg@alaska-research.com> schrieb im Newsbeitrag
news:Hgo8wbTzDHA.1976@S15147418...
> "Klemens Lichter" <csl@lichter.de> wrote in Message
> news:G$s6iqNzDHA.1972@S15147418...
>
> (...)
> > Now I had to do some urgend changes and I decided to do them in the old
> and
> > long time used way using my good old DOS-Fileeditor to change the Source
> und
> > using the pbuild command to compile and link. This I did on another PC
on
> > which my usually used Xbase++-installation (1.82). Though I now used the
> new
> > XPJ-file with all the changes and new settings coming from VX there was
no
> > problem to pbuild the whole project with the old 1.82 version. So there
is
> a
> > good compatibility downstairs. But I was very surprised that the same
> > handling on the other PC, where VX is installed, was not possible. Using
> the
> > command PBUILD myProject /A gave me the following error message:
> >
> > arc -v LB.ARC
> > Name               Length    Stowage    SF   Size now  Date       Time
> > CRC
> > =================  ========  ========  ====  ========  =========  ======
> > ====
> >              ====  ========            ====  ========
> >      Total      0         0              0%         2
> >
> > There were no file entries selected.
> >
> > Processing time:      0.09 secs.
> >
> > Please be aware: VX within the IDE compiles and runs and debugs the
> project
> > with no problem. The old XBase++ without VX over it pbuilds and runs and
> > debugs the prject without problems. The VX at commandline pbuilds with
the
> > above problem. Unfortunately I am unable to see what this error is. The
> > .ARC-file is as following:
>
> (...)
>
> > Any Idea whats wrong? Or is it forbidden to use this version from
> > commandline?
>
> Klemens,
>
> both PBUILD and ARC can still be used as commandline tools. My
> (off-hand) guess is that it wasn't the resource compiler that produced
> this message. Could it be that something else named ARC is located
> within the (commandline) path on that particular machine? Something
> like "ARChive" perhaps? What happens if you call ARC manually using
> the parameters specified above? Or with the /? parameter? Normally,
> ARC should reveal its true identity via a prompt such as "Alaska Resource
> Compiler".
>
> Some shells come with utilities that allow you to locate a certain file
> within the current PATH setting. If you have one of these, have it locate
> the executable that might get called by PBUILD. Is this the correct one?
>
> HTH,
>   Till
>   [Alaska Research & Development]
>
>
>