VompClient for Window does not work at all computer (2000/XP)

[kanzler]

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

[MartenR]

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

Marten

[kanzler]

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? 

[MartenR]

Look into the readme.win file and generate a log file after the instructions therein.

Marten

[kanzler]

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!

[MartenR]

Unfortunetely DirectX 9 is not equal to DirectX 9. Please install a DirectX runtime newer or equal to DX9  February 2006.

Marten

[kanzler]

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.

[MartenR]

So the logs have changed after installing the runtime. So this part is fixed.
Now, I need to know the OS the graphics card for getting a better insight for this new error.

Marten

[kanzler]

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?

[MartenR]

This might be the reason. Unfortunetely this graphics card is not on my compatibility list. Maybe a can do a fix in Vomp maybe not, it depends on the graphics card capabilities. I'll send you a tool for determineing the graphic cards caps.

Btw, maybe using a newer driver might help!

Marten

[kanzler]

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.

[MartenR]

I have already send a mail to you at 8 o'clock using the mail address in your forum profile.
Did it arrive your inbox?

[dingo35]

I have on one computer exactly the same behaviour as described by the topic starter; on other computers all works well.

When starting vompclient it creates a white window and immediately exits. I installed directx9 from feb 2007. The log file says:
Could not create Direct3D9 device!

When I start graphedit.exe, it displays MPV decoder filter connected to Video Renderer, not Video Mixing Renderer 9, so this is obviously my problem.
Removing the connection MPV -> Video Renderer is ok, but when I try to connect MPV Decoder to Video Mixing Renderer 9 it says:

These filters cannot agree on a connection. Verify type compatibility of input pin and output pin. (Return code 0x80040217)

I don't understand, because on two other computers (all win xp sp 2) this all installed perfectly well.

Anybody any clue?

[MartenR]

@dingo35
If it already exists at Direct3d device creation, some thing of your DirectX installation might be wrong, thus a not 3d capable graphics card or switched of 3d acceleration etc. .

So what type of graphics card are you are using, what os (also xp) , did you turn off graphics card accelaration in the control panel?

Marten

[dingo35]

@dingo35
If it already exists at Direct3d device creation, some thing of your DirectX installation might be wrong, thus a not 3d capable graphics card or switched of 3d acceleration etc. .

So what type of graphics card are you are using, what os (also xp) , did you turn off graphics card accelaration in the control panel?

Marten

Hi Marten, thx for your quick response. Graphics card is onboard Sis 730 chipset, on Windows XP sp2, Directx9,0c redist feb 2007 . Dxdiag reports hardware accell is active and all tests are working fine. Direct3d is reported active and test is working fine.

I am not an expert, but this is my only PC having this graphics chipset, so I agree with your suspicion that this probably is a compatibility issue. The main question is: why does this pretty "standard" chipset does not match Video Mixing Renderer 9 ? Any idea where to look/what to look for?

Thx, Hans.