Jump to content

98 SE SP 3.32


Gape

Recommended Posts

The version of msvcrt.dll included in uSP is older then mine - I have 6.10.9359.0 - any particular reason to not include that in uSP?

A later version is included in the unofficial 932590 hotfix, which includes MSVCRT.DLL 6.1.9848.0 (from the Win2000 Q932590 hotfix):

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

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

MDGx lists it in this thread.

Link to comment
Share on other sites


The version of msvcrt.dll included in uSP is older then mine - I have 6.10.9359.0 - any particular reason to not include that in uSP?

Because of version consistency:

atl.dll - 3.0.9782

mfc42.dll - 6.0.9782

msvcirt.dll - 6.0.9782

msvcp60.dll - 6.0.9782

msvcrt.dll - 6.0.9782

Dated Feb, 2004.

Source.

If I include 6.1.9848 version of msvcrt.dll, I need to update to 6.1.xxxx versions of these files. Does anyone know latest 6.1.xxxx versions of these files ?

Link to comment
Share on other sites

I've installed this pack (SP 3.1 BETA 1), but when I go to Add/Remove it says that I have Unofficial Windows98 SE Service Pack 2.1a. Why so? During the installation, I kept some files which were recommended. Is this the cause? Then, do I need to reinstall it and let those files be overwritten?

By the way, does this pack have an animated boot logo? I only saw a splash screen when the computer was booting. Thanks for any reply.

Edit: I forgot to say that I installed SP 2.1a and RP7 before this pack. Some files it recommended to keep are:

File name: Advpack.dll

Description: ADVPACK

Your version: 6.00.2900.2180

File name: Comctl32.dll

Description: Common Controls Library

Your version: 6.00.2600.500

And Explorer.exe, Shell32.dll too.

Edited by Aloha
Link to comment
Share on other sites

I haven't had any problems yet, so I think I will keep these files. I'm not sure if any of them comes from RP7. I don't want to mess up with it at all. Whether the version is 2.1a or 3.0 beta 1, this SP was created by the same person, right? If reinstalling and overwriting these files can result in reinstalling RP7, I would rather not risk. Thanks for your reply, Fredledingue.

Link to comment
Share on other sites

x Removed WIN.INI sShortDate.

OH NO! I strongly disapprove of this, Gape. :(

BOTH the 2_4DATE.EXE file AND "sShortDate" are needed to make ALL programs that have date functions use the

"m/d/yyyy" format.

The "sShortDate=M/d/yyyy" in WIN.INI is used by 16bit programs like File Manager (WINFILE.EXE). File Manager does NOT use the date format settings from the Windows registry.

While the 2_4DATE.EXE file only updates the Windows registry to make only 32bit programs like Windows Explorer use the m/d/yyyy format. 2_4DATE does NOT make 16bit apps like File Manager use the 4-digit year date format. That's why "sShortDate" is still needed.

So you will need to put back WIN.INI sShortDate into the next beta release of the 98se SP.

Edited by erpdude8
Link to comment
Share on other sites

Also, All: there is newer msvbvm60.dll (6.0.97.98, kb930828) available, for example here. There is newer kb934602, but is is not available yet [i've tried to request it].

Forget it, Tihiy. KB934602 is another hotfix that has been "shortlived" and is no longer available from MS support anymore. I've tried requesting KB934602 myself a few weeks ago and MS doesn't have it anymore as what I've been told. Consider using KB930828 which should be mentioned at MDGx's web site.

OR better yet, try KB941029 which has 6.0.98.02 of msvbvm60.dll and MS KB article 941029 has keyword "kbhotfixserver" near the bottom of the article in the Keywords: section; one tell-tale sign that there may be a hotfix available for it. MS KB article 934602 doesn't have keyword "kbhotfixserver" on it.

Link to comment
Share on other sites

Success! Thanks.

I don't know if the CRLUPD.CAB gets applied.

x Removed WIN.INI sShortDate.

OH NO! I strongly disapprove of this, Gape. :(

BOTH the 2_4DATE.EXE file AND "sShortDate" are needed to make ALL programs that have date functions use the

"m/d/yyyy" format.

The "sShortDate=M/d/yyyy" in WIN.INI is used by 16bit programs like File Manager (WINFILE.EXE). File Manager does NOT use the date format settings from the Windows registry.

While the 2_4DATE.EXE file only updates the Windows registry to make only 32bit programs like Windows Explorer use the m/d/yyyy format. 2_4DATE does NOT make 16bit apps like File Manager use the 4-digit year date format. That's why "sShortDate" is still needed.

So you will need to put back WIN.INI sShortDate into the next beta release of the 98se SP.

@Gape... Do the whole 2_4date update or not. It's your call.

I use Office2000, Adobe, & other 90's vintage apps

on several 98SE computers, all with no problems.

All without the 2_4date update.

And with no issues I know.

--

If anyone doesn't know...

Applying the 2_4date update is equal to choosing

the Short Date Style -

MM/dd/yyyy -

in the Control Panel --> Regional--> Date tab.

This updates both the registry and win.ini.

--

Link to comment
Share on other sites

Hi guys [and gals],

Added links to SP2 3.0 Beta 1:

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

* Unofficial Windows 98 SE Service Pack 2 (SP2) installs ALL previously released Hotfixes, Patches + Updates (free):

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

- 98 SE SP2 3.0 Beta 1 Test [20.5 MB, English]:

http://www.mdgx.com/spx/SESP30B1.EXE

- 98 SE SP2 3.0 Beta 1 Test [18.6 MB, French]:

http://www.mdgx.com/spx/SP30B1FR.EXE

98 SE SP2:

http://exuberant.ms11.net/98sesp.html

Enjoy.

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