Slow image data transfer

You sound like you have tried all of the normal fixes.

Try a new PC and see what happens. Try a PCMCIA network adapter. Maybe the onboard is off kilter.

Are you using the new version of software from their website? That loads so much quicker for me.

Also, is there anything running in the system tray? I've had instances where norton anti-virus was slugging my machine down to a crawl.

My normal ethernet port when connected to my home network runs at 100mbs. I disconnected my home network, plugged in finishlynx to that port, reconfigured the IP and it now runs at 10mbs. All Firewalls are disabled and nothing is running in the system tray.

Launched Finishlynx, system found camera right away then loaded camera run time module 2x. 1st time took 1min 2nd time over 9min, then message "error booting camera base IP address may be bad". Yesterday it took this long but the camera booted up and functioned, albeit with a very slow transfer rate. In fact, when Finishlynx software is running it slows down the entire computer. I am using lynx version 5.20-e.

The Lynx 5L100 & 5L200 (green cameras) have a 10mbs nic card. However the 5L300 has a 10/100card. No matter what camera you run if you're using a 100mbs hub the Hub will output in 100mbs to the computer provided your computers nic card is 100mbs. However, the Data between the Lynx camera and hub will only be 10mbs if using a 5L100 or 5L200

Do you have the ability to go on another machine? What happens if you try it on another computer? Then we can determine where the issue may lie.

Another thing I would try is a cross-over cable between just the Camera and Computer.

The base IP could be a variety of things I was told by Lynx.

There is a file called Lynx.cfg in C:\Lynx which if deleted blows away the settings. This is a good thing because if it's corrupted Lynx won't use that file it will just create a new one. Delete the Lynx.cfg file

Just a few more things to try.

I was getting the same "error booting camera base IP address may be bad" message. I was able to resolve it by disabling all my wireless connections in Network Connections.