Winsock Program without Admin Rights

[gr8gonzo]

I'm trying to construct a simple LAN chat application that does not need to be installed. The reason is that some people don't have rights to install programs or put anything into the system folders or anything like that. So what I want to do is create a program and then send the required DLLs and OCX files along with the executable.

Now, I'm using MS Winsock Control 6.0 (VB6 Pro) and I tried to send the program to a machine without rights, but I keep getting an error about invalid or missing files or components when it is trying to load MSWINSCK.OCX (if I remember correctly). Is there a way to find out what files I need to send with it to make the program work? The program is just the Standard EXE with the Winsock component added on. There is also a declare statement in a code module that calls a procedure for playing a WAV file and for flashing the title bar, but it appears they are being called from the user32 library, which seems to already exist.

- Jonathan

 

[randy4126]

you can use depends which is a toll that comes with vb 6 to find your dependency's hope that helps.
Randy

You can Email me at: RCooper@cinci.rr.com

 

[randy4126]

if you need to register the dll's you will have a problem without install rights Randy

You can Email me at: RCooper@cinci.rr.com

 

[dilettante]

How sophisticated does it need to be?

My question is, can you live with one-on-one chat or do you need many-to-many chat?

If many-to-many, can you live with hosting a chat server on one machine somewhere, with all the participants connecting their chat client to the server?

True many-to-many peer-to-peer is messy. Every time somebody sends a message they have to repeat it for every other client (if there are "n" chatters, you have to do "n-1" sends of each message). This isn't a big deal, even server-based chat normally does this unless it is multicast-based.

The problem is that each peer needs a way to find out about every other peer in the chat group. Plus a new chatter has to figure out what machine(s) to connect to in order to start chatting.

A "spider in the middle" chat-server approach is easier to build.

Also:

Do the users have known static IPs? DNS addresses (names) for their machines?

If not, how are they going to "find" each other without a chat-server?


I have an answer in mind for you, but it depends on answers to some of the questions above.