From: skaller <skaller@users.sourceforge.net>
To: Martin Chabr <martin_chabr@yahoo.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] File MSVCR71. DLL missing for 3.09.0 on Windows
Date: Tue, 19 Sep 2006 05:00:59 +1000 [thread overview]
Message-ID: <1158606059.15083.66.camel@rosella.wigram> (raw)
In-Reply-To: <20060918140346.21939.qmail@web27503.mail.ukl.yahoo.com>
On Mon, 2006-09-18 at 16:03 +0200, Martin Chabr wrote:
> Dear forum members,
>
> when I tried OCaml 3.09.0 (Microsoft-based version,
> the top-level interpreter) on Windows 98 and 2000, I
> got the following error message:
>
> "DLL file MSVCR71.DLL not found"
http://support.microsoft.com/?kbid=827073
http://www.dll-download.net/msvcr71.html
http://www.dll-files.com/dllindex/dll-files.shtml?msvcr71
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
prev parent reply other threads:[~2006-09-18 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 14:03 Martin Chabr
2006-09-18 19:00 ` skaller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1158606059.15083.66.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=martin_chabr@yahoo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).