fadlee.org

US BailOut?

China Milk Scandal?

Georgian Conflict?

Let’s just take a deep breath for just one second, since now Eid Mubarak has come…

Again! one proof that Bali was more famous (or important) rather than Jakarta or other Indonesian city.

Take a look at http://map.google.com/ , then search: bali. Now you can see the detail map of Bali. Rather than you search: jakarta, it’s only global main road (scale of java road) that appear!

Here’s the complete legian area:

Here’s when you search Hard Rock Cafe:

Here’s the poor jakarta:

So? it is really bali were more interest and ‘more people looking’ instead of Jakarta or Indonesia? Or It’s because in Bali there more Hotel Investor that pay more to google?

So? Is google-ism were more capitalism?

Cheers Mate!

Jasdwal imsakiyah Kota Jakarta 

Sumber: PKPU

I found little bug on google chrome related to facebook website that using maybe some of AJAX code.
On ‘Discover People You May Know’ part, when you want to closed the person you may not know (do not show this person) using [x] button, it didn’t work!

Maybe you guys from google can explain this bug?

Dikutip dari detik.com:

Los Angeles Paris Hilton dikenal sebagai salah satu selebriti yang rajin dugem. Cukup sering terdengar betapa gila aksinya ketika dugem. Namun kini Paris tiba-tiba mengaku ingin meninggalkan kegilaanya itu.

“Aku tak mau pergi ke klub lagi sekarang. Aku terperangkap dalam gaya hidup yang kelihatannya menyenangkan saat itu, tapi sebenarnya kemudian meninggalkan kehampaan,” ucapnya pada majalah terbitan Inggris, Heat, detikhot kutip dari Female First, Kamis (4/9/2008).

Apa kiranya yang membuat Paris insyaf? Rupanya bintang film ‘House of Wax’ itu berubah karena kehadiran seorang pria yang kini mengisi hari-harinya.

“Pacarku adalah sahabatku. Aku sekarang ini lebih sering berada di rumah dan menghabiskan waktuku bersama Benji,” katanya.

Benji tak lain adalah personel band Good Charlotte yang dipacari Paris sejak awal 2008 ini. Bersama rocker itu, socialite berambut pirang tersebut mengaku kini telah menjadi orang yang berbeda

Ternyata trend tobat bukan cuma ada di infotainment indonesia, tetapi juga mancanegara. Tentu saja hal tersebut dapat meningkatkan amupun mengurangi popularitas artis yang bersangkutan. we’ll se what the next manouver from paris huh.

When using Windows NT integrated security with SQL Server, the SQL Server login information must be identical to the Windows NT account information. Therefore, if you change the Windows NT password of the domain account that the SQL Server is logged on with, then you also must update the password in the following SQL Server services: MSSQLServer, SQLServerAgent, MSDTC, and the MODTBAD Office Developer DCOM component.

If you change a password, it must be updated on the server, the developer workstation, and the client computers. If the password is not updated for the SQL Server Agent, Access Workflow Designer cannot start and stop the agent automatically. Access Workflow Designer also uses the agent to manage time-out events for team solutions, so it is critical this service be set up properly.

Any time you change a password, it should be updated in the following locations:

• Changing the sa Password on the Server
• Changing the User ID for MODTBAD
• Changing the sa Password on the Client

Changing the sa Password on the Server

During installation of the Access Workflow Designer server components, you enter the user name and password of the Windows NT domain. When using Windows NT integrated security, this same account information is used by SQL Services. When you change the Windows NT password for that log on, it also must be changed for SQL Server services. For information about changing the password when using MSDE, see Changing the sa Password on the Client.

To set up SQL Server services to log on under a different user account

1. On the Start menu, point to Settings, and then click Control Panel.
2. Double-click Services.
3. Double-click MSSQLServer, SQLServerAgent, or MSDTC. You must update the information for each of these services.
4. In the Services dialog box, in the Login area, select This account, and then enter or update the account information.
5. Click OK. Update the other services listed in step 3 as required.
6. Click Close.

   Important If Microsoft Full-Text Search is installed on the computer, do not change the MSSQLServer account information in the Services application in Control Panel. Although the Search service is assigned to the local system account, it also tracks the MSSQLServer service account. You must change the MSSQLServer service account in SQL Server Enterprise Manager for the Microsoft Search service to stay synchronized.

Changing the User ID for MODTBAD

During installation of the Access Workflow Designer server components, you enter the user name and password of the Windows NT domain account that the Access Workflow Designer executable (MODTBAD.exe) uses to log on to the domain. Generally, this is the same account used by the SQL Server Services. If this is the case, when you change the Windows NT password for that log on, it also must be changed for MODTBAD.exe.

To change the User ID for MODTBAD

1. From the Start menu on the server, select Run, and then type DCOMCNFG.
2. If you have never run DCOMCNFG before and Office is installed on the server, you may see two messages asking if you want to register Msohelp.exe. Click Yes for both messages.
3. On the Team Solutions tab, select MODTBAD.
4. Click Properties, and then select the Identity tab.
5. Under This user, type or browse for the user whose password has changed.
6. Enter and confirm the new password.
7. Click OK.
8. Restart the server.

   Note The Windows NT domain account used for the MODTBAD identity must have system administrator permissions on the server. However, this account does not have to be the same account used by SQL Server.

Changing the sa Password on the Client

You have a variety of options for updating the SQL Server Agent password on the clients. The method you specify depends on the tools available on the client computer.

If the SQL Server Enterprise Manager is available on the client computer, you can change the sa password directly. For details, follow the procedure in Changing the sa Password on the Server.

If Access is available on the client computer, update the password using the Security option on the Tools menu in an Access data project.

If you are using MSDE on the client, there is no user interface for changing the sa password for the SQL Server Agent. You can update the password by accessing the client computer remotely using SQL Server Enterprise Manager on the server.

To change the sa password on the client using Access

1. From the Tools menu in your Access data project, select Database Security.
2. On the Server Logins tab, select sa, and then click Edit.
3. Change the password, and click OK.

You can connect to the client computer remotely to use SQL Server Enterprise Manager to modify the client settings as long as you have created a server alias for your client computer. For details, see Using MSDE with Windows 95/98.

To change the sa password on the client computer without SQL Server Enterprise Manager

1. In the SQL Server Enterprise Manager, right-click the SQL Server Group, and select New SQL Server Registration. If the registration wizard launches, clear the Always run this wizard option, and click OK.
2. Type the name of your client computer, or click Browse to display a list of computer names.
3. Under Connection, select Use SQL Server authentication, enter sa in the Login Name field and the sa password, and click OK.
4. Expand the client computer node you just added, and then expand the Management node.
5. Right-click SQL Server Agent, and select Properties.
6. On the Connection tab, enter the appropriate Password for SysAdmin login ID.
7. Click OK.

After you have changed the client settings, you must synchronize your offline subscription by opening your solution in Internet Explorer and selecting Tools and then Synchronize. A dialog box appears in which you can enter the new password.

Most security experts’ recommendations include changing passwords frequently to enhance security. It is easy to change the password on a SQL Server Username via Query Analyzer. Changing the password with Query Analyzer makes it easy to coordinate changing the password on the database server at the same time as it is changed in the connection string. This approach provides the flexibility to change the password at the most appropriate time for the application.
To change the SQL Server Username password, just connect to the database with Query Analyzer using the SQL Server Username that is being updated and the current password. Then run “sp_password” to change the password.

sp_password [ [ @old = ] 'old_password' , ]

{ [ @new =] 'new_password' }

[ , [ @loginame = ] 'login' ]

Here is a simple example that changes the current password from

"currentPSWD" to "newPSWD";

sp_password 'currentPSWD', 'newPSWD'

Be sure to use a strong password, “newPSWD” is just an example. I always like to
test any change like this right away. For a quick test to confirm that the new
password is working, close Query Analyzer and then re-connect with the new
password. That is all there is to it, except for changing your connections
string. It is obvious, but still critical to remember to change the password in
your connection string if this SQL Username is used in your code. Once the
password has been changed and tested with Query Analyzer, update the connection
string with the new password and test that e verything still works correctly,
and you’re done.