I'm wondering if anyone has compiled an index of all those numbers, and the directories they're associated with? I couldn't find anything on Google, and I figure a complete list would be pretty handy. In case you're thinking I'm an evil little leech of a newb, I'd be willing to do this myself if no one already has.
Page 1 of 1
[DestinationDirs] codes for *.inf installations
#2
Posted 25 October 2005 - 12:26 PM
Hi, I have just found a little proggie to help in creating inf files that has plenty of very nice features.
http://snoopy81.ifra...om/en/willy.htm
http://snoopy81.ifra...om/en/willy.htm
#3
Posted 25 October 2005 - 01:28 PM
Quote
In case you're thinking I'm an evil little leech of a newb, I'd be willing to do this myself if no one already has
I started to compile such a list once but it quickly got added it to my "latter" list. You'll find some relevant info, links, and a partial list on this thread, and a wealth of information via this one.
I pulled the following snippets from one of the MS docs mentioned in the second thread (can't recall which right now) - it highlights just how complicated the job of setting up a complete (ie. not just DirID's) and definative list might be:
Quote
Variable LDIDs (VarLDIDs) allow for INFs to reliably find the existing Program Files, Accessories, etc., locations.
Directories that have long file names or that may have extended characters in their names may have multiple LDIDs. For example, 28700 and 28701 both point to "Program Files", but 28700 corresponds to the short file name "Progra~1" while 28701 corresponds to the long file name. Likewise, 28700 and 28702 both point to the short name "Progra~1", but 28700 renders this name in the OEM character set whereas 28702 renders it in ANSI characters. Different LDIDs are appropriate for different uses. In general, OEM/SFN LDIDs are uses for file copying, ANSI/LFN are used for strings written to the registry, and ANSI/SFN are used for Setup.ini entries that create start menu shortcuts.
The flag values at the end of the VarLDID.LFN and VarLDID.SFN sections show how the directories are represented internally as strings. The flag values have the following meanings:
0 = OEM/SFN (Default)1 = ANSI/SFN2 = OEM/LFN3 = ANSI/LFN
Directories that have long file names or that may have extended characters in their names may have multiple LDIDs. For example, 28700 and 28701 both point to "Program Files", but 28700 corresponds to the short file name "Progra~1" while 28701 corresponds to the long file name. Likewise, 28700 and 28702 both point to the short name "Progra~1", but 28700 renders this name in the OEM character set whereas 28702 renders it in ANSI characters. Different LDIDs are appropriate for different uses. In general, OEM/SFN LDIDs are uses for file copying, ANSI/LFN are used for strings written to the registry, and ANSI/SFN are used for Setup.ini entries that create start menu shortcuts.
The flag values at the end of the VarLDID.LFN and VarLDID.SFN sections show how the directories are represented internally as strings. The flag values have the following meanings:
0 = OEM/SFN (Default)1 = ANSI/SFN2 = OEM/LFN3 = ANSI/LFN
Anyhow, good luck. And be sure to let us lazy leeches know when you're done.
Share this topic:
Page 1 of 1



Help
Back to top









