How To Istalling warcraft on ubuntu

WorldofWarcraft
Before you get started
In Linux, Direct Rendering Infrastructure (DRI) facilitates faster graphics rendering, so before you begin the installation you should check whether DRI is enabled. To do this, run the following command:
glxinfo | grep rendering
You should see output similar to this:
direct rendering: Yes
If this line says "No", it means that graphics data will not be passed directly to the graphics hardware, thus significantly reducing speed at which WoW will run. This is usually caused by a configuration issue with the graphics card driver. See the troubleshooting section for elaboration.
Note though that even if you do have Direct Rendering, it might not be enough. If you graphics card is an Intel GMA, your performance will be low in any case. Most people who successfully play WoW on Ubuntu are probably using an NVIDIA or ATI card with proprietary drivers.
Installing Wine

he official deb package file of Wine from WineHQ's download page, is recommended for most users, as it works almost out of the box for most people, and has a gold rating at the moment.
For full instructions on installing Wine see the Wine page.
Deb package
1. You can easily install Wine through the repositories. Ubuntu will automatically configure and install it for you. You can go to System, then Administration and Synaptic Package Manager, search for it and mark for installation.
You may also use the command line. Simply run:
sudo apt-get install wine
2. Before proceeding to install World of Warcraft you must run winecfg at least once (it must setup the ~/.wine directory structure before you can install Windows applications into it). This is a very important step. In a Terminal window type the following:
winecfg
Select your Windows type, configure disk and removable drives, etc, then press Apply and Ok. As it closes, winecfg will create a .wine directory structure in your home folder, populating with information about drives and devices installed in your system. If you fail to do this before trying to install World of Warcraft then you'll probably see errors like the following when running winecfg in the future:
err:winecfg:apply_drive_changes unable to define devicename of 'C:'
Compiling Wine from source
Other experienced users, who are unable to make this work or just want more control over the installation, may want to try to compile Wine from source in order to play WoW. Instructions can be found here: https://wiki.ubuntu.com/BuildingWineFromSource

Installing WoW
Original WoW
If you have the installation discs, this guide recommend that you copy the contents of your discs to your hard disk and install WoW from there. If you have the new DVDs see the note below.
Create a convenient directory ( 'wow_install' on your Desktop for example)
Copy all of the files from the first WoW CD to this new directory.
For each of the remaining WoW CD's, copy just the 'Installer Tome #.mpq' files. In the end, you should have the 'DirectX' directory, and the 'autorun.inf', 'installer.ico', 'Installer Tome.mpq', and 'Installer.exe' files from disc 1, and 'Installer Tome 2.mpq', 'Installer Tome 3.mpq', 'Installer Tome 4.mpq', and 'Installer Tome 5.mpq' from the remaining discs. Note that the 'Installer.exe' file on the first disc is different from the files of the same name on the subsequent discs; if you get the wrong one the install will fail with
Unrecognized key "options". (AttributeParser::Parse)
Note that on some WoW DVD's the installer executable is hidden and you need to re-mount the disc with the 'unhide' option. To do this type in a terminal:
sudo umount /dev/cdrom
sudo mount -t iso9660 -o ro,unhide /dev/cdrom /media/cdrom0/
Start the installation by opening a terminal and running these commands:
cd //
wine Installer.exe
Replace  with the right path to the directory where you copied all the files above.
Some dialogs during installation may appear blank or garbled, and the installer may even hang for up to 5 minutes at 100% CPU, while appearing to be doing nothing. Simply wait and click next when possible.
Note: If you have not already done so, you may want to install Microsoft's proprietary fonts, because they can solve some text related graphical glitches during installation.
Burning Crusade
The BC install is more or less the same as the base game install.
Create a new directory separate from the directory where you copied the original game discs.
Copy the 'Autorun.inf', 'Installer.exe', 'Installer.ico', and 'Installer Tome.mpq' files from the first Burning Crusade disc to this new directory.
Copy just 'Installer Tome 2.mpq', 'Installer Tome 3.mpq', and 'Installer Tome 4.mpq' from the remaining install discs.
Run the installer by opening a terminal and executing these commands:
cd //
wine Installer.exe
Replace  with the right path to the directory where you copied all the files (the BC files, not the original WoW files).
Alternate Installation Methods
If the above isn't possible for some reason (you don't have the discs for example, or a working media drive), here's some alternate ways to install the game.
Alternative 1 (Installing in Windows):
Just install WoW in Windows and run WoW under Wine from your Windows Partition. Or copy the entire World of Warcraft folder over from your Windows installation after installation to play from your Ubuntu partition.
Alternative 2 (Download the Entire Game):
If you have lost a CD, do not have access to a CD drive or simply would not like to bother with patching and messing with the CD's, you can download and run the installer, which is in fact the full game almost fully patched, from the blizzard downloader. They work very nicely with Wine.
Installer Downloads: Original WoW - US Version Burning Crusade - US Version (requires a valid account for log in) WoW - European clients, in all languages
In order to use the Blizzard Downloader effectively, you must 1) open certain ports on your computer and 2) enable port forwarding on your router.
Firewall Configuration for Blizzard Downloader
The easiest way to open these ports is to use the firewall program Firestarter.
From the command line, install Firestarter with this command: sudo apt-get install firestarter.
When it is running, select the "Policy" tab, right-click in the Allow Service area, and select Add Rule.
Under port, type 6112 and make sure that the "Anyone" radio button is selected. Make a note in the comments field that this port relates to Blizzard.
Repeat these steps for ports 3724 and for the range 6881-6999 (which will be recognized as BitTorrent ports).
Router Configuration for Blizzard Downloader
Next, configure your router to forward those ports on the router to your computer only. The steps are similar to the above, but vary slightly from router to router and may be found on Blizzard's website: http://www.blizzard.com/support/wow/?id=aww01199p
Once the firewall is configured and the network port forwarding is working, run the downloader with (Burning Crusade US Version example):
wine WoW-BurningCrusade-enUS-Installer-downloader.exe
Configuration
OpenGL or Direct3D
Background
The Windows version of World of Warcraft supports 3D rendering using either Direct3D or OpenGL. The Direct3D mode in WoW is the most tested and it has a number of features over the OpenGL mode, such as support for a hardware cursor. However, in Wine the Direct3D mode is supported only through an emulation layer, that runs on top of OpenGL. Therefor this guide recommends that you enable the OpenGL mode directly, instead of using it indirectly through Direct3D. This works better for most people.
Enable OpenGL mode
Find the file wtf/Config.wtf in your main WoW directory. By default it is found in/home//.wine/drive_c/Program\ Files/World\ of\ Warcraft/, where is you computer login name. Note that since .wine begins with a period, you will not be able to see it, but you may still access it in a terminal. In the Nautilus file manager, you can press Ctrl + h to see hidden files. If config.wtf does not exist, run the game and log into a character, then exit WoW. The game should then have created the file. Open it using a text editor, and add the following line to it:
SET gxApi "opengl"
Hardware cursor in OpenGL
There is a workaround to get a kind of hardware cursor even in OpenGL mode. The workaround is to use a slightly modified version of Wine which will always display the X11 cursor (which is not laggy). If you are interested, there is a thread in the forums discussing it. Instructions explaining how to get started can be found in the thread.
Playing
Start from the Desktop Icon
Double click the icon you find on your Desktop titled World of Warcraft, this will start the launcher. If you have never used something requiring HTML rendering with Wine you will be prompted to download and install the Gecko rendering engine. Do this as it will enable the WoW Launcher to display news.
Start from the Terminal
Starting from the terminal is simple, just enter:
wine "C:\Program Files\World of Warcraft\Launcher.exe"
(install when prompted about the Gecko rendering engine)
Or, dive right into the game with:
wine "C:\Program Files\World of Warcraft\WoW.exe"
Gnome menu icon
You can make a Gnome menu entry for WoW by doing the following commands in a terminal:
wget http://kde-files.org/CONTENT/content-files/41569-wow-icon-scalable.svg -O WoW.svg
sudo mv WoW.svg /usr/share/pixmaps/
gksudo gedit /usr/share/applications/wow.desktop
Add this to the text editor window, which should have appeared after the third command, change  in the Exec= line to your computer login username, and save:
[Desktop Entry]
Encoding=UTF-8
Name=World of Warcraft
Exec=wine /home//.wine/drive_c/Program\ Files/World\ of\ Warcraft/WoW.exe
Icon=/usr/share/pixmaps/WoW.svg
Terminal=false
Type=Application
Categories=Application;Game;
StartupNotify=false
Note: Remember that you should also edit the Exec= line to reflect your WoW installation path, if you've installed to a special location.
Troubleshooting
Audio troubleshooting
If you experience stuttering you could try this:
In config.wtf set:
SET Sound_SoundOutputSystem "1"
SET Sound_SoundBufferSize "150"
The optimum value for Sound_SoundBufferSize varies depending on you setup. It may be anything from 50 to 300.
If you are no hearing any audio at all from WoW, you may want to try to switch Wine to use a an older audio sub system named OSS. To do this, just type winecfg in a terminal, press enter, and the wine configuration application window should appear and you should go to the audio tab. In there, choose OSS. Make sure you only have one sound output system (e.g. ALSA/OSS/ESD) ticked at a time.
When an application is outputing sound through OSS, it will cause conflicts with other applications outputing audio, because OSS can only output audio from one application at a time. To work around this issue, you can wrap your running WoW/Wine instance with the never audio system using the padsp launch prefix in a terminal. Start wine by typing:
padsp wine WoW.exe
rather than just
wine WoW.exe
Graphics troubleshooting
If you are having trouble with your graphics, here is a few tweaks you could try.
Config.wtf
Add the following to Config.wtf:
SET ffxDeath "0"
SET ffxGlow "0"
Note that disabling ffxGlow may also enable antialiasing for some users.
If you experience a problem with missing character and object models, and/or the login windows background is black, add:
SET M2UseShaders "0"
regedit tweaks
This is a simple registry edit for Wine that either will either fix crash issues and increase frame rate in game, or it will decrease the performance and even make the game crash. You should give it a try to see what is does for you, as you may always easily remove it again, if it acts negatively for you.
Open a terminal window, type regedit and press enter. This will start the Wine equivalent of the windows registry editor. If you are familiar with using the registry editor under windows then this is pretty much the same.
1. Find this key HKEY_CURRENT_USER\Software\Wine\
2. Highlight the wine folder in the left hand pane by clicking left on it. The icon should change to an open folder
3. Right-click on the wine folder and select [NEW] then [KEY]
4. Replace the text New Key #1 with OpenGL
5. Right-click in the right hand pane and select [NEW] then [String Value]
6. Replace New Value #1 with DisabledExtensions (Notice it's case sensitive!)
7. Then double click anywhere on the line, a dialog box will open.
8. In the value field type GL_ARB_vertex_buffer_object
More troubleshooting can be found at WorldofWarcraft/Troubleshooting.


To start/run Windows programs using Wine
After installing an application using the directions above, those applications can be started and used by entering wine programname.exe (e.g. wine realplayer.exe). When done, close the application as one would normally. You must run the installed executable, which will by default be in the virtual Windows drive created by Wine, at ~/.wine/drive_c. Generally programs will install themselves somewhere under Program Files inside the virtual Windows drive, following Windows conventions.
You can also use the Wine file browser, by running winefile in a terminal. Clicking the C:\ button in the toolbar will open a window where you can browse the virtual Windows drive created in .wine. Doubleclicking an executable in the Wine file browser will run it in Wine.
Instead of having to always enter the terminal or use the Wine file browser, you may also create a desktop icon, and start a Wine application using that icon. To do this, right click on the desktop and select "Create a launcher." If you wish, select an icon from the list of available icons (or browse to an icon you would like to use), fill out other information that is requested (Name, generic name, etc.). For the command, type in wine the-location-of-the-program.exe (e.g. wine /home/john/.wine/realplayer.exe). The most important part of creating a launcher is the command, the generic name is not as important. Just make sure you de-select "Run in terminal." This completes the process.
In some cases the application requires to be running from a certain location. In this case create launcher with command
sh -c cd /home/USER/.wine/drive_c/Program Files/Appdir/; wine /home/USER/.wine/drive_c/Program Files/Appdir/game.exe
Of course you will need to replace USER and Appdir with the proper data.
If you desire to have an icon on the panel, create a launcher on the panel of choice. Do this by right-clicking the panel, selecting "Add to Panel," and selecting "Custom Application Launcher." This will ask you for the same information as before.
Alternatively, to make life easier, you can set it so wine will automatically open .exe files files for you - instead of using the Wine File to locate the file each time. To do so, right click on the .exe file, select Properties, and then select the Open With tab. Click the 'Add' button, and then click on 'Use a custom command'. In the line that appears, type in wine, then click Add, and Close. Now all .exe files will be automatically opened by Wine, so you can use Nautilus to browse and open them instead of the Wine File.
Uninstalling Wine Applications
Open up a terminal window and type the command below.
wine uninstaller
What this will do is open up a program similar to the Windows add/remove programs control panel, allowing you to uninstall applications from a Wine installation. Running uninstall programs directly via Wine should also work normally. Alternatively, you could also simply delete the folder of the application. However, as when done in Windows, this method will be unclean and will not remove the program's configuration from the Wine registry like using an uninstaller will.
Configuring Wine
On the command line or in Run Application, type
winecfg
Adding CD and DVD drives to Wine
Go to the drives tab in winecfg. Hit the Autodetect button.
If you find that this does not work correctly for you, then follow these instructions:
1. Run
winecfg
1. Navigate to the drives tab
2. Click on Add...
3. In the path bar, type
/media/cdrom
1. Click Show Advanced button below the Browse... button and set the Type to
CD-ROM
1. Click OK
If you have more than one CD/DVD device you will need to identify each one differently. Use /media/cdrom0 for the first CD/DVD device, /media/cdrom1 for the second one, and so on. If in doubt, type the following command in your terminal.
ls -la ~/.wine/dosdevices/
What this command will do is check your CD/DVD device details after Wine is installed.
Adding applications to the menu
It is good procedure before setting up the menu entry to launch the new Windows program from the command line to make sure the program runs properly. To do this type this command in the terminal.
wine "C:\PATHTOPROGRAM\Program.exe"
For example the command would be wine "C:\Program Files\World of Warcraft\WoW.exe" Once you are satisfied that you have the correct details, use the normal menu editing process to add a new entry. When you get to the Command field of the entry editor be sure to copy and paste the line you used to launch the program from the terminal. Finish and save the new entry. Test to make sure the new Windows program loads via the menu.
Changing application specific settings
1. Type this command into your terminal.
winecfg
1. Click on Add Application...
2. Navigate to where the .exe is and choose that program
3. The dropdown at the bottom allows you to choose which version of Windows Wine should emulate. Also, any changes to the Libraries and Graphics tabs will only affect the chosen application in the Applications tab.
Using Windows Themes/Skins In Wine
Color Scheme
You can change the wine color scheme to closely match the default Ubuntu colors with this Terminal command.
gedit ~/.wine/user.reg
You may also want to create a backup copy in your Home folder with this command via terminal.
cp ~/.wine/user.reg ~/
Replace the [Control Panel\\Colors] section with
[Control Panel\\Colors] 1176981676
"ActiveBorder"="239 235 231"
"ActiveTitle"="203 133 61"
"AppWorkSpace"="198 198 191"
"Background"="93 77 52"
"ButtonAlternativeFace"="200 0 0"
"ButtonDkShadow"="85 85 82"
"ButtonFace"="239 235 231"
"ButtonHilight"="255 255 255"
"ButtonLight"="255 255 255"
"ButtonShadow"="198 198 191"
"ButtonText"="0 0 0"
"GradientActiveTitle"="239 235 231"
"GradientInactiveTitle"="239 235 231"
"GrayText"="198 198 191"
"Hilight"="246 200 129"
"HilightText"="0 0 0"
"InactiveBorder"="239 235 231"
"InactiveTitle"="239 235 231"
"InactiveTitleText"="255 255 255"
"InfoText"="0 0 0"
"InfoWindow"="255 255 166"
"Menu"="239 235 231"
"MenuBar"="239 235 231"
"MenuHilight"="246 200 129"
"MenuText"="0 0 0"
"Scrollbar"="239 235 231"
"TitleText"="255 255 255"
"Window"="255 255 255"
"WindowFrame"="0 0 0"
"WindowText"="0 0 0"
Using Theme/Skins
Wine has basic handling for Windows theme/skin files in the "msstyles" format. There is a large number of these themes onDeviant Art. To use these you must make a folder in Wine's virtual Windows drive, then tell Wine to use the theme.
Firstly go into Wine's virtual drive, which is usually ".wine/drive_c" in your Home folder (this is hidden, you may need to select View->Show Hidden Files in the file manager). Inside this folder go into the "windows" folder then make a new folder in there called "Resources". Enter this new folder and make a new folder called "Themes". Inside here you should make a folder for each theme you want, and put the files ending in ".msstyles" directly into them. For example, the full path to a theme file called sample.msstyles might be "/home/username/.wine/drive_c/windows/Resources/Themes/Sample/sample.msstyles".
Next you need to tell Wine to use your theme, so once again run this command in the terminal.
winecfg
In the configuration window select the tab Desktop Integration and un-check out the Theme: box, which should now have your theme in it's menu. After selecting the theme click Apply at the bottom to see how it looks (they don't always display properly), then if you are happy click ok and you're done!
Fullscreen issues with overlapping Panel
Sometimes the Panel overlaps your fullscreen application you're running in wine. If you are running Visual Effects, the first solution you should try is to turn those off: Go to System -> Preferences -> Appearance, and click the Visual Effects tab. Select None, and your screen will flash. Try your full-screen application again. You may re-enable Visual Effects afterwards - just don't forget to turn them back off when you want to run that application again!
If that does not work, then you will have to turn off the panels prior to running the application and restarting it afterwards, until a better workaround can be found. In Ubuntu the commands are gnome-session-remove gnome-panel and gnome-panel & respectively. In Xubuntu I understand they are killall xfce4-panel and xfce4-panel.
Instructions for using wine over remote X11 sessions
If you're (trying) to use wine over a forwarded X11 session (ie Ubuntu is on one computer; you're connected to it by ssh or another connection and you already have X11 forwarding set up to display regular Ubuntu applications on your remote computer) and the windows opened by wine are lacking fonts etc, the answer is here
Instructions for specific Windows programs
Some Windows programs have been tested on Ubuntu. They are listed below:
DVDShrink
FlashPlayerStandalone
WorldofWarcraft
Also, see Wine's Application Database at http://appdb.winehq.org/ or http://wine-review.blogspot.com/

Creating file associations
f you want certain files to open in a windows application by clicking on them, the best way is to create a script. For example I want Adobe Flash project files (*.fla) to open in Adobe's Flash editor if I double click it.
You can for example create a file using this terminal command.
gedit ~/.wine/Flash\ 8
Now paste the following example script in it, save and close gedit.
Example script:
#!/bin/sh

QUICKPARLOCATION="c:\\Program Files\\Macromedia\\Flash 8\\Flash.exe"
PARAM=`winepath -w "$*"`
wine "$QUICKPARLOCATION" "$PARAM"
exit 0
Make sure the file is executable with this command.
chmod +x ~/.wine/Flash\ 8
After you completed this go to an *.fla file right click it, properties, go to the “open with” pane, click add, add this line into your terminal and select the radio button.
'/home//.wine/Flash 8'
Now if everything went ok, you can doubleclick the file and it will be openend in Flash 8.
Troubleshooting
Error: Cannot change screen BPP from 32 to XX
In some cases (mostly games) the application does not start and you get error: Cannot change screen BPP from 32 to 16 (or some other number).
In such case editing xorg.conf and CTRL-ALT-Backspace helps as is described on http://ubuntuforums.org/showthread.php?t=649283
'dhtmled.ocx' is missing or invalid
It seems that in Ubuntu Karmic Wine(v1.0.1) registry isn't configured correctly to use ActiveX component dhtmled.ocx. On some application this can cause error like this: "Component 'dhtmled.ocx' or one of it's dependencies not correctly registered: a file is missing or invalid". So we must tell Wine where to find this file.
1. Download registry file:
cd ~
wget http://jwc.sourceforge.net/other/ieslinux-dhtmledit.reg
2. Open regedit:
wine regedit.exe
3. Import the downloaded registry settings
file->import registry file->open ~/ieslinux-dhtmledit.reg
Screen flickers to black when starting an application
This is sometimes caused by a problem with the video driver not handling XRandR well. To see if this is actually a problem with XRandR, in a console, run:
xrandr
If your screen blanks while running that command, then this might be the issue. To work around this issue, Wine can be configured to not use XRandR. To do so:
1. Start Wine's Registry Editor.
2. Navigate to "HKEY_CURRENT_USER\Software\Wine\X11 Driver". You may need to create X11 Driver.
3. Create a new key called "UseXRandR" and set it to "N".
See Wine Bug #15214 and Wine Wiki page UsefulRegistryKeys.
HOWTO: WoW with Wine

This howto is for installing and playing World of Warcraft using Wine under Ubuntu.

The howto found in this post is just a short'n'simple version, intended to demonstrate the minimum amount of steps required to make WoW run. The complete howto, which will likely be more of a help to you, is found in the Ubuntu community documentation wiki:
https://help.ubuntu.com/community/WorldofWarcraft



Short'n'simple HOWTO 
(only 8 steps)

1. Install Wine from here: http://www.winehq.org/download/deb

2. Copy all of the files from all of the CD's to a directory on your hard drive. Just overwrite when prompted, and make sure to copy CD 1 last (you need a specific file from CD 1).

3. Open a terminal (also called a konsole, CLI, and command prompt) and do these commands inside to start the installation:
Code:
cd //
wine Installer.exe
Replace with the right path to the directory where you copied all the files.

4. Wait and click next when possible. 

5. Do this command in a terminal, and just press ok to close the configuration utility that opens:
Code:
winecfg
6. Now run this command in a terminal:
Code:
gedit ~/.wine/drive_c/Program\ Files/World\ of\ Warcraft/wtf/Config.wtf
Add these lines to the text file:
Code:
SET SoundOutputSystem "1"
SET SoundBufferSize "150"
SET gxApi "OpenGL"
7. Save the file and exit.

8. You should be able to play WoW using the shortcut on your desktop, or by running this command:
Code:
wine "C:\Program Files\World of Warcraft\WoW.exe"


Reg tweak
This is a simple registry edit for Wine that either will either fix graphical glitches, increase framerate, or even stop the game from crashing, or it will create glitches, decrease the performance, and even make the game crash. You should give it a try to see what is does for you, as you may always easily remove it again, if it acts negatively for you.

Open a terminal window, type regedit and press enter. This will start the Wine equivalent of the windows registry editor. If you are familiar with using the registry editor under windows then this is pretty much the same.

Notice: the guide below is case sensitive!

1. Find this key HKEY_CURRENT_USER\Software\Wine\
2. Highlight the wine folder in the left hand pane by clicking left on it. The icon should change to an open folder
3. Right-click on the wine folder and select [NEW][KEY]
4. Replace the text New Key #1 with OpenGL
5. Right-click in the right hand pane and select [NEW] then [String Value]
6. Replace New Value #1 with DisabledExtensions
7. Then double click anywhere on the line, a dialog box will open.
8. In the value field type GL_ARB_vertex_buffer_object



How To Get Help
If this short guide doesn't work right away for you, then please look over the complete howto first:
https://help.ubuntu.com/community/WorldofWarcraft

If, after following every step in the complete howto, you are still having troubles running the game, I would like to invite you to look over this comprehensive troubleshooting article, for common issues, that arise from following this guide:
https://help.ubuntu.com/community/Wo...roubleshooting

Also, in case the troubleshooting section doesn't solve your issue, you are welcome to post questions in this tread, but in order for other people to be able to effectively help you, you need to be very descriptive about your issue, and post some useful info about your system specs etc. Please write up some details about your
CPU
RAM
Graphics card make and model
Graphics card driver version number
Wine version number

And please be polite to people. We are all just jolly amateurs, like yourself. 


For more troubleshooting :
http://ubuntuforums.org/showthread.php?t=579378

busybox v1.15.3 (ubuntu 1:1.13.3-1ubuntu1)built_in shell(ash)

I couldn't do anything else. I don't want to loose my not backed up info.
I googled the error and I found that I could boot from a live cd so I downloaded Ubuntu 10.10 and boot it from livecd... Now I am running firefox from livecd trying to fix this error.

How to resolv :

Simple ways is :
It looks like it's not detecting your root partition (/dev/sda1), which is the partition that essentially contains your OS. (/)
The reason you can't input anything probably is because the console isn't loaded yet. (initramfs) somehow doesn't seem a proper console prefix to me but I might be wrong, you might want to give it some time to load.
However, I find it hard to believe that just a CUPS (Common Unix Printing System) update could cause this since CUPS is just the Linux print service.
When you boot your computer, the GRUB bootloader should give you a choice which kernel to use. See if there is a kernel that has a lower version than the one selected and see it that boots.
If it does, the kernel entry is probably faulty and won't load the proper drivers/modules for it to find your hard drive. Creating a new entry or rebuilding your kernel might work.
If that doesn't work, you might want to boot Ubuntu into recovery mode and see if you can access /dev/sda1 from there.

1.) Restart computer with a live-Cd.
Open a terminal window.
At the command prompt, write:
sudo fsck -f /dev/sd??
You must change "sd??" to something else(with ur own partition)

or u can use :

2.)When you turn on the computer, hold down the SHIFT key and the grub menu should show. Then select an older kernel.
Or boot the live CD and download and run the bootinfoscript and post the output here.
While you're figuring out the bootinfoscript you can give us the output of
Code:
fdisk -l
and
Code:
ls /boot

or u can read tis articles :

3)grub or grub2

4.) Extrass from others sites :

Recently I messed up GRUB boot loader in my laptop installed with Ubuntu which resulted in grub rescue prompt. So I had to boot Ubuntu Live CD to get it fixed. Thought of blogging it, may be useful for some one.

This fix involves two steps. First one is to chroot into Ubuntu installation partition. Second one is to install the grub MBR (Master Boot Record). I am using Ubuntu Lucid 10.04 and Live CD also of same.

Step-1: Boot your machine with Ubuntu Live CD and select Trying Ubuntu without installation option when it is prompted (Live CD mode)

Step-2: Be patient till you get complete desktop ready.

Step-3: Ubuntu main menu -> Places -> Home Folder -> Look for other partitions listed on left hand side pane. Mount one by one and identify your Ubuntu root partition. When you are in your root partition, press Ctrl+L to view the complete mount path. Press Ctrl+C to copy this path. This path is normally /media/xx..xx kind of long path, where xx..xx denotes your hard disk partition unique id.

If you know your Ubuntu root partition you can replace the above GUI step-3 with simple mount command like this (Applications -> Accessories -> Terminal):

$ sudo mount /dev/sdax /mnt/myroot (where sdax is your root partition)

Let’s say you have mounted root partition at /media/xx..xx.

Step-4: $ Run the terminal through Applications -> Accessories -> Terminal.

Step-5: Run the following commands to export the pesudo file system of Live CD to your would be root file system soon.

$ sudo mount ‐‐bind /dev /media/xx..xx/dev

$ sudo mount ‐‐bind /proc /media/xx..xx/proc

$ sudo mount ‐‐bind /sys /media/xx..xx/sys

Step-6: Changing the root file system of live system to your hard disk installed root file system.

$ sudo chroot /media/xx..xx

Step-7: Installing GRUB Boot record in Master Boot record of your hard disk. My hard disk is sda. Replace your hard disk device node in the following command.

$ sudo grub-install /dev/sda

Step-8: Reboot the Live Ubuntu. Eject the CD.

Install Office pada ubuntu

Sukses install SuperOS 10.10, pengen install Microsoft Office 2007 dengan Wine bawaannya. Biasanya langsung klik kanan setup.exe dan pilih Open With Wine sudah bisa install. Tapi gak tahu kenapa (karena masih awam ) yang muncul adalah tulisan

“The file ‘/media/Data/Applications/Jendela/Microsoft Office 2007 Enterprise/setup.exe’ is not marked as executable. If this was downloaded or copied from an untrusted source, it may be dangerous to run. For more details, read about the executable bit.”?

Caranya:

Masuk ke folder tempat Microsoft Office berada melalui terminal. Buka Applications – Accessories – Terminal. Contoh file saya berada di /media/Data/Applications/Jendela/Microsoft Office 2007 Enterprise. Ketik di Terminal cd /media/Data/Applications/Jendela/Microsoft Office 2007 Enterprise tekan enter.

Setelah berada di /media/Data/Applications/Jendela/Microsoft Office 2007 Enterprise$ ketikkan wine ./setup.exe

Setelah itu install seperti biasa.

or just follow this :
forums.
stream.
geek.
or just download the scripts :
gtk scripts.

How To fix Grub after install windows

U can read complex articles or just going to CD for resolving ur fixed for grub

Recovery Using the Ubuntu Desktop/Live CD (RECOMMENDED)

You can check the current version installed on your system via Synaptic or from the command line. Open a Terminal and enter the following:
grub-install -v
GRUB 2 should display a version number of 1.96 or later. Legacy GRUB is version 0.97.
Create and boot from a Live CD
Grub2: Download the latest version of Ubuntu Desktop edition from http://www.ubuntu.com/GetUbuntu/download and burn your Ubuntu CD.
. Grub Legacy: See the dual-boot guide about recovering grub

Reboot your computer and boot into a live session.
Mount your Ubuntu partition from Places menu. If you have multiple Ubuntu partitions (e.g., /boot, /home, /), you need to mount the /boot partition.

Are you using Grub or Grub 2?

Go into boot/grub directory and check for the existence of the files menu.lst and grub.cfg.

. Grub Legacy uses boot/grub/menu.lst.
. Grub 2 uses uses boot/grub/grub.cfg.
1.If you are still not sure, view the file and check whether syntax follows Grub2 conventions.
If you downloaded Ubuntu Karmic 9.10 Live CD, but your installed version of Ubuntu uses Grub Legacy, please use this guide
https://help.ubuntu.com/community/DualBoot/Grub#Ubuntu%209.10%20&%20earlier
Overwriting the Master Boot Record

Existing MBR will be lost. In order to dual-boot your computer, we will be creating a new Master Boot Record to include all operating systems, including Ubuntu Linux and Microsoft Windows. This is to be expected.

Your Ubuntu partition is now mounted. You will need to continue Using the Terminal.
Verify if your partition is correct.
mount | tail -1
You should see output similar to this:
/dev/sda2 on /media/0d104aff-ec8c-44c8-b811-92b993823444 type ext4 (rw,nosuid,nodev,uhelper=devkit)
Note the designation for the disk /dev/sda which you will be using later, and the directory in /media.

Use Tab Completion in Terminal to complete the path. Hitting the key will automatically finish file names, directory locations, and other long or hard to type file names.
To make sure this is indeed the Ubuntu boot partition, run
ls /media/0d104aff-ec8c-44c8-b811-92b993823444/boot
But substitute the example's UUID, 0d104aff-ec8c-44c8-b811-92b993823444, with your volume's UUID which you found earlier. If your boot partition was a separate partition which you mounted in a previous step, use this instead
ls /media/0d104aff-ec8c-44c8-b811-92b993823444
In either case, the output should be something like this:
config-2.6.18-3-686 initrd.img-2.6.18-3-686.bak System.map-2.6.18-3-686
grub lost+found vmlinuz-2.6.18-3-686
initrd.img-2.6.18-3-686 memtest86+.bin
If what you have is not similar, unmount it and try another partition.
Now that everything is mounted, we just need to reinstall GRUB by specifying the correct directory and the correct drive name:
sudo grub-install --root-directory=/media/0d104aff-ec8c-44c8-b811-92b993823444 /dev/sda
If you get BIOS warnings try:
sudo grub-install --root-directory=/media/0d104aff-ec8c-44c8-b811-92b993823444 /dev/sda --recheck

Replace /dev/sda with the location you want to install GRUB on.
If all went well, you should see something like this:
Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.

(hd0) /dev/sda
Reboot, making sure to boot to your hard drive and not to the live CD. Grub should be installed and both Ubuntu and Windows should have been automatically detected and listed in the menu.
The Master Boot Record will execute Grub as the initial boot-loader. The Windows boot-loader is contained within the Windows partition and will then be chainloaded by the Grub boot-loader.
For Grub Legacy
Please refer to the guide
https://help.ubuntu.com/community/DualBoot/Grub#Ubuntu%209.10%20&%20earlier

Troubleshooting
I don't see a Grub menu
If the menu is not normally displayed during boot, hold down the SHIFT key as the computer attempts to boot to display the GRUB 2 menu. For Grub Legacy, use ESC key to display a menu.
Grub comes up in shell mode with no boot menu
You may have mixed up Grub Legacy and Grub 2. This symptom is most typical when you assumed you have Grub 2, but your Ubuntu OS actually uses Grub Legacy. Follow these instructions again using Ubuntu 9.04 Live CD.
If you are certain you have Grub 2 and it's still displaying shell mode by now, follow the method using chroot listed here...http://www.ubuntu-inside.me/2009/06/howto-recover-grub2-after-windows.html.
What if Grub 2 does not list Windows
If, after installing grub, Windows does not appear in the boot-menu, boot into Ubuntu and execute command
sudo update-grub2
Grub 2 gives "error: no such device: xxxxx.xxxxx.xxxxx.xxxx"
If at any time grub2 gives this error, boot up into Ubuntu (on hard disk if possible, otherwise with Live CD), open a terminal and run command
sudo update-grub2
This should automatically detect the devices and configure grub appropriately.
What if Grub Legacy misses Windows
If, after installing grub, Windows does not appear in the boot menu, you will need to edit /boot/grub/menu.lst (That is a lowercase "L" and not the number 1 in menu.lst)
Open a terminal and enter:
gksu gedit /boot/grub/menu.lst
Or, in Kubuntu:
kdesu kate /boot/grub/menu.lst
Your Windows stanza should look something like this:
title Windows XP/Vista # Use any title you wish, it will appear in the grub boot menu
rootnoverify (hd0,0) # This is the location of the windows partition
makeactive
chainloader +1
Note: Put your Windows stanza before or after AUTOMAGIC KERNEL LIST in the menu.lst
Recovery using Microsoft Windows and Its Bootloader

If you have your Linux system in a second (or third...) hard disk this method will not work. Please check Super Grub Disk's method that address this problem.
This method will also fail with Grub 2.
This method allows you to restore GRUB and keep the Windows boot-loader as your primary boot-loader. Thanks to Ubuntu's support for NTFS writing this method is now quite simple.
The previous method puts GRUB back on the MBR (Master Boot Record) of the hard drive instead of in the root partition. Should you not wish to do so, for instance if you use a third-party boot manager like Boot Magic or System Commander, this next suggestion will be helpful. Another reason to prefer this method is for when restoring the Grub menu after a re-ghosting. In either case, use this alternative.
Restoring GRUB
1. Boot from a Live CD, like Ubuntu Desktop, or similar. It is recommended to use Ubuntu 9.04 or newer as this has NTFS write support.
2. Open a Terminal. Open a root terminal (For non-Ubuntu live CDs type su the terminal. For Ubuntu based distros run
sudo -i}
Enter root passwords as necessary.
3. Type
grub
which makes a GRUB prompt appear.
4. Type
find /boot/grub/stage1
You'll get a response like "(hd0)" or in my case "(hd0,3)". Use the output from this command for the following commands.
Note:
You should have mounted the partition which has your Linux system before typing this command. (e.g. In Knoppix Live CD partitions are shown on the desktop but they're not mounted until you double-click on them or mount them manually)
5. Type
root (hd0,3)
note the space between root and (hd0,3).
6. Type
setup (hd0,3)
into the prompt. This is key. Other instructions say to use "(hd0)", and that's fine if you want to write GRUB to the MBR. If you want to write it to your Linux root partition, then you want the number after the comma, such as "(hd0,3)".
7. Type
quit
8. At this stage you can either restart the system and install your own boot-loader, or you can continue and tell the Windows boot-loader where to find GRUB which will handle booting Linux.
Making Windows Load GRUB (and then Linux)
This is taken from Dual-Boot Linux and Windows 2000/Windows XP with GRUB HOWTO which has been helping people dual boot since at least 2005.
1. In Linux open a command window.
2. Mount a drive which you can share with Windows. This could be a USB drive, a FAT32 partition on your hard drive, or if you are using a Linux distribution which supports NTFS writing natively (Such as Ubuntu 8.04 or later) then you can mount the actual Windows C:\ drive itself! The advantage of writing to the Windows drive is that you are going to need to put a file there eventually, so it saves time copying a file around. For example:
#mkdir /tmp/windows
#mount /dev/sda1 /tmp/windows
However, when writing directly to the C:\ drive you could also do some damage to the system if you delete or move something. If you do pick the option to write directly, go in, put the file where it belongs, and touch NOTHING else.
3. Now you are going to make a copy of your boot partition. Finding out what this is called is not always completely reliable since the Linux naming conventions differ from the GRUB naming conventions. Linux labels partitions as hd[Letter][Number] orsd[Letter][Number] whereas GRUB always names them as hd[Number][Number]. If you installed GRUB on (hd0,0), then the/boot partition will be on hda1 or sda1. (Since (hd1,0) == hdb1 or sdb1, then by extension if you installed GRUB on (hd0,1) then the /boot partition will be on hda2 or sda2 and so on and so forth.) This narrows you down to two possibilities. If you now paste
ls /dev |grep hd
it will let you know if you have that drive on your machine. If nothing comes up which matches, then that means you must have an sd drive.
Note: The command df won't work as you are booted from a Live CD.
4. Having determined your boot partition run this command as root by using sudo
sudo #dd if=/dev/sda2 of=/tmp/windows/linux.bin bs=512 count=1
Looking at this example /dev/sda2 is your boot partition and /tmp/windows/ is the drive you want to copy the boot sector image to.
5. If you haven't created linux.bin in the Windows drive then you need to copy it there now.
6. Next, reboot your computer and boot into Windows. Open C:\boot.ini in Notepad, and add a new line at the bottom:
c:\linux.bin="Linux"
This file might be write protected. If that is so, you need to enable writing to the file. To do so, right click, and from the context menu select Properties. Then uncheck the box that says "File is read only". Make sure to put that checkmark back afterwards.
Next, make sure that at the top of the boot.ini file there is a timeout set, i.e timeout=5 or some such number.
Do not edit this file from the Live CD, even if you have NTFS write support. Linux and Windows represent line breaks in different ways, so even though you can edit the file, it won't add a new line.
7. That's it, reboot and you will be given the option of booting into Linux, selecting that will chainload GRUB and this will let you boot into your Linux distro.
Source: http://ubuntuforums.org/showpost.php?p=121355&postcount=5

Recovery Using the Unofficial Rescatux
Note about grub2: Rescatux can be used to restore either Grub (Ubuntu 9.04 and previous versions) or Grub2 (Ubuntu 9.10 and later versions)
Download Rescatux
Burn the Rescatux ISO in a cdrom
Make your PC boot from the cdrom
At Debian Live Boot screen just press ENTER
Select Restore grub / Fix Linux Boot option and click on OK button
Select the partition where your Ubuntu is and click on OK button
Select the hard disk where you want Grub to be installed (usually the first one)
Grub was installed OK confirmation / Grub was not installed error will appear
Look for System → Shutdown in the top tray in order to halt your machine
Recovery Using the Unofficial "Super Grub Disk"
Note about grub2: The methods regarding "Super Grub Disk" described here do not work with grub2 but with grub legacy. That means that you should not use them for fresh Ubuntu 9.10 install or Ubuntu newer versions.
From within Windows
Download Auto Super Grub Disk
Double-click auto_super_grub_disk_1.7 icon, install it, and reboot.
On the next boot, select the Unetbootin-supergrubdisk menu entry; this will launch the Auto Super Grub Disk.
Do nothing till you see your Grub menu again.
Next time you boot Windows, click yes when asked to remove UNetbootin-supergrubdisk to remove the Super Grub Disk menu entry.
As a standalone cd/floppy/usb
Download Super Grub Disk
Burn into a cdrom (better) or a floppy
Boot from it
Select: GRUB => MBR & !LINUX! (>2) MANUAL |8-)
Select the Linux or Grub installation you want to restore.
You see the message: SGD has done it!
Reboot
You're done.
Preserving Windows Bootloader
The method shown above puts GRUB back on the MBR (Master Boot Record) of the hard drive instead of in the root partition. If you use a third-party boot manager like Boot Magic or System Commander you probably won't want to do that. This method could also be used to restore the Grub menu after a re-ghosting. If this is the case, use this alternative.
NOTE: This alternative, used without a third-party boot manager, will not cause Ubuntu to boot.
This method will let you boot your second hard disk Linux installations from Windows while the Using the Ubuntu Desktop/Live CD. Preserving Windows Boot-loader instructions will not.
Either:
Download Super Grub Disk
Burn into a cdrom (suggested) or a floppy
Boot from it
Or:
Download UNetbootin Super Grub Disk Loader (Windows .exe version)
Run the installer and reboot when once done installing.
On the next boot, select the "UNetbootin-supergrubdisk" menu entry; this will launch the Super Grub Disk interface.
Then:
Pick the Super Grub Disk (WITH HELP) :-))) option
Select your language from the list
Choose Windows
Select: Windows chainloads Grub!
Select the Linux or Grub installation you want to restore to its own partition.
You see the message: SGD has done it!
Reboot
Job completed.
Recovery Using the Ubuntu Alternate/Install CD
This section explains how to rescue Grub, using the Ubuntu Alternate/install CD.
1.Enter your computers BIOS to check computer can boot from CD ROM. If you can boot from CD, insert CD ROM into drive. Exit the BIOS (if needed save your settings to make sure the computer boots from the CD ROM).
2.When the Ubuntu splash screen comes up with the boot: prompt, type in rescue and press enter.
3.Choose your language, location (country) and then keyboard layout as if you were doing a fresh install.
4.Enter a host name, or leave it with the default (Ubuntu).
5.At this stage you are presented with a screen where you can select which partition is your root partition (there is a list of the partitions on your hard drive, so you are required to know which partition number Ubuntu is on). This will bedev/discs/disc0/partX, where the X is a partition number.
6.you are then presented with a command prompt (a hash).
7.type
$ grub-install /dev/XXX
where XXX is the device of your Ubuntu install. (eg: grub-install /dev/""hda"" or grub-install /dev/""sdb"" ). Note: newer 2.6.xx kernels call all hard disks ""sdx"" now but not sure if grub does.
The GUI Way: Using the Alternate/Install CD and Overwriting the Windows bootloader
Again, this is for Grub legacy, not for Grub2. So, do not try with Ubuntu 10.04 or more recent unless you have deliberately installed Grub legacy and managed to get it working in the past.
After re-initializing your mount points and other options, and after writing the changes to disk, system files are automatically installed. Each time I have tried this an error is thrown that busybox-initramfs could not be installed (I assume because a newer version exists - but I don't know. This error MIGHT be avoided if one has internet access, again, I don't know). The error aborts the installation of system files, and returns you to the menu. If you then select to install the grub boot-loader, it too, errors-out because the installation of system files did not complete. You are stuck in a loop. Unless you know some bash-magic to bypass this impasse, your only alternative (you will be unable to boot into your system now), is to return to the partitioner, reformat, and reinstall from scratch.
1.Boot your computer with the Ubuntu CD
2.Go through the installation process until you reach "[!!!] Disk Partition"
3.Select Manual Partition
4.Mount your appropriate linux partitions:
/
/boot
swap
...
5.DO NOT FORMAT THEM.
6.Finish the manual partition
7.Say "Yes" when it asks you to save the changes
8.It will give you errors saying that "the system couldn't install ....." after that
9.Ignore them, keep select "continue" until you get back to the Ubuntu installation menu
10.Jump to "Install Grub ...."
11.Once it is finished, just restart your computer
From: http://doc.gwos.org/index.php/Restore_Grub and http://ubuntuforums.org/showthread.php?t=76652
Recovery Using Third-Party Proprietary Software

This software runs only under Microsoft Windows.
EasyBCD software allows Microsoft Windows users to boot into multiple operating systems, including Ubuntu Linux.
Troubleshooting
This section applies to...
Dual-boot setups in which Windows was installed after Ubuntu
Conditions where Windows failure forced a re-installation
Windows recovery techniques involving the "restoration" of the MBR
Cases where GRUB failed to install
Prerequisites:
Your Ubuntu partitions are all still intact
You have a LiveCD, such as the Ubuntu Desktop CD or the Knoppix Live CD
You are familiar enough with your LiveCD to gain access to a console
You remember how you set up your partitions (having a printout of /etc/fstab is ideal, though you can make do with the output of
sudo fdisk -l /dev/sda
Knowledge of how your kernel works (specifically with regards to initrd), if you're using a non-Ubuntu kernel or you have built your own
Your kernel's version; this howto assumes 2.6.10-5-386
Preparing Your Working Environment
To begin the restoration procedure, insert your LiveCd and reboot your computer. Proceed with your LiveCD's bootup procedure until you are presented with an interface. To find how to open a command-line please click here] or try
Applications -> Accessories -> Terminal
Note: Since this is a LiveCD environment, any changes to user accounts or file-system layouts at this level will not be permanent. This means you can set a temporary root password and create directories without affecting your actual installation.
Now, you need to gain root access. Under Ubuntu, this can be done with the following commands:
sudo -i
Under Knoppix, the following command will suffice, and you will not be prompted for a password.
su -
Now that you have root access, you need to mount the partition(s) containing your boot-loader files.
You will need access to both your /sbin/ and /boot/ directories. If you have a /boot/ listing in your fstab, you are among those who will need to mount two partitions.
Begin by creating a mount point for your working environment -- you'll notice this is the same as creating a directory.
mkdir /mnt/work
If you need to mount /boot/, too, run the following command.
mkdir /mnt/work/boot
Now it's time to actually load your file-system data. Review your fstab and identify the location(s) of / and /boot/; these will likely look something like /dev/sda3 and /dev/sda4, though the letter 'a' and the numbers 3 and 4 may differ.
Note: For the remainder of this howto, /dev/sda3 and /dev/sda4 will be assumed, so alter them as needed when typing them in yourself.
Enter the following commands to load your file-system and some information GRUB may need.
mount /dev/sda4 /mnt/work
mount -o bind /dev /mnt/work/dev
mount -o bind /proc /mnt/work/proc
cp /proc/mounts /mnt/work/etc/mtab
Now, you have to enter your working environment. The following command will take care of that.
chroot /mnt/work/ /bin/bash
Warning: From this point on, any files you modify will affect your Ubuntu system. You have left the safety of the LiveCD. Exercise caution.
Recovering GRUB Automatically
If you have a separate /boot/ partition, type the following line.
sudo mount /dev/sda3 /boot/
Reinstalling GRUB from this point is easy. Just enter the following command.
sudo /sbin/grub-install /dev/sda
If the command you used above failed, which is unlikely, you will need to configure GRUB manually (it isn't too hard). If it succeeded, you should read the note at the start of the final section: "Configuring the GRUB Menu".
Recovering GRUB Manually
Before you can undertake the next step, it's important that you understand how GRUB identifies partitions.
To GRUB, numbers begin with 0, and letters are expressed numerically, also beginning with 0.
For example, /dev/sda1 is "hd0,0" to GRUB. Similarly, /dev/sdb3 is "hd1,2".
Note: The "root" line must point to the location of your /boot/ partition if you have one. If you do not have one, point it at your /partition.
sudo /sbin/grub
grub> root (hd0,2)
grub> setup (hd0)
grub> quit
Configuring the GRUB Menu
Note: This step does not need to be done if you're just trying to recover your MBR. Installing Windows will not alter the contents of your existing menu.lst, so if everything was working right before, everything will continue to work right now, and you can restart your computer.
Open the GRUB menu file,
sudo gedit /boot/grub/menu.lst
with your favourite text editor. We use Gedit as an example.
Note: Your menu.lst file is used to control the operating systems GRUB displays on start-up, as well as its visual appearance. This howto will only explain how to get your operating systems to boot, it will not tell you how to make your boot-loader pretty.
A sample menu.lst, stripped of unnecessary comments, appears below. It is based on the /dev/sda3 and /dev/sda4 example above, and assumes Windows resides at /dev/sda1.
timeout 5 #The number of seconds GRUB should wait before booting an OS
default 0 #The entry which should be booted by default
fallback 1 #The entry which should be booted in the event of the first one failing

title Ubuntu, 2.6.10 #A 32-bit Ubuntu entry
#This (or something like it) should be in your configuration
root (hd0,2)
initrd /initrd.img-2.6.10-5-386
kernel /vmlinuz-2.6.10-5-386 root=/dev/sda4

title Ubuntu, 2.6.10 #Another 32-bit Ubuntu entry
#This is an example of an Ubuntu entry which does not have a separate /boot/ partition
#(it is provided only as an alternate to the example above -- do not use them together)
root (hd0,2)
initrd /boot/initrd.img-2.6.10-5-386
kernel /boot/vmlinuz-2.6.10-5-386

title Microsoft Windows XP Home #An entry for a Windows installation
#If you're reading this guide, you probably want this
root (hd0,0)
makeactive
chainloader +1
And that's it. Save and close the file, then reboot and try out the entries.

Reset Your Ubuntu Password Easily from the Live CD

Our last article on how to reset your Ubuntu password easily through the grub menu was quite popular, so I’ve decided to make a series on all the different ways to reset your password on either Linux or Windows… today’s lesson is how to use the Live CD to reset the password.
Note that we’ll also cover how to protect yourself against somebody else resetting your password, so stay tuned!

Of course, this method will also work if you’ve installed your Ubuntu Live CD to a thumb drive.
Resetting the Password
You’ll want to boot from your Ubuntu Live CD, choosing “Try Ubuntu without any change to your computer” from the boot menu.

Once the system boots, open up a new Terminal window from Applications \ Accessories and then type in the following command:
sudo fdisk -l
This command is used to tell what device name the hard drive is using, which in most cases should be /dev/sda1, but could be different on your system.

Now you’ll need to create a directory to mount the hard drive on. Since we’re actually booting off the live cd, the directory doesn’t really get created anywhere.
sudo mkdir /media/sda1
The next command will mount the hard drive in the /media/sda1 folder.
sudo mount /dev/sda1 /media/sda1
Now it’s time for the command that actually does the magic: chroot. This command is used to open up a shell with a different root directory than the current shell is using, and we’ll pass in the folder where we mounted the hard drive.
sudo chroot /media/sda1
Now you should be able to use the passwd command to change your user account’s password, and it will be applied to the hard drive since we are using chroot.
passwd geek
Note that you’ll have to type your username after the passwd command in order to change the right password

Now you should be able to reboot your system and log yourself in with your new password.

Moving Home Partition

This guide will follow these 6 basic steps:

1. Setup your new partition
2. Backup and edit your fstab to mount the new partition as /media/home (just for the time being) and reboot.
3. Use rsync to migrate all data from /home into /media/home.
4. Edit fstab again so the new partition mounts as /home instead of /media/home but not reboot just yet.
5. Move /home to /old_home and reboot
6. Delete /old_home.

Creating a new partition

Setting up /home on a separate partition is beneficial because your settings, files, and desktop will be maintained if you upgrade, (re)install Ubuntu or another distro. This works because /home has a sub-folder for each user's settings and files which contain all the data & settings of that user. Also, fresh installs for linux typically like to wipe whatever partition they are being installed to so either the data & settings need to be backed-up elsewhere or else avoid the fuss each time by having /home on a different partition.

Setup Partitions

This is beyond the scope of this page. Try here if you need help. Memorize or write down the location of the partition, something like /sda3. When you do create a new partition it is highly suggested that you create an ext3 or ext4 partition to house your new home folder.

Find the uuid of the Partition

The uuid (Universally Unique Identifier) reference for all partitions can be found by opening a command-line to type the following:

sudo blkid

Alternatively, for some older releases of Ubuntu the "blkid" command might not work so this could be used instead

sudo vol_id -u

for example

sudo vol_id -u /dev/sda3

Now you just need to take note (copy&paste into a text-file) the uuid of the partition that you have set-up ready to be the new /home partition.

Setup Fstab

Your fstab is a file used to tell Ubuntu what partitions to mount at boot. The following commands will duplicate your current fstab, append the year-month-day to the end of the file name, compare the two files and open the original for editing.

1. Duplicate your fstab file:

sudo cp /etc/fstab /etc/fstab.$(date +%Y-%m-%d)

2. Compare the two files to confirm the backup matches the original:

cmp /etc/fstab /etc/fstab.$(date +%Y-%m-%d)

3. Open the original fstab in a text editor:

gksu gedit /etc/fstab

and add these lines into it

# (identifier) (location, eg sda5) (format, eg ext3 or ext4) (some settings)
UUID=???????? /media/home ext3 nodev,nosuid 0 2

and replace the "????????" with the UUID number of the intended /home partition.

NOTE: In the above example, the specified partition in the new text is an ext3, but if yours is an ext4 partition, you should change the part above that says "ext3" to say "ext4", in addition to replacing the ???'s with the correct UUID. Also note that if you are using Kubuntu or Xubuntu, you may need to replace "gedit" with "kate" or "mousepad", respectively. They are text editors included with those distributions.

4. Save and Close the file, and then restart your machine. It should now auto-mount the new partition as /media/home. We will edit the fstab again later so this arrangement of the partition is only temporary.

To ensure your partition is mounted, mount all file systems declared in fstab with:

sudo mount -a

Copy /home to the New Partition

Next we will copy all files, directories and sub-directories from your current /home folder into the new partition:

sudo rsync -axS --exclude='/*/.gvfs' /home/. /media/home/.

The --exclude='/*/.gvfs' prevents rsync from complaining about not being able to copy .gvfs, but I believe it is optional. Even if rsync complains, it will copy everything else anyway.

Check Copying Worked

You should now have two duplicate copies of all the data within your Home Folder; the original being located in /home and the new duplicate located in /media/home. You should confirm all files and folders copied over successfully. One way to do this is by using the diff command:

diff -r /home /media/home

The only difference that should exist is the excluded /.gvfs directory mentioned above.

Preparing fstab for the switch

We now need to modify the fstab again to point to the new partition and mount it as /home. So again on a command-line

gksu gedit /etc/fstab

and now edit the lines you added earlier, changing the "/media/home" part to simply say "/home" so that it looks like this:

# (identifier) (location, eg sda5) (format, eg ext3 or ext4) (some settings)
UUID=???????? /home ext3 nodev,nosuid 0 2

Then, press Save, close the file but don't reboot just yet.

Moving /home into /old_home

As long as you have not rebooted yet, you will still see 2 copies of your /home folder; the new one on the new partition (currently mounted as /media/home) and the old one still in the same partition it was always in (currently mounted as /home). We need to move the contents of the old home folder out of the way and create an empty "placeholder" folder to act as a mount point for our new partition.

Type the following string of commands in to do all this at once:

cd / && sudo mv /home /old_home && cd / && sudo mkdir -p /home

By default, when you open a terminal window it places you within your home folder. Typing cd / takes us to the root folder and out of home so we can then use the sudo mv command to essentially rename /home into /old_home, and finally create a new, empty /home placeholder.

With your fstab now edited to mount your new partition to our /home placeholder and the original /home now called /old_home, reboot your computer. Your new partition will mount as /home and everything should look exactly the same as it did before you started.

Deleting the old Home

You can delete your old home directory with:

cd /
sudo rm -r /old_home

Be careful with the above command as mistyping it could result in the deletion of other files and folders.

or u can go for other Tutorial :
1.Moving Home Partition
2.and this for Problems Solved

My Definitions Sources

# DARK ANGEL24 Source.list
# This My List of Favourite
#########################################################################################
# deb cdrom:[Ubuntu 10.04.1 LTS _Lucid Lynx_ - Release i386 (20100816.1)]/ lucid main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://archive.ubuntu.com/ubuntu lucid main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu lucid main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu lucid-updates main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu lucid-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu lucid-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu lucid-backports main restricted universe multiverse
deb http://archive.canonical.com/ubuntu lucid partner
deb-src http://archive.canonical.com/ubuntu lucid partner
deb http://security.ubuntu.com/ubuntu lucid-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu lucid-security main restricted universe multiverse
deb http://packages.medibuntu.org/ lucid free non-free
deb-src http://packages.medibuntu.org/ lucid free non-free
deb http://archive.getdeb.net/ubuntu lucid-getdeb apps
deb-src http://archive.getdeb.net/ubuntu lucid-getdeb apps
deb http://ppa.launchpad.net/cairo-dock-team/ppa/ubuntu lucid main ## Cairo-Dock-PPA-Stable

How to fix gpf key on ubuntu ?

sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 313D312748A22A95; gpg --export --armor 313D312748A22A95 | sudo apt-key add -



gpg –keyserver keyserver.ubuntu.com –recv 3E5C1192

gpg –export –armor 3E5C1192 | sudo apt-key add -

sudo apt-get update





sudo apt-get update -o Acquire::http::No-Cache=True

sudo aptitude update -o Acquire::http::No-Cache=True

sudo apt-get -o Acquire::http::No-Cache=True -o Acquire::BrokenProxy=True update

sudo aptitude update -o Acquire::http::No-Cache=True -o Acquire::BrokenProxy=True



sudo bash

apt-get clean

cd /var/lib/apt

mv lists lists.old

mkdir -p lists/partial

apt-get clean

apt-get update

What is the best linux distro for me?

Below are the refferences for new users who are mainly looking for a linux distro experience that's similar and compatible with the one they're used to.
1.For newbies: Ubuntu

that ordinary computer users can recognise, and doesn't require any assumed knowledge. You can install Ubuntu on to most machines without any difficulty, and there's a good chance your monitor will be optimally configured and your wireless access point will be discovered. This is where many previous new users may have stumbled, and Ubuntu has raised the bar when it comes to hardware compatibility.

Ubuntu is composed of many software packages, of which the vast majority are distributed under a free software license (also known as open source). The main license used is the GNU General Public License (GNU GPL) which, along with the GNU Lesser General Public License (GNU LGPL), explicitly declares that users are free to run, copy, distribute, study, change, develop and improve the software.

2.For OS migrants: Linux Mint

Linux Mint is another distribution built on the strong foundations of Ubuntu. It takes the good points, such as the excellent hardware compatibility and easy installation, and performs a facelift on the weakest points, which is the muddy ambience of the Ubuntu desktop.

Usability has been enhanced by removing the top menu bar and replacing the themes and palette of the original distribution with a tub of choco-mint ice cream. But what makes Mint most effective for a recent convert to Linux is its excellent support for codecs. Most music and video will play without any further requirements, and Adobe Flash and Sun's Java are installed by default.

3.Family friendly: Qimo

It's a distribution with a focus on young children, with a friendly oversized desktop and colourful engaging artwork. A small toolbar of educational games sits at the bottom of the screen, and children can use these to quickly launch a selection of open source games and educational resources.

Addressing the second point is a little harder. That's because content filtering is a tricky and technical subject, and not at all in-line with an open, family friendly distribution. You could take any distribution, for example, and use a carefully configured OpenDNS or DansGuardian server to filter contents to the sites that you don't want your family to have access to.

4.Everyday Linux: Fedora

For every day desktop use, Fedora can't be beaten. The choice of software is excellent, and we can't think of anything that's missing. Fedora's stance on freedom is a little painful if you need proprietary drivers or MP3 support, but these issues can be worked around. Both the Gnome and KDE desktops look and feel brilliant, and the performance of our Fedora installation is as good as any other tuned Linux distribution.

It's also a distribution that will have users of other operating systems looking over your shoulder. Fedora might not be the easiest distribution to use, or the one with the largest package repository, but we feel it represents the very best that open source software has to offer.

5.Business: OpenSUSE

It's a distribution that's very close to the development of OpenOffice.org, and it scales extremely well. If you need professional support and training, you can get it from Novell as well as a number of third-party providers.

At the heart of OpenSUSE 11.1 is the word processor, and Novell does an excellent job of integrating OpenOffice.org into whichever desktop you choose (Gnome and KDE are available). Themes and icons look fantastic, and OOo loads quickly and is configured for compatibility with Microsoft Office documents.

A to-do tasks manager is bundled alongside the office suite, and this can be synchronised with Evolution, the standard email application. Pervasive desktop searching is enabled as standard, and Wine is a click away for running any remaining Windows applications you may need to run from the Linux desktop.

6.Light and fast: Puppy Linux

I's a tiny distribution, fitting into a tiny 100MB ISO image. This means it can be installed on any cheap old USB disk and used on an old computer.

But unlike many other lightweight distributions, the Puppy desktop covers almost every task you'll ever need. Photo editing, document writing, listening to music and watching videos can all be accomplished using a low-fat application listed in the main menu, or from the icon on the desktop.

These applications may not be quite as user-friendly, or quite as capable, but they can accomplish 90% of the tasks most people need. And they'll do it quickly. There's even wireless networking support, so you can quickly shoe-horn a laptop into providing a quick Linux fix, or maybe squeeze Puppy alongside a standard install on a netbook computer to give yourself a breath of fresh air once in a while.

7.Sysadmin: Arch Linux

A distribution that's unashamedly built for reconfigurability and gaining geek credentials. It's a distro for experienced Linux users who aren't afraid of getting their hands dirty. Arch doesn't make any assumptions about what packages you might want to install. Logging into live CD-based system, you're invited to run the install script from a specific directory.

From the solid foundation of Arch's base installation, you can build an administrator's toolkit that will only include the applications and the tools for your working environment. This will save system resources on the machine, and your mental resources when you need to get a job done quickly. Arch includes all the packages you'll ever need, especially when it comes to useful command line tools you'll find more effective at system administration.

8.Coder: Mandriva

If you prefer scripting languages like Perl or Python you're better off using your standard desktop, as these languages are now so common that any one distribution is as good as another, while professional developers using an IDE like JBuilder will find that Red Hat Enterprise Linux is often the only distribution supported by the vendor.

Not only does it include a working development environment from the first boot, the development libraries themselves are easy to find and install through the package manager. Gnome, KDE and Xfce developers are well catered for, and the distribution includes Java.

9.Server: CentOS

You can install and use commercial packages designed for RHEL, but it also means you get the same high level of security and integrity that Red Hat's direct customers enjoy. This makes CentOS the perfect choice of operating system for running a server on a restrictive budget.

Like RHEL, CentOS is based on a Gnome desktop, and includes access to many of the same applications, servers and utilities you can find with any standard distribution. If you've used a recent Fedora release, you'll feel right at home. Security features include an excellent firewall and SELinux, a policy enforcement mechanism that prevents wayward applications from ever causing security problems, even if they do happen to be compromised or broken. There are also plenty of updates, and there's a large community who are willing to help. If you ever do need professional-level support, the transition from CentOS to RHEL is seamless.

10.Music Production: 64 Studio

64 Studio provides a complete audio production environment, as well as all the kernel and system tweaks to optimise your hardware. It has been designed to create a professional setup that's capable of recording, mixing and mastering many simultaneous tracks of audio.

The Sound & Video menu is crammed full synths, an oscilloscope, guitar and studio effects, an audio sampler, a turntable emulator and several methods for monitoring audio. But the two most important entries are Rosegarden and Ardour. These are the open source equivalents of Cubase and Pro Tools in the commercial world, and they're both exceptional applications for composing and recording music.

All of these applications are part of the default 64 Studio desktop, and you can see that this distribution covers everything from the recording, and sound generation part of a project, through the editing and mastering to the final CD burning. We can't think of any other system that provides anywhere near the same amount of functionality for the zero cost.

11.Gamers: Live.linux-gamers

If you live for gaming, Linux isn't the best choice of platform. Most of the major releases don't offer Linux versions, and there's little third-party hardware support for controllers. But most of us love playing games, and switching to Linux doesn't mean you have to abandon this wonderful time waster.

We've found that the best solution is to boot into a live distribution specifically tailored for games, and the best we've come across is called Live.linux-gamers.net. It contains a DVD's worth of data and includes almost anything worth playing, along with the proprietary graphics cards drivers to ensure maximum performance from your hardware.

There are two companies that sell a commercial version of Wine, the Windows compatibility layer, specifically tweaked for running the latest Windows games. These two applications are called CrossOver Games and Cedega, and both claim to run titles such as Spore, World of Warcraft and many Steam titles. Packages are available for most popular distributions, and in our experience they work quite well.

12.Multimedia: Mythbuntu

The installation includes everything you need to get started, and bundles the most common MythTV plugins for media playback. You can even use the installation disc as a live CD in a spare machine, turning it into a MythTV client on the network for ad-hoc TV and movie watching. Even without a MythTV system on the network, you can still use the disc for basic multimedia playback, as it operates as a standard Ubuntu disc with a few additional packages.

We think it's easier to stick with Mythbuntu if you're after a multimedia distribution for your home entertainment system. But if you want a slick user interface without the hassle of configuring MythTV, LinuxMCE is worth a look.

Dialing with kpp or gnome ppp is the same ways

Add User to Group
For kppp to be started from the menu, the user name needs to be added to the group "dip."
To do this, open the Root Terminal, and type:
gpasswd -a (username) dip
Insert username where it says (username).
It is not necessary to turn the computer off and restart now, but if you do, you will be able to start Kppp from the menu.
You may also get a message saying:
"/etc/resolv.conf is missing or can't be read! Ask your system administrator to create this file (can be empty) with appropriate read and write permissions."
Let's create this file.

Create File resolv.conf
In the Root Terminal, and type:
cd /etc
touch resolv.conf
This file is now created.
Kppp will now start without displaying the message.
Before you can send or receive anything on the internet, there needs to be one more modification.

Modify /etc/ppp/peers/kppp-options
Open the Root File Manager.
Go to "/etc/ppp/peers/" and open the file "kppp-options."
The contents of the file are:
#noauth
Delete the "#," so it becomes:
noauth
Save the file.
Close the Text Editor and File Manager.
For this to take effect, turn the computer off and restart.
Kppp will now work.

Set Up Kppp
Following is an explanation of how to set up Kppp using common options. In some situations the information which needs to be entered may be different. Enter information as appropriate for your situation.
Begin by clicking on "KPPP" in the menu to open it.
Click "Configure." You will see a new window.
Click "New." You will see a new window.
You may try "Wizard" and see if it works. Only some countries are included here. If your country is not included, you cannot set it up using this method. Let's use Manual Setup.
Click "Manual Setup." You will see a new window.
Click "Add." You will see a new window.
Enter the phone number your computer dials to connect to the internet. Then click "OK." This will close this window and take you back to the previous one.
Enter the name of your internet provider in the box following "Connection name." (You can enter anything here.)
You may click on the "Accounting" tab and set up accounting if you want to record your phone costs, but this is not necessary.
Click "OK." This will close this window, and take you back to the previous one.
Click the tab "Modems."
Click "New."
Enter the name of your modem in the box following "Modem name." (You can enter anything here.)
The box following "Modem device" needs to set as appropriate for your modem. If you have an internal modem, leave it as "/dev/modem." If you have an external serial modem, it may be "/dev/ttyS0." If you are not sure, try different ones and see which works.
In the box following "Connection speed," change it to "115200."
Click "OK." This will close this window, and take you back to the previous one.
Click "OK" again. This will close this window, and take you back to the previous one.
In the box following "LoginID," enter the username you use to connect to the internet.
In the box following "Password," enter the password you use to connect to the internet.
You can now click "Connect," and connect to the internet.
You can also click "Quit" to close it.

Scripts

Sorry about late write this article.,
its for beginner and fresh install Lucid on PC, and is easy to use,
Simple copy paste script and u can drink coffe or something.,
it take a long long timre :

Update 18 Apr. 2010: A new version of the script has been released. Please see: What To Do After A Fresh Ubuntu Install Script - New Version Released [Ubuntu 10.04 Lucid Lynx]
To download and run the script, simply paste this in a terminal:

sudo apt-get install zenity
wget http://launchpad.net/ubuntustart/0.4.x/0.4.9/+download/ubuntu-10.04-start-0.4.9.13.tar.gz
tar -xvf ubuntu-10.04-start-0.4.9.13.tar.gz
cd ubuntu-10.04-start/
sudo ./ubuntu-10.04-script



Update: I replaced the old download link above with the latest version!
Here's what the script does:

* add extra repositories (Medibuntu, Getdeb, etc)
* download and install the latest updates
* install Ubuntu Tweak
* install codecs, web browser plugins (Java, Flash), additional support for archives (RAR, 7-Zip) and additional fonts; installs the latest Flash Player for Ubuntu 10.04 Lucid Lynx 64bit from Adobe's website
* Gconf tweaks: move the Metacity window buttons back to the right, disable the GDM login sound, fix the update manager behavior to always show updates and enable the icons in menus and buttons
* install GIMP (which has been removed from Ubuntu 10.04 Lucid)
* install VLC
* install Thunderbird email client
* install Chromium web browser
* install Google Chrome - the latest dev version (it will download the 32 or 64 bit version automatically - depending on your system architecture)
* install WINE
* install MPlayer
* set MPlayer and Totem character encoding to Central / Eastern European (Windows-1250), you can disable this by removing lines: 64 and 69,70,71,72,73,74,75, or selecting manual configuration from the script menu
* install Pidgin instant messaging client