Saat ini dua operator besar sedang bertarung dalam rangka memasarkan produk mereka yaitu koneksi internet unlimited menggunakan jaringan 3G amupun HSDPA.
Hal ini diawali oleh Telkomsel dengan melaunching Telkomsel Unlimited pada bulan Mei 2008. Kemudian disusul oleh Indosat dengan 3.5 Broadband Unlimited pada bulan September 2008.
Telkomsel memberikan tarif untuk paket Basic Rp. 125 ribu (tanpa modem) dan Rp. 250 (dengan modem kontrak setahun). Sedangkan Indosat memberikan tarif di paket Basic menjadi Rp. 100 ribu.
Dari pertarungan tersebut kita bisa melihat masih banyak persoalan yang masih mereka belum tangani. Mash ingat ketika awal-awal masa perkembangan selular. Isu utama yang dilontarkan adalah masalah Coverage (jangkauan), kemudian disusul dengan isu “Tarif Murah”, dan akhirnya sekarang menyusul “Internet Murah”. Entah ada isu apalagi di kemudian hari. Apa mungkin kita bisa menelpon ke mana aja tanpa di kenakan biaya sepeserpun alias gratis? Kalau itu bisa terwujud kita mungkin akan senang. Tetapi, mungkinkah murahnya tarif akan sejalan dengan kualitas layanan yang mereka berikan. Kita tunggu saja tanggal mainnya.

Beberapa hari yang lalu aku mendapatkan kiriman CD Instalasi Open Solaris dari Sun Microsistem. Udah lama aku pesen lewat internet.

Namun pas dicoba berulang kali, ternyata belum bisa jalan nih di kompi ku. Ada-ada saja pesen yang timbul, mulai harus masukin password lha. Padahal kan harusnya gak mesti pake.

Kemudian aku ganti menggunakan DVD ROM adik ipar karena memang DVD ROM punyaku lagi masalah. Tapi pas dicoba malah beda lagi perilakunya. Sistem termenung seribu bahasa.

David Eliott has just released a new version of his modified boot-132 bootloader.
One of the new things it can do is to load kexts from an .img file which contains kexts (or even an mkext) and boot Leo.
That means you can have two mkexts, one folder with kexts on the .img file and the folder with kexts from your installed system
or even two folders with mkexts.
How does it work?

Basically, you create a flat dmg with the kexts in a folder and the bootloader will load them for you. This means quite a lot;
you can boot from a retail Leo DVD and install it, you can update straight from apple, you can reinstall and not have to add
the same kexts to your install every time. The bootloader behaves like the linux kernel: you can use an mboot (a patched syslinux
was used) compatible bootloader which tells to boot-dfe about the .img file (the ramdisk or initrd, as it’s known by the linux users)
and boot-dfe is going to use the kexts (or mkext) from it.
What does it do?

This new boot-dfe has been tested with the retail Leopard DVD and it can boot, install and run Leopard without having to build
a modified DVD.

Infos about hardware:

[OFF]: Vanilla = Original Mac OS X DVD or Mac OS X Installation with running original mach_kernel.

AMD systemz isn’t supported.
To use Mac OS X Vanilla DVD needs a Intel “Mac” closer systemz, like a Intel Core processos and Intel Chipset. This is only combination supported by “Vanilla Installz”, other processors and chipsets isn’t supported by “Mac OS X Vanilla systemz”

You *can* boot and install retail on any SSE2 or better Intel pre-Core architecture systems, but you wont be using the vanilla kernel. See below for link

This is how it’s done: you burn an ISO (which has the bootloader on it) to a CD/DVD, after it gets to the boot
prompt, you press ESC or ENTER and it prompts for a new BOOT DEVICE, you swap the BOOT CD/DVD with the LEO Retail DVD, you press
enter and it shows you the name of the bootable partition from the DVD, you press enter and Leo starts to load.

Quick resume about “oh, what to do now?”

#1 – Burn .iso on a CD;
#2 – Boot this CD;
#3 – When Darwin prompt appear, eject CD and put Mac OS X Leopard Retail DVD;
#4 – Press enter (or -v and enter…wherever…)
#5 – After install, boot using CD boot again and install .kext needed…and usual files.
#6 – Done!

For the time being, you cannot have this bootloader on an USB stick and have it boot the Retail Leopard DVD. The reason why this
happens is related to the way the BIOS handles DVDs and optical media: there’s no BOOT DEVICE associated with an optical drive
which the BIOS has not booted from. Basically, this is like the disk swap trick known to the PlayStation gamers.
You can already put this on an USB stick/CD/DVD and boot a vanilla install (vanilla= no added kext, no replaced kext on the partition).

As usual, this only works for compatible machines(that means you still can’t boot a vanilla system on AMD, they need specialised patches).

What are you going to do in the future?

David Eliott said he’d merge some of the things from Chameleon into boot-dfe. Those involved in the development of Chameleon will merge
the support for ramdisks into Chameleon and more effort will go into making the distribution 100% legal.
Work might(read: should, in the very close future) also go into making Chameleon boot the Retail DVDs when loading the bootloader from the HDD.

User guide and link to the ISO

This ISO needs to be modded (add dsmos to the Extensions folder) in order to be able to boot Leo.

Credits for this go to:

David Eliott: for modding boot to allow us to boot from Retail Leopard DVDs;

Kabyl: for modding boot to allow the usage of a separate folder on the disk and merging features from Chameleon to boot-dfe-146;

bumby: for compiling syslinux and figuring out how to build the ISO;

ToH and HMBT: tests and improvments;

Superhai, STiCKpIN: for good methods and research day-by-day;

Patched ‘boot’ file supporting JMicron, Boot.plist and device-properties strings: here

Download .ISO Original with project kexts (all your need is here – noobs try this first): http://www.mediafire.com/?uwd9dtttjfk

Download .ISO with modified kexts: http://www.mediafire.com/?1ne1zbl4znv

Superhai Method to edit image: http://forum.insanelymac.com/index.php?s=&…st&p=803725

STiCKpIN *NEW* Method to boot from USB Stick (needs Windows): http://forum.insanelymac.com/index.php?showtopic=115064

HMBT Auto-Patch for edit image (Beta): http://homepage.mac.com/f41qu3/.Public/CDBoot_RC2.sh

Chameleon for Hard Disk: http://tinyurl.com/6je4eh

If you had problems, need advice, and other help type, go here: http://forum.insanelymac.com/index.php?showtopic=114651

Boot Retail Leo and Vanilla installs on Intel SSE2 and better – Boot 132 on pre-Core !, It is possible to boot the retail Leo DVD on Pentium 4-class CPUs: http://forum.insanelymac.com/index.php?showtopic=123841

Cheerz,

Sumber

*** SSE2 & SSE3 Intel owners, you CAN boot the retail Leopard DVD! ***

Latest News: I posted a guide on how to install patches/kernels to the hidden EFI partition: here

(Older posts on this subject, leading up to me actually getting it to work are archived here)

As we all know, dfe’s excellent modified Boot-132 bootloader allows us to place extra kernel extensions on a ramdisk, which can be used to boot the retail Leopard DVD on Core architecture PCs. An amazing milestone in OSx86 history, as i’m sure we all agree.

But what exactly is required to run the retail Leopard DVD and the so-called vanilla (ie Apple-supplied) kernel? Why can’t my Pentium D run it?

It turns out the kernel performs an explicit check for the CPU ‘family’. Only processors in ‘Family 6′ (or P6 processors) are permitted to boot. Pentium 4 and its derivatives (including Celeron D and Pentium D) are in Family 7 (P7).

There are a whole bunch of intel CPUs in the P6 family, but only Core Solo and above have SSE3, thus effectively limiting the kernel to Core processors.

64-bit operation adds another level of complexity – the only implementation of a certain routine in the kernel code (bcopy) in 64-bit mode uses SSSE3 (Supplemental SSE3), which – again – only Core and better CPUs have.

The upshot is that my machine *requires* a patched kernel to boot. The changes needed are fairly minimal, but as it stands my machine cannot run the kernel which is on the retail Leopard DVD.

Thus my thoughts turned to another approach – can I specify the ‘extra’ kernel extensions *and* a kernel, and have the machine boot from the DVD? I emailed dfe to ask if this is something he could add support for, only to discover it was already possible:

QUOTE

Hi Munky,

If you look slightly more closely at the code you’ll realize that it names the ramdisk rd(u,p) just like hard drives are hd(u,p). So it already works to do something like rd(0,1)/mach_kernel.custom assuming you have a file mach_kernel.custom in the root of the ramdisk and the partition is numbered 1. I think partition numbers start at 1 so you should be ok with that. If not try 0.

It’s been a while since I did this but I remember it working fine. That is, you simply enter the full path to the kernel on the boot command-line followed by any options.

Enjoy,
-Dave

This led me to perform a whole bunch of experiments to try to get my Pentium D to boot the retail DVD. See here for the blow-by-blow account of me getting this to work

Ok munky, get to the damn point. Where’s the beef?

Heh.. ok, well here’s what i’ve managed so far:

- Booted the retail DVD from a modified boot-132 CD.
- Installed successfully to a fresh partition on a GPT disk.
- Booted the installed partition and completed setup, again by booting from the boot-132 CD.

To boot, you need to place a suitable patched kernel in the root of the ramdisk image (initrd.img), and at boot time, after typing in the two-digit code to boot the Leopard DVD (or your hard disk partition), you boot thus:

rd(0,1)/mach_kernel.patched -legacy boot-uuid=<uuid of boot device>

OR

rd(0,1)/mach_kernel.patched -legacy rd=diskXsY

So, to break that down:

rd(0,1) refers to the ramdisk, so rd(0,1)/mach_kernel.patched is how we’re specifying the kernel to boot.

-legacy is needed if the kernel cannot operate in 64-bit mode. the kernel i have been testing with is an experimental pre-release kernel and still has SSSE3 routines in the 64-bit code, so I have to force 32-bit operation.

boot-uuid=<uuid> or rd=diskXsY – this is the real trick. specifying a kernel on a different device causes the boot sequence to switch the ‘root’ device to the device which holds the kernel. trying to boot without specifying the uuid or root device (rd) will cause mach to try to boot from the ramdisk itself. this is obviously not what we want. so you need to specify the uuid or the correct bsd address of the device you want to boot – the Leopard DVD or the installed partition.

Remember, this is all down to dfe and his cunningness, and his helpfulness and patience in assisting me. Thanks dfe!!!

** This functionality is coming to a Chameleon release very soon. Once Chameleon supports this approach, this project will be retired. Thanks to everyone who uses this bootloader, thanks for the support and the kind words **

- v5.1 fixes an error in the packaging – in v5, ‘boot’ was the v5 version, but ‘boot-turbo-munky.bin’ was still v4.
- v5 has updated FSB detection code from Chameleon
- Basic dual booting is possible. Just hit esc at darwin bootprompt and enter 81 for 2nd drive, 82 for 3rd…
- v4 now supports JMicron ATA
- v3 now supports Boot.plist on the EFI partition
- v2 now supports device-properties (aka EFI Strings) in com.apple.Boot.plist !

A *BIG* thank u to Chameleon team for sharing their great sources – porting was a cinch!

The release of dfe’s amazing boot-132 loader was an eye-opener for many of us in the community. The fact we can boot the shrink-wrapped, unmodified retail Leopard DVD on modern Intel machines (and, it turned out, on any SSE2 or better Intel machine) means we have the ability to boot a totally unmodified OS X. (The install DVD of course boots into Mac OS X).

However, it seemed most people didnt realise the gravity of this, or simply thought ‘oh thats nice, use retail to install. ok, back to hacking in /System/Library/Extensions….’.

This is, imho, the wrong approach.

The *right* approach is to leave /System/Library/Extensions alone, and apply patches and modifications to the system from a different vector, just like boot-132.

This is, in my humble opinion, the ultimate hackintosh install method.

What benefit does that give you?

* Well, how about trouble-free Software Update direct from Apple? Even on SSE2 Intels? (and AMDs when Voodoo 9.5.0 final comes out…)

* How about being able to completely erase and reinstall the OS without breaking ur carefully-assembled patches?

* How about being able to boot *the same disk* on a real mac and your hack?

* How about having a com.apple.Boot.plist completely outwith the installed OS?

all without losing the usual EFI strings goodness you’ve come to expect from a bootloader… (Thx to Chameleon team!)

So munky, where’s the beef?

Well first, a little history…

When you format a GPT (GUID Partition Table) disk in Disk Utility, there is always a hidden, 200Mb partition created as the first partition on the disk. This is supposed to be a 200Mb FAT-32 partition used for storing EFI drivers, and is mandated by the EFI / GPT specs.

Apple honours the specs and so puts the 200Mb partition there. However, (and this is the important part…) *Apple dont use it!*

So we can hijack it and use it for our own ends.

You’re still not getting to the point…

Ok ok. So here goes. We repurpose the EFI system partition to hold our kexts (and, if necessary, kernels) so we dont have to change the main installation. AT ALL.

The nice thing is that Mac OS X and Disk Utility (at least the graphical version) will continue to hide the EFI partition, as you’re not supposed to see it. But you also have the option to mount it if you need to make changes. And, of course, on ALL systems (currently Intel SSE2 and better), Software Update can be used without much chance (if any) of breakage.

Hmmm… ok i’m sold. So how do I do it?

Well, first grab the attached zip file. This contains a modified version of boot0 from chameleon, the unmodified boot1h from chameleon, and a fork of dfe’s boot2. boot0 has been changed to look for the EFI system partition, and boot2 has been modified to load extra kexts from the EFI partition.

Warnings, Pre-Requisites

*** YOU’RE DOING THIS AT YOUR OWN RISK BTW. Dont bitch at me if your computer explodes and kills your cat. ***

You are probably best to try getting your system to boot a retail disc with boot-132 before you attempt this method. Getting it to work with boot-132 is good practice for maintaining a ‘patches-free’ system, and will give you a good idea of the kexts you’ll need for your particular system.

NB: YOU CANNOT USE ANYTHING OTHER THAN A RETAIL DVD. Dont try a restore or drop-in disc, they WILL NOT WORK.

Another BIG NOTE: existing chameleon, pc-efi etc bootloaders can seriously mess this up. If you have problems please try with only one hd attached and make sure u *completely destroy* the existing partitions before install.

In the following guide, i’ve used the convention of diskXsY. Please understand, you should NEVER type diskX or diskXsY – X and Y are placeholders and need to be replaced with proper values. On most systems installed to the first hard disk, this will be disk0. Partition 1 on any GPT disk formatted by Disk Utility will be the 200Mb EFI partition. So in most cases, we’ll be talking about disk0, rdisk0 and disk0s1.

Finally, please make sure you read and re-read this guide before starting. If you are unsure about any of the steps, then my advice is DONT DO IT. Wait for someone to turn these set of instructions into an easy-to-use installer or something.

Finally, the beef!

So, best practice is to use a boot-132 disc and install a fresh Leopard installation onto a GPT disk from retail. Lets call this ‘Phase 0′. You find or create a boot-132 disc capable of booting to the installer from a retail Leo disc on your particular setup. Go into Disk Utility from the menu and partition one of your drives as GUID Partition Table type and create at least one partition big enough for Leopard. Look elsewhere for questions about boot-132 (like the links above). This guide assumes you can, and have, booted the retail Leo disc and installed to a GPT disk.

Once you’ve done that, boot into your new install via boot-132, and do the following:

Phase 1: Reformatting the EFI System Partition.

1) Open Terminal

2) sudo -s (and type in your password)

3) diskutil info / | grep Identifier – this tells you the values for diskXsY for ‘/’, which is the currently-booted system. (If you’re doing this on a disk other than the one you’ve booted from, you need to modify accordingly.)

4) diskutil list – diskXs1 should be called EFI. this is the hidden EFI partition on your target drive.

5) diskutil eraseVolume “HFS+” “EFI” /dev/diskXs1 – now, be *VERY* sure this is the correct drive. this will format the EFI partition as HFS+. (NB After erasing it will try to mount it, but will fail with “Could not mount disk0s1 with name after erase”. Ignore this).

Phase 2: Installing the modified bootloader.

1) Extract the attached zip file to a directory (Safari might do this for you).

2) in terminal, cd to that directory (the one containing boot0, boot1h, boot-turbo-munky.bin and fdisk)

3) ./fdisk -f boot0 -u -y /dev/rdiskX – this puts the stage 0 bootloader onto the target disk

4) dd if=boot1h of=/dev/rdiskXs1 – this puts the stage 1 bootloader onto the target partition (EFI partition)

5) mkdir /Volumes/EFI

6) mount_hfs /dev/diskXs1 /Volumes/EFI

7) cp boot-turbo-munky.bin /Volumes/EFI/boot

8) cp update.sh /Volumes/EFI/

Phase 3: Make the disk bootable

This stage may not be necessary on some boards, but on my Intel board and Bad Axe boards it is. If you skip this step and your system wont boot, try doing it. That said, doing this on boards which DONT need it will do no harm so my logic is do it anyway.

Type the fdisk command and then each line as shown:

1) ./fdisk -e /dev/rdiskX (NB: Ignore any fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory error)

2) f 1

3) w

4) q

Phase 4: Setup your new bootloader EFI partition

1) Setup directory tree:

mkdir -p /Volumes/EFI/System/Booter
mkdir /Volumes/EFI/Extensions
mkdir /Volumes/EFI/.fseventsd

2) touch /Volumes/EFI/.fseventsd/no_log – this prevents the File System Events Daemon (fseventsd) from logging on this volume, which can cause the EFI partition to become unmountable.

3) copy necessary extensions into /Volumes/EFI/Extensions (eg:

cd <directory containing kexts>
cp -R *.kext /Volumes/EFI/Extensions)

4) if necessary, copy patched kernel into /Volumes/EFI/ (eg:

cd <directory containing the wonderful Voodoo kernel)
cp mach_kernel.voodoo /Volumes/EFI/

5) cd /Volumes/EFI
chmod +x update.sh
sudo ./update.sh – this will build a kextcache in /System/Booter. Please check update.log for any errors. (Dependency warnings are ok and normal – the dependencies will be available at boot time from /System/Library/Extensions).

6) umount /Volumes/EFI (If this fails, do umount -f /Volumes/EFI).

7) rm -rf /Volumes/EFI

8) If your machine cannot use the vanilla kernel, at this point you must take a note of your install’s UUID. Open Disk Utility.app and click on the partition containing your fresh install. Click the blue ‘I’ information icon and look for Universal Unique Identifier. This should be a fairly long hex string. Write this down somewhere on a piece of paper. (not in a text file on the computer!)

You should be ready to boot at this stage.

Phase 5: Test boot!

So this differs slightly depending on whether you have a Core cpu or not – that is, whether you can (or choose to) run the vanilla kernel or a patched kernel.

If you boot the vanilla kernel, you should just have to press Return, as the bootloader should find your installed OS.

If you boot a patched kernel, the magic you need is this:

bt(0,0)/mach_kernel.voodoo -v boot-uuid=<the install’s uuid you wrote down earlier>.

With a bit of luck, you’ll boot up into your nice shiny new Leopard install, and be able to use Software Update without worrying.

Phase 6: Post-Install – Kexts, EFI strings, Boot.plist, Troubleshooting

Kexts:

So you booted back up, but you maybe dont have gfx support, or are missing some nice LAN kext… To mount EFI:

sudo -s
mkdir /Volumes/EFI
mount_hfs /dev/diskXs1 /Volumes/EFI

to install new kexts:

sudo -s
cd path/to/kext
cp -R Blah.kext /Volumes/EFI/Extensions
cd /Volumes/EFI
./update.sh

EFI Strings and com.apple.Boot.plist:

v3 of the bootloader supports a com.apple.Boot.plist file located on the EFI partition. You can place this in either of these two locations:

/Volumes/EFI/com.apple.Boot.plist
-or-
/Volumes/EFI/Library/Preferences/SystemConfiguration/com.apple.Boot.plist

Its your choice, and it makes no difference. If you have both it will favour the one in /Library/Pref…..

This is, of course, the place to put EFI strings – aka device properties – strings. This bootloader supports EFI strings in the same format as Chameleon expects them.

Troubleshooting

If you ever get ‘mount_hfs: Invalid argument’ when trying to mount the EFI partition, do this to fix it:

fsck_hfs /dev/disxXs1.

*** Always unmount the EFI partition before rebooting, to stop this happening! umount /Volumes/EFI! ***

Notes

On my system (a Pentium D920 currently, though after tomorrow it’ll be a Core 2 Duo), there is actually one modification to the installed system, and that is the com.apple.Boot.plist file. I simply couldnt be bothered typing out the uuid every time I booted the machine, so I put my boot parameters into that plist file. v3 supports a com.apple.Boot.plist on the EFI partition

I also have a vanilla installation on a USB drive which I share between two real macs (my home MacBook Pro and my work MacBook Pro) as well as my hack. I have the necessary kexts and kernels on the EFI partition (remember, the real macs ignore this partition), and to boot it on my hackintosh, i just have to type in the correct parameters for booting, ie:

bt(0,0)/mach_kernel.voodoo boot-uuid=<blah>. v3 supports com.apple.Boot.plist on EFI.

One thing – you can actually use rd=diskXsY to specify the boot device. I prefer using boot-uuid because that wont break if I change the configuration of hard disks on my machine, whereas the diskXsY values could.

Another thing, for pre-Core users, please keep the relevant System.kext on the EFI partition for the kernel you wish to use. For example, my hackintosh has mach_kernel.voodoo (9.4.0 kernel for 10.5.4), and the 9.4.0 (10.5.4) System.kext in /System/Booter/Extensions.mkext. These are used in preference to the kernel and System.kext on the installation, which are both vanilla 9.5.0 (10.5.5) versions. This means USB mounting etc wont break.

Dual- Triple- Quadruple-…. Booting!

Since this bootloader is based on dfe, you can hit escape at the darwin boot prompt and enter a new bios device id to boot from. If you have a 2nd hard disk with Windows, you can hit esc, type 81 and enter, and it should show the darwin prompt with ‘Foreign OS’. Hit enter to boot Windows

Background Reading

If this stuff is new to you, or you’re having trouble following, please read these threads first:

http://forum.insanelymac.com/index.php?showtopic=113288

http://forum.insanelymac.com/index.php?showtopic=123841

http://forum.insanelymac.com/index.php?showtopic=123313

Source Code

I thought i’d better post on the subject of ‘wheres the source?’. At this time, while I could obviously make my own changes available, I need to speak to the other dude who directly worked on this to ask if he’s ok about his work being released. I can’t see there being a problem, but since its his work and not mine, im not about to release without his express permission.

I hope to have this resolved very soon and post a complete diff. The basis for this diff is dfe’s revision 146 stage2 bootloader (aka boot-132) code, which is in turn a diff from some old apple sources.

(So that means if you take apple’s source, apply dfe’s diff, apply the other dude’s diff and then apply my diff and you’ll have the source for the v3 binary posted here. Sheesh!)

Changelog and Downloads

v1 is the original bootloader, comprising Turbo’s changes to the dfe bootloader. Deprecated by v2
v2 supports EFI strings in com.apple.Boot.plist. apply them in chameleon style – ie <device-properties> tag. Deprecated by v3
v3 supports a com.apple.Boot.plist on the EFI partition (in root or in /Library/Preferences/SystemConfiguration), boots faster, and integrates the update.sh script
v4 supports JMicron and other ‘troublesome’ ATA
v5 adds the improved FSB detection code from Chameleon
v5.1 is a repackaging of v5 to correct a misnamed file. No other changes.
Attached File(s) efi_boot_v5.1.zip ( 60.29K ) Number of downloads: 1228

Reboot, hit F8, and enter -s

After pressing enter, you’ll eventually end up at a command line.

Code:

/sbin/fsck -fy /sbin/mount -uw / touch /var/db/.AppleSetupDone passwd root

…and enter a new password.

This will at least get you into osx, though you’ll be running as the “root” administrator account… which is always recommended you don’t use.
(I believe you can use the “adduser” command if you’d like to setup a proper account)
You also will have skipped all of the configuration, so you’ll be forced to use US English on a QWERTY keyboard,
you will not be able to migrate your old account off another mac, you may not be able to setup networking manually….
But at least you’ll be able to log in!

Halo pada posting kali ini saya akan menjelaskan tutorial langkah demi langkah cara membuat program berjalan otomatis pada waktu startup di Ubuntu. Pada tutorial ini saya akan memberikan contoh membuat program Avatar Window Navigator (Program yang berupa dock toolbar yang biasanya terdapat di sistem operasi Macintosh. Saya akan memberikan tutorial cara menginstall program ini di lain hari) berjalan secara otomatis pada waktu startup.

Tutorial ini juga dapat diterapkan untuk membuat suatu program berjalan secara otomatis pada waktu startup Ubuntu, karena pada intinya cara membuat suatu program berjalan secara otomatis di Ubuntu adalah sama. Bagi kamu yang ingin mengetahui program Avatar Window Navigator di Ubuntu dapat melihat gambar dibawah ini. Pamer sedikit ga papa kan

Oke berikut ini merupakan tutorial langkah demi langkah membuat program Avatar Window Navigator berjalan secara otomatis pada waktu startup di Ubuntu.

• Piih menu System->Preferences->Sessions.
• Pilih tab startup programs dan klik tombol Add seperti yang ditunjukkan pada gambar dibawah ini

• Pada Window Add Startup Program isikan name, command, dan comment. Point terpenting disini adalah command. Jangan sampai kamu salah memasukkan command milik program lain. Karena saya ingin membuat program Avatar Window Navigator berjalan secara otomatis maka saya memasukkan command avant-window-navigator. Setelah itu klik tombol Ok. Supaya lebih jelasnya coba perhatikan gambar dibawah ini

Bagaimana bila kamu tidak hafal command untuk program yang mau dijalankan pada waktu startup Ubuntu ?. Caranya gampang sekali. Berikut ini tip untuk mengetahui command suatu program di Ubuntu.

• Pertama pilih System->Preferences->Main Menu.
• PIlih categori dimana menu program kamu berada. Pada kasus Avatar Window Navigator, saya memilih categori Accessories karena menu program tersebut berada pada categori tersebut.

Langkah berikutnya klik kanan pada menu program yang mau dijalankan pada waktu startup dan pilih sub menu properties. Apabila bingung coba perhatikan gambar dibawah ini

Copi textbox command pada window Launcher properties dan pastekan pada text box command pada window add startup program

Oke sekian saja posting saya kali ini. Selamat mencoba dan good luck

Sumber: http://www.kaplinglinux.com/

Make Your Linux Desktop Look Like A Mac – Mac4Lin Project Documentation

Akhirnya dengan perjuangan yang sangat melelahkan, aku bisa install Ubuntu menggunakan face nya Mac OS X Leopard. Gogling sana sini akhirnya bisa membuahkan hasil.

Tampilan ubuntu rasa apel di desktop saya.

Di bawah ini akan ditapilkan tata cara nya:

Revision 1.1
1 November, 2007
Mac4Lin Guide Copyright Anirudh, 2007
Developer: Anirudh (infra_red_dude)
Website: http://sourceforge.net/projects/mac4lin

Do you want to give your desktop a dash of Mac OS X? Do you want to change your GNOME desktop from the default look to something like this?

Then read on…..

The goal of this project is to bring the look and feel of Mac OS X (latest being 10.5, Leopard) on *nix GTK based systems. This document will present the procedure to install Mac4Lin pack & tweak certain things to get that almost perfect Mac OS X like desktop.

NOTE: Backup all files before deleting/replacing the original ones. Nobody can be held responsible for any loss of data that may occur when installing and/or during usage. This guide holds good for all versions of Mac4Lin. For version specific information please see the README file for each component (if any). Also see the changelog file for changes in that version. Compiz in this guide refers to Compiz-Fusion. Unless explicitly specified, the installation procedures apply to all versions of GNOME.

Download all the Mac4Lin .tar.gz files from the latest release & except the Icon themes extract all other files to a temporary folder .

1 Applying GTK Metacity Theme

GNOME 2.20

Goto System > Preferences > Appearance. Click Install. Browse and choose the Mac4Lin GTK Metacity Theme .tar.gz file (wherever it is extracted).

After the installation is confirmed click on ‘Apply new theme’.

GNOME 2.18

Goto System > Preferences > Theme > Customize > Control. Click Install. Browse and choose the Mac4Lin GTK Metacity Theme .tar.gz file (wherever it is extracted). Select to Apply.

Also make sure that the Window border is set to the Mac4Lin theme. Click on the Window border and select the Mac4Lin GTK theme.

For both GNOME 2.18 & 2.20

To set Leopard like GNOME panel background right click on an empty area on the top panel and select Properties. Now goto the Background tab and click on the Background image radio button. Navigate to /home/<user name>/.themes/<Mac4Lin GTK theme folder>/gtk-2.0/Panel and select the image you like, to be set as background for the GNOME panel.

The following is only for those who do not use Emerald theme manager:

To shift the traffic lights (close,min,max buttons) to the left of the title bar goto a terminal windows and type:

gconf-editor

and press Enter. Now navigate to: apps>metacity>general. On the right double click ‘button_layout’. Delete that & type: ‘close,minimize,maxmize:menu’ (without quotes). Press OK and then quit. The buttons will now be on the left side of titlebar.

To restore the original layout, just replace the string by ‘menu:minimize,maximize,close’.

2 Applying GTK Icon Theme

GNOME 2.20

Goto System > Preferences > Appearance. Click Install. Browse and choose the Mac4Lin Icon Theme .tar.gz file (wherever it is extracted). Be sure to select the correct icon theme, the GNOME 2.20 ONLY version.

After the installation is confirmed click on ‘Apply new theme’.

Memang agak ribet sih untuk install printer di Linux amd64 karena kebanyakan driver hanya mendukung i386. Untuk Instalasi biasa ( menggunakan Processor Intel ) -i386, anda bisa mengikuti / membaca tips sebelumnya
Instal Printer i255 in Linux

Untuk instalasi drivernya , ada tambahan perintah :

sudo dpkg -i –force-all bjfiltercups-2.3-0.i386.deb
sudo dpkg -i –force-all bjfilteri255-2.3-0.i386.deb

Untuk Printer Lainnya tergantung paket deb yang ada, misalnya untuk ip1880 menggunakan perintah :

sudo dpkg -i –force-all cnijfilter-common_2.70-2_i386.deb
sudo dpkg -i –force-all cnijfilter-ip1800series_2.70-2_i386.deb

Lalu lakukan pengecekan shared library yang digunakan

Untuk i255

ldd /usr/local/bin/bjfilteri255

Untuk ip1800

ldd /usr/local/bin/cifip1800

Jika ada library yang belum ditemukan, lakukan symbolic link ( seperti membuat shortcut kalau di Windows )
Kalau di t4 saya , ada 2 library yang belum ditemukan yaitu :

linux-gate.so.1 => (0xffffe000)
libcnbpcmcm312.so => /usr/lib/libcnbpcmcm312.so (0xf7eea000)
libcnbpess312.so => /usr/lib/libcnbpess312.so (0xf7ea2000)
libm.so.6 => /lib32/libm.so.6 (0xf7e7c000)
libdl.so.2 => /lib32/libdl.so.2 (0xf7e78000)
libtiff.so.3 => not found
libpng.so.2 => not found
libcnbpcnclapi312.so => /usr/lib/libcnbpcnclapi312.so (0xf7dfd000)
libcnbpcnclbjcmd312.so => /usr/lib/libcnbpcnclbjcmd312.so (0xf7df8000)
libcnbpcnclui312.so => /usr/lib/libcnbpcnclui312.so (0xf7df1000)
libpopt.so.0 => /lib32/libpopt.so.0 (0xf7de9000)
libc.so.6 => /lib32/libc.so.6 (0xf7c9a000)
libpthread.so.0 => /lib32/libpthread.so.0 (0xf7c82000)
/lib/ld-linux.so.2 (0xf7f0f000)
libjpeg.so.62 => /usr/lib32/libjpeg.so.62 (0xf7c62000)
libz.so.1 => /usr/lib32/libz.so.1 (0xf7c4c000)

Jadi saya melakukan symbolic link :

sudo ln -s libpng12.so.0.15.0 /usr/lib32/libpng.so.2
sudo ln -s libtiff.so.4.2.1 /usr/lib32/libtiff.so.3

Disini juga letak perbedaannya dengan i386. Biasanya kalau di Intel, kita hanya perlu melakukan symbolic link ke /usr/lib, tapi kalau di amd64 kayaknya harus symbolic linknya ke /usr/lib32/

Hasilnya akan seperti ini :

linux-gate.so.1 => (0xffffe000)
libcnbpcmcm312.so => /usr/lib/libcnbpcmcm312.so (0xf7eea000)
libcnbpess312.so => /usr/lib/libcnbpess312.so (0xf7ea2000)
libm.so.6 => /lib32/libm.so.6 (0xf7e7c000)
libdl.so.2 => /lib32/libdl.so.2 (0xf7e78000)
libtiff.so.3 => /usr/lib32/libtiff.so.3 (0xf7e25000)
libpng.so.2 => /usr/lib32/libpng.so.2 (0xf7e02000)
libcnbpcnclapi312.so => /usr/lib/libcnbpcnclapi312.so (0xf7dfd000)
libcnbpcnclbjcmd312.so => /usr/lib/libcnbpcnclbjcmd312.so (0xf7df8000)
libcnbpcnclui312.so => /usr/lib/libcnbpcnclui312.so (0xf7df1000)
libpopt.so.0 => /lib32/libpopt.so.0 (0xf7de9000)
libc.so.6 => /lib32/libc.so.6 (0xf7c9a000)
libpthread.so.0 => /lib32/libpthread.so.0 (0xf7c82000)
/lib/ld-linux.so.2 (0xf7f0f000)
libjpeg.so.62 => /usr/lib32/libjpeg.so.62 (0xf7c62000)
libz.so.1 => /usr/lib32/libz.so.1 (0xf7c4c000)

Untuk ip1880, perbedaanya hanya pada library yang dibutuhkan yaitu :
libpng.so.3, jadi lakukan perintah :

sudo ln -s libpng12.so.0.15.0 /usr/lib32/libpng.so.3

Restoring the computer to an end–user–ready state

Sysprep is a tool designed for corporate system administrators, OEMs, and others who need to deploy the Windows® XP operating system on multiple computers. After performing the initial setup steps on a single system, you can run Sysprep to prepare the sample computer for cloning.

Sysprep assigns a unique security ID (SID) to each destination computer the first time the computer is restarted. Sysprep configures the operating system to use Windows Welcome or Mini–Setup to run the first time the end user restarts the computer. This shortened form of GUI–mode Setup takes 5 or 6 minutes instead of the usual 45 to 60 minutes, and it prompts the end user only for required and user–specific information, such as accepting the End–User License Agreement (EULA) and entering the Product Key, user name, and company name.

Sysprep is a valuable utility even if you do not use disk duplication. You can run Sysprep with the –nosidgen switch to configure Windows Welcome or Mini–Setup on a single computer. In this case, Sysprep allows for auditing that may have been done; automates the Mini–Setup portion of the process so that users can still enter user–specific information, such as regional options and TAPI information; and bypasses setting up unique SIDs, because the SIDs will already be unique when Setup is actually run on the computer.

The Sysprep utility can be used in three different contexts:

1. Disk duplication. Using Sysprep to prepare images for disk duplication allows you to copy fully installed systems onto similar hardware. Sysprep modifies the local computer Security ID (SID) so that it is unique to each computer. For more information, see How to Use Sysprep to Prepare Images for Disk Duplication.
2. Auditing. When you use Sysprep after auditing the computer (using the –nosidgen command–line option), Sysprep will be ready for the end user to run Windows. For more information, see How to Use Sysprep for Auditing Installations.
3. Automating Mini–Setup. Sysprep creates a shortened GUI–mode Setup that takes five or six minutes instead of the usual 45 to 60 minutes, and it prompts the end user only for required user–specific information, such as accepting the EULA, entering the Product Key, and entering the user name and company name. To use Sysprep in this mode, preinstall Windows XP on the local computer, and then run Sysprep with the –nosidgen parameter, using the steps below. For more information, see How to Use Sysprep to Automate Mini–Setup.

You can use Sysprep to restore the computer to an end–user–ready state. For more information, see How to Use Sysprep to Restore the Computer to an End–User–Ready State.

Top of page

Factory mode

The Factory mode of Sysprep is a method of preconfiguring installation options that can reduce the number of images an OEM needs to maintain. For more information, see How to Use Sysprep in Factory Mode.

General notes about sysprep

In Windows XP:

• You can run Sysprep from any location, including a floppy disk.
• Sysprep runs only if the computer is a member of a workgroup, not a domain. If the computer is joined to a domain, Sysprep removes it from the domain.
• You can run additional programs or commands at the end of Mini–Setup by providing a Cmdlines.txt in your Sysprep folder.
• You cannot run Sysprep on a computer that has been configured as a Cluster Service server, a Certificate Services server, or a domain controller. You can run Sysprep on a standalone server.
• If you run Sysprep on an NTFS file system partition that contains encrypted files or folders, the data in those folders become completely unreadable and unrecoverable.
• You can only use this version of Sysprep on Windows XP installations. You cannot use this version of Sysprep on a Windows 2000 installation.

Related Links

• How to Prepare Images for Disk Duplication with Sysprep
• How to Use Sysprep for Auditing Installations
• How to Use Sysprep to Automate Mini-Setup
• How to Use Sysprep to Restore the Computer to an End-User-Ready State
• How to Use Sysprep in Factory Mode

Set up a wireless network without a router

Selama ini dalam diskusi di milis, jika ada yang menanyakan bagaimana membuat sebuah jaringan nirkabel (wireless network) tanpa router, saya selalu googling sebentar dan memberikan hasil temuannya.

namun kemarin malam saya baru menyadari bahwa hit yang paling atas, URL yang mengacu ke situs microsoft dan yang biasa saya informasikan ke orang lain, ternyata sudah tidak ada. fasilitas pencarian yang disediakan oleh microsoft sendiri juga tidak banyak membantu.

untungnya artikel tersebut masih tersimpan di google cache, tertanggal 14 november 2008 kemarin. berhubung tulisan yang menghilang dari situs microsoft ini merupakan informasi yang berguna untuk umum, dan ada kemungkinan tidak ada terus disimpan di google cache, saya putuskan untuk menyalin artikel tersebut di sini.

---

Published: August 15, 2006

Wireless networks are helpful because they let you use your computer and connect to the Internet anywhere in your home or office. However, most wireless networks use a wireless router, which can be expensive. If you have more than one computer, you can set up a wireless network without buying a wireless router and save yourself some money.

In a traditional wireless network, a wireless router acts as a base station, much like the base station for cordless phones. All wireless communications go through the wireless router, allowing nearby computers to connect to the Internet or to each other.

Ad hoc wireless networks work more like walkie-talkies, because the computers communicate directly with each other. By enabling Internet Connection Sharing on one of the computers, you can share Internet access.

Ad hoc networking might seem like a much smarter alternative to using a wireless router, but it does have a couple of disadvantages:

• If the computer connected to the Internet is shut down, all computers that are part of the ad hoc network lose their Internet access.
• To connect to the Internet, one computer always needs a wired network connection.

To connect your computers to the Internet using an ad hoc wireless network, follow these high-level steps (described in more detail later in this article):

1. Enable Internet Connection Sharing on the Internet-connected computer. You can skip this step if you don’t need to access the Web.
2. Set up the ad hoc wireless network on the Internet-connected computer.
3. Add your other computers to the wireless network.

How to enable Internet Connection Sharing

On networks with wireless routers, the router has the important job of forwarding communications from the computers on your home network to the Internet. On ad hoc networks, you must designate one computer to serve this role. The computer you choose must have a wired connection to the Internet, and it should be left on whenever you want to be able to use your other computers.

How to set up the first computer

To set up an ad hoc wireless network that allows computers to share an Internet connection without a router

1. If necessary, install a wireless network adapter
2. Click Start, and then click Control Panel.
3. Under Pick a category, click Network and Internet Connections.
4. Under or pick a Control Panel icon, click Network Connections.
5. Right-click your wireless network connection, and then click Properties.
6. In the Wireless Network Connection Properties dialog box, click the Wireless Networks tab.
7. On the Wireless Networks tab, under Preferred networks, click Add.
8. In the Wireless network properties dialog box, on the Association tab, type the name of your ad hoc wireless network in Network name (SSID) box (shown in step 10). For example, you could name your wireless network MyHomeNetwork.
9. Clear the The key is provided for me automatically check box and select the This is a computer-to-computer (ad hoc) network check box.
10. Create a 13-digit password and type it in both the Network key and Confirm network key boxes. For the best security, include letters, numbers, and punctuation. Then click OK.
11. Click OK again to save your changes.

How to set up additional computers

If the computer you want to add to your network does not have built-in wireless network support, install a wireless network adapter.

Windows XP automatically detects the new adapter and notifies you that it found a wireless network.

Now connect your computer to your wireless network

Note: These steps apply only if you’re using Windows XP Service Pack 2 (SP2). If you haven’t installed SP2, visit Microsoft Update to install it before connecting to the ad hoc network.

1. Right-click the Wireless Network icon in the lower right corner of your screen, and then click View Available Wireless Networks.Note:
   If you run into any problems, consult the documentation that came with your network adapter. Don’t be afraid to call the manufacturer’s technical support department for help.
2. The Wireless Network Connection window appears and displays your wireless network listed with the SSID you chose. If you don’t see your network, click Refresh Network List in the upper left corner. Click your network, and then click Connect in the lower right corner.
3. Windows XP prompts you to enter a key. Type your encryption key in both the Network key and Confirm network key boxes, and then click Connect.

Windows XP shows its progress as it connects to your network. After you’re connected, you can close the Wireless Network Connection window.

Repeat these three steps on each computer that you want to connect to your ad hoc wireless network.

Now you’re ready to browse the Web wirelessly, from any computer you add to your home network.

Sumber: RyoSaeba.wordpress.com

AA1 yang memiliki built-in BIOS recovery routine, sehingga tidak mungkin untuk flash BIOS meskipun sistem tidak bisa boot lagi. Ini hanya dimaksudkan untuk keadaan darurat dan mungkin akan menghilangkan garansi anda, jadi resiko ditanggung sendiri.

Ikuti setiap langkah dengan hati-hati!

Pertama, Format USB dengan FAT.

Download BIOS terbaru, dan letakkan kedua FLASHIT.EXE dan BIOS file ke dalam direktori root dari USB stick. Ubah nama file BIOS ke ZG5IA32.FD, yang penting. Jangan keluarkan USB stick.

Matikan AA1, pastikan kedua baterai dan AC adaptor terhubung. Tekan Fn + ESC, ditahan dan tekan tombol power untuk menghidupkan AA1. Lakukan lagi Fn + ESC setelah beberapa detik, tombol power akan berkedip. Tekan tombol power sekali. AA1 yang sekarang akan memulai Flash BIOS, jangan dimengganggu walau dalam kondisi apapun. Setelah tombol daya berhenti berkedip, dan AA1 akan segera reboot. Kemudian tunggu beberapa saat.

BIOS telah di flash ulang, semua pengaturan kembali ke standar.

Jika karena alasan tertentu anda membuat kesalahan selama prosedur dan tidak reboot dengan sendirinya sampai menunggu 5 menit sebelum AA1 off, aman nya bahwa BIOS blom di flashing.

You can download it here, release notes are included. As the minor version bump already suggests there are only a few changes. Two of them are battery calibration related, the other one is a fix for the crisis mode which refers to the BIOS recovery routine as described here. If you have not already prepared a bootable USB stick read how to do so here. The BIOS is now also available from Acer Japan here. It’s only the BIOS file with no tools to actually flash it. Instead Acer Japan uploaded a tool to flash the BIOS from within Windows, available here. It’s official so it’s probably safe to use. Acer Taiwan put the BIOS online now as well, available here. And finally the BIOS has been uploaded to their european server. There is actually a text file included which recommends to flash the BIOS from DOS via a bootable USB stick.

Distributor Intel
Astrindo
Tel: 6221-6121331
astrindo@rad.net.id

CPU – Boxed, Tray, Mobile BMB Server products – MB, CPU, Chassis
Ingram Micro
Tel: 6221-6265085-86
erijaya@cbn.net.id

CPU – Boxed, Tray BMB Server products – MB, CPU, Chassis
SIS
Tel: 6221-3807668
yuli_kustio@sistech.co.id / john_kurniawan@sistech.co.id

CPU – Boxed, Tray
Terra
Tel: 6221-6266780
samuel.lauw@terra.co.id

CPU – Boxed, Tray BMB Server products – MB, CPU, Chassis
Attrix Technology (Indonesia)
Roxy Mas Blok C1 No. 31 Fl. 1
Jl Hasyim Ashari , Jakarta Indonesia 10150
Tel: +62 21 6334222
Fax: +62 21 6334331
Email: amir@attrix.com
Contact Person: Amir

Distributor AMD
eMD
021-6000909
021-6011234

Distibutor Sapphire, Western Digital, Seagate, Philips, Elsa, MCPRO:
Atikom
Jln. Mangga Dua Abdad
Rukan Mangga Dua Elok B/16
Jakarta 10730
021-6123612
021-6245959
www.atikom.co.id

Distributor HIS, Adata, :
Alamraya Electronics
HiTech Mall Lantai 1A no. 38
Jl. Kusuma Bangsa 116-118
Surabaya
Telp : (031) 5476582, 5476589

Asiaraya Computronics
Mangga 2 Mall Lantai 4 Blok A-62
Jakarta
Telp : (021) 6019408, 6018488

Distributor Kingston & Gigabyte:
Jakarta (Head Office)
PT. NUSANTARA ERADATA
Jl. P. Jayakarta 117 Blok C. 28
Jakarta 10730
Tlp: (021) 601 8218, 600 9085 (Hunting)
Fax: (021) 624 6914, 624 3649
(022) 723-6983 Bandung office
(022) 727-6780 Fax, Bandung office

Distributor Kingston:
Mikro Utama
(62-21) 612-8250
(62-21) 612-8251
(62-21) 612-8252

Distributor Asus, Intel, CoolerMaster, Creative, TwinMos:
PT Astrindo Senayasa
Gedung Mal Mangga Dua Ruko No 26-27
Jl.Arteri Mangga Dua Raya
Jakarta 10730 – Indonesia
Telp : 62-21-6121330
62-21-6121331
Fax : 62-21-6121329
e-mail : sales@astrindo.co.id

Distributor ABIT:
P.T. Spectrum Utama – ABIT Public Relations Division
Kompleks Ruko Bahan Bangunan dan Interior
Jln. Mangga Dua Raya Blok F7 no.5
Jakarta Utara 10730.
Telp : 021-6125505 / 6013281

Distributor Thermaltake:
Solitech
Mangga Dua Mall Lt.V B 81
Jl.arteri Mangga Dua Raya
Jakarta 10730 – Indonesia
Telp : 021-6129561
Fax : 021-62303811
e-mail : solitech@centrin.net.id

GPL COM
Mangga Dua Mall Lt.5 B/73
Jakarta, 10730
INDONESIA
TEL: +62-21-62301227 / 31
FAX : +62-21-623-01404
gplm2m@myrealbox.com

DIGITAL OUTLET
Mangga Dua Mall 3F/ 2B
Jakarta 10730
TEL: +62-21-6230-1383
FAX: +62-21-6230-2416

Reseller Asetek WaterChill CPU, VGA & Chipset Cooling:
Arjuna Digital
Jln. Macan No.16 Burangrang
Bandung 40262
Mobile Local: + 62 22 70796404
Mobile GSM: + 62 855 2117404
www.geocities.com/arjunadigital/waterchill.html
adee404@yahoo.com

Distributor GlobalWin:
Mangga besar V no 35B , Jakarta . Indonesia.
62 21 6262589 (salah sambung)
Setiabudhi 38 . Bandung . Indonesia.
E-Mail: indonesia@globalwin.com.tw

Distributor MSI:
Alfa Artha Andhaya:
021-6121202 / 6127464
marketing-msi@corexindo.com

Distributor DFI, TwinMOS, PixelView:
Sempurna
Ruko Dusit Blok A no. 3B
021-6129920 / 6129946
atau
SEMPURNA COMP
MANGGA DUA MALL LT.4 NO 43A
tlp : 021-6129920-6129946

Distributor DFI
3 DIMENSI Computer
Ruko M2M Blok A/3B JI, Mangga Dua Dalam, Jakarta Pusat
TEL : 62 21 6126255
FAX : 62 21 6126256

Distributor AcBel, Apacer:
SME
021-6257759

Distributor Winfast, XPC Shuttle Barebone dan Planet networking :
Diamondindo Mitra Lestari
Ruko Harco Mangga Dua D/10 jl. Arteri Mangga Dua, Jakarta 10730
tel : 021-6124030
fax : +62216124031
sales@diamondindo.com

Distributor ECS:
ECS Indonesia
021-6282048

Distributor GeCube:
Amtec
Terowongan Harco Mas No. 10 – 12A
Jl. Mangga Dua Raya – Jakarta Pusat
Telp. (021) 3000 – 5417, 3000 – 5418, 3000 – 5419
Faks. (021) 3000 – 5419

Distributor Albatron:
PT. Kent Power Dinamika Indonesia
Jakarta : Mall Mangga Dua lt.IV A/120, Jakarta Utara
(telp. 62-21-, 5671887 , 5601101)

Surabaya : THR Mall lt.II / E 23
(telp. 62-31-3815092 )

Distributor Eagle:
Eagle Indonesia
0216120956

Distributor Visipro:
Terra
021-6120003
021-6266780
www.terra.co.id

Distributor V-Gen:
Interface
021-6957133

Distributor MVM, Triplex:
Prince
021-6009863

Retailer Antec:
Digital One
Phone: +62 21 62302406

OC2
Phone: Jakarta +62 21 62303780

Talenta Komputama
Phone: +62 274 557388/517077

Distributor Altec Lansing
Express Utama
JI. Pintu Besar Selatan No. 71-D
(62) 21 6322 332
(62) 21 6303 134
Mr Tommy Widjaja altecmm@cbn.net.id

Distributor BenQ:
DAT
021-6120720

Distributor Enlight:
Enlight Indonesia
021-6129946

Distributor DVD drive NU, TEAC:
Geic
021-6011975

Distributor DVD Drive NEC:
GPL COM
Mangga Dua Mall Lt.5 B/73
Jakarta, 10730
INDONESIA
TEL: +62-21-62301227 / 31
FAX : +62-21-623-01404
gplm2m@myrealbox.com

Distributor DVD Drive Lite-On:
Dragon Computer di Jakarta:
Pusat Perkantoran Graha Kencana Blok DM-DN
Jl. Raya Perjuangan No.88 Kebon Jeruk
Jakarta 11530

HDD MAXTOR
PT Jayacom Alpha Electronic
JI Kentang No 12, Mangga Besar V
Jakarta 11180,
Indonesia
Tel: 021-6011925
Fax: 021-6299331

HDD HITACHI
PT Bintang Mas Rezeki Nusantara
Mangga Dua Mall (M2M) Lt 4 no 53
Jakarta Jakarta
Tel 6221-30005229
Jl Kartini Raya 64A no 2A-2B.
Jakarta Jakarta 10750
Tel 6221-6264750.
Email marketing@bintang-mas.com JI Kartini Raya 64A no 2A-2B
Jakarta 10750
Tel 6221-30005229
Tel 6231-71333350
Email marketing@bintang-mas.com Hitech Mall (THR) Lt 1 Blk C10
Surabaya Surabaya
Tel 6231-71333350

Sound card Prodigy
Chandracom
021-4513708

Distributor Logitech
Surya Candra
Komp. Marinatama Mangga Dua
Blok G/3 Jl. Gunung Sahari Raya No.2
021-6456617

Distributor Vantec, Sunbeam, Arctic Cooling
Techno Solution
6230-4380
Mangga 2 Mall lt.3/47B

Mushkin
bilucom
021-628-1758
Plaza pinangsia lt3

Sumber: Forum OprekPC.com

Using the Ubuntu Desktop/Live CD

Quick Start

This option will use the Desktop/Live CD to install Grub into your MBR (Master Boot Record). This option will overwrite your Windows Boot Loader. It is OK to do this, in fact that is the goal of this how to (in order to boot Ubuntu)

1. Boot the Desktop/Live CD. (Use Ubuntu 8.04 or later)

2. Open a terminal (Applications -> Accessories -> Terminal)

3. Start grub as root with the following command :

• sudo grub

4. You will get a grub prompt (see below) which we will use to find the root partition and install grub to the MBR (hd0)

•          [ Minimal BASH-like line editing is supported.   For
           the   first   word,  TAB  lists  possible  command
           completions.  Anywhere else TAB lists the possible
           completions of a device/filename. ]
  
  grub>

  Type the following and press enter:

  find /boot/grub/stage1

  If you get “Error 15: File not found”, try the following:

  find /grub/stage1

  Using this information, set the root device (fill in X,Y with whatever the find command returned):

  grub> root (hdX,Y)

  Install Grub:

  grub> setup (hd0)

(In case you want to install GRUB to another drive (like hdX) use the above command as ‘setup (hdX)’ and then continue)

• Exit Grub:

  grub> quit

5. Reboot (to hard drive). Grub should be installed and both Ubuntu and Windows should have been automatically detected.

6. If, after installing grub, Windows will not boot you may need to edit /boot/grub/menu.lst (That is a small “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 # You can use any title you wish, this will appear on your grub boot menu
   rootnoverify (hd0,0) #(hd0,0) will be most common, you may need to adjust accordingly
   makeactive
   chainloader +1

  Note: Put your Windows stanza before or after AUTOMAGIC KERNEL LIST in the menu.lst

Overwriting the Windows bootloader

Boot from a Live CD and open a terminal. You’ll need to run a few commands as root so you can use sudo -i to get a root shell and run them normally instead of using sudo on each of them. Be extra careful when running a root shell, especially for typos !

We’ll need to find which partition your Ubuntu system is installed on. Type the command fdisk -l. It will output a list of all your partitions, for example :

fdisk -l

Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1           8       64228+  83  Linux
/dev/hda2               9        1224     9767520   83  Linux
/dev/hda3   *        1225        2440     9767520   a5  FreeBSD
/dev/hda4            2441       14593    97618972+   5  Extended
/dev/hda5           14532       14593      498015   82  Linux swap / Solaris
/dev/hda6            2441       14530    97112862   83  Linux

Partition table entries are not in disk order

Here I have three Linux partitions. /dev/hda2 is my root partition, /dev/hda1 is my /boot partition and /dev/hda6 is my /home partitions. If you only have one, obviously this is the one your Ubuntu system is installed on. If you have more than one and you don’t know which one your Ubuntu is installed on, we’ll look for it later. First, create a mountpoint for your partition, for example :

mkdir /mnt/root

Then mount your partition in it. If you don’t know which one it is, then mount any of them, we’ll se if it’s the correct one.

mount -t ext3 /dev/hda2 /mnt/root

Of course, replace /dev/hda2 with the correct name of your partition. You can check if it’s the correct one by running ls /mnt/root, which should output something like this :

bin    dev      home        lib    mnt   root     srv  usr
boot   etc      initrd      lib64  opt   sbin     sys  var
cdrom  initrd.img  media  proc  selinux  tmp  vmlinuz

If what you have looks not at all like this, you didn’t mount the correct partition. Do umount /mnt/root to unmount it and try another one. You also need to mount your /boot partition if you made one, like this :

mount -t ext3 /dev/hda1 /mnt/root/boot

To make sure it was the correct one, run ls /mnt/root/boot, which sould output 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

Once again, if what you have doesn’t fit, unmount it and try another partition.

Now that everything is mounted, we just need to reinstall GRUB :

sudo grub-install --root-directory=/mnt/root /dev/hda

If you got BIOS warnings try:

sudo grub-install --root-directory=/mnt/root /dev/hda --recheck

Of course, replace /dev/hda 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/hda

Now you can reboot and the GRUB menu should appear. If you see a warning message regarding XFS filesystem, you can ignore it.

Preserving Windows Bootloader

This method allows you to restore GRUB and keep the Windows bootloader as your primary bootloader. Thanks to Ubuntu’s support for NTFS writing it’s now an absolute cinch.

The method shown above puts GRUB back on the MBR (master boot record) of the hard drive instead of in the root partition. But you probably won’t want that, if you use a third-party boot manager like Boot Magic or System Commander. (The original poster also suggested that this would be useful to restore the Grub menu after a re-ghosting.) In that case, use this alternative.

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.

Restoring GRUB

1. Boot from a Live CD, like Ubuntu Live, Knoppix, Mepis, or similar. Ideally use Ubuntu 8.04 or higher as this has NTFS write support and makes life a bit easier; this isn’t necessary, just handy.

2. Open a Terminal. Open a root terminal (that is, type “su” in a non-Ubuntu distro, or “sudo -i” in Ubuntu). 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 whatever your computer spits out for the following lines. Note that 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)”. 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 bootloader, or you can continue and tell the Windows bootloader 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 2005, or maybe before.

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 machine, or if you are using a Linux distro which supports NTFS writing like Ubuntu 8.04+ (maybe earlier?) then you can mount the actual Windows c:\ drive itself! The big bonus of writing to the windows drive is that you are going to need to put a file there, so it saves copying a file around. For example

#mkdir /tmp/windows
#mount /dev/sda1 /tmp/windows

3. Now you are going to make a copy of your boot partition; finding what this is called is not 100% deterministic because Linux might call your drives sdX or hdX, whereas GRUB always calls them hdX and Linux names them [hd|sd][Letter][Number] whereas GRUB names them as hd[Number][Number]; note that df won’t work as you are booted from a live CD. But let’s have a go; if you installed GRUB on (hd0,0), then /boot is on hda1 or sda1, (hd1,0) == hdb1 or sdb1, (hd0,1) == hda2 or sda2, etc… this narrows you down to two possibliities, now issuing ls /dev |grep hd will let you know if you have that drive on your machine, if nothing comes up which matchs, then you must have an sd drive. Ok great…

4. Having hopefully determined your boot partition issue the command (as root)

#dd if=/dev/sda2 of=/tmp/windows/linux.bin bs=512 count=1

Where /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. Reboot into Windows, open c:\boot.ini in notepad and on a new line at the botton add c:\linux.bin="Linux". This file might be write protected, if it is enable write in the right click context menu -> properties; you should disable write afterwards. Make sure that at the top of the boot.ini file there is a timeout set, i.e timeout=5. (Ah ha, you say, now I have NTFS support, why don’t I just edit boot.ini in Linux, the answer to this is that 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.

From: http://ubuntuforums.org/showpost.php?p=121355&postcount=5

From Inside Ubuntu

You have to run “grub” not from the Ubuntu Desktop/Live CD, but from your disk installation to make it work. To do this mount your root partition (following examples assume a root partition on hda1):

sudo mkdir /mnt/linux
sudo mount /dev/hda1 /mnt/linux

then change directory to your installation sbin and run grub from there

cd /mnt/linux/sbin
sudo ./grub

Using the Unofficial “Super Grub Disk”

From within Windows

• Download Auto Super Grub Disk

• Double-click auto_super_grub_disk_1.0 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. But you probably won’t want that, if you use a third-party boot manager like Boot Magic or System Commander. (The original poster also suggested that this would be useful to restore the Grub menu after a re-ghosting.) In that case, use this alternative.

This alternative, used without a third-party boot manager, will not cause Ubuntu to boot.

This alternative will let you boot your second hard disk Linux installations from Windows while the Using the Ubuntu Desktop/Live CD Preserving Windows Bootloader instructions will not.

Either:

• Download Super Grub Disk

• Burn into a cdrom (better) 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:

• Super Grub Disk (WITH HELP) ))

• Select: your language

• Select: 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
• You’re done.

Using Microsoft Vista

If you have Vista installed and you installed Ubuntu and when you rebooted it didn’t show up as a dual boot option, try going into Vista (since that is all you can do), use the program EasyBCD version 1.7 It looks like this:

Add your Linux install to the boot sequence.

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 anything you’re comfortable with
• You’re 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 fdisk -l /dev/hda)

• Knowledge of how your kernel works (specifically with regards to initrd), if you’re using a non-Ubuntu kernel or 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 proceedure until you are presented with an interface. If your LiveCD does not immediately present you with a console, also called a terminal, open one — to do this with the Ubuntu LiveCD, click Applications -> System Tools -> Terminal.

Note: Since this is a LiveCD environment, any changes to user accounts or filesystem 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 bootloader 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 filesystem data. Review your fstab and identify the location(s) of / and /boot/; these will likely look something like /dev/hda3 and /dev/hda4, though the letter ‘a’ and the numbers 3 and 4 may differ.

Note: For the remainder of this howto, /dev/hda3 and /dev/hda4 will be assumed, so alter them as needed when typing them in yourself.

Enter the following commands to load your filesystem and some information GRUB may need.

mount /dev/hda4 /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. Excercise caution.

Recovering GRUB Automatically

If you have a separate /boot/ partition, type the following line.

sudo mount /dev/hda3 /boot/

Reinstalling GRUB from this point is easy. Just enter the following command.

sudo /sbin/grub-install /dev/hda

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/hda1 is “hd0,0″ to GRUB. Similarly, /dev/hdb3 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, /boot/grub/menu.lst, with your favourite text editor. An example follows.

sudo nano /boot/grub/menu.lst

Note: Your menu.lst file is used to control the operating systems GRUB displays on startup, 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 bootloader pretty.

A sample menu.lst, stripped of unnecessary comments, appears below. It is based on the /dev/hda3 and /dev/hda4 example above, and assumes Windows resides at /dev/hda1.

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/hda4

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.

Using the Ubuntu Alternate/Install CD

This section explains how to rescue GRUB (the GRand Unified Boot loader), using the Ubuntu alternate/install CD ROM.

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 be dev/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/hdaX where X is your Ubuntu root install.

The GUI Way: Using the Alternate/Install CD and Overwriting the Windows bootloader

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 partions:
   • /
   • /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

GRUB Resources

• GRUB Manual

• GRUB homepage

• Grub wiki

• Linux+Win+Grub HowTo

• Super Grub Disk. Ready to go cdrom or floppy that restores Grub on MBR automatically

• Linux Recovery and Boot Disk Creation with Grub.

• Win32 Grub

• Booting with GRUB

• WinGRUB

• GRUB Installer for Windows

• GRUB for DOS – Bridging DOS/Windows to Unix/Linux

Sumber: https://help.ubuntu.com/community/RecoveringUbuntuAfterInstallingWindows

Pada beberapa ponsel jaman sekarang sudah ada aplikasi IM yang disematkan di dalam HP. Saya menemukan di beberapa merk terkenal seperti Nokia, Motorola, Sony Ericsson dan mungkin pada ponsel lainnya.

Pada awalnya saya mencoba memasukan username dan password YM saya di aplikasi IM tersebut. Namun pas di coba tidak bisa. Setelah googling akhiarnya saya menemukan bahwa untuk menggunakan YM di aplikasi IM tersebut harus menggunakan server IMPS. Kalau ingin tahu lebih jelas mengenai IMPS silahkan cari di wikipedia yah.

Langsung saja, saya sebenarnya hanya ingin menggunakan IM tersebut untuk YM saja. dan akhirnya saya menemukan cara menggunakan nya:

1.   Bukalah aplikasi IM yang ada di ponsel.
2.   Masukan pada bagian alamat web (web address) http://imps.next.msg.yahoo.com/gateway
atau
imps.msg.yahoo.com

3.   Masukan Username dan Password YM anda.

Setelah selesai langsung login deh.

NB: berjalan hanya pada yahoo internasional, yahoo lokal saya coba tidak bisa.

Jika ingin mencoba memasukan messenger dari pihak selain Yahoo Messenger, silahkan mencoba IMPS nya Mobjab.

Mungkin postingan saya kali ini sangat tidak disukai oleh Telkomsel, XL dan Indosat selaku pemegang lisensi Blackberry di Indonesia,karena saya dituding pro Blackberry Black market ataupun Blackberry yang tak jelas.

Ini ada tips dari saya bagaimana caranya kita UNLOCK PIN blackberry dari operator tertentu yang bisa kita buka sehingga bisa digunakan oleh operator lain,dan cara inilah yang digunakan oleh para penyelundup Blackberry operator luar negeri sehingga bisa masuk ke Indonesia, kebetulan saya sendiri adalah pengguna Blackberry Black Market (BM), dan Blackberry saya kebetulan milik salah satu operator luar negeri at&t artinya blackberry saya tersebut hanya bisa digunakan oleh operator at&t,tetapi kenyataannya tidak saya sudah berulang kali ganti operator dalam negeri di Blackberry saya. Bagaimana caranya ya ?

CARA PERTAMA :

Telp ke operator dimana kita berlangganan,bilang mau Release PIN BlackBerry. fungsinya open pin blackberry agar :
- dapat di ganti ke operator lain
- mau di jual ke orang lain agar orang yg beli dapat pake bb kita (sudah unlock)
- sekaligus menghilangkan email kita yg di sudah kita masukkan ke hp blackberry kita

CARA KEDUA

Dalam dunia Blackberry cara kedua ini dikenal dengan istilah TENDANG PIN
Ini namanya tendang PIN, caranya sebagai berikut :

bb A= bb yg mau kita tendang PIN nya
bb B= bb laen yg berfungsi normal dan terdaftar di operator

Syaratnya sinyal bb A dan bb B sudah GPRS besar

Langkah-langkah :
1. Login ke web operator BB dengan username bb B di PC ato opera mini.(www.namaoperator.blackberry.com)
2. Pilih change device , masukkan PIN dan IMEI bb A lalu save
3. SSB (send service book), sampai successfull, sampe nerima email notifikasi sukses di BB A
4. Pilih change device lagi, masukkan PIN dan IMEI bb B lalu save
5. SSB lagi, sampai successfull, sampe nerima email notifikasi sukses di BB B
6. Wipe handheld bb A
7. Bb A sudah bisa digunakan untuk create new user lagi.

SEMOGA BERHASIL..

Sumber: http://eri-communicator.blogspot.com/2009/07/unlock-pin-blackberry.html

1. Buka menu App. World
2. Pilih MyWorld
3. Tekan : Alt + R S T

Setelah beberapa detik, bb App. World akan close secara otomatis, dan begitu buka lagi listnya sekarang hanya tinggal aplikasi2 yg terinstall ..
semoga bermanfaat

Posted with WordPress for BlackBerry.

Untuk menjadi member di ßlackberry ßeta Zone ternyata gampang-gampang susah.
Supaya tidak repot coba klik link:
http://browser.lazap.com/index.php?q=aHR0cHM6Ly93d3cuYmxhY2tiZXJyeS5jb20vYmV0YS9hcHBseQ%3D%3D

Kemudian isi sesuai yang di minta. Untuk negara saya menggunakan malaysia.

Posted with WordPress for BlackBerry.

Meski terus digempur oleh sistem operasi lain seperti iOS, Android, dan BlackBerry, posisi Symbian belum tergeser sebagai sistem operasi yang digunakan sebanyak 35-42% dari total ponsel pintar yang beredar. Maka tidak heran jika banyak penjahat cyber yang coba memanfaatkanya sebagai ‘alat’ melakukan kejahatan.

Menurut pemaparan Marchelle David, Independent Security Researcher, dalam ajang AVAR yang digelar di Grand Hyatt, Bali, 17-19 November 2010. Meski sudah banyak pembenahan yang dilakukan Nokia terhadap Symbian, namun tidak mampu membendung seluruh ancaman yang beredar. Seperti 15 program jahat berikut berikut.

1. SymbOS.Flexispy
Ini adalah spyware yang dapat mengambil seluruh informasi di ponsel korban. Mulai dari sms, daftar panggilan, email, bahkan hingga menyadap percakapan.

2. SymbOS.Kidnap
Malware ini biasanya mendompleng pada aplikasi ternama. Kasus yang ditemukan malware ini menjangkit paket parlingo.sis, yakni aplikasi jejaring sosial. Pelaku bakal mencuri data korban seperti akun Facebook, Yahoo, dan lainya.

3. SymbOS.Disabler
Virus ini bisa memblokir panggilan masuk atau keluar, dan bahkan bisa menghalau seluruh pengiriman atau pun penerimaan sms.

4. SymbOS.Flerfox
Virus bakal menguras seluruh memori (RAM) ponsel dan membebankan kinerja prosesor. Alhasil, ponsel tersebut bakal terasa kurang responsif.

5. SymbOS.Lopsoy
Malware ini bakal membuat para penggunanya mengirimkan sms bertarif premium ke nomer tertentu. Kasus yang pernah ditemukan, malware ini dipaketkan bersama aplikasi gameloft3d.sis.

6. SymbOS.Porndial
Sepeintas memiliki cara kerja yang sama dengan SymbOS.Lopsoy. Hanya saja korban bakal ‘dipasksa’ melakukan panggilan bertarif premium dengan iming-iming mendapat konten porno.

Selain keenam program jahat tersebut, masih ada sembilan aplikasi lain yang tidak kalah berbahaya seperti SymbOS.Dadsey, SymbOS.appdisabler, SymbOS.killphone, SymbOS.Enoriv, SymbOS.Flesp, SymbOS.Badassist, SymbOS.SMSTrap, SymbOS.Cardtrap, SymbOS.Skuller.

Melihat ‘kue’ yang begitu besar, tentunya membuat para pembuat virus atau malware tidak melewatkannya begitu saja. Ribuan malware dan virus siap menjangkit sistem operasi besutan Nokia tersebut.

Sumber: http://m.detik.com/read/2010/11/19/082841/1497301/323/15-virus-berbahaya-untuk-ponsel-symbian

Posted with WordPress for BlackBerry.

Blackberry 7 devices:

BlackBerry Bold series (2011): BlackBerry Bold 9900/9930/9790
BlackBerry Torch series (2011): BlackBerry Torch 9810
BlackBerry Torch series (2011): BlackBerry Torch 9850/9860
BlackBerry Curve series (2011): BlackBerry 9350/9360/9370/9380

Blackberry 6 devices:

BlackBerry Torch series (2010): BlackBerry Torch 9800
BlackBerry Curve series (2010): BlackBerry 9300/9330
BlackBerry Style 9670 (2010)
BlackBerry Pearl series (2010): BlackBerry Pearl 3G 9100/9105
BlackBerry Bold series (2010-2011): BlackBerry Bold 9780/9788

Blackberry 5 devices:

BlackBerry Bold series (2008-2010): BlackBerry Bold 9000/9700/9650
Blackberry Tour series (2009):BlackBerry Tour (9630)
BlackBerry Storm series (2009): BlackBerry Storm2 (9520/9550)
BlackBerry Storm series (2008):BlackBerry Storm (9500/9530)
Blackberry Curve series (2009-2010):BlackBerry Curve 8900 (8900/8910/8980)
Blackberry Curve series(2009): BlackBerry Curve 8520/8530

Blackberry 4 and earlier devices:

Blackberry 8800 series (2007): BlackBerry 8800/8820/8830
Blackberry Pearl series (2006):BlackBerry Pearl 8100/8110/8120/8130
Blackberry Pearl Flip series (2008): BlackBerry Pearl Flip 8220/8230
Blackberry Curve series (2007): BlackBerry Curve 8300 (8300/8310/8320/8330/8350i)

Sumber: Wikipedia

9 Series:
9930 – Montana
9900 – Dakota
9860 – Monza
9810 – Jenning
9800 – Talladega
9790 – Bellagio
9780 – Delta
9700 – Onyx
9670 – Oxford
9650 – Niagara
9520 – Odin
9500 – Thunder
9380 – Orlando
9370 – Sedona
9360 – Apollo
9350 – Sedona
9300 – Kepler
9100 – Stratus
9000 – Meteor

8 Series:
8900 – Javellin
8830 – Huron
8820 – Huron
8800 – Indigo/Huron
8700 – Electron
8530 – Aries
8520 – Gemini
8350 – Orion
8330 – Saturn
8320 – Saturn
8310 – Saturn
8300 – Baby Bear, Papa Bear, Mama Bear
8200 – Kick Start
8120 – Comet
8100 – Pearl

Ada yang mau nambahin biar tambah koleksinya.

Terkadang ketika mempunyai BB baru kita bingung bagaimana cara memindahkan Kontak BBM dari BB lama.
Mungkin bagi yang punya Komputer hal ini tidaklah begitu sulit. Namun bagi yang tidak punya Komputer hal ini akan merepotkan.

Sekarang ada cara mudah untuk memindahkan kontak BBM dengan mudah tanpa harus melalui PC. Bahkan ketika BB lama akan dijual untuk menambah Biaya pembelian BB baru sekalipun tidak akan jadi masalah.

1. Turn Off Network Operator
- buka menu
- pilih manage connection
- buang tanda centang pada Mobile Network

2. Backup Kontak BBM
- buka Blackberry Messenger
- tekan 
- pilih option
- pilih backup
- pilih Backup file locally
- pilih backup now
- pastikan lokasi file backup di MMC
- lalu Save

3. Restore Kontak BBM
- pastikan mobile network di BB yang lama/baru masih Off
- buka Blackberry Messenger di BB yang baru
- tekan 
- pilih option
- pilih restore
- pilih Restore using a backup file from device
- cari lokasi file backup yang ada di MMC
- lalu restore deh

4. Turn On Mobile Network
- setelah semua kontak masuk ke BB yang baru
- pindahkan SIM card yang sudah aktif layanan BIS nya
- buka menu
- pilih manage connection
- beri tanda centang pada Mobile Network

Tunggu hingga proses refresh kontak BBM dengan sempurna. Disarankan bagi yang memakai Full BIS bisa menggunakan bantuan WiFi.
Atau cari lokasi yang jaringan operatornya lancar dan sudah support 3G.