Skip to main content
A
A.DelNegro1-Visitor
1-Visitor
August 16, 2010
Question

WF3, Borrowing licenses & Windows 7

  • August 16, 2010
  • 9 replies
  • 1648 views
Anyone had any issues with borrowing licenses while on Windows 7? I
just installed Win7 (64bit) and was trying to borrow a license over the
weekend and I got a weird error message.

It appears that the batch file for borrowing creates a temporary batch
file called "ptc_setvars.bat". I get an error that this file cannot be
found when I run "proe_borrow.bat". Not sure if the syntax is different
in Win7 or what.

Anyone had this issue?

Thanx in advance.
Tony
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

9 replies

D
dgschaefer21-Topaz II
21-Topaz II
August 16, 2010

I get that error message in XP when I don't have write access to the
Pro/E bin folder where proe_borrow.bat resides.  Without write access,
the ptc_setcars.bat cannot be created, and therefore won't be there when
called on.

Doug Schaefer
A
A.DelNegro1-VisitorAuthor
1-Visitor
August 16, 2010
I have been getting that message as well. I'm sure that's the cause.

Thanx Doug.

Tony
B
Bari14-Alexandrite
14-Alexandrite
August 17, 2010
Did you run the proe_borrow.bat file as administrator?
A
A.DelNegro1-VisitorAuthor
1-Visitor
August 22, 2010
Still having issues borrowing a license.

At this point I'm having issues changing the read-only status of the pro/bin folder. I tried the properties dialog in windows explored and even tried the dos based attrib command and for some reason the folder is still read-only. Not sure why Win7 insists on this being read only anyway, I guess new security.

Anyone know how to get this setting changed?

Thanx
Tony

J
JonTribe1-Visitor
1-Visitor
August 23, 2010

Hi Chaps

Has anyone found a solution to this borrowing issue yet??

We have this problem on all our Windows 7, 64 bit machines.

I just tried to run the proe_borrow.bat as administrator and it's returning 2 error messages one in a DOS window reads

"x86e_win64_ptc_setvars' is not recognized as an internal or external command, operable program or batch file.

'ptc_setvars.bat' is not recognized as an internal or external command, operable program or batch file.

Could not find C:\PTC\WF3_M240\bin\ptc_setvars.bat"

The other in a windows error message reads Windows can not find '\bin\proe.exe'.

Any ideas / advice would be gratefully received.

TIA

DomenicLaritz
DomenicLaritz17-Peridot
17-Peridot
August 23, 2010
Try this:

Start a command shell as administrator.
Change the working directory to the folder, where the file proe_borrow.bat is.
Type in proe_borrow.bat and press the enter key - now it should work.

Regards, Domenic
D
dgschaefer21-Topaz II
21-Topaz II
August 23, 2010
I'm not familiar at all with Win7, but can you create a shortcut to
proe_borrow.bat and set the 'start in' directory to a folder where you
have write permissions, say your desktop? In theory, that would allow
the ptc_setvars.bat to be written (to the desktop), but it's possible
that proe_borrow.bat then wouldn't be able to find it.

Doug Schaefer
J
JonTribe1-Visitor
1-Visitor
August 23, 2010

I finally sorted it!

I generated a variable 'PRO_MACHINE_TYPE' and set it to X86E_WIN64

Then re-installed Pro-E and everything seemed to run fine, not sure if it was the variable or re-install that fixed it....

J
JonathanHodgson13-Aquamarine
13-Aquamarine
August 23, 2010
I suspect it was the variable.

PTC batch files use these variables pretty heavily, and will likely not
work if a key one is missing. I had to heavily hack (and simplify!) our
copy of purge.bat to get around this...


Does a Pro/E "install" actually do anything beyond copying files and
creating a shortcut? We've run from network installs in the past, and
I'm fairly sure that no changes have been made to our machines when
adding a new version - simply update the launcher script to point to the
latest location.

Regards,
Jonathan

Terms & ConditionsAccessibility statement