HP a1740n P5BW-LA Motherboard BIOS tutorial

This was an annoying repair!
This tutorial is to flash BIOS version 3.17 or 5.08 on HP / ASUS P5BW-LA (OEM Asus motherboard to HP) and requires BIOS from HP.

The bios update from windows failed (hang)
Bios screen displayed Award Bootblock recovery BIOS
BIOS Checksum failed
----------------------------------------------
Download the following archive with awardflash134, drdos and rom files
1. Create a bootdisk with DrDos as described on this site
2. Put Awardflash 1.34 into the image
3. Put HP bios version 317 and 508 into image
4. Boot the CD
5. Run awardflash
6. Load the bios image required (508 is newer)

Notes:
1. I couldn't get motherboard to boot from USB only from CD
2. The files can be in *.rom or *.bin ending it doesn't matter
3. There are many versions and bioses and tutorials online which make restoring this bios a mess!

HTC Sleep2Wake

Q: It keeps taking screenshots when I lock the screen!?

A: This is due to an incompatibility with this feature and the native
screenshot in Sense. TO stop the screen shots, you need to edit your
build.prop and change the property ro.htc.framework.screencapture to false, and then reboot.

HTC dynamic links to phone numbers

From http://forum.xda-developers.com/showthread.php?p=27035550



build.prop you will have this line

ro.da1.enable=true



change to



ro.da1.enable=false

then add just below that this line

ro.da1.method=false

IncredibleS HBoot

http://forum.xda-developers.com/showthread.php?t=1705913
http://forum.xda-developers.com/showthread.php?t=1761319&page=3

OpenVPN Routing

Expanding the scope of the VPN to include additional machines on either the client or server subnet.

Including multiple machines on the server side when using a routed VPN (dev tun)

Once the VPN is operational in a point-to-point capacity between
client and server, it may be desirable to expand the scope of the VPN so
that clients can reach multiple machines on the server network, rather
than only the server machine itself.

For the purpose of this example, we will assume that the server-side LAN uses a subnet of 10.66.0.0/24 and the VPN IP address pool uses 10.8.0.0/24 as cited in the server directive in the OpenVPN server configuration file.

First, you must advertise the 10.66.0.0/24
subnet to VPN clients as being accessible through the VPN. This can
easily be done with the following server-side config file directive:

<strong>push "route 10.66.0.0 255.255.255.0"</strong>

Next, you must set up a route on the server-side LAN gateway to route the VPN client subnet (10.8.0.0/24) to the OpenVPN server (this is only necessary if the OpenVPN server and the LAN gateway are different machines).

Make sure that you've enabled IP and TUN/TAP forwarding on the OpenVPN server machine.

Including multiple machines on the server side when using a bridged VPN (dev tap)

One of the benefits of using ethernet bridging is that you get this for free without needing any additional configuration.

Including multiple machines on the client side when using a routed VPN (dev tun)

In a typical road-warrior or remote access scenario, the client
machine connects to the VPN as a single machine. But suppose the client
machine is a gateway for a local LAN (such as a home office), and you
would like each machine on the client LAN to be able to route through
the VPN.

For this example, we will assume that the client LAN is using the 192.168.4.0/24 subnet, and that the VPN client is using a certificate with a common name of client2.
Our goal is to set up the VPN so that any machine on the client LAN can
communicate with any machine on the server LAN through the VPN.

Before setup, there are some basic prerequisites which must be followed:

• The client LAN subnet (192.168.4.0/24 in our example) must not be
  exported to the VPN by the server or any other client sites which are
  using the same subnet. Every subnet which is joined to the VPN via
  routing must be unique.
• The client must have a unique Common Name in its certificate ("client2" in our example), and the duplicate-cn flag must not be used in the OpenVPN server configuration file.

First, make sure that IP and TUN/TAP forwarding is enabled on the client machine.

Next, we will deal with the necessary configuration changes on the
server side. If the server configuration file does not currently
reference a client configuration directory, add one now:

<strong>client-config-dir ccd</strong>

In the above directive, ccd should be the name of a
directory which has been pre-created in the default directory where the
OpenVPN server daemon runs. On Linux this tends to be /etc/openvpn and on Windows it is usually \Program Files\OpenVPN\config.
When a new client connects to the OpenVPN server, the daemon will check
this directory for a file which matches the common name of the
connecting client. If a matching file is found, it will be read and
processed for additional configuration file directives to be applied to
the named client.

The next step is to create a file called client2 in the ccd directory. This file should contain the line:

<strong>iroute 192.168.4.0 255.255.255.0</strong>

This will tell the OpenVPN server that the 192.168.4.0/24 subnet should be routed to client2.

Next, add the following line to the main server config file (not the ccd/client2 file):

<strong>route 192.168.4.0 255.255.255.0</strong>

Why the redundant route and iroute statements, you might ask? The reason is that route controls the routing from the kernel to the OpenVPN server (via the TUN interface) while iroute controls the routing from the OpenVPN server to the remote clients. Both are necessary.

Next, ask yourself if you would like to allow network traffic between
client2's subnet (192.168.4.0/24) and other clients of the OpenVPN
server. If so, add the following to the server config file.

<strong>client-to-client<br />push "route 192.168.4.0 255.255.255.0"</strong>

This will cause the OpenVPN server to advertise client2's subnet to other connecting clients.

The last step, and one that is often forgotten, is to add a route to
the server's LAN gateway which directs 192.168.4.0/24 to the OpenVPN
server box (you won't need this if the OpenVPN server box is
the gateway for the server LAN). Suppose you were missing this step and
you tried to ping a machine (not the OpenVPN server itself) on the
server LAN from 192.168.4.8? The outgoing ping would probably reach the
machine, but then it wouldn't know how to route the ping reply, because
it would have no idea how to reach 192.168.4.0/24. The rule of thumb to
use is that when routing entire LANs through the VPN (when the VPN
server is not the same machine as the LAN gateway), make sure that the
gateway for the LAN routes all VPN subnets to the VPN server machine.

Similarly, if the client machine running OpenVPN is not also the
gateway for the client LAN, then the gateway for the client LAN must
have a route which directs all subnets which should be reachable through
the VPN to the OpenVPN client machine.

Including multiple machines on the client side when using a bridged VPN (dev tap)

This requires a more complex setup (maybe not more complex in practice, but more complicated to explain in detail):

• You must bridge the client TAP interface with the LAN-connected NIC on the client.
• You must manually set the IP/netmask of the TAP interface on the client.
• You must configure client-side machines to use an IP/netmask that is inside of the bridged subnet, possibly by querying a DHCP server on the OpenVPN server side of the VPN.

Fixing no HDMI audio on 9600GT

From the link http://forums.nvidia.com/index.php?showtopic=88391&pid=513648&mode=threaded&start=0#entry513648

Got it to work, Example of mine.



nv_SoftwareDeviceSettings]

HKR,, OverrideEdidFlags0, %REG_BINARY%, 4C,2E,12,0A,00,00,FF,FF,04,00,00,00,7E,01,00

HKR,, InstalledDisplayDrivers, %REG_MULTI_SZ%, nv4_disp

HKR,, VgaCompatible, %REG_DWORD%, 0

HKR,, MultiFunctionSupported, %REG_DWORD%, 1

HKR,, RotateFlag, %REG_DWORD%, 4

HKR,, DevSwitchSuppressMask, %REG_DWORD%, 7

HKR,, HDTVModePruning, %REG_DWORD%, 6

HKLM,"Software\NVIDIA Corporation\Global\NvSvc\OemConfigurations"
,LoadLimitedSID,%REG_SZ%,"S-1-5-11"



HKR,, NV_Modes, %REG_MULTI_SZ%, "{*}S 720x480
720x576=1;720x576=8032;SHV 1680x1050=1;1920x1200x32 1920x1440
2048x1536=1F;640x480 800x600 848x480 960x600
1024x768x8,16=1FFF;1600x900x32 1600x1200x32
1920x1200x8,16=3F;1280x720x32 1280x768x32 1280x800x32 1280x960x32
1280x1024x32 1360x768x32=3FF;1600x900x8,16
1600x1200x8,16=7F;1280x720x8,16 1280x768x8,16 1280x800x8,16
1280x960x8,16 1280x1024x8,16 1360x768x8,16=7FF;1024x768x32 1152x864
1440x900=FFF;"



[nv_SoftwareDeviceSettings_G7x]

HKR,, InstalledDisplayDrivers, %REG_MULTI_SZ%, nv4_disp

HKR,, VgaCompatible, %REG_DWORD%, 0

HKR,, MultiFunctionSupported, %REG_DWORD%, 1

HKR,, RotateFlag, %REG_DWORD%, 4

HKR,, DevSwitchSuppressMask, %REG_DWORD%, 7

HKR,, HDTVModePruning, %REG_DWORD%, 6

HKLM,"Software\NVIDIA Corporation\Global\NvSvc\OemConfigurations"
,LoadLimitedSID,%REG_SZ%,"S-1-5-11"



HKR,, NV_Modes, %REG_MULTI_SZ%, "{*}S 720x480
720x576=1;720x576=8032;SHV 1680x1050=1;1920x1200x32 1920x1440
2048x1536=1F;640x480 800x600 848x480 960x600
1024x768x8,16=1FFF;1600x900x32 1600x1200x32
1920x1200x8,16=3F;1280x720x32 1280x768x32 1280x800x32 1280x960x32
1280x1024x32 1360x768x32=3FF;1600x900x8,16
1600x1200x8,16=7F;1280x720x8,16 1280x768x8,16 1280x800x8,16
1280x960x8,16 1280x1024x8,16 1360x768x8,16=7FF;1024x768x32 1152x864
1440x900=FFF;"



[nv_SoftwareDeviceSettings_77]

HKR,, OverrideEdidFlags0, %REG_BINARY%, 4C,2E,12,0A,00,00,FF,FF,04,00,00,00,7E,01,00

HKR,, InstalledDisplayDrivers, %REG_MULTI_SZ%, nv4_disp

HKR,, VgaCompatible, %REG_DWORD%, 0

HKR,, MultiFunctionSupported, %REG_DWORD%, 1

HKR,, RotateFlag, %REG_DWORD%, 4

HKR,, DevSwitchSuppressMask, %REG_DWORD%, 7

HKR,, HDTVModePruning, %REG_DWORD%, 6

HKLM,"Software\NVIDIA Corporation\Global\NvSvc\OemConfigurations"
,LoadLimitedSID,%REG_SZ%,"S-1-5-11"





Search your model of card, mine being a 8200 look
toward the bottom of the inf and it will have a number to the left of it
which mine was 77, so i found the line nv_softwaredeviceSettings_77 and
also added the line i inserted into nv_softwaredevicesettings. Hope
this helps :)





NVIDIA_C73.DEV_07E1.1 = "NVIDIA GeForce 7100 / NVIDIA nForce 630i"

NVIDIA_C73.DEV_07E2.1 = "NVIDIA GeForce 7050 / NVIDIA nForce 630i"

NVIDIA_C73.DEV_07E3.1 = "NVIDIA GeForce 7050 / NVIDIA nForce 610i"

NVIDIA_C73.DEV_07E5.1 = "NVIDIA GeForce 7050 / NVIDIA nForce 620i"

NVIDIA_C77.DEV_0846.1 = "NVIDIA GeForce 9200"

NVIDIA_C77.DEV_0848.1 = "NVIDIA GeForce 8300"

NVIDIA_C77.DEV_0849.1 = "NVIDIA GeForce 8200"

NVIDIA_C77.DEV_084A.1 = "NVIDIA nForce 730a"

NVIDIA_C77.DEV_084B.1 = "NVIDIA GeForce 8200 "

NVIDIA_C77.DEV_084C.1 = "NVIDIA nForce 780a SLI"

NVIDIA_C77.DEV_084D.1 = "NVIDIA nForce 750a SLI"

NVIDIA_C77.DEV_084F.1 = "NVIDIA GeForce 8100 / nForce 720a"

NVIDIA_C79.DEV_0860.1 = "NVIDIA GeForce 9400"

Protect your android from theft

I must recommend the following android applications as the best to protect and find your phone in case of theft:
1. Avast Mobile Security
2. Cerberus

I have tested many others but these came out the best with features, cost and especially rooted protection of the phone!
Also tried:
webroot, lookout, AVG, mcaffee,
Open Prey seems very good but pretty expensive!

Replace roomba power supply from 110v to 220v

http://gianmauro.wordpress.com/2006/12/29/irobot-roombascooba-110v-to-220v-mod/

http://www.schneordesign.com/Avi/irobot/roomba_mod1.htm

Compiling ATRIX Android firmware from source

http://forum.xda-developers.com/showthread.php?t=915435