about ChicagoMode

NTFSD
1

Hi, all.
What does ‘ChicagoMode’ in fastfat source code mean?

Thanks in adv.

Alex.

2

I don’t have the source in front of me (so this is just a guess) but I suspect it has something to do with Win95 support. “Chicago” was the internal project name for Windows 95.

3

Not my thing, but I would guess that it has to due to with lfn handling in a way that was compatible with downlevel (dos) systems.

mm

4

Chicago mode related to specific behaviors of FAT on Windows 95 systems (such as the generation of short names, another special case that I recall.)

Tony
OSR

5

>

Thanks, guys.

I found this sippet in fastfat source code:

#define COMPATIBILITY_MODE_KEY_NAME
L"\Registry\Machine\System\CurrentControlSet\Control\FileSystem"
#define COMPATIBILITY_MODE_VALUE_NAME L"Win31FileSystem"

//
// Read the registry to determine if we are in ChicagoMode.
//

ValueName.Buffer = COMPATIBILITY_MODE_VALUE_NAME;
ValueName.Length = sizeof(COMPATIBILITY_MODE_VALUE_NAME) -
sizeof(WCHAR);
ValueName.MaximumLength = sizeof(COMPATIBILITY_MODE_VALUE_NAME);

Status = FatGetCompatibilityModeValue( &ValueName, &Value );

if (NT_SUCCESS(Status) && FlagOn(Value, 1)) {

FatData.ChicagoMode = FALSE;

} else {

FatData.ChicagoMode = TRUE;
}

In windows 2003 and windows7, this key value is zero.

Thanks! :slight_smile:

Alex.

6

Long filenames support?

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntfsd…
> Hi, all.
> What does ‘ChicagoMode’ in fastfat source code mean?
>
> Thanks in adv.
>
> Alex.
>