Date: Wed, 10 Jul 2002 02:05:27 -0400   
   From: HECTOR SANTOS   
   To: ANDREW WHITE   
   Subject: RE: Major Problem with Long Filename Format   
   Newsgroups: win.server.wish.list   
   Message-ID: <1026281127.33.1026261565@winserver.com>   
   References:  <1026261565.33.0@winserver.com>   
   X-WcMsg-Attr: Rcvd   
   X-Mailer: Wildcat! Interactive Net Server v7.0.454.5   
   Lines: 56   
      
   This is the "WISH LIST" forum, not a "Problems reporting" forum. But   
   I guess if you "wishing for a fix" so that you don't have to spend the   
   "MORE trouble" looking for another package after what 15+ years in lieu   
   of getting a bug fixed when you know bugs fixes is not unknown at   
   Santronics, then I guess it is ok to post here. :-) But you should    
   visit the other forums where there is active discussions on current    
   operations.   
      
   Also, a good place is the use support web site which has the "Problem    
   Reporting" site. It will ask you for upfront information to help    
   minimize the guessing game of what you have or do not have.   
      
   With that a side.....   
      
   If you are part of the AUP, 450.2 released yesterday resolves long    
   file name issues dealing with spaces and plus characters.  This was   
   one of the major holdups for releasing AUP 450.2.   
      
   I too noticed the [1] in multi-dotted file names.   
      
   Unfortunately, Wildcat! is not inserting this [1], that is your    
   Microsoft IE BROWSER doing this. I wish it was in was in my control so    
   I can fix it.   
      
   Nonetheless, Wildcat! is most definitely sending to the browser what is    
   called the "Content-Disposition" containing the true name of the file.    
   That is the standard.     
      
   But for some reason the IE browser added the [1] to multi-dotted file    
   names.  You should ask Microsoft about that. Thanks for reminding me.   
   I'm going to ask them too.   
      
   ---   
      
   On 7/10/02 1:36 AM, ANDREW WHITE wrote to ALL:   
      
   > Not sure exactly which conference to pos this is, but I've noticed a problem    
   > with the longname file support that is giving my organization fits.  We use    
   > filenames such as 55_AWhite.cup.car  Notice there are 2 periods in the file    
   > name.  Well, WinServer wants to insert it's own [1] instead so the filename    
   > looks like 55_AWhite[1].cup.car  Well, that means that everytime someone    
   > downloads a file, they have to change the name of it.. not good, since it is    
   > vital that everyone running our program must have the SAME filenames on each    
   > computer.  Also, if you leave a space in the name, WinServer wants to insert    
   > a "+" sign upon download.  Also, not good.  Is there anyway to get these    
   > problems fixed?  It's causing us all kinds of trouble and I'd hate to have    
   to    
   > look for another software package, being a dedicated Wildcat user since V.3   
   >    
   > Than you for your time...   
   > --   
   > Andrew White   
   > www.hgns.net   
   >     
      
       
    * Origin: Prison Board BBS Mesquite Tx  //telnet.RDFIG.NET www. (1:124/5013)