User:Black Fox

http://stuff.black-fox.cz/bf_ava.png

Name: Radek Liška

Nick: Black_Fox

Country: Czechia (also known as Czech Republic if you want to be really formal)

E-mail: radekliska [att] gmail [ddot] com

How to reach me: PMs at forum, I don't really lurk in IRC currently

Area of interest at ReactOS: I've been the only active Czech translation maintainer since early 2008, I go to JIRA from time to time to retest old bugs and rarely even do some patches for code, HW testing ability since early 2014

Goal: To be permanently able to invest more time into ROS, finish Czech translation, unify Czech translation, submit some more code patches/tests, get my test notebooks to install and boot to ROS.

Random Facts:

- birthday: June 26th

- testing configs: VirtualBox in newest available version, Lenovo T400, Toshiba Satellite A50-101, QEMU (no longer)

- I even donated some money to foundation! The total sum of my donations is now around €100. Imitate me for the good of the project ;)

Random info for my easier finding:

- set condition * first always

- tab+k, bt, proc [list|attach], thread [list|attach]

- putty: 115200, don't forget to switch from XON/XOFF to the RTS/CTS (need to verify this)

- Logging into file - KDBinit - do I really have to set something before I'm able to log into file?

- Forum tutorial: How to get debug output from VirtualBox in Windows

- Forum tutorial: How to create translation patch from TortoiseSVN in Windows

---

OBSOLETE/OUT OF DATE:

Tested software (newest on top) - all results since rewrite of CompatDB have been inserted into it as well, this is just for personal reference

App	Rev	VMWA	QEMU	VBOX	RHDW	SEE BUGS	DESCRIPTION
qutIM 0.2 + ICQ + Jabber	47102	NTD	NTD	PARTIALLY	NTD		Situation is completely the same as in r44199.
qutIM 0.2 + ICQ + Jabber	44199	NTD	NTD	PARTIALLY	NTD		Seems to work, but cannot connect -> no idea if it works for sure. Anyway it gets a lot further than the previous test.
qutIM 0.2 beta2 + ICQ	42470	NTD	NO	NTD	NTD	4789	Either takes ages to start or hangs somewhere (main thread is ready, other thread is waiting for something). VM does NOT hang on assert, but backtrace looks exactly the same in the waiting thread (ending with "Couldn't access memory at 0x0C20B4BC!").