go to my.ini

max_connections=500

Please note that an instruction of the form
set-variable=max_connections=500
should be placed in the [mysqld] section. Otherwise MySQL will ignore it.

[share]
browseable = yes
writeable = yes
write list = root
comment = server
valid users = root
path = /
public = yes

Goto

http://asterisk.hosting.lv/

DL the right one
# choose codec binary appropriate for your Asterisk version and CPU type, use x86_64 for 64-bit mode, scroll to the end of the list for FreeBSD binaries
# delete old codec_g729/723*.so files (if any) from /usr/lib/asterisk/modules directory
# copy new codec_g729/723*.so files into /usr/lib/asterisk/modules directory
# restart Asterisk

Then connect to the Asterisk console with:
asterisk -r
and type (adjust accordingly):
load codec_g729-ast14-gcc4-glibc-core2.so

You should then see something like:
Loaded /usr/lib/asterisk/modules/codec_g729-ast14-gcc4-glibc-core2.so => (G729/PCM16 (signed linear) Codec Translator, based on IPP)
== Registered translator ‘g729tolin’ from format g729 to slin, cost 1
== Registered translator ‘lintog729′ from format slin to g729, cost 6

Exit from the console with:
quit

Then use nano to edit /etc/asterisk/sip.conf and just below:
allow=ulaw
add:
allow=gsm
allow=g729

# check the codec is loaded with ‘core show translation recalc 10′ on Asterisk console (‘show translation’ in Asterisk 1.2)
# G.723.1 send rate is configured in Asterisk codecs.conf file (Linux Asterisk 1.2, 1.4, 1.6, TRUNK and Callweaver, FreeBSD 7.x Asterisk 1.4 binaries only):

other cool linux commands

cat /proc/cpuinfo
cat /proc/meminfo
dmesg
lspci

then

change your access point eg using the E71 or E72, and I changed it by going through these steps:

Installations -> App. Mgr. -> Select Gmail -> Click Open -> Go to Access Point.

or are just generally fuicked off that you cant update the firmware

Simple change the product code of the phone to an unbranded one and then use nokia’s own software update service to update your phones firmware.

1) get the

2) Nemesis Service Suite
This is an application that actually does the changing of the product code. It can (preferably) be downloaded from the maker’s site BPreaks.brinkster.net for the latest version. (left hand side, downloads section)

3) change your product code from xxxxxxxx to xxxxxxxxxx using

NOKIA FIRMWARE FINDER-BEST TOOL

est tool for search the latest firmware your nokia.
Easy to use just 4 step
- choose nokia type (ex. E63 RM-437)
- select the latest firmware are available
- select firmware release for your country
- select firmware do you need (ex. only mcu, ppm or complete)
download

5) then use the Nokia Software Updater to update the firmware to the new phones correct firmware

It’s the “Breathing light” that you need to turn off, rather than any notification:

Tools –> Profiles –> General (or whichever profile you use) –> Personalise –> Breathing light –> Off

Try this and see if it helps.

Outlook has a rule to automatically Cc another person on outgoing messages, but no equivalent for Bcc. This page offers two code samples for adding such an automatic Bcc. Both use the Application.ItemSend event, which fires whenever a user sends a message or other item.

Method #1 (Basic)

This version is suitable for Outlook 2003 or later. It uses Outlook objects exclusively and includes error handling to avoid problems with an invalid Bcc address.

Place this VBA code in the built-in ThisOutlookSession module:

Private Sub Application_ItemSend(ByVal Item As Object, _
 Cancel As Boolean)
 Dim objRecip As Recipient
 Dim strMsg As String
 Dim res As Integer
 Dim strBcc As String
 On Error Resume Next

 ' #### USER OPTIONS ####
 ' address for Bcc -- must be SMTP address or resolvable
 ' to a name in the address book
 strBcc = "someone@somewhere.dom"

 Set objRecip = Item.Recipients.Add(strBcc)
 objRecip.Type = olBCC
 If Not objRecip.Resolve Then
 strMsg = "Could not resolve the Bcc recipient. " & _
 "Do you want still to send the message?"
 res = MsgBox(strMsg, vbYesNo + vbDefaultButton1, _
 "Could Not Resolve Bcc Recipient")
 If res = vbNo Then
 Cancel = True
 End If
 End If

 Set objRecip = Nothing
End Sub

Make sure you substitute the right e-mail address for “someone@somewhere.dom.”

The reason that this method is not suitable for versions earlier than Outlook 2003 is because it will trigger an address book security prompt due to the use of Recipients.Add. You could avoid security prompts by simply setting the Item.Bcc property to the desired address, but that has two problems. First, it would wipe out any Bcc recipients that the user might have already added. Also, in some Outlook configurations, setting Bcc without trying to resolve the address results in an unresolved address, even if you use a proper SMTP address; you’ll get an error, and Outlook won’t send the message.

Method #2 (Redemption)

This version uses the same basic technique as Method #1, only with the third-party Outlook Redemption library to avoid security prompts in versions before Outlook 2003 and, if the recipient cannot be resolved, to display to the user the name resolution dialog.

Private Sub Application_ItemSend(ByVal Item As Object, _
 Cancel As Boolean)
 ' Requires a reference to
 ' the SafeOutlook library (Redemption.dll)
 Dim objMe As Redemption.SafeRecipient
 Dim sMail As Redemption.SafeMailItem
 On Error Resume Next

 Set sMail = CreateObject("Redemption.SafeMailItem")
 Item.Save
 sMail.Item = Item
 Set objMe = sMail.Recipients.Add("myaddress@mydomain.dom")
 objMe.Type = olBCC
 If Not objMe.Resolve(True) Then
 Cancel = True
 End If

 Set objMe = Nothing
 Set sMail = Nothing
End Sub

Make sure you substitute the right e-mail address for “myaddress@mydomain.dom.“