หน้าเว็บ

วันพฤหัสบดีที่ 19 พฤศจิกายน พ.ศ. 2552

Cmd prompt for Window

Specific Control panel

"Control desktop"
"Control color"
"Control date/time"
"Control international"
"Control mouse"
"Control keyboard"
"Control printers"
"Control fonts"


Management

Certificate Manager : " certmgr.msc"
Indexing Service : "ciadv.msc"
Computer Management : "compmgmt.msc"
Device Management : " devmgmt.msc"
Disk Defragmenter : "dfrg.msc"
Disk Management : "diskmgmt.msc"
Event Viewer : "eventvwr.msc"
Shared Folders : "fsmgmt.msc"
Group Policy : "gpedit.msc"
Local Users and Groups : "lusrmgr.msc"
Removable Starage : "ntmsmgr.msc"
Performance Monitor : " perfmon.msc"
Resultant Set of Policy : "rsop.msc"
Security Policy : "secpol.msc"
Services : "services.msc"
Windows Management Infrastrusture : "wmimgmt.msc"


Thanks : Robopony

วันพุธที่ 18 พฤศจิกายน พ.ศ. 2552

Check printer when have problem

Check Printer when have problem


1. Check power of printer.

2. Check usb connector.

3. Check driver.

4. Test print file.

5. Change to other Usb slot.

6. If can't print read error on printer.

7. If can't print uninstall driver and install againas.

8. Check error on printer

9. Check Ink of printer

วันอังคารที่ 3 พฤศจิกายน พ.ศ. 2552

How to install rdesktop on Ubuntu

How to install rdesktop on Ubuntu



Code:
sudo apt-get install rdesktop
should take care of it. You way also want to install tsclient for a graphical frontend for rdesktop.
Code:
sudo apt-get install tsclient
You can also use Synaptic Package Manager to do this. Click on System --> Administration --> and choose Synaptic Package Manager.

Thanks : linuxquestions.org

VMWare Server 2 – RuntimeFault: Database temporarily unavailable or has network problems

If you add a new User (New Permission) to the VMWare Server 2 via the VMware Infrastructure Web Access you may get the message “The server response included one or more errors” with the details “RuntimeFault: Database temporarily unavailable or has network problems”.

vmerr


To fix this you first have to stop the VMWare management service:

/etc/init.d/vmware-mgmt stop


Now open the file “/etc/vmware/hostd/authorization.xml” and change the value of ‘’ to 50 for example.


After that change you can start the VMWare management service again:

/etc/init.d/vmware-mgmt start


Now you can relogin into the VMware Infrastructure Web Access and add the new user. (If you get the error again, change the value of again to a higher value)


Thanks : mogilowski.net

Introduction To VMware VIX API

Introduction to VMware VIX API.


The VIX API allows you to automate virtual machine operations on VMware Server or VMware Workstation.


About the VIX API

The VIX API (or "Vix") is a library for writing scripts and programs to manipulate virtual machines. It is high-level, easy to use, and practical for both script developers and application programmers. The VIX API is designed for three kinds of users:

  • Technically Adventurous Users - For example, dedicated IT personnel in an organization building their own in-house tools.
  • Partners - Software vendors using Vix to integrate VMware products with their own products or to build management products specifically for virtual machines.
  • VMware Engineering - VMware uses Vix in its own products as a general abstraction layer between core virtual machine processes and associated service processes.

The VIX API runs on Microsoft Windows (Windows95 or later) and Linux platforms (kernel 2.4.x or later recommended). It supports programs written in C, Perl, and COM (Visual Basic, VBscript, C#).


Compatibility

This release of the VIX API is compatible with VMware Server 2.0 and VMware Workstation 6.5.

Product Compatibility

VIX API Version

Compatible Platform Products

Library Location

1.0.3

VMware Server 1.0

server-1

1.1

VMware Workstation 6.0

ws-3

1.1.1

VMware Workstation 6.0.1 or earlier

ws-3

1.1.2

VMware Workstation 6.0.2 or earlier

ws-3

1.1.4

VMware Workstation 6.0.4 or earlier

ws-5

1.1.5

VMware Workstation 6.0.5 or earlier

ws-5

1.6.0

VMware Server 2.0 or earlier

VIServer-2.0.0

1.6.1

Workstation 6.5 or earlier

Workstation-6.5.0

The library location is not important if you use the wrapper library as recommended.

Vix Version 1.x supports programs written to version 1.x of the VIX API. Exceptions are noted on function reference pages. For example, VMware Server does not support record and replay, while VMware Workstation does not support virtual machine registration.

Vix libraries are installed with VMware Server and VMware Workstation and provide API compatibility corresponding to the product release. Vix libraries are downward compatible in most cases. If you upgrade VMware Server or VMware Workstation, you should also upgrade any separately installed Vix libraries. For instructions, see Installing the VIX API. You should also upgrade VMware Tools to match the product release.

With VMware Server, you can run Vix programs remotely. With VMware Workstation, Vix programs usually run on the host.


64-Bit Library Support

The VIX API provides 64-bit libraries for Linux only. Windows 32-bit libraries may work in 64-bit emulation mode.


Redistributable Code and Sample Code

As noted in the End User License Agreement, the VIX API allows you to build and distribute your own applications. To facilitate this, the following files are designated as redistributable for the purpose of that agreement:

  • VixAllProducts.lib and VixAllProductsd.lib
  • vix.lib and vix.dll
  • vixCOM.dll
  • libvixAllProducts.so
  • libvix.so

Redistribution of the open source libraries included with the VIX API is governed by their respective open source license agreements.

The VIX API also includes sample code, which you can use as a starting point for your own programs. Code is delivered in the Samples directory installed with VMware VIX. A Makefile is provided for Linux, and an nMakefile for Windows.


Installing the VIX API

On the VMware Server or VMware Workstation host, you do not need to install any additional VIX API components. Vix libraries are installed by default under “VMware VIX” or vmware-vix. To compile programs on these systems


To control VMware Server remotely from another machine, you need header files vix.h and vm_basic_types.h, as well as one or more library files. You can get these files in one of two ways: Use the Vix standalone installer to get the files needed to compile a program


Using the Windows Standalone Installer

To install the VIX API files on Windows:

  1. Download the installer program to your Desktop.
  2. Double-click the installer icon to run the graphical installer.

To uninstall the VIX API, go to Start > Settings > Control Panel and use the Add/Remove Programs control panel.


Using the Linux Standalone Installer

To install the VIX API files on Linux:

  1. Download the tar-gzip package. For example:
    wget http://www.vmware.com/downloads/server/VMware-vix-110068.i386.tar.gz
  2. As superuser, extract the package:
    sudo tar zxpf VMware-vix-110068.i386.tar.gz
  3. Change directory and, as superuser, run the VMware installer:
    cd vmware-vix-distrib
    sudo ./vmware-install.pl
  4. Read the EULA and type "yes" if you agree to its terms. You can accept most defaults by typing Enter when prompted.

To uninstall the VIX API, run the vmware-uninstall-vix.pl script. The uninstaller is at /usr/bin/vmware-uninstall-vix.pl by default.


Upgrading an Earlier Installation

If you are using older Vix libraries, VMware recommends that you upgrade those libraries using the standalone installer. The standalone installer provides a current version of the wrapper library, which allows programs to communicate with any Vix library, regardless of version or target architecture. The wrapper library dynamically loads appropriate library files at connection time.

Otherwise you must link your program to a Vix library that matches the server version. This gets inconvenient if your program communicates with more than one version of the server.

VMware Tools in virtual machines should be kept up-to-date with the VMware version on the host. When upgrading, also update VMware Tools in all guest operating systems. The VIX API relies on a current matching version of VMware Tools to perform many operations.

Upgrading the Vix libraries replaces the older header files, vix.h and vm_basic_types.h with newer header files. The header files are installed at the following locations by default:

  • On a Windows system:
    • C:\Program Files\VMware\VMware VIX\vix.h
    • C:\Program Files\VMware\VMware VIX\vm_basic_types.h
  • On a Linux system:
    • /usr/include/vmware-vix/vix.h
    • /usr/include/vmware-vix/vm_basic_types.h

Whether or not you use the wrapper library, your programs may call only the functions supported by the host. If you communicate with an older host, you cannot use newer features.


Sample Vix Programs

On Windows, the sample programs are installed in C:\Program Files\VMware\VMware VIX\Samples by default. An nMakefile is provided to compile all sample programs using nmake and the Visual Studio C compiler.

On Linux, the sample programs are installed in /usr/share/doc/vmware-vix/VMwareVix/samples/ by default. A Makefile is provided to compile all sample programs using make and the GNU C compiler.

Compiling on Windows With Wrapper Library

To use the wrapper library with VIX 1.6, you need Visual Studio 2005 (Visual C release 8.0) or later. To compile code on Windows using the wrapper library, use the following procedure. Files are in the C:\Program Files\VMware\VMware VIX folder.

  1. Add the header file to an include statement in your source code:
  2. #include "vix.h"
    ... program code here ...
  3. Compile for, and link with, the multithreaded version of the C runtime library. For Workstation 6.0.1 and later, you may use either the debug or the non-debug version of this library. For Workstation 6.0.0 and earlier, you must use the non-debug version.
    • To compile and link with the debug version (libcmtd.lib) use compiler options /MTd /nodefaultlib:libcmtd.lib.
    • To compile and link with the non-debug version (libcmt.lib) use compiler options /MT /nodefaultlib:libcmt.lib.
  4. Compile code to link with these files:
    • VixAllProducts.lib for non-debug, or VixAllProductsd.lib for debug.
    • kernel32.lib
    • user32.lib
    • advapi32.lib
    • ole32.lib
    • oleaut32.lib
    • ws2_32.lib
    • shell32.lib

Compiling on Linux With Wrapper Library

This procedure assumes that you have installed Vix components in the default directories. If you made different choices during the installation, specify your directory choices instead.

  1. Add an include statement in your source code for the header file:
    #include "vix.h"
    ... program code here ...
  2. Compile your application, linking to the wrapper library and dynamic load library:
    $ gcc -I/usr/include/vmware-vix vixapp.c -o vixapp -lvixAllProducts -ldl

Compiling on Windows Without Wrapper Library

If you do not use the wrapper, you need to link the appropriate Vix libraries for the VMware product to which your Vix program connects. Workstation 6.5 is able to link a debug version of the C runtime library.

To compile your code for use with Workstation 6.5:

  1. Make the required DLL files available to your program, either by placing them in the same directory as your executable, or by placing them in the system directory (C:\WINDOWS\system32). The easiest option is to copy DLL files from the directory C:\Program Files\VMware\VMware VIX\Workstation-6.5.0\32bit or 64bit.
    • vix.dll (or vixd.dll if you are using debug C runtime library)
    • iconv.dll (or inconvd.dll if you are using debug C runtime library)
    • libxml2.dll (or libxml2d.dll if you are using debug C runtime library)
    • libeay32.dll
    • ssleay32.dll
    • vmcryptolib.dll
    • zlib1.dll
  2. Add the header file to an include statement in your source code:
    #include "vix.h"
    ... program code here ...
  3. Compile your code to link in vix.lib statically.
  4. Compile for, and link with, the multithreaded version of the C runtime library. You may use either the debug or the non-debug version of this library.
    • To compile and link with the debug version (libcmtd.lib) use compiler option /MTd with Microsoft Visual Studio.
    • To compile and link with the non-debug version (libcmt.lib) use compiler option /MT with Microsoft Visual Studio.

To compile your code for use with Workstation 6.0.x:

  1. Make the required DLL files available to your program, either by placing them in the same directory as your executable, or by placing them in the system directory (C:\WINDOWS\system32). The easiest option is to copy DLL files from the directory C:\Program Files\VMware\VMware VIX\ws-2\32bit or ws-3\32bit.
    • vix.dll
    • iconv.dll
    • libxml2.dll
    • libeay32.dll
    • ssleay32.dll
    • vmcryptolib.dll
    • zlib1.dll
  2. Add the header file to an include statement in your source code:
    #include "vix.h"
    ... program code here ...
  3. Compile your code to link in vix.lib statically.
  4. Compile for, and link with, the multithreaded version of the C runtime library. You must use the non-debug version of this library (libcmt.lib) by using compiler option /MT with Microsoft Visual Studio.

To compile your code for use with VMware Server 1.0:

  1. Make the following DLL files available to your program, either by placing them in the same directory as your executable, or by placing them in your system directory (C:\WINDOWS\system32). The easiest option is to copy DLL files from the directory C:\Program Files\VMware\VMware VIX\server-1\32bit.
    • vix.dll
    • ssleay32.dll
    • libeay32.dll
  2. Add the header file to an include statement in your source code:
    #include "vix.h"
    ... program code here ...
  3. Compile your code to link in vix.lib statically.

Compiling on Linux Without Wrapper Library

To compile your code with VMware Server or VMware Workstation installed:

  1. Add an include statement in your source code for the header file:
    #include "vix.h"
    ... program code here ...
  2. Compile your application, linking statically to libvix.so, as in the following examples.
    • To link the VMware Workstation library on a 32-bit machine:
      gcc -I/usr/include/vmware-vix -o vixapp vixapp.c /usr/lib/vmware-vix/Workstation-6.5.0/32bit/libvix.so
    • To link the VMware Server 2.0 library on a 32-bit machine:
      gcc -I/usr/include/vmware-vix -o vixapp vixapp.c /usr/lib/vmware-vix/lib/VIServer-2.0.0/32bit/libvix.so
    • To link the old VMware Server 1.x library:
      gcc -I/usr/include/vmware-vix -o vixapp vixapp.c /usr/lib/vmware-vix/lib/server-1/32bit/libvix.so
Thanks : VMware.com

วันจันทร์ที่ 2 พฤศจิกายน พ.ศ. 2552

Howto automount all my hdd

*First mount all the drives manually.*


then,open the "* Run Application Window *",for this press " *Alt+F2* " to open it.
then write there " *gksu nautilus* ", a window will be appeared and press
the "*up*" button once.

open the file "*mtab* " from " *etc* " folder
here you can see some text like this ,

/dev/sda8 /media/PHOTO vfat rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush 0 0
/dev/sda5 /media/SONGS vfat rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush 0 0

copy those texts and paste it *at the end *of a file named "*fstab*", you
can find the file into the " *etc* " folder.


How to automount all Harddisk on ubuntu

*First mount all the drives manually.*


then,open the "* Run Application Window *",for this press " *Alt+F2* " to open it.
then write there " *gksu nautilus* ", a window will be appeared and press
the "*up*" button once.

open the file "*mtab* " from " *etc* " folder
here you can see some text like this ,

/dev/sda8 /media/PHOTO vfat rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush 0 0
/dev/sda5 /media/SONGS vfat rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush 0 0

copy those texts and paste it *at the end *of a file named "*fstab*", you
can find the file into the " *etc* " folder.

Thanks : ubuntu.com

How to format a thumb drive on ubuntu

First make sure USB thumb drive is not mounted. Click on Places > Computer > Select USB thumb drive > Right click > Select Unmount Volume.

Let us assume that /dev/sda1 is your partition name for USB thumb drive. To format type the following command


$ sudo mkfs.ext3 /dev/sda1


Now use e2label command to change the filesystem label on the ext3 filesystem located on device /dev/sda1:


$ sudo e2label /dev/sda1 usb-thumbdrive


You can also create an MS-DOS/Windows XP file system under Linux, enter:


$ sudo mkfs.vfat /dev/sda1


Thanks : cyberciti.biz

How to format a new hard disk on ubuntu

How to format a new hard disk on ubuntu

Let's get going!

Removing and creating a partition
Having decided your drive's name (let's call it sda) we must now remove the default partition that the manafacturer put there:
Code:
sudo fdisk /dev/sda
This will start fdisk. We want to remove the partion(s), there should only be one.
Press d (for delete).
It might ask you for the partition number, press 1 and enter. If there are more then delete them too.

Now to make a new partition.
Press n (for new), then p (for primary), then 1 and then simply press enter for the next two questions.
This will make a new partition that uses the entire disk. If you want more complex partitioning then read the fdisk manual (man fdisk) or use parted or some other app.
Here's what we did with n, the values will differ from yours:
Code:
Command (m for help): n                                                    
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (197-621, default 197):
Using default value 197
Last cylinder or +size or +sizeM or +sizeK (197-621, default 621): +128M
Now to write the new partion and exit, press w and enter.
You should be ready to make a filesystem now.

Making a filesystem : "Formatting"
You need to put a system in-place, on the disk, such that it can handle files. This is called (unsurprisingly) a filesystem.
The one we are going to use is called "ext3". On Gnu/Linux we are spoiled for choice and there are loads of filesystems you can use, go do some research if you want to.
So, let's make the filesystem:
Code:
sudo mkfs.ext3 /dev/sda1
* Note the 1 at the end, because we are making the filesystem in that partition (thanks Mike)

Now it will go off and do strange stuff, simply wait for it to finish.

Using the new file system
Well, at this point you should be able to right-click on the icon (on your Desktop) and choose "mount" (I assume that's the verb it will present to you). After that you should be able to open a window and use the drive*
* all this assumes it's an external USB drive.
If you cannot then you will need to mount it yourself, try:
Code:
sudo mkdir /media/sda1
sudo mount /dev/sda1 /media/sda1
Note: We are actually mounting the first partition on the drive, hence the 1 at the end: sda1
And the mounted directory can be anywhere you like, but its common location is /media.


Or Use GUI

Install
Code:
sudo apt-get install gparted
sudo gparted
Note: Open from System => Administration => Partition Editor

And Mount your Partition with
Code:
sudo mkdir /media/sda1
sudo mount /dev/sda1 /media/sda1
Note: /dev/sda1 is your new partition

Thanks : ubuntuforums.org || answers.yahoo.com