Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[DestinationDirs] codes for *.inf installations

Featured Replies

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.


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
Hi appathetic loser. Never judge a book by it's title right. :)

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:

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

Anyhow, good luck. And be sure to let us lazy leeches know when you're done. :)

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.