Sharing XP-RC2 experience

[wkulecz]

I'll wager you're only running MS apps.

We need to run non-MS apps remotely and VNC on XP (I tested both RC1 and RC2) with its install defaults works much better than Remote Desktop. XP to XP, 100BaseTX full duplex connection. Based on Remote Destops performance on this link I don't see how you could do anything useful over a modem.

I guess it should be called "Remote Desktop for Microsoft Applications" instead if what you say is true.

As to configuring Remote Desktop I didn't see a lot of options.

--wally.

[smanzo]

Originally posted by wkulecz
I'll wager you're only running MS apps.

Nope. MS apps, Agent, eConsole, a few Stardock apps for color, some custom Payroll and Financial applications. I've also run VNC, Timbuktu and Teminal Server from my desktop machine on the LAN (10BaseT) from home (Modem) through my Remote Desktop connection

We need to run non-MS apps remotely and VNC on XP (I tested both RC1 and RC2) with its install defaults works much better than Remote Desktop. XP to XP, 100BaseTX full duplex connection. Based on Remote Destops performance on this link I don't see how you could do anything useful over a modem.

I guess it should be called "Remote Desktop for Microsoft Applications" instead if what you say is true.

Again, see above. I can't speak to your experience, but I can speak to mine. It just happens that they don't match.

As to configuring Remote Desktop I didn't see a lot of options.

--wally.

It's on the client side. If you use defaults over a LAN, it'll try to use full quality. From the client side, expand the Options button and check out the DISPLAY and EXPERIENCE tabs. Just for reference, my connection to my workstation on the remote modem PC is as follows:
1152*864*256 colors (DISPLAY)
Optimize for Modem (EXPERIENCE)
Show themes enabled, bitmap caching enabled
Desktop background, show contents of windows while dragging, menu and windows animation disabled.

[wkulecz]

I have two applications displaying real-time graphics. It blew me away that Remote Desktop was useless while VNC was almost there. My code seemed to work about as well over VNC as XP but the other application that I recieve windows messages from, over which I have no control and has its roots win 3.1, just didn't work over XP's Remote Desktop.

--wally.

[smanzo]

Fair enough. As I've said, IME Remote Desktop was stronger than VNC over a modem. The difference over the LAN is negligible, but I haven't tried real-time video.

[sergiovalentino]

RC2 + Marvel g400 no OpenGL hardware support.
And what about this not working Matrox crossover driver?

[wkulecz]

I am not trying to do video remotely, but I am plotting real time graphics. My signal processing complexity is probably about the same order of magnitude as an MPEG 1 decoder, but I only run about MP3 audio rate worth of data thru it. But instead of sending real time streams to the sound card like an MP3 player, I display "real-time" graphics for human interpretation of whats going on with the data. Since VNC was almost there with no "special knowledge" of windows, I really expected XP Remote Desktop to do the trick. Apparently the other application that sends me the raw data doesn't use some windows function that Remote Desktop relies on. My graphics ultimately call third party libraries that seem to work well with Remote Desktop.

As to the Matrox WDM crossbar driver in XP, I know nothing about it. It appeared as a "selection" when I was playing around with MovieMaker. The XP RC2 test machine happened to have my G200 Marvel in it. I hooked up the BOB and tried tuner and line in captures but got nothing and didn't persue it further.

--wally.

[hapz]

Getting back to my initial posting, does anybody know how to MANUALLY install the Matrox VidCap drivers so they work with AVI_IO, etc.?

E.g., which registry settings make Windows "see" that there is a video driver available.

[smanzo]

The usual method to make Windows "see" a new DLL is REGSVR32 {path\dllname}.

Similarly, you unregister a DLL via REGSVR32 /u {path\dllname}.

[hapz]

smanzo, it was worth trying but all I got was this error message, no matter which of the RRxxx.dll drivers I used:

"xxx.dll was loaded, but the DllRegisterServer entry point was not found"