mIRC Homepage
Posted By: BaFe * /write: unable to open file - 12/04/04 06:25 PM
When i try to use /write command with filenames like "shadow.type" or "prn.type" it returns unable to open file - error. There are no such files, so no read-only possibillity. Also with /write C:\[censored]\shadow.blaa returns the error message.
I dont know if there are others than "shadow" or "prn" that brings the error, but those I've noticed...
Same appears to be with all my friends using mIRC 6.14, so what the heck? crazy
Posted By: LocutusofBorg Re: * /write: unable to open file - 14/04/04 03:27 PM
Make sure there are no spaces in the filepath. Also, mIRC cannot /write to a file in a directory that doesn't exist. If the directory does exist but the file doesn't, /write will work and create the file, but if the directory doesn't exist either you get that error. If your directorypath contains spaces, mIRC will pick that up as a non existant directory...

/write c:\program files\text.txt stuff

In this case, mIRC will attempt to write the phrase files\text.txt stuff to the file called c:\program. While in this case there won't be a problem, similar things happen when spaces appear in the directory path.
Posted By: BaFe Re: * /write: unable to open file - 14/04/04 08:24 PM
Thx for reply, but the same error appears also with only /write shadow.ini blaa so no matter if the folder does'nt exist or i forget the "-apostrophe. Try it your own to create a shadow.txt file to anywhere with /write command (mirc6.14) so i really think this is a bug. :tongue:
Posted By: ADubb Re: * /write: unable to open file - 15/04/04 06:29 AM
yup, i got the same error, but only on shadow.[any extension]

weird eh?
Posted By: Iori Re: * /write: unable to open file - 19/04/04 10:54 AM
This is a problem with several filenames. (I don't know why.)
//echo -a $mkfn(shadow) $mkfn(ip) $mkfn(global)
shadow_ ip_ global_
Posted By: Khaled Re: * /write: unable to open file - 25/04/04 01:54 PM
That is correct, some filenames may be classified as device names by the Windows system you are using. If so, mIRC checks that and prevents you from writing to those device names to prevent system errors, freezes, etc.
Posted By: tidy_trax Re: * /write: unable to open file - 25/04/04 02:26 PM
i take it that is why it cant write to NUL.txt
Posted By: Iori Re: * /write: unable to open file - 26/04/04 11:38 AM
In the case of names such as "prn" or "con" that may be true, but each of those filenames that I mentioned are valid in other programs and Windows itself. :tongue:
In fact some are only blocked by mIRC in Windows NT and not in 9x.
Posted By: BaFe Re: * /write: unable to open file - 28/04/04 09:16 PM
Thx for the $mkfn that'll help me a lot smile
© mIRC Discussion Forums