Extension inf. What is .inf and how to fix it

I came across this problem. They brought a computer to reinstall the operating system; it used to have Windows XP (the computer was old), and it refused to boot in any of the available modes. But it seemed like nonsense, one problem was that the user needed to save his data. To save existing files, I found a fairly simple method. Fortunately, I had a flash drive with the Linux Mint distribution (it just came to my aid), I booted from it and connected an external USB HDD and transferred all user data. It was even easier to save the data by removing the hard drive and installing it in a work computer and transferring the data. I didn't want to disassemble my home computer, so I used a bootable USB flash drive. It turns out these were still flowers compared to what awaited me next.

And so on in order.

Using the Rufus utility, I prepared a bootable USB flash drive with the Windows XP operating system, but the computer refused to boot from it and did not recognize that it was bootable. Everything was set correctly in the BIOS, because... Before that, I already booted from a flash drive under Linux. Okay, I downloaded the UltraISO program, prepared a flash drive using it, but now the fun began. The computer saw that it was bootable, but the following error came out: “ inf file txtsetup.sif is corrupted or missing, status 18. Installation cannot continue. Press any key to exit ».

I thought it was all about the USB drive, I used a 64 GB flash drive. Although I loaded the Linux paradox, it was from a 64 GB flash drive that everything was fine, which means the system can work with large drives. Well, who knows, I repeat the same procedure with a 32 GB flash drive, the result is the same. The turn came for the 8 GB flash drive and again the same result. Then I decided to search the Internet and found a site describing a similar error.

There was some banal advice (quote from the site): “ I went online and quickly found information that to solve this error, you need to put the “txtsetup.sif” file from the “I386” folder into the root of the flash drive that we created. And rename the “I386” folder, which is located on the flash drive, to $WIN_NT$.~BT.”

It seems like nothing is simple, I decided to do it. But that was not the case, and the installation seemed to work until some time, but then there was another error. " Could not find CD drive" Although on the site’s forum all users, in response to this advice, shouted “ Hooray! Everything helped", but apparently not in my case.

And again a fiasco. The advice didn't help.

I started experimenting with programs that can help prepare bootable usb carrier. And miracle, I came across interesting program, here is her website: http://www.winsetupfromusb.com/. The program is free, you can download it by clicking on the “Download” tab.

You don’t even need to install it on your computer, just unpack the archive. There are two versions for 32 and 64 bit operating systems.

The program has a clear interface (albeit in English), which is not difficult to figure out on your own.

The first field indicates USB drive where you need to install the operating system image, then, so as not to bother, select the checkbox automatic detection format. There is one thing here, the program does not work with ISO images, the image must be unpacked into a separate directory and indicated in the field below. That’s all “GO”, we wait for the end of the copying procedure and USB creation media with the operating system.

It was only after such manipulations that I managed to avoid the error described above and successfully install operating system Windows XP.

Not such a common situation, but when servicing a large fleet user computers sometimes it happens that for some device the manufacturer has not released drivers for the required version OS. It could be old version OS, or old device. All in all. Sometimes you need to install drivers manually. They are usually supplied in the form of several files. Most often they have the extension inf or sys, but they can also be different.

The procedure for installing a driver in Windows 10 depends on how you install it. Each method has its pros and cons. The most important advantage is that any user, from a beginner to a master, can choose the most convenient one for himself, avoiding system errors and the departure of programs in the future. We will look at each method in detail separately. Remember that the most important thing is to use drivers from reliable sources, so as not to damage the operating system and accidentally launch a virus, eliminating which will take much more time and effort than installing any driver.

What you need to install the driver

In order to install the driver manually, you need an installation disk or special software that will help you step by step through the entire installation procedure. Below we will look at one of these programs - Driver Easy. There are situations when, due to incompatibility, the driver from the installation disk generates an error. It is in such cases that we need programs that will help us find and update the driver. In addition, this option will be more acceptable for owners of netbooks, which often do not have a disk drive. For such cases there is an installation option required driver from a USB drive, we will also analyze it today, since this method has its own characteristics.

Manual installation - instructions

Installing the driver manually using Device Manager

1. Open the Windows 10 Control Panel by pressing the Win + X key ( Windows key and the X key) and left-click on the “Control Panel” item

2. For convenience, it is advisable to set up small icons.

3. Click on “Device Manager”.

In the Device Manager window, expand the categories and find the device you need. Then click right click mouse over the device name and select Update Driver Software. The photo shows an example of installing the Realtek PCIe GBE Family Controller network adapter driver.

Installing the driver manually using Driver Easy

1. In the main window of the Driver Easy program, click on the driver of the device that needs to be updated. After this, you will see the standard task manager window, which was described above. Select the device to update.

2. You will see two options in the pop-up window. Click Browse My Computer to install the driver software.

3. Click Browse to locate the downloaded driver file.

Click the Down Triangle button in Driver Easy, then select Open File Location to open the driver folder.

For convenience, you can copy and paste the location of the downloaded files into the field.

The path to the file:

As you already understood, the update takes a lot of time and requires basic knowledge of working with personal computer. In addition to updating manually, Driver Easy can automatically search, download and install all drivers that need updating. But, as we already said, this is not safe, since this function works in automatic mode, and in this case it is impossible to make a backup copy in case of a serious failure.

Installing the driver from a CD or DVD

Almost all computer and hardware manufacturers provide a set of drivers for various hardware devices. For example, the driver CD that comes with your printer contains drivers for many different printers, not just the one you purchased. When installing drivers, make sure that you are installing drivers for your printer model and not for another one. Also, make sure that you are installing it for the version of Windows that is installed on your computer. The process of installing a driver from a CD is no different from standard process installation of any other program. Be sure to follow all instructions in the installer the first time you run it. In some cases, you need to remove the old driver before installing the new one.

If you have a driver CD but your computer doesn't have a drive or it doesn't work, you can also load the drivers from a USB drive.

Installing drivers from a USB drive

After copying the drivers to a USB drive, you can install the necessary software on your computer. Make sure the drive is connected to your computer, open Windows Explorer and find your device name in it. For example, if you have a USB drive that is assigned to the E: drive when connected, then you need to click on the icon named E: in order for the contents to open.

Once the drivers are found on the disk, you must determine exactly how they will be installed on your computer. If the directory contains executable files or installation file (extension *.exe), then you can install the driver using this file. If the drivers are compressed into a ZIP file, you will need to extract the file using archivers such as 7-Zip and WinZip.

Installing inf file

If the above recommendations did not help you, then all instructions for installing drivers and hardware devices are always contained in a file with the .inf extension, which is located in the C: Windowsinf folder. The folder containing the information files is protected and hidden. To make it appear, in the folder view settings, check the “Hidden items” checkbox. To find the information file for the device you need, follow these instructions:

Open Device Manager;

Right-click on the selected device and select “Properties” from the menu

After that, go to the “Details” tab. Expand the list and select “INF Name”. The file name will be displayed in the "Value" field.

Once you know the file name, return to the Task Manager, select the device, click "Update Driver" and specify the path to the *.inf file (in in this example it will be C:Windowsinfoem3.inf)

Creating Registry Items
Defining initialization parameters (INI-settings)
Copying files from the distribution and placing them on the system
Device installation
Managing other INF files
Configuring Device Options

INF files are initialization files that configure
device or application on your system and set its entries in the registry.
INF files are usually supplied by the product manufacturer with the device
or application. In addition, you can find them on electronic bulletin boards.
tions and other on-line services. You will need INF files for many common
(not PnP) devices that you will need to configure to work with
Windows 95. INF files typically include a list of valid logical
configurations, device driver file names, etc. In some cases, you
you will need to write INF files for devices or software yourself
nia. The format of lNF files is similar to the format of INI files that were used
in Windows Z.x, including square brackets, keys and sections used by
Windows 95 only.

INF file structure
When you install a new device. Windows looks for INF files for this
device using the device ID. Having collected
from the INF file all the necessary information, the system creates an element in the registry
for this device under the key HKEY_LOCAL_MACHINE. Values ​​from INF file
are copied to the registry element corresponding to the device driver. Such
values ​​like DevLoader= and Driverdesc= are included in the hardware element
Driver=. The Enum element contains the values ​​Driver= and ConfigFlags=.
INF files are ASCII files consisting of several
sections. Each section is designed to perform a specific task.
Section names are usually enclosed in square brackets. Typical elements
represent a key and a value connected by an equal sign. To section
you can include one or more values. In addition, the element
You can include comments by separating them with a semicolon, for example:

keyname=value ;this part of the line is a comment

Since INF files are ASCII files, there must be
the manner in which they will provide information to the registry in
binary format. The INF structure defines binary file, which transforms
Converts ASCII text into binary format when read by the registry.

Types information files:
Layout. Defines disk and version information, as well as
contains a list of all files indicating the disk on which they are located -
Xia.
Selective Install. Defines parts of the installation
lations that are optional components, as well as those parts that
Some depend on the installation of other components. For example, Microsoft Fax is
will be preliminary Microsoft downloads Exchange. You have the opportunity to up-
Manage the installation of components of these types.
Application/Installation, APPS.INF (Applications/Installation). Discovering-
Removes the MS-DOS applications you use and sets options for them
environment. These lNF files contain settings and parameters for many applications.
niy DOS. Typically, this is the largest information file on your system.
meh. It includes many types of memory settings, advanced settings
memory (XMS), as well as other parameters that were contained in Windows Z.x
PIF settings
Device Installation and Configuration
devices). This is the most general of all the information files on which we
Until now we have concentrated all our attention. These files describe the parameters on-
construction sites for specific physical devices. If you have a device driver
stva earlier versions, the INF file will contain information about this device.
swarm. Plug and Play devices, on the other hand, place information about
directly to your registry.

General lNF file organization
Each device section in the INF files consists of the following sections:

Chapter .
Identifies the INF and class of the supported device.
Below is a list of some of the devices you can enable:

adapter keyboard NetService

CDROM MCADevices NetTrans (network transports)
diskdrive media nodriver
dispaly modem PCMCIA
EISADevices monitor ports
Fdc mouse printer
Hdc MTD SCSIAdapter

Chapter .
Identifies the device manufacturer (e.g. Link, Micro, etc.) and
corresponding products. Each INF file must have at least
one section [Manufacturer].

Chapter .
Contains information about the physical attributes of the device and its drivers.

Chapter .
This section is optional. He identifies new class for the specified installation
swarms in the INF file

Chapter .
Identifies localized strings in an INF file

Chapter .
Contains information about how devices are controlled by user information.
interface W95.

APPS.INF elements
In the APPS.INF file section you will find the items listed in
table Using these elements you can quickly transfer settings to W95
PIF from your old ones Windows installations.
Many of the applications listed in the APPS.INF file are
old games for MS-DOS. If you encounter the game not working in
W95 environment, view this file. You may be able to modify some
any of its elements in such a way that the game starts or becomes
work better. If you are making changes to the APPS.INF file, you will need
Reboot W95 so that the changes made are added to the registry. In addition to editing
editing the APPS.INF file, you can change some of the parameters by
By opening the properties page of a specific application.
Below is an example of an [appname] section:

LowMem=440
EMSMen=None
XMSMem=None
Enable=lml
Disable=win,hma

In this part of the APPS.INF file, the section is replaced by the name of the executable
module, for example, PRODIGY.EXE, PARADOX.EXE, etc.

Registry Item Name Key Description Value

ALLOWSSAVER Allows the sav splash screen to appear
(works in REALMODE) with DOS programs running.
Default setting

ALTENTER Allows you to use the keyboard
combination + to switch
The difference between full screen and windowed
modes. Default setting.

ALTESC Allows output using Aes
keyboard shortcut -.
Default setting.

ALTPRTSCRN Allows you to take a Psc snapshot
screen using a keyboard shortcut
+. Default setting.

ALTSPACE Allows the use of keyboard aps
combination + to display
system menu. Default setting.

ALTTAB Allows you to use the keyboard
combination for switching between applications
niyami. Default setting.

BACKGROUND Instructs the application to run in win
background. Default setting.

CDROM Allows the use of the MSCDEX driver. cdr

CLOSEONEXIT Closes the DOS window upon exit. He is cwe
This is the default setting.

CRTLESC Allows you to close an application by pressing ces
keyboard shortcut +.
Default setting.

DETECTIDLE Sets the sensitivity in the inactive com- dit
languor. Default setting.

DISKLOCK Allows direct access to dsk
(works in REALMODE) disk.

EMS Enables EMS386 for DOS programs. ems
(works in REALMODE) Default setting.

EMSLOCKED Indicates EMS memory is locked eml

EMULATEROM Indicates the need to use emt
for fast ROM emulation. Settings
default.

EXCLUSIVE Works in exclusive mode. This exc
the parameter is ignored.

FASTPASTE Activates fast paste from the application.
marriage. Default setting.

GLOBALMEM Enables gmp global memory protection

LOWLOCKED Indicates that lml memory is low
(up to 640 KB) is blocked. This option
ignored.

MOUSE Activates mouse functions. Configuration via mse
(works in REALMODE) by default.

NETWORK Allows a DOS program to access net
(works in REALMODE) to network drives and printers. Settings
default.

PRIVATECFG Allows a DOS program to use per- cfg
(works in REALMODE) personal file CONFIG.SYS. Is not
default setting.

REALMODE Runs the program in real mode DOS. dos
Not is the default setting.

UNIQUESETTINGS Runs DOS programs in separate DOS-uus
sessions. Not a setting
omissions.

USEHMA Instructs the use of HMA (upper hma
memory addresses). Default value.

VESA Gives DOS programs access vsa
(works in REALMODE) advanced graphic capabilities.

WINDOWED Runs the application in a window, not in win
full screen mode. Setting by
default.

WINLIE Prevents DOS programs from detecting lie
W95. Not the default option.

XMSLOCKED Instructs XMS memory to be locked. Xml

The following parameters are available but not implemented in the APPS.INF file:

DISPLAYTBAR (dtb) Displays the toolbar.
EXCLMOUSE (exm) Enables mode exclusive use mice
QUICKEDIT (qme) Activates the mouse mode quick editing
WARNIFACTIVE (wia). Allows you to issue warnings if the application
DOS is still active

Section reference
The tables below describe all the keywords and meanings associated with
ated with specific sections. The section syntax is given below:
same. Square brackets are used to indicate the start of a new section.
To make INF settings clear to W95 and the registry, square brackets
must be present.

Signature=$CHICAGO$
Class=name_of_class
Provider=%File_creator%
LayoutFile=filename.inf

Signature $Chicago$ Specifies the operating system for the INF file.
At the time of writing, most INF files
The code name for Windows 95 was:
Chicago.

Class name_of_class Indicates the class that will be defined in the re-
estre. List of common device classes that
you can enter here, given in this application-
earlier.

LayoutFile filename.inf This line specifies the name of the INF file containing
common names of the source disk and files that
must be enabled to install this
devices. If it is not defined, then by default
The file name is usually LAYOUT.INF. If you not
include this data in the Version section, then you should
will include sections in the APPS.INF file
SourceDiskName and SourceDiskFiles.

The section syntax is given below.

"manufacturer" %string_value%=manufacturer_section

Section information

Keyword Description

"manufacturer" The name of the manufacturer of this device, enclosed in
quotes. Any string can be included here. This is the key
The statement is optional.

%string_value% Specifies the name of the string included in the Stings section
INF file. Strings must be enclosed within characters
percent (%).

manufacturer_section Points to the Manufacturer Name section in the INF file.

The section includes device descriptions for the specified device
swarms The keywords used in this section are described in the table.
The syntax for this section is as follows:

description of device=install_section,ID_of_device

Section information

Keyword Description

description_of_device Description of the device to be installed.
install_section Specifies the name of the Install section for this device.
ID_of_device Identifier (ID) of the device being installed.
Contains Links to devices compatible with
data. This list can include several
devices, separated by commas.

The section can be used to specify the files you want
those copy, rename or delete. Depending on the element of the section
La you can use the following three syntax parameters:

new_filename, old_filename

This construct is used for RenFiles elements. Inclusion allowed
any number of elements new_filename, old_filename.

DelFiles elements use the following syntax:

filename

The filename parameter specifies the name of the file you want to delete.

The CopyFiles element uses the following syntax. Options
source_filename and temporary_filename are optional in this construct.
flax.

destination_filename,source_filename,temporary_filename

Below is a sample section syntax. This section includes
additional sections INF file that contains device descriptions. IN
on the right side of the expression, after the equal sign, you can specify several values
values ​​separated by commas.

LogConfig=section_name
Copyfiles=file_list_section
Renfiles=file_list_section
DelFiles=file_list_section

AddReg=AddRegitry_section
DelReg=DelRegitry_section
Ini2Reg=IniToRegistry_section
UpdateCfgSys=UpdateConfig_section
UpdateAutoBat=UpdateAutoexec_section
Reboot or Restart

Section information

Keyword Meaning Description

Contains the device name, corresponding
information provided
noah in this section. In chapter
ManufacturerName of the INF file must
please attend link to
this section

LogСonfig section_name Contains information about sections
logical configuration of the device
swarms. Section_name values
point to sections of the INF file
which contains information
tion about this device.

CopyFiles file_list_section Contains the information needed
to copy the specified file
or files to the directory specified
in the File_List section. You can
instruct the system to copy
separate file. To do this, before
file name must be included
symbol @. In this case the file will be
copied to directory
DefaultDestDir defined in
section of the DestinationDir INF file.

RenFiles fiie_list_section Allows you to rename the specified
nal file. Represents
pointer to File_List section
INF file.

DelFiles file_list_section Allows you to delete the specified
file. Represents a decree-
tel to the FileList section of the INF file.

UpdateInis UpdateIni_section_name Allows you to specify the INI value
file you want to change
thread via INF file. Representation
is a pointer to a section
Update INI.

UpdatelniFields UpdateIniFields_section_name Allows you to change, replace
or delete individual elements
INI file values ​​(as opposed to
the previous parameter, which
changed the entire meaning).
This parameter represents the
fight pointer to the Update section
IniFields.

AddReg AddRegistry_section Allows you to specify a subkey or
value that is required before
add to the registry. Is
is a pointer to the Add section
Registry.

DelReg Del_Registry_section Allows you to specify a subkey or
value that needs to be deleted
pour from the registry. Is
is a pointer to the Delete section
Registry

Ini2Reg IniToRegistry_section Moves strings and
sections from the INI file. Representation
is a pointer to a section
Ini to Registry.

UpdateCfgSys UpdateConfig_section Contains a pointer to the section
Update Config. in this section
there are teams that
must be added, removed
or renamed in the file
CONFIG.SYS.

UpdateAutoBat UpdateAutoexec_section Contains a pointer to the section
Update AutoExec. In this section
there are teams that can
modify the AUTOEXEC.BAT file.

Reboot or Restart Commands that cause a restart
system or reboot the computer
computer after completion of the program
installation grams.

Below is an example of section syntax. Chapter
must be specified in the section. This section contains
configuration information system resources, including IRQ, input/output ports
water, DMA channels, etc. For each element included, the Setup program
creates a logical configuration entry in binary format and includes this
information in the registry in the driver section. INF files can contain multiple
(or none) sections. Key words and meanings
of this section are described in the table.

ConfigPriority=value_of_priority
MemConfig=menory_range_settings
I/OConfig=ioport_settings
IRQConfig=irq_sectings
DMAConfig=dma_settings

Keyword Meaning Description

ConfigPriority value_of_priority Contains the priority value
configurations for this device -
stva.

MemConfig memory_range_settings Specifies the memory range for
of this device.

I/OConfig ioport_settings Allows you to specify for the device
I/O port configuration.

IRQConfig irq_settings Contains a LIST of valid IRQs
for this device. If
the device does not use IRQ,
should not include this
line to the INF file.

DMAConfig dma_settings Specifies valid values
DMA for this device.

For the settings listed in the table, you can specify more than one,
and several resources. However, during the installation process it will be used
Just one of the resources listed. To specify multiple resources
owls for one device, you will need to create the corresponding number
records for each resource.

Below is an example of section syntax. Section name
must be indicated in the section. This section contains
Runs commands that manipulate strings in the AUTOEXEC.BAT file. Keywords
and the meanings of this section are given in the table.

CmdDelete=command
CmdAdd=command
UnSet=environmentvariablename
PreFixPath=%ldid%
RemOldPath=%ldid%
TmpDir=%ldid%

Keyword Meaning Description

CmdDelete command Specifies the command that should be
be removed from the AUTOEXEC.BAT file.
This line is processed before
line CmdAdd.

CmdAdd command Specifies the command that is required
add to the AUTOEXEC.BAT file.

UnSet environmentvariablename Specifies the environment variable that
ru you want to remove from the file
AUTOEXEC.BAT.

PreFixPath %ldid% Allows you to enable a predefined
fixed variable path in the form
logical directory identifier
(logical directory identifier, LDID).

RemOldPath %ldid% Allows you to specify the path that should be
be removed from the AUTOEXEC.BAT file.

TmpDir %ldid% Allows you to specify a temporary directory on
installation time.

Below is an example of section syntax. Section name
must be specified in the section. This section
contains string manipulation commands in the CONFIG.SYS file. Keywords
and the meanings of this section are described in the table.

DevRename=current_name,new_name
DevDelete=driver_name
DevAddDev=driver_name,configkeyword
Stacks=dos_stack_values
Buffers=dos_buffer_values
Files=dos_buffer_values
LastDrive=dos_lastdrive_value

Keyword Meaning Description

DevRename current_name,new_name Allows you to rename drivers
devices called from a file
CONFIG.SYS. The section may contain
several lines DevRename.
DevRename entries are being processed
first before it starts
processing any other
section records.

DevDelete driver_name Allows you to specify drivers
devices that should be
removed from CONFIG.SYS file.
A section may contain several
DevDelete records.

DevAddDev driver_name,configkeyword Allows you to specify new driver,
which should be added to
CONFIG.SYS file. Section may
contain multiple entries
DevAddDev.

Stacks dos_stack_values ​​Specifies the Stacks= value in
CONFIG.SYS file.

Buffers dos_buffer_values ​​Specifies the Buffers= value in
CONFIG.SYS file.

Files dos_file_values ​​Specifies the Files= value in
CONFIG.SYS file.

LastDrive dos_lastdrive_value Specifies the value of lastdrive=
in the CONFIG.SYS file.

Below is an example of section syntax. Chapter
must be specified in the section with the UpdateINIs entry. This
section adds, deletes, or replaces entries in the specified INI file.
The keywords and meanings for this section are described in the table.

ini-file,ini-section,original_entry,new_entry,options

Value Description

options Optional operation flags that can accept
one of the following values

0 Default value. Looks for key (record name)
original_entry, ignoring its value. If the key is
is present, the corresponding entry is replaced by
new_entry. If original_entry is NULL, new_entry
definitely added. If new_entry is NULL,
original_entry is removed.

1 Searches for an original_entry entry by key and value. Update
The division is carried out only if the
the key and value of the original_entry entry.

2 Searches for a record whose key matches the one specified in
original entry. If the entry already exists, it is not saved.
is placed with the value you specified in new_entry.

3 Searches for an entry whose key and value match the
specified in original_entry. If such a record exists,
it is replaced by new_entry.

Below is the syntactic construction of the section.
The section name must be specified by the element
. Affirmations of this replace,
add or remove fields in the specified INI file entry. Unlike
section, the commands from this section work from the fragment-
mi records, and not with records as a whole.

ini-file,ini-section,profile_name,old_field,new_field

If there was a comment in the INI file line for the specified entry,
it is removed. The modifiers old_field and new_field are optional
telny.

The section allows you to add keys and values ​​to the registry.
In addition, there is an optional possibility to establish the actual
Russian meaning. The section name must be specified
section's AddReg element. The section syntax looks like this:
in a general way:

reg_root_string

In this section you can include subkeys, value names and
(optional) the values ​​themselves.

The section is used to remove connections from the registry.
chen and value names. The syntax for this section is as follows:
zom:

reg_root_string,subkey

The name of this section must be specified by the DelReg element in the section
. Each item included in this section will be removed from the registry
subkey or value.

The section allows you to move strings and sections to the registry
ly from the INI file. This operation either creates a new entry in the registry, or
subkey or value.

The section name must be specified by the element
lni2Reg in section .

Chapter . The section name link should
be present in one of the following three section elements:
DelFiles, CopyFiles or RenFiles. The section syntax is given below.

More detailed information can be found in the table.

file_list=ldid,subdirectory
DefaultDestDir=ldid,subdirectory

Keyword Meaning Description

file_list ldid,subdirectory Specifies the FileList section name.

Subdirectory Specifies the directory located
in the ldid directory. This is the meaning
not necessary.

Ldid Specifies a logical identifier
disk. List of valid values
ldid is given below.

DefaulDestDir Allows you to specify the destination directory
default for all unmentioned
File_List sections. This option
is optional. By default
The W95 uses the directory
LDID_WIN.

Chapter
name_of_source_disk=disk_number

The disk_number element is defined in the section that
ry uses the following syntax:

disk_ordinal=description_of_disk,label,serial_number

Section sets a new device class in the section
registry The section syntax is given below.
Detailed information about the values ​​and elements that are used in
this section can be found in the table above.

CopyFiles=fils_list_section
RenFiles=fils_list_section
DelFiles=fils_list_section
UpdateInis=UpdateIni_section_name
UpdateIniFields=UpdateIniFields_section_name
AddReg=AddRegistry_section
DelReg=DelRegistry_section

Finally, the last section of the INF file is the . This
section defines one or more string keys. The syntax for this is
section is given below.

string_key="valve"

The keyword string_key denotes the string key generated
from alphanumeric characters, for example, MfgName. Although section
usually last in the INF file, string keys
can be used wherever strings are acceptable.
The Setup program replaces the string key with the string specified
element "value" and further uses it, for example:
MSFT="Microsoft"
By typing the MSFT line. Most Setup interprets it as Microsoft

LDID values
The table lists the valid LDID (logical disk identifier) ​​values,
which you can use in INF files.

ID Indicates

00 Empty LDID; used to create a new LDID
01 Source device:\path
02 Temporary directory Setup; used only during the process
W95 installations
03 Uninstall directory
04 Backup catalog
10 Windows Directory
11 Catalog SYSTEM
12 Catalog lOsubsys
13 COMMAND Catalog
14 Catalog Control Panel
15 Printers Catalog
16 Workgroup Catalog
17 Catalog INF
18 Catalog Help
19 Directory Administration
20 Fonts Catalog
21 Viewers Directory
22 Catalog VMM32
23 Color Catalog
25 Shared Catalog
26 Winboot directory
27 Machine-specific directory
28 Winboot Host Directory
30 Root directory boot device
31 Root directory of the virtual boot device host disk
32 Directory with the previous version of Windows (if any)
33 Catalog from previous MS-DOS version(if any)DB

Many MS Windows users have long noticed that the standard notepad is a rather inconvenient program to use. This free text file editor, which provides syntax support for a large number of programming languages, can replace it. The program contains a fairly wide range of options and is characterized by minimal consumption of processor resources. The program makes it possible to simultaneously view several documents at once and edit them, without closing unnecessary windows. An option has also become available: editing the same document in different places, which is very convenient...

AkelPad is a small but convenient and fast text editor. The program works with text documents in single or multi-window mode, fully supports Unicode strings on Windows systems, as well as Unicode code pages. Using AkelPad, you can even edit files that have a Read-Only attribute, as well as preview them before opening them. Other features of the editor include a multi-level rollback system, a list of recently opened documents in the program, memory of the code page for a file, as well as the position of the insertion mark and the last search/replace line. Supports d...

Notepad2 is a simple application that allows you to type and edit text. It will help in creating HTML pages, programming in various languages ​​(CSS, Java, JavaScript, Python, SQL, Perl, PHP) as it can highlight code. The program is built on the principle of a simple notepad; it is lightweight and compact. This text editor checks all parentheses for pairs and supports auto-indentation. Notepad2 not only supports ASCII encodings and UTF-8, but also knows how to convert them. Allows you to roll back unwanted operations many levels back. Supports block selection of text elements and has numbered...

PSPad is a very useful code editor suitable for coders who write in multiple languages. Suitable for those who need program code highlighting. Can easily replace popular tools. The PSPad will prove its worth when working with complex code syntax. It was created to help all types of users. The program comes with an impressive list of templates. There are features like syntax highlighting, macro recording, or search and replace functionality that are common to similar applications. It comes with a HEX editor, FTP client, so the user can edit the code directly...

There are a lot of programs on the Internet that allow you to edit source another program, file, etc. However, most of these programs are just a text editor like Notepad. They differ from the above editor only in that they have syntax highlighting. However, in some cases, this program functionality is not enough. A programmer may need to quickly find different parts of a document. And now, finally, a program has appeared that allows you to solve this problem. The program is called SynWrite. Its distinctive feature is the presence navigation bar with a tree that...

The error “INF file txtsetup.sif is corrupted or missing” is mainly encountered only by those users who are trying to install Windows version XP from a removable USB device (flash drive). However, this problem is typical only for those cases when the UltraISO program was used to write the installation distribution onto the media. Next we will show you how to get around this glitch in several simple ways. But first, it’s worth understanding the essence of the issue.

INF file txtsetup.sif is corrupted or missing (status 18): What is the problem?

As it turns out, the whole trick lies precisely in the program used to transfer the distribution from the original disk or its copy saved on the hard drive to an external USB drive.

The UltraISO application, although it is not advertised, has a number of limitations in this regard. Either the program itself considers the XP modification obsolete or irrelevant, or something else. But the most interesting thing is that images of Windows 7 and higher systems recorded using this utility do not cause problems, and the error “INF file txtsetup.sif is corrupted or missing” never appears. To correct the situation, we can offer several simple techniques.

The INF file txtsetup.sif is corrupted or missing: what to do in the simplest case?

As is already clear, the first thing that comes to mind is to stop using the UltraISO program to create the image.

But if, for some reason, the user does not have another utility, you can use it, although you will have to dig a little into the installation distribution itself (if you want everything to work).

Actions with installation folders

First of all, you should copy the original txtsetup.sif object from the i386 directory of the main distribution directory to the root of the USB drive. Naturally, the source should be the original DVD or downloaded from official resource system image. In no case is it recommended to perform such actions in terms of images or distributions, in general case called Re-Pack. The effect may not be achieved (sometimes you can even get the opposite effect, when the installation becomes impossible at all).

After this, to avoid the error “INF file txtsetup.sif is corrupted or missing,” you need to rename the desired directory, giving it the name $WIN_NT$.~BT, and then repeat the installation. Many, however, consider this technique to be too primitive and not give the desired effect.

What to do if the USB drive is not detected?

Sometimes the problem with the error “INF file txtsetup.sif is corrupted or missing” may also be due to the fact that there seems to be a USB drive in the system, but it fails at the initial boot stage.

If you install the system from a flash drive, even the presence of installed drivers does not guarantee that it will be possible to boot from it, although normal mode The device is detected without problems.

The media must be inserted into the appropriate port before turning on the desktop computer or laptop, and only then set boot priorities in the BIOS settings (usually the Boot section). If this does not help, you will have to completely reinstall the device drivers, even if the system boots normally this device recognizes.

Creating bootable media: some nuances

However, since the problem is precisely UltraISO, which is why the error “INF file txtsetup.sif is corrupted or missing” appears, you should use programs like Win SetupFromUsb or WinToFlash.

Both programs are quite simple, but it is better to use the second utility. The fact is that it does not require the use of an image, but is capable of adding files and folders directly when recording. To do this, simply launch the Transfer Wizard and follow its instructions. In process boot distribution you will only need to specify the path to the full directory with the installation files and wait until the writing process to the media is completed.

During installation, the system will display a window with several lines, but at the first start you need to select item 1 with the active line 1-st text mode setup (Debug boot rDisk 1 indicating partition 2). If in the future you receive an error regarding the HAL.dll library, the installation must be repeated, but select the fourth item from the menu (rDisk2 with partition 1).

When the XP installation is complete, you will need to open the boot.ini file in any text editor and add it in a line containing the parameters “partition(1)=\Windows” indicating current version, through the right slash (/) with the command noexecute and further, as shown in the image above.

By the way, errors related to the HAL component can also appear on a production system. Eliminating them is quite a difficult task, although you can figure it out if you want. True, in in this case, it is this library that is relevant to the main issue, so to speak, insofar as, nevertheless, the occurrence of such situations should not be discounted.

As practice shows, this method almost always works. But this only applies to official distributions. If the user has some kind of re-pack at his disposal, created by someone unknown and from what, such actions, even if desired, may not have an effect. In addition, when downloading them, no one is protected from the penetration of viruses or malicious codes into the system (they can work even during installation, infiltrating the RAM or starting along with startup processes). The cleaning process can be quite complex, and in some cases you will even have to use specific utilities like Rescue Disk, which are loaded from removable media even before the system starts and identifies threats that the average user is not even aware of.

conclusions

This is the nature of the “INF file txtsetup.sif is corrupt or missing” error. How to correct the situation, I think, is already clear. The technique of creating bootable media based on a program other than UltraISO, of course, looks somewhat complicated. However, it is possible to solve the problem in this way in 99 percent of cases out of 100. As for the UltraISO utility, its use is only advisable when creating images of other systems. Windows 10, for example, can be installed from a flash drive without problems. And the very nature of the question consists, apparently, not only in the above utility, but also in the Windows distribution XP, which cannot always be used for installation in modern computer systems based on the latest configurations, which, by the way, also apply to this software, to put it mildly, with complete disregard. If you try to install XP in its normal form, it is better to install the minimum package downloaded from the official Microsoft website, and then install additional service packs, including SP3, one by one and enable automatic updates in the system itself. At the very least, this will save the user from constantly installing a security update (and these products are designed to do just that). But in general, and this is still far from a fact, that the system will be installed in normal mode. In general, although it is believed that XP seems to be one of the simplest and least resource-demanding systems, alas, you can find so many bugs and shortcomings in it that you are simply amazed. Therefore, it remains to advise users of any level not to use such a modification (especially since it was recently announced that support for XP and Vista was officially discontinued). So, think for yourself.