I'm trying to install Dynamics V2 with cvs on a new note book, following the
documentation every thing worked ok until I got to "pbuild".
I set the DLC, POSSE and PATH variable, but when I run pbuild I get the
following output with a Progress error.
pbuild: BEGIN Building the Progress Applications...
PROGRESS=prowin32.exe + " -b -inp 18000 -yy 1950 -tok 1600 -D 150 -mmax
DIRLIST= adecomm adecomp adedesk adedict adeedit adeicon aderes aderesc
adetran adeuib adeweb adexml adm adm2 as4dict icf prodict prohelp protools
eb2 webutil wrappers
Convert HTML w/ Embedded 4gl to .w ...
>>Compile Procedures for gui<<
pbuild: Creating dictdb database ... Thu Aug 8 10:06:07 2002
PROGRESS database empty was not found. error: 293
I think it's Path problem but I can't figure it out.
prodb runs from the commeand line but has the same error when you choose the
Any help will be appreciated, thanks.
Labtech Systems Inc.
905 814 8836 x-201
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
If I'm not mistaken (and I may be) cygwin gets confused if you have spaces
in the path to your Progress installation. IOW, if you install Progress in
C:\Program Files\Progress, cygwin will not recognize the path.
Bruce S Gruenbaum, Principal Software Engineer
the Progress Company
From: Gustavo Brasil
Sent: Thursday, August 08, 2002 10:49 AM
Subject: Using Pbuild
I'm trying to install Dynamics V2 with cvs on a new note book,
Compile Procedures for gui<<
prodb runs from the commeand line but has the same error when you
I'm going to reinstall Progress and give it a try....
- Original Message -
From: "Bruce S Gruenbaum" To: ; Sent: Thursday, August 08, 2002 11:24 AM
Subject: RE: Using Pbuild
adetran adeuib adeweb adexml adm adm2 as4dict icf prodict prohelp
Also make sure you specify all paths using the UNIX-style forward slash (e.g.,
Bruce S Gruenbaum wrote:
Progress Software Corp.
The art of progress is to preserve order amid change, and
to preserve change amid order. -Alfred North Whitehead
I used to have a similar situation a time ago. In my case, I wasn't using
any spaces in the PATH (I used c:/Progress/91c), but any way...take a look
at this also:
Your DLC definition should be something like with:
#script to set up environment variables for Progress 9.1C
DLC="C:/" export DLC
PATH="$DLC:$DLC/bin:$PATH" export PATH
#end of script 91c
Note the "C:" instead of the "/cygdrive/c". The other scripts can keep those
Sent: Thursday, August 08, 2002 11:49 AM
You shouldn't have to reinstall progress...
Cygwin allows the use of DOS filename notation (for filenames over 8 chars
long) - I guess because it just passes this to the underlying OS - in this
case NT/w2k which does the DOS notation conversion.
So you can substitute this:
From: PSC - Bruce Gruenbaum
Sent: Friday, 9 August 2002 3:25 a.m.
To: email@example.com; firstname.lastname@example.org
I think we figure out the problem, The DLC, PATH and POSSE environment
variable has to be created on the windows environment, before starting
Go to Control Panel/System/Advanced/Environment Variable and create the
Start cygwin and run Pbuild, it should work ok.