This is a weird problem that involves one text file and one image file. The first is model.mtl, whose second line refers to the second file, model.jpg, as follows

map_Kd model.jpg

I however have this problem:
*.mtl files written in Linux are interpreted by most Windows apps as if 'model.jpg' had a '/' before it.
The file model.jpg doesn't load because the 3D apps understands that the path to model.jpg is:
//model.jpg
Obviously '/model.jpg' is not found.
It however should be read
/model.jpg

The command 'map_Kd' is interpreted by 3D apps as an instruction to load the file model.jpg. The model.mtl is the file that contains that instruction.
All 3D apps in Linux and else understand this.
The text files*.mtl are correct when opened in a text editor.
Those files where in the same directory when they were written by the Linux app.
What is happening?

well, while i had a very hardtime reading your question, i think i understand your problem correctly. There is no problem with extra slashes. both

> cd /home/user//directory1///directory2

and

>cd /home/user/directory1/directory2

will do the same thing. it seems to me that the problem is that your pathname is missing the leading period '.'. for example:

> cd ./directory1

and

>cd /directory1

are not the same thing. the first will go into a directory located in your Current directory. the second will go to a directory named 'directory1' in the root directory (/). you need the . before the slash to specify a relative path as apposed to an absolute path.

I'm sorry about my question not being clear.
I found that the problem lies in the 3D app. It can't connect the loaded .jpg to the .obj files.
I thought that this was a Windows problem reading Linux text files or the paths to files in text files written in Linux. Humm, this is embarrasing.
And thanks for the post. I learnt that pathnames with // or/// can be read by Linux, but Windows won't take \\ or \\\.
Melsync