Initialization and recovery of Windows XP - Windows 98 - Windows 95 - MS-Dos
Introduction:
In this paper I address an issue that could be quite useful for people who frequently for various reasons are subject to failures at the start of your operating system.
In most cases, people with no knowledge in computer not sure why the failure is caused much less how to fix , you end up being so many times, doing a reinstall of so that while sometimes used to terminate the step and assures you the solution of the problem is not the purpose of this article, but rather understand why error.
then try to see where we could ahorranos this process, not just for the sake of saving time but as mentioned a little understand the operation of boot errors in Windows .
Let's focus on the recovery of the family of Windows XP operating system, 98 and 95, also will make a brief theoretical basis of MS-Dos.
Stage
boot MS-DOS operating system:
To locate the exact point where the OS takes control of the PC, briefly explain the steps that are initialized until the SO takes control of the machine .
turn on the computer the first thing that runs is the POST (Power On Self Test ) , the Post is responsible for carrying out the checking of vital hardware components of the PC, then BIOS (Basic Input Output Sistem ) access the MBR (Master Boot Record ) where MBP (Master Boot Program ) runs and reads the MBT (Master Boot Table ) looking for a primary partition and active.
Once this information is directed the first sector of the partition, called BOOT SECTOR where you load the program manager to locate the boot files on the operating system. These are IO.SYS, MSDOS.SYS and EL latter called the command interpreter called COMMAND.COM.
There are also two basic configuration files are loaded at startup these are called by command.com automatically when its load: The CONFIG.SYS and AUTOEXEC.BAT
Troubleshooting the Operating System boot:
To
to determine a problem while loading an operating system first we must ensure that system files were successfully loaded
Once these passed the test, only then could begin the task of verifying the configuration files . In the first instance if the problem is one of the configuration files (config.sys autoexec.bat) have two function keys F5 and F8, to be pressed just before receiving the message "Starting MS-Dos" that allow us to:
F5: Avoid load CONFIG.SYS and AUTOEXEC.BAT. In this way the device drivers are not loaded and not executed command lines.
F8: You can step through each of the lines of the files mentioned above.
When the function is executed F8 key, what happens is that c ada written line in the autoexec.bat and config.sys files are executed line by line before this should respond with a Yes or No to complete and accomplish the same task with
These two functions are very useful in detecting problems during the loading phase of an operating system because it allows us to omit all or part of configuration files avoiding the burden on drivers hardware and command execution.
Let's take an example: Suppose you have trouble booting the operating system on our PC, we then reboot and press the F5 key just before receiving the message "Starting MS-Dos", so, as already explained, the operating system is loaded without the inclusion of config.sys and autoexec.bat files.
This has two possible outcomes:
successful load
If this happens then you should conclude by showing the prompt on the screen, ie C: \\
Thus, we know which houses the fault, and we are ready to begin the ...
Remedial action:
It consists of restarting the machine and this time instead of using the F5 key (which helps us to determine where was the problem) we will with the F8
anger The system now asking for a confirmation step by step execution of each line in the config.sys in the first instance and then the autoexec.bat.
Because we do this? Simple, with the above procedure only thing we know is that the fault lies in both or any of the files config.sys and autoexec.bat but still we need to know where these command line error occurs.
Knowing that by omitting these files we load successful, certainly when loading step, and answered affirmatively each of the questions, get to a point where the system hangs. This is where we must take note of what sentence caused the failure and that file is. We will
now restart the computer again, this time by pressing the F5 key to make a clean start, and then using the DOS text editor (EDIT) to open the file that we had determined that the line had defective or command that caused the error, assuming this was the CONFIG.SYS file, the command would be "Edit config.sys
Once inside the same would be sufficient to add" REM "in front on the faulty line. The command "REM" prevents the command line is charged, but in turn enables us at any time to return the situation to its previous state . If we are sure that line is not useful for anything, we can safely proceed to delete it.
If the situation does not change
If after pressing F5, the system continues in the same conditions, ie we do not get the prompt. In this case the problem will surely be in the system files and not the configuration. Let's review who were ...
io.sys
msdos.sys
command.com
The way to repair these files is:
boot with a floppy disk containing the same operating system version, and by typing "SYS" to transfer the same to the hard drive.
The command would Sys c: (or the drive where you want to transfer the system files.)
To perform this task without risk should take into account the following documents:
Make backup of the files mentioned.
Use exactly the same operating system version.
Evolution of configuration files from DOS to Windows:
S i start well in any Windows 9x (This abbreviation includes Windows 95/98/98SE/ME) still present system files mentioned above ( Io.sys - MSDOS. sys - Command.com - Config.sys - Autoexec.bat ) the same functionality has changed, and on the other side have been adding new configuration files .
In Windows9x joined the existing files for DOS, two new files that let you manage all software and hardware parameters that the system must handle, these are the Win.ini and System.ini
Since the advent of Windows 9x file Msdos.sys change its functionality, now is a text file, meaning it can be edited, its function is the configuration of basic parameters such as boot the location of the Windows folder, or loaded at boot time or not graphical interface.
So far we have seen how to solve specific problems load DOS operating system using the function keys F5 and F8, now see the tools that Windows offers.
Detection startup problems in Windows operating system:
In Windows 9x, the functions of the two keys used in DOS are summarized in a single, F8 key, which adds other features, the pressed we will find a menu similar to this
1. It gives us the opportunity to continue with the normal load of the system, so as if the interruption to the process had never been performed.
2. With this option the system boots normally, but creating a file (bootlog.txt) in the root directory, which brings us one by one all the modules loaded by the system.
3. Start using this mode, the system starts with a minimum configuration, avoiding the burden of external drivers, using a standard video mode with 16 colors. When starting the system in this way we can solve problems such as those we have to install new drivers or programs, and as a consequence, the system will not boot.
4. It's a way similar to that obtained in DOS by pressing F8
5 - In this way then boot the machine without the graphical interface, ie the DOS version of Windows itself that we are using
6 - is similar to the previous mode but prevents the loading of the config.sys and autoexec.bat
error messages when loading Windows XP:
When something failure during startup system, different messages will appear depending on the stage it occurs the same .
Recall that during the initialization and POST messages correspond to the BIOS. Since this time we look at the operating system-specific messages, we description from the time the program takes over the boot record .
know the system error messages, and its origin, will help us locate the problem quickly.
There are two models for Windows XP boot record: those installed the system to access NTFS partitions, and another to access FAT partitions. The error messages vary depending on to one system or another.
If the boot record is for FAT and charging an error reading the disc, the message is for the following
And to NTFS as follows:
If the disc does not have reading problems, the program tries to locate and load the NTLDR file. If a FAT partition, you can not find the file, the error is as follows
or the next ..
At this stage of loading the operating system, we can see short messages and sometimes confusing, for example, that show below. This is so, then remember that the loading program, tables of parameters and error messages, should fall to 512 bytes, and it is the boot sector of partition (Boot record)
that this stage in the load, and error messages are more extensive and readable. For example, the following message shows the error message generated during charging if you can not find the file NTOSKRNL.EXE
strange and confusing messages Magazines :
If the file is missing or damaged, not generate a specific error message but a strange behavior: The pc starts the load, and reboots cyclically without displaying any error message .
But even more confusing is the error that is generated (both FAT and NTFS) when the BOOT.INI file is missing. In this case the system, which has more than one primary partition, erroneously states that the error in loading Windows is because they could not locate the file hall.dll.
If the system has only one primary partition and boot.ini is missing, by default the operating system initialized looking for the path c: \\ windows.
I hope this guide on the recovery of operating system Windows 9X, XP and MS-DOS you have used to get a little more on topic what are some of the mistakes which you can you find, because of these, and how to fix .
0 comments:
Post a Comment