• Windows invalid filenames

    From Nightfox@VERT/DIGDIST to All on Wednesday, October 26, 2011 18:35:04
    So, here's a strange issue in Windows that I just found recently.. I found this with Windows 7, so I'm not sure if other versions of Windows do it too. It won't let you create files with names that start with a period. Some programs (mainly ones that originated in the *nix world) use a configuration file that starts with a period - For instance, Vim uses a configuration file called .vimrc. However, if you try to create a file with a name like that in Windows, Windows shows the error message "You must type a file name." Even though you just did.. So, does anyone know how to configure Windows to allow such filenames?

    Nightfox

    ---
    þ Synchronet þ Digital Distortion BBS - digdist.bbsindex.com
  • From Corey@VERT/TSGC to Nightfox on Wednesday, October 26, 2011 20:10:04
    Re: Windows invalid filenames
    By: Nightfox to All on Wed Oct 26 2011 06:35 pm

    So, here's a strange issue in Windows that I just found recently.. I found this with Windows 7, so I'm not sure if other versions of Windows do it too. It won't let you create files with names that start with a period. Some programs (mainly ones that originated in the *nix world) use a configuration file that starts with a period - For instance, Vim uses a configuration file called .vimrc. However, if you try to create a file with a name like that i Windows, Windows shows the error message "You must type a file name." Even though you just did.. So, does anyone know how to configure Windows to allo such filenames?

    Nightfox


    yep. only unix/linux did that.

    "Practise safe Lunch, Use a Condiment"


    ---
    þ Synchronet þ Three Stooges Gentlemens Club - Las Vegas, Nv - tsgc.dyndns.org
  • From Digital Man@VERT to Nightfox on Wednesday, October 26, 2011 23:03:23
    Re: Windows invalid filenames
    By: Nightfox to All on Wed Oct 26 2011 06:35 pm

    So, here's a strange issue in Windows that I just found recently.. I found this with Windows 7, so I'm not sure if other versions of Windows do it
    too. It won't let you create files with names that start with a period.
    Some programs (mainly ones that originated in the *nix world) use a configuration file that starts with a period - For instance, Vim uses a configuration file called .vimrc. However, if you try to create a file
    with a name like that in Windows, Windows shows the error message "You must type a file name." Even though you just did.. So, does anyone know how to configure Windows to allow such filenames?

    Works here (on NTFS):

    echo blah > .blah

    dir .blah
    Volume in drive C has no label.
    Volume Serial Number is D8E4-4092

    Directory of C:\

    10/26/2011 11:03 PM 7 .blah

    Perhaps you're using FAT32 or some other file system that doesn't allow such naming?

    digital man

    Synchronet "Real Fact" #60:
    How to get Synchronet technical support: http://wiki.synchro.net/howto:support

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net
  • From art@VERT/FATCATS to Digital Man on Thursday, October 27, 2011 12:06:20
    Re: Windows invalid filenames
    By: Digital Man to Nightfox on Wed Oct 26 2011 23:03:23

    Hey Nightfox, DM,

    So, here's a strange issue in Windows that I just found recently.. I
    Works here (on NTFS):
    echo blah > .blah

    This is a limitation in the UI, not in the NTFS filesystem itself.

    While the GUI won't let you do that, it does work if you create them via another route as DM's done.

    Regards,

    / art @ fatcats [dot] poorcoding [dot] com \
    \ Fatcats +o - http://fatcats.poorcoding.com /

    ---
    þ Synchronet þ fatcats bbs - http://fatcats.poorcoding.com
  • From Mindless Automaton@VERT/ELDRITCH to Digital Man on Thursday, October 27, 2011 08:13:45
    Digital Man wrote:
    Re: Windows invalid filenames
    By: Nightfox to All on Wed Oct 26 2011 06:35 pm

    So, here's a strange issue in Windows that I just found recently.. I found
    this with Windows 7, so I'm not sure if other versions of Windows do it too. It won't let you create files with names that start with a period. Some programs (mainly ones that originated in the *nix world) use a configuration file that starts with a period - For instance, Vim uses a configuration file called .vimrc. However, if you try to create a file with a name like that in Windows, Windows shows the error message "You must
    type a file name." Even though you just did.. So, does anyone know how to
    configure Windows to allow such filenames?

    Works here (on NTFS):

    echo blah > .blah

    dir .blah
    Volume in drive C has no label.
    Volume Serial Number is D8E4-4092

    Directory of C:\

    10/26/2011 11:03 PM 7 .blah

    Perhaps you're using FAT32 or some other file system that doesn't allow such naming?


    If you are creating the file in Windows Explorer, it doesn't allow it
    (XP, NTFS here). Ie. right click, New, Text Document, attempt to name
    .blah . The work around is to create it from prompt. :o

    -Mindless Automaton
    ---
    þ Synchronet þ Eldritch Clockwork BBS - eldritch.darktech.org
  • From Boraxman@VERT/MSRDBBS to Nightfox on Thursday, October 27, 2011 20:05:33
    Re: Windows invalid filenames
    By: Nightfox to All on Wed Oct 26 2011 06:35 pm

    So, here's a strange issue in Windows that I just found recently.. I found this with Windows 7, so I'm not sure if other versions of Windows do it too. It won't let you create files with names that start with a period. Some programs (mainly ones that originated in the *nix world) use a configuration file that starts with a period - For instance, Vim uses a configuration file called .vimrc. However, if you try to create a file with a name like that i Windows, Windows shows the error message "You must type a file name." Even though you just did.. So, does anyone know how to configure Windows to allo such filenames?

    Nightfox


    You might have get the source code and comment out the function that is

    int Make_Unix_Incompatible(void)


    ---
    þ Synchronet þ MS & RD BBs - bbs.mozysswamp.org
  • From Nightfox@VERT/DIGDIST to Digital Man on Thursday, October 27, 2011 21:32:02
    Re: Windows invalid filenames
    By: Digital Man to Nightfox on Wed Oct 26 2011 23:03:23

    Works here (on NTFS):

    echo blah > .blah

    dir .blah
    Volume in drive C has no label.
    Volume Serial Number is D8E4-4092

    Directory of C:\

    10/26/2011 11:03 PM 7 .blah

    Perhaps you're using FAT32 or some other file system that doesn't allow such naming?

    I'm using NTFS. I figured that something like what you suggest would work, but I was trying to create a new file by right-clicking, then selecting New > Text Document, and calling it something like .blah. That -should- let you create the file with that name, but I guess for some reason Microsoft has decided that Windows shouldn't let that happen.

    Nightfox

    ---
    þ Synchronet þ Digital Distortion BBS - digdist.bbsindex.com
  • From Nightfox@VERT/DIGDIST to Boraxman on Thursday, October 27, 2011 21:33:32
    Re: Windows invalid filenames
    By: Boraxman to Nightfox on Thu Oct 27 2011 20:05:33

    You might have get the source code and comment out the function that is

    int Make_Unix_Incompatible(void)

    Ah, true.. Another issue is that the "void" is not necessary - If the function takes no command arguments, it is more clearly declared with an empty parameter list, as follows:
    int Make_Unix_Incompatible()

    Nightfox

    ---
    þ Synchronet þ Digital Distortion BBS - digdist.bbsindex.com
  • From Deuce@VERT/SYNCNIX to Nightfox on Friday, October 28, 2011 02:37:03
    Re: Windows invalid filenames
    By: Nightfox to Digital Man on Thu Oct 27 2011 09:32 pm

    I'm using NTFS. I figured that something like what you suggest would work, but I was trying to create a new file by right-clicking, then selecting New
    Text Document, and calling it something like .blah. That -should- let
    you create the file with that name, but I guess for some reason Microsoft has decided that Windows shouldn't let that happen.

    Try putting quotes around the file name.

    ---
    Synchronet - Jump on the Web 0.2 bandwagon!


    ---
    þ Synchronet þ My Brand-New BBS (All the cool SysOps run STOCK!)
  • From Nightfox@VERT/DIGDIST to Deuce on Friday, October 28, 2011 21:22:00
    Re: Windows invalid filenames
    By: Deuce to Nightfox on Fri Oct 28 2011 02:37:03

    but I was trying to create a new file by right-clicking, then selecting N
    Text Document, and calling it something like .blah. That -should- let
    you create the file with that name, but I guess for some reason Microsoft has decided that Windows shouldn't let that happen.

    Try putting quotes around the file name.

    Windows Explorer won't let you put quotes into filenames when renaming a file.

    Nightfox

    ---
    þ Synchronet þ Digital Distortion BBS - digdist.bbsindex.com
  • From Access Denied@VERT/PHARCYDE to Nightfox on Friday, October 28, 2011 19:30:45
    Re: Windows invalid filenames
    By: Nightfox to Digital Man on Thu Oct 27 2011 09:32 pm

    I'm using NTFS. I figured that something like what you suggest would work, I was trying to create a new file by right-clicking, then selecting New > Te Document, and calling it something like .blah. That -should- let you create the file with that name, but I guess for some reason Microsoft has decided t Windows shouldn't let that happen.

    Report it to M$ as a bug. They need some damn work to do, anyway. :)

    --
    axisd

    ---
    þ Synchronet þ thePharcyde_ >> telnet://bbs.pharcyde.org (Wisconsin)
  • From Corey@VERT/TSGC to Access Denied on Friday, October 28, 2011 23:22:09
    Re: Windows invalid filenames
    By: Access Denied to Nightfox on Fri Oct 28 2011 07:30 pm

    Re: Windows invalid filenames
    By: Nightfox to Digital Man on Thu Oct 27 2011 09:32 pm

    I'm using NTFS. I figured that something like what you suggest would wor I was trying to create a new file by right-clicking, then selecting New > Document, and calling it something like .blah. That -should- let you cre the file with that name, but I guess for some reason Microsoft has decide Windows shouldn't let that happen.

    Report it to M$ as a bug. They need some damn work to do, anyway. :)

    --
    axisd


    and they will fix it. and rename it, and sell us the new fixed version.

    "Practise safe Lunch, Use a Condiment"


    ---
    þ Synchronet þ Three Stooges Gentlemens Club - Las Vegas, Nv - tsgc.dyndns.org
  • From elm@VERT/ECHTOBBS to Nightfox on Friday, October 28, 2011 20:21:43
    Re: Windows invalid filenames
    By: Nightfox to All on Wed Oct 26 2011 18:35:04

    So, here's a strange issue in Windows that I just found recently.. I found this with Windows 7, so I'm not sure if other versions of Windows do it too. It won't let you create files with names that start with a period. Some programs (mainly ones that originated in the *nix world) use a configuration file that starts with a period - For instance, Vim uses a configuration file called .vimrc. However, if you try to create a file with a name like that i Windows, Windows shows the error message "You must type a file name." Even though you just did.. So, does anyone know how to configure Windows to allo such filenames?

    Nightfox


    The last character of a line in a .host file is a '.'. Go DNS!

    =)

    bbs.echto.net

    ---
    þ Synchronet þ -=-= echto bbs =-=-
  • From Access Denied@VERT/PHARCYDE to Corey on Saturday, October 29, 2011 17:31:32
    Re: Windows invalid filenames
    By: Corey to Access Denied on Fri Oct 28 2011 11:22 pm

    Report it to M$ as a bug. They need some damn work to do, anyway. :)

    and they will fix it. and rename it, and sell us the new fixed version.

    Sell it to who? I am not part of this "us" you speak of. :)

    --
    axisd

    ---
    þ Synchronet þ thePharcyde_ >> telnet://bbs.pharcyde.org (Wisconsin)
  • From Corey@VERT/TSGC to Access Denied on Saturday, October 29, 2011 17:16:38
    Re: Windows invalid filenames
    By: Access Denied to Corey on Sat Oct 29 2011 05:31 pm

    Re: Windows invalid filenames
    By: Corey to Access Denied on Fri Oct 28 2011 11:22 pm

    Report it to M$ as a bug. They need some damn work to do, anyway. :)

    and they will fix it. and rename it, and sell us the new fixed version.

    Sell it to who? I am not part of this "us" you speak of. :)

    --
    axisd


    the public.
    What you you think vista and 7 was?
    fixed nt based systems.

    "Practise safe Lunch, Use a Condiment"


    ---
    þ Synchronet þ Three Stooges Gentlemens Club - Las Vegas, Nv - tsgc.dyndns.org
  • From Lurch@VERT/APPY to Corey on Sunday, October 30, 2011 19:00:18
    Re: Windows invalid filenames
    By: Corey to Access Denied on Fri Oct 28 2011 23:22:09

    Re: Windows invalid filenames
    By: Access Denied to Nightfox on Fri Oct 28 2011 07:30 pm
    the file with that name, but I guess for some reason Microsoft has dec Windows shouldn't let that happen.

    Report it to M$ as a bug. They need some damn work to do, anyway. :)

    --

    Not really a bug. ".blah" When creating it from explorer windows is looking for the first part of the filename. By default it should be filename.extension so when you put .blah windows is looking for the filename as it views the .blah as the extension.

    DOS / command shell doesn't care what you name the file. You don't have the same issue in other OS's as they don't view file names in the same way.

    -=[LurcH]=-

    ---
    þ Synchronet þ -=[TAF BBS - Telnet://taf.org.nz]=-
  • From Boraxman@VERT/MSRDBBS to Access Denied on Sunday, October 30, 2011 20:57:42
    Re: Windows invalid filenames
    By: Access Denied to Nightfox on Fri Oct 28 2011 07:30 pm

    Re: Windows invalid filenames
    By: Nightfox to Digital Man on Thu Oct 27 2011 09:32 pm

    I'm using NTFS. I figured that something like what you suggest would wor I was trying to create a new file by right-clicking, then selecting New > Document, and calling it something like .blah. That -should- let you cre the file with that name, but I guess for some reason Microsoft has decide Windows shouldn't let that happen.

    Report it to M$ as a bug. They need some damn work to do, anyway. :)

    --
    axisd

    They're too busy. Their army of employees is flat out just trying to get windows to tile at the press of a buttom.

    ---
    þ Synchronet þ MS & RD BBs - bbs.mozysswamp.org