Metamorphman's Site

ID:158297 Sep 23 2009, 12:58 am
Metamorphman	Recently I discovered that trying to make a new .dm file named 'aux.dm' resulted in said .dm file to be un-included the instance it was made, and for DreamMaker to spurt out a 'Unable to read aux.dm' error. This got me thinking that aux.dm is probably an internal system file. Just out of curiosity, I'd like to see the contents of this elusive dm file, if that's ok. :)

#1 Sep 23 2009, 1:02 am
Nadrew	This actually isn't caused by BYOND, it's caused by Windows. aux.dm is a reserved device name. Attempting to save any file as aux.dm will fail. You'll get an actual error message when you try it from programs like Notepad.

#2 Sep 23 2009, 1:04 am In response to Nadrew (#1)
Metamorphman	Oh, wow. :o That's interesting. Thanks.

#3 Sep 23 2009, 7:28 pm In response to Metamorphman (#2)
Hobnob	Other ones to avoid are CON, PRN, COM1, COM2, COM3, COM4, LPT1, LPT2, LPT3, and NUL. Attempting to create a file (with any extension) named as one of these will usually fail under windows. This stuff is a hangover from DOS where you would read and write to these pseudo-files to access devices like printers and serial ports. AUX for instance was an alias for COM1, the first serial port.