I downloaded from official site and installed latest version of Gammu for windows.
The set-up runs just fine like any other exe I have ever installed.
Then, when I try to call the command as instructed in the official guide I get this message: (alternative)
I've tried anything but it's always the same.
All of the other similar "win32 not a valid application" questions are related to self-made applications or programming in general: I haven't found a similar problem related to gammu in the whole web, except for a very old case from seven years ago which suggest to downgrade, which of course I can't do.
any suggestion to this problem? anyone had a similar one
Okay, there seems to be problem with running apps built with recent Visual studio on Windows XP and 2003.
Fortunately there is a configuration to change this.
I've just committed this change to Gammu and the new binaries will soon build. They should be available for download here. It would be great if you can test them...
Related
I am attempting to install the Arelle XBRL software and these are the steps I am following.
Download the Windows 64 bit version from http://arelle.org/pub/applications/
Double click on installer
As soon as I click the installer I get an NSIS Error message depicted below.
What I have tried:
E-mailing the Arelle support dept but they don't seem to answer at all
Searched for a solution
The most common solution I have found was to run the installer from the command prompt with the below syntax. This seems to have worked for many people but I am still getting the exact same error.
"C:\Users\MyPc\Desktop\arelle-win-x64-2019-07-24.exe" /NCRC
This problem has existed for weeks and it doesn't make sense as Arelle is a widely used program for use with XBRL and many people have downloaded it.
Disk checks and various error checks are being done frequently by the company's administrator so computer maintenance is always occurring.
Any ideas?
I've had the same issue, I've downloaded installer from another computer and another net, run it on computer where was issue, and it works.
Oracle form downloaded at:
http://www.oracle.com/technetwork/developer-tools/forms/downloads/index.html
When I ran the file setup_fmw_12.2.1.3.0_fr_win64.exe,
it gave me an error "Cannot launch the installer (555)".
fmw_12.2.1.3.0_fr_win64_Disk1_2of2 <-- Folder
setup_fmw_12.2.1.3.0_fr_win64-2.zip
fmw_12.2.1.3.0_fr_win64_Disk1_1of2 <-- Folder
setup_fmw_12.2.1.3.0_fr_win64.exe
Even though this relates to the installation of a developer tool, most would consider this particular type of question as generally off topic for stackoverflow. Your question also contains too little information to determine what the problem really is.
However, let's just mention some obvious things to see if it helps you solve your own problem:
Did you try the setup on another computer (or a virtual machine). This could be a good way to avoid the whole problem rather than spending a lot of time trying to fix it.
Did you locate any log files for the failed install?
A quick look seems to indicate that you can find log files at: %SystemDrive%\Program Files\Oracle\Inventory\logs (%SystemDrive% is normally C:\).
Or %SystemDrive%\Program Files (x86)\Oracle\Inventory\logs for 32bit installers on 64 bit systems).
Found in the troubleshoot section here - have a look yourself too - read from the top.
And the most obvious of all: did you contact Oracle support or search their user community or knowledge bases? Somebody will have seen this problem before. Looks like you need to register: https://support.oracle.com/
A quick search reveals that the Oracle Universal Installer is a Java based installer. Could Java be broken on the box you install on? (looks like the launcher should install the runtime automatically, but this could fail due to special conditions on the box. Try on a clean virtual machine). How to check whether java is installed on the computer.
Try disabling your anti-virus as well before running the setup on the problem box. Some setups even try to access the Internet during installation, and then your firewall could be a problem too. I would hate to turn that off though.
I know, there are countless threads about this control already and I've been reading them for hours. I can't add get this ocx to load into VB6, running 64 bit Win 7.
Things I have already tried:
1. unregistering and re-registering (used regsvr32 from syswow64)
2. Did the regtlib msdatsrc.tlb thing I've found
3. Reinstalled sp6
4. Installed the cumulative update everyone is saying is the latest version
I haven't reinstalled VB6, I don't have the media at work or I would have, but this has shown to never be the solution to this problem on the successful fixes I've read about these past few days I've been working on this.
Things to note that people aren't talking about in the other threads: I can add the ocx to Office without issue, then add controls (treeview, imagelist, etc) and use them fine. I can't add the OCX to a new, empty VB6 project. Most users are trying to open existing project, which fails for me as well, but never say whether they can add the OCX to a new project. I can't.
I hate to create another one of these threads to further muddy the water, but the solutions in other threads haven't been working for me and no one is mentioning where they can add it to Office or a new project.
This used to work fine months ago, too many things have happened since then to be able to pinpoint one that may have caused this. My main focus is to be able to add it to a new project again.
Thanks.
EDIT:
VB is being run in elevated XP SP3 compatibility mode.
Found the solution. I don't know how it came to be, but I had 3 different versions registered in my registry. Maybe the version that was trying to be used by VB wasn't compatible but was compatible with Office? I don't know.
Here's what I did.
I opened up the registry (regedit.exe) and searched for the key 831FDD16-0C5C-11D2-A9FC-0000F8754DA1 and found the three different versions were listed. I made a backup of the sections I was going to change, of course, and then just deleted all of the version entries. After that, I went back and registered what I had in my syswow64 directory and now it's back to normal. Rechecking the registry shows I now only have version 2.2 installed.
I built a Lazarus program and it's now in exe form.
I am able to run it on two of my computers running XP and Vista.
However, there are other computers as well running XP, Vista and Win7 but I cannot get it to run at all on them.
There are no errors, nothing... Has anyone else had this issue?
The program is connecting to a postgres DB on my LAN server.
Any idea on fixing this is really valued.
NEW INFO:
Maybe I'm wrong but here's a thought... On the development machine, I initially got an error like **libpq.dll* not found when I first tried to connect to postgres. Then after setting the path, it was fine. I'm thinking now if it cannot find that library and that's why it's not able to run.
If this is the case, should my line Application.OnException:=#CatchErr; catch the error? If not how else should I check if this dll or anything else is missing?
First, a sincere and big THANK YOU to Marco and MArtyn for the great tips and guidelines hat got me thinking of this strange issue.
Here's what happened...
I installed a fresh copy of Windows 7 and XP. As usual it did not work.
Then I suspected the old problem of libpq and then I copied libpq.dll from my working OS and put it in the application folder. By the way this machine has no Lazarus or Postgres. The moment I did this, I got my first error message saying that msvcr100.dll was missing.
And then I copied that as well. So the cycle of copy pasting went on for each and every error until I had finally brought these files to my 'non-working'.
libpq.dll - 9.2.1.12263 - PosgreSQL Access Library
msvcr100.dll - 10.0.40219.1 - Microsoft C Runtime Library
ssleay32.dll - 1.0.1.2 - OpenSSL Shared Library
libeay32.dll - 1.0.1.2 OpenSSL Shared Library
libintl.dll - 0.18.1.0 - LGPLed libintl for Windows NT/2000/XP/Vista/7
Once these files came in, the problem was gone!
Now the program works great :)
Thanks for all your inputs!
I now have to see what the above files have to say about their licenses as I have to distribute the app to other users. But I'm glad at least we figured out the problem.
No, base Lazarus programs don't require special permissions. Of course it could be that a specific functionality in the program requires special permissions (like access to ports below 1024, access to certain paths etc).
Also be aware that EXE's downloaded from what the system considers insecure sources (internet, certain kinds of shares) might be blocked by default. If that is the case, if you take the properties of the .EXE in windows explorer, there will be an "unblock" button.
Anything network related of course requires proper configuration of the firewall. The popups that query you might not always come, in case of doubt configure the firewall manually.
I got a weird problem with my VB app that has got me very confused. I am updating an existing program. I had to add some processing queue capabilities. On my system, unit testing worked great but when I compile it and run it on a different computer (a network server machine) it first tries to open an office install. If I cancel this, the program seems to run fine. The problem is that this program will be run in the background and I can't be hitting cancel each time it runs.
So my question is this: what is going on here? I'm usually a java developer we eclipse so I'm used to being able to include all the needed libs into the jar files automatically. It doesn't seem like the case with VB6. it seems like it expects all the same libs to be on all the systems. Is there any way to tell what might be triggering this?
The only thing I can think of that is causing it is that I'm using the "OpenProcess" function in the kernal32 lib. that the only major change I have made.
any help would be very appricated. thanks!
EDIT:
It seems that multiple versions of word were installed on the system and it was screwing things up somehow. We uninstalled one and it fixed it.
I ran into this a while ago and it was related to my installer for the VB6 app overwriting some system files for Office that it shouldn't have. Any time one of the System dlls was accessed Windows would determine that something was wrong and the Office installer would start up.
The short-term fix was to let the Office Installer repair the broken chain of dlls.
The long-term fix was to never overwrite built-in Windows System dlls.
You could also check out the Microsoft Fix it Center.