[FireDAC][Phys][IBLite]-314. Cannot load vendor library [ibtogo64.dll] error - firedac

I am using a software from our vendor. The software works well on some machines, but get an error
[FireDAC][Phys][IBLite]-314. Cannot load vendor library [ibtogo64.dll]
on other machines. All of these machines have 64 bit Windows 10 Enterprise OS. And the ibtogo64.dll file is present in the same folder where the software exe file is located. I would really be grateful if someone could point me to right direction on how to resolve this issue.
Thank you.

Related

Openfiler installation problem with Dell R630 Server

We are trying to install a CentOS-based Openfiler distribution on Dell R630 server with PERC H330 mini RAID controller but unfortunately, the installation can't find a hard disk to install the OS.
Any ideas on how to solve that?
The Linux distribution doesn't contain the necessary driver packages. It might be possible to create an an device driver media, like an USB stick, which does contain the RPM installation packages. More information you will find in the Driver Installation section of the handbook.

DLL not found error using uFllex in Unity

I have bought, downloaded and then installed uFlex for Unity. The install seemed to go without any errors, but when I try to run any of the example scenes I get lots of errors. The first and most serious sounding of which is:
DllNotFoundException: flexRelease_x64
uFlex.FlexSolver.Start () (at Assets/uFlex/Scripts/Solver/FlexSolver.cs:102)
Also the scenes don't seem to run/work. Have tried googling to see if it's a common error but that didn't show up anything. Tried finding the missing DLL but not sure where to put it, or whether it's platform/version specific?
Any thoughts on how to troubleshoot this
Anyone else have similar issues?
Not sure if it's relevant but I'm running Unity Version 2017.2.ob11 Personal, and my OS is Ubuntu 16.04.5 LTS. I have windows installed as well - is switching to running Unity under Windows likely to help?
It won't and shouldn't work on Linux at this point.
Read the requirement from the plugin page:
NVidia GPU with at least CUDA 3.0 compute capability
Windows 64 bit (Win 32bit experimental, Android and Linux support planned)
The support is currently for Windows. You get the exception because the dll for Linux has not been provided. It can't load Windows dll on Linux. If the native side (C++) of the plugin is open-source, you can compile it for Linux and include it in your project then it should work. Since it's not, your only option at this moment is to switch to Windows.

Found the NXT device but can not upload a program to NXT

I'm using Ubuntu 14.04 (64 bit). After installing leJOS_NXJ_0.9.1beta-3, I was able to flash the NXT device. However, when I tried to upload a program, it showed a message "Found NXT: NXT 0016530CDF15" and then just stuck there.
I also tried Eclipse with leJOS plugin, and got the same problem. It showed
Program has been linked successfully
Uploading ...
Found NXT: NXT 0016530CDF15
and it got stucked there.
Can anybody help me with this issue?
Thanks,
Thuy
This site might be able to help, it provides the information to install and configure correctly all the software necessary for you to develop Java programs for the NXT, maybe by following this site it will hopefully fix the problem.
This tutorial will show you how to install and configure all the software necessary for you to develop Java programs for the LEGO Mindstorms NXT. Java is much more powerful and flexible than the original NXT-G software that LEGO provides. We will be using the Eclipse editor to write the actual Java code and to download this into the NXT. This combination enables you to conveniently write software and to quickly test it on the NXT. Of course there are many other Java editors, but we consider this combination to be particularly convenient. This tutorial focuses on the Windows XP platform, A Mac OS X tutorial is also available. We have two additional steps for Windows Vista. You will work through the following five steps - See more at: http://www.bartneck.de/2008/03/04/java-lego-nxt-eclipse-tutorial/#sthash.h1ZOZvlX.dpuf

How to update from a original XP no service pack to XP3 with no internet

First off I used to be an XP guy and I still have the copy that I bought back in 2002. I had to downgrade my computer to an old iMac I had in storage and the only copy that I have of XP (I really do not want to buy a new one) is the old copy. I installed into a fully formatted drive and then realised that this XP disc came out before service pack 1. Which means that there really is no support for this. Next I noticed that the ethernet driver is unrecognized (big shock) therefore I have no internet, so I cannot install using windows update. Therefore I do not have any updates (again this disc is very old) and no access to the internet.
I have another computer that I can burn discs off of and it has the internet but I will not have it for much longer.
The device I installed the XP on is an 20-inch iMac (Early 2006), 2.0 GHz Intel(R) CPU T2500 with 1.98GB RAM
Is it possible to update my machine and be able to do use it the way it should be?
How I managed it was that I downloaded found an executable version of SP1a and then updated the system by moving the file over, then I downloaded the service pack SP3 ISO, updated the system.
However it didn't fix the ethernet driver and since I had no idea what the controller's actual name nor the company that made it, I moved over the Auslogics System Information, did a diagnostics took the problem devices "Value" and did research in order to find the needed information, and got the driver and moved it over. Yay monotony.

Deploy files on a network share from a client machine using an installation package?

We have a large application that has been developed over 15 years and in installed in 200+ client locations. The application currently consists of an Access database and a bunch of executable and report files located on a network share. A Setup.EXE file is run on each client machine (dlls are installed on the client) and then the client machines run the executables directly from the network share. During our upgrade procedure the new executable and report files are copied to the network share and that way each client gets the update immediately.
Our current installation program is very old and, among other things, it doesn't handle x64 so we are in the process of moving to a new deployment tool. At the same time we are migrating client Access databases to SQL Server. I am having difficulty finding a deployment tool to do what we require. Specifically we need the install/upgrade file to do the following:
It must be able to be run from a client machine on a network and copy the new executable and report files to the network share. That share could be a Linux box or a dumb storage device.
Accept a password before running the installation
Allow the user to select the network share as the location to copy the executables
It must NOT add anything to the client machine from where the package is run (Add/Remove Programs, registry, etc.)
Connect to a SQL Server database and run a script
The install/upgrade must be contained in a single, standalone .msi or .exe file. (no dependencies on dlls or frameworks other than those that come with Windows XP)
The file must be able to be run in one simple step. It is the end user that runs the upgrade without our support and without involvement from IT.
It looks like the closest thing to what I need is WiX but the problem there is that whenever the .msi file is run from a client, the client machine thinks that a program is being installed so it allows the client machine to uninstall the product, which is not acceptable.
If the product were written today it would certainly be architected differently but it currently is what it is and we can’t change that. Any help here would be greatly appreciated!
WiX is just a toolset built on top of Windows Installer technology. It makes many things easier and simpler as well as hides lots of Windows Installer weird features... But, it is still limited by Windows Installer, its underlying technology.
Your list of requirements made me think that Windows Installer is not the right technology to choose. I would assume that you'll spend more time on workarounds, than on functional code... But I have no experience with other installation technologies, so I'll leave those recommendations to others.