Messages

I have tried to get a newer driver version for my graphics card, but unfortunetely I use the newest one.

Ok. I will wait for you.

At this time, I tried out the vompclient at WinXP on 2 different computers. The both graphiccards have the Intel815 chipset (Dell Optiplex GX150, HP Vectra VL400). What are the minimum requirements for computers to use vomp?

Now I have tried 2 other DirectX Patches. It does not work at all. When I start the client, the window from vompclient.exe is white but nothing happens. The client hangs up.

Here the logfile.
11:34:52.000754 [info]   Core - Starting up...
11:34:52.000754 [info]   Core - Remote module initialised
11:34:52.000754 [info]   Core - LED module initialised
11:34:52.000754 [info]   Core - Mtd module initialised
11:34:52.000754 [info]   Core - Timers module initialised
11:34:52.000754 [info]   Core - Read from MTD: PAL 720x576
11:34:52.000754 [info]   Core - Video module initialised

That´s all.

I have used the directx version 2/2007 and 8/2006.

I hope you have another idea.

Hi,
here is the logfile information. I think the problem is the directx software, but why?
I hope you can solve my problem.

20:32:44.000859 [info]   Core - Starting up...
20:32:44.000859 [info]   Core - Remote module initialised
20:32:44.000859 [info]   Core - LED module initialised
20:32:44.000859 [info]   Core - Mtd module initialised
20:32:44.000859 [info]   Core - Timers module initialised
20:32:44.000859 [info]   Core - Read from MTD: PAL 720x576
20:32:44.000859 [info]   Core - Video module initialised
20:32:44.000890 [WARN]   OSD - Could not create Direct3D9 device!
20:32:44.000890 [EMERG]  Core - OSD module failed to initialise
20:32:44.000890 [notice] Core - ViewMan module shut down
20:32:44.000890 [notice] Core - Command module shut down
20:32:44.000890 [notice] Core - VDR module shut down
20:32:44.000890 [notice] Core - OSD module shut down
20:32:44.000890 [notice] Core - Audio module shut down
20:32:44.000890 [notice] Core - Video module shut down
20:32:44.000890 [debug]  Timers - Timers shutdown start
20:32:44.000890 [debug]  Timers - Timers shutdown end
20:32:44.000890 [notice] Core - Timers module shut down
20:32:44.000890 [notice] Core - MTD module shut down
20:32:44.000890 [notice] Core - LED module shut down
20:32:44.000890 [notice] Core - Remote module shut down
20:32:44.000890 [notice] Core - Log module shutting down... bye!

Take a look at http://www.loggytronic.com/forum/index.php?topic=195.0 maybe this helps.

Marten

I have read this before, but it did not work. Is it a problem with a missing DLL?
All the computers have the same microsoft patch level.

Do you have an idea? 

Hallo,

I would use the vompclient for windows on my computers. On some computers the client works well and on serveral other computers the client does not work. At all computers they have the some windows updates and powerdvd software. When I will start the client, the windows opens and the windows is closed. I can not the message "connecting to server" because the window is closed.

Can you help me to solve my problem? Can you give me the name of all DLL files that the client will use?

Thx.
DER KANZLER