daddydave Posted January 3, 2007 Share Posted January 3, 2007 (edited) What is the significance of msvbvm60.dll that some people put in the FIX folder? I see it has something to do with VB. Is there a bad version in the original source? Edited January 3, 2007 by daddydave Link to comment Share on other sites More sharing options...
Tarun Posted January 3, 2007 Share Posted January 3, 2007 It's the primary DLL that drives all Visual Basic 6+ applications. Link to comment Share on other sites More sharing options...
daddydave Posted January 3, 2007 Author Share Posted January 3, 2007 It's the primary DLL that drives all Visual Basic 6+ applications.And by putting it in the FIX folder, it is replacing a bad DLL? Link to comment Share on other sites More sharing options...
Tarun Posted January 3, 2007 Share Posted January 3, 2007 Not so much replacing a bad DLL, but it comes standard with XP; and I know CCleaner is dependent on it. Link to comment Share on other sites More sharing options...
daddydave Posted January 3, 2007 Author Share Posted January 3, 2007 (edited) Not so much replacing a bad DLL, but it comes standard with XP; and I know CCleaner is dependent on it.So I can introduce new DLL's in that folder there in addition to FIXing DLL's if I understand you correctly...I might try putting gdiplus.dll there then to see if it makes Launchy happy... Edited January 3, 2007 by daddydave Link to comment Share on other sites More sharing options...
Tomcat76 Posted January 3, 2007 Share Posted January 3, 2007 (edited) To replace an existing file permanently, overwrite the original file yourself in the SOURCE folder.To replace a compressed file that would exist in SOURCESS\I386 near the end of an HFSLIP run, place the new compressed file in the FIX folder.To replace an uncompressed file that would exist in SOURCESS\I386 near the end of an HFSLIP run, place the new uncompressed file in the FIX folder.There is also HFEXPERT\APPREPLACEMENT. The new files should always be uncompressed. ModifyPE is run on files in APPREPLACEMENT before they are slipstreamed. Edited January 3, 2007 by Tomcat76 Link to comment Share on other sites More sharing options...
Super-Magician Posted January 3, 2007 Share Posted January 3, 2007 For gdiplus.dll, there is a hotfix named gdiplus_dlnd.exe for 2K that you can place in HF. Link to comment Share on other sites More sharing options...
daddydave Posted January 8, 2007 Author Share Posted January 8, 2007 For gdiplus.dll, there is a hotfix named gdiplus_dlnd.exe for 2K that you can place in HF.Thanks, Super-Magician, that fixed my Launchy issue. Ironically I already had two versions of the file from .NET 1.1 and .NET 2. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now