8thString

This to document minimal installation of Debian 4.0 (Etch) on VirtualBox host. Download latest Debian Etch, I am using debian-40r3-i386-netinst.iso. During the package installation, deselect all. This should give you a minimal Debian installation. During installation, you say "No" during selecting the mirror. We will update /etc/app/sources.list after the installation anyway. Reboot virtual machine after installation. Add the following lines to your /etc/apt/sources.list, I am using nano to edit sources.list file. Since I am near Hongkong, I selected the mirror sites as shown below, change this as you see fit: hostname:/# nano -w /etc/apt/sources.list Additional entries into /etc/apt/sources.list #more entries from here of course from /etc/apt/sources.list deb http://ftp.hk.debian.org/debian etch main contrib non-free deb-src http://ftp.hk.debian.org/debian etch main contrib non-free Then do: hostname:/# aptitude update hostname:/# aptitude upgrade The above command

Draft - draft - draft - draft /etc/app/sources.list deb http://update.eeepc.asus.com/p900 p900 main deb http://update.eeepc.asus.com/p900/en p900 main deb http://xnv4.xandros.com/xs2.0/pkg/ xs2.0-xn main non-free deb http://xnv4.xandros.com/xs2.0/upkg-srv2 etch main contrib non-free deb http://download.virtualbox.org/virtualbox/debian etch non-free add public keys wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | sudo apt-key add - sudo apt-get install xandros-archive-keyring sudo apt-get install build-essential download sources http://support.asus.com/download/download.aspx unrar x Eee_PC_900_source_code_part1.rar dpkg --install linux-source-2.6.21.4-eeepc_17_all.deb cd /usr/src tar xvjf linux-source-2.6.21.4-eeepc.tar.bz2 cd linux-source -2.6 .21 .4 -eeepc ln /usr/src/linux-2.6.21.4 /usr/src/linux -s cd /usr/src/linux make oldconfig make prepare make all apt-get install virtualbox create a file, /bin/vbox/run sudo nano /bin/vboxrun and paste: --

If you are are a console junkie and you frequently play around or look around what is running in your system you may find that using TaskManager can be time consuming and limiting. So I looked around and found a way to use pslist (from Windows Sysinternals) or tslist ( a built in command line ). The command below means to show information about a process running on "remote_machine" with process name of python.exe D:\><path_to_pslist>pslist.exe \\remote_machine | findstr python.exe This one is using the built in tslist command. Same as before, we want to query for a process named python.exe on "remote_machine." D:\> tslist /S remote_machine | findstr python ~ts

Additional repository for Eee PC 900, see link . Seems like location of simpleui.rc was changed in Eee900 PC. In my machine it is now located in: /var/lib/AsusLauncher/ ~ts

Vitrite is a tiny utility written by me,  Ryan VanMiddlesworth , that allows you to manually adjust the level of transparency for almost any visible window. It works by utilizing a feature present in Windows 2000/XP (and all later incarnations) for variable window transparency. WinSpy++ is a handy programmer's utility which can be used to select and view the properties of any window in the system. WinSpy is based around the Spy++ utility that ships with Microsoft Visual Studio. ~ts

I have VMWare Server 2.0 Beta x running on Windows Server 2008 Std 64bit. At only 2GB I can only run one virtual machine. So the machine was upgraded to 8GB! I didn't notice much performance improvement in the host machine but I can start kicking in four virtual machines. But......... The big but.. was that Windows Server 2008 just crashes randomly. Sometimes just a few minutes.. booom it crashes. Digging a little further I was able to simulate the crash pretty easily. Remote the machine's console session (/admin switch in mstsc.exe) then login back to the host machine. So I was thinking/asking myself, was it because of the new 8GB memory upgrade? It must be, but is it the hardware or software that does not like the upgrade. Trying to eliminate variables, I booted the machine into System Rescue CD then run memtest for two hours. No dice here. So it must not be the new memory being faulty. Digging more, I found out that there was a video error logged in Control Panel>

TestPartner run results can be exported using command line, tpexport, or via File|Export from with TestPartner itself. Another way of exporting run results is via TestPartner.TLB automation. The beauty with TestPartner.TLB is that you can export with it the xsl. See below for the code. Option Explicit Sub TestTPResultDump() Dim t As New TPApp Dim pCount As Integer Dim p As Integer Dim sCount As Integer Dim sName As String Dim tp2 As TestPartner.TPProject2 t.Login "admin", "admin", "TestPartner_SQL", 1 pCount = t.Projects.Count For p = 1 To pCount If t.Projects.Item(p).Name = "ScratchProject" Then Debug.Print t.Projects.Item(p).Name Set tp2 = t.Projects.Item(p) Dim rc As Integer For rc = 1 To tp2.Results.Count If tp2.Results.Item(rc).Name = "scratch2" Then Debug.Print tp2.Results.Item(rc).Description