Solved

Windows 8 MSVCR71.dll

Posted on 2013-10-30
8
2,821 Views
Last Modified: 2014-08-07
Windows 8 fails to load the exe with a message indicating that the MSVCR71 cannot be loaded even though it is in the application folder.

The run-time files were created on a Windows 7 system.

Do I need a different version of MSCVR71.dll for Windows 8.
0
Comment
Question by:TomPreen
  • 5
  • 2
8 Comments
 
LVL 53

Expert Comment

by:McKnife
ID: 39612994
And the dll is supposed to be found out of the box? Was it registered using regsvr32.exe?
0
 

Author Comment

by:TomPreen
ID: 39613499
It was included with the runtime files and the user did not report any errors when running setup.

However this dll must reside in the same folder as the application exe http://support.microsoft.com/kb/326922

Initially this was not the case as the application and associated files were supplied as separate entities.

The user is upgrading from XP to Windows 8 and this setup procedure worked without problem.
0
 
LVL 53

Expert Comment

by:McKnife
ID: 39613514
Trying to help, I asked questions. Please answer those.
Did you register it?
Is it supposed to work like this, or are those separate entities not supposed to work together/no one can confirm they should?
0
 

Author Comment

by:TomPreen
ID: 39613577
Windows setup handles any registration of DLL's that is required.

Specific registration of DLL's is never required.

VFP9 provides Installshield as an application which creates the necessary installation Windows
Setup exe.

Do you have experience of installation of VFP applications or do I need to add tags to ensure my question is picked up by someone that does.
0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 
LVL 53

Expert Comment

by:McKnife
ID: 39613617
No VFP experience, sorry. Just asked because your setup was not quite clear - most important, we still don't know if it is supposed to work this way, so if others are able to use it on win8.
0
 
LVL 53

Accepted Solution

by:
McKnife earned 500 total points
ID: 39877722
Please respond or finalize it, this question is growing old :)
0
 
LVL 53

Expert Comment

by:McKnife
ID: 40105269
You can always select your own comment/solution.
0
 
LVL 29

Expert Comment

by:Olaf Doschke
ID: 40246321
1: >Specific registration of DLL's is never required.

2: >VFP9 provides Installshield as an application which creates the necessary installation Windows
Setup exe.

Statement 2 is true, but statement 1 not, installshield generated setups don't automatically register DLLs needing registration, you can configure Installshield for automatic COM detection in DLLs and OCXes, but you should rather manually set DLLs for registration. Anyway MSVCR71.DLL is one of the DLLs you don't need to register at all (see http://fox.wikis.com/wc.dll?Wiki~VFP9RuntimeFiles). MSVCR71.DLL either must be installed into SYSWOW64 or into the same folder as the VFP exe. You may also install into Microsoft Shared, but then of course need to register it. It doesn't contain any COM Servers, though as far as I know, that's also a reason it's not autodetected for registration.

An old setup may not work on Win8, if it installs into System32, though Win8 downward compatibility will redirect writes to System32 to SYSWOW64 for 32bit setups, but not if you suggested to your clients to turn User Account Control Off, for example, or if you use a new 64bit version of Installshield to install 32bit software. Windows has no way to detect whether the installed software needs libraries or runtimes in System32 or Syswow64 and older versions of setup generating software obviously also can't know windows mechanisms for downward compatibility. In the light aof all this It's always best to install anything your app needs into it's folder in one place, this is also what MS recommends in regard to DLL hell. There are new concepts for assemblies, the global assembly cache, but that's .NET, not VFP stuff.

This has all been done very unsatisfactorily by MS, but in the end you may have bitten yourself.

Bye, Olaf.
0

Featured Post

Backup Your Microsoft Windows Server®

Backup all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
Technology opened people to different means of presenting information, but PowerPoint remains to be above competition. Know why PPT still works today.
This Micro Tutorial will give you a basic overview of Windows DVD Burner through its features and interface. This will be demonstrated using Windows 7 operating system.
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

863 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now