MSFN Forums > 98 FE + 98 SE + ME updates + patches + (hot)fixes

bristols

Oct 23 2007, 04:52 PM

QUOTE (RetroOS @ Oct 21 2007, 09:59 AM)

Even moderators need holidays!

That might explain why the latest unofficial 9x IE6 and OE6 updates haven't shown up?
They've probably already been compiled, but haven't been posted anywhere...
Afterall, MDGx is the updates collector man!

I noticed and decided to post about the fact that MDGx continues to update his own site with new and revised hotfixes:

- check bottom of the home page: "Site UPDATED October 23 2007"
- check the dates next to the first three updates under the heading "Free Updates + Patches" on the home page, which include the latest unofficial IE6 Cumulative Update for 98/98SE.

I'm not sure whether or not he wants the information posted here (otherwise why not post it himself?). I can only guess that he is not against us downloading the updates, because he has taken the trouble of compiling them and making them available on his own site.

MDGx

Oct 24 2007, 01:36 AM

UPDATED · 10-24-2007

Hopefully all install/rename INF problems should be resolved.

Please test these updated patches, and let me know:

ITOLEUP.EXE - Italian
OLEUP.EXE
KB891711.EXE
Q891711.EXE
Q891711F.EXE - French
Q891711I.EXE - Italian
RICHED9X.EXE
ITSHELME.EXE - Italian
SHELL98.EXE
SHELL98F.EXE - French
SHELL98I.EXE - Italian
SHELL98P.EXE - Polish
SHELLME.EXE
ME918547.EXE
Q918547.EXE
KB918547.EXE

All others are English.

BTW:
I need a volunteer to translate the text files from English to Polish = SHELL98P.EXE.
PM me if you want to do this. Thanks.

Enjoy.

P.S.:
I'll be waiting for more feedback on the new Xeno86 VACHE.VXD patch for 98 SE.
I'll build an installer if it works for most testers.

RetroOS

Oct 24 2007, 01:39 AM

MDGx, nice to see you around again.
It's amazing how everything seems to slow down when you're not posting.
You must be the motivator as well as the moderator!

Good to see those 9x updates rolling on.

The Dream Lives!

MDGx

Oct 24 2007, 02:47 AM

Many thanks for your kind appreciation.

I hope to keep you guys busy for the next few days testing all those updates.

bristols

Oct 24 2007, 07:37 AM

Welcome back MDGx, and thanks as always for the updates.

RetroOS

Oct 25 2007, 12:08 AM

Has anyone tested Sun Java 1.6.0_03 on Windows 9x? (Yes, it does work)
The installer claims that it is best on a newer OS but does not claim it will not work!
I've been running it for about a week.
It appears faster and more stable than 1.5.0_13.
No problems so far with IE6 and Firefox...

Anyone else had experience with Java 6 on 9x?

Analada

Oct 25 2007, 09:31 AM

QUOTE (RetroOS @ Oct 25 2007, 12:08 AM)

Has anyone tested Sun Java 1.6.0_03 on Windows 9x? (Yes, it does work)
The installer claims that it is best on a newer OS but does not claim it will not work!
I've been running it for about a week.
It appears faster and more stable than 1.5.0_13.
No problems so far with IE6 and Firefox...

Anyone else had experience with Java 6 on 9x?

Yes it works well for me on firefox.

I'd like to get the enhanced ("unlimited") security files. Evidently they can be downloaded with the JDK (java development kit) but haven't yet found them. What is installed is limited 128 bit encryption.

It's probably a good idea to go with this version as it has fixed some security bugs.

dencorso

Oct 27 2007, 01:57 AM

Hi, MDGx!

Now that you're back, let me please direct your attention to two subjects I believe will interest you.

1)Random occasional lock-ups due to CNTRL98 (updated Win 98 SE CONTROL.EXE v4.10.0.1999) update: see this post by fastlanephil and the second post following it, by myself. I believe CONTROL.EXE v4.10.0.1999 needs revision. But, unfortunately, all I can report about the lock-ups is that they are haphazard and occur for no apparent reason.

2) My own USB FDD DiskTSD.VxD 4.90.0.3000 Patch, to allow NUSB to work with FDDs without eliciting a BSOD!

Petr's findings (as quoted in my post) indicate there might be problems in incorporating it to 98SE3ME, so, please, do test it in this context. Also, the principle underlying this patch is pretty general, and might allow the use of other Win ME VxDs in Win 98SE. But among those that always crashed Win 98SE, which do you think would be the most worthy of investigation? Please advise.

bristols words also represent my own feelings exactly, so:

QUOTE (bristols @ Oct 24 2007, 10:37 AM)

Welcome back MDGx, and thanks as always for the updates.

Added on October 31st, 2007 - 01:09 AM: I confirm that the selfsame patching strategy applies to other files, as it has enabled me to have the following Win ME files running on my Win 98SE system, up to now without any detectable problems:

DISKTSD.VXD v. 4.90.0.3000
DISKVSD.VXD v. 4.90.0.3001
CDTSD.VXD v. 4.90.0.3000
CDVSD.VXD v. 4.90.0.3003
SMARTVSD.VXD v. 4.90.0.3000
and with a slightly modificated version patching
VNETBIOS.VXD v. 4.90.3000 (since Nov 10th 2007)

fastlanephil

Oct 28 2007, 04:37 AM

QUOTE (MDGx @ Oct 24 2007, 01:47 AM)

Many thanks for your kind appreciation.

I hope to keep you guys busy for the next few days testing all those updates.

Welcome back!

{Whistling tune to Welcome Back Kotter)

MDGx, if you get a chance, I am very interested in what you think about this issue in Win 98 SE - ME:

QUOTE (fastlanephil @ Oct 16 2007, 02:04 AM)

QUOTE (fastlanephil @ Oct 14 2007, 01:16 PM)

galahs, dencorso, eidenk, rloew

From what I understand of the problem, in order to make Win 95-98-ME able to run (backward compatible with) 16-bit Win 3.X programs, they need to be able to operate in 16-bit mode. Thus the files, User.exe, User32.dll, GDI.exe, and GDI32.dll limit the 16-bit system resource size to 64 kbyte. Likewise, there are three 32-bit system resource limitations, 2 Mbyte each per this article (click "About System Resources" at the bottom):

http://www.mvps.org/serenitymacros/repair.html

Some more reading on the subject:

http://onlinehelp.bc.ca/tips.htm#resources
http://www.aumha.org/win4/a/resource.htm

Thanks for the input everybody

, I suppose that this is the real root of the system resource problem. Note that in two bytes there are ((2 raised to the 8th power) squared =) 65536 possible combinations, thus there is only a 64K 16-bit heap size.

"...The resource table is essentially a big list of information about all the resources that are in memory at any given time. So if an application tells Windows to load a resource, Windows finds an empty spot in this resource table, and fills it in with the information about the resource that was just loaded. Now, instead of giving the application a four-byte pointer to the resource, Windows can just tell the application where the resource is in the table. If I tell Windows to load a window, and that window winds up taking the 383rd slot in the resource table, Windows will tell me "Okay, I've loaded the resource, and it's #383." Since these 'index numbers' are much smaller numbers than memory addresses, under this scheme, a resource's number can be stored in only two bytes instead of four; when you only have a few megabytes of memory to work with, and lots of resources being used, that's a huge improvement.

There's a problem with this scheme. There's only so many different possible values that you can store in a certain number of bytes of computer memory, just like there's only so many different numbers you can write down if you aren't allowed to use more than a certain number of digits. If you have four bytes of memory to work with, you can store billions of different possible values in those four bytes. But if you only have two bytes, there's only 65536 different numbers that you can store in those two bytes. So if you use two-byte numbers as your resource identifiers, you can't have more than 65536 resources loaded into memory at one time; if you loaded more than that, there'd be no way for programs to tell them apart. But on the computers of the day, there'd be no way to fit more than a few thousand resources into memory at one time anyway. So this limitation wasn't seen as being a problem, and the Windows designers went ahead and used the resource table and two-byte resource identifiers.

Now, we leap ahead to the present day. Memory is incredibly cheap; the memory savings from using two-byte resource numbers instead of four-byte pointers simply aren't significant anymore. There'd be more than enough memory to hold hundreds of thousands of resources in memory at one time. But there's still only 65,536 different possible resource identifiers; so only that many resources can be loaded into memory at once. Beyond that, you're out of resources, no matter how much memory you have left."

http://www2.whidbey.com/djdenham/Window_memory.htm

http://www.msfn.org/board/Enable48BitLBA_B...0&start=300

bristols

Oct 28 2007, 08:09 PM

QUOTE (MDGx @ Oct 24 2007, 09:47 AM)

I hope to keep you guys busy for the next few days testing all those updates.

I have been dutiful, MDGx.

I have an issue to report concerning a DLL from the RICHED9X.EXE update. Using Miranda (the current ANSI version - 0.7.1), I get the following message when I click on a contact from my contacts list (in order to open a message window):

CODE

The specified module could not be found (USP10.dll)

The message appears only on the first occasion that I do this - not subsequently. The message window opens as normal after I dismiss the message, and I can continue without problem (at least I haven't discovered a problem yet).

erpdude8

Oct 29 2007, 11:09 AM

QUOTE (bristols @ Oct 28 2007, 09:09 PM)

I have been dutiful, MDGx.

I have an issue to report concerning a DLL from the RICHED9X.EXE update. Using Miranda (the current ANSI version - 0.7.1), I get the following message when I click on a contact from my contacts list (in order to open a message window):

CODE

The specified module could not be found (USP10.dll)

The message appears only on the first occasion that I do this - not subsequently. The message window opens as normal after I dismiss the message, and I can continue without problem (at least I haven't discovered a problem yet).

try using an older version of the usp10.dll file, bristols. And store a copy of the usp10.dll in the Miranda program's folder to ensure full compatibility. the updated riched9x.exe patch installs the usp10.dll file featured from WinServ2003 SP2.

Note to MDGx: The Exception Error Cmapieng.vxd fix for WinME is no longer available from the NAI web site. MS article 275003 still mentions the "broken" download link but I have removed references to the cmapieng.vxd patch from my Win98/ME updates page.

also, I have revised the unofficial WMP9 update rollup pack for Win98se/ME and made an unofficial WMP9 update rollup pack for Win2k; both include the recent wmp.dll ms07-047 security fix. Let me know if you need them.

the_guy

Oct 29 2007, 02:28 PM

@erpdude8: I wouldn't mind looking at those.

the_guy

Drugwash

Oct 29 2007, 05:31 PM

@ bristols: which version of usp10.dll do you have installed? I have 1.0471.4030.0, together with riched20.dll 5.30.23.1221 (I know about .1228 but dont' have it around) - the other richedit versions don't work correctly with SpellChecker in Miranda - and I have no such problem. Also, please specify which messaging plug-in you're using (SRMM, Scriver, tabSRMM, nConvers), and if that error comes up with any of the aforementioned (switch them in Options > Plugins, if you got them installed; make sure you install the appropriate, compatible versions).

blackwire

Oct 30 2007, 01:15 PM

QUOTE (bristols @ Oct 28 2007, 10:09 PM)

QUOTE (MDGx @ Oct 24 2007, 09:47 AM)

I hope to keep you guys busy for the next few days testing all those updates.

I have been dutiful, MDGx.

I have an issue to report concerning a DLL from the RICHED9X.EXE update. Using Miranda (the current ANSI version - 0.7.1), I get the following message when I click on a contact from my contacts list (in order to open a message window):

CODE

The specified module could not be found (USP10.dll)

The message appears only on the first occasion that I do this - not subsequently. The message window opens as normal after I dismiss the message, and I can continue without problem (at least I haven't discovered a problem yet).

The usp10.dll 1.0626.5756.0 (vista_rtm.061008-1400) file IS buggy! I have encountered the same error while running ms word 2000, and ms powerpoint viewer 2003 refuses to start because of the buggy usp10.dll file. I have downgraded to an older version, 1.0420.2600.2180 (xpsp_sp2_rtm.040803-2158) and everything works fine now. Please update your RICHED9X.EXE package to fix these bugs. I love your work MDgx, without you, windows 9x would be completely useless.

bristols

Oct 30 2007, 01:54 PM

QUOTE (Drugwash @ Oct 30 2007, 12:31 AM)

@ bristols: which version of usp10.dll do you have installed? I have 1.0471.4030.0, together with riched20.dll 5.30.23.1221 (I know about .1228 but dont' have it around) - the other richedit versions don't work correctly with SpellChecker in Miranda - and I have no such problem. Also, please specify which messaging plug-in you're using (SRMM, Scriver, tabSRMM, nConvers), and if that error comes up with any of the aforementioned (switch them in Options > Plugins, if you got them installed; make sure you install the appropriate, compatible versions).

Hi Drugwash, apologies if I was too vague.

The version of USP10.DLL that (for me) causes Miranda problems is 1.0626.5756.0 (from the latest revision of MDGx's RICHED9X.EXE, as noted by blackwire in the post above). Like blackwire, I reverted to version 1.0420.2600.2180, which has cleared up the problem.

As for plugins, I have added none. I'm using a vanilla install (being still a Miranda newbie).

MDGx

Oct 31 2007, 11:04 AM

Rich Text (RTF) Edit Controls RICHED20.DLL 5.50.99.2014 + USP10.DLL 1.422.3790.3959 Security Vulnerability Fix:
http://www.microsoft.com/technet/security/...n/ms07-013.mspx
Unofficial Windows 95/98/ME RTF Fix [1.12 MB, English]:
http://www.mdgx.com/files/RICHED9X.EXE

HTH

blackwire

Oct 31 2007, 06:40 PM

The new version of RICHED9X.EXE works fine with MS office now. Thanks!!

bristols

Nov 1 2007, 06:34 AM

Yep, USP10.DLL version 1.0422.3790.3959 seems to work fine with Miranda. Thanks MDGx for the revision.

erpdude8

Nov 5 2007, 11:46 AM

QUOTE (blackwire @ Oct 30 2007, 02:15 PM)

The usp10.dll 1.0626.5756.0 (vista_rtm.061008-1400) file IS buggy! I have encountered the same error while running ms word 2000, and ms powerpoint viewer 2003 refuses to start because of the buggy usp10.dll file. I have downgraded to an older version, 1.0420.2600.2180 (xpsp_sp2_rtm.040803-2158) and everything works fine now. Please update your RICHED9X.EXE package to fix these bugs. I love your work MDgx, without you, windows 9x would be completely useless.

not just buggy, blackwire. Usp10.dll version 1.0626.5756.0 from Vista is more likely incompatible with Win9x/ME/NT4 OSes and users should revert to using v1.04x of usp10.dll

QUOTE

@erpdude8: I wouldn't mind looking at those.

the_guy

sure thing, the_guy. I've uploaded the revised unofficial WMP9 URPs for Win98se/ME and Win2k at the Usaupload site; email me for the links but I'm only going to keep the URPs up at USAUpload until this Friday. Hopefully MDGx has gotten my message last week about the updated WMP9 URPs and has gotten them.

MDGx

Nov 13 2007, 08:46 AM

WMP9 URPs:

* WMP9URP: Unofficial Windows Media Player 9.0 (WMP9) Update Rollup Packs
(URP) for Windows 98/98 SP1/98 SE/2000/ME install ALL previously released WMP9
Hotfixes, Patches + Updates:
- WMP9URP2K for Windows 2000 [8.96 MB, English]:
http://www.mdgx.com/spx/WMP9URP2K.EXE
- WMP9URP9X for Windows 98/98 SP1/98 SE/ME [8.77 MB, English]:
http://www.mdgx.com/spx/WMP9URP9X.EXE
- ITMP9URP for Windows 98/98 SP1/98 SE/ME [8.57 MB, Italian]:
http://www.mdgx.com/spx/ITMP9URP.EXE
Windows 98 SE, ME + 2000 require WMP9 [13.3 MB, English]:
http://www.mdgx.com/wmp.htm#WMP9
already installed!
Windows 98 + 98 SP1 require Unofficial WMP9 [13.3 MB, English]:
http://www.mdgx.com/spx/WMP90_98.EXE
already installed!
How to install WMP9 on Windows 98:
http://erpman1.tripod.com/cmptips2.html

HTH

dencorso

Nov 16 2007, 12:27 AM

Well, here is a version history for CDVSD.VXD:

LENOVO Windows 95/98 installation supplement files - ThinkPad 390, 172x
12/04/1998 04:47p 4.10.0.2001 30,395 CDVSD.VXD Windows 98 FE

KB242534 Computer Hangs When Removing DVD-ROM Drive From Bay
12/03/1999 04:47p 4.10.0.2184 31,931 CDVSD.VXD Windows 98 FE
12/06/1999 12:46p 4.10.0.2223 32,443 CDVSD.VXD Windows 98 SE

KB265314 Error Message "No Valid Drive/Disc Found" Playing Audio CD After Using Data CD-ROM
06/21/2000 12:47pm 4.10.0.2185 31,931 Cdvsd.vxd Windows 98 FE
06/21/2000 12:33pm 4.10.0.2224 32,443 Cdvsd.vxd Windows 98 SE

KB265405 Problems Resuming After Suspend While MPEG Is Playing
06/28/2000 10:00am 4.10.0.2225 32,443 Cdvsd.vxd Windows 98 SE

KB274370 Error Message on a Blue Screen When You Try to Play Digital CD Audio
09/28/2000 10:26p 4.10.0.2186 32,443 Cdvsd.vxd Windows 98 FE
09/28/2000 10:05p 4.10.0.2226 32,443 Cdvsd.vxd Windows 98 SE
09/28/2000 10:08p 4.90.0.3002 41,643 Cdvsd.vxd Windows Me

KB304708 Your Computer May Stop Responding with IEEE 1394 DVD and USB Storage Drives
08/09/2001 7:08a 4.90.0.3003 41,643 Cdvsd.vxd Windows Me

Many of us are using CDVSD.VXD v. 4.10.0.2224, kindly posted by ElectricString, since Xeno86 found out that CDVSD.VXD v. 4.10.0.2226 is buggy, as reported here. CDVSD.VXD v. 4.10.0.2225 has not surfaced up to know, so it is unavailable for testing. The version history I presented above shows that Win ME CDVSD.VXD v 4.90.0.3002 is equivalent to Win 98SE CDVSD.VXD v 4.10.0.2226. This makes Win ME CDVSD.VXD v 4.90.0.3003 the most updated version of that VXD, up to the present, thus presumably incorporating all the previous hotfixes. Yet, unpatched Win ME CDVSD.VXD cannot run under Win 98SE. But the selfsame version patch that I applied to USB FDD DiskTSD.VxD 4.90.0.3000 Patch, allows Win ME CDVSD.VXD v 4.90.0.3003 to run flawlessy under Win 98SE. I have been using it since Oct 31st in my system, without any problem, so I can affirm it works OK and has not the bug Xeno86 found on v. 4.10.0.2226. So here I offer you the patched version of Win ME CDVSD.VXD v 4.90.0.3003, renumbered as 4.90.0.3004 to reflect the fact it has been patched and runs OK under Win 98SE and FE (but not anymore under Win ME!).

Download-link: CDVSD.VXD v. 4.90.0.3004 for Win 98 SE (and FE) or at uploaded to

As always, the standard disclaimer applies: It works great for me, but YMMV and I can guarantee nothing whatsoever about this patch, and about the use you make of it. By deciding to use it you fully accept that anything you do is of YOUR SOLE RESPONSIBILITY... Moreover, modding files voids the EULA, of course. You have been warned.

Drugwash

Nov 16 2007, 01:34 AM

Please try a real host, like http://uploaded.to/ or something. Maybe that way I could download it too. Thank you.

[EDIT]
Sorry, my IE seems to be FUBAR - I can't seem to download from that host either, although it used to work. Something is really FU here, and I need to fix it a.s.a.p. But I really dunno what to do first, it's driving me crazy.

erpdude8

Nov 16 2007, 10:39 PM

QUOTE (dencorso @ Oct 5 2007, 07:44 PM)

Hi, erpdude8!

As you already know, the files for Win 98SE from Q329128 have recently surfaced in SESP30-alpha-1 and remain present in alpha-2. They are NDIS.VXD 4.10.0.2226; PPPMAC.VXD 4.10.0.2223 and VIP.386 4.10.0.2228, of course. But Q329128 also carries fixes for Win 98FE and ME. Yet, both in his anouncement and in the spupdate.inf included in SESP30-alpha-1, Gape refers to those files as if they were part of Q301453. And while both MSKB articles pertain to "multicast packets that have a TTL setting of 0 (zero)", Q301453 is for Win 2k/XP, while Q329128 is the correct article number for Win 9x/ME, and only Q329128 contains the above mentioned files. It is a fact that Q301453 points to Q329128 and vice-versa, but I don't see the point in referring to it in such a roundabout way.

It is great that those files are now available, after everybody sought them for so long. And VIP.386 4.10.0.2228 IS better than 4.10.0.2227, for in some way the system becomes less resouce-hungry when 2228 is installed. I can't help but wonder whether Gape has the complete Q329128 or if he just found its files for Win 98SE somewhere. Gape,

would you please be so kind as to enlighten us? You rock, both of you! Without your continued endeavours, our computing experience would be so much the poorer.
Keep on the good work!

Win 9x/ME forever!

Well, dencorso, read this.

BREAKING NEWS about the latest NDIS.VXD, PPPMAC.VXD & VIP.386 files for BOTH Win98 FE and Win98 SE: I have obtained the actual Q301453 hotfix for Win98 from MS support! Unbelievable!!!

The files from the Q301453 Win98 hotfix are the same versions as the ones listed in Q329128. Q329128 is not available from MS BUT Q301453 for Win98 IS available as I've just emailed MS for it. yay!

dencorso

Nov 17 2007, 12:28 AM

Great news, erpdude8!

And mystery solved:
Gape wasn't referring to Q329128 in a roundabout way after all!
There really IS a Q301453 Win98 FE and SE hotfix!!!
So, then, that's whence Gape got those files, after all, just as he said!!!
Gape,

I tend you my apologies.
Say, erpdude8, have you already asked for the Win ME version of Q301453, or should I?

the_guy

Nov 17 2007, 04:57 PM

I just received KB301453 for Windows ME.

It's going to be in the next USP release, date TBA.

the_guy

Fredledingue

Nov 18 2007, 12:39 PM

Why do we have two IE updaters: IEUPD and MDIE6CU with apparently the same new files (last additions) in them?

erpdude8

Nov 19 2007, 09:45 AM

QUOTE (dencorso @ Nov 17 2007, 01:28 AM)

Great news, erpdude8!

And mystery solved:
Gape wasn't referring to Q329128 in a roundabout way after all!
There really IS a Q301453 Win98 FE and SE hotfix!!!
So, then, that's whence Gape got those files, after all, just as he said!!!
Gape,

I tend you my apologies.
Say, erpdude8, have you already asked for the Win ME version of Q301453, or should I?

the_guy has taken care of getting the Q301453 hotfix for WinME, dencorso.

It would be better off if Microsoft mentioned the updated ndis.vxd, pppmac.vxd & vip.386 files for Win98/ME in MS article 301453 instead of having to write them in a separate article and be told that they're not available and get confused.

I'm currently in the process of getting Q301453 hotfix for Italian language editions of Win98 since I already got the English Q301453 patch for Win98. It's incredible that the updated files from Q329128 have been packaged in the most unlikely place!

Please note that the Q301453 hotfix for Win98 requires the Dialup Networking 1.4 Q285189 security update. If you try to install Q301453 without the DUN 1.4 update for Win98, the patch will refuse to install the updated ndis.vxd, pppmac.vxd & vip.386 files and will be told to install the DUN 1.4 update.

if you view the file properties of the latest PPPMAC.VXD files and click on the Version tab and select the "Internal Name" property, it will say "PPPMAC (128 Bit)". the pppmac.vxd files from Q301453 for Win98 contain 128bit security for Dialup Networking but you'll need the DUN 1.4 update for Win98 to take advantage of 128bit security.

dencorso

Nov 19 2007, 03:18 PM

I'm aware of that, erpdude8, and have been using Q285189 for a long time now.
But thank you for the heads up just the same.

You do rock!

RetroOS

Nov 20 2007, 02:34 AM

QUOTE (MDGx @ Nov 14 2007, 03:46 AM)

WMP9 URPs:

* WMP9URP: Unofficial Windows Media Player 9.0 (WMP9) Update Rollup Packs
(URP) for Windows 98/98 SP1/98 SE/2000/ME install ALL previously released WMP9
Hotfixes, Patches + Updates:
...
- WMP9URP9X for Windows 98/98 SP1/98 SE/ME [8.77 MB, English]:
http://www.mdgx.com/spx/WMP9URP9X.EXE
...

Cool update MDGx. But...
I have your 98MP10 installed, and when I installed WMP9URP9X, it back-dated the following two files:

\WINDOWS\SYSTEM\WMDMLOG.DLL v10 > v9
\WINDOWS\SYSTEM\WMDMPS.DLL v10 > v9
Also it added v9 of WMPBAND.DLL into \WINDOWS\SYSTEM.
98MP10 installed v10 of WMPBAND.DLL into \Program Files\Windows Media Player.
I had to reinstall 98MP10 to update those two back-dated files...

erpdude8

Nov 20 2007, 04:02 PM

QUOTE (RetroOS @ Nov 20 2007, 03:34 AM)

Cool update MDGx. But...
I have your 98MP10 installed, and when I installed WMP9URP9X, it back-dated the following two files:

\WINDOWS\SYSTEM\WMDMLOG.DLL v10 > v9
\WINDOWS\SYSTEM\WMDMPS.DLL v10 > v9
Also it added v9 of WMPBAND.DLL into \WINDOWS\SYSTEM.
98MP10 installed v10 of WMPBAND.DLL into \Program Files\Windows Media Player.
I had to reinstall 98MP10 to update those two back-dated files...

You should have installed WMP9UPR9X first and then 98MP10, RetroOS. OR UN-install 98MP10 and reinstall WMP9 and WMP9URP9X. Next time, remember that. anyways, re-installing 98MP10 solved your problem.

WMP9URP9X was designed to update the original release of WMP9 under Win98se & WinME, meaning without any unofficial addons like 98MP10.

98MP10 was created by MDGx while WMP9URP9X is my creation. I may release an updated
version of WMP9URP9X that will NOT install under Win98se with 98MP10 installed. WMP9URP9X does NOT really support 98MP10 and vice-versa. having both WMP9URP9X and 98MP10 addons installed may cause other problems that I don't know of and I have not really tested 98MP10 on any Win98se machine with WMP9 installed.

QUOTE (dencorso @ Nov 19 2007, 04:18 PM)

I'm aware of that, erpdude8, and have been using Q285189 for a long time now.
But thank you for the heads up just the same.

You do rock!

no probs, dencorso. I've already sent the english and italian Q301453 patches for Win98 to MDGx.
Thanks again for the Q301453 patch for WinME.

Analada

Nov 21 2007, 05:43 AM

QUOTE (erpdude8 @ Nov 20 2007, 04:02 PM)

QUOTE (RetroOS @ Nov 20 2007, 03:34 AM)

Cool update MDGx. But...
I have your 98MP10 installed, and when I installed WMP9URP9X, it back-dated the following two files:

\WINDOWS\SYSTEM\WMDMLOG.DLL v10 > v9
\WINDOWS\SYSTEM\WMDMPS.DLL v10 > v9
Also it added v9 of WMPBAND.DLL into \WINDOWS\SYSTEM.
98MP10 installed v10 of WMPBAND.DLL into \Program Files\Windows Media Player.
I had to reinstall 98MP10 to update those two back-dated files...

You should have installed WMP9UPR9X first and then 98MP10, RetroOS. OR UN-install 98MP10 and reinstall WMP9 and WMP9URP9X. Next time, remember that. anyways, re-installing 98MP10 solved your problem.

WMP9URP9X was designed to update the original release of WMP9 under Win98se & WinME, meaning without any unofficial addons like 98MP10.

98MP10 was created by MDGx while WMP9URP9X is my creation. I may release an updated
version of WMP9URP9X that will NOT install under Win98se with 98MP10 installed. WMP9URP9X does NOT really support 98MP10 and vice-versa. having both WMP9URP9X and 98MP10 addons installed may cause other problems that I don't know of and I have not really tested 98MP10 on any Win98se machine with WMP9 installed.

QUOTE (dencorso @ Nov 19 2007, 04:18 PM)

I'm aware of that, erpdude8, and have been using Q285189 for a long time now.
But thank you for the heads up just the same.

You do rock!

no probs, dencorso. I've already sent the english and italian Q301453 patches for Win98 to MDGx.
Thanks again for the Q301453 patch for WinME.

Umm...I did the same thing...made the same mistake....

So, yes, probably a good idea if you can to prevent WMP9URP9X from installing under Win98se if 98MP10 installed.

RetroOS

Nov 21 2007, 11:42 PM

QUOTE (erpdude8 @ Nov 21 2007, 11:02 AM)

...
WMP9URP9X was designed to update the original release of WMP9 under Win98se & WinME, meaning without any unofficial addons like 98MP10.

98MP10 was created by MDGx while WMP9URP9X is my creation. I may release an updated
version of WMP9URP9X that will NOT install under Win98se with 98MP10 installed...

Okay then, I suppose I should redirect my 'cool update' to you erpdude8!
Your udpate did update some other files so instead of making it not install with 98MP10, maybe just don't back-date those two files...

What about the added WMPBAND.DLL file in the \WINDOWS\SYSTEM directory instead of \Program Files\Windows Media Player?
I've never had this file in \WINDOWS\SYSTEM before that I am aware of...

Tihiy

Nov 22 2007, 01:22 AM

I'm sorry to say this, Elvis and others, but wmpband.dll won't ever work on 9x systems. [I was sure it has left the building long time ago?]

dencorso

Nov 25 2007, 08:56 PM

Well, here is a brief version history for VNETBIOS.VXD:

04/23/99 10:22PM 4.10.0.1998 39,506 Vnetbios.vxd Win 98 SE (original distribution, same for FE)
07/13/99 08:32PM 4.10.0.2223 35,434 Vnetbios.vxd Win 98 FE (+ SE ?) Q265528, which nobody ever has obtained;
06/08/00 05:00PM 4.90.0.3000 38,633 Vnetbios.vxd Win ME (original distribution, also in Q272991)

Unpatched Win ME VNETBIOS.VXD will not load under Win 98 SE (or FE). Windows'll instead throw a "file is damaged" message and freeze while loading. But this can be solved by using my downversion patching trick. So here I offer you the patched version of Win ME VNETBIOS.VXD v 4.90.0.3000, renumbered as 4.90.0.3001, to reflect the fact it has been patched and runs OK under Win 98SE and FE (but not anymore under Win ME!).

Download-link: VNETBIOS.VXD v. 4.90.0.3001 for Win 98 SE (and FE)

As always, the standard disclaimer applies: It works great for me, but YMMV and I can guarantee nothing whatsoever about this patch, and about the use you make of it. By deciding to use it you fully accept that anything you do is of YOUR SOLE RESPONSIBILITY... Moreover, modding files voids the EULA, of course. You have been warned.

PROBLEMCHYLD

Nov 26 2007, 01:48 AM

@ dencorso
Do you think your down version patching trick will work with most files?

dencorso

Nov 27 2007, 12:06 AM

Hi, PROBLEMCHYLD!

Well, probably with most VxDs, yes.
Then, there are three types of Win ME VxDs:
1) Those that don't need any patching to load (almost all are included in 98SE2ME, except for a handful that load but do not work well, at least in some setups: VCACHE.VxD and NDIS.VxD are representative examples of the latter). MDGx has fully explored this field already. There are 11 VxDs (from %windir%\system\) and two PDRs (from %windir%\system\iosubsys\) that can just be transplanted as they are. See MDGx's 98SE2ME page.
2) Those that need downversion patching to load, but then work OK: besides the three already released (DISKTSD.VxD, CDVSD.VxD and VNETBIOS.VxD), I'm testing three more (DISKVSD.VxD, CDTSD.VxD and SMARTVSD.VxD), as I reported above. I do beleieve most VxDs and PDRs from %windir%\system\iosubsys\ and from %windir%\system\ will load after patching, the question is whether they'll work OK.
3) Those that do not work in Win 98SE, despite patching, even when patching gets them to load (probably most in %windir%\system\VMM32\, as well as those packed inside VMM32.VxD). I've kept away from those on purpose, because I don't believe they'll work.

With other types of files, like WDM drivers (.SYS and .MPD files), possibly, but I don't know for sure. They are PE executables, not LE executables, anyway... I just didn't investigate it at all, up to now.

In general, unnecessarily over-restrictive version checking is still a common programmer practice, so relaxing this restrction by patchig can provide many good finds. On the other hand, sometimes files are really tied to a specific OS version, and those won't work, despite patching (or worse: may wreak havoc in the test system, once one gets them to load through patching...). Lots of patience, good backups and careful testing are all that's required to find out.

MDGx

Nov 30 2007, 11:23 AM

* Unofficial Windows 98 SE Computer Hangs With IEEE 1394 (FireWire) DVD + USB Drives CDVSD.VXD 4.90.3004 Fix:
http://web.archive.org/web/20041113063902/...om/?kbid=304708
Direct download [78 KB, English]:
http://www.mdgx.com/files/Q304708.EXE
This CDVSD.VXD 4.90.3004 Fix installs also as part of NUSB:
http://www.msfn.org/board/?showtopic=43605
also here:
http://www.mdgx.com/web.htm#NUS

P.S.:
More updates to follow soon...
I will also update 98SE2ME to include CDVSD.VXD 4.90.3004 [unofficial], and also VIP.386 4.10.2228 [official], CONTROL.EXE 4.90.3001 [unofficial], DISKTSD.VXD 4.90.3001 [unofficial], NDIS.VXD 4.10.2226 [official], VCACHE.VXD 4.10.2223 [unofficial] [as soon as Xeno86 sends me VCACHE.VXD 4.10.2223 English, I only have Polish + French].

HTH

MDGx

Nov 30 2007, 12:06 PM

Thank you dencorso... again

* Unofficial Windows 98 SE Networking Errors VNETBIOS.VXD 4.90.3001 Fix:
http://web.archive.org/web/20050206045511/...om/?kbid=272991
Direct download [70 KB, English]:
http://www.mdgx.com/files/Q272991.EXE

HTH

MDGx

Dec 1 2007, 02:46 PM

Guys,

Good news...
Fixed *all* problems with both SCR569X.EXE [Unofficial MSE 5.6] + SCR579X.EXE [Unofficial MSE 5.7].
Everything works now 100%.

Please re-install the one you like.
No more errors that I'm aware of.
I personally recommend MSE 5.7, because some web sites are moving on to support exclusively MSE 5.7 [talk about universal internet standards

], which is installed by Windows Vi$ta.

- Unofficial MSE 5.7 5.7.0.16535 for Windows 98/98 SP1/98 SE/ME [710 KB]:
http://www.mdgx.com/files/SCR579X.EXE

- Unofficial MSE 5.6 5.6.0.8832 for Windows 98/98 SP1/98 SE/ME [675 KB]:
http://www.mdgx.com/files/SCR569X.EXE

Uninstall/restore function not necessary anymore, everything works now as expected.
If you don't like one, re-install the other.

Please post here any problems you might encounter with Unofficial MSE 5.6 or 5.7.

P.S.:
Please ignore %windir%\SYSTEM\WSHCON.DLL , which installs as part of Unofficial MSE 5.7 [SCR579X.EXE].
Works only with NTx OSes [2000/XP/2003/Vi$ta], but certain applications expect to find it in the same directory as all other MSE 5.7 files.

HTH

PROBLEMCHYLD

Dec 2 2007, 01:02 AM

dencorso
what about Vxdmon.vxd?

Bleeder

Dec 2 2007, 01:00 PM

QUOTE (MDGx @ Dec 1 2007, 03:46 PM)

Please post here any problems you might encounter with Unofficial MSE 5.6 or 5.7.

Many thanks for your work on this!

I recently noticed there is a newer MSE 5.6 jscript.dll in KB942840. Could that be added to your MSE 5.6 update?

MDGx

Dec 4 2007, 02:23 PM

All December 2007 TZ (Time Zone) DST (Daylight Saving Time) updates for all Windows 32-bit (Win32) OSes are finally here [as of December 4 2007]:
http://www.mdgx.com/add.htm#TZU

Of particular interest in this 98/ME forum...

* Microsoft Windows 98/98 SP1/98 SE/ME 2006-2008 December 2007 Cumulative Daylight Saving Time (DST) Time Zone Updates (English):
http://support.microsoft.com/?id=942763
- Unofficial DST Update for Windows 98/98 SP1/98 SE/ME [114 KB, English]:
http://www.mdgx.com/files/Q942763.EXE
- Unofficial DST Update for Windows 98/98 SP1/98 SE/ME [117 KB, Italian]:
http://www.mdgx.com/files/IT942763.EXE
ALL these DST Updates MUST be installed by ALL Windows users REGARDLESS of geographical or Time Zone location!
ALL Unofficial Cumulative DST Updates above install ALL Time Zone Updates and also delete obsolete 2006 Australian (Melbourne Commonwealth Games) DST registry entries (if any):
http://support.microsoft.com/?id=909915
Windows 98, 98 SP1 + 98 SE require ALL Year 2000 (Y2K) Updates + Q237493 TIMEDATE.CPL Fixes already installed:
http://www.mdgx.com/web.htm
DST Help and Support Center:
http://support.microsoft.com/gp/cp_dst/
List of products affected by DST:
http://support.microsoft.com/gp/dst_prodlist/
How to Configure 2007 DST:
http://support.microsoft.com/?id=914387
DST Changes:
http://www.microsoft.com/windows/timezone.mspx
DST Updates MSFN Forum:
http://www.msfn.org/board/?showtopic=87399
Wikipedia: Daylight Saving Time (DST):
http://en.wikipedia.org/wiki/Daylight_saving_time

HTH

MDGx

Dec 4 2007, 03:05 PM

QUOTE (Bleeder @ Dec 2 2007, 12:00 PM)

I recently noticed there is a newer MSE 5.6 jscript.dll in KB942840. Could that be added to your MSE 5.6 update?

Here you go...

* Microsoft Windows 98/98 SP1/98 SE/ME Scripting Engines (MSE) v5.6 include: VBScript (VBS) 5.6, JScript (JS) 5.6, Windows Script Components (WSC), Windows Script Host (WSH) 5.6 + Windows Script Runtime (WSR) 5.6:
http://msdn2.microsoft.com/en-us/library/ms950396.aspx
- Unofficial MSE 5.6 5.6.0.8834 for Windows 98/98 SP1/98 SE/ME [669 KB]:
http://www.mdgx.com/files/SCR569X.EXE

Enjoy.

dencorso

Dec 12 2007, 04:01 PM

Well, here is a brief version history for DiskVSD.VxD:

04/23/99 10:22PM 4.10.0.1998 10,194 DISKVSD.VXD Win 98 SE (original distribution, same for FE)
06/08/00 05:00PM 4.90.0.3000 10,140 DISKVSD.VXD Win ME (original distribution)
08/09/00 05:00PM 4.90.0.3001 10,140 DISKVSD.VXD Win ME Q271277

Unpatched Win ME DiskVSD.VxD will not load under Win 98 SE (or FE). Windows'll instead throw a "file is damaged" message and freeze while loading. This can be solved by downversion patching. So here I offer you the patched version of Win ME DiskVSD.VxD v 4.90.0.3001, renumbered as 4.90.0.3002, to reflect the fact it has been patched and runs OK under Win 98SE and FE (but not anymore under Win ME!).

Download-link: DiskVSD.VxD v. 4.90.0.3002 for Win 98 SE (and FE)

Q271277 "Computer Hangs Accessing Removable Disk Such as Magneto-Optical Disk" corrects a problem documented by Microsoft only for Win ME (it does not necessarily mean it doesn't exist in the Win 98 SE/FE version...), but since many of us are now running the patched version of Win ME DiskTSD.VxD, I think it's advisable to also run this matching DiskVSD.VxD just to be on the safe side. And, in any case, this is the most up-to-date existing version of DiskVSD.VxD known to work with Win 98SE (and FE).

As always, the standard disclaimer applies: It works great for me, but YMMV and I can guarantee nothing whatsoever about this patch, and about the use you make of it. By deciding to use it you fully accept that anything you do is of YOUR SOLE RESPONSIBILITY... Moreover, modding files voids the EULA, of course. You have been warned.

MDGx

Dec 13 2007, 12:11 AM

UPDATED · 12-12-2007

Please see the top of this topic for most recent updates.

Enjoy.

eidenk

Dec 13 2007, 02:26 PM

That's a huge list indeed.

QUOTE

MSE 5.7 requires MS IE 6.0 SP1 or newer already installed

Seems to be working just fine with IE 5.5 SP2 as well.

RetroOS

Dec 14 2007, 09:48 PM

QUOTE (MDGx @ Dec 13 2007, 07:11 PM)

...
Updates:
Too many to list here...

...

WHOA

!
Who said 9x was dead? - Oh wait, it was just a small pain in the side of my head!
Talk about a mammoth fourth quarter of updates for 2007 and what a start to 2008 with a hiss and a roar!

MDGx, how do you find time to keep up all those updates? You make up the hub of 9x support!
Maybe we should call you 'Little Microsoft'? - Just friendlier!

Well, 2008 is lookin' goooood!

Long Live Windows 9x!

Acheron

Dec 15 2007, 10:35 AM

denCorso,

patching Windows ME files to run on Windows 98 is awesome

. However to avoid confusion could you change for example patches the version numbering from 4.90.300x to 4.10.300x

The 4.10.3000 series will tell us that these files are not original Windows 98 files, since these files are in the range 4.10.1998 to 4.10.22xx
It will also prevent people from installing these files on Windows ME.

For example I would prefer it if your 4.90.0.3001 DISKVSD.VXD patched file now would be named 4.10.0.3001 keeping build subnumbers the same as the original patch.

dencorso

Dec 16 2007, 02:04 AM

Acheron:
Your proposal makes sense. Then again, downversioning 4.90.0.xxxx to 4.10.0.xxxx is a major version change, that implies the patched version has some kind of continuity with previous 4.10.0.22xx VxDs, which is not quite the case. Sure, I know I don't need to explain to you anything about version numbers, but I provide the link to Petr's post about it for any reader who may need it. I had thought about upversioning the patches as 4.90.1.xxxx, then opted for the simpler 4.90.0.(xxxx+1) scheme because: (1) no real good solution exists for perfect versioning of patched versions, as you fully know, for you have participated in an analogous discussion regarding the versioning of LLXX patches in Enable48BitLBA, some time ago; (2) the solution reached there of not changing the version numbers doesn't appeal to me, for I feel there should be an easy way of recognizing a patched from an unpatched file, as PassingBy pointed out to me, even if at first I disagreed, because I had in mind precisely the discussion regarding the versioning of LLXX patches, and (3) my patch changes the file very little to achive its aim, so I opted for the present scheme that denotes this, and it seems safe since MS won't be issuing any more hotfixes for Win 9x/ME. In any case, the files are already released, and modifying their versioning scheme at this point would just add further confusion, by creating pairs of files differing only in their versioning scheme, since it is impossible to substitute all files everywhere after the initial release. So, I think it better to leave things as they are, at this point. But I promise you I'll muse about it for some more time and perhaps use a different versioning scheme for patched files in future releases of other patched files.

the_guy

Dec 16 2007, 01:58 PM

Is there any way that you can make Windows Movie Maker it's own option, disabled unless Option 3 is installed?

the_guy