Thursday, September 17, 2009

OPERATING SYSTEM

Open source OS

OPERATING SYSTEM

Open source OS

OPERATING SYSTEM

Step 1 - Start your PC and place your Windows XP CD in your CD/DVD-ROM drive. Your PC should automatically detect the CD and you will get a message saying "Press any key to boot from CD". Soon as computer starts booting from the CD your will get the following screen:

Step 2 - At this stage it will ask you to press F6 if you want to install a third party Raid or SCSI driver. If you are using a an IDE Hard Drive then you do not need to press F6. If you are using a SCSI or SATA Hard drive then you must press F6 otherwise Windows will not detect your Hard Drive during the installation. Please make sure you have the Raid drivers on a floppy disk. Normally the drivers are supplied on a CD which you can copy to a floppy disk ready to be installed. If you are not sure how to do this then please read your motherboard manuals for more information.

Step 3 - Press S to Specify that you want to install additional device.

Step 4 - You will be asked to insert the floppy disk with the Raid or SCSI drivers. Press enter after you have inserted the disk.

Step 5 - You will see a list of Raid drivers for your HDD. Select the correct driver for your device and press enter.

Step 6 - You will then get a Windows XP Professional Setup screen. You have the option to do a new Windows install, Repair previous install or quit. Since we are doing a new install we just press Enter to continue.

Step 7 - You will be presented with the End User Licensing Agreement. Press F8 to accept and continue

Step 8 - This step is very important. Here we will create the partition where Windows will be installed. If you have a brand new unformatted drive you will get a screen similar to below. In our case the drive size is 8190MB. We can choose to install Windows in this drive without creating a partition, hence use the entire size of the drive. If you wish to do this you can just press enter and Windows will automatically partition and format the drive as one large drive.

However for this demonstration I will create two partition. The first partition will be 6000MB (C: drive) and second partition would be 2180MB (E: drive). By creating two partition we can have one which stores Windows and Applications and the other which stores our data. So in the future if anything goes wrong with our Windows install such as virus or spyware we can re-install Windows on C: drive and our data on E: drive will not be touched. Please note you can choose whatever size partition your like. For example if you have 500GB hard drive you can have two partition of 250GB each.

Press C to create a partition.

Step 8 - Windows will show the total size of the hard drive and ask you how much you want to allocate for the partition you are about to create. I will choose 6000MB. You will then get the screen below. Notice it shows C: Partition 1 followed by the size 6000 MB. This indicates the partition has been created. We still have an unpartitioned space of 2189MB. Next heighlight the unpartitioned space by pressing down the arrow key. Then press C to create another partition. You will see the total space available for the new partition. Just choose all the space left over, in our case 2180MB.

Step 9 - Now you will see both partition listed. Partition 1 (C: Drive) 6000MB and Partition 2 (E: Drive) 2180MB. You will also have 8MB of unpartitioned space. Don't worry about that. Just leave it how its is. Windows normally has some unpartitioned space. You might wonder what happened to D: drive. Windows has automatically allocated D: drive to CD/DVD-ROM.

Select Partition 1 (C: Drive) and press Enter.

Step 10 - Choose format the partition using NTFS file system.This is the recommended file system. If the hard drive has been formatted before then you can choose quick NTFS format. We chose NTFS because it offers many security features, supports larger drive size, and bigger size files.

Windows will now start formatting drive C: and start copying setup files as shown on the two images below :

Step 11 - After the setup has completed copying the files the computer will restart. Leave the XP CD in the drive but this time DO NOT press any key when the message "Press any key to boot from CD" is displayed. In few seconds setup will continue. Windows XP Setup wizard will guide you through the setup process of gathering information about your computer.

Step 12 - Choose your region and language.

Step 13 - Type in your name and organization.

Step 14. Enter your product key.

Step 15 - Name the computer, and enter an Administrator password. Don't forget to write down your Administrator password.

Step 16 - Enter the correct date, time and choose your time zone.

Step 17 - For the network setting choose typical and press next.

Step 18 - Choose workgroup or domain name. If you are not a member of a domain then leave the default settings and press next. Windows will restart again and adjust the display.

OPERATING SYSTEM

Installation Process of Windows 2003


Step #1: Plan your installation
When you run the Windows Server 2003 Setup program, you must provide information about how to install and configure the operating system. Thorough planning can make your installation of Windows Server 2003 more efficient by helping you to avoid potential problems during installation. An understanding of the configuration options will also help to ensure that you have properly configured your system.
I won't go into that part right now (I might later this month, no promises...) but here are some of the most important things you should take into consideration when planning for your Windows

Server 2003 installation:
• Check System Requirements
• Check Hardware and Software Compatibility
• Determine Disk Partitioning Options
• Choose the Appropriate File System: FAT, FAT32, NTFS
• Decide on a Workgroup or Domain Installation
• Complete a Pre-Installation Checklist
After you made sure you can go on, start the installation process.
Step #2: Beginning the installation process
You can install Windows Server 2003 in several methods - all are valid and good, it all depends upon your needs and your limitations.


For example, you can install directly from a CD by booting your computer with the CD, or you can also copy the I386 folder from a CD and run the setup process by going into the I386 folder and using the WINNT or WINNT32 command (depending upon your existing operating system). It doesn't matter how you run the setup process, but the moment it runs - all setup methods look alike.

Step #3: The text-based portion of the Setup program
The setup process begins loading a blue-looking text screen (not GUI). In that phase you will be asked to accept the EULA and choose a partition on which to install 2003, and if that partition is new, you'll be asked to format it by using either FAT, FAT32 or NTFS.



1.Start the computer from the CD.

















.You can press F6 if you need to install additional SCSI adapters or other mass-storage devices. If you do you will be asked to supply a floppy disk with the drivers and you CANNOT browse it (or a CD for that matter). Make sure you have one handy.














1.If you want, you can press F2 to run the ASR sequence. For that you need a good backup created by the Windows Server 2003 backup program, and the ASR floppy disk. If you plan to install a new copy of 2003 - don't do anything.














1.Setup will load all the needed files and drivers.
















1.Select To Setup Windows Server 2003 Now. If you want, and if you have a previous installation of the OS, you can try to fix it by pressing R. If not, just press ENTER.
















1.Read and accept the licensing agreement and press F8 if you accept it.















Select or create the partition on which you will install Windows Server 2003. Depending upon your existing disk configuration choose one of the following
If the hard disk is unpartitioned, you can create and size the partition on which you will install Windows Server 2003











































If the hard disk is already partitioned,but has enough unpartitioned disk space,you cancreat an additonal partition in the partitioned space.
  • Ifthe hard disk already has a partition that is large enough,you can install Windows server 2003 on that partition.If the partition has an existing operating system,you will overwrite the operating system if you accept the default installation path.However,files other than the operating files,such as program files and data files,will not be overwrite.

  • If the hard disk has an existing partition,you can delete it to create more unpartitiond space for the new partition.Deleting an existing partition erases all data on that partition.

  • If you select a newpartition during setup,create and size only the partition on which you will install windows server 2003.After installation use disk management to partition the remaining space on the hard disk.

1. Select a file system for the installation partition. After you create the partition on which you will install Windows XP Professional, you can use Setup to select the file system with which to format the partition. Windows XP Professional supports the NTFS file system in addition to the file allocation table (FAT) and FAT32 file systems. Windows Server 2003, Windows XP Professional, Windows 2000, and Windows NT are the only Microsoft operating systems that you can use to gain access to data on a local hard disk that is formatted with NTFS. If you plan to gain access to files that are on a local Windows XP Professional partition with the Microsoft Windows 95 or Windows 98 operating systems, you should format the partition with a FAT or FAT32 file system. We will use NTFS.


























Setup will then begin copying necessary files from the installation point (CD, local I386 or network share).
Note: If you began the installation process from an MS-DOS floppy, make sure you have and run SMARTDRV from the floppy, otherwise the copying process will probably last more than an hour, perhaps even more. With SMARTDRV (or if setup was run by booting from CD) the copying will probably last a few minutes, no more than 5 max.






















The computer will restart in graphical mode, and the installation will continue.













Step #4: The GUI-based portion of the Setup program
The setup process reboots and loads a GUI mode phase.




































It will then begin to load device drivers based upon what it finds on your computer. You don't need to do anything at this stage.


















Click Customize to change regional settings, if necessary.
Current System Locale - Affects how programs display dates, times, currency, and numbers. Choose the locale that matches your location, for example, French (Canada).
Current Keyboard Layout - Accommodates the special characters and symbols used in different languages. Your keyboard layout determines which characters appear when you press keys on the keyboard.



If you don't need to make any changes just press Next.



















If you do need to make changes press Customize and add your System Locale etc.


















Note for Hebrew users: Unlike W2K, it is SAFE and it is OK for you to install Hebrew language support at this phase.
To install Hebrew support:


After pressing Customize go to the Languages tab and select the "Install files for complex script and right-to-left languages".
















A warning message will appear. Press Ok.



















Warning: You must now press Apply!!!

















Setup will copy the necessary files from the installation point.



















You can now go to the Regional Options tab and select Israel in the Location drop-down list, and Hebrew in the Standards and Formats drop-down list. Click Ok.

















Type your name and organization.

Type the product key.

Type the computer name and a password for the local Administrator account. The local Administrator account resides in the SAM of the computer, not in Active Directory. If you will be installing in a domain, you need either a pre-assigned computer name for which a domain account has been created, or the right to create a computer account within the domain.

Select the date, time, and time zone settings.

Setup will now install the networking components.

After a few seconds you will receive the Networking Settings window. BTW, if you have a NIC that is not in the HCL (see the What's the HCL? page) and XP cannot detect it, or if you don't have a NIC at all, setup will skip this step and you will immediately go to the final phase of the setup process.
Press Next to accept the Typical settings option if you have one of the following situations:
You have a functional DHCP on your network.
You have a computer running Internet Connection Sharing (ICS).
You're in a workgroup environment and do not plan to have any other servers or Active Directory at all, and all other workgroup members are configured in the same manner.

Otherwise select Custom Settings and press Next to customize your network settings.

One thing you CAN do (you don't have to do it, it's your call - read more about it on the Increase Internet Connection Speed in Windows XP page) is to uninstall the Qos Packet Scheduler. Click it and press the Uninstall button. If you want to keep it you can simply remove the mark from the QoS check-box. In anyway you can later install or uninstall it if you want.

Keep the TCP/IP, Client for Microsoft Networks and the File and Print Sharing options selected.
Highlight the TCP/IP selection and press Properties.

In the General tab enter the required information. You must specify the IP address of the computer, and if you don't know what the Subnet Mask entry should be - you can simply place your mouse pointer over the empty area in the Subnet Mask box and click it. The OS will automatically select the value it thinks is good for the IP address you provided.

If you don't know what these values mean, or if you don't know what to write in them, press cancel and select the Typical Settings option. You can easily change these values later.
In the Workgroup or Domain window enter the name of your workgroup or domain.
A workgroup is a small group of computers on a network that enables users to work together and does not support centralized administration.
A domain is a logical grouping of computers on a network that has a central security database for storing security information. Centralized security and administration are important for computers in a domain because they enable an administrator to easily manage computers that are geographically distant from each other. A domain is administered as a unit with common rules and procedures. Each domain has a unique name, and each computer within a domain has a unique name.
If you're a stand-alone computer, or if you don't know what to enter, or if you don't have the sufficient rights to join a domain - leave the default entry selected and press Next.

If you want to join a domain (NT 4.0 domain of W2K/2003 Active Directory domain) enter the domain's name in the "Yes, make this computer a member of the following domain" box.

To successfully join a domain you need the following:
The person performing the installation must have a user account in Active Directory. This account does not need to be the domain Administrator account.
and
The computer must have an existing computer account in the Active Directory database of the domain that the computer is joining, and the computer must be named exactly as its domain account is named.
or
The person performing the installation must have appropriate permission to create a domain account for the computer during installation.
Also, you need to have connectivity to the domain's domain controllers (only to the PDC if on an NT 4.0 domain) and a fully functional DNS server (only in AD domains). Read the
Joining a Domain in Windows XP Pro and Requirements when Joining a Domain pages for more on this issue.
Enter the Active Directory domain name (in the form of xxx.yyy, for example: DPETRI.NET) or the NetBIOS name of the NT 4.0 domain (in the form of xxx, for example: DPETRI). Press Next.
Note: If you provide a wrong domain name or do not have the correct connectivity to the domain's DNS server you will get an error message.
A username/password window will appear. Enter the name and password of the domain's administrator (or your own if you're the administrator on the target domain).

Note: Providing a wrong username or password will cause this phase to fail.
Next the setup process will finish copying files and configuring the setup. You do not need to do anything.

After the copying and configuring phase is finished, if XP finds that you have a badly configured screen resolution it will advise you to change it and ask you if you see the new settings right.

BTW, the minimum supported screen resolution in XP is 800X600.
Setup finishes and boots Windows XP.

A Welcome screen is the first thing you see. The computer checks your Internet connectivity (required for the mandatory Activation and voluntary Registration processes).

You will be asked to register your copy of XP. You can decline if you want.

XP will ask you for the default username that will log onto this computer. You can enter as many as 5 users, but you can create more after the installation is finished.
BTW, the Administrator is not shown as a valid logon option (read more about it on the
Add the Administrator's Account to the Welcome Screen in XP Pro page).

That's it! you're done!

Now head towards the Customize a New XP Installation page.

Thursday, August 27, 2009

Resource Allocation Graph

Resource-Allocation Graph (Cont.)



ProcessResource Allocation Graph




*If the graph does not contain a cycle, then no deadlock existsn
*If the graph does contain a cycle,then a deadlock does existn
* With single resource instances,a cycle is a necessary and sufficient condition for deadlock
*no cycle IMPLIES no deadlock
*deadlock IMPLIES cycle (necessary condition)
*cycle IMPLIES maybe deadlock (but not sufficient condition)
*single instance
resource AND cycle IMPLIES deadlock
*(necessary and sufficient)

• Deadlock can be described through a resource allocation graph.
• The RAG consists of a set of vertices P={P1,P2 ,…,Pn} of processes and R={R1,R2,…,Rm} of resources.
• A directed edge from a processes to a resource, Pi->Rj, implies that Pihas requested Rj.
• A directed edge from a resource to a process, Rj->Pi, implies that Rjhas been allocated by Pi
.• If the graph has no cycles, deadlock cannot exist. If the graphhas a cycle, deadlock may exist.


Resource Allocation Graph With A Deadlock




*If the graph contains a cycle the deadlock may or may not existn
*If the graph does not contain a knot, then a deadlock does not existn
*With multiple resource instances,a
*knot is a sufficient condition for deadlock
Deadlock! P3 cannot continue until it acquires an R2. But we know that P2 can’t continue until itgets an R3, which isn’t going to happen until P3 can go. But P1 is waiting for an R1, which isn’tavailable until P2 can go... We have a problem. No process can continue.However, a cycle alone is not enough to guarantee deadlock:

Resource Allocation Graph With A Cycle But No Deadlock








Here, there is a cycle, but P2 and P4 are not waiting for anything. That means that eventually theywill free their resources, and the other processes can get what they need.If there is a single instance of each resource, a cycle in the resource allocation graph means wehave deadlock. When there are multiple instances, it only means there is a possibility of deadlock.



Resource-Allocation Graph For Deadlock Avoidance








Here, P1 has been granted R1 and has a claim edge indicating that it may also need R2. P2currently requesting R1 and also may need R2.This is a safe state, as P1, P2 is a safe sequence.



Unsafe State In Resource-Allocation Graph





There is no deadlock yet, since there’s a chance that P1 will not need R2 before completing,thereby freeing up R1 for P2. But the state is not safe, since we cannot guarantee a safe sequence.It’s possible that P1 will need R2 before it releases R1, and deadlock would follow.


Thursday, August 20, 2009

OPERATING SYSTEM

DEADLOCK RECOVERY

ans:
Abort all deadlocked processes: this method clearly will break the deadlock cycle, but at a great expense, since these processes may have computed for a long time, and the results of these partial computations must be discarded, and probably must be recomputed later
*Abort one process at a time until the deadlock cycle is eliminated:
* this method incurs considerable overhead, since, after each process is aborted, a deadlock-detection algorithm must be invoked

OPERATING SYSTEM

DEADLOCK DETECTION
ans:

*Allow system to enter deadlock state n
*Detection algorithmn
*Recovery scheme
* An algorithm that examines the state of the system to determine whether a deadlock has occurred
*An algorithm to recover from the deadlock