If you have FAT32 partitions, it is much simpler than with NTFS.
Just boot with a Win98 floppy and copy the NTLDR or NTDETECT.COM files
from the i386 directory to the root of the C:\ drive.

For NTFS:

1. Insert and boot from your WindowsXP CD.
2. At the first R=Repair option, press the R key
3. Press the number that corresponds to the correct location for the installation of Windows you want to repair.
   Typically this will be #1
4. Enter in the administrator password when requested
5. Enter in the following commands (X: is replaced by the actual drive letter that is assigned to the CD ROM drive.
   COPY X:\i386\NTLDR C\:
COPY X:\i386\NTDETECT.COM C:\
6. Take out the CD ROM and type exit

Incoming search terms:

• centos repair ntldr windows (1)

How do I find out if a given PCI hardware is supported of by the current CentOS / Debian / RHEL / Fedora Linux kernel?

You can easily find out find out if a given piece of PCI hardware such as RAID, network, sound, graphics card is supported or not by the current Linux kernel using the following utilities under any Linux distributions.

Required Tools

1. /lib/modules/$(uname -r)/modules.pcimap : This file is automatically generated by depmod, and used by pcimodules command to determine which modules correspond to which PCI ID’s. You need to use this file to find out if driver is supported or not.
2. lspci command – list and query all PCI devices connected to the system.

Use lspci Command To List All PCI Devices

Will an Intel Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller Card be taken care of by a Linux kernel 2.6.27-11-server?
$ lspci
$ lspci | grep -i audio
Sample Output:

00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)

Note down the identifier in first field i.e. 00:1b.0. Now use lspci -n as follows to get result for device 00:1b.0.
$ lspci -n | grep 00:1b.0
Sample Output:

00:1b.0 0403: 8086:27d8 (rev 01)

Where,

• 00:1b.0 – Device
• 8086 – constructor code for Intel Corporation
• 27d8 – The model id.

Use the model id to search driver, as follows:
$ grep 27d8 /lib/modules/$(uname -r)/modules.pcimap
Sample Output:

snd-hda-intel        0x00008086 0x000027d8 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0

snd-hda-intel is kernel driver handling PCI audio device. You can get more information about this driver by typing the following:
$ modinfo snd-hda-intel
$ modinfo snd-hda-intel| egrep 'description|filename|depends'
Sample Output:

filename:       /lib/modules/2.6.27-11-server/kernel/sound/pci/hda/snd-hda-intel.ko
description:    Intel HDA driver
depends:        snd-pcm,snd-page-alloc,snd

Another example – Will an Adaptec AAC-RAID SCSI SA Card work with Linux kernel v2.6.18-128.1.10.el5 (CentOS / RHEL 5 kernel)?

Type the following commands:
$ lspci | grep -i RAID
Output:

07:0e.0 RAID bus controller: Adaptec AAC-RAID

Get device id:
$ lspci -n | grep '07:0e.0'
Output:

07:0e.0 0104: 9005:0285

Search for device id to driver mapping:
$ grep 0285 /lib/modules/$(uname -r)/modules.pcimap
Output:

aacraid              0x00009005 0x00000285 0x00009005 0x00000286 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000285 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000287 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x000017aa 0x00000286 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x000017aa 0x00000287 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000288 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000289 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x0000028a 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x0000028b 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x000002a4 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x000002a5 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x0000028e 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x0000028f 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000290 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00001028 0x00000291 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000292 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000293 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000294 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x0000103c 0x00003227 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000296 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000297 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00001014 0x000002f2 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00001014 0x00000312 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000298 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x00000299 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00009005 0x0000029a 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00001028 0x00000287 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x00001028 0xffffffff 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0x000017aa 0xffffffff 0x00000000 0x00000000 0x0
aacraid              0x00009005 0x00000285 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0
ata_piix             0x00008086 0x00002850 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0

Get detailed information about aacraid driver:
$ modinfo aacraid | egrep 'description|filename|depends'
Output:

filename: filename:       /lib/modules/2.6.18-128.1.10.el5/kernel/drivers/scsi/aacraid/aacraid.ko
description:    Dell PERC2, 2/Si, 3/Si, 3/Di, Adaptec Advanced Raid Products, HP NetRAID-4M, IBM ServeRAID & ICP SCSI driver
depends:        scsi_mod

Task: Show kernel drivers handling each device and also kernel modules capable of handling it

Pass the -k option (works with latest lspci version only):
$ lspci -k
Sample Output:

00:00.0 Host bridge: Intel Corporation 82975X Memory Controller Hub
	Kernel modules: i82975x_edac
00:01.0 PCI bridge: Intel Corporation 82975X PCI Express Root Port
	Kernel driver in use: pcieport-driver
	Kernel modules: shpchp
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
	Kernel driver in use: HDA Intel
	Kernel modules: snd-hda-intel
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
	Kernel driver in use: pcieport-driver
	Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 5 (rev 01)
	Kernel driver in use: pcieport-driver
	Kernel modules: shpchp
00:1c.5 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 6 (rev 01)
	Kernel driver in use: pcieport-driver
	Kernel modules: shpchp
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
	Kernel driver in use: ehci_hcd
	Kernel modules: ehci-hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
	Kernel modules: intel-rng, iTCO_wdt
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller (rev 01)
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
	Kernel driver in use: i801_smbus
	Kernel modules: i2c-i801
01:00.0 VGA compatible controller: nVidia Corporation Quadro FX 570 (rev a1)
	Kernel driver in use: nvidia
	Kernel modules: nvidia, nvidiafb
03:00.0 SATA controller: Marvell Technology Group Ltd. 88SE6145 SATA II PCI-E controller (rev a1)
	Kernel driver in use: pata_marvell
	Kernel modules: ahci, pata_marvell
04:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03)
	Kernel driver in use: e1000e
	Kernel modules: e1000e
04:00.3 Serial controller: Intel Corporation Active Management Technology - SOL (rev 03)
	Kernel driver in use: serial
04:00.4 IPMI SMIC interface: Intel Corporation 82573E KCS (Active Management) (rev 03)
05:02.0 Ethernet controller: Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless (rev 03)
	Kernel driver in use: ndiswrapper
05:04.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)
	Kernel driver in use: ohci1394
	Kernel modules: ohci1394

Task: Lists all driver modules for all currently plugged in PCI devices

Type the pcimodules command (again you need updated pciutils package):
$ pcimodules
Sample Output:

ohci1394
ipmi_si
e1000e
ahci
pata_marvell
nvidia
nvidiafb
i2c-i801
ata_piix
ata_generic
pata_acpi
ata_piix
ata_generic
pata_acpi
intel-rng
iTCO_wdt
ehci-hcd
uhci-hcd
shpchp
snd-hda-intel
shpchp
i82975x_edac

Task: Update pci.ids Database

/usr/share/hwdata/pci.ids file is all known ID’s used in PCI devices: ID’s of vendors, devices, subsystems and device classes. You can update this database by typing the following command at a shell prompt:
$ update-pciids

Suggested Readings:

1. Linux – lspci command to list and find out more information about all PCI devices.
2. Linux find out or display IDs for adapters installed in a server
3. Linux find out my VIDEO Card Memory RAM size using command line utility
4. The PCI Utilities – The PCI Utilities are a collection of programs for inspecting and manipulating configuration of PCI devices, all based on a common portable library libpci which offers access to the PCI configuration space on a variety of operating systems.
5. The PCI ID Repository – This is a public repository of all known ID’s used in PCI devices: ID’s of vendors, devices, subsystems and device classes. It is used in various programs (e.g., The PCI Utilities) to display full human-readable names instead of cryptic numeric codes.
6. man pages lspci, update-pciids, and pcimodules

Incoming search terms:

• listing pci devices under centos (1)

Code Listing 1: Converting files with tr and sed

 

    // Convert from DOS/windows to unix
    % tr -d '\015' win.txt > unix.txt

    // Convert from unix to DOS/windows
    % sed -e 's/$/\r/' unix.txt > win.txt

 

Incoming search terms:

• how to convert txt linux to windows from windows (1)
• shell script convert windows format to unix format (1)
• windows tool convert txt linux (1)

Answer:A denial-of-service attack (DoS attack) or distributed denial-of-service attack (DDoS attack) is an attempt to make a computer resource unavailable to its intended users.

You can always use netstat command to get list of connections under Windows. Open command prompt by visiting Start > Run > Type “cmd” in box.

netstat is a command line utility which displays protocol statistics and current TCP/IP network connections in a system. Type the following command to see all connections:
netstat -noa
Where,

1. n: Displays active TCP connections, however, addresses and port numbers are expressed numerically and no attempt is made to determine names.
2. o: Displays active TCP connections and includes the process ID (PID) for each connection. You can find the application based on the PID on the Processes tab in Windows Task Manager.
3. a: Displays all active TCP connections and the TCP and UDP ports on which the computer is listening.

You can use find command as filter to searches for a specific string of text in a file. In the following example you are filtering out port 80 traffic:
netstat -ano | find /c "80"
Find the IP address which is having maximum number of connection and block it using Cisco firewall or IPSec. Another protective measurement is to harden the TCP/IP stack.

Incoming search terms:

• ddos programing (1)
• detecting dos on web server (1)
• netstat cmd udp tcp ip (1)

i change application pool from IIS to .net 4 classic and integrated but i have HTTP Error 500.19 – Internal Server Error.
now how can i fix that problem ?
i need to solve this problem.

A: Grant the httpdocs folder read/list permission for IIS_WPG service. I think .NET 4 is still not supported by Plesk (among many other things they’re lacking behind)

Incoming search terms:

• net framework 4 centos (2)
• change framework in plesk 9 (1)
• plesk net on linux (1)
• plesk http error 500 19 (1)
• plesk 9 ve framework 4 kullanımı (1)
• plesk 10 framework 4 (1)
• net framework plesk (1)
• NET Framework 4 plesk install (1)
• net framework 4 plesk 9 0 (1)
• net framework 4 plesk (1)

1. Insert and boot from your WindowsXP CD.
2. At the first R=Repair option, press the R key
3. Press the number that corresponds to the correct location for the installation of Windows you want to repair.
   Typically this will be #1
4. Enter in the administrator password when requested
5. cd \windows\system32\config
6. Depending on which section was corrupted:
   ren software software.bad or ren system system.bad
7. Depending on which section was corrupted
   copy \windows\repair\system
   copy \windows\repair\software
8. Take out the CD ROM and type exit

Incoming search terms:

• centos window is corrapt how to secure data (1)
• smbclient plesk (1)

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

1. Start Registry Editor (REGEDT32.EXE) and go to the following subkey:
   

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
   \Parameters

2. From the Edit menu, choose Add Value.
3. Enter the following values:
   

   Value Name: IpEnableRouter
   Data Type: REG_DWORD
   Value: 1

4. Exit Registry Editor and restart Windows NT.

Incoming search terms:

• how to configure ip routing in windows (1)
• how to disable window ip routing (1)

1. Install VMware Tools

To start, VMware Tools needs to be installed in your Virtual Machine. That should at least be from vSphere version 4.0.

2. Update your Graphics Drivers

Go to your Hardware Manager in Windows and right click your Display Adapter. Choose Update Driver Software.

Say you’ll browse to a specific location and point it to C:\Program Files\Common Files\VMware\Drivers\wddm_video.

Et voila: your driver has been updated!

3. Reboot your VM

After the driver’s been installed, reboot your Virtual Machine and you will notice the smooth console access you’re used to from Windows Server 2003.

Incoming search terms:

• w2008 esxi console blank (2)
• download vmware windows server 2008 (1)
• How to install NIC drivers for windows server 2008 (1)
• update nic driver server 2008 esx (1)
• vmware debian linux virtuale machine console is black (1)
• vmware driver windows server 2008 tagging (1)

    Error: “The network location cannot be reached. “

The most likely cause is that Host Headers for that particular site are configured for an IP address which is either no longer configured on the server, or on which IIS is no longer listening. I’m just going to assume you know how to check if an IP is configured on a server.

To check whether IIS service is listening on a particular IP, you’ll need the Windows Server Support Tools (hit google for another version if you should need it). After the installation, can you use the following Command Prompt tools.

> httpcfg query iplisten
IP                      : 10.1.5.200

If your IP address isn’t present, try adding it.

> httpcfg set iplisten -i 10.1.5.201
HttpSetServiceConfiguration completed with 0.

And query the list again.

> httpcfg query iplisten
IP                      : 10.1.5.200
------------------------------------------------------------------------------
IP                      : 10.1.5.201
------------------------------------------------------------------------------

If it does not work after the httpcfg change, you may have to reboot your server (I know, it sucks). For some reason, restarting IIS alone may not always help.

A very likely cause is that something else was occupying port 80 already when the IIS service started, causing it to delete that particular listen IP from it’s configuration. To track that down, use netstat.

> netstat -anb | find “80″

That will list all connections or programs listening to port 80.

Incoming search terms:

• network location cannot be reached rootkit (3)
• httpsetserviceconfiguration firewall (1)
• iis start site the network location cannot be reached (1)

503 Service Unavailable

You can fix this problem as follows.

Login to your vmware server as root user.

Type the following command to turn on the service:
# chkconfig vmware-webAccess on
# service vmware-webAccess start

Now login as root to your server:

Fig.01: vSphere Web Access Login In Action

Once logged in you can setup guest operating systems, start and stop vms and so on. This can be done using any browser under Linux / OS X or Windows operating systems:

Fig.02: vSphere Web Access in Action

Alternatively, you can use MS-Windows vSphere client to start and stop vSphere web access services without using shell prompt.

Incoming search terms:

• ken katos virtual disk driver (3)
• 503 service unavailable vmware centos (1)
• 503 service unavailable workstation (1)
• vcenter server Web service not available (1)
• vmware server service unavailable (1)
• vmware web access 503 service unavailable (1)
• vmware webaccess 503 (1)