trevor89 Posted April 10, 2011 Share Posted April 10, 2011 I just thought Id post this for those who want to try it. (I know its been added then taken out again )Windows ME's My Pictures Shimgvw.dll window in 98se.The following is not included in 98-2-me as some have complained of incompatabilities.However I have now got it on 2 computers of different configurations.Select Option 3 in 98-to-meTo Enable copy shimgvw.dll to windows\system\then type in Run Regsvr32 shimgvw.dllthen type regsvr32 webview.dllthen finaly regsvr32 mydocs.dllGo to My Pictures and you should now see a nice zoom in/out box in the left side when you select an image.Trev.P.S. the 2 other steps get rid of the script error about wiamgr.devices...With rp7 this wasnt required however with rp9.7 it is. Link to comment Share on other sites More sharing options...
jds Posted June 17, 2011 Share Posted June 17, 2011 Unofficial MSE 5.7 5.7.0.18066 + JSCRIPT.DLL 5.7.0.20550 for Windows 98/98 SP1/98 SE/ME [732 KB]:http://www.mdgx.com/files/SCR579X.EXERequires MS IE 5.5 SP2 or newer already installedFILE:MSE 5.7:http://www.mdgx.com/files/SCR579X.EXEREQUIRED:Requires MS Internet Explorer (IE) 5.5 SP2:http://www.mdgx.com/ietoy.htm#IE55or MS IE 6.0/6.0 SP1:http://www.mdgx.com/ietoy.htm#6S1already installed!Any idea what is this requirement for IE 5.5 or higher? I've just installed with IE5.01SP2 and everything seems normal. (What's the best way to test?)Joe. Link to comment Share on other sites More sharing options...
dencorso Posted June 17, 2011 Share Posted June 17, 2011 If I had to bet on a single file, that would be shlwapi.dll... Link to comment Share on other sites More sharing options...
jds Posted June 18, 2011 Share Posted June 18, 2011 If I had to bet on a single file, that would be shlwapi.dll...Thanks, Den.Well, my installed version of 'shlwapi.dll' is 5.00.3314.2100, which is consistent with the version numbering for IE 5.01SP2. SCR579X seemed to have installed fine with this, however, if I do encounter Javascript problems, I'll try extracting the IE 5.5 version and seeing if that makes any difference.BTW, that link was an interesting "can of worms"! It's a shame, I can't help but feel we are missing some potentially valuable members and are poorer as a result. (The sudden disapperance of LLXX is one example that comes to mind.)Joe. Link to comment Share on other sites More sharing options...
PROBLEMCHYLD Posted July 26, 2011 Share Posted July 26, 2011 What version is newer?MSDIA80.DLL 8.0.50727.4053MSDIA80.DLL 8.0.50727.42 Link to comment Share on other sites More sharing options...
dencorso Posted July 26, 2011 Share Posted July 26, 2011 4053The version number is stored as four 16-bit words, each part of it may have value 0 to 65535. So the lowest version number is 0.0.0.0 and the highest 65535.65535.65535.65535.Nowadays the version number may use four 32-bit numbers instead of 16-bit numbers, but the logic remains the same. Link to comment Share on other sites More sharing options...
Anemos2006 Posted October 4, 2011 Share Posted October 4, 2011 is it the Final version`_? Link to comment Share on other sites More sharing options...
CharlesF Posted November 6, 2011 Share Posted November 6, 2011 (edited) The new VBVM60.EXE 6.0.9821 is not working (at least) for me.I had to manually use the VBVM60.INF.EDIT: BTW, the link More info on the 11-1-2011 Update page is wrong.You have to use the one from the main Visual Basic (VB) page: More info. Edited November 6, 2011 by CharlesF Link to comment Share on other sites More sharing options...
PROBLEMCHYLD Posted January 5, 2012 Share Posted January 5, 2012 SETUPAPI:http://www.mdgx.com/web.htm#MEUand:http://www.mdgx.com/web.htm#9SU* Unofficial Windows 98/98 SP1/98 SE/ME SETUPAPI.DLL 5.1.2600.2180 Update [442 KB]:http://www.mdgx.com/files/SETUPAPI.EXEThis patch breaks NUSB 2.4 and 3.0. With updated file, when I clicked on the NUSB icon in the system tray, it did not respond. When I restored the original setupapi.dll everything worked fine.Can someone look into this issue and try to find a fix. I would like to add it to the Service Pack? Link to comment Share on other sites More sharing options...
Drugwash Posted January 5, 2012 Share Posted January 5, 2012 (edited) Try the (presumably) Win2000 version 5.00.2195.1526 (I'm currently using it) or a similar one within the 5.0.xxxx.xxxx range. The XP version (5.1.xxxx.xxxx) may just not work.EDIT:Careful though - it does have a lot of dependencies:KERNEL32.DLLADVAPI32.DLLCOMCTL32.DLLCOMDLG32.DLLGDI32.DLLLZ32.DLLMPR.DLLOLE32.DLLRPCRT4.DLLSHELL32.DLLUSER32.DLLVERSION.DLLWINSPOOL.DRVCABINET.DLLCFGMGR32.DLLBest if you can test it first on a vanilla 98SE, open it in Dependency Walker and see if there's any missing module/function. If everything's OK, you can include the new version among the first replaced files; otherwise wait until its requirements are updated and only then replace it. Edited January 5, 2012 by Drugwash Link to comment Share on other sites More sharing options...
PROBLEMCHYLD Posted January 5, 2012 Share Posted January 5, 2012 Try the (presumably) Win2000 version 5.00.2195.1526This version is included in 98SE2ME. Its the WinME version.The WinXP version works great besides the systray icon bug. I have tested this in the past. Link to comment Share on other sites More sharing options...
gerislamico Posted January 18, 2012 Share Posted January 18, 2012 hey MDGx. check out the WTL app for creating and patching files at this site:http://www.codeproject.com/tools/patch.aspthis tool uses the MSPATCHA.DLL file to "patch" existing files (like what the IEUPDATE.EXE file does to those DLL files in IE updates like KB912812, KB905915. etc.). you'll have to login to the CodeProject site to download the WTL patcher. it can also use the MSPATCHC.DLL file to create patches.IEUPDATE.EXE uses the info from the "_SFX_MANIFEST_" file inside recent IE updates to "patch" many of the DLL files.Contents of the "_SFX_MANIFEST_" file from IE update KB912812:--------[Deltas]"RTMQFE\browseui.dll" = "browseui.dll._p", browseui.dll"RTMQFE\cdfview.dll" = "cdfview.dll._p", cdfview.dll"RTMQFE\danim.dll" = "danim.dll._p", danim.dll"RTMQFE\dxtrans.dll" = "dxtrans.dll._p", dxtrans.dll"RTMQFE\iepeers.dll" = "iepeers.dll._p", iepeers.dll"RTMQFE\inseng.dll" = "inseng.dll._p", inseng.dll"RTMQFE\mshtml.dll" = "mshtml.dll._p", mshtml.dll"RTMQFE\msrating.dll" = "msrating.dll._p", msrating.dll"RTMQFE\mstime.dll" = "mstime.dll._p", mstime.dll"RTMQFE\pngfilt.dll" = "pngfilt.dll._p", pngfilt.dll"RTMQFE\shdocvw.dll" = "shdocvw.dll._p", shdocvw.dll"RTMQFE\shlwapi.dll" = "shlwapi.dll._p", shlwapi.dll"RTMQFE\urlmon.dll" = "urlmon.dll._p", urlmon.dll"RTMQFE\wininet.dll" = "wininet.dll._p", wininet.dll[Verify]"RTMQFE\browseui.dll" = 4CCEFD261EB9C0481F3EADB60305A07F"RTMQFE\cdfview.dll" = 6F6648E2197EDA21C1D2CF1D6887D9F2"RTMQFE\danim.dll" = CC6F690887A37362C21326D332F48AA7"RTMQFE\dxtrans.dll" = A4D8D11EEEFC1A89CCF7FA5698C27B85"RTMQFE\iepeers.dll" = 7D7AA31981F6770C7323C713869CC49E"RTMQFE\inseng.dll" = AA1E2E594CF861D1200100C9988E5332"RTMQFE\mshtml.dll" = D2C040629DC44C110897009366CB93B0"RTMQFE\msrating.dll" = F02EB202619E20B537331EEC54FB30C2"RTMQFE\mstime.dll" = E31099347F200693B4A8A1F81BF9ECE8"RTMQFE\pngfilt.dll" = 4DB34F3C29CFD1DF1F92FCD9C8DDB755"RTMQFE\shdocvw.dll" = A79348B75DA190EC91E2BA5CCF5C25BE"RTMQFE\shlwapi.dll" = D311A7FC4E081EE7AAAA6F581CF3C471"RTMQFE\urlmon.dll" = 9C40366FD9BE7965408C51C102E18879"RTMQFE\wininet.dll" = AAA8906281E95954A20DF24BFC288FDE[Delete]"*._p"--------also bundled inside recent IE updates are files with extension "._p" < those are patch files. IEUPDATE along with the MSPATCHA.DLL file patches the original DLL files (those are the RTMGDR editions) with the "._p" files, thus turning them into the RTMQFE editions of the DLL files.What role do "*. _p" filesAs they are generated and used to generate applicationIf I change the dlls, I must modify these files *. _p Link to comment Share on other sites More sharing options...
submix8c Posted January 18, 2012 Share Posted January 18, 2012 What role do "*. _p" filesQFE vs GDR. Ignore them - AFAICT, they are deltas for the QFE "version" . Re-read the quote you gave. Link to comment Share on other sites More sharing options...
gerislamico Posted January 18, 2012 Share Posted January 18, 2012 What role do "*. _p" filesQFE vs GDR. Ignore them - AFAICT, they are deltas for the QFE "version" . Re-read the quote you gave.If you edit a DLL and change the internal language for example, I create a new file type. _p Link to comment Share on other sites More sharing options...
dencorso Posted January 18, 2012 Share Posted January 18, 2012 Sure. The deltas are for creating the QFE version. It's a way to save space, as the QFE contain just a bunch of bytes that differ from the GDR, and the deltas simply record which bytes should be changed and how to change them... they are patch patterns. 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