I’ve noticed that when borrowing an existing filename from a save dialog window to simply add or modifiy the filename to save a sequential or similarly named file, MAX will try to save over the old name used to start the process.  Regardless of what is in the filename box.

1. Render and save a JPG to render 1.jpg
2. From Frame buffer save the file again
3. In the same folder, select the file render 1.jpg
4. Edit the File name: text box to read render 2.jpg
5. MAX will ask to overwrite render 1.jpg
6. Deselect the file render 1.jpg from the browser portion
7. Cut and Paste the filename render 2.jpg from the text box
8. This is the only way to save a replicated file naming structure

Is it safe to say you are using Vista?
Here, this is a Vista problem, not limited to Max.
If you save it the second time and don’t highlight the file already
in the folder you can save it to another name by typing immediately
into the save field.
Once you’ve highlighted a file already present in the folder,
Windows will always try to save to that file name.
This is totally irritating,
but it’s what has been happening since I installed Vista.

Don

Max 2012
Windows 7 64 SP1

hmm… I tested notepad.  It did not behave the same way.

I did request this hotfix however from Microsoft.

http://support.microsoft.com/kb/935415

We’ll see.

Thanks, I requested the hotfix as well.
After reading the warnings, I plan to created a restore point before applying it though.
If it produces other problems I want the option to go back.

Don

Max 2012
Windows 7 64 SP1

Couple of new things I’m now finding:
I am not having the problem with Max 2009, buy am having it with Max 2008.
I filled in the form for the hotfix (correctly, I might add) and the file
from the download link says it’s not for my system when I try to install it.

Don

Max 2012
Windows 7 64 SP1

Don, were you able to get to the bottom of this?  I never heard back from MS on the fix for this.  I have noticed that NO other program but MAX 9 behaves this way when saving a file via the Frame Buffer.  I know Vista is a less than perfect environment for software engineers, but this seems pretty basic to me.

Is anyone else seeing this?

Did you install the alternate method of fixing the problem, install Vista SP1?

http://support.microsoft.com/kb/935791/

In the KB that you linked earlier, it said you could install SP1 or ask for the Hotfix.

Maneswar Cheemalapati [FA]

yep.  I’m running SP1.

Hmmm, didn’t think it was fixed but can’t seem to reproduce it right now in either 9, 2008 or 2009. Service Pack One here as well.

Max 2012
Windows 7 64 SP1

Has anybody discovered a fix for this issue?  No other program suffers from this bug but MAX.  I would at least like to hear from someone running MAX 2009 32-bit on Vista 64 where this does not occur.  See my first post for exactly what’s happening.

Still seeing it in 64 bit Vista, Max 2009.

Max 2012
Windows 7 64 SP1