spacing problems

hi
if i open a file in "My Documents" or any folder with a space in its name it says eg. if the file was called picture.bmp

"C:\My.bmp" is causes a lot of problems, please help

 

That shouldn't be a problem; maybe can you enlarge on the exact message you get from your computer?

 

i'll tell you exactly what it does

I open up C:\My Documents
I double click on printed.bmp
A message appears saying "C:\My.bmp was not found" the title of the box is Paint, wiht only an OK box.

 

I think the message is very clear. It is simply saying that the file the shortcut refers to is not in the location it is looking for it.

And also it appears that Paint is set as the default program to view .bmp files which looks to me like it is opening properly but it just can not find the file.

Unless I am mistaken C:\My.bmp says that the file should be in the Root folder of C: drive.

BillyBob

 

Error on only this one particular *.bmp or all *.bmp's. Does it happen on all files in "My Documents" folder?

Does it happen when accessing the files in the "My Documents" folder only or effects other folders as well? Which folders? All folders with spaces in the name?

What's the properties report as the path, when you right click on this *.bmp?

Tried moving it out of the "my documents" folder and opening from.... say the desktop?

=============
Possible and likely association problem with the path used to the program associated with file type. See:
google

Or some similar solution. You need that "%1"
to be included in the path. Let me see if I can find a link to one of those handy dandy reg patches that is known to fix this. A search on windows archived files of past posts has to have this/these patch link in them.

Here ya' go:
http://www.dougknox.com/utility/98fileassoc/bmp_assoc_98.zip
Download it, extract it, double click on it, when asked if you wish to merge etc confirm "yes ". This patch will make the neccessary registry changes/fix to associate bmp with mspaint.

Additional nfo:
google groups

 

Where did you go Ray? I see you've check this board a couple of times but have not added any feedback update. Are you nervous or unfamiliar about the use of registry patches?

 

Yes sorry about that my computer came down with a virus(that turned all programs into ms-dos ones or something so none of them could be run) so i had to format my disk and reinstall windows, anyway the problems has gone now, thanks anyway

bmp's were already associated with mspaint

 

Sorry to hear that Ray. I see you used the fix that worked for you. My bet is this still boiled down to association problem and was caused by the viral infection rather than a user blooper. They do make association changes and will take over and control extensions to executables. It obviously went a bit deeper than a bmp "open" association, though.

As a side note, it was not a question of whether bmp was associated to mspaint but whether the "open" command string for the path to mspaint was correct and had included the "%1" at the end of it ie; C:\Progra~1\Access~1\MSPAINT.E*XE "%1 " (not including that asterisk, which I assume was put there by a script from this board, as a safety)

I do hope you have taken steps to protect yourself far better in the future. Lot's of ugly critters on the net just waiting to nab ya'. Our security Forum has excellent and very informative guide lines and links to appropriate advice, software, howtos and whys. These are pinned to the tops of the main forum and the subforum. Perhaps you'd be interested in peeking into these.

Once again, I am sorry to hear you were caught with your guard down and had to use such a drastic measure to recover but thank you for taking the time to update this post. I was interested in the base cause for your initial problem. Now we both know. Your most welcome.