Cara Rahasia Internetan Gratis Dengan Kartu IM3

Kali ini saya akan tulis postingan yang cukup menarik yaitu Cara Rahasia Internetan Gratis Menggunakan Kartu IM3. Cara rahasia internetan gratis ini sebenarnya sudah banyak diketahui ama orang – orang pinter ( lho, brarti eCHO pinter dunk cool ). ngga juga seh, asalkan kita banyak surfing diInternet lama – lama juga bakal nemuin trik ini.
okeh dekh, langsung yah. ( maaf, mungkin posting kali ini bahasanya sedikit tingkat tinggi lol )
Akses internet gratis menggunakan kartu IM3 tidak perlu software segala macam, hanya saja pengaturan beberapa di modem kita, dan kemudian di sini teman – teman COba :
* Pertama
a. Membuat profil baru di modem Anda dengan nama indosatmms ( ingat bukan indosatgprs !! )
b. Isi Username dengan indosatmms
c. Isi password dengan indosatmms
d. Dengan APN dapat mengisi dengan indosatmms atau indosatgprs
e. DNS diisi dengan: 208.67.222.222 dan 208.67.220.220
* Kedua:
Fase kedua adalah fase input proxy. Caranya, buka Mozilla, pilih menu tool -> Option-> Advance -> Network -> Setting -> Manual proxy. Proxy yang terisi adalah 10.19.19.19 dan pada kolom port diisi oleh 8080.
Gunakan server proxy ini karena aman bebas dari hacker evil.
SELAMAT MENCOBA !! SILAHKAN BERKOMENTAR JIKA BINGUNG !!

How-To: Clone or Copy a VirtualBox Virtual Disk

As a virtual machine environment user, I regularly create ‘base’ images of machines that I can reuse – a base Windows Server 2003 environment, or SQL Server 2005 environment for example. That way, when I need a new machine, I can simply create a copy of the virtual disk and add any additional software I need, saving myself valuable time creating new virtual environments.

With VMWare’s various offerings, copying a virtual disk is easy: copy the disk in Windows Explorer and add it to a newly created VM; VMWare will detect that the disk was a copy and create a new unique identifier (UUID) for the disk before adding it to the VM. Easy and painless. Not so with VirtualBox.

With VirtualBox, copying a virtual disk is a bit of a pain. If you copy the disk in Windows Explorer and try and use it in a new VM, VirtualBox will have a hissy fit and display the error shown below. A bit of a ‘wordy’ way to say that it already knows about this disk, don’t you think?



The publicised way around this is to use the command-line VBoxManage CloneHd tool, however there is another – secret and undocumented – way to clone a disk: the setvdiuuid tool. Lets look at these two methods in detail.

Cloning a Virtual Disk – The ‘Supported’ Method
Cloning a disk is (IMHO) a clunky and Unix-y type way of creating a duplicate disk. We need to invoke the CloneHd command of the VBoxManage tool, supplying the disk to clone and the name of the new ‘cloned’ disk. In its simplest form, you would do something like this at the command-line:

VBoxManage clonehd "DiskToClone.vdi" "ClonedDisk.vdi"

The VBoxManage tool will chug away and clone the disk for you, creating a new UUID in the process:



The cloned disk can now be used on a new VM without incurring the ‘I already know about this disk’ error.

Copying a Disk – The ‘Unsupported’ Method
The alternative to the CloneHd tool is an undocumented option available in VBoxManage – the setvdiuuid command. As the command help states: ‘This is a development tool and shall only be used to analyse problems. It is completely unsupported and will change in incompatible ways without warning’. Because of this, let me add a little disclaimer: I don’t accept any responsibility if you completely destroy your VM using this procedure. Having said that, it appears to work without issue, so I’m more than happy to use it myself – just make sure that you take a backup of you virtual disk before using it if necessary.

To use the tool, simply create a copy of the virtual disk’s VDI file in Windows Explorer; open the Windows command-line and issue the setvdiuuid command for the newly copied disk:

VBoxManage internalcommands setvdiuuid "CopiedDisk.vdi"

The tool will create a new UUID and assign it to the disk:



The new copied disk can now be used on a new VM without incurring the ‘I already know about this disk’ error.



Read more: http://www.modhul.com/2009/06/17/how-to-clone-or-copy-a-virtualbox-virtual-disk/#ixzz0waZGAv3p

http://sentientmobile.com/jshaw/blog/post/2009/08/26/Running-VirtualBox-on-a-Windows-Vista-bootcamp-partition-in-Mac-OS-X.aspx

VirtualBox is an open-source virtualization software from Sun much like VMWare and Parallels, but free for personal use!  I just tried it out on my Mac OS X to run a Windows Vista VM on a physical Windows Vista partition created through bootcamp, and thought I'd share my experience (and to write down for myself for future reference :)).  

I had googled and found someone doing very similar thing on a Ubuntu machine.  Most of the info is pretty relevant on a Mac OS X as well, except that I couldn't use the solution of assigning my user account to the "disk" group; there's no "disk" group on Mac OS X.  The other solution mentioned of changing permission works however.  Here's exactly what I did:

0. Read the relevant part of the VirtualBox User Manual regarding using raw partition ("9.10.2 Access to individual physical hard disk partitions").

1. Locate the device and partition holding your Windows Vista partition (e.g, using "df -k" command):

jshawsworlds-macbook:~ jshawsworld$ df -k

Filesystem    1024-blocks     Used Available Capacity  Mounted on

/dev/disk0s2     73269248 31999364  41013884    44%    /

devfs                 110      110         0   100%    /dev

fdesc                   1        1         0   100%    /dev

map -hosts              0        0         0   100%    /net

map auto_home           0        0         0   100%    /home

/dev/disk0s3     82685740 56175456  26510284    68%    /Volumes/Untitled

/dev/disk1s1        15632      144     15488     1%    /Volumes/CANON_DC

/dev/disk2s1    334784000 46614707 288169292    14%    /Volumes/My Book

/dev/disk2s2    153600000 29766376 123833624    20%    /Volumes/Mac OS Partition 2

For me, for example, I know the Windows partition is /dev/disk0s3.

2. Back up your existing Windows Vista partition, to a external drive for example, since you might damage the Windows paritition in this exercise and render it unusable!  One free tool I find pretty reliable in backing up and restoring Windows partition is winclone.

3. Change to root to do the next few commands:

sudo su

You may need to enable root user by going to the "Directory Utility" app, click on the lock icon, and then Edit->Enable Root User.

4. Unmount the Vista partition in Mac OS X if you currently have it mounted, since we don't want VirtualBox accessing it at the same time that Mac OS is accessing it:

umount /dev/disk0s3

and make sure it has been unmounted (i.e.,  the directory /Volumes/Untitled is empty in my case).

5. Change the device to read/write, which is needed by VirtualBox as stated in the user manual:

chmod 666 /dev/disk0*

Note that you have to change permission for all of disk0, not just the Windows parition (hence the "disk0*"), since createrawvmdk needs to access disk0 as well as disk0s3.

6. Run the command

VBoxManage internalcommands createrawvmdk -filename /Users/jshawsworld/WinVista.vmdk -rawdisk /dev/dev0 -partitions 3 -relative

7. Finally change the owner to your user account for the vmdk file you just created as root, so you can access it as yourself when running VirtualBox later:

chown jshawsworld /Users/jshawsworld/*.vmdk

8. Run VirtualBox from Finder, and browse to the vmdk file. 

9. Make sure that "IO APIC" and "VT-x/AMD-V" in your Virtual Machine Settings are both on, and then start the VM.  It should start.

Even though I got it working, it was painfully slow..., even after giving it 2 GB of memory.  I had tried VMWare Fusion to do the same thing before, and remember it wasn't any faster.  To really work efficiently in Windows I think booting to it via bootcamp is still the way to go.  XP might be faster; who knows maybe Windows 7 will be much faster.  For light-weight OS's (like Linux) running it as a VM is definitely the way to go.

How To Convert VMWare Image (.vmdk) to VirtualBox Image (.vdi)

I’ve found more and more people are switching to Virtualbox these days and I keep running into the same question.  ”How can I convert my VMware images to Virtualbox images?”  Well, breath easy because it is possible and not very difficult!

There are two methods that I am aware of that will allow you to use your VMware images on Virtualbox.  The first method I’ll outline uses the graphical Virtualbox interface and the second uses the command line. Each method should be equally as stable, it simple depends on your preference.

Method 1

Start Virtualbox
Inside the Virtualbox Menu click: File > Virtual Media Manager
Click on the “Add” button.
Locate and select the VMware .vmdk file you’d like to convert.
Click Open.
Verify your disk image has been added to the list of images and that the virtual and actual sizes appear accurate.
Click OK
Create a new virtual machine profile, selecting your imported image for the storage.
Boot your new virtual machine.

Method 2
To use the second method we’ll need an addition command-line tool called qemu.

sudo aptitude install qemu

You’ll new be able to convert a .vmdk (VMware image) to a .bin format, which can then be converted to a Virtualbox native .vdi format.

qemu-img convert /path/to/original.vmdk converted.bin

You’ll then need to use the VBoxManage utility that comes with Virtualbox to convert the .bin to a native .vdi format:

VBoxManage convertdd converted.bin converted.vdi

You can now create your new Virtualbox machine profile, using this new .vdi file as your disk image.

Two methods for converting VMware images to Virtualbox images.  Are there any other methods that you can suggest, or have you had better experience with one or the other?  Let us know!