Warning on illegal characters

[gammalost]

Thank you for making such a wonderful program.

 

Yesterday I made an ISO. Did a bit of cut/pasting for the filename. I failed to see that the filename contained a ":" in it. Imgburn started it's process as normal, but when it was done (and unfortunately I had deleted the sourcefiles) it only left a 0 byte file. The name of the file was the text before the ":".

 

Would be great if imgburn gave a warning when target filename contained characters that could potentially cause problems.

[LIGHTNING UK!]

I can't see that would have ever worked.

 

Even if ImgBurn didn't look for invalid characters in the file name, the OS wouldn't have been able to create the file and so that API function would (should) have failed and ImgBurn would have errored out.

[gammalost]

Behold

One thing I have learned over the years is that users will always find a way to do stuff they shouldnt be able to.

See included pictures + part of the log

 

I 19:38:58 Destination File: \\r2-backup\xxxx\xxxxx\xxxx\test X test : Vol 7 (2011) AVC BD25.iso
I 19:38:58 Destination Free Space: 345 143 738 368 Bytes (337 054 432,00 KiB) (329 154,72 MiB) (321,44 GiB)
I 19:38:58 Destination File System: NTFS
I 19:38:58 File Splitting: Auto
I 19:38:58 Writing Image...

I 19:57:43 Operation Successfully Completed! - Duration: 00:18:44

I 19:57:43 Average Write Rate: 19 819 KiB/s (4.5x) - Maximum Write Rate: 22 006 KiB/s (5.0x)

I wonder where the data went though since the file is 0 bytes.
Edit: the data is obviously tied to the 0 byte file as space was freed when I deleted it.

 

Edited November 11, 2013 by gammalost

[LIGHTNING UK!]

It seems that Windows just creates a file with an alternate data stream or something when you pass a file name with a colon in the name like that.

 

When I just tried it, it wasn't easy to delete the file either lol

 

I've added a check for that now, thanks.