Frontpage
Forums
Tutorials
Members
Calendar
Subscription
Donate
Links
Contact 
HelpThis post has been edited by daddydave: 02 January 2007 - 09:55 PM
Page 1 of 1
msvbvm60.dll?
in HFSLIP/FIX
Rate Topic:
#1
- Member
-
- Group: Members
- Posts: 102
- Joined: 08-December 06
- OS:Windows 7 x64
-
Country:
Posted 02 January 2007 - 09:55 PM
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?
Back to top
#2
- Area 5 Investigator
-
- Group: Super Moderator
- Posts: 2,991
- Joined: 27-January 04
- OS:Windows 7 x64
-
Country:
Posted 02 January 2007 - 10:10 PM
It's the primary DLL that drives all Visual Basic 6+ applications.
#3
- Member
-
- Group: Members
- Posts: 102
- Joined: 08-December 06
- OS:Windows 7 x64
-
Country:
Posted 02 January 2007 - 10:30 PM
Tarun, on Jan 2 2007, 11:10 PM, said:
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?
#4
- Area 5 Investigator
-
- Group: Super Moderator
- Posts: 2,991
- Joined: 27-January 04
- OS:Windows 7 x64
-
Country:
Posted 02 January 2007 - 11:30 PM
Not so much replacing a bad DLL, but it comes standard with XP; and I know CCleaner is dependent on it.
#5
- Member
-
- Group: Members
- Posts: 102
- Joined: 08-December 06
- OS:Windows 7 x64
-
Country:
Posted 03 January 2007 - 12:06 AM
Tarun, on Jan 3 2007, 12:30 AM, said:
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...
This post has been edited by daddydave: 03 January 2007 - 12:06 AM
#6
- MSFN Junkie
-
- Group: Developers
- Posts: 3,171
- Joined: 08-August 05
Posted 03 January 2007 - 03:53 AM
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.
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.
This post has been edited by Tomcat76: 03 January 2007 - 04:01 AM
#7
- Friend of MSFN
-
- Group: Members
- Posts: 970
- Joined: 15-January 06
Posted 03 January 2007 - 06:49 AM
For gdiplus.dll, there is a hotfix named gdiplus_dlnd.exe for 2K that you can place in HF.
#8
- Member
-
- Group: Members
- Posts: 102
- Joined: 08-December 06
- OS:Windows 7 x64
-
Country:
Posted 08 January 2007 - 05:22 PM
Super-Magician, on Jan 3 2007, 07:49 AM, said:
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.
Share this topic:
Page 1 of 1