[trevor89]

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-me

To Enable copy shimgvw.dll to windows\system\
then type in Run Regsvr32 shimgvw.dll

then type regsvr32 webview.dll
then finaly regsvr32 mydocs.dll

Go 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.

[jds]

bristols, on 16 October 2008 - 03:32 AM, said:

MDGx, on May 20 2005, 01:04 AM, said:

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.EXE
Requires MS IE 5.5 SP2 or newer already installed

www.mdgx.com/files/scr57.php said:

FILE:
MSE 5.7:
http://www.mdgx.com/files/SCR579X.EXE

REQUIRED:
Requires MS Internet Explorer (IE) 5.5 SP2:
http://www.mdgx.com/ietoy.htm#IE55
or MS IE 6.0/6.0 SP1:
http://www.mdgx.com/ietoy.htm#6S1
already 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.

[dencorso]

If I had to bet on a single file, that would be shlwapi.dll...

[jds]

dencorso, on 16 June 2011 - 08:42 PM, said:

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.

[PROBLEMCHYLD]

What version is newer?

MSDIA80.DLL 8.0.50727.4053
MSDIA80.DLL 8.0.50727.42

[dencorso]

4053

Petr, on 15 December 2006 - 01:56 PM, said:

The 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.

[Anemos2006]

is it the Final version`_?

[CharlesF]

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.

This post has been edited by CharlesF: 05 November 2011 - 08:31 PM

[PROBLEMCHYLD]

blackwire, on 28 February 2007 - 01:26 PM, said:

SETUPAPI:
http://www.mdgx.com/web.htm#MEU
and:
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.EXE

This 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?

[Drugwash]

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.DLL
ADVAPI32.DLL
COMCTL32.DLL
COMDLG32.DLL
GDI32.DLL
LZ32.DLL
MPR.DLL
OLE32.DLL
RPCRT4.DLL
SHELL32.DLL
USER32.DLL
VERSION.DLL
WINSPOOL.DRV
CABINET.DLL
CFGMGR32.DLL

Best 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.

This post has been edited by Drugwash: 05 January 2012 - 12:03 AM

[PROBLEMCHYLD]

Drugwash, on 04 January 2012 - 11:46 PM, said:

Try the (presumably) Win2000 version 5.00.2195.1526

This 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.

[gerislamico]

erpdude8, on 15 May 2006 - 04:27 PM, said:

hey MDGx. check out the WTL app for creating and patching files at this site:
http://www.codeproje...tools/patch.asp

this 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" files
As they are generated and used to generate application
If I change the dlls, I must modify these files *. _p

[submix8c]

gerislamico, on 18 January 2012 - 08:17 AM, said:

What role do "*. _p" files

QFE vs GDR. Ignore them - AFAICT, they are deltas for the QFE "version" . Re-read the quote you gave.

[gerislamico]

submix8c, on 18 January 2012 - 08:56 AM, said:

gerislamico, on 18 January 2012 - 08:17 AM, said:

What role do "*. _p" files

QFE 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

[dencorso]

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.

[gerislamico]

Dencorso if I respond to me, then even be omitted in the repackaging to *. _p

[dencorso]

Yes. I think you can safely omit the *._p

[gerislamico]

dencorso, on 19 January 2012 - 09:31 PM, said:

Yes. I think you can safely omit the *._p

Thanks

[gerislamico]

MDGx, on 27 November 2005 - 06:02 PM, said:

Petr, on Nov 27 2005, 01:51 AM, said:

Hi MDGX, I found that for re-enabling of local troubleshooter just small registry change is necessary. And it should be noted that if local troubleshooter is enabled, Windows Update will show Internet Explorer Critical Update again. Two small INF files are attached. AFAIK it is not necessary to install Tshoot.ocx again. Or is it? I just noted that in your file is version 1.0.1.2123 while in Windows 98 SE is version 1.0.1.2115 and in Windows 98 Gold is version 1.0.0.2004 (and does not use chm file). Windows Me does not use ocx it at all.

Petr

You're right, TSHOOT.OCX is not really necessary to fix this bug, but [as you already noticed] this TSHOOT.OCX build is newer than all others, so besides fixing the REG entries, this fix also updates TSHOOT.OCX to newest version.
This TSHOOT.OCX build is from this MS update:

* Microsoft Windows 98/98 SP1/98 SE Troubleshooter HTML Help TSHOOT.OCX build 1.0.1.2123 + TSHOOT98.CHM Update:
http://support.micro...windows/tshoot/
Direct download [385 KB, English]:
http://www.mdgx.com/files/TSHOOT98.ZIP
posted here [scroll all the way down to the bottom of topic]:
http://www.mdgx.com/web.htm#98SE

Hope this helps.

It is necessary to modify the original Win98SE TSHOOT98.CHM the new TSHOOT98.CHM Microsoft Windows 98/98 SP1/98 SE Troubleshooter HTML Help
If so, what is the change to do in TSHOOT98.CHM Spanish version and modify that application the same
Thanks for your reply

PD:
They have something to do these log entries with the changes
HKLM,"SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{4B106874-DD36-11D0-8B44-00A024DD9EFF}","Compatibility Flags",0x00010001,0x000
HKLM,Software\Microsoft\Windows\CurrentVersion\Runonce,"Reg",,"%11%\regsvr32 /s %18%\TShoot.ocx"

This post has been edited by gerislamico: 03 February 2012 - 03:07 PM