×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Fixed working directory

Fixed working directory

Fixed working directory

(OP)
I've searched, but none with this same problem.


The startup directory is never the one I'd set in the previous session.

"Start in" is set to "D:\Documents\", but PROE ignores it and goes to "C:\Windows\System32\"

'file_open_default_folder' IS 'working_directory'

????

RE: Fixed working directory

If you are using a shortcut (link) from your desktop or other convenient location to start Pro/E then right click on the shortcut, click on "properties" and set the Start in directory there.

----------------------------------------

The Help for this program was created in Windows Help format, which depends on a feature that isn't included in this version of Windows.

RE: Fixed working directory

(OP)
The desktop shortcut "Start in" is already set to where I want. PROE ignores it.

RE: Fixed working directory

In our case the "start in" dir is a temporary directory that is cleaned upon login. Proe generates some temporary files that you usually do not need in your working directory. I am not much in system admin but I think you should set your home directory from your account settings. The start in directory and the home directory can be two different dirs.Be aware where you put your config files. This depends on whether you are the only user on the system.

RE: Fixed working directory

Double check that the shortcut start in dir is valid, The only reason I know of for Pro/E to ignore it is an invalid setting.

----------------------------------------

The Help for this program was created in Windows Help format, which depends on a feature that isn't included in this version of Windows.

RE: Fixed working directory

(OP)
I'm the only user on the computer.
Standalone license and everything.


Where do I set the "home" directory ?


I've changed the start-in dir on proe's shortcut to C:\projects\

I gave that folder complete control to everyone. Sure proe can access it.

But no.
The thing insist on C:\windows\system32\

RE: Fixed working directory

Home is an environment variable in windoze. You set it through the control panel. See snapshot attached.

----------------------------------------

The Help for this program was created in Windows Help format, which depends on a feature that isn't included in this version of Windows.

RE: Fixed working directory

This may be a stupid question, but have you checked that C:\Windows\System32\ is the working directory?

I say this because on my computer, when I open Creo, the first directory opened is My Documents, but when I click on the working directory it goes to where I set it to open from.

RE: Fixed working directory

Ahh!!! You may need to set this config option:

file_open_default_folder working_directory

----------------------------------------

The Help for this program was created in Windows Help format, which depends on a feature that isn't included in this version of Windows.

RE: Fixed working directory

(OP)
'file_open_default_folder' IS 'working_directory' on 'Tool' > 'options'
Double checked that.


I'm starting to think that I am missing the concept of working directory...

Let me explain what I do, then you tell me if I'm doing anything wrong:

1 - I open ProE.

2 - Without any Part or Assembly or Manufacturing or any kind of work open, I click on File, then 'Set Working directory'
It starts on C:\Windows\System32

3 - On that window, I navigate to C:\Projects, and click OK.
Period.

4 - Then I close ProE (Prompt : Yes - as I have no opened work).

5 - Finally, I reopen ProE, and click 'File' > 'Set working directory' to verify if the thing is C:\Projects, as it should be.
But NO, the son of a ! is back to System32.


Where is the error ?

RE: Fixed working directory

(OP)
robertib, 'file_open_default_folder' IS 'my documents' on your case, probably.

And your Creo is obeying the law, as it should be.

I wish it did like yours on mine...

RE: Fixed working directory

Is your shortcut launching the proe.exe file or to a batch file that eventually calls proe.exe?

David

RE: Fixed working directory

Lucas,

Set Working Directory like you do ONLY applies to your current session of Wildfire. That is why closing Wildfire and restarting it is still pointing to the C:\Windows\System32.
The icon that you use to launch Wildfire from on your desktop should have c:\projects in the "Start In:" field when you do a right clcik and Properties on it.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

RE: Fixed working directory

A suggestion may be to make sure your "start In" location in the shortcut properties is the location of your config.pro file. Otherwise you will be loading the default or at least that is how it is with our setups. Other than that is sounds like a permissions issue with windows and ProE. Starting in C:\Windows\System32 is what seems the most odd to me. Before I had mine configured the way I like it would start in the ProE installation directory in some kind of \text directory.

Good luck,

- J -

RE: Fixed working directory

(OP)
'Config.pro' is at "C:\Program Files\proeWildfire 5.0\text", Not "C:\Projects"

Is that the issue here ?
"text" folder, mr jvian... Interesting, not ?

The desktop shortcut points to an executable: proe.exe



Config.pro:

chamfer_45deg_dim_text iso/din
drawing_setup_file
$PRO_DIRECTORY\text\iso.dtl
format_setup_file
$PRO_DIRECTORY\text\iso.dtl
pro_unit_length unit_mm
pro_unit_mass unit_kilogram
template_designasm
$PRO_DIRECTORY\templates\mmks_asm_design.asm
template_drawing
$PRO_DIRECTORY\templates\a3_drawing.drw
template_sheetmetalpart
$PRO_DIRECTORY\templates\mmns_part_sheetmetal.prt
template_solidpart
$PRO_DIRECTORY\templates\mmns_part_solid.prt
todays_date_note_format %dd-%Mmm-%yy
tolerance_standard iso
tol_mode nominal
weld_ui_standard iso

file_open_default_folder working_directory
override_store_back no


Above all, my friends: so far I have not thanked you. I do so now. Thank you all !

RE: Fixed working directory

Pro/E automatically loads 4 config files on startup (if they exist) in this order:

1)<load_point>\text\config.sup
2)<load_point>\text\config.pro
3)startup_dir\config.pro
3)$HOME\config.pro

<load_point> is where Pro/E is installed, in your case it appears to be C:\Program Files\proeWildfire 5.0\.

$HOME is whatever you have set your Windoze environment variable HOME to. In Windoze 7 it is usually C:\Users\user_name.

Settings in files loaded later will override pervious settings except those in config.sup which can not be overridden.

So you config.pro in the text dir is exactly where one file should be and it has nothing unusual. If you don't have any of the other config files, that's OK, Pro/E will just skip them and carry on.

----------------------------------------

The Help for this program was created in Windows Help format, which depends on a feature that isn't included in this version of Windows.

RE: Fixed working directory

(OP)
Where is this startup_dir ? Is it a folder ? where ?
If it's supposed to be an environment variable, it is absent.

Config.sup doesn't exist, and a copy of th config.pro I've pasted on the Home dir (in this case, the C:\projects - exactly as is on proe's shortcut, and on the environment variables)

If there's nothing on startup_dir, what next ?


Goddam, I'm formatting this thing...

RE: Fixed working directory

dgallup meant the Start in: directory as defined in your desktop icon that you use to launch Pro/E from.
When I select Working Directory after opening Pro/E it displays the contents of the folder I have specified in the Start in: box of the icon properties.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

RE: Fixed working directory

Try taking a look at the batch file that is the target of your desktop Pro/E launch icon. It should be something like <loadpoint>\bin\proe1.bat. See if it is doing something non-standard like changing the directory or running some command other than proe.exe.

If all else fails, just delete the the icon you are using and make a new shortcut to the batch file. Set the startin dir and see if it works.

----------------------------------------

The Help for this program was created in Windows Help format, which depends on a feature that isn't included in this version of Windows.

RE: Fixed working directory

You can also set the target to proe.exe and see what happens. This is how I have my system set. It will still read the proe.psf file for your license and such, but not have any changes imposed by a proe.bat.

Post your proe.bat, if you want, so we can look at it if you don't understand what it is doing.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

RE: Fixed working directory

(OP)
Creating a shortcut to 'proe.exe' and adding "C:\Projects" to the "Start in" makes no change. "Set Working Directory" window will still start on "C:\Windows\system32"

Creating a shortcut to 'proe.bat' and adding "C:\Projects" to the "Start in" makes no change. "Set Working Directory" window will still start on "C:\Windows\system32"

(Actually, it's "C:/projetos," as I did it in my language. But every field that requires paths are absolute and coherent. I am sure the problem is not here.)

Proe1.bat:

CODE

@echo off
"C:\Program Files\proeWildfire 5.0\bin\proe.exe" "C:\Program Files\proeWildfire 5.0\bin\proe1.psf" %* 

proe1.psf:

CODE -->

// PTC - PSF file: proe 
//
PRODUCT=Pro/ENGINEER
DESC=Pro/ENGINEER (default)
ENV=INTRALINK_DIR=__INTRALINK_DIR__
ENV=ILINK_CMD_NAME=__ILINK_CMD_NAME__
ENV=INTRALINK_CMD=%INTRALINK_DIR%\bin\%ILINK_CMD_NAME%
ENV=MECH_LP=C:\Program Files\proeWildfire 5.0\mech
ENV=MECH_HOME=%MECH_LP%\%PRO_MACHINE_TYPE%
PSF=%MECH_LP%\install\nt\mech.psf
ENV=PRO_MECH_COMMAND="%PRO_DIRECTORY%\bin\proe.exe" "%PRO_DIRECTORY%\bin\proe1.psf"
ENV=PATH+=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\deflib
ENV=PATH-=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\lib
ENV=PATH-=%INTRALINK_DIR%\%PRO_MACHINE_TYPE%\illib
ENV=NMSD_TIMEOUT=300
ENV=PRO_COMM_MSG_EXE=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\pro_comm_msg.exe
ENV=PROE_START=%PRO_DIRECTORY%\bin\proe.exe
ENV=CDRS_DATA=%PRO_DIRECTORY%
ENV=PRO_IMAGE_CONVERTER=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\convert_image.exe
ENV=PROGUIDE_DIRECTORY=%PRO_DIRECTORY%\uifdoc
ENV=SPG_DIRECTORY=%PRO_DIRECTORY%
ENV=PRO_USRMAIN=%PRO_DIRECTORY%\usrprog\umain\usrmain.c
ENV=PROTABLE_DIRECTORY=%PRO_DIRECTORY%\protable
ENV=MOZILLA_FIVE_HOME=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\MOZILLA
ENV=PROTAB=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\protab.exe
ENV=ZIP_EXEC=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\zip.exe
ENV=CLHOME=%PRO_DIRECTORY%\text\pcldata
ENV=PVIEW_PROEPVIEW_HOME=%PRO_DIRECTORY%\apps\prodview
ENV=CV_ENV_HOME=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\CV102
ENV=VC_VCONF_START=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\ptcvconf.exe
ENV=DEBUG_HLP_DLL_PATH=%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\lib\dbghelp.dll
ENV=PTC_D_LICENSE_FILE-=C:\Program Files\proeWildfire 5.0\lic_gen\license.dat
ENV=PROE_FEATURE_NAME=PROE_WF5 ()
RUN="%MECH_LP%\install\nt\pro_mech_env.bat"
RUN="%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\nms\nmsd.exe" -noservice -timeout %NMSD_TIMEOUT% &
RUN="%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\obj\xtop.exe"
// USER - PSF 
// Add User specific environment or run applications below here 

RE: Fixed working directory

It works for me just like looslib showed. I have set up every computer in our office by setting the start in directory of the shortcut since we switched from HP-UX to windoze NT, XP & 7.

There has to be something strange in your version of windoze (LucasDemh). You aren't using windoze 8 are you?

----------------------------------------

The Help for this program was created in Windows Help format, which depends on a feature that isn't included in this version of Windows.

RE: Fixed working directory

Quote (LucasDemh)


"Start in" is set to "D:\Documents\", but PROE ignores it and goes to "C:\Windows\System32\"

Try setting it to C:\Documents\ you have D listed above in quote which may or may not have been a typo.
Is your "D:" Drive the large partition of your drive and "C:" is used for Microsoft Install & System files? otherwise it may just be a typo. Usually Windows will tell you there is an error in the start in path if it doesn't exist. Check the loadpoint Config.pro in the text sub directory of your proe creo install directory. Create a New File and hit save and then check if it's saving to system32 directory.

Typically the trail.txt.## files are written to the startup directory so there will be a group of them in system32 if that's where Proe is actually starting in that dir. Or see if when you do a save it browses to the Working Directory as default.

trail_file_dir "path to trail file save directory"
the above option may be set to C:\Windows\System32\ in the loadpoint config.pro in the text\ directory.

"It's not the size of the Forum that matters, It's the Quality of the Posts"

Michael Cole
Boston, MA
CSWP, CSWI, CSWTS
Follow me on !w¡#$%
@ TrajPar - @ mcSldWrx2008
= ProE = SolidWorks

RE: Fixed working directory

Getting off subject but I believe the config option is trail_dir and I set it to $temp and then purge that every time Pro/E starts.

Getting back to setting the working directory, what do you see when you pop up the folder tree? The working directory should be highlighted.

----------------------------------------

The Help for this program was created in Windows Help format, which depends on a feature that isn't included in this version of Windows.

RE: Fixed working directory

(OP)
It's windows 7.

D:/documents/ is correct, but no longer used.
I am now trying to point start_in to C:/projects.

For some reason, on the sortcut properties, it insists on NOT ADDING QUOTATION MARKS on the Start in field path.
After pressing OK, and openin properties again, the ones I've put are not there.


Is this relevant ?

Changin from backslash to slash, and combinations, gives the same thing.

RE: Fixed working directory

My shortcuts have no quotation marks.

----------------------------------------

The Help for this program was created in Windows Help format, which depends on a feature that isn't included in this version of Windows.

RE: Fixed working directory

Only need the quotation marks if your directory path has spaces in it.

Win7 is a little different than WinXP. My example was on a XP system.
Let me see if I get the same behavior on a Win7 system, if I can find one open after the engineers leave at 3:30. I stay later to work on Windchill things.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

RE: Fixed working directory

(OP)
Guys,

Thank you all for the efforts I am seeing here.

And don't go too deep on this tread.
I hope I'm not taking your time with this.

RE: Fixed working directory

Windows7 does through a curve at you.
I took my shortcut and copied it on my desktop, then changed the Start In folder. Pro/E still looked at the ORIGINAL icon's Start In folder as the working directory. I tried it with 3 different directories and drive combinations.

It looks like you had c:\system32 as your original default Start In folder. I will investigate some more if I get time. Being on Windchill, we don't use the native folders unless someone does a backup and then they usually navigate to their own folder of choice.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

RE: Fixed working directory

(OP)
Huh !
There it was, then...

Why the hell would I ever put this on system32 after installing...?
Not even by accident I could do that..
Besides, I didn't even knew about the functionality of the start in field of the shortcut...

Or...

Just now you put me to thinking:

I once wrote a batch file that didn't work. Only because the Windows' CMD start directory was the C:\Users\lucas>_ folder, and not C:\Windows\system32>_
I found over the internet a way to change that CMD's start in dir through a registry editign, and that's what I did* !

oh, boy...

>But Cancel/suspend this topic.<

Being or not this change the one to blame, I cleaned up the disk and installed windows 8 for testing.
Didn't install proE back, but soon I will.

If that happen again... Well... it used to happen on 7, as you say, now imagine 8...
Maybe it's incompatibility anyway...

Thank you all for the help.

I'll continue under subscription.


*Now I have windows 8 I can see that by defauld for windows CMD starts in the user's folder.
Again, I'll have to change it.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources