gdipp 0.8.2 fails to start with Vista x64 clean installation, 0.7.6 works fine for now.

[GoogleCodeExporter]

Which program triggers the problem? Specify the filename if possible.
Vista x64 SP2 clean install

What steps will reproduce the problem?
1. Just trying to start the service v. 0.8.2
2.
3.

What is the expected output? What do you see instead?
Expect the service to start properly.

What version of gdipp (including renderer)? On which operating system?
0.8.2 - Vista x64 SP2

Please provide any additional information below. Screenshots always help.

Original issue reported on code.google.com by derin.es...@gmail.com on 5 Jul 2010 at 1:18

[GoogleCodeExporter]

What is the problem? The service failed to start or started but no rendering?

Original comment by crendk...@gmail.com on 5 Jul 2010 at 3:50

[GoogleCodeExporter]

Hi there!

First off, let me thank you for the effort. The 0.7.6 version seems to work 
stably. Also the result of the rendering is much better IMHO than Clear Type! 
So Thanks.

In any case, the service just did not start. When the service was starting, I 
received an error message to the effect of gdipp.dll being unable to be 
started. That's all I can say really.

Other than that, this is a clean OS, not much installed on it besides a couple 
of browsers and open office. I am using 120 dpi for fonts but I suspect that 
that would be an issue. I have not upgraded to IE8, but again that would not 
seem to be an issue either I'd guess. 

On the other hand, There are a few questions and comments about the program 
that I have. Where should I post those?

Best.

Original comment by derin.es...@gmail.com on 5 Jul 2010 at 4:14

[GoogleCodeExporter]

Can you upload the screenshot of the error message dialog?

Original comment by crendk...@gmail.com on 5 Jul 2010 at 8:10

[GoogleCodeExporter]

I receive the error twice. I guess once per service. I have used the service 
installer by the way...

Below is the contents of the "View Details" box of one of the error messages:

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name: gdipp_hook_64.exe
  Application Version:  0.8.2.0
  Application Timestamp:    4c2f22f8
  Fault Module Name:    d2d1.dll
  Fault Module Version: 6.0.6002.18005
  Fault Module Timestamp:   49e0421d
  Exception Code:   c0000135
  Exception Offset: 00000000000b8fb8
  OS Version:   6.0.6002.2.2.0.256.1
  Locale ID:    1033
  Additional Information 1: fa3e
  Additional Information 2: ac0507478d1c5bd693cfc4fe3987e900
  Additional Information 3: fa3e
  Additional Information 4: ac0507478d1c5bd693cfc4fe3987e900

Original comment by derin.es...@gmail.com on 5 Jul 2010 at 8:54

Attachments:

• gdipp_Hook_error.jpg

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Looking at other threads, I also tried delayed service start. But that only 
delays the crash. Also, the crash occurs right after installation as well...

I also have no anti virus software or security suite installed. UAC is turned 
on, so I tried turning it off which did not make a difference. 

Original comment by derin.es...@gmail.com on 5 Jul 2010 at 10:33

[GoogleCodeExporter]

From the error report, I see the fault module is actually in d2d1.dll, not any 
of gdipp's. Considering you are using Windows Vista, you may probably need to 
install the Platform Update, which is essential for DirectWrite. The 64-bit 
package can be downloaded at 
http://www.microsoft.com/downloads/details.aspx?FamilyId=e2da6ef8-92b6-4370-9e22
-2c05a8c37ab0&displaylang=en. If the problem still exists, let me know. Thanks.

Original comment by crendk...@gmail.com on 6 Jul 2010 at 7:43

• Changed state: Accepted

[GoogleCodeExporter]

Thanks for the update. Unfortunately I will not be able to confirm whether the 
platform update worked. When I tried doing the update, it sent my Vista 
installation into a tailspin of infinite reboots! Man, this was only a side 
project where I was checking some software out as I am on a Mac now for about a 
year now. How glad I am that I had made the switch. This is ridiculous. In any 
case, thanks for your effort. 

Original comment by derin.es...@gmail.com on 6 Jul 2010 at 9:14

[GoogleCodeExporter]

I'm very sorry for the trouble. I'm not sure if the update is compatible with 
your system, or there is some bug in the update. I personally use Windows 7, so 
there is no need for the update. I heard that some update package may cause 
system to infinite reboot.

Currently there is nothing I can do to remedy your loss. I can only say that 
anybody with similar problem should exercise caution on applying the update.

Original comment by crendk...@gmail.com on 6 Jul 2010 at 10:33

[GoogleCodeExporter]

Hey mate, it's not your fault at all! To make things "safer" I actually went 
through the windows update interface and not used the direct download. There 
was another platform update item there. It's description was the same as the 
download you linked to but it's KB# was slightly lower than the one you had 
linked to. In any case I went through with that, again which was brought up by 
Windows Update as an optional update. You know the rest. It's a shame really. 
No wonder the outcry against Vista... I wish you well in your efforts to bring 
better font rendering to Windows...

And by the way. Let me make those few comments that I had before I leave; I'm 
sure you are already thinking about this but if you gave GUI access to the 
settings in the xml file with previews and all, that would be awesome - maybe 
like the one in various Linux distributions. Also, as far as I understand, your 
algorithm is already pushing stuff it can't render forward to clear type. It 
might make sense to build a mechanism where the user can also manually exclude 
certain programs from the gdipp rendering engine. Just as a safety and 
versatility measure.

Original comment by derin.es...@gmail.com on 6 Jul 2010 at 8:44

[GoogleCodeExporter]

For your comments:

GUI access is supposed to be the work of gdipp Preview, shipped as the name of 
gdipp_pre_xx.exe. There are many reasons I have not contribute time on it. The 
main one is the internal infrastructure of this project is still about to 
change dramatically. GUI access of the old infrastructure could be a waste of 
time for the new infrastructure.

To exclude a program from rendered by gdipp, simply put its executable name in 
the <exclude> node. The last section of 
http://code.google.com/p/gdipp/wiki/SETTING_Beta contains instruction of this 
node. You can also learn from the default setting.

Original comment by crendk...@gmail.com on 7 Jul 2010 at 6:12

[GoogleCodeExporter]

If your problem is still unsolved, try the upcoming 0.9.1. If problem still 
exists, reopen this issue. Thanks!

Original comment by crendk...@gmail.com on 18 Sep 2010 at 4:02

• Changed state: Fixed