Welcome to MSFN

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


whatever420

Newer Version .dll files?

33 posts in this topic

Hey folks...

I downloaded an app yesterday (Browser Hijack Retaliator) from http://www.zamaansoft.com/products/bhr/index.php .

Inside, I found 6 dll files that are newer than any I've come across before...

  1. ASYCFILT.DLL (version 3.50.5014)
  2. COMCAT.DLL (version 5.0 (XPClient.010817-1148))
  3. DAO350.DLL (version 3.51.1608.0)
  4. OLEAUT32.DLL (version 3.50.5014.0)
  5. OLEPRO32.DLL (file version 5.0.5014 / product version 3.50)
  6. STDOLE2.TLB (version 3.50.5014)

dlls.gif

Has anyone run across these versions before?

Does anyone know if they are for use in an Win98SE environment?

Any help is great appreciated :) .

Here are the .dll files (compressed 7z self-extractor):

http://members.dialmaine.com/drdole/Apps/DLLS.exe

Edited by whatever420
0

Share this post


Link to post
Share on other sites

Those files aren't good for 9x OSes AFAIK.

0

Share this post


Link to post
Share on other sites

I have these .dll files on my 98SE system, Rev's are older than your list, but newer than original install. The Zamaan's Software site says Browser Hijack Retaliator supports 98.

If you trust Zamaan's, and the site you used for the download, then newer .dll versions don't seem worrisome to me, although it would be wise to archive copies of your versions in a .zip file before you do the install so you can go back. If you don't completely trust Zamaan's then it is wiser not to install BHR even if the .dll's matched your own.

0

Share this post


Link to post
Share on other sites

Thanks for the responses...

Anyone else want to weigh in...?

0

Share this post


Link to post
Share on other sites

I have tried your OLE DLLs on my Win98 SE.

Everything OK, except that Internet Explorer web browser external links/URLs stopped working. :(

Those DLLs are probably from WinXP retail or some Win2004 Service Pack.

They are not meant for 9x OSes.

Last versions known to work properly with all 9x OSes are these:

http://www.mdgx.com/add.htm#OLE

respectively this file:

http://www.mdgx.com/files/OLEUP.EXE

OLEUP installs these files:

ASYCFILT.DLL 2.40.4528

OLEAUT32.DLL 2.40.4522

OLEDLG.DLL 5.0.1601.0

OLEPRO32.DLL 5.0.4528

STDOLE2.TLB 2.40.4528

Also, WinME COMCAT.DLL 5.0.1601.1 works ok with Win98 FE (retail/Gold/1st edition) + 98 SE.

BTW, COMCAT.DLL 5.0.1601.1 is installed by 98SE2ME:

http://www.mdgx.com/98-5.htm#KRM9S

DAO350.DLL 3.51.1608.0 is installed by current MDAC patches:

http://www.mdgx.com/add.htm#DAC

to my knowledge.

HTH [Hope This Helps]

0

Share this post


Link to post
Share on other sites

Thanks for your input MDGx...

Yes, the info you provided helps quite a bit... :)

0

Share this post


Link to post
Share on other sites

Greetings to you all!

This is my first post to this forum,

although I've been reading it for some time now...

I've been experimenting with the files posted by whatever420

and here are my findings:

I have the latest OLEUP installed

in my fully updated Win 98SE system,

so I started with these files:

ASYCFILT.DLL 2.40.4528

OLEAUT32.DLL 2.40.4522

OLEDLG.DLL 5.0.1601.0

OLEPRO32.DLL 5.0.4528

STDOLE2.TLB 2.40.4528

Since whatever420's post, I've been running

OLEPRO32.DLL 5.0.5014 instead of 5.0.4528

and

COMCAT.DLL 5.0.2600.1

in my system, having found no apparent problems.

It's been about a month already, so I thought I

should write you about it.

Previously I had been using

COMCAT.DLL 5.0.2195.1

(I can't remember whence exactly did I get it...)

It also worked fine.

But these COMCAT.DLL are all 5.0, as is also

COMCAT.DLL 5.0.1601.1, installed by 98SE2ME

so the all should work well with OLE32.DLL 4.71

(I use currently OLE32.DLL 4.71.3328.0)

See http://support.microsoft.com/default.aspx?...B;EN-US;Q201364

Then again,

OLEPRO32.DLL 5.0.5014 is a different matter,

because it's OLE 3.50 and all the files installed

by OLEUP are 2.40, including OLEPRO32.DLL 5.0.4528,

but it is an experimental fact that it works well,

at least in my machine. So, despite the fact it's

OLE 3.50, OLEPRO32.DLL 5.0.5014 seems to be the

most updated version of OLEPRO32 to run correctly

on Win 98SE...

As for the other OLE 3.50 files posted by whatever420,

I agree with MDGx: they do not work correctly on 98SE.

0

Share this post


Link to post
Share on other sites
ASYCFILT.DLL 2.40.4528

OLEAUT32.DLL 2.40.4522

OLEDLG.DLL 5.0.1601.0

OLEPRO32.DLL 5.0.4528

STDOLE2.TLB 2.40.4528

MDGx, can you re-package your OLE Automation patch to include the following:

ASYCFILT.DLL v2.40.4530 (from KB917423)

OLEAUT32.DLL v2.40.4519 (from VB6 KB924053)

OLEPRO32.DLL v5.0.4530 (from KB917423)

STDOLE2.TLB v2.40.4530 (from KB917423)

As for the other OLE 3.50 files posted by whatever420,

I agree with MDGx: they do not work correctly on 98SE.

me too. I've gotten "missing export" errors with OLE 3.50 files with Win9x's Autoplay option enabled when accessing CDs. The OLE 3.50 files are meant for WinXP only and not for other Windows OSes.

Edited by erpdude8
0

Share this post


Link to post
Share on other sites

Thanks for the OLE automation update, MGDx. It fixed an intermittent crash starting ZoneAlarm 5.5 in Win98 :thumbup

0

Share this post


Link to post
Share on other sites

Neat, dencorso's first post was apparently in this thread. Kind've a weird thread to necromancy (and with a double-post no less), but whatever.

Queue

0

Share this post


Link to post
Share on other sites

I confirm that one was my 1st post here, all right. I had lurked in the shadows for about two years, by then... :)

I don't mind some eventual thread resurrection... it brings over fond memories.

BTW, duplicate post removed.

0

Share this post


Link to post
Share on other sites

COMCAT.DLL 5.0.2600.1

in my system, having found no apparent problems.

It's been about a month already, so I thought I

should write you about it.

Previously I had been using

COMCAT.DLL 5.0.2195.1

(I can't remember whence exactly did I get it...)

It also worked fine.

COMCAT.DLL 5.0.2600.1

I believe it from Office 2003. It is on and old Winxp sp2 machine I have laying around.

COMCAT.DLL 5.0.2195.1 Comes from Windows 2000 SP4.

I will be adding one of the files to SP3. Do you have any more newer files that work on Win98?

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

OLEAUT32.DLL 2.40.4532.0 Windows 2000 Service Pack 4

Does not work. It breaks VB scripts and display an ActiveX error.

I still use COMCAT.DLL 5.0.2600.1, but downgraded OLEPRO32.DLL to 5.0.4530.0 after finding some issue with OLEPRO32.DLL 5.0.5014. And regarding OLEAUT32.DLL, I've stopped updating it at 2.40.4520.0. Never found a latter version that really worked OK.

0

Share this post


Link to post
Share on other sites

I still use COMCAT.DLL 5.0.2600.1, but downgraded OLEPRO32.DLL to 5.0.4530.0 after finding some issue with OLEPRO32.DLL 5.0.5014. And regarding OLEAUT32.DLL, I've stopped updating it at 2.40.4520.0. Never found a latter version that really worked OK.

OLEAUT32.DLL 2.40.4522 Windows 2000 SP4 works with no problems on my system. I think maybe you should try it out.

I haven't had any apps break or any popup errors

0

Share this post


Link to post
Share on other sites

Found 2 more versions. I haven't tested them yet.

OLEAUT32.DLL 2.40.4527.0 (Windows2000-KB886766-v2-x86-ENU.EXE) +V3

OLEAUT32.DLL 2.40.4528.0 (Windows2000-KB139071-x86-ENU.EXE)

0

Share this post


Link to post
Share on other sites

Some newer files you guys can test. I will test them sometime this week.

GDIPLUS.DLL 5.2.6002.22791

MSSTDFMT.DLL 6.1.98.16

RICHED20.DLL 5.40.11.2221

0

Share this post


Link to post
Share on other sites

I still use COMCAT.DLL 5.0.2600.1, but downgraded OLEPRO32.DLL to 5.0.4530.0 after finding some issue with OLEPRO32.DLL 5.0.5014. And regarding OLEAUT32.DLL, I've stopped updating it at 2.40.4520.0. Never found a latter version that really worked OK.

OLEAUT32.DLL 2.40.4522 Windows 2000 SP4 works with no problems on my system. I think maybe you should try it out.

I haven't had any apps break or any popup errors

I'm sorry I wasn't quick enough to react in time but OLEAUT32.DLL v.2.40.4520.0, with PE Timestamp of 12/3/2007, is actually *newer* than v. 2.40.4522.0, which has a PE Timestamp of 06/20/2003 !!! :P

I've discussed it at some lenght here and here.

0

Share this post


Link to post
Share on other sites

USBUI.DLL 5.1.2600.5512 Windows XP SP3 works with no problems :thumbup

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

This is just a heads up, because I released this tool in the Unattended Win2k forum... :angel

To see the original release post, please do click in the curly arrow in the quotation box header.

<snip> Well, here I am, back to the subject of PETimestamps... <snip>

[i have written] my own application for this, using an unambiguous format for the time and date string, and also presenting the hexadecimal unix time, together with the file name, all this in just one line. And it also supports "*.*", of course! I called it, rather unimaginatively, PETmStp (attached below), and here's hoping it will be as useful as I anticipated it should be. Please do report any bugs found.

PETmStp.7z

0

Share this post


Link to post
Share on other sites

:thumbup Thanks for the tool :thumbup

As you can see I have updated some files in the SP from using your tool.

I always thought we was suppose to go by the version number. Apparently I was wrong. Thanks again.

0

Share this post


Link to post
Share on other sites

The problem with version numbers is MS starts their numbering from arbitrary points... So, while one keeps *only* to files *they* intended for a given OS, version numbers work OK (sort of...). But when we started including files they intended should be used in NT6, Win2K and now WinXP, some numbering lines began to cross. This explanation holds for most cases, but, maybe, not all. :)

0

Share this post


Link to post
Share on other sites

The problem with version numbers is MS starts their numbering from arbitrary points... So, while one keeps *only* to files *they* intended for a given OS, version numbers work OK (sort of...). But when we started including files they intended should be used in NT6, Win2K and now WinXP, some numbering lines began to cross. This explanation holds for most cases, but, maybe, not all. :)

I guess that's why HFSLIP goes by date and not by version.

I don't know if I missed any, but I think I have all the latest working updates as of now for SP3.

I'm sure if I continue working on it, I will find more ways to improve it. Thanks again :w00t:

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

Found 2 more versions. I haven't tested them yet.

OLEAUT32.DLL 2.40.4527.0 (Windows2000-KB886766-v2-x86-ENU.EXE) +V3

OLEAUT32.DLL 2.40.4528.0 (Windows2000-KB139071-x86-ENU.EXE)

those 4527 and 4528 builds of oleaut32.dll file will break some apps on your 98se machine, PROBLEMCHYLD.

just like with what build 4532 from win2k did.

I use the NT4 version of oleaut32.dll file 2.40.4520.0 dated 12/21/2007 which is actually newer than 2.40.4522 dated 6/20/2003.

and here's a shocker about v2.40.4520 of oleaut32.dll! (pay close attention dencorso and PROBLEMCHYLD!)

it's also listed in MS KB article 327177.

BUT version 2.40.4520 of oleaut32.dll in KB327177 is dated 5/31/2002 with a size of 929,792 bytes

while version 2.40.4520 of oleaut32.dll in MS08-008 (946235) is dated 12/21/2007 with a size of 939,144 bytes.

SO, those two oleaut32.dll files that are version 2.40.4520 are NOT binarily identical (hmm, did Microsoft loose track of version numbers there?) confusing, isn't it?

I have the newest working oleaut32.dll file (build 4520) from the MS08-008 security bulletin for Win9x.

Edited by erpdude8
0

Share this post


Link to post
Share on other sites

@erpdude8

Unfortunately this seems to be a standard M$ practice... A lot of Win2k udpates (especially HBRs) have got files with same version number as the other ones but the file itself may be different / have different date, etc. A good way to determine which one is really newer is to compare version number first, and then, if they are identical, use xcopy/d to use the newer one (by date). HFSLIP uses xcopy/d only which in my opinion is a very bad method because there are sometimes newer files with older date. That's why I use both - first version compare and then xcopy/d only if the version is identical.

0

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.