Jump to content

98 FE + 98 SE + ME updates + patches + (hot)fixes


Recommended Posts

Now I have these new patches that I need to post [unsorted, some may be posted already]:

- Windows ME:

ME268452.EXE

ME272620.EXE

ME289635.EXE

ME300889.EXE

ME301540.EXE

ME304708.EXE

ME307908.EXE

ME309081.EXE

ME311430.EXE

ME314417.EXE

ME321635.EXE

- Windows NT 4.0 Workstation:

KB823803.EXE

KB824105.EXE

KB840987.EXE

KB841356.EXE

KB841533.EXE

KB873339.EXE

KB873350.EXE

KB885249.EXE

KB885835.EXE

KB885836.EXE

KB891711.EXE

KB896358.EXE

Hope this helps.

MDGx,

Petr sent me the 260710, 268356, 277784, 278368, and the 304082 updates. These updates are not on that list. Would you like them sent to you?

You already have the 272620 and the 314417 updates posted.

the_guy

Link to comment
Share on other sites


If I've been asking it is because I recalled the above post.

...that post was by erpdude, not by one of the win98se Prophets (MDGx, Gape)... I just did a few searches thru forums & google, and nowhere is it mentioned (by the Prophets) that his FIXED ole update breaks anything... (a few of the IE cumul. updates are mentioned as Help-breakers...), and this topic has been rehashed so much, we all should know exactly what Prophet MDGx has (painfully) restated, again, above, regarding it... it's very simple to remember: oleupdate 4526 only needs one of the 4 files to be 4522... and then no probs... very easy.

>;]

Link to comment
Share on other sites

If I've been asking it is because I recalled the above post.

...that post was by erpdude, not by one of the win98se Prophets (MDGx, Gape)... I just did a few searches thru forums & google, and nowhere is it mentioned (by the Prophets) that his FIXED ole update breaks anything... (a few of the IE cumul. updates are mentioned as Help-breakers...), and this topic has been rehashed so much, we all should know exactly what Prophet MDGx has (painfully) restated, again, above, regarding it... it's very simple to remember: oleupdate 4526 only needs one of the 4 files to be 4522... and then no probs... very easy.

>;]

Timeline : Ole update 4526 is first posted by MDGx. Various problems are reported by several users. It is then spotted Oleaut32.dll is responsible for those problems. Then MDGx posts an updated Oleupdate 4526 with an Oleaut32.dll downgraded to version 4522. At this stage erpdude specifically asks a special Oleupdate for Windows ME with ALL files of version 4522 (post quoted by me above). Neither Gape nor MDGx are using WinMe as far as I know. At erpdude's request MDGx then posts a special Oleupdate for WinMe that contains only files of version 4522. Then a few days ago erpdude says 4526 is allright for WinME without elaborating further. As a service pack for WinME is put together by the_guy who does not use WinME either I was just asking confirmation from erpdude that finally 4526 files aren't breaking PC Health on WinME. I use myself WinME but PC Health is deinstalled from my machine since a long time.

Can you explain the prophet bit please ? Prophets usually announce something to come so I cannot understand what you mean by calling Gape and MDGx prophets as they are not making announcements of events to come.

Link to comment
Share on other sites

-prophets: well, I was gonna call em win98se gods, but thought that was a little over the top... ;) And perhaps prophets was a bit overkill as well, tho not too far a stretch: they find stuff from newer ("the future") OS's/fixes and use em in old win98, as prophets would "find" info from future and use to improve things in the present... [ok, a stretch, but Prophets sounded nice at the time... of course, hadn't slept in 36 hrs, so was on fumes :P ]

...

-winME/4526: -I see, was thinkin of win98se, not ME... sry... -guess I'm still blocking-out acceptance of the fact that some people prefer to use ME... (I'm still traumatized by tryin to use ME when it first came out :realmad: , so I kinda skip over any mention of using it now... ;) ) -I guess if ya yank out all the junk that made it so crappy/unstable, then it could be worthwhile... to each their own...

>;]

Link to comment
Share on other sites

Timeline : Ole update 4526 is first posted by MDGx. Various problems are reported by several users. It is then spotted Oleaut32.dll is responsible for those problems. Then MDGx posts an updated Oleupdate 4526 with an Oleaut32.dll downgraded to version 4522. At this stage erpdude specifically asks a special Oleupdate for Windows ME with ALL files of version 4522 (post quoted by me above). Neither Gape nor MDGx are using WinMe as far as I know. At erpdude's request MDGx then posts a special Oleupdate for WinMe that contains only files of version 4522. Then a few days ago erpdude says 4526 is allright for WinME without elaborating further. As a service pack for WinME is put together by the_guy who does not use WinME either I was just asking confirmation from erpdude that finally 4526 files aren't breaking PC Health on WinME. I use myself WinME but PC Health is deinstalled from my machine since a long time.

Can you explain the prophet bit please ? Prophets usually announce something to come so I cannot understand what you mean by calling Gape and MDGx prophets as they are not making announcements of events to come.

actually, eidenk, I didnt check very well about the ole files. I had to double-check which versions of the OLE files i had installed.

at that time MDGx posted a OLE update 4522 for ME because I feared that OLE update 4526 might break some third party apps (which I think I didn't mention earlier). and I wasnt sure if Help and support center [NOT PC health] would work correctly with build 4526. after further testing and have installed OLE update 4526 on my ME computer, help & support works fine. still have yet to determine if it will or will not cause problems with the third party software I have on my machine.

I've sent Petr most of the ME fixes I've obtained for the past several months. at this point I have the ME Q276602 patch but I'm not going to send it because of a known problem. if you need the rest of the ME patches,

ask Petr for them.

Link to comment
Share on other sites

I think Help and Support Center is a part of PC Health as it went away when I uninstalled PC Health. Anyway thanks for those clarifications.

As for the new ME patches why not sending them to MDGx so that anyone can get them from his site ?

Link to comment
Share on other sites

Petr sent me the 260710, 268356, 277784, 278368, and the 304082 updates. These updates are not on that list. Would you like them sent to you?

You already have the 272620 and the 314417 updates posted.

the_guy

the_guy:

Thanks a lot for the offer, I already have them, Petr sent them to me too [thanx Petr].

Please see top post for updates, I just posted a bunch of WinME hotfixes:

http://www.msfn.org/board/?showtopic=46581

______________________________________________

at this point I have the ME Q276602 patch
erpdude8:

Could you send me a copy of WinME Q276602 patch at your convenience, please?

Many thanks in advance.

______________________________________________

eidenk:

I do have WinME installed, but it's avery old copy, with SR + PCH removed, so it's not that good for testing purposes.

I did install OLE update 2.40.4526 on WinME a while back, and it worked ok, as far as I can tell, but I have no idea if it affects SR or PCH functionality.

Edited by MDGx
Link to comment
Share on other sites

KB905915 IE CUMUL UPDATE -WinME- (12/8/05)

-MDGx: did ya forget to add this here? (I noticed your own site has it...)

Added on 12-15-2005 = please see top of topic. Edited by MDGx
Link to comment
Share on other sites

Could you send me a copy of WinME Q276602 patch at your convenience, please?

Many thanks in advance.

at this time, no. maybe in January 2006 if I determine the benefits of Q276602 pci.vxd fix for ME outweigh the risks. Q276602 for WinME has a known problem listed in Microsoft KB article 810447:

http://support.microsoft.com/kb/810447

however, if WinME users do not use multiple flash storage devices, then the Q276602 patch might be safe to install.

the last few weeks of Dec. 2005, I'm going to take a break for the holidays. I wont make any more posts after Dec. 20 until year 2006 begins. see ya after New Year's in 2006!

correction: about the "Microsoft Windows 98/98 SE HP Omnibook Portable Computer Docking Error VIP.386" fix. Vip.386 file version for Win98 FE/SP1 is 4.10.2003, not 4.10.2002.

Edited by erpdude8
Link to comment
Share on other sites

at this time, no. maybe in January 2006 if I determine the benefits of Q276602 pci.vxd fix for ME outweigh the risks. Q276602 for WinME has a known problem listed in Microsoft KB article 810447:

http://support.microsoft.com/kb/810447

however, if WinME users do not use multiple flash storage devices, then the Q276602 patch might be safe to install.

If not Q276602 then Q285882 should be correct, or not?

Petr

Link to comment
Share on other sites

Could you send me a copy of WinME Q276602 patch at your convenience, please?

Many thanks in advance.

at this time, no. maybe in January 2006 if I determine the benefits of Q276602 pci.vxd fix for ME outweigh the risks.

Isn't it usually best to let several people test components out, so that testing gets the benefit of a greater variety of setups?

Link to comment
Share on other sites

If not Q276602 then Q285882 should be correct, or not?

Petr

perhaps. but you will have to ask for Q285882 from Microsoft support.

It's important to note that the Win98 SE version of Q276602 (pci.vxd 4.10.2227) is safe to use while the WinME version of Q276602 (pci.vxd 4.90.3004) may cause problems. that goes to show you that one version of a patch is not always equal to the other version of the patch; bottom line, one version of a patch causes problems while the other version does not.

KB905915 IE CUMUL UPDATE -WinME- (12/8/05)

-MDGx: did ya forget to add this here? (I noticed your own site has it...)

Added on 12-15-2005 = please see top of topic.

________________________________________

UPDATED 12-15-2005

Please see top of topic for newest updates:

http://www.msfn.org/board/?showtopic=46581

UH-OH! speaking of IE Update KB905915, a Windows XP user has found problems with KB905915.

see here:

http://www.msfn.org/board/index.php?showtopic=62879

Edited by erpdude8
Link to comment
Share on other sites

MDGx:

your revised first post on the first page of this thread still mentions about the Win98 Vip.386 fix as the following:

"* Microsoft Windows 98/98 SE HP Omnibook Portable Computer Docking Error VIP.386 (build 4.10.2002 for Win98/98 SP1 + build 4.10.2227 for Win98 SE) Fix"

correct this to read:

"* Microsoft Windows 98/98 SE HP Omnibook Portable Computer Docking Error VIP.386 (build 4.10.2003 for Win98/98 SP1 + build 4.10.2227 for Win98 SE) Fix"

I'm going to take a nice break from the MSFN site. I'll be back after new year's 2006.

Edited by erpdude8
Link to comment
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.
×
×
  • Create New...