Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: ralph Newsgroups: comp.lang.basic.visual.misc Subject: Re: 64 bit Windows install difficulty Date: Mon, 19 Mar 2012 20:42:05 -0500 Organization: Aioe.org NNTP Server Lines: 34 Message-ID: References: <31017545.1291.1332096428383.JavaMail.geo-discussion-forums@vbbfy7> <18433174.4307.1332144455764.JavaMail.geo-discussion-forums@ynlt15> <26795801.2392.1332162041006.JavaMail.geo-discussion-forums@vbkc1> <14127446.381.1332176755304.JavaMail.geo-discussion-forums@vbbp15> <18949830.2160.1332197425379.JavaMail.geo-discussion-forums@vbux23> NNTP-Posting-Host: QPUqO38R4VH3RL6SKQdX5g.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Forte Agent 6.00/32.1186 Xref: csiph.com comp.lang.basic.visual.misc:1002 On Mon, 19 Mar 2012 15:50:25 -0700 (PDT), peter.lawton@blueyonder.co.uk wrote: > >I do have two users reporting install failure on 64 bit machines, and >with the same error message, referring to msvbvm50.dll. Something's going on.... > >Your experiment on your wife's computer - where was the VB5 >application residing? Was it in Program files (x86)? > The search rules for the Windows Launcher to find a dependent shared DLL (Win32 DLL, Regular DLL, ...) for a given executable are as follows: 1) the file specified by a fullpathname 2) the folder the executable is launched from 3) the current directory 4) the current 'System' folder (c:\windows\system32\ or \SysWoW64\) 5) the 'Windows' folder (c:\Windows, ... c:\WinNT) 6) folders contained in the Path environmental variable (in order, left to right) It worked on Mike's wife's computer because of Rule 2 or 3. The Launcher attempts to resolve all dependencies before any code after the entry point in the executable is called. Therefore the DLL must be in one of those search locations before the executable is launched. -ralph