Subject:
|
Re: Reinstalling all cad stuff
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Tue, 16 Mar 1999 21:04:51 GMT
|
Viewed:
|
2150 times
|
| |
|
|
Hi here are extracts from two articles out of the microsoft documentation:
extract 1:
Long Names to Use for Testing
Use the following guidelines to test your application for proper handling of
long file and printer names (spaces are represented by the # character):
Allow periods, plus signs, commas, semicolons, equal signs, and square
brackets anywhere.
Don't save leading or trailing spaces.
Don't save question marks.
Support MAX_PATH characters (including the drive, path, and extension).
Save to a universal naming convention (UNC) path, such as
\\Server\Directory\Filename.
If your application uses a default extension, it should add it
automatically. For example, "test." will save as "test..ext".
test
....test....
....####test####....
....####te..st####....
test....
....test
.test
test.
test#test#test#test
C:\test#1234567890[on to MAX_PATH total length]
\\folder#one\folder#two\folder#three\folder#four\file
test (saved as "test.ext")
###test (saved as "test.ext")
test### (saved as "test.ext")
###..test..##(saved as "..test...ext")
test#;#+#,#=#[#] (saved as "test#;#+#,#=#[#].ext")
####....####test.test####....## (saved as "....####test.test####.....ext")
extract2:
Note
Neither the user nor an application can control the name created by the
automatic alias process. Related issues are discussed in "Long File Names
and Network Compatibility" later in this chapter.
For the file name to comply with the 8.3 file name rules, it must use only
the valid characters for an alias and it must be all uppercase. Valid
characters for 8.3 file names (and aliases) can be any combination of
letters and numbers, a space (ASCII 20H), ASCII characters greater than 127,
and the following special characters:
$ % ' - _ @ ~ ` ! ( ) ^ # &
The following additional characters are valid in long file names, but are
not valid in alias names or 8.3 file names:
+ , ; = [ ]
The following rules also apply for Windows 98 file systems:
Maximum file name component length is 255 characters, including NULL.
Maximum path length is 260 characters, including NULL (compared to 80
characters for a short name).
The OEM character set used by the installable file system (IFS) is
determined by the registry and the contents of the file Unicode.bin.
The long file name directory entries use the Unicode character set to store
the names.
The file name and the alias are the same if the file name meets 8.3 file
name rules (that is, if it contains only valid characters for an alias and
it is all uppercase). This means that a file name using only valid
characters for an alias and following the 8.3 file name format is still not
the same as the alias name if it contains lowercase characters. However, in
this case the alias is the uppercase version of the file name. For example,
if the long file name is Examples.txt, its alias is EXAMPLES.TXT. The case
is preserved in the long file name. (Note, though, that path-based APIs in
the Windows 98 file system are not case-sensitive. So a search of the form
"EXAMPLES.TXT" or "Examples.txt" will find the same files.)
Tip
To see the alias for a file, right-click the file in any shell program such
as Windows Explorer, and then select Properties from the context menu. The
value for MS-DOS Name in the General Properties dialog box shows the alias
assigned to this file. Also, the dir command at the command prompt shows the
long file name.
Paul Gyugyi a écrit dans le message <36EB5A65.CE9B8A20@gyugyi.com>...
> I can guess what it is: IE is using a temp file name and path
> name that is a little too weird for LDLite. The LDLite code
> that opens file names changed in 1.6, and it is possible that
> a unallowed symbol is in the path to the file, e.g. something
> not matching:
> alpha [a-zA-Z]
> special [\.\_,\-\~/\\#:]
> digit [0-9]
> ident ({alpha}|{digit}|{special})+
>
> Please see if you can find the path the the file, maybe by doing
> a Start/Find for ldlite.dat when LDLite is running. (BTW, it is
> common for browsers to use temp filenames which include the
> name of the application, like ldraw.dat ldraw(2).dat, etc.)
>
> DOS gurus: what symbol(s) have been left out of the above regexp
> that are valid in filenames?
>
> Um, *wham*, I just noticed "(" and ")" in ldraw(2).dat. That would
> be the problem, then.
>
> Thanks,
> -gyug
>
>
> KJMRR wrote:
> [...]
> >
> > Nope. Funny thing here.... The file name is "ldraw". Then after I tried • it
> > again, on the same dat file (this is via the lugnet.cad.dat interface) • the
> > file name was "ldraw(2)". Wierd. • [...]
> >
> > Hmm.... I just tried another thing. Just yesterday I downloaded Netscape
> > Communicator 4.51 (I've been using IE4). So, after your comment about it
> > all working fine for you in Netscape, I thought I'd try that. And, well,
> > everything works. No problems. So, clearly its something IE specific. • I
> > don't know what.
> >
|
|
Message has 1 Reply:
 | | Re: Reinstalling all cad stuff
|
| (...) Benoit, This information you extracted from the two articles -- was it copyrighted information? Did MS place it in the public domain or grant a license to republish it elsewhere? --Todd (26 years ago, 29-Mar-99, to lugnet.cad)
|
Message is in Reply To:
| | Re: Reinstalling all cad stuff
|
| I can guess what it is: IE is using a temp file name and path name that is a little too weird for LDLite. The LDLite code that opens file names changed in 1.6, and it is possible that a unallowed symbol is in the path to the file, e.g. something not (...) (26 years ago, 14-Mar-99, to lugnet.cad)
|
14 Messages in This Thread:
 
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
