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

[erpdude8]

I'll test the unofficial Q926247 files on a Win95 + Winsock2 PC. I'll post the results later this afternoon.

doesnt work under Win95, EVEN with Winsock2 installed. Running SNMP.EXE from Q926247 under Win95+WS2 displays the "The SNMPAPI.DLL file expects a newer version of Windows. Upgrade your Windows version" error message. BOTH the snmp.exe and snmpapi.dll files from Q926247 will work properly under Win98 & ME.

Replace snmp.exe and snmpapi.dll with the versions from the Windows 95 Winsock2 update

NO DONT! MDGx already created the unofficial 314147 fix for Win95. The updated SNMP.EXE & SNMPAPI.DLL files from Win98's Q314147 update DO work properly under Win95.

Edited January 2, 2007 by erpdude8

[erpdude8]

also has Q926247 been tested under NT4?

never mind. it may not work on a NT4 OS

Edited January 2, 2007 by erpdude8

[soporific]

MDGX, regarding your latest Timezone hotfixes ...

Can I confirm with you that you now only need to install Q928388 and not also Q929120??

My testing revealed that absolutely nothing of value is installed with Q929120 when the latest version of Q928388 has already been done ... but I have been known to smoke a spliff or 6 so I could be hallucinating ...

and thanks as always for these unofficial hotfixes, it will soon be the case that auto-patcher has more unofficial hotfixes than the mouldy old official ones ... and better ones too!

[MDGx]

MDGX, regarding your latest Timezone hotfixes ...

Can I confirm with you that you now only need to install Q928388 and not also Q929120??

You're right.

As I said in this post:

http://www.msfn.org/board/?s=&showtopi...st&p=607811

The pair Q928388 + Q929120 [9x OSes] of patches and also

the pair KB928388 + KB929120 [NTx OSes] are respectively identical.

Take your pick, install the one you wish.

Italian users:

IT928388 installs also the fix from Q929120.

P.S.:

In the near future I'll delete one of them [probably the older KB number].

I'll also create another Italian IT929120 and will delete the older one [iT928388].

HTH

[soporific]

MDGx, regarding your new NUSB24.EXE ...

I've got it installing properly ... my code can differentiate between 23e and 24 ... but there's one teeny weeny little problem ... it prompts if the USER wants to reboot even when I use the /Q:A /R:N switches .... so it can't go into auto-patcher yet ... but I want to release v1.8 very soon !!! Can you look into this?

Cheers mate.

PS - thanks for the info about the Timezone updates --- your notes did say that was the case I was just being a bit paranoid and wanted to be sure.

[erpdude8]

Fixed INF uninstall code:

* Unofficial Windows ME 2-4 GB Files Errors KERNEL32.DLL 4.90.3001 Fix:

http://support.microsoft.com/?id=318293

Direct download [324 KB]:

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

More info:

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

Fix below here:

http://www.mdgx.com/web.htm#9SU

and here:

http://www.mdgx.com/web.htm#W98

Fixed INF uninstall code:

* Unofficial Windows 98/98 SP1/98 SE 2-4 GB Files Errors KERNEL32.DLL (4.10.2002 for Win98/98 SP1 + 4.10.2226 for Win98 SE) Fix:

http://support.microsoft.com/?id=318293

Direct download [347 KB]:

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

More info:

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

WARNING: PLEASE DO NOT RE-INSTALL OR RERUN COPY2GB.EXE/C2GBME.EXE files if these updates are ALREADY installed!!!!! I did this and they rendered my Win98 & ME systems unusable & unbootable, initiating an automatic shutdown after startup (AND the updated KERNEL32.DLL file was NOT copied after the original KERNEL32.DLL file was renamed!)

I had to put in a Win98 boot disk on my Win98se machine and rename KERNEL32.ORI back to KERNEL32.DLL in DOS mode to get the PC running again [same with the WinME computer].

If you REALLY NEED to re-install these patches, UNINSTALL them first, reboot and then RERUN the patches!!

MDGx, can you address this FATAL problem with the COPY2GB.EXE & C2GBME.EXE patches?

Edited January 8, 2007 by erpdude8

[erpdude8]

MDGx, can you address this FATAL problem with the COPY2GB.EXE & C2GBME.EXE patches?

scratch that. I've just revised the C2GBME.INF, COPY2GB.INF, FE.INF & SE.INF files to deal with this problem. I'll send you the updated INF files. the updated KERNEL32.DLL files will now be copied as KERNEL32.NEW to the Windows\System folder and the INF files will make WININIT rename the old kernel file [from kernel32.dll to kernel32.ori] and WININIT will also rename the new kernel file [from kernel32.new to kernel32.dll] - all this according to the revised INF files. this will ensure the old kernel file gets renamed AND the new kernel file gets renamed from kernel32.new extension to kernel32.dll, even when re-installing the Copy2Gb Kernel32.dll fixes

Edited January 8, 2007 by erpdude8

[Drugwash]

How many levels of installing/uninstalling would this system allow? Would it also take into account broken (interrupted/unfinished) installations/uninstallations?

I'm asking because with all these power/ultra/super/extra/etc-packs, there might be a chance of multiple installation of the same patch, which might wreak havoc as is or while trying to uninstall (if needed).

[soporific]

MDGx, can you address this FATAL problem with the COPY2GB.EXE & C2GBME.EXE patches?

scratch that. I've just revised the C2GBME.INF, COPY2GB.INF, FE.INF & SE.INF files to deal with this problem. I'll send you the updated INF files. the updated KERNEL32.DLL files will now be copied as KERNEL32.NEW to the Windows\System folder and the INF files will make WININIT rename the old kernel file [from kernel32.dll to kernel32.ori] and WININIT will also rename the new kernel file [from kernel32.new to kernel32.dll] - all this according to the revised INF files. this will ensure the old kernel file gets renamed AND the new kernel file gets renamed from kernel32.new extension to kernel32.dll, even when re-installing the Copy2Gb Kernel32.dll fixes

This was the exact reason i made an installer for an older version of Copy2Gb --- to account for those trying to re-install it. Well, to be completely honest, to account for ME trying to needlessly re-install it and breaking my boot routine (can't find kernel32.dll) -- I should have made a bigger song and dance about it at the time, you may have been able to use some of my batch code.

Edited January 9, 2007 by soporific

[MDGx]

UPDATED · 1-9-2007

Added to 1-9-2007 UPDATE:

VML Fix here:

http://www.mdgx.com/ietoy.htm#VGX

* Unofficial Internet Explorer 5.5 SP2/6.0/6.0 SP1 for Windows 98/98 SP1/98 SE/ME Vector Markup Language (VML) VGX.DLL Security Vulnerability Fix:

http://www.microsoft.com/technet/security/...n/ms07-004.mspx

Direct download [1.06 MB]:

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

This Fix replaces obsolete IE925486.EXE.

Enjoy.

[erpdude8]

hey everyone. I'm back from jury duty. what a weird way to start off year 2007 by doing jury duty!

note to Drugwash and soporific: download the updated COPY2GB.EXE file from MDGx's web site. The install/uninstall problems have been fixed.

The C2GBME.EXE kernel32.dll fix for WinME will need to be revised again to include the START.EXE file (and a "START /W NIRCMD" string in the C2GBME.INF file). I was not sure if the NIRCMD.EXE file was executed on older & current releases of C2GBME.EXE. perhaps many instances of NIRCMD were executed too quickly.

[Drugwash]

Welcome back, erpdude8. Sorry to hear about a bad start off; hopefully you'll get over it soon. And thanks for the heads up, will download the updated COPY2GB.EXE right away.

@ MDGx: VS6SP6U.EXE dated 28 Nov 2006 at your site is rebooting on finish without warning; you may wanna revise it when possible.

[MDGx]

Drugwash:

VS6SP6U.EXE dated 28 Nov 2006 at your site is rebooting on finish without warning; you may wanna revise it when possible.

I have deleted all INF + SED reboot directives [the rest is up to the advanced setup APIs], please try it again:

Unofficial VS6 SP6 Runtime + ActiveX Controls Libraries (DLLs) for Windows 98/98 SP1/98 SE/ME [2.11 MB]:

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

Thanks for your feedback.

HTH

[Drugwash]

Regarding newest DST update package: how would one go around clicking OK in an unattended installation? Any commandline switch for that? I'm thinking about projects such as auto-patcher and similar, which would incorporate this update.

Sorry if I'm out of track.

[MDGx]

Regarding newest DST update package: how would one go around clicking OK in an unattended installation? Any commandline switch for that? I'm thinking about projects such as auto-patcher and similar, which would incorporate this update.

Sorry if I'm out of track.

Unfortunately I don't know of a way to click OK in an unattended installation for the new Time Zone updates.

Workaround:

But who wants to make an unattended install, needs to add this command line to tte batch/inf/whatever file after the

Q929120.EXE /Q:C /R:N

or similar line:

RUNDLL32.EXE SHELL32.DLL,Control_RunDLL TIMEDATE.CPL

and then instruct the user to click OK in the "Date/Time Properties" dialog box.

Also, for this to work unattended, the SED file [i named it VS6SP6U.SED] needs to *NOT* have the BOLD line:

[Version]Class=IEXPRESS

SEDVersion=3

[Options]

PackagePurpose=InstallApp

ShowInstallProgramWindow=1

HideExtractAnimation=0

UseLongFileName=0

InsideCompressed=0

CAB_FixedSize=0

CAB_ResvCodeSigning=0

RebootMode=N

InstallPrompt="Install %FriendlyName%?"

DisplayLicense=%DisplayLicense%

FinishMessage=%FinishMessage%

TargetName=%TargetName%

FriendlyName=%FriendlyName%

AppLaunched=%AppLaunched%

PostInstallCmd=%PostInstallCmd%

AdminQuietInstCmd=%AdminQuietInstCmd%

UserQuietInstCmd=%UserQuietInstCmd%

SourceFiles=SourceFiles

TargetNTVersion=0:%OSWarn%:OK

[strings]

OSWarn="This Update canNOT install on your Windows Operating System!"

DisplayLicense=C:\TEMPINST\Q929120.TXT

FinishMessage=

TargetName=C:\TEMPINST\Q929120.EXE

FriendlyName="Unofficial Windows 95/98/ME 2007 Daylight Saving Time (DST) Time Zone Update"

AppLaunched=Q929120.INF

PostInstallCmd="RUNDLL32.EXE SHELL32.DLL,Control_RunDLL TIMEDATE.CPL"

AdminQuietInstCmd=Q929120.INF

UserQuietInstCmd=Q929120.INF

FILE0=Q929120.INF

[sourceFiles]

SourceFiles0=C:\TEMPINST\

[sourceFiles0]

%FILE0%=

;

The line above must be replaced with this one:

PostInstallCmd=<none>

Then the Q929120.EXE installer must be recompiled with the modded SED file [example]:

IEXPRESS.EXE /N C:\TEMPINST\VS6SP6U.SED

Edit:

P.S.:

If any1 needs the text file [Q929120.TXT] to recompile the installer:

Unofficial Windows 95/98/ME 2007 Daylight Saving Time (DST) Time Zone Update

EXTREMELY IMPORTANT:

At the end of this installation you MUST confirm your Time Zone selection:

When you see Date/Time Properties -> you MUST click OK.

This Update installs *both* 2007 Daylight Saving Time (DST) Time Zone Updates:

- Western Australian (Perth):

MicroSoft Knowledge Base (MSKB) Article Q929120:

http://support.microsoft.com/?id=929120

- and U.S.A.:

MicroSoft Knowledge Base (MSKB) Article Q928388:

http://support.microsoft.com/?id=928388

and also deletes *obsolete* 2006 Australian (Melbourne Commonwealth Games) Daylight Saving Time (DST) Time Zone Update registry entries (if any):

MicroSoft Knowledge Base (MSKB) Article Q909915:

http://support.microsoft.com/?id=909915

How to Configure 2007 U.S.A. DST:

http://support.microsoft.com/?id=914387

Preparing for 2007 DST Changes:

http://www.microsoft.com/windows/timezone/dst2007.mspx

MSFN DST Forum:

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

The text file can be modified for unattended installs:

remove the "EXTREMELY IMPORTANT:" section.

HTH