Fixed working directory

[LucasBS]

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'

????

 

[looslib]

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

 

[LucasBS]

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:

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

proe1.psf:

// 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

 

[looslib]

Attached screen shots of my icon properties and Set Working Directory in WF5 when I change the Start In field.

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

Ben Loosli

 

[dgallup]

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.

 

[mjcole]

"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

 

[dgallup]

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.

 

[LucasBS]

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.

 

[dgallup]

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.

 

[looslib]

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

 

[LucasBS]

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.

 

[looslib]

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

 

[LucasBS]

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.