Resource File Formats

This section describes the format of the binary resource file that the resource compiler creates based on the contents of the resource-definition file. This file usually has an .res extension. The linker reformats the .res file into a resource object file and then links it to the executable file of an application.

A binary resource file consists of a number of concatenated resource entries. Each entry consists of a resource header and the data for that resource. A resource header is DWORD-aligned in the file and consists of the following:

• A DWORD that contains the size of the resource header
• A DWORD that contains the size of the resource data
• The resource type
• The resource name
• Additional resource information

The RESOURCEHEADER structure describes the format of this header. The data for the resource follows the resource header and is specific to each type of resource. Some resources also employ a resource-specific group header structure to provide information about a group of resources.

Accelerator Table Resources

An accelerator table is one resource entry in a resource file. It does not have a group header. An ACCELTABLEENTRY structure describes each entry in the accelerator table. Multiple accelerator tables are permitted.

Cursor and Icon Resources

The system handles each icon and cursor as a single file. However, these are stored in .res files and in executable files as a group of icon resources or a group of cursor resources. The file formats of icon and cursor resources are similar. In the .res file a resource group header follows all of the individual icon or cursor group components.

The format of each icon component closely resembles the format of the .ico file. Each icon image is stored in a BITMAPINFO structure followed by the color device-independent bitmap (DIB) bits of the icon’s XOR mask. The monochrome DIB bits of the icon’s AND mask follow the color DIB bits.

The format of each cursor component resembles the format of the .cur file. Each cursor image is stored in a BITMAPINFO structure followed by the monochrome DIB bits of the cursor’s XOR mask, and then by the monochrome DIB bits of the cursor’s AND mask. Note that there is a difference in the bitmaps of the two resources: Unlike icons, cursor XOR masks do not have color DIB bits. Although the bitmaps of the cursor masks are monochrome and do not have DIB headers or color tables, the bits are still in DIB format with respect to alignment and direction. Another significant difference between cursors and icons is that cursors have a hotspot and icons do not.

The group header for both icon and cursor resources consists of a NEWHEADER structure plus one or more RESDIR structures. There is one RESDIR structure for each icon or cursor. The group header contains the information an application needs to select the correct icon or cursor to display. Both the group header and the data that repeats for each icon or cursor in the group have a fixed length. This allows the application to randomly access the information.

Dialog Box Resources

A dialog box is also one resource entry in the resource file. It consists of one DLGTEMPLATE dialog box header structure plus one DLGITEMTEMPLATE structure for each control in the dialog box. The DLGTEMPLATEEX and the DLGITEMTEMPLATEEX structures describe the format of extended dialog box resources.

Font Resources

Fonts are stored in the resource file as a group of resources. Individual fonts make up a font group. A FONT Statement resource definition statement in the .RC file defines each font. Each individual font in the resource consists of the complete contents of the related .fnt file. A FONTGROUPHDR structure follows all the individual font components in the .res file.

Font resources are not added to the resources of a specific application. Instead, they are normally added to executable files that have a .fon extension. These files are usually resource-only DLLs rather than applications.

Menu Resources

A menu resource consists of a MENUHEADER structure followed by one or more NORMALMENUITEM or POPUPMENUITEM structures, one for each menu item in the menu template. The MENUEX_TEMPLATE_HEADER and the MENUEX_TEMPLATE_ITEM structures describe the format of extended menu resources.

Message Table Resources

A message table is a resource that contains formatted text for display as an error message or in a message box. The main structure in a message table resource is the MESSAGE_RESOURCE_DATA structure.

Version Resources

The main structure in a version resource is the VS_FIXEDFILEINFO structure. Additional structures include the VarFileInfo structure to store language information data, and StringFileInfo for user-defined string information. All strings in a version resource are in Unicode format. Each block of information is aligned on a DWORD boundary.

NTFS overview

Applies to: Windows 10, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008

NTFS—the primary file system for recent versions of Windows and Windows Server—provides a full set of features including security descriptors, encryption, disk quotas, and rich metadata, and can be used with Cluster Shared Volumes (CSV) to provide continuously available volumes that can be accessed simultaneously from multiple nodes of a failover cluster.

For additional feature information, see the Additional information section of this topic. To learn about the newer Resilient File System (ReFS), see Resilient File System (ReFS) overview.

Increased reliability

NTFS uses its log file and checkpoint information to restore the consistency of the file system when the computer is restarted after a system failure. After a bad-sector error, NTFS dynamically remaps the cluster that contains the bad sector, allocates a new cluster for the data, marks the original cluster as bad, and no longer uses the old cluster. For example, after a server crash, NTFS can recover data by replaying its log files.

NTFS continuously monitors and corrects transient corruption issues in the background without taking the volume offline (this feature is known as self-healing NTFS, introduced in Windows Server 2008). For larger corruption issues, the Chkdsk utility, in Windows Server 2012 and later, scans and analyzes the drive while the volume is online, limiting time offline to the time required to restore data consistency on the volume. When NTFS is used with Cluster Shared Volumes, no downtime is required. For more information, see NTFS Health and Chkdsk.

Increased security

Access Control List (ACL)-based security for files and folders—NTFS allows you to set permissions on a file or folder, specify the groups and users whose access you want to restrict or allow, and select access type.

Support for BitLocker Drive Encryption—BitLocker Drive Encryption provides additional security for critical system information and other data stored on NTFS volumes. Beginning in Windows Server 2012 R2 and Windows 8.1, BitLocker provides support for device encryption on x86 and x64-based computers with a Trusted Platform Module (TPM) that supports connected stand-by (previously available only on Windows RT devices). Device encryption helps protect data on Windows-based computers, and it helps block malicious users from accessing the system files they rely on to discover the user’s password, or from accessing a drive by physically removing it from the PC and installing it on a different one. For more information, see What’s new in BitLocker.

Support for large volumes

NTFS can support volumes as large as 8 petabytes on Windows Server 2019 and newer and Windows 10, version 1709 and newer (older versions support up to 256 TB). Supported volume sizes are affected by the cluster size and the number of clusters. With (2 32 – 1) clusters (the maximum number of clusters that NTFS supports), the following volume and file sizes are supported.

Cluster size	Largest volume and file
4 KB (default size)	16 TB
8 KB	32 TB
16 KB	64 TB
32 KB	128 TB
64 KB (earlier max)	256 TB
128 KB	512 TB
256 KB	1 PB
512 KB	2 PB
1024 KB	4 PB
2048 KB (max size)	8 PB

Note that if you try to mount a volume with a cluster size larger than the supported maximum of the version of Windows you’re using, you get the error STATUS_UNRECOGNIZED_VOLUME.

Services and apps might impose additional limits on file and volume sizes. For example, the volume size limit is 64 TB if you’re using the Previous Versions feature or a backup app that makes use of Volume Shadow Copy Service (VSS) snapshots (and you’re not using a SAN or RAID enclosure). However, you might need to use smaller volume sizes depending on your workload and the performance of your storage.

Formatting requirements for large files

To allow proper extension of large .vhdx files, there are new recommendations for formatting volumes. When formatting volumes that will be used with Data Deduplication or will host very large files, such as .vhdx files larger than 1 TB, use the Format-Volume cmdlet in Windows PowerShell with the following parameters.

Parameter	Description
-AllocationUnitSize 64KB	Sets a 64 KB NTFS allocation unit size.
-UseLargeFRS	Enables support for large file record segments (FRS). This is needed to increase the number of extents allowed per file on the volume. For large FRS records, the limit increases from about 1.5 million extents to about 6 million extents.

For example, the following cmdlet formats drive D as an NTFS volume, with FRS enabled and an allocation unit size of 64 KB.

You also can use the format command. At a system command prompt, enter the following command, where /L formats a large FRS volume and /A:64k sets a 64 KB allocation unit size:

Maximum file name and path

NTFS supports long file names and extended-length paths, with the following maximum values:

Support for long file names, with backward compatibility—NTFS allows long file names, storing an 8.3 alias on disk (in Unicode) to provide compatibility with file systems that impose an 8.3 limit on file names and extensions. If needed (for performance reasons), you can selectively disable 8.3 aliasing on individual NTFS volumes in Windows Server 2008 R2, Windows 8, and more recent versions of the Windows operating system. In Windows Server 2008 R2 and later systems, short names are disabled by default when a volume is formatted using the operating system. For application compatibility, short names still are enabled on the system volume.

Support for extended-length paths—Many Windows API functions have Unicode versions that allow an extended-length path of approximately 32,767 characters—beyond the 260-character path limit defined by the MAX_PATH setting. For detailed file name and path format requirements, and guidance for implementing extended-length paths, see Naming Files, Paths, and Namespaces.

Clustered storage—When used in failover clusters, NTFS supports continuously available volumes that can be accessed by multiple cluster nodes simultaneously when used in conjunction with the Cluster Shared Volumes (CSV) file system. For more information, see Use Cluster Shared Volumes in a Failover Cluster.

Flexible allocation of capacity

If the space on a volume is limited, NTFS provides the following ways to work with the storage capacity of a server:

• Use disk quotas to track and control disk space usage on NTFS volumes for individual users.
• Use file system compression to maximize the amount of data that can be stored.
• Increase the size of an NTFS volume by adding unallocated space from the same disk or from a different disk.
• Mount a volume at any empty folder on a local NTFS volume if you run out of drive letters or need to create additional space that is accessible from an existing folder.

Формат файла .SERVICE

Как открыть файл .SERVICE?

Если файл .SERVICE известен Вашей системе, то открыть его можно двойным нажатием мышкой или клавишей ENTER. Эта операция запустит ассоциируемые с файлом .SERVICE аппликации, установленные в системе. Если система встречает файл впервые и отсутствуют соответствующие ассоциации, то акция закончится предложением системы, найти соответствующее программное обеспечение в компьютере либо сети интернет.

Иногда случается, что для обслуживания типа файлов .SERVICE приписана неправильная программа. Это случается в следствии действия враждебных программ, таких как вирусы или вредоносные программы, но чаще всего это результат ошибочного совмещения аппликации с расширением файла .SERVICE. Если во время обслуживания нового типа файлов .SERVICE мы укажем системе неправильную программу, то система ошибочно будет рекомендовать ее использование всякий раз, когда будет встречаться файл этого типа. В таком случае следует попробовать повторно выбрать соответствующую аппликацию. Нажмите правой кнопкой мышки на файл .SERVICE, а затем выберите из меню опцию «Открыть с помощью. » затем «Выбрать программу по умолчанию» . Сейчас выберите одну из установленных аппликаций из вышеуказанного списка и попробуйте снова.

Ручное редактирование Реестра Windows

Если наша система не справляется с расширением .SERVICE и подвели все автоматические и полуавтоматические методы обучения его этому искусству, остается ручное редактирование реестра Windows. Этот реестр хранит всю информацию, касающуюся рабоы нашей операционной системы, в том числе соединения расширений файлов с программами для их обслуживания. Команда REGEDIT вписанная в окне „поиск программ и файлов” или „запустить в случае старших версий операционной системы, предоставляет нам доступ к реестру нашей операционной системы. Все операции, проведенные в реестре (даже не очень сложные, касающееся расширения файла .SERVICE) имеют значительное влияние на работу нашей системы, поэтому прежде чем проводить какие-либо модификации следует убедится, что сделана копия актуального реестра. Интересующий нас раздел — это ключ HKEY_CLASSES_ROOT. Следующая инструкция показывает, шаг за шагом, как модифицировать реестр, а конкретно запись в реестре, содержащую информацию о файле .SERVICE.