search for: lpt9

"lpt1" through "lpt9" and "com1" through "com9" are in fact "special" file names under various versions of Microsoft Windows. However, "R Extensions" says only that "lpt1" through "lpt4" and "com1" through "com3" cannot be used as...

...ile systems and supported operating system platforms, the ASCII control characters as well as the characters ?"?, ?*?, ?:?, ?/?, ?<?, ?>?, ???, ?\?, and ?|? are not allowed in file names. In addition, files with names ?con?, ?prn?, ?aux?, ?clock$?, ?nul?, ?com1? to ?com9?, and ?lpt1? to ?lpt9? after conversion to lower case and stripping possible ?extensions? (e.g., ?lpt5.foo.bar?), are disallowed. Also, file names in the same directory must not differ only by case (see the previous paragraph). In addition, the basenames of ?.Rd? files may be used in URLs and so must be ASCII and not co...

...ny name starting "prn" (upper or > lowercase), followed by an extension (i.e. a dot and characters) is taken > to be the DOS printer device. According to Writing R Extensions, names > starting with "?con?, ?prn?, ?aux?, ?clock$?, ?nul?, ?com1? to ?com9?, and > ?lpt1? to ?lpt9' (possibly followed by extensions) are also bad. You can > Google "PRN filename in Windows" to find lots of people confused by this. > One page I get is > > https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx > > but there's no guarantee that will work...

Dear all, while preparing some exercises I came across some highly surprising behaviour of file.exists(). The specific value "prn.us.txt" always returns TRUE, even though that file is nowhere to be found on my system. In a fresh R session 3.4.4 installed on Windows 10: > grep("prn.us.txt", dir(recursive = TRUE)) integer(0) > file.exists("prn.us.txt") [1] TRUE

...not an R bug. Any name starting "prn" (upper or lowercase), followed by an extension (i.e. a dot and characters) is taken to be the DOS printer device. According to Writing R Extensions, names starting with "?con?, ?prn?, ?aux?, ?clock$?, ?nul?, ?com1? to ?com9?, and ?lpt1? to ?lpt9' (possibly followed by extensions) are also bad. You can Google "PRN filename in Windows" to find lots of people confused by this. One page I get is https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx but there's no guarantee that will work five minutes from now....

...s printers on various ports. It seems to output to port LPT1 regardless of the port I specify in the registry and win.ini. Here is a simplified scenario, in which I define only one printer, on LPT2. Can any one tell me what is happening? Follow-up question: Am I limited to 9 printers, on LPT1-LPT9? -Lee Allen output of wine --debugmsg +psdrv (just one relevant line, I think): trace:psdrv:PSDRV_ExtDeviceMode16 (hwnd=0000, hDriver=0000, devOut=(nil), Device='Wine PostScript Driver', Port='LPT1:', devIn=(nil), Profile='(null)', Mode=0000) <-----------------------...

...device open LPT4 not supported (yet) err:file:CreateFileA Couldn't open device 'LPT4'! fixme:win32:DEVICE_Open Unknown VxD LPT5 fixme:win32:DEVICE_Open Unknown VxD LPT6 fixme:win32:DEVICE_Open Unknown VxD LPT7 fixme:win32:DEVICE_Open Unknown VxD LPT8 fixme:win32:DEVICE_Open Unknown VxD LPT9 fixme:win32:DEVICE_Open Unknown VxD COM0 err:file:CreateFileA Couldn't open device 'COM3'! err:file:CreateFileA Couldn't open device 'COM4'! fixme:win32:DEVICE_Open Unknown VxD COM5 fixme:win32:DEVICE_Open Unknown VxD COM6 fixme:win32:DEVICE_Open Unknown VxD COM7 fixme:win32...

...ice no known default for device lpt5 fixme:file:get_default_lpt_device no known default for device lpt6 fixme:file:get_default_lpt_device no known default for device lpt7 fixme:file:get_default_lpt_device no known default for device lpt8 fixme:file:get_default_lpt_device no known default for device lpt9 err:wgl:X11DRV_wglCreateContext Cannot get FB Config for iPixelFormat 0, expect problems! err:wgl:X11DRV_wglCreateContext Cannot get FB Config for iPixelFormat 0, expect problems! wine: Unhandled page fault on read access to 0xfffffff8 at address 0x4bb9b7 (thread 001c), starting debugger... Unhandl...