How to install windows XP (page 1)

Berikut ini saya sajikan tutorial untuk menginstall windows XP. Untuk menginstall Windows XP kita membutuhkan sebuah komputer dan CD Windows XP. Selain itu sebaiknya siapkan cemilan karena proses instalasi ini akan membutuhkan waktu lama.

1. Siapkan CD Windows XP lengkap dengan Serial Number nya


2. Siapkan juga Driver Motherboard agar semua hardware yang ada bisa bekerja secara optimal nantinya


3. Pastikan computer Anda sudah disetting untuk booting dari CD ROM, kalau belum, silakan ubah melalui BIOS


4. Boot (nyalakan) komputer anda dan masukkan CD Windows XP


5. Tunggu beberapa saat sampai muncul tulisan "Press any key to boot from CD" di layar monitor anda.



6. Silakan tekan "Enter" atau sembarang tombol


7. Selanjutnya proses instalasi akan mengecek konfigurasi hardware KOMPUTER anda


8. Akan muncul tulisan "Windows Setup" di bagian kiri atas layar yang berwarna biru.



9. File-file yang ada di CD ROM akan diload ke dalam memori dalam proses instalasi ini. Selanjutnya layar "Welcome To Set Up Windows" akan tampil.



10. Tekan "ENTER" untuk menginstall WINDOWS XP. Tekan "R" untuk merepair Windows XP. atau Tekan "F3" untuk keluar dari proses instalasi. Di sini saya akan menekan "Enter" karena kita akan menginstall Windows XP


11. Selanjutnya akan muncul EULA (End User License Aggrement). Silakan baca dulu dan tekan "F8" jika anda setuju. Atau tekan "ESC" jika tidak setuju dengan isinya



12. Jika Anda setuju, selanjutnya proses instalasi akan mencari dan membaca partisi harddisk anda


13. Akan ditampilkan semua partisi harddisk Anda. Anda bisa mengatur partisi harddisk di sini. Untuk mengintall WINDOWS XP, setidaknya kita butuh 1 buah partisi.
    



14. untuk membuat partisi baru di area harddisk yang masih kosong, tekan "C". Untuk menghapus partisi yang dipilih, tekan "D". Hati-hati dalam melakukan penghapusan partisi, karena hal ini bisa saja menyebabkan data anda hilang. Setelah partisi dibuat, langkah selanjutnya adalah menentukan di partisi mana WINDOWS XP akan diinstall (biasanya di partisi C). Tekan "ENTER"


15. Selanjutnya akan permintaan apakah Anda akan memformat partisi yang tadi.



16. Disarankan untuk memilih NTFS File System


17. Partisi yang akan digunakan untuk lokasi penginstallan windowws XP anda akan diformat



18. Setelah harddisk diformat, setup akan mengcopy semua file yang dibutuhkan ke dalam memori. Proses ini akan membutuhkan waktu yang cukup lama.



19. Sesudah semua file sudah tercopy ke harddisk, setup akan mereboot computer anda



20. Setelah reboot, akan muncul lagi tulisan "Press Any Key to boot from CD". Kali ini jangan tekan tombol apapun, karena jika kita menekan tombol, kita akan kembali ke proses awal instalasi. Jika Anda tidak menekan tombol apapun, Windows akan tampil di layar secara otomatis

Untuk sementara sekian dulu tahapan instalasi windows xp berhubung akan ada pemadaman listrik dari PLN. Kapan-kapan disambung lagi.

Introduction CakePHP

Introduction to CakePHP
Section 1
What is CakePHP?

CakePHP is a free open-source rapid development framework for PHP. Its a structure of libraries, classes and run-time infrastructure for programmers creating web applications originally inspired by the Ruby on Rails framework. Our primary goal is to enable you to work in a structured and rapid manner - without loss of flexibility.
Section 2
Why CakePHP?

CakePHP has several features that make it a great choice as a framework for developing applications swiftly and with the least amount of hassle. Here are a few in no particular order:

1.

Active, friendly community
2.

Flexible Licensing
3.

Compatibility with PHP4 and PHP5
4.

Integrated CRUD for database interaction and simplified queries
5.

Application Scaffolding
6.

Model View Controller (MVC) Architecture
7.

Request dispatcher with good looking, custom URLs
8.

Built-in Validation
9.

Fast and flexible templating (PHP syntax, with helpers)
10.

View Helpers for AJAX, Javascript, HTML Forms and more
11.

Security, Session, and Request Handling Components
12.

Flexible access control lists
13.

Data Sanitization
14.

Flexible View Caching
15.

Works from any web site subdirectory, with little to no Apache configuration involved

Section 3
History of CakePHP

In 2005, Michal Tatarynowicz wrote a minimal version of a Rapid Application Framework in PHP. He found that it was the start of a very good framework. Michal published the framework under the MIT license, dubbing it Cake, and opened it up to a community of developers, who now maintain Cake under the name CakePHP.
print chapter

source : http://manual.cakephp.org/chapter/intro, ajax

CodeIgniter

Welcome to CodeIgniter

CodeIgniter is an Application Development Framework - a toolkit - for people who build web sites using PHP. Its goal is to enable you to develop projects much faster than you could if you were writing code from scratch, by providing a rich set of libraries for commonly needed tasks, as well as a simple interface and logical structure to access these libraries. CodeIgniter lets you creatively focus on your project by minimizing the amount of code needed for a given task.

Please read the Introduction section of the User Guide to learn the broad concepts behind CodeIgniter, then read the Getting Started page.
Who is CodeIgniter For?

CodeIgniter is right for you if:

* You want a framework with a small footprint.
* You need exceptional performance.
* You need broad compatibility with standard hosting accounts that run a variety of PHP versions and configurations.
* You want a framework that requires nearly zero configuration.
* You want a framework that does not require you to use the command line.
* You want a framework that does not require you to adhere to restrictive coding rules.
* You are not interested in large-scale monolithic libraries like PEAR.
* You do not want to be forced to learn a templating language (although a template parser is optionally available if you desire one).
* You eschew complexity, favoring simple solutions.
* You need clear, thorough documentation.

http://codeigniter.com/user_guide/

Getting Started with jQuery

This guide is an introduction to the jQuery library. Basic knowledge of JavaScript and the document object model (DOM) is required. It starts from ground up and tries to explain details where necessary. It covers a simple hello world example, selector and event basics, AJAX, FX and usage and authoring of plugins.

This guide contains no "click me" examples. The intention of providing only "copy me" code is to invite you to try it for yourself. Copy an example, see what it does, and modify it.

Setup

To start, we need a copy of the jQuery library, which we can get from the main download page. The jQuery Starterkit provides some markup and CSS to work with. After downloading and extracting its content we put jquery.js into the same directory and open starterkit.html and custom.js with our favorite editor and starterkit.html with a browser.

Now we have everything to start with the notorious "Hello world" example.

Hello jQuery

We start with an empty html page:

 <html>                                                                  
 <head>                                                                  
 <script type="text/javascript" src="jquery.js"></script>         
 <script type="text/javascript">                                         
   // we will add our javascript code here                                     
 </script>                                                              
 </head>                                                                 
 <body>                                                                  
   <--- we will add our HTML content here -->                                        
 <body>                                                                 
 <html>

This page just loads the jquery.js library (make sure the URL points to where you stored your copy of jquery! This example assumes that you store it in the same directory as this example file). Two comments indicate where we will expand this template with code.

As almost everything we do when using jQuery reads or manipulates the document object model (DOM), we need to make sure that we start adding events etc. as soon as the DOM is ready.

To do this, we register a ready event for the document.

$(document).ready(function() {
// do stuff when DOM is ready
});

Putting an alert into that function does not make much sense, as an alert does not require the DOM to be loaded. So lets try something a little more sophisticated: Show an alert when clicking the link.

$(document).ready(function() {
$("a").click(function() {
alert("Hello world!");
});
});

This should show the alert as soon as you click on the link.

Lets have a look at what we are doing: $("a") is a jQuery selector, in this case, it selects all a elements. $ itself is an alias for the jQuery "class", therefore $() constructs a new jQuery object. The click() function we call next is a method of the jQuery object. It binds a click event to all selected elements (in this case, a single anchor element) and executes the provided function when the event occurs.

This is similar to the following code:

Link

The difference is quite obvious: We don't need to write an onclick for every single element. We have a clean separation of structure (HTML) and behavior (JS), just as we separate structure and presentation by using CSS.

With this in mind, we explore selectors and events a little further.

J2ME

Java 2 Micro Edition (J2ME) combines a resource-constrained JVM and a set of Java APIs for developing applications for mobile devices. This article is the first in a series. This time, after a quick introduction to J2ME, I will provide a step-by-step guide to creating J2ME applications, also known as MIDlets, using a simple example. This will cover how to test and deploy these MIDlets as well. Finally, I will round out this installment with a look at the lifecycle of a MIDlet.
J2ME Introduction

What is J2ME? Cut away the hype and the excess fat and you are left with yet another (set of) Java APIs. Since these APIs cannot run on a traditional Java Virtual Machine (JVM), due to the limited size of mobile devices in regards to memory and resource availability, J2ME defines a limited version of the JVM as well. In a nutshell:

J2ME combines a resource constrained JVM and a set of Java APIs for developing applications for mobile devices.

Do you, as a developer, have to install this JVM and the APIs on mobile devices? No. Device manufacturers install and prepackage their devices with this JVM (and associated APIs). As a developer, you only need to develop applications targeting these devices and install them. Easier said than done!

J2ME can be divided into three parts, as shown in Figure 1: a configuration, a profile, and optional packages. A configuration contains the JVM (not the traditional JVM, but the cut-down version) and some class libraries; a profile builds on top of these base class libraries by providing a useful set of APIs; and optional packages, are well, an optional set of APIs that you may or may not use when creating your applications. Optional packages are traditionally not packaged by the device manufacturers, and you have to package and distribute them with your application. The configuration and profile are supplied by the device manufacturers and they embedded them in the devices.

he most popular profile and configuration that Sun provides are the Mobile Information Device Profile (MIDP) and Connected Limited Device Configuration (CLDC), respectively. As the name suggests, CLDC is for devices with limited configurations; for example, devices that have only 128 to 512KB of memory available for Java applications. Consequently, the JVM that it provides is very limited and supports only a small number of traditional Java classes. (This limited JVM is actually called the KVM.) Its counterpart, the Connected Device Configuration (CDC) is for devices with at least 2MB of memory available and supports a more feature-rich JVM (but still not a standard JVM).

The MID profile complements the CLDC configuration very well because it minimizes both the memory and power required for limited devices. It provides the basic API that is used for creating application for these devices. For example, it provides the javax.microedition.lcdui package that allows us to create the GUI elements that can be shown on a (limited) device running the MID profile on top of a CLDC configuration. Note that MIDP cannot be used with CDC devices. CDC devices get their own set of profiles, like the Foundation and Personal profiles. However, I will not cover these profiles or the CDC here, and will concentrate on using MIDP and CLDC only.

The latest versions of MIDP and CLDC are 2.0 and 1.1, respectively. Not many devices currently support these versions, but the list is growing rapidly. Sun maintains a list of devices according to version.
Acquiring and Installing the J2ME Development Kit

Getting started with developing applications (henceforth called "MIDlets") for the J2ME platform is easy. Although device manufacturers install and prepackage their devices with this JVM (and associated APIs), you still need to install the J2ME Wireless Toolkit 2.2 on your development machine. Before that, however, you must also have the Java Development Kit (JDK), version 1.4.2 or greater, installed.

Warning: I had problems getting the Wireless Toolkit to work properly with JDK 5.0. If you don't need the latest features in version 5.0, it is best to stick to any 1.4.2 version. I have used 1.4.2_05 for all examples in this series.

You need this Toolkit because it contains tools that are important in generating MIDlets. This Toolkit provides the development environment for the MIDP 2.0 and CLDC 1.1 (and for MIDP 1.0 and CLDC 1.0, since these parameters are backwards compatible), and it provides the optional packages required for the optional libraries, like 3D and Mobile Media applications. Lastly, it provides the ability to sign your MIDlets so that they can be authenticated before installation on a remote mobile device.

Once you download the installation package for the Toolkit, install it in the directory of your choice. The default, on Windows, is C:\WTK22, and this will be the installation directory for the examples in this series as well. I will not explain the directories created under this folder just now. Before I do that, let us try and understand the process of generating a MIDlet from scratch.

Pages: 1, 2, 3