Thankyou for your reply.
Unfortunately, due to the delay in responding( over 6 weeks), i have managed to rectify the issue by paying an expert who spent 6 hours trying to and eventually getting it partially operational.
Utube was more helpful then Microsoft.
I founnd that this is a common issue that Microsoft has been aware of for several years.
The solution involved a change in the operating system. The USB index had to be manually alted to accept the device.
A simple change once i was aware how but, for people like me who are not computer savy, a frustrating and difficult concept to understand.
A simple piece of code could have been written years ago when this issue was first observed.
Pitty that a Microsoft product isn't made compatible to another Microsoft product or that a simlpe fix is ignored to the detriment of loyal customers.