Information Technology: 2009

Monday, June 22, 2009

midnight commander

To run midnight commander you need glib 1.x.x. or newer.

1. Install glib
# wget ftp://ftp.gtk.org/pub/gtk/v2.5/glib-2.5.6.tar.gz
# tar zxvf glib-2.5.6.tar.gz
# cd glib-2.5.6
# ./configure --prefix=/usr
# make
# make install

NOTE. If you're installing Glib 2.x.x configure it with /usr directory.

2. Install Midnight Commander
# wget http://www.ibiblio.org/pub/Linux/ut...mc-4.6.0.tar.gz
# tar zxvf mc-4.6.0.tar.gz
# cd mc-4.6.0
# ./configure
# make
# make install

To run Midnight commander use

#mc

Wednesday, May 27, 2009

NTOSKRNL.EXE is missing or corrupt.

Issue:

NTOSKRNL.EXE is missing or corrupt.

Related errors:

Below is a listing of the full error message that may be related to this error.

Windows NT could not start because the below file is missing or corrupt:

C:\Winnt\System32\Ntoskrnl.exe

Cause:

Keyboard issue
Miscellaneous corruption
Corrupt boot.ini file.
Missing boot.ini file.
Missing or corrupt ntoskrnl.exe file.
Windows NT installed on a partition bigger then 7.8GB
Corrupted hard disk drive or severely corrupted Windows.

Solution:

Keyboard issue

This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer.

Miscellaneous corruption

Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration. Additional information about doing this can be found on document CH000626.

Corrupt boot.ini file

This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer.

Make sure the line pointing to the operating system and it's drive and partition is properly configured in the [boot loader] and [operating systems] section. Additional information about boot.ini can be found on document CH000492.

Missing boot.ini file

Microsoft Windows XP users:

If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue. Additional information about rebuilding the boot.ini can be found on document CH000648.

Microsoft Windows NT and Windows 2000 users:

To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need an ERD and follow the below steps. If you do not have an ERD you will be unable to follow these steps.

Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
In the setup menu, type R to start the repair.
When prompted for the ERD diskette insert the diskette and inspect the startup environment.

Missing or corrupt ntoskrnl.exe file

If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.

Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
Select the operating system you wish to fix, and then enter the administrator password.
Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
Type exit to reboot the computer.

Windows NT installed on a partition bigger then 7.8GB

If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the error message as shown below.

OS Loader v4.01
Disk I/O error status=00000001
Windows NT could not start because the below file is missing or corrupt: winnt\system32\Ntoskrnl.exe
Please reinstall a copy of the above file.

If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.

Corrupted hard disk drive or severely corrupted Windows

Attempt to check the hard disk drive for any errors by running the chkdsk error. To do this follow the below steps.

Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
Select the operating system you wish to fix, and then enter the administrator password.
Once at the recovery console type chkdsk /r
Once completed type exit and see if issue is resolved.

If after trying all of the above steps you are still encountering the same issue it's likely that Windows is severely corrupted and it is recommended you attempt to reinstall Windows. Additional information about erasing the computer and starting over can be found on document CH000186.

Finally, if during the Windows installation you encounter errors it's likely that your hard disk drive is bad.

NTLDR is Missing.

Related errors:

Below are the full error messages that may be seen when the computer is booting.

NTLDR is Missing
Press any key to restart

Boot: Couldn't find NTLDR
Please insert another disk

NTLDR is missing
Press Ctrl Alt Del to Restart

Cause:

Computer is booting from a non-bootable source.
Computer hard disk drive is not properly setup in BIOS.
Corrupt NTLDR and/or NTDETECT.COM file.
Misconfiguration with the boot.ini file.
Attempting to upgrade from a Windows 95, 98, or ME computer that is using FAT32.
New hard disk drive being added.
Corrupt boot sector / master boot record.
Seriously corrupted version of Windows 2000 or Windows XP.
Loose or Faulty IDE/EIDE hard disk drive cable.

Solutions:

Computer is booting from a non-bootable source

Many times this error is caused when the computer is attempting to boot from a non-bootable floppy disk or CD-ROM. First verify that no floppy diskette is in the computer, unless you are attempting to boot from a diskette.

If you are attempting to boot from a floppy diskette and are receiving this error message it is likely that the diskette does not have all the necessary files and/or is corrupt.

If you are attempting to install Windows XP or Windows 2000 and are receiving this error message as the computer is booting verify that your computer BIOS has the proper boot settings. For example, if you are attempting to run the install from the CD-ROM make sure the CD-ROM is the first boot device, and not the hard disk drive.

Second, when the computer is booting you should receive the below prompt.

Press any key to boot from the CD

Important: When you see this message press any key such as the Enter key immediately, otherwise it will try booting from the hard drive and likely get the NTLDR error again.

Note: If you are not receiving the above message and your BIOS boot options are set properly it's also possible that your CD-ROM drive may not be booting from the CD-ROM properly. Verify the jumpers are set properly on the CD-ROM drive. Additional information about checking the CD-ROM drive connections can be found on document CH000213.

Additional information: This error has also been known to occur when a memory stick is in a card reader and the computer is attempting to boot from it. If you have any type of card reader or flash reader make sure that no memory stick is inside the computer.

NBTstat

NBTstat

NBTSTAT [ [-a RemoteName] [-A IP address] [-c] [-n] [-r] [-R] [-RR] [-s] [-S] [interval] ]

-a	(adapter status) Lists the remote machine's name table given its name
-A	(Adapter status) Lists the remote machine's name table given its IP address.
-c	(cache) Lists NBT's cache of remote [machine] names and their IP addresses
-n	(names) Lists local NetBIOS names.
-r	(resolved) Lists names resolved by broadcast and via WINS
-R	(Reload) Purges and reloads the remote cache name table
-S	(Sessions) Lists sessions table with the destination IP addresses
-s	(sessions) Lists sessions table converting destination IP addresses to computer NETBIOS names.
-RR	(ReleaseRefresh) Sends Name Release packets to WINs and then, starts Refresh
RemoteName	Remote host machine name.
IP address	Dotted decimal representation of the IP address.
interval	Redisplays selected statistics, pausing interval seconds between each display. Press Ctrl+C to stop redisplaying statistics.

Examples

nbtstat -a 204.224.150.3

Local Area Connection:
Node IpAddress: [204.224.150.3] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status
---------------------------------------------
HOPE4  <00> UNIQUE Registered
CHGROUP  <00> GROUP Registered
HOPE4   <20> UNIQUE Registered
HOPE4   <03> UNIQUE Registered
CHGROUP  <1e> GROUP Registered
CHGROUP  <1d> UNIQUE Registered
..__MSBROWSE__. <01> GROUP Registered
ADMINISTRATOR  <03> UNIQUE Registered

MAC Address = 00-00-00-00-00-00

Information Technology

Monday, June 22, 2009

midnight commander

Wednesday, May 27, 2009

NTOSKRNL.EXE is missing or corrupt.

NTOSKRNL.EXE is missing or corrupt.

Issue:

Cause:

Solution:

NTLDR is Missing.

Cause:

NBTstat

notes9

notes8

ie55beta

notes4

notes3

you are visitor number

About Me