Add wintab section

debug.md

@@ -4,7 +4,7 @@ In case that you are having some problem running Aseprite, you can
 execute it with the `--debug` option in the command line.
 
 After running Aseprite, you will see that a
-`Aseprite-v1.1.9-DebugOutput.txt` file (or with a similar name) will
+`Aseprite-v1.2-DebugOutput.txt` file (or with a similar name) will
 be created in your desktop.  You can send us that file at
 [[email protected]](mailto:[email protected]) so we can help us
 solving your specific problem.

troubleshooting.md

@@ -4,19 +4,21 @@ If you have a problem starting Aseprite (e.g. it starts and closes
 inmediately), you can try:
 
 1. [Reset your preferences](reset-preferences.md)
-2. Use the [debug option](debug.md) to send a report to [[email protected]](mailto:[email protected])
+1. Use the [debug option](debug.md), this generates a `Aseprite-v1.2-DebugOutput.txt` file
+1. Windows only: Check if the last line of the generated
+   `Aseprite-v1.2-DebugOutput.txt` file says:
+   `PEN: Wintab library loaded`. If that is the case, try [disabling Wintab](wintab.md).
+1. In other case, contact us at
+   [[email protected]](mailto:[email protected]) with the
+   `Aseprite-v1.2-DebugOutput.txt` file.
 
-You might try to find your problem on:
+You might also try to find your problem on:
 
 * [Aseprite Community](https://community.aseprite.org)
 * [Steam General Discussion forum](http://steamcommunity.com/app/431730/discussions/0/)
 * [Steam Bug Reports forum](http://steamcommunity.com/app/431730/discussions/2/)
 * [Closed bugs on the GitHub](https://github.com/aseprite/aseprite/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20%20label%3Abug)
 
-As usual, you can always contact us at
-[[email protected]](mailto:[email protected]) for any kind of
-problem or issue.
-
 ---
 
 **SEE ALSO**

wintab.md

@@ -0,0 +1,23 @@
+# WinTab
+
+`WinTab32.dll` is a library/DLL/API used to communicate with your
+stylus/tablet (Wacom, etc.). Sometimes, when we load this DLL the
+program just hangs. We don't know why this happen, but there are few
+users experimenting this (maybe a buggy `WinTab32.dll`, or maybe a
+buggy Aseprite).
+
+Sometimes the problem is solved reinstalling the driver, sometimes the
+problem persists. In these cases you can execute Aseprite with
+`--disable-wintab` parameter (available since Aseprite v1.2):
+
+    "C:\Program Files\Aseprite\Aseprite.exe" --disable-wintab
+
+This will bypass the `WinTab32.dll` loading process. Your stylus might
+not work correctly, but at least Aseprite can be executed and used
+with your mouse/trackpad.
+
+---
+
+**SEE ALSO**
+
+[Troubleshooting](troubleshooting.md)