Re: [GD-General] Missing DLL: MSVCP70.DLL

[Colin F. <cp...@ea...>]

Okay, I did more Google searching and I have come
to the following conclusions:

(1) Under Windows 98 you can simply copy the
    following two files:

      (a) MSVCR70.DLL   (336 KB)
      (b) MSVCP70.DLL   (476 KB)

    to the following directory:

       C:\windows\system

    and the problem should be solved.

    NOTE:  There are a few other DLLs
    that might be required for MFC:

      (c) MFC70.DLL
      (d) MFC70U.DLL

    (I do not have these files installed 
     under Windows 98, and my non-MFC app
     compiled under MSVC7.0 works fine.)

    and I noticed the following mystery-DLL
    on my WIndows 98 machine, but apparently
    this file is not required for my particular
    application:

       (e) MSVCI70.DLL  (54 KB)



(2) Under Windows 2000, files (a) and (b) can be
    placed in the folowing location:

           c:\winnt\system32

    (NOTE: "system32", not "system" as with Win 98.)



(3) Apparently, an alternative to "installing" the DLLs
    in the offcial locations is simply putting the DLLs
    in the directory containing your application.
    Thus, you know exactly what DLL version you are
    getting.  There is no DLL slamming going on.
    The disadvantages include:

        * Redundancy : DLL may exist on the system
        * Missing upgrades and bug fixes in official DLL        


(4) Lots of developers instruct users to download
    these DLLs from their web sites to use their
    applications.

    I'm not saying this make is "right" to ask users
    to download (potentially old, potentially hacked,
    potentially virus-invested) DLLs from one's web
    site.  Even if developers directed users to the
    Microsoft web site to download these DLLs, I'm
    not sure it would be the "right" thing to do --
    especially if Microsoft required visitors to 
    get a Microsoft Passport to download those DLLs!
    (Let us hope that we won't one day need Microsoft
     Passports to literally travel.  "You papers, please!")


Anyhow, I am still interested in knowing the two things
mentioned in my previous post:

(A) Can I compile with MSVC7.0 and yet only require 
     users to have MSVC6.0 DLLs?

    If this is insane (lots of settings changes, etc)
    then I will just give up on the idea.

(B) What is the best way to make one's application work
    on systems that may not have the required DLLs?

    * Ship local version in application directory?
    * Direct user to a Microsoft link?
    * Do your own detection of whether or not the DLL is 
        present in the system directory, and then ask the
        user if he or she wants to install if the DLL is
        NOT already present?

Okay, I'm sure all of these questions expose me as an
amateur novice nOOb Hax0r wannabe hopeful grasshopper.
When will I B 1337 ?!  ROTFL! LOL!  ::^)   

--- Colin