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

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

-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 ]
...
-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 , 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...
>;]

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.

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 ?

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
______________________________________________

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.

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.

-oops, one old link at the top of topic needs updating:
"12-15-05: - Unofficial MS IE 5.5 SP2 Patch for Windows 98/98 SE [3.07 MB]:
http://www.mdgx.com/files/IE896688.EXE..."
...
-s/b IE905915.EXE

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.

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

Petr

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

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.



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

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.

erpdude8:

I have updated Windows ME PCI.VXD fixes:

* Microsoft Windows ME PCMCIA Adapter Code 10 Device Manager Error PCI.VXD build 4.90.3004 Fix:
http://support.microsoft.com/?id=276602
Direct download [175 KB, English]:
http://www.mdgx.com/files/ME276602.EXE
BUG: Long Delay With Multiple Flash Memory Storage Devices after installing PCI.VXD 4.90.3004 Fix:
http://support.microsoft.com/?id=810447
FIX: MUST install OLDER PCI.VXD 4.90.3003 Fix below IF using more than 1 Flash Memory Device/Drive!

* Microsoft Windows ME Standby Hang With Multiple MS-DOS Prompt Sessions PCI.VXD build 4.90.3003 Fix:
http://support.microsoft.com/?id=285882
Direct download [173 KB, English]:
http://www.mdgx.com/files/ME285882.EXE

a belated happy new year 2006, MDGx. can you package the Win95/IE HTML Help v1.33 build 4.74.9273 addon into IExpress/Wextract? the current HHUPD95.EXE file will NOT work when running it directly from a write-protected floppy disk or a CD disc; the HHUPD.EXE and HHUPDNT.EXE files, on the other hand, do work on write-protected floppies and CD discs because those two HTML Help EXE installers extract files to a temp folder while HHUPD95.EXE does NOT; HHUPD95.EXE extract files on the current folder where HHUPD95.EXE is stored. I'll check back in a few days if HTML Help v4.74.9273 (hhupd95.exe) is created from IExpress/Wextract.

I'll also send you my unofficial DCOM95 Update pack for Win95 & unofficial DCOM98 Update pack for Win98 which includes the imagehlp.dll file from WinME and iprop.dll file from NT4 SP6a. Both of the imagehlp.dll and iprop.dll files I mentioned work under Win9xME. Please post up the unofficial DCOM update packs on your site ASAP.

also, take note that installing WMI 1.5 under Win95 requires DCOM 95. If DCOM95 is not installed under Win95, the WMI 1.5 installer will refuse to install the WMI files.

HNY 2 u 2.

I have repacked HHUPD95.EXE [HTML Help 1.33] with iexpress [696 KB]:
http://www.mdgx.com/files/HHUPD95.EXE
posted here:
http://www.mdgx.com/add.htm#HHU
and here:
http://www.mdgx.com/web.htm#HH95

I got the DCOM95 update from you a few days ago, but didn't have time to look at it yet.
If you wish to send [newer] DCOM95 + DCOM98 updates, please go ahead. I'll get to them as soon as I can.

I have added a DCOM95 warning for Win95 users who want to install WMI:
http://www.mdgx.com/add.htm#WMI

BTW:
I looked at IPROP.DLL you sent [from WinNT4 SP6a] with DCOM95 update, and compared with IPROP.DLL from WinME setup CD [the 1 I use with Win98 SE] using GETVER.EXE:
IPROP.DLL NT4 SP6a = 4.0.1381.326 11-18-1999 96016 Bytes
IPROP.DLL WinME CD = 4.0.1381.4 6-8-2000 110592 Bytes
Looks like the 1 from WinME is newer and byte size is larger, but I got no idea if code works better with 9x OSes [?].

Hope this helps.

Posted unofficial patches [by anonymous developer] for:
- Windows 98 FE (First Edition)
- Windows 98 SE
- Windows ME
to fix the Security Vulnerability described in MS06-001 Security Bulletin:
http://www.microsoft.com/technet/security/...n/ms06-001.mspx
This exposes Win98 (FE)/98 SE/ME computers to *critical* security risk when a malware WMF [Windows Metafile Format] file is accessed from the internet [embedded into web page], due to a flaw in Windows graphical rendering engine [GRE].
These patches replace GDI32.DLL + GDI.EXE from %windir%\SYSTEM [usually C:\WINDOWS\SYSTEM] with newer versions [click links below to download patches]:
- GDI32.DLL + GDI.EXE 4.10.2003 for Win98 FE:
http://www.mdgx.com/web.htm#9SU
- GDI32.DLL + GDI.EXE 4.10.2226 for Win98 SE:
http://www.mdgx.com/web.htm#9SU
- GDI32.DLL + GDI.EXE 4.90.3002 for WinME:
http://www.mdgx.com/web.htm#MEU

Patch author's explanation:

BTW:
The author told me to post these patches without asking for beta testing, because...

Hope this helps.

Just a note:
GDI.EXE contains the following note:


Petr

That's a personal note from the author of the patch.
But the author told me to post this patch without asking for beta testing, because...


Hope this helps.

Hi MDGx,

could you ask the author of the patch to patch also the files for Windows 98 Gold, i.e. version 4.10.2002? They are contained in this fix: http://www.winpack.org/petr/98/289635USA8.EXE

Petr

hopefully the author should patch the ones from Win98 Gold ASAP.

so Petr, have you worked on getting the KB828028 hotfix for Windows ME? please respond as soon as you obtain the WinME kb828028 patch.

note to MDGx about D3DIM700.DLL build 4.7.0.723 Fix for ME; this fix is included in DirectX 8 and higher. May want to put "DirectX 8 and higher include D3DIM700.DLL fix". Or put "DirectX 9.0c installs newer D3DIM700.DLL file build 4.09.00.0902."

-MDGx: re: 1/9 fix:
"* Microsoft Windows 98/98 SE MSASN1.DLL build 5.00.2195.6824 Security Vulnerability Fix"

-uh oh...

-I already had a newer ver. of MSASN1.DLL (5.0.2195.6905), and that 1/9 fix of yours renamed it to msasn1.qfe, but it did NOT replace it with anything... I had NO msasn1.dll in windows/system anymore, and that broke winUpdate... (among other things, I'm sure)...

...as soon as I renamed it back, winUpdate worked again...
???

[-EDIT: the specific winUpdate error was 0x80070485, supposedly relating to CABINET.DLL, and recommending to reinstall windows installer, but my cabinet.dll file was fine, and following the (annoying) MS instructions for "properly" reinstalling winInstaller of course didn't fix the error...]

MDGx:

The unofficial WinME Gdi.exe/Gdi32.dll v4.90.3002 patch did not work.
Even though I shut down Stmgr.exe with either Coolkill or Winkill
and ran the WinME patch & rebooted, I got message "Windows detected
and repaired inconsistencies in some of your system files. Before
these repairs can take effect, Windows must be restarted.
Do you want to restart Windows now?"

Looks like WinME's SFP feature ran at startup and saw the wininit.log
file (NOT wininit.ini file) referencing the gdi.exe and gdi32.dll files
and restored the older GDI files after a Windows restart. You have
to prevent Stmgr.exe from loading at startup (from Msconfig) and then
run the unofficial WinME GDI patch for it to work just right.

In order for the unofficial WinME Gdi.exe/Gdi32.dll 4.90.3002 patch
to really work, you MUST disable System Restore, shut down Stmgr.exe AND
disable the SFP [Statemgr] Startup entry by running System Configuration
Utility [msconfig.exe], click on Startup tab and uncheck Statemgr
and click on OK; dont reboot yet. Now run the unofficial WinME kb912919
patch, and after WinME loads, delete the wininit.log (NOT the wininit.ini)
file from the Windows folder. If you dont delete the wininit.log file and
you re-enable SFP [or run Statemgr.exe or Stmgr.exe], the dialog box
saying "Windows detected and repaired inconsistencies..." will appear and
restore the older Gdi.exe and Gdi32.dll files. So before re-enabling
WinME's SFP feature, delete the wininit.log file first.

Please post up these instructions on how to really get the unofficial
WinME Gdi.exe/Gdi32.dll 4.90.3002 patch to work.

Also the two GDI files from unofficial Win98se 4.10.2226 Gdi.exe/Gdi32.dll fix
have the wrong version dates. They should be dated 1/6/2006
instead of 10/4/2005.

Good that you posted both the WinME pci.vxd 4.90.3003 and 4.90.3004 fixes and
that you listed the problem the pci.vxd 4.90.3004 fix causes.
I was a little ticked off that you first posted the pci.vxd v4.90.3004 Q276602 fix w/out listing the problem that it causes. You know better not to prematurely
post up patches that have problems and not list the problems. Hopefully you won't commit any kind of mental blunder like that again.




PsycoUnc,

The 1/9 MSASN1.DLL 5.00.2195.6824 fix is NOT exactly MDGx's even though it is listed at the MDGx site. That patch was from Microsoft. Microsoft created the MSASN1.DLL 5.00.2195.6824 fix for Win98, NOT MDGx.

There may be a incorrent checksum in file(s) or file(s) is in HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\SessionManager\WarnVerDLLs (CheckVerDLLs).

I will ask.

BTW:
This fix is also available here:
http://ftp.isu.edu.tw/pub/CPatch/msupdate/.../289635usa8.exe

Done.

MSASN1.DLL Q828028 fix is not by me, it was obtained by Petr from Microsoft.
I am aware that it is older than MSASN1.DLL from Gape's SP2 2.1a, but Q828028 is the only one available for separate install.

Please notice that all patches at my site which start with Microsoft are official patches from MS.
Similarly, all patches at my site which start with Unofficial are unofficial patches by me or by others.

Hope this helps.

I have updated the WinME GDI patch installation instructions:
http://www.mdgx.com/web.htm#MEU

The patch author date-stamped the GDI files for Win98 SE. I do not know the reason why.

Hope this helps.

The unofficial IE Q896688 patch was created by a concerned user, it is not official from Microsoft, therefore I cannot update it whenever MS updates their official IE cumulative patch.

But recently I have received the newer unofficial IE905915 patch from the author, and I'll post it as soon as I can at my site.

Hope this helps.

I have reproduced the error you mention when trying to install MSASN1.DLL from Q828028.
After reboot, all I have in %windir%\system is MSASN1.QFE [the newer build 5.00.2195.6905 from Gape's SP2] and no DLL.
I had to rename it back to MSASN1.DLL to make it work.

Therefore I have added a warning:

* Microsoft Windows 98/98 SE MSASN1.DLL build 5.00.2195.6824 Security Vulnerability Fix:
http://www.microsoft.com/technet/security/...n/ms04-007.mspx
Direct download [166 KB, English]:
http://www.mdgx.com/files/Q828028.EXE
More info:
http://erpman1.tripod.com/current/asn1fix.html
Do NOT install this Fix IF already installed Unofficial Windows 98 SE SP2:
http://exuberant.ms11.net/98sesp.html
which installs newer MSASN1.DLL build 5.00.2195.6905!

Hope this helps.

New MS06-002 KB908519 update is available.

Direct download:

Windows98-KB908519-ENU.EXE
Prerequisities: Windows 98 or 98SE, IE 5.5 SP2 or newer

WindowsME-KB908519-ENU.EXE
Prerequisities: Windows Me, IE 5.5 SP2 or newer

Contains
File: T2EMBED.DLL
Size: 163,600 bytes
Date: 24-Nov-2005 16:54
Version 5.00.2195.7073

The same file for 98FE, 98SE, ME and for all languages.

Petr

I've gotten the KB905819 T2EMBED.DLL updates for Win98/ME. however, Microsoft made one minor boo-boo in the KB905819.inf file. Here's where MS messed up in the INF file:

---------
;qfecheck
HKLM,%UpdateKey%\%SPKey%\%LocaleID%%UpdID%\,,,"%UpdName%"
HKLM,%UpdateKey%\%SPKey%\%LocaleID%%UpdID%\,,,"%UpdName%"
HKLM,%UpdateKey%\%SPKey%\%LocaleID%%UpdID%,%10%\t2embed.dll,,"5.0.2195.7073"
---------

It should be:
HKLM,%UpdateKey%\%SPKey%\%LocaleID%%UpdID%,%11%\t2embed.dll,,"5.0.2195.7073"

%10% points to Windows folder while %11% points to Windows\System folder.

So if you view the Q905819 update in QFEcheck it will say:
"Tmembed.dll 5.0.2195.7073 NOT FOUND"

I opened Regedit and go to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Updates\WinME\UPD908519
it says:
C:\WINDOWS\t2embed.dll 5.0.2195.7073

change C:\WINDOWS\t2embed.dll to C:\WINDOWS\SYSTEM\t2embed.dll and QFECheck will find the "missing" t2embed.dll file.

---
and I'm still waiting for Petr to obtain the WinME version of the KB828028 patch. I thought it would be easy for him to ask for ME kb828028 from MS, just like it was easy for him to ask for the W98 kb828028 patch. what's the hold up?

I posted something related to this subject here:
http://www.msfn.org/board/?s=&showtopic=65...ndpost&p=447938

Here is the answer from the author of the GDI/WMF patches:
________________________________________

Here is the answer from the author of the GDI/WMF patches:
Hope this helps.

I don't suppose to ask MS for this patch, MS has sent to me too many patches already.

I also don't suppose that it could contain anything usuful (if exists at all). mesp202en-a3 contains msasn1.dll version 5.00.2195.6905 white KB828028 (W98) contains 5.00.2195.6824 and KB828028 (W2K) 5.00.2195.6823.

Petr

Which of the unofficial patches work best on a 98SE2ME installation that was haX0red with Tihiy's Revolutions 4.0 pack?

Probably all of them [in theory], because as far as I know none of the files updated by the unofficial patches replace Tihiy's RP files.
But I haven't experimented this yet.

Tihiy may have more details about this subject.

Hope this helps.

<sarcasm>
Format C:
</sarcasm>
Seriously, you should look for patches that may improve system stability, but it is unsafe to install 98SE2ME or patched system files (user*,gdi*,shell*,kernel*) over RP4 due to its architecture.

I think you misunderstand...

I install 98SE2ME, THEN your Revolutions Pack...

NOW I want to patch WMF vulnerability.

NOT reinstall 98SE2ME over RP4.

--but hey since you say RP will not help my system and think it is so bad I should reformat; then I will do that.

[shouts to the whole world] Hey everybody even Tihiy says his RP is crap!


Or did I misunderstand you like you misunderstood me?

--iWindoze

I've said:
So: you better should not install WMF patch because it installs updated gdi* files.
Please post next time with RP (Lite) questions to RP (Lite) thread.
P.S. RP4 is crap. Powerful crap.

Hi!
I would just like to know if there would be anyone who would have downloads that includes all the fixes to upgrade Win95b to Win95C?
Likewise, has there been a final version for an unofficial WinME SP?
Any assistance would be greatly appreciated.
Thanks!
-KIKI-

nope. there's no final release of the unofficial WinME SP, yet Kiki. it will be a while before that since it is in alpha 3 stage and hasnt reached beta. come back in a couple of months for the unofficial WinME SP. maybe by middle of March of this year (or in early Spring) there might be at least an RC (release candidate) version of WinME service pack.

Win95 C isnt much different from Win95B; win95c = win95b + osr2.1 usb supplement update w/ some registry changes.

Okay I see it

I'll be moving my parents to eiher Win2000 or Linux come my next visit home. Id rather do Win2000 than Linux for the simple reason that Linux needs too many updates and on dial up they're a real pain. You better get on with that Windows 2000 pack, right? unless that's some powerful crap too?

Thanks for the answers though.

-iWindoze

PS: powercrap and lack of updates is why I'll be moving them to 2000 (in case anyone was about to ask me why I'd do that...)

OH boooooo! BOOOOOOOO! booooo! BOOOOOOO!
<the crowd in my mind is BOOing at Petr for not attempting to ask microsoft support for thw winme Q828028 hotfix>

Then the way you requested for the Win98 Q828028 hotfix from microsoft support by email with "no problems" was a FLUKE! A stroke of LUCK! Then how do I really know that it was easy to ask for the Q828028 patches from MS support. what is your secret? I know I had a hard time asking for Win98 Q828028 patch by email several times and I just kept getting convoluted, circuitous responses.

i'm getting a little suspicious...

some Win9xME users prefer the Microsoft patches instead of "unofficial" patches because they are uncomfortable with unofficial solutions. And I get that.

unfortunately, the WinME install instructions ARE STILL NEEDED as the revised ME912919.EXE file that included the Nircmd.exe file to kill SFP, System restore, Vxdmon etc., DID NOT WORK properly under my WinME computer SAD!

it still generated that "Windows detected and repaired inconsistencies..." error message after reloading WinME & after installing ME912919 w/ Nircmd.exe file. I think the patch installed the updated GDI files to soon (or should I say "too quickly") before Nircmd had a chance to finish. The patch should WAIT until Nircmd finishes shutting down, SFP, system restore & Vxdmon and THEN install the updated files. AND note that the WININIT.LOG file is created AFTER rebooting & reloading WinME desktop, NOT right after installing the ME912919 patch.

MDGx told me it worked on a clean ME OS on his test machine. But it's a completely different story on my WinME computer and on my relative's WinME computer, both of which are slower than the one MDGx has. Looks like ME912919 doesnt work well on slow computers.

I have created .INF files that fix the "T2EMBED.DLL Fix Installer Error" problems under Win98 & ME. I have also created an .INF file that fix the "NWNP32.DLL Fix Installer Error" problem after installing the IPF Error Nwnp32.dll fix under Win95 osr2 and Win98 FE/Gold. I have sent these .INF files to MDGx and should post up these fixes as soon as possible. MDGx should also mention that the Nwnp32.dll FIX requires either MS Client for Netware Networks or Novell Netware v3.x/4.x Client to be installed in order for the Nwnp32.dll patch to really work & install the updated file.

ok MDGx. I have obtained the newer ME912919.EXE patch. It properly shut down SFP, system restore and Vxdmon and installed the updated GDI files after waiting for Nircmd to finish shutting down SFP/system restore. It no longer prompted the "Windows has found and repaired inconsistencies..." message after restarting the ME machine BUT the "You must restart the computer..." message popped up after reboot. And when I restarted the computer the second, third, fourth times, the Restart Computer message kept on popping up. And I noticed the wininit.ini file was still there in the Windows folder. I had to delete the wininit.ini file manually after the second or third time I rebooted when I ran ME912919.EXE again. Hopefully this will be fixed in V4 of ME912919.

Also, you may want to create a separate Unofficial HTML Help 5.20.3790.2453 patch just for WinME that will include the NIRCMD file (and call it HHUPDME.EXE). Ditto for Unofficial OLE Automation 2.40.4526 Update for WinME with the inclusion of NIRCMD file (and call that one OLEUPME.EXE).

AND I am NOT going to change my opinion on this until the WinME kb828028 msasn1.dll hotfix has been obtained (either by Petr, me or someone else) from MS. so far, Petr has not responded to this yet.

...getting even MORE suspicious on how Petr got the Win98 KB828028 patch. I no longer believe him when he emailed me a few weeks ago saying he got this patch with "no problems" from MS. I can only speculate he got it by other means.

Hello MDGx,

may I know why you have used the old crypt32.dll from Q329115 and not the new one from Q835732?

Petr

Because of different CRYPT32.DLL builds:

- Q329115 = 5.131.2133.6 = newer [but older date 9-12-2002]
- Q835732 = 5.131.1880.14 = older [but newer date 1-23-2004]

I have used the newer build.

P.S.:
Have you tested this new CRYPT9X.EXE on your 9x computer(s)?
Please let me know if it doesn't work ok.
Thanks.

I think that 5.131.1880.xx are for Windows 98 and WinNT and 5.131.2133.xx version is for Windows ME.

5.131.1880.14 is much newer build with fixes not implemented in 5.131.2133.6 and therefore I'd recommend this newer fix for Windows 98 and Windows 98 SE, and older 5.131.2133.6 for Windows ME because according to erpdude8 posts there is no Q835732 crypt32.dll file that would work on Windows Me.

Sometimes the file date is modified and does not reflect the real date when it was built, but for PE executables you can find the build date/time in the PE header and for these files it is the same as file date-

Petr

I've made a CRYPT9X patch of my own that has the latest crypt32 files for Win98, plus the latest msasn1.dll file from NT4 835732 patch. The CRYPT9X.EXE file should only be used under Win95/98 and NOT under ME.

Petr, I wonder if you would mind emailing Czech MS support for Hotfix 828028 for Windows ME. Looks like they seem to be more intelligent than the ones from the english MS email support address and know more of the 828028 hotfixes for win98/me. thanks for the email you sent me.