Jump to content

Maximus Decim Data Access Component Update, New! MDDACU 1.1


Recommended Posts

MD Data Access Component Update 1.1

Only for Windows 98se

----------------------------------------------------------------

MDAC 2.8sp1 (include MSXML 3.0SP7)

Jet 4.0sp8 (837001)

Jet 4.0 Repl (321076)

MSXML 4.0 SP2 + 887606

2 files Jet 3.5sp3 (msjet35.dll, msrepl35.dll)

2 files MDAC 2.5sp3 (vfpodbc.dll, drvvft.chm - Visual FoxPro Driver)

XMLinst 3.0

3 files IE6sp1 + 832414(msxml.dll, msxmld.dll, msxmlr.dll - MSXML 2.5sp3)

MSXML 2.6sp2 + 887606

KB911562 - Update for MDAC ver.2.8sp1

KB870669 - Security update for MDAC

---------------------------------------------------------------

english - http://rapidshare.de/files/18802937/MDDACU11E.EXE.html

russian - http://rapidshare.de/files/18801381/MDDACU11R.EXE.html

For silent installation it is necessary to unpack archive (this cab-archve)

in any directory and to run the "setup.exe /Q"

What's new:

added

*KB911562 - Update for MDAC ver.2.8sp1

*KB870669 - Security update for MDAC

Link to comment
Share on other sites


Hi Maximus-Decim,

well, I know what the NUSB does (you also had nice text explanation)..and it's great!!

What will this upgrade do for me besides update components (what are the components used for)?

Edited by jasinwa
Link to comment
Share on other sites

-can this package be used as the "MSXML fixes" which we are supposed to apply after the 905915/912812 update(s)? (MDGx says we have to do HTML Help Update before, and MSXML fixes after, those updates... ) ?

Link to comment
Share on other sites

Hey again, PsychoUnc!

Yep, I just did it like I always do. This package works fine for the "After."

Edit - But I did need to manually replace URLMON.DLL with the older version in KB905915. The installer didn't put the older file over the newer one. I used System File Checker for this, having extracted KB905915.

Edited by Eck
Link to comment
Share on other sites

After I had replaced the buggy URLMON.DLL from KB912812 (build 6.00.2800.1538) with the older version from 905915 (build 6.00.2800.1526), I tried to install MDDACU 1.1. When the installer was "Setting up Control Panel", I got this error message:

RUNDLL32 caused an invalid page fault in
module KERNEL32.DLL at 016f:bff7a138.
Registers:
EAX=01472064 CS=016f EIP=bff7a138 EFLGS=00210212
EBX=0041c710 SS=0177 ESP=03befcfc EBP=03befd30
ECX=20616d6d DS=0177 ESI=0041c6a4 FS=424f
EDX=64616f4c ES=0177 EDI=014720d0 GS=0000
Bytes at CS:EIP:
89 51 08 8b 53 08 8b 43 04 89 42 04 8d 93 0b 10
Stack dump:
03befd30 0041c6a4 00410000 00000000 bff7b31d 00410000 0041c6a4 0000006c 00000200 0041abb8 0041ac38 00000000 0041c6a4 03befd6c 65f014db 00410000

I had applied the Kernel Update to KERNEL32.DLL some time ago. Could the updated KERNEL32.DLL be the reason for the error message?

Then I uninstalled the Kernel Update, and tried installing MDDACU 1.1 again. Same error message. :(

After clicking off the error message, the rest of the installation seems to complete OK.

What gives?

Edited by bristols
Link to comment
Share on other sites

Hmmm, some new glich, eh? My install of the MDAC updater went fine. Don't know what might be mucking up the works there.

Just guessing it's probably something left over from that kernel32 project. Frustrating, freak'n Windows! Perhaps the important stuff got installed. Have you tried testing Internet Explorer to see if ActiveX stuff will again install properly and work?

Mine mostly does. I had a problem with Windows Update Catalog when trying to go to my download basket, but that might be a Windows Catalog website problem. Dunno, really.

Also, sometimes different versions of MDAC components installed by other programs stop proper installation of other versions. Right now the only 3rd party interferrence I've got with MDAC is the ATI Multimedia Center and possibly stuff installed by WorksSuite 2005. Since I have the latest available versions of both installed, perhaps that's why the MDAC updater worked for me without problems.

If you've got some really old version installed by a game or something it might interfere. See in add/remove if you have DAO listed, and if it's there more than once (meaning you may have more than one version).

Link to comment
Share on other sites

Well I have too the kernel update installed but I don't have any problems with installing this. The kernel update itself cannot be the cause.

And housecall is working like it should again! Thanks a lot

Edited by noguru
Link to comment
Share on other sites

Yeah, I guess it's some other problem interferring. It'll be nice if he can troubleshoot it out, but if not I suppose he'll need to clean install again. Sheesh! I hate when that happens.

Link to comment
Share on other sites

Hi Eck and noguru,

Thanks for the feedback regarding the error message I received when installing MDDAC 1.1 - helpful to know that MDDAC installed without problems for the both of you. I think I've narrowed down my problem to a handful of files, after getting an idea from another forum member. I haven't got any further than that in terms of troubleshooting the issue, just yet. Anyway, the updated MDDAC files did all seem to install (insofar as they actually replaced older files).

I tried installing MDDAC 1.1 on another 98 SE box, different in a few ways from the box on which I received the above kernel error. The attempted installation on this other box was successful - MDDAC 1.1 installed just fine, with the updated KERNEL32.DLL from Kernel Update Project. So yes noguru, it seems that the KUP can't be the cause of the problem.

The box with the kernel error has files from MDGx's 98SE2XP installation scripts (the IE files only, not the WMP files), and a handful of 2003 replacement files (that the successful-install box doesn't have). The successful-install box has 98SE2ME Option 2 installed, the kernel-error box doesn't.

So, perhaps the culprit(s) is one of those 98SE2XP files, or one of the handful of 2003 replacements. I will post again once I have a definitive answer. ;)

Edited by bristols
Link to comment
Share on other sites

...that's a great combo of install beds, bristols...

:yes:

... if I weren't so busy [lazy :boring: ], I'd keep up a # of diff. install dir's [i already have a tiny (yet careful) real-mode DOS batch snippet that quickly switches between w98se installs (renames any 2 sets of ProgFiles/Windows dirs); -I used to keep 4 or 5 going, during testing/experimentation, til school got me busy this year)...

>;]

Link to comment
Share on other sites

I tried installing MDDAC 1.1 on another 98 SE box, different in a few ways from the box on which I received the above kernel error. The attempted installation on this other box was successful - MDDAC 1.1 installed just fine, with the updated KERNEL32.DLL from Kernel Update Project. So yes noguru, it seems that the KUP can't be the cause of the problem.

The box with the kernel error has files from MDGx's 98SE2XP installation scripts (the IE files only, not the WMP files), and a handful of 2003 replacement files (that the successful-install box doesn't have). The successful-install box has 98SE2ME Option 2 installed, the kernel-error box doesn't.

So, perhaps the culprit(s) is one of those 98SE2XP files, or one of the handful of 2003 replacements. I will post again once I have a definitive answer.

Please do, I'm curious which 98SE2XP [ http://www.mdgx.com/98-5.htm#MP9 ] file(s) are buggy, so I can remove them.

Thanks.

Link to comment
Share on other sites

  • 7 months later...

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.
×
×
  • Create New...