NetMeeting Forum

I've continued to work on this. By using the function of having Netmeeting log on to a directory, I can successfully connect to others as long as they are logged on to the directory that I'm logged onto. They can then share their screen with me. I am still unable to share my screen with them.

Do you mean you can connect to an ils-server? I haven't been able yet to do this. Can you explain me how you did this please? Have you used some special settings. Thanks in advance Robbert.o

Mark,

I'm in the same boat you are, Netmeeting at work for all cross-site meetings and no way to view other's/share my desktop under Linux.

I have not purchased CrossOver yet. I'm interested to hear if you have upgraded to 3.0.0 yet and if so are you still unable to share your desktop?

Thanks,

Russ

You cannot share your desktop nor can you see a shared desktop with 3.0.0 of Crossover and Netmeeting 3.01.

I am experiencing no problems connecting to ils-servers. It is only connecting to the other users and sharing your desktop that causes problems. :)

Cameron,

In the first post of this thread, Mark says that he can view others' shared desktops, but he can not share his desktop wiith others.

He made that post before Crossover 3.0.0 came out. Are you saying that with the new 3.0.0 release the ability to see others' shared desktops has been removed?

Thanks,

Russ

Removed, no. Broken, yes. At least that is my experience. Netmeeting is one of those funny applications that seems to be used a great deal in certain businesses but M$ is trying to get people off of it. Kinda like M$ Java. I would love to tell Codeweavers don't support the M$ JVM but then I wouln't be able to fill out an expense report.

In 2.1.0 Netmeeting worked most of the time. In 3.0.0 Netmeeting seems more stable but isn't working if viewing a shared desktop is important. I suspect Netmeeting will get better over time.

I would recommend anyone that wants Netmeeting to work, start voting and pledging money. I have submitted a pledge but it hasn't show up yet.

I already pledged. I'm not running Netmeeting with crossover yet, only with wine. The only functions i've been able to get working are chatting and file transfer, haven't tried desktop sharing yet. My question is about the video function, is anyone able to receive video? Somehow, I have the feeling that this shouldn't be a very difficicult problem to fix , but i haven't been able to get this running. Does it work in cross-over? Robbert

Cameron,

I just promoted myself from "Anonymous Coward" to Russ Radke. ;^)

I have installed CrossOver 3.0.0, followed by IE6 and Netmeeting 3.0.1. The only strangeness during the install was from IE6 complaining that the installation of "dcom95.exe failed. It installed after that and runs somewhat (un)stably. It crashes after 0-5 links being followed.

Netmeeting doesn't come up. As you mentioned elsewhere, it does not create a menu entry or a startup script in ~/cxoffice/bin. So I launched it manually with "~/cxoffice/bin/wine -cx-app conf.exe" (I also later tried cb32.exe and wb32.exe). It came up and took me all of the way through setup (farther than I ever got with stock wine), but then it tried to bring up the default Netmeeting window and, after creation of an X window with the correct title, crashed dumping several 100 lines of wine debug info to the screen.

I guess this is surprising, but the fact that IE6 doesn't work well is very surprising as it is a "supported" app. I am thinking that I have a Crossover configuration problem, so I guess I'm going to approach CodeWeavers with "IE6 doesn't work", and after that is solved try Netmeeting again.

Can you please reply with your system info and command line for launching Netmeeting? And you too Mark, if you're reading this. I'll greatly appreciate all help tossed my way...

I'm on a P4 2.2GHz running RedHat 9 (2.4.20-18.9).

Thanks,

Russ

Can you post the last lines of the debug info here? I guess it shouldn't be very hard to solve this problem. Greetings Robbert

You should be running DCOM98 not DCOM95. I would move your cxoffice directory and reinstall. Start by installing IE before anything else that will download and install DCOM, IE and some other stuff.

I've gone to CrossOver 3.0.1, and removed my previous install files.

I tried manually installing dcom98, but it fails saying that a newer version of dcom98 or dcom95 is already installed. I even tried forcing recognition of a win98 OS and it failed the same way.

So I started fresh again and installed dcom95 from the "supported applications" list in the installer. It worked fine. Then I installed IE6, which also worked fine. Now IE6 works reliably without crashing. At this point I've got IE6SP1, Outlook Express 6, dcom95, and Media Player 6.4 installed.

So I now do a "Install unsupported software" install of NM30.EXE (NetMeeting 3.01). It installs perfectly. I then copy the startup script for IE6 over to "netmeeting" and change the path to point to conf.exe. Upon launching, I go through all the configuration, and then it tries to launch the application. I see the startup splash-screen, then main window (NetMeeting- Not In A Call) and the little sub-window that has the globe in it, but then the WineDbg dump starts and it crashes.

Here are the pertinent-looking parts of the dump (I'm not fluent in WineDbg):

[russr@freki ~]# netmeeting
wine: Unhandled exception (thread 000e), starting debugger...
WineDbg starting on pid a
No debug information in ELF '/home/russr/.cxoffice_bin/bin/wine-pthread' ((nil))
Breakpoint 1 at 0x4000cf70 (_end+0x37fc2dd8)
No debug information in ELF '/home/russr/.cxoffice_bin/lib/libwine.so.1' (0x40017000)
...
Unhandled exception: unimplemented function ws2_32.dll.WSALookupServiceBeginW called in 32-bit code (0x409a4056).
In 32-bit mode.
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:003b GS:0033
...
Stack dump:
0x41ba8980: 409b580c 736e414c 80000100 00000001
...
Backtrace:
=>0 0x409a4056 (WS2_32.DLL..text+0x3056 in WS2_32.DLL) (ebp=41ba89d8)
1 0x409a41c4 (WS2_32.DLL.WSALookupServiceEnd in WS2_32.DLL) (ebp=41ba89e8)
2 0x7795c630 (WLDAP32.DLL.ldap_get_dnW+0x3d2 in WLDAP32.DLL) (ebp=41ba8a34)
...
*** Invalid address 0x56e58955

0x409a4056: jmp 0x409a4050
Modules:
Address Module Name
0x00400000-004a6200 (PE) C:\Program Files\NetMeeting\conf.exe
0x10000000-10009600 (PE) C:\WINDOWS\SYSTEM\SECUR32.DLL
...
Threads:
process tid prio
0000000a (D) C:\Program Files\NetMeeting\conf.exe
0000000e 0

Well, I guess the problem is in the unhandled exception ws2_32.WSALookupServiceBeginW etc. Appearently it calls an unimplemented function. I had a similar problem, so maybe you can try this: reinstall Netmeeting, and in the configuration of Netmeeting be sure to uncheck the option "log on to an ils-server when Netmeeting starts". If you would like to log on to an ils-server afterwards, as the program has started, provide the IP-number of the server instead of it's name (you van find the IP-numbers of the servers somewhere on the internet) ; Can you try this ? and let me know Bye

That fixed it. I can now bring the tool up, but when I then connect to my ILS server using the ip address, I can join a call, but can not see the desktop that is being shared by others in the call.

This is what Cameron reported back on 6-11, that desktop viewing used to work in CrossOver 2.1, but is now broken in 3.0.0.

I'm going to go back to CrossOver 2.1 and try it there. Stay tuned...

I've now installed and configured Netmeeting under Crossover 2.1.0 identically to how I did under Crossover 3.0.1. Under Crossover 2.1.0 I can now see the shared desktops of other users. So I am seeing exactly what Cameron saw earlier, that viewing of others' desktops was working in 2.1.0 and is now broken in 3.0.1.

I voted for and pledged the purchase price of my copy of Crossover to Netmeeting, which is entirely fair because the only reason I bought it is to run Netmeeting. Hopefully it will help this app get some attention...

BTW. I forgot to mention that it was DCOM95. I was mistaken when I said DCOM98 I meant DCOM95 the second version.