It will be answer with something like:

“OSX:/Users/carlo/Desktop/one two three four five #1EEA75/”

It weird because I can load file up to 51 charachters without problem… and over 51 the error occurs.

But I’m counting the “path size” as the length of the string (see the patch that I’ve attatched).

Is it possible that is a “spaces” problem instead of the length of names?

Thanks

I’m using the “opendialog” object to fill an lcd with names of the files of a certain folder (it’s the Topher LaFata’s filebrowse).
It result something like:

replace /Users/carlo/Desktop/one two three four fiv#1EF185/myfile.wav

that doesn’t work with buffer~.

I think it is not possible to solve this issue. Hovewer, I would like to know “when” thi happen, to show an error message.

It is not ok to count the number of characters of the string of the path I guess… how can I do it?

I’m using the same solution.
Carlo, hope this helps (pay attention to the loadbang):

#P button 36 35 15 0;
#P outlet 36 218 15 0;
#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#N vpatcher 2094 296 2404 659;
#P window setfont “Sans Serif” 9.;
#P comment 150 243 100 196617 contains #;
#P window linecount 0;
#P newex 28 223 236 196617 sel 1 2;
#P newex 28 201 34 196617 zl len;
#P button 70 121 15 0;
#P newex 28 180 54 196617 thresh 20;
#P button 28 121 15 0;
#P button 141 272 15 0;
#P button 28 271 15 0;
#P outlet 141 300 15 0;
#P window linecount 1;
#P newex 99 37 48 196617 loadbang;
#P message 99 63 100 196617 substitute # dummy;
#P newex 28 88 66 196617 regexp #;
#P outlet 28 300 15 0;
#P inlet 28 34 15 0;
#P window linecount 0;
#P comment 40 243 100 196617 doesn’t contain #;
#P window linecount 1;
#P message 70 151 14 196617 2;
#P message 28 151 14 196617 1;
#P connect 3 0 5 0;
#P fasten 6 0 5 0 104 83 33 83;
#P connect 5 0 11 0;
#P connect 11 0 0 0;
#P fasten 1 0 12 0 75 173 33 173;
#P connect 0 0 12 0;
#P connect 12 0 14 0;
#P connect 14 0 15 0;
#P connect 15 0 9 0;
#P connect 9 0 4 0;
#P connect 5 3 13 0;
#P connect 13 0 1 0;
#P connect 7 0 6 0;
#P connect 15 1 10 0;
#P connect 10 0 8 0;
#P pop;
#P newobj 36 120 50 196617 p toolong;
#P message 36 194 71 196617 Path too long!;
#P newex 278 194 36 196617 zl reg;
#P newex 36 81 278 196617 t l l;
#P newex 36 55 71 196617 opendialog fold;
#P fasten 2 0 5 0 283 214 41 214;
#P connect 3 0 5 0;
#P connect 6 0 0 0;
#P connect 0 0 1 0;
#P connect 1 0 4 0;
#P fasten 4 1 3 0 81 165 41 165;
#P fasten 4 0 2 0 41 157 283 157;
#P lcolor 6;
#P connect 1 1 2 1;
#P window clipboard copycount 7;

Hope to find a really solution one day :)

best,
nesa

#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P comment 340 407 316 196617 tail – strips first 30 characters
(‘kMDItemFSName =’);
#P comment 340 389 316 196617 grep – extracts only the line
containing full file name;
#P message 90 520 257 196617 “one two three four five six seven eight
nine ten.txt”;
#P newex 90 459 64 196617 fromsymbol;
#P newex 90 492 80 196617 prepend set;
#P newex 90 387 230 196617 append | grep -m 1 kMDItemFSName | tail -c
+30;
#P newex 90 364 69 196617 prepend mdls;
#P newex 90 329 107 196617 sprintf symout “%s”;
#P user dropfile 113 148 402 287 1;
#P newex 90 302 110 196617 conformpath max boot;
#B color 5;
#P newex 90 410 31 196617 shell;
#P button 90 82 15 0;
#P newex 90 117 56 196617 opendialog;
#P comment 340 371 316 196617 mdls – lists the metadata attributes
for the specified file;
#P comment 201 134 100 196617 dropfile:;
#P user panel 82 356 247 80;
#X brgb 206 242 171;
#X frgb 0 0 0;
#X border 1;
#X rounded 0;
#X shadow 0;
#X done;
#P connect 4 0 3 0;
#P connect 3 0 6 0;
#P connect 7 0 6 0;
#P connect 6 0 8 0;
#P connect 8 0 9 0;
#P connect 9 0 10 0;
#P connect 10 0 5 0;
#P connect 5 0 12 0;
#P connect 12 0 11 0;
#P connect 11 0 13 0;
#P window clipboard copycount 16;

Also I’m not sure that exist a “shell” object for Windows XP that does the “grep” function.
Maybe this one: http://www.maxobjects.com/?v=objects&id_objet=3531&requested=shell&operateur=AND&id_plateforme=0
?