Everything was going fine. Assembly went good, downloaded the LynxTerm v1.08 software, installed it, did some moves with the software on the robot,… all went fine.
Until I tried to install the ‘RIOS for SSC-32’ -software that was delivered with the kit on a CD-rom.
I always get the same error message during installation:
Error 1305.Error reading from file D:\Common\Borland\Shared\BDE\bantam.dll
I checked the content of the mentioned file and the the dll is present there.
Can somebody please help.
I’ve checked the forum for similar tags but none of them mentions this problem. Does somebody have the same problem?
i think the CD may be corrupted, could you try to manually copy the file Bantam.dll from the CD to any place on your HD ?
If you can’t and get an error message it means the CD is corrupted.
Maybe you can try to clean the CD first or use another CD drive to test.
If you still can’t read this file, you should ask another CD from Lynxmotion. In this case please take care of your current Serial Number written on the CD paper sleeve as the new CD will not contain any Serial number
I recently bought a AL5D complete kit with RIOS 1.06 CD in it. The robot is working fine with ltrm111. When I tried to install RIOS, I got a similiar error from one of the previous post. VeroResearch had 1305, but mine is 1309.
Error 1309.Error reading from file D:\Common\Borland\Shared\BDE\bantam.dll
Verify that the file exists and that you can access it
I tried to ignore it, but the next dll file had the same problem. Actually, it does not read any of the files in the BDE folder. I tried to copy the CD ROM into my local hard drive and the installation still failed the same way. I even tried different PCs with windows XP, Win 7 (64-bit). They all failed the same. I changed the BDE folder security to allow full control for everyone/user, but same error. So, I don’t know what to do now. Please Help.
BTW, there was another error saying
Error 1155. File D:\Lynxmotion RIOS SSC-32.msi not found
The file name was originally Lynxmo~1 on the CD ROM. Windows does that for long file names, so I fixed the problem by copying the CD ROM into local drive and change it back to full name. That error is gone. But then I start getting the 1309 errors. I wonder if there is any co-relation.
I think I found the problem… I post it anyway if anyone has the same issue. The files that comes with the CD ROM are shorter versions of the file names (same as folder names). We need to copy the CD ROM into local drive and run setup there. Then we just need to change the folder or file names to their full name whenever an error msg pops up that complains the file names or path names. This should work ^^
Strange. We had this problem quite a while ago. It was fixed, but it seems another broken CD snuck out. When did you purchase it? I’ve checked most of the other CDs in the building, but I can’t find any others with this problem.
