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'
????
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
----------------------------------------
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
RE: Fixed working directory
RE: Fixed 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
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
----------------------------------------
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
Problem remains.
https://www.dropbox.com/s/us9g79f0i6jfk0e/ProeProb...
Did I do something wrong ?
The directory pointed is there and is freely accessible.
RE: Fixed 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
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
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
And your Creo is obeying the law, as it should be.
I wish it did like yours on mine...
RE: Fixed working directory
David
RE: Fixed working directory
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
Good luck,
- J -
RE: Fixed working directory
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
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
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
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
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
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
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
proe1.psf:
CODE -->
RE: Fixed working directory
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: Fixed working directory
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
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 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
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
----------------------------------------
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
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
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
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
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.