| DD
Tournament Poker
Locating Windows Installer Log Files
and Debugging Steps
If you are having a problem installing
DD Tournament Poker, it is helpful to send us any log files that
the installer generates. You may also wish to try the debugging
steps mentioned in step 6 of this document.
To locate these files, follow the steps below. |
 |
Start Windows Explorer (part 1) - Choose
Run... in Start Menu
|
 |
Start Windows Explorer (part 2) - Type explorer
and click OK
|
 |
Navigate to installer temporary folder. (Windows XP / 2000 / 2003)
(Windows 98 / Me see below)
Go
to these folders:
- My Computer
- C: (Hard Disk or Local Disk)
- Documents and Settings
- [your name] (look for a folder with your
name or your user id)
- Local Settings (you may need to "Show Hidden Files" to view Local Settings under Tools, Folder Options, View)
- Temp
Once you find the temporary directory, sort by Date Modified
(so arrow on Date Modified column is pointing up).
Then locate the most recent folder that starts with a capital
I and followed by a bunch of digits. Open that folder and go to
step 4.
Navigate to installer temporary folder. (Windows 98 / Me)
Go to these folders:
- My Computer
- C: (Hard Disk or Local Disk)
- Windows
- Temp
Once you find the temporary directory, sort by Date Modified (so arrow on Date Modified column is pointing up).
Then locate the most recent folder that starts with a capital I and followed by a bunch of digits. Open that folder and go to step 4.
|
 |
Navigate to Windows folder inside. Go to these
folders
- I1095603286 (the folder from the previous
step; your folder will have different digits)
- Windows
In the Windows folder, you will see 2 or 3 log files (ddpokererr.txt,
ddpokerout.txt and hs_err_pid3260.log
(yours will have different digits). Email us all of these
files.
Note: The installer launcher is located here
too (called poker.exe). Some customers have reported
that running the installer by double clicking on the launcher
in this folder sometimes fixes the problem, so that is worth a
try.
|
 |
Hint: If you don't see the file extensions
like shown above (for example, .txt,
.exe, .dll,
etc.), then you need to change your folder options as follows:
a) Choose Tools -> Folder Options...
b) Select View tab
c) Uncheck the box next to "Hide extensions for
known file types"
d) Click OK |
 |
Determining Bad Fonts
If you found a log file named like hs_err_pidNNNN.log
then you may want to look at it with Notepad. If there is an error
in the hs_err_pidNNNN.log
file that has the line "Current
Java thread: at sun.awt.font.NativeFontWrapper.registerFonts(Native
Method)" then you have bad fonts on your system. To
identify them, follow the steps below to use our tool to identify
the bad fonts:
- Save fonttest.bat and FontTest.class
to the Windows directory you found above (right
click on the links and choose "Save Target As..."
and navigate to the Windows directory by navigating through
the same folders as listed above).
- After saving the two files in Step 1, from Windows Explorer,
double click on fonttest.bat. This will launch
a black DOS window which attempts to launch a simple Java application.
As Java processes the fonts on your system, it lists them. This
application should crash just like the installer - the last
font listed before the error message is usually the bad font
(see example below).
You can delete it or move it from C:\Windows\Fonts
and run fonttest.bat again until you get a window that says
"Java Launched Successfully". At that point, you should
be able to successfully run the DD Poker installer.
NOTE: Previous customers who ran into this
problem found a problem with the following fonts (if you find
a problem font, send it to us so we can list it here):
- lsansi.ttf
- bddenver.ttf
- bdenver.ttf
- bdspring.ttf
- signatur.ttf
- Amazonn_.ttf
|
 |
Sample output of fonttest.bat
When you run fonttest.bat you will see output like this (you
may need to scroll up in the window to find the right line). The
last font listed before the "An unexpected
exception" line is the bad one (highlighted in red
below). In this example, you would delete c:\WINDOWS\Fonts\LSANSI.TTF.
After deleting the one bad font, re-run fonttest until you don't
get an error.
...
C:\WINDOWS\Fonts\jenkt.ttf - CMAP 3,1 found at offset 292.
opened font file C:\WINDOWS\Fonts\jokewood.ttf fd=20
closing font descriptor 10
C:\WINDOWS\Fonts\jokewood.ttf - CMAP 3,1 found at offset 292.
opened font file C:\WINDOWS\Fonts\LATHA.TTF fd=10
closing font descriptor 11
C:\WINDOWS\Fonts\LATHA.TTF - CMAP 3,1 found at offset 282.
opened font file C:\WINDOWS\Fonts\LSANSI.TTF
fd=11
closing font descriptor 12
C:\WINDOWS\Fonts\LSANSI.TTF - CMAP
3,1 found at offset 282.
An
unexpected exception has been detected in native code outside
the VM.(ERROR
LINE - LOOK FOR THIS - THEN LOOK AT LAST FONT BEFORE THIS LINE)
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x2E12382
Function=Java_sun_awt_font_GlyphList_discardData+0x63F2
Library=C:\Program Files\ddpoker\jre\bin\fontmanager.dll
Current Java thread:
at sun.awt.font.NativeFontWrapper.registerFonts(Native Method)
- locked <0x141ffb70> (a java.lang.Class)
...
|
|
