Problem with ProE2001 search path

When you are defining a search path in the Windows NT operating system, you must precede the backslash character with another formatting character.

So, Geoffrey, are you on the NT operating system? And, if so, do you know what this warning means?

David Janes

Seems that you need to either a) remove the space from the directory name, or b) enclose the path with quotes: ie g:"\Drawing files\proe\ldt\fittings" also delete the trailing \ from the path.

HTH

: >g:\Drawing files\proe\ldt\ : >g:\Drawing files\proe\ldt\standart_parts\ : >g:\Drawing files\proe\ldt\conservator\ : >g:\Drawing files\proe\ldt\cover\ : >g:\Drawing files\proe\ldt\tank\ : >g:\Drawing files\proe\ldt\fittings\ : >

: >and below is partial content of the config.pro file : >

: >weld_ui_standard ANSI : >windows_scale 1.000000 : >www_add_aux_frame NO : >www_export_geometry_as JPG_VRML : >www_multiple_views TOP : >www_tree_location OUT : >x_angle 0.000000 : >y_angle 0.000000 : >search_path_file G:\Drawing Files\ProE\LDT\search.pro : >

: >Could someone give me some hint as what is wrong with the proe setup? : >

: >Thanks and regards, : >

: >Geoffrey : >

: : Seems that you need to either a) remove the space from the directory : name, or b) enclose the path with quotes: : ie g:"\Drawing files\proe\ldt\fittings" : also delete the trailing \ from the path. : Nooooo, noo, no no no, you're not telling me that this multi-grand professional program can't get past the 16-bit bug which wouldn't let you use long file names or file names with spaces in them!?! That got fixed in Windows 95. THAT'S STILL IN PRO/E'S CODE!?!?! It runs on NT, doesn't even have a 16-bit file system. I don't know, man, this is kind of beyond belief, beyond the 'Outer Limits', if it's true. Jeez, I hope not, cuz that would mean that PTC has about 10 years of catching up to do. NO SPACES IN FILE NAMES? I think they got past that, didn't they. They can't be that dorky. I mean, really, that's just silly. Maybe it's the goofy batch files or the goofy batch utilities, like Amateur/BATCH (I would say Pro/BATCH, but there's nothing even remotely professional about using batch files on a Windows system which eschewed batch processes with the end of 16-bit programming in favor of the GUI interface and OOP. Pro/e has a long way to go before it's even a half-assed GUI program.

Well...what can i say..take a Pro/zack and call tech in the morn.. The OP's search setup look good except for the space, and I use the exact same method and all is well, except for the space in the filename. Even in win2K you need to enclose paths with quotes for command line functions to work correctly otherwise the space is considered as an option separator.... Pro isn't entirely to blame for this one... Willy Gates needs a shake as well...

"David Janes" wrote > NO SPACES IN FILE NAMES? I think they got past that, didn't they.

Uh uh. Some things work with spaces, some don't (search paths don't). Try opening a STEP file and an IGES file with spaces in the file name. 8~)

======================

Have you installed Wildfire?

They specifically warn you that even though they default the Pro/E code to the Program Files directories, Mechanica may not work properly if you have spaces in the Pro/E directory structure. Go figure!

32-bit interpretation of 16-bit utilities, like setvars. Pro/e is such a mix and jumble of 16 and 32 bit code, it's a wonder it works at all. While it's true that some strings must be enclosed in quotes to be passed correctly, this applies to 32 bit terminal programs, where parameters are passed as so-called 'environment variables', a hangover from dos days. Windows services do not directly use these services and are not bothered by spaces in file names. So, it really depends on how the code was programmed in the first place. If you open Properties and find a 'Start in' box, you will see a directory string enclosed in quotes. Those programs which do not have a 'start in' box do not use these environment variable services. Whereas, there are still programs on xp which show, in any report on active processes, that some have paths such as C:\PROGRA~1\MOUSE~1\SYSTEM\EM_EXEC.EXE (a Logitech mouse driver). If your system shows such path and files names which are all caps, they are using 16 bit system and file resources, which do not support long file names or spaces in file names. Oh, and BTW, B Gates was going to get rid of all this crappy dos shit a long time ago but met the furious protests of 16 bit games who kinda sorta talked him out of it.

David Janes

Hello David,

Could you please be more specific about this "another formatting character"? I remember I have read something about the extra formatting character a while ago.

Thanks,

Geoffrey

: > When you are defining a search path in the Windows NT operating system, : you must : > precede the backslash character with another formatting character. : : Hello David, : : Could you please be more specific about this "another formatting character"? : I remember I have read something about the extra formatting character a : while ago. : Um, well, I was hoping you'd know. Seems to me I've seen NT paths formatted something like this:

g:\\Drawing files\\proe\\ldt\\standart_parts

with a double backslash or an extra formatting character before the backslash. Others have suggested enclosing the whole search string in quotes as follows:

"g:\Drawing files\proe\ldt\standart_parts"

I can't give you the definitive answer except to try each and see which works.

David Janes

I think the problem is that you can't use spaces in the directory names.

g:\Drawing files\ should probable be g:\Drawing_files\

I've not had probles with double slashes as described in the previous post in either NT, Win 2K, or XP