Downloading and Installing Google Chrome on Linux

Here’s a quick tutorial on how to install Google Chrome on your Ubuntu Linux OS.  This is not Chromium, as some of you may have experienced in the past.  Chromium web browser was the base for Google Chrome, however if you’ve tried it in Linux, although it may have a similar feel like Google Chrome, you will shortly experience crashes.

Anyway, with that said, let’s get started on installing Google Chrome the quick and easy way in Ubuntu Linux.

1. Download the Debian Package (Courtesy of Brandon Taylor)
2. Right click on the .deb package


Right click on the .deb package to view the context menu and click on GDebi package installer

3. At the following prompt, click on Install Package

    

   

   Click on Install Package at the prompt to install Google Chrome

4. Wait a little bit until the installation completes.  You will be notified by the following screen.

    

   

   You will be prompted that the installation of Google Chrome in Ubuntu finished.

5. Now you are ready to use Google Chrome.  Go to Applications > Internet > Google Chrome.

    

   

   Launch Google Chrome on Linux

This version of Google Chrome is “unstable” so it’s probably in it’s alpha or beta testing phase, but I have not had any problem.  It supports Google iThemes as well as all the gadgets that I have in my iGoogle.   Pages are served quickly and rendered correctly for the most part.  The only problem that I have experienced between the Windows version of Chrome and this unstable release of Chrome for Linux is being able to access the new Yahoo E-mail.  It will not allow me and instead Yahoo will force me to choose the Classic Mail interface.

returned status value 4 and status text “Text was truncated or one or more characters had no match in the target code page.”. (SQL Server Import and Export Wizard)

You are here because you probably get strange errors while trying to upload a text or comma delimited file to SQL Server using their import and export utility.

Among the many errors  you are receiving, one of the most discernible ones is:

returned status value 4 and status text “Text was truncated or one or more characters had no match in the target code page.”. (SQL Server Import and Export Wizard)

After going back and editing your mappings by increasing the nvarchar size or even changing the field type to text, you are still receiving this error.

Well below is a depiction of the steps that you should take either during your initial upload of the text file or after the error is received.  Please note that to get to these different screens, use the navigation on the left hand side column.  The options are General, Columns, Advanced and Preview.

First, you’ll arrive at the place were you choose the flat file that you will be uploading to SQL server.  If the column names are in the first row, be sure to check the check box for that.

Choosing Flat File Source in SQL SERVER import wizard

Next we can preview the data and set the delimiter if it is wrong.

Set your column and row delimiters in SQL Server Import Utility

This next one is the important one, the one that will keep you from getting that error.  Click on “Advanced” and you will be taken to a page where you will be setting the column properties.  Here, you will go to the column that is causing problems based on your error result, or you can proactively change the column type before you finish out the import wizard.  In this example, I know that I my column Provider_Name needs to be greater than the default nvarchar(50) value set by SQL server.   So I changed mine to 255.

Advanced Section - Flat File import - SQL Server

Lastly, you want to preview your data.  Although this step is optional, it is still good to view it in case any characters within your data acted as a delimiter wrongfully, thus throwing off your rows and columns.

Preview your Flat File data as it will go into SQL Server

Once you have completed that, finish out the wizard like you normally would.   Be sure that you drop the table that was created in anticipation of the previous export attempt.  Otherwise you will be facing another error.

Good luck.

error while trying to run project unable to start debugging. No such interface supported

I encountered the error above after trying to run a program in visual studio 2003.   At first I thought that I may have been trying to use a class or namespace outside the 1.1 .NET framework, but it was really something else.  So if you get the message “error while trying to run project unable to start debugging.  No such interface supported” when you run your project in Visual Studio, copy the text below into a text file, save it as a batch file (with a .bat extension) and double click on it.  It will update the necessary .dll files that you need to run Visual Studio.

Also, depending on the visual studio version that you have, you may need to modify the first four (4) paths.

—- Copy text below to a text file.  Save with a .bat extension.  Double click file –

cd C:\Program Files\Common Files\Microsoft Shared\VSA\7.1\VsaEnv\Packages\Debugger\
regsvr32 Sdm2.dll

cd C:\Program Files\Common Files\Microsoft Shared\VS7Debug\
regsvr32 Msdgb2.dll

cd C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\
regsvr32 mscordbi.dll

cd C:\Program Files\Common Files\Microsoft Shared\VS7Debug\
regsvr32 Pdm.dll

cd C:\WINDOWS\System32\
regsvr32 Shell32.dll

cd C:\WINDOWS\System32\
regsvr32 Browseui.dll

cd C:\WINDOWS\System32\
regsvr32 Mshtml.dll

cd C:\WINDOWS\System32\
regsvr32 Oleaut32.dll

cd C:\WINDOWS\System32\
regsvr32 Actxprxy.dll

cd C:\WINDOWS\System32\
regsvr32 msjava.dll

cd C:\WINDOWS\System32\
regsvr32 Urlmon.dll

cd C:\WINDOWS\System32\
regsvr32 Shdocvw.dll

Thanks to Jennifer Evans for posting this a while back (http://bytes.com/topic/visual-basic-net/answers/670649-no-such-interface-supported)