Funny, I just saw the same error two days ago. Its -at least in my case-
because I created the install on a 64 bit machine and the user was running
a 32 bit machine. So I had to re-install on a slow machine running the
ancient 2 gig limited 32bit OS that windows is to get a running install for
those guys. The psf for windows 64 bit worked for windows 7-64, 7-32 and
obviously xp-32.
So you gotta do what i'm doing right now and modify your installer to guess
what system you are currently running and then go grab that version to
install.... But I have not dug into it deep enough to see if there is a
simple set of files that can be switched between the 2 versions so I don't
have to keep two different sets.
Just kill 32bit now, now one needs it anymore. Go 64bit all the way or
Arm/atom for the little things in life.
regards,
Alfonso
On Tue, Nov 13, 2012 at 11:34 AM, Jeremy Handler <
jeremy.handler@hunterindustries.com> wrote:
> Our users are running a batch file to launch CREO2****
>
> ** **
>
> For ½ the users this works for the other half they receive the error
> below. Their paths are correct? ****
>
> The cmd C:\parametric doesn’t work like C:\proe1 did?****
>
> ** **
>
> copy "\\hqstor1\data\Shared\ProE Config\config.dtl" C:\prowork****
>
> copy "\\hqstor1\data\Shared\ProE Config\appearance.dmt" C:\prowork****
>
> copy "\\hqstor1\data\Shared\ProE Config\TABLE.PNT" C:\prowork****
>
> ** **
>
> copy "\\hqstor1\data\Shared\ProE Config\config.sup" "C:\PTC\Creo2\Creo
> 2.0\Common Files\M020\text"****
>
> copy "\\hqstor1\data\Shared\ProE Config\config.pro" "C:\PTC\Creo2\Creo
> 2.0\Common Files\M020\text"****
>
> copy "\\hqstor1\data\Shared\ProE Config\parametric.psf" "C:\ptc\Creo2\creo
> 2.0\parametric\bin"****
>
> start "C:\ptc\Creo2\creo 2.0\parametric\bin\parametric" "C:\ptc\Creo2\creo
> 2.0\parametric\bin\parametric.psf" %*****
>
> exit****
>
> ****
>
> ** **
>
> ** **
>
