Shoutbox

With this bug it will be possible crash msn of others.

If you have an email adres: com1.test@comgenie.com , or an other email adres which starts with com1.  , And you chat with somebody which have msgplus chatlogging on. Msn will crash, because it tries to save it as com1.test@comgenie.com , But com1. is a reserved windows filename.

Windows-version: Windows XP, 5.01.2600
Messenger-version: 7.5.0160
Messenger Plus!-version: 3.54.0132

Suggestion to fix: Put a character before the filename or something, like _ .

Cya, Comgenie

quote:

---

Originally posted by Comgenie
But com1. is a reserved windows filename

---

so true....

and the bug happens with com2. , com3. , nul. , etc...

Plus! should detect such names and avoid them

quote:

---

Originally posted by Comgenie
Suggestion to fix: Put a character before the filename or something, like _ .

---

i think it would be better if the _ is put in the place of the dot after com1, this way, the name of the file will start with "c" and when you sort the logs by name it gets placed at the spected possition

Thank you for the report, I was actually not aware of such limitations in the file system. I checked the MSDN and found the documentation I needed. The problem is fixed .

I never thought of that either (besides the few illegal filename characters which exist) and thus need this to be fixed in some of my personal programs also, so...

quote:

---

Originally posted by Patchou
I checked the MSDN and found the documentation I needed

---

can you list the appropiate links? (so I don't have to search for it; and it would benefit others as well I assume)

http://msdn.microsoft.com/library/default.asp?url.../naming_a_file.asp
?

yep, that's the doc I used to fix my code. I bet 90% of the programs I have installed on my comp are not aware of this strange limitation as well.

quote:

---

Originally posted by Patchou
I bet 90% of the programs I have installed on my comp are not aware of this strange limitation as well.

---

only 90%? I think that all programs that write to a file without selecting the fine name with the GetOpenFileName API, have that bug.

quote:

---

Originally posted by Patchou
strange limitation

---

that's a limitation of the times of MSDOS, where you could print a file typing

type file > lpt1

and do similar things (like using nul in the same way as /dev/null is used in unix)

yeah but accepting it as part of another file name? I mean, I never saw a command trying to do someting with the serial port by doing com1.whatever .

quote:

---

Originally posted by Patchou
yeah but accepting it as part of another file name? I mean, I never saw a command trying to do someting with the serial port by doing com1.whatever .

---

Well you never know, windows has a lot of dodgy things relating to MODE, like that C:\con\con bug

It can be pretty fun to do [img]c:\con\con[/img] and crash all the 98 users