Could not start ocamlbrowser on Windows - ocaml

Problem: ocamlbrowser could not be started on Windows 8.
When I was installing ocaml on windows, it complained that the Tcl package could not be downloaded. I downloaded ActiveState ActiveTcl8.5.13 manually; however, ocamlbrowser still failed to start. I don't know if there's anything wrong with my installation, or configuration. In my point of view, ocamlbrowser is an useful tool, especially for beginner. Could someone help me to figure this out?
OS: Windows 8, 64-bit.
Ocaml: 4.00.1 (installed using official windows binary installer)
Tcl: ActiveTcl8.5.13 (installed after ocaml installation.)
Thanks!
Nick

You need to install a 32bit version of Active Tcl ("x86"), you installed 64bit while ocamlbrowser from that installer is linked against a 32bit one.
Try this dependency browser to see for yourself. http://www.dependencywalker.com/

Related

Should I install "mingw32-base" from the MinGW installation manager?

So I decided to install a c++ compiler for Windows and thus downloaded the MinGW installer. Once I opened it, I saw a number of packages and checked all the "C++ compiler" packages (am I using the right terminology here?) for installation. I also saw other stuff like "mingw32-base" and all. What does this do? Should I install it? Also, what is the difference between mingw and mingw32?
If you don't need additional packages you shouldn't install them.
But MinGW is a bit outdated. It's better to switch to MinGW-w64, which exists for both 32-bit and 64-bit Windows.
You can get MinGW-w64 either by installing MSYS2 and installing via its package manager (pacman), or - if you don't need the additional MSYS2 shell and just want to compiler tools - you can get a standalone package from https://winlibs.com/ and just unzip it.

I am trying to install MinGW but it's always failing to install

I am trying to install MinGW but it's always failing to install.
on windows 7
link of the program:
https://sourceforge.net/projects/mingw/files/latest/download
Tar zips are not generally for windows users the downlink should be a windows installer mingw-get-setup.EXE thus (not a GnuZip)
Also if your trying to unpack 32bit collections the question is which architecture do you need, certainly 32.exe will run on 64, but 64.exe will NOT work on 32.
Current build is 32bit "Although (currently) offering only a 32-bit compiler suite, all of MinGW's software will execute on the 64bit Windows platforms."
get it from official https://osdn.net/projects/mingw/releases/
latest link I got was
https://osdn.net/frs/redir.php?m=liquid&f=mingw%2F68260%2Fmingw-get-0.6.3-mingw32-pre-20170905-1-bin.zip
once you have a valid windows .zip file, right click to "extract" then the exe should be in the bin folder.
Then it's just you on your own, and the myriad of instructions from google.
MinGW is a compiler generating files for the Windows platform, but MinGW itself can also be run on other platforms (like Linux for example).
What you need is are Windows binaries of MinGW.
But MinGW is a bit outdated and only supports 32-bit Windows.
I would really recommend using MinGW-w64.
Standalone build of MinGW-w64 for Windows (both 32-bit and 64-bit) are available at https://winlibs.com/ just download the archive and extract it. Then all the tools you need will be in the mingw32/bin or mingw64/bin folder.
If you're not very familiar with command line tools you should really use an IDE. There are some instructions on https://winlibs.com/ on how to use MinGW-w64 with Code::Blocks.
If on the other hand you are very familiar with command line or the Linux shell you should take a look at MSYS2 which also allows installing MinGW-w64 with it's pacman tool.

pyinstaller 3.2 build pyqt4/python2.7 to onefile exe, can not run missing msvcr100.dll?

As title,
Build successful, but the exe can't run. can not found msvcr100.dll.
I can put msvcr100.dll with exe in the same dir, the exe can run.
But I just want only one exe file.
Anyone know how to do?
Has solved. This is a bug of pyinstaller3.2, the new in the git has solved this bug. Down the newest source in the github, erverything works fine.
Has solved. This is a bug of pyinstaller3.2, the new one in the git has solved this bug. Down the newest source in the GitHub, everything works fine.
This is correct, I cant tell you how much that answer helped me out. I have been trying to build a single exe Exploit to execute on Windows XP with-out it crashing for my OSCP Labs/Exam. I followed so many tutorials and nothing seems to work. I was able to build the EXE but could not get it to run under a single EXE.
If anyone who reads this is getting "This Program cannot be run in DOS mode" try running it from another machine with the same build (Windows XP). There is not much info out there on how to solve that from a Reverse Shell on a End Of Life Operating System using an EXE exploit built with Pyinstaller. (Lots of Trial and Error and determination)
Microsoft Visual C++ 2008 Redistributable Package (or some other version depending on python version) is needed in any case, python27.dll requires it
I was also receiving an error about msvcr100.dll when ran from the GUI on my build machine(WinXP SP2). This is corrected in the 3.3 Dev version on GitHub.
I installed the C++ 2008 Package but this didn't solve my problem when I re-built the EXE, the 3.3 Dev Pyinstaller was the solution.
What I did was:
Zip down the Dev version of Pyinstaller 3.3 Dev(GitHub) is the newest for 11/14/16 that I could tell. Make sure you have Python 2.7.x (I used 2.7.11) and pywin32 installed that matches (Python 2.7.x) version. (And it does matter if its 64-bit or 32-bit) Use the setup.py to install Pyinstaller, make sure you do not have a previous version already installed, if so use pip or etc. to remove. I installed with pip first and this was my whole issue.
I was able to get all of my 32-bit Single EXE Exploits to run on 64-bit/32-bit Windows machines up to Windows 10.
Once that is completed, make sure Pyinstaller is in your $PATH and follow the standard tutorials on creating a --onefile EXE. Copy to your Windows Target machine and it should work with-out error. I did not need to pull any dependencies over but you may have to include some with the --hidden command. Its greatly detailed in the Pyinstaller documentation on how to include hidden .dlls
If this still doesn't work for you try using py2exe. Its a little more complicated but it your determined you will figure it out.
If you have code written in python 2.x.x and 3.x.x you can have multiple environments of Python and have Pyinstaller installed in each. This is in the documentation as well.
Thank you jim ying. Your 2 sentence answer was exactly what I needed.

Howto install the latest CodeLite in openSUSE

Hi I've tried to install the latest codelite but when I try to open it, it doesn't. I followed the instructions on the site but no luck.
I'm using openSUSE 13.2 64-bit
You probably need to install the wxWidgets runtime libs, which were supposed to be included in the CodeLite package but weren't.
openSUSE don't seem to have a meta-package for these, and there are a confusing number of choices, most of which will be wrong for you. However if you ask yast to install libwx_gtk2u_webview-suse-3_0-0 I think you'll find that will depend on the rest of the correct libwx* family.
At the time of this writing, you can install codelite and wxwidget in opensuste in a straightforward method. Just go to the
opensuse software repository and search for codelite. After representation of the results press on the button
Direct Install
to let you install the package on your machine.

Trouble Installing PythonMagick Windows 7

I am trying to install PythonMagick. I am using Python 2.7 and running Windows 7. I have tried following the directions in the readme, but all of the configuration scripts are of type "file" and cannot be executed in either the python or windows command line. What should I do?
I recommend you use the pre-compiled installer from the Unofficial Windows Binaries for Python Extension Packages.
Just follow this link and download the right installer for your Python interpreter (in your case it will either be PythonMagick-0.9.10.win-amd64-py2.7.‌exe or PythonMagick-0.9.10.win32-py2.7.‌exe, depending on whether you've installed the 64 or 32 bit Python interpreter).