Results 1 to 3 of 3

Thread: Install WINXP using LAN connection

  1. #1
    Join Date
    May 2008
    Posts
    432

    Install WINXP using LAN connection

    The term Network Boot describes the process of booting a computer (desktop, laptop or server) from a network server. But with the computer network boot code must be equipped one, for As the TCP / IP BOOT-PROM or PXE PROM code. The network boot method is also automated operating system installations used for, and an "auxiliary operating system network loaded, the above and as a platform for the actual operating system installation serves. Moreover, in specific situations, this method can be used, with an emergency or maintenance, the operating system network loaded on to perform specific tasks, such as off-virus scanning, firmware updates, etc. For the network-boot TFTP are almost exclusively the standard protocols, PXE, DHCP, BOOTP and used. In current desktops, laptops and servers with LAN-on-motherboard chip sets, are usually the default settings already a PXE network boot code.

    BOOTP (Bootstrap Protocol) is a standardized, vendor-independent protocol that allows a booting machine, address and additional configuration parameters over the network from a BOOTP server to obtain an IP. This can network boot file (also called the boot image) the name and the position of the include. DHCP (Dynamic Host Configuration Protocol) is the successor to BOOTP, provides the dynamic allocation of IP addresses, and performs other extensions, the concept of validity (IP lease) an IP address next. TFTP (Trivial File Transfer Protocol) is a standardized, vendor-independent protocol that allows booting of a machine, the assigned network boot file (boot image) over the network from a TFTP server to download it. PXE (Preboot Execution Environment) is an industry standard protocol, the DHCP and TFTP runs on top to network boot method to implement a common, and in addition a network boot API provide, by the downloaded network boot file can be used to network boot to perform other functions.


    If your machines on a network-boot-code equipped with already, enable this code in the system setup of the computer. For machines that are not a network-boot-code feature, we provide add-on BOOT-PROM code physical PROM delivered into existing memory programmed or FLASH in the BIOS can be integrated system than that. On the server side operating system is not a special need. The only requirements are that the server TCP / IP "speaks" and related services for the network boot protocols (e.g. DHCP and TFTP) provides. There are DHCP (or BOOTP) and TFTP services on the network boot server needs. These services can be either the same server or different servers running on The hardware architecture of the server is not relevant as long as the server will boot services. On the side of the network-booting machine, all Intel-compatible x86 architectures supported, including 64-bit x64 architectures.

    Basically, all the network adapter for network booting should be used provided they medium for the placement of the network boot code (i.e., the BOOT-PROM) provide a. This can be a blank PROM socket into which a PROM device is then inserted, or an onboard FLASH chip, in the BOOT-PROM code is then loaded into it. For LANOnBoard machines, the add-on boot code, the system BIOS are also integrated. Our list of supported network adapters and chipsets provides information about whether we specific network adapter or chipset your support.

    During the DHCP or BOOTP phase, only very few packets between boot finished machine and boot server replaced, so that these protocols, the overall performance do not affect normal. TFTP is against the transfer of the entire boot image from the TFTP server booting machine responsible. Here the performance depends on several factors, mainly the size of the boot images, network speed, TFTP server performance, and of course the number of simultaneously-booting machines.

    The Boot Files

    When a PC starts, it must find its operating system, load and execute. This is called the boot. In the case of GNU / Linux, the most used is as follows:
    • The BIOS has multiple boot options: hard disk, CD, etc. The most common value for this option is to boot from the hard disk.
    • The BIOS then looks on the hard disk area called the MBR (Master Boot Record). This field contains the boot loader. This is GRUB or LILO. The BIOS gives his hand to this program.
    • The boot loader is a Linux kernel on the hard disk, loads it into memory and then gives him her hand, passing parameters.
    • Linux starts up and takes account of these parameters to determine what to do.
    • But in the case of a diskless, the disc should not be used to host the operating system. We must therefore find other ways to boot.
    • The method used is the method currently LAOG boot from network with PXE protocol.


    Boot from the PXE NIC

    The network boot is for a client to obtain from a server machine's network identity (its IP address, broadcast address, its subnet mask, its hostname, domain name, DNS server names, the address of the gateway) and information on the boot server (the server's IP address and name of the boot file). The client machine must be connected to the network and positioned to boot first on its network interface (UNDI / PXE): this is to position in the PC BIOS. The PXE protocol outlines the steps necessary for the effective start of the client machine.

    Issuance by the client in a DHCPDISCOVER request application of its network identity, and this request contains the MAC address. Receipt by the DHCP server of the application which processes by seeking a match of the MAC address in dhcpd.conf, then sends the client a DHCPOFFER response containing its network identity if it has been found. Receipt by the customer and positioning of these parameters (ifconfig equivalent) then the server sends a request asking DHCPREQUEST boot information.


    Received by the server in the DHCPREQUEST request that trafficking in seeking information requested in the dhcpd.conf file, then sends the client a response DHCPPACK containing the IP address of the TFTP server and boot file name (pxelinux.0 ). Receipt by the customer query DHCPPACK that connects to the TFTP server (port 69) request and loading the file specified.
    After loading, execution of this file, always a connection TFTP load a configuration file in a directory pxelinux.cfg; it contains the name of the kernel and boot options then load the kernel and other files necessary to boot (initrd). The kernel is then started the initrd file is a compressed file system, the file system contains the kernel modules and anything else useful.

  2. #2
    Join Date
    May 2008
    Posts
    432

    Re: Install WINXP using LAN connection

    Installing and configuring the boot loader: pxelinux

    The boot loader (bootloader) is the one that loads the Linux kernel into memory. For PXE, you need a bootloader smart can load a kernel and initrd images, and decompress. After creating / diskless / tftpboot in which we built the systems required for diskless clients of that server, create a directory pxelinux.cfg (this is normally done by the script dkl-init-serveur.sh, cf. Installation section).
    • cd / tftpboot
    • mkdir pxelinux.cfg
    • cd / tftpboot
    • cp / usr/local/syslinux-1.72/pxelinux.0 / tftpboot


    In the directory / tftpboot / pxelinux.cfg, a file will be edited by diskless PC that will boot by PXE. Each file name is the hex number of PC's IP address (e.g. C3DC4F0C: C3 195, DC 220, 4F and 0C for 79 to 12).

    BIOS Setup:

    To access the BIOS, press the Delete key or F2 on your keyboard during startup, it would be really bad luck if you miss the setup of the bios. Once in the BIOS Setup, you put on the BIOS Features Setup Menu and press Enter.
    The name of this menu may vary depending on the version of BIOS, the easiest way to locate this menu is to be placed above and read the brief description at the bottom of the screen. Most of the time, Boot Sequence is included.

    BIOS Setup
    • BIOS Feature Setup menu contains information relating generally to the startup options of the computer.
    • Locate the entry Boot Sequence and using the + and - specify the order CDROM, C, A instead of the default order A, C, SCSI.
    • Once you are done, press the Esc key two times. This effect will be to display a window asking to save the new settings. Press Y followed by Enter. Now your computer will boot priority from the CDROM.
    • If the drive contains no bootable CD, the computer will boot normally from the hard drive.

    Formatting

    When your BIOS is configured so that it boots from the Network.
    After about ten seconds if no button is pressed, the computer starts normally. Wait a few moments while Windows is inspecting your configuration and then copy the files needed to install.

    Once the program is initialized, you can choose between :
    • Install XP: If you want to format and reinstall XP directly after
    • Repair or Recover: If you want to reinstall Windows without losing your data, in this case, go here
    • Exit program if you do not want to format Windows XP ultimately (e.g. if you just realize that you forgot to save something important.
    • After pressing the Enter key, the program prompts you for the hard disk and partition to be formatted
    • Now select the file system to use.
    • If you want to install Windows XP after formatting it is best to choose NTFS as the file system, however if you plan to install Windows 9x/Me better opt for a FAT file system. The full format quick format is preferable to.

    Make a Low-Level Formatting

    If your hard disk appears damaged and lost clusters or makes the system unstable, it is possible in this case to make a Low-Level Formatting.
    A Low-Level Formatting is not limited to erasing the FAT (File Allocation Table, somehow Contents of your hard disk, it enables the system to access files ...) but resets the hard disk surface cluster after cluster and the MBR and remove the partitions so allow several hour format even if you do not need to intervene during the course of the operation.

    Please note, if the data formatted with the format command can be optionally retrieved classic with some software, however those formatted with a utility low-level are lost forever! Make sure therefore taking the necessary precautions regarding the backups.

    Also, keep in mind that this type of formatting is not recommended if not required! This is reserved for advanced users. In addition, you must download the program for low-level format is specific to your hard drive, here are those of the major manufacturer.

  3. #3
    Join Date
    May 2008
    Posts
    432

    Re: Install WINXP using LAN connection

    Other Recommended Software

    Wake on LAN

    Wake on LAN Ex 2 2.09 is a handy free program to turn our remote pc: Wake On LAN Ex 2 2.09. It's very lightweight (only 200 kb of weight) and very easy to use. It is available for all Windows systems. Using the program is as simple as running, enter the information requested and click Send. This will make your pc can be booted using Wake On LAN and boot normally.

    WOL depends on the ability of remote pc may be suspended, hibernated or turned off in response to a Wake On LAN event. Wake On LAN Ex 2 also allows to shutdown, restart, hibernate, and log off the remote pc.

    As a prerequisite, Wake On LAN Ex 2 should be installed. NET Framework 2.0.
    Wake On LAN Ex 2 9.2 fixes a bug that is found that the MAC address has 17 characters instead of 16 as at the previous version.

    Boot WinPE 2.0


    TFTPD32 is a small DHCP server and TFTP (among other functions) very easy to use. He will serve our WinPE to boot from the network. Download this package , and install the Windows Automated Installation Kit. If necessary, install previously. Net framework 2.0 and MSXML 6.0 on the CD WAIK.
    • Install it in C: \ TFTPD32
    • By default, WinPE will be created in C: \ winpe and files needed to boot Windows PE PXE will be inserted in C: \ TFTPD32 \ winpe
    • Open a command prompt Windows PE Tools
    • Enter the command: copype x86 c: \ winpe
    • Wait until the control (about 1 minute '). The file c: \ winpe does not exist before this command to move.
    • This will create C: \ winpe entire tree that we will be required.
    • mount the image on the hard disk read / write: (Always from a command prompt Windows PE Tools)
    • Copy the files to be used by the network boot (PXE): All content, including directories of C: \ WinPE \ mount \ Windows \ Boot \ PXE directory to your C: \ TFTPD32 \ WinPE \ boot
    • De-mount
    • Copy the file C: \ Program Files \ Windows AIK \ Tools \ PETools \ x86 \ boot \ boot.sdi to C: \ TFTPD32 \ WinPE \ boot
    • Copy the file C: \ winpe \ winpe.wim to C: \ TFTPD32 \ WinPE \ sources \ boot.wim (note the name change)
    • Copy the file C: \ winpe \ ISO \ boot \ BCD to C: \ TFTPD32 \ WinPE \ boot \ BCD (BCD is the name without extension)

    Boot Options

    The points of entry into safe mode are mainly two, depending on whether the system is working just enough to start in normal mode or that you are stuck and you have used the power switch or the reset button to restart it. In the first case there are two possible situations: the most common is that you have a single installation of Windows (and you have not installed the Recovery Console), then start no menu to select the operating system and Windows is automatically start in normal mode. In this case, to get into Safe Mode, you must be timely to press the F8 key after the initial startup of the computer, after the post bios and before the Windows logo appears. If you have installed multiple OS, or even Windows XP and the recovery console (useful for maintenance operations when Windows will not start even in safe mode), after the BIOS messages will see the menu of operating systems installed and at this point, press F8.

    F8 menu appears with the advanced startup options, including three different safe modes: the minimum (first), with the support of the network and one with a command line interface (text mode). The second of the two cases mentioned at the beginning related to the startup of Windows after a crash or hangup that freezes the system after a serious error or sudden paralysis (no response to commands). When you restart a menu of boot options: Safe Mode, Safe Mode with Networking, Safe Mode with Command Prompt, Last Known Good Configuration startup and normal that is a subset of the available options by pressing F8. There is another way to start Safe Mode without using F8, but it requires Windows to run. You are running MSConfig in Run, it opens the Boot.ini section and check the box / button and SAFEBOOT MINIMAL NETWORK or to restart the computer in Safe mode with network support or at least, when prompted to restart you click Restart.

    Problems:

    The network adapter must be recognized by pxegrub. However, part of the network cards is not recognized by LAOG pxegrub. All network cards recognized by Linux are not recognized by pxegrub.

    The list of network cards recognized by pxegrub is not the same as the list of compatible cards (PXE AC has nothing to do). For a PXE network card is compatible, we need the PXE protocol is programmed into the smart card network. Depending on the model, a network card may not be compatible or PXE. But for a card to be recognized by pxegrub requires that developers write software pxegrub driver for this card pxegrub. Pxegrub is under development and all the drivers are not available.

Similar Threads

  1. Replies: 5
    Last Post: 01-05-2011, 10:50 AM
  2. Not able to install video Driver on WINXP x64
    By asho69 in forum Monitor & Video Cards
    Replies: 1
    Last Post: 28-12-2010, 03:36 AM
  3. not able to install oracle 8 on winxp
    By mayank27 in forum Windows Software
    Replies: 4
    Last Post: 29-07-2009, 10:11 PM
  4. How to install NetBEUI in WinXP ?
    By Faakhir in forum Networking & Security
    Replies: 3
    Last Post: 17-03-2009, 12:32 PM
  5. Fails to install updates winxp
    By dellinspiron8600winxp001 in forum Windows Update
    Replies: 6
    Last Post: 16-08-2008, 09:48 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,703,839.75962 seconds with 17 queries