config.sys and autoexec.bat
system
If one waits at least 10 seconds before turning the computer back on, generally, everything will reset to its normal configuration. This, of course, depends on why a "cold boot" was initiated in the first place, e.g., to recover from a "freeze" or was it a sudden shut down. In the latter instance, the "cold boot" should probably go into "safe mode".
The BIOS, having completed its functions, loads the boot code in the master boot record and transfers control to it. The master boot record code begins execution. If the boot device is a floppy disk, the process continues with step 6.The master boot code examines the master partition table. It is searching for two things. First, it must determine if there is an extended DOS partition. Second, it must determine if there is a bootable partition specified in the partition table.If the master boot code finds an extended partition on the disk, it loads the extended partition table that describes the first logical volume in the extended partition. This extended partition table is examined to see if it points to another extended partition table. If it does, then that table contains information about the second logical volume in the extended partition, so it is loaded and examined. (Recall that logical volumes in the extended partition have their extended partition table chained one to the next.) This process is continued until all of the extended partitions have been loaded and recognized by the system.After loading the extended partition information (if any), the code attempts to boot the primary partition that is marked active (bootable). If there are no partitions marked active, then the boot process will terminate with an error. The error message is often the same one that occurs if the BIOS finds no boot device, and is generally something like "No boot device", but can be the infamous "NO ROM BASIC - SYSTEM HALTED".If there is a primary partition marked active, the code will boot it. The rest of the steps assume this is a DOS primary partition.The volume boot sector is loaded into memory and tested, and the boot code that it contains is given control of the remainder of the boot process.The volume boot code examines the structures on the disk that it is booting to ensure that everything is correct and in the right place. If not, the boot process will end in an error here as well.The code searches the root directory of the device being booted for the operating system files that contain the operating system. For a system running MS-DOS these are the files "IO.SYS", "MSDOS.SYS" and "COMMAND.COM".If the operating system files are not found, the boot program will display an error message, which is usually something like "Non-system disk or disk error - Replace and press any key when ready". Some people think that this message means the system was never booted, that the BIOS examined the floppy disk for example and just rejected it because it couldn't boot it. As you can see from this description of the boot process, the volume boot code was indeed loaded and executed, and in fact it is what prints the message when it can't find the operating system files! See here for an explanation of why this distinction is so important.If the operating system files are found, the boot program will load them into memory and transfer control to them. First, IO.SYS is loaded and its code executed. IO.SYS will then executed MSDOS.SYS (in pure DOS systems, MSDOS.SYS is just a text file in Windows 95 and later.) Then the more complete operating system code loads and initializes the rest of the operating system structures. For MS-DOS, this means loading the command interpreter (COMMAND.COM) and then reading and interpreting the contents of the CONFIG.SYS and AUTOEXEC.BAT system control files.
Kind of - It tells the computer to start up the initial files to get the computer 'up and running'. These are files such as driver programs for the display, keyboard, mouse, screen, printer etc, along with disk controllers, operating system and internet access programs.
In Windows AND Mac, this is called Safe Mode, only loading up essential files. This can be used when you suspect a virus to be infecting your computer. To enable this, restart your computer and select boot options from the options displayed when the computer is booting.
System files are files necessary to boot an operating system. They do not necessarily exist on any given NTFS volume, and the choice of file system does not affect which system files are present.
you need a msdos boot able floppy or CD
Yes. Along with MSDOS.sys, they are the two hidden system files that are loaded and executed when you boot your computer. In newer operating systems, IO.sys and MSDOS .sys are combined into one hidden file.
msdos.sys , io.sys , command.com
msdos.sys io.sys command.com
The boot files are in C://Windows/system32
config.sys and autoexec.bat
Windows 98 startup disk has some useful utilities and can be used to repair Windows 98 without any additional drives. A floppy which was created by format A s, just have loader, and couple system files to be able to boot MSDOS.
A boot sector virus is a computer virus that puts itself in the boot sector of a computer. The boot sector is the partition on the disk drive that contains all of the programs and files necessary for the computer to start up. This ensures that the virus will be executed once the computer is turned on.
The volume boot sector.
A boot sector virus. Boot sector viruses place themselves in the MBR (master boot record). This is a partition on the hard disk that contains all of the programs and files necessary for the computer to boot up when it is powered on. The virus places itself here and gains control of the computer before the operating system can gain control.
You need to start Windows using a boot disk that loads basic files. Your PC should check the CD drive for necessary files before checking the hard drive. Use an original XP installation disk.