Hi,

Hmm...Hard to say without actually seeing the source code and testing.
However, by the sounds of it there could be a problem with a string
not properly being converted to unicode before being passed to a COM
object. However, since Windows COM objects only accept unicode anyway
I would think the compiler would catch that error and refuse to build
the program so you got me on that one.

On 12/28/11, Clement Chou <[email protected]> wrote:
> I'm trying to start a game for my pc... it's configured for Japanese
> computers and screen readers, and when I start the game I get a message that
> says "error 39 in line -1." I have no idea what the problem is, but I know
> it has a problem with com objects or something... because that was what the
> developer told me, and when he deleted the com object in the executable, the
> game worked fine. However, the game works fine on my desktop. It seems to be
> only my laptop that has this issue... but I have Japanese support set up on
> my laptop so I don't think it's the text recognition acting up... so what is
> the problem? Any of the computer wizzes know anything? Thanks!
> ---
> Gamers mailing list __ [email protected]
> If you want to leave the list, send E-mail to
> [email protected].
> You can make changes or update your subscription via the web, at
> http://mail.audyssey.org/mailman/listinfo/gamers_audyssey.org.
> All messages are archived and can be searched and read at
> http://www.mail-archive.com/[email protected].
> If you have any questions or concerns regarding the management of the list,
> please send E-mail to [email protected].
>

---
Gamers mailing list __ [email protected]
If you want to leave the list, send E-mail to [email protected].
You can make changes or update your subscription via the web, at
http://mail.audyssey.org/mailman/listinfo/gamers_audyssey.org.
All messages are archived and can be searched and read at
http://www.mail-archive.com/[email protected].
If you have any questions or concerns regarding the management of the list,
please send E-mail to [email protected].

Reply via email to