Of course, before start working, the car needs to be jacked up and securely supported by jackstands and wheel chucks.

First, remove all but the screws on drivers side. The bolt specification of my car is unknown. 5/16″ socket fits best. M6-1.0 x 16mm hex flanged cap screws works too. There are 19 bolts on my pan, try not to lose them. I lost one and that experience is maddening… I eventually found the lost screw. Next time, I will either put that back or replace all of them with the M6-1.0 x 16mm screws.

Let the ATF fluid drain for a bit. When the draining stops, remove the pan completely. Be aware that there are still considerable amount of the fluid in the pan at this point. Try to spill at little as possible, as it will not only make a smaller mess but also provide reference to the # of Qt that needed to be added back in.

According to the transmission fluid pan, mine tranny is a AX4N. The pan is equipped with a reusable gasket. Since this gasket is sort of bolted on the pan and looks much nicer than the king pro disposable one I bought, I decided to reuse the old gasket. I suspect to replace the gasket, one will need to just buy a OEM pan.

Once the pan is completely off, pull down to remove the ATF filter. Don’t forget to also remove the filter o-ring. A small flat-head screw driver and a pair of needle nose pliers will make the job significantly faster. In the mean time, try not to damage the inner surface of the aluminum tube inside which the o-ring is located.

The feel the slury the bottom of the pan and inspect the magnet. Mine feels smooth and there is no small pieces of metal. There are ~2mm thick fluffy impurities on the magnet. Not sure if this is a normal accumulation over two years or it’s because the previous owner did not drop pan when flushing tranny fluid. Clean the pan and magnet with Break cleaner. One can is most likely enough. I bought two on the safe side.

While waiting for the pan to air dry, wipe the mating surface on the transmission side to make sure it is smooth. Then bolt the pan back on. First get the bolts finger tight, then tighen in cross pattern until it is snug. If a torque wrench is available, torque to ~6-8ft*lb (9ft*lb max).

Since the collected old fluid measures ~6Qt (probably ~0.5Qt to 1Qt more including spill), replace 6Qt of new fluid. Checking underneath the car to make sure there is no leak. Don’t be fooled by the spilled ATF fluid flowing down the outside of dipstick tube.

Lower the car. Start the engine, let it run for a few min while pay attention to dashboard lights and car sound. Run the shifter from P to 1 and back a few times, then check fluid level. Add more fluid as needed.

Go driver around then come back and check fluid again.

Keep an eye on fluid level in the next few trips for leaks and levels.

General steps include:

Frist, backup GPS. Do so using windows explorer and copy all the files, including any hidden file from GPS to a backup location.

Second, extract navcore and ttsystem files into the root directory of the GPS. Note that downloaded winrar files typically contain only one folder named navcorexxxx and ttsystemxxx, go into these folders and extract all the files. After this step, the GPS root directory should contain a whole bunch of folders and files.

Third, patch the navcore and ttsystem using appropriate patching programs. Some program maybe reported to anti-virus as containing trojan horses. Authors of the program claims that they have no virus and the detection is triggered by some feature of the program. Some kind of code-need-to-stay-in-memory stuff. This will require temporarily disable real time protection of the anti-virus.

Fourth, generate map keys for the device using appropriate key gen.  Map keys are generated based on meta data associated with the map. Example, “8B 00 88 3D B5 C9 EA FD 01 3B DB 3C C4 5D 4A AE United_States-141.meta    ; United_States_845_2667″ is a meta data associated with a map of US v8.45.2667. Information behinde the “;” are comments. Before running the keygen, should update any meta.txt file the keygen has and make sure this meta data is included.

Once that is complete, GPS is updated.

From: http://www.mitbbs.com/article_t/PDA/31251983.html by red007007

Step 1. find your device code. http://htc-n-gps.blogspot.com/2007/04/how-to-check-device-code-for-tomtom-6.html (thanks to cyb (葱油饼|无药可救));

Step 2. copy everything in the device to make a backup;

Before actually wiping the device, might be useful to extract all the files into a folder on the computer and make sure that the size of the folder is sufficiently small to fit on the device.

Step 3. format the device (choose fat32 format);

Step 4. downloads the following files and extract to your device‘s root directory (file links
provided by ferrygao);

Navcore: http://rapidshare.com/files/293835147/SE_Navcore.9004.1804.Basicpack.rar

ttsystem:  http://rapidshare.com/files/293840695/SE_ttsystem.9004.1804.rar
maps: http://forum.ppcwarez.org/viewtopic.php?f=265&t=78832

Step 5. download Keygen: http://www.linksave.in/1271195344a34abbb7659a (file link provided by ferrygao); extract the file to your computer drive;

Step 6. run RunMeforAllAutomatic from your computer. Choose option 1 and
then select the correct drive of your GPS device, input your device code at
prompt;

Step 7.download voice file. http://depositfiles.com/files/7bgmxkqyh; extract to your GPS device; then rename the folder (enu_Samantha) as VocalizerTTS.

Comment: enu-Samantha is a “.cab” file. Extract files in the “.cab” archive into a folder called “enu_Samantha” and then rename the folder to “VocalizerTTS”. Note that this may be case sensitive, so caps might be important
Step 8. Reset your GPS device by pressing and holding the power switch for
15 seconds. You should see a black screen with system information. Turn off
the GPS.

Step 9. Restart and your device is now map-updated and TTS for street names.

Enjoy. Many thanks to cyp,IMKirby,iloli,and xhxh.

After the above steps, GPS has TTS working, but is extremely sluggish. Suspect might be because of low disk space (970MB/977MB). Deleted some files from the “Helpme” directory and freed up ~2MB of space. The GPS runs better. A few problem remained:

1. Center panel that shows turning instructions are squished, looks like the navcore is intended for a wide-screen unit

2. Device is still at little slow at time, low free ram ~2MB free. But suspect the device is actually usable in the current states

二零零八年十二月八日探家

轻骑负剑出蓟门，

且访大道且修身。

六载浮萍逐云月，

一夕嘉陵洗风尘。

<JWM>
<Tray  autohide=”false” insert=”right” x=”0″ y=”-1″ border=”1″ height=”28″ >
<!– Additional TrayButton attribute: label –>
<TrayButton label=”开始” icon=”mini-dog.xpm”>root:3</TrayButton>
<TrayButton popup=”显示桌面” icon=”showdesk16.xpm”>showdesktop</TrayButton>
<TrayButton popup=”Run commandline” icon=”gexec.xpm”>exec:gexec</TrayButton>
<TrayButton popup=”Geany” icon=”geany.xpm”>exec:geany</TrayButton>
<TrayButton popup=”文件管理器” icon=”mini-folder.xpm”>exec:rox</TrayButton>
<TrayButton popup=”终端” icon=”xterm.xpm”>exec:rxvt</TrayButton>
<TrayButton popup=”SeaMonkey浏览器” icon=”mozilla.xpm”>exec:seamonkey</TrayButton>
<TrayButton popup=”Opera浏览器” icon=”opera.png”>exec:opera</TrayButton>

<!– Additional Pager attributes; width, height –>
<Pager/>
<!– Additional TaskList attribute: maxwidth –>
<TaskList/>
<Dock/>
<!– Additional Swallow attribute: height –>
<Swallow name=”blinky”>
blinkydelayed -bg “#DCDAD5″
</Swallow>
<Swallow name=”asapm”>
asapmshell -u 4
</Swallow>
<Swallow name=”freememapplet”>
freememappletshell
</Swallow>
<Swallow name=”xload” width=”32″>
xload -nolabel -fg red -hl white -bg “#888888″
</Swallow>
<Clock>minixcal</Clock>
</Tray>
</JWM>

p.s. the icon files are located at /usr/share/mini-icons folder.

http://ubuntuforums.org/showpost.php?p=5031046&postcount=3

file name: 99-hdd-spin-fix.sh
#!/bin/sh
hdparm -B 254 /dev/hda

cp 99-hdd-spin-fix.sh /etc/acpi/suspend.d/
cp 99-hdd-spin-fix.sh /etc/acpi/resume.d/
cp 99-hdd-spin-fix.sh /etc/acpi/start.d/

“VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Please install the virtualbox-

ose-modules package for your kernel and execute ‘modprobe vboxdrv’ as root.
VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).”

A quick search found the followinghttps:

//bugs.launchpad.net/ubuntu/+source/virtualbox-ose-modules/+bug/214393

following the advise:

run “uname -a“

Linux sliverstone 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

run “dpkg -l |grep virtualbox-ose“

ii  virtualbox-ose                             1.5.6-dfsg-6ubuntu1                                x86 virtualization solution – binaries
ii  virtualbox-ose-modules-2.6.22-14-generic   6                                                  virtualbox-ose modules for linux-image-2.6.2
It seems that the failure during upgrade failed to upgrade the  the virtualbox-ose-module.

hence, run:

sudo apt-get install virtualbox-ose-modules-2.6.24-16-generic

After installation, the problem is solve.

GNU Screen

This article first appeared when I wrote it for Kuro5hin. If you want to read the original version of the article with comments containing some useful Screen tips and tricks, here is the original, archived article at Kuro5hin.

There is also a French version of this article available, translated by Geoffrey.

Most modern Unix-based operating systems (e.g. Linux, MacOS X, and BSD) come with a little console-mode utility called GNU Screen. It’s a powerful tool in the hands of the console warrior, a veritable Swiss Army knife of text-mode human-computer interaction.

This utility, despite its considerable usefulness, goes unused by a great many people. Why is this? Few people even know it’s there, and those that do rarely understand the problem it solves. In this article, I will explain what screen does for you, and provide a simple set of instructions for accomplishing basic tasks using screen. My audience is those that are skilled with the command line but who have little or no experience with screen itself.

What screen does

Screen is best described as a terminal multiplexer. Using it, you can run any number of console-based applications–interactive command shells, curses-based applications, text editors, etc.–within a single terminal. The desire to do this is what gets most people hooked on screen. I used to start a half-dozen terminal emulators when I logged into my machine: I wanted one to read my email, one to edit my code, one to compile my code, one for my newsreader, one for a shell into my web host, and so on. Now I start one terminal emulator, and run screen in it. Problem solved.

The other main cool feature of screen is its ability to decouple the terminal emulator from the running programs. This means that you can use screen to keep programs running after you accidentally close the terminal emulator, or even after you log out, and later resume right where you were. It means that the idea of a “session” in which you are running a number of console programs is a free-floating entity that you can bind to any terminal anywhere, or no terminal at all if you want.

Getting started with screen: launching and switching between programs

Start screen just by typing screen at your favorite command shell prompt. You’ll probably be greeted by a welcome message. Dismiss this and you’ll have an empty terminal containing a shell prompt, which is pretty much what you had before you started screen. What happened?

Every program running under screen runs in a window, and every window is identified by a unique number. Screen made a new window, numbered it 0, and started a command shell inside it. Type something in your new window so you’ll be able to recognize it when you switch to it later.

Now make another window; this will be window 1. To do this, type C-a c; that is, type Ctrl-a and then type c (mnemonic: create window).

Now that you have two windows, try switching between them. To do this, type C-a C-a, which will switch you to whichever window you were using before the current one. Some other useful window switching methods, which you’ll need if you plan to run more than two programs:

1. Use C-a n and C-a p to switch to the next or previous window in the list, by number.
2. Use C-a N, where N is a number from 0 to 9, to switch to the corresponding window.
3. Use C-a " to get a full-screen list of windows. You can navigate this list with the arrow keys (or vi-style, with j and k), and pick a window to activate by pressing Enter when it’s highlighted. C-a w will give you a small, non-interactive list of windows.

Detaching and reattaching: the magic of terminal decoupling

If you did the exercise above, you have successfully created a screen session. You can detach from this session by pressing C-a d. You can also detach just by closing the terminal emulator that contains the session. However, keep in mind that neither of these actually end your session. All they do is unbind your session from the current terminal. All of the programs you started running within screen are still running. Really.

Try it: just close whatever terminal emulator you were using to do the exercise above. Then log out, and log back in, if you desire. Start up a new terminal emulator, and type screen -r (the R, obviously, stands for “reattach”). You’ll be right back where you were when you detached.

You can probably imagine a lot of good uses for this. You can start all your favorite console programs once and just leave them running in a persistent screen session. Some people have “screen uptimes” of several months.

One other good use for the detach and reattach is as a console-mode “remote desktop” feature. You can detach from a screen session at work, shell into the machine from home, and reattach. Very, very handy. With a bit of extra work, you can even have a number of terminals all attached to the same session–great for collaborative efforts and meetings.

Copying, pasting, and the scrollback buffer

Screen remembers a configurable number of scrollback lines, and you’ll need them because you won’t be able to use your terminal emulator’s scroll features while running screen. You can access the scrollback buffer by entering “copy mode”, which is accomplished by typing C-a [. You can mark text anywhere in the scrollback buffer and paste it with C-a ]. Screen is also capable of logging to files, but that’s beyond the scope of this tutorial.

Monitoring for silence and activity

One of the disadvantages of running a bunch of programs within screen is that you can’t keep an eye on all of them at the same time, since in general you can only see one at once. (Actually, you can split the screen and look at more than one at a time, but that’s an advanced topic beyond the scope of this tutorial.) To help mitigate this problem, Screen has features that allow you to monitor a window for silence–useful for knowing when a compile has finished, for example–or activity–useful for knowing when someone is finally talking on your favorite IRC channel, for example.

To start or stop monitoring the current window for 30 seconds of silence, type C-a _; to start or stop monitoring a window for activity, type C-a M.

Making it go away

As you’ve seen from the section on detaching and reattaching, screen is not easy to kill. You can’t just close its containing terminal. (Actually, you can, but then all those processes are still running on your system, ready to be reattached.)

To my knowledge, the only way to do this nicely (i.e. without sending nasty signals to processes that don’t deserve it) is to close each of your screen windows. Exit whatever programs or shells each is running, and they will go away. When the last program running inside screen is exited, screen itself will go away. You can forcefully quit screen with C-a C-\, but I wouldn’t recommend it.

Other stuff

Screen does much, much more than I’ve described above, but it’s enough to get you started. You can type C-a ? for a terse list of commands available while you’re in screen. The screen man page has a wealth of info, too. And here are some web resources, if you have questions: