Usb to Serial COMM Adapter (part no. 42855) Unable to install Win 7

Anything that doesn't fit in the below or just general help
10 posts Page 1 of 1
Copthall
New member
Posts: 6
Joined: Mon Sep 09, 2013 9:06 am
by Copthall » Mon Sep 09, 2013 9:53 am
I tihnk the title says it all. I am trying to install the USB to serial COMM adapter but the driver fails to install. (Windows 7) I tried downloading from your site (lindy.co.uk/drivers_and_manuals/search/42855) but the link is just 2 zipped .cab files. Is there another link?
Last edited by Copthall on Mon Sep 09, 2013 9:53 am, edited 1 time in total.

 

LINDY Shippers
LINDY Staff
Posts: 655
Joined: Wed Mar 17, 2010 1:32 pm
 
by LINDY Shippers » Mon Sep 09, 2013 10:10 am
Hi

The following file should work fine - http://www.lindy.co.uk/downloads/42855.win8.zip

Chris

 

Copthall
New member
Posts: 6
Joined: Mon Sep 09, 2013 9:06 am
by Copthall » Mon Sep 09, 2013 1:19 pm
Nope, didn't help at all. Still not correctly installed (yellow exclamation) No communication through the device, it's not even registering as a Port device now.

 

LINDY Shippers
LINDY Staff
Posts: 655
Joined: Wed Mar 17, 2010 1:32 pm
 
by LINDY Shippers » Mon Sep 09, 2013 1:36 pm
These drivers are WHQL certified so it must be something in the OS that is either corrupt or the device has a problem.

Is it a new device or has it been working before?

It might be worth starting fresh by removing the device driver (right click, remove , delete in device manager)

Chris

 

Copthall
New member
Posts: 6
Joined: Mon Sep 09, 2013 9:06 am
by Copthall » Mon Sep 09, 2013 4:07 pm
We've recently upgraded our network from XP to Win7. All 10+ of these devices we have worked before, now none of them do. I have already tried removing the driver and removing the device from Device Manager (and lots of restarts in between), installing it in multiple USB ports (and PC's)

Every occasion it just gives a yellow exclamation mark and we are unable to make a connection through it. Trying to update the driver automatically gives the response that the driver is signed and installed correctly.
Last edited by Copthall on Mon Sep 09, 2013 4:09 pm, edited 1 time in total.

 

LINDY Shippers
LINDY Staff
Posts: 655
Joined: Wed Mar 17, 2010 1:32 pm
 
by LINDY Shippers » Mon Sep 09, 2013 4:12 pm
When moving from XP to windows 7 was the machine also changed?

Do you have any serial device attached when trying to install the driver?

 

Copthall
New member
Posts: 6
Joined: Mon Sep 09, 2013 9:06 am
by Copthall » Mon Sep 09, 2013 4:15 pm
Attached is a ss of the Device Manager, Device Properties and the result of the last attempt to update the driver.

 

Copthall
New member
Posts: 6
Joined: Mon Sep 09, 2013 9:06 am
by Copthall » Tue Sep 10, 2013 10:40 am
When moving from XP to windows 7 was the machine also changed?

Do you have any serial device attached when trying to install the driver?

On the whole we kept the same PC's as before. I have always installed the device unconnected, will try connected.

 

LINDY Shippers
LINDY Staff
Posts: 655
Joined: Wed Mar 17, 2010 1:32 pm
 
by LINDY Shippers » Tue Sep 10, 2013 11:08 am
Could you run the chip checker program in the downloaded driver?

You can also get the latest package here - http://www.prolific.com.tw/US/ShowProdu ... 25&pcid=41

Chris

 

Copthall
New member
Posts: 6
Joined: Mon Sep 09, 2013 9:06 am
by Copthall » Tue Sep 10, 2013 1:56 pm
Don't worry, managed to get it working again with your old unsigned 2000_ME_XP driver package.
10 posts Page 1 of 1