tErmY

Nobody's gonna test RLoew's non-XMS ramdisk?

Now this is weird. I looked at three different XP "update packs." All of them are using MSXML 4.0 SP 2 instead of SP 3. I downloaded Problemchylde's latest "service pack" for 98. He's got one from 07/12/16. It's up to v3.56 now. Last one I had was v3.37 from 01/15. He's also using MSXML 4.0 SP 2. Why aren't these guys using SP 3? It's been out for almost seven years.

You weren't kidding. They look like the exact same files. I grabbed the others while I was at it. I might need something to do after I finish transplanting XP files. FWIW, I use XMSDSK on my clunkers.

Thanks. I didn't know that. Downloaded for posterity

No QEMM or Helix Hurricane? How about XMSDSK?

Well, this is certainly disappointing. There used to be several guys around here who knew about these things, or were willing to test them. I guess they've all moved on. Where's Axcel216 when you need him? Oh hell, I'd settle for Problemchylde right about now :) Looks like I'll have to test these files myself. The latest unofficial "update pack" for XP that I found was XPSP3_QFE_UpdatePack_20170619. It's designed to be "slipstreamed," so the files don't need to be patched. Inside was a newer version of GDIPLUS.DLL. It's a Vista file. Version 5.2.6002.24064. File date 02/13/17. 1,753,088 bytes. It seems to work under SE. There are no missing dependencies. Of course, ti wouldn't register, but I don't believe any version of GDIPLUS will. My network works. I've got Internet access. As far as I can tell, it hasn't screwed anything up yet. Looks like it's safe enough to test. I don't rightly know what GDIPLUS is used for. I believe it's got something to do with Visual C. I'll be sure to let you guys know if my machine blows up :)

More XP updates: https://www.askwoody.com/2017/xp-sp3server-2003-security-patches-released-june-2017/ Wonder if any of this stuff can be used with 9X?

https://blogs.technet.microsoft.com/msrc/2017/05/12/customer-guidance-for-wannacrypt-attacks/ There are 32-bit and 64-bit versions for XP SP2.

So, are 9X machines vulnerable? I see MickeySoft released a patch for XP. Could portions of it be used with 98?

Thanks, Jumper! You're a genius

Thanks, MiKl. That's the same problem I had. It starts fine, but crashes when I try to add files.

I tried it again. I captured the FineSSE error if I can figure out how to attach it.

I was mistaken about FlashBlock, however I did run into another problem. Finesse23.exe kept popping up with an access violation whenever I ried to run XnConvert. When I reverted back to 4.5.2 from Release_5.7 the problem went away. My content line reads: contents=Kstub822,std,kexbases,kexbasen,K452stub I just downloaded your Release.7.7 I'll try it out and try switching the order of the contents line.

Only problem so far is that it seems to have broken FlashBlock 1.5.14.2 under BonEcho 2.0.0.22pre and Firefox 3.6.28. No big deal. I just disabled FlashBlock. Don't really need it with NoScript.

I've got the same problem as oc_dt and gg41.

Confirmed. I'm now using the same files as you. Everything seems to be ok, but I seldom use Internet Exploder. FWIW, I am using KernelEX 4.0 RC2.

poor choice LLXX. Qwerty.Msi is for NT-based versions of Windows only, excluding 9xME OSes. read the System Requirements section for Qwerty.Msi. also it requires .NET Framework 1.1 or higher installed. Works on Win98se without the kernel update... also using a very stripped down .NET framework here (I hate .NET but this is the best free .msi manipulator so far, so until I can find something better...) What did you do to strip it down?

yes, Hu$tle. HOWEVER, I have tested version 5.6.0.8833 of JSCRIPT.DLL and VBSCRIPT.DLL files and they do NOT register under Win98/ME. MDGx is RIGHT about THAT. If these files were from a beta version of Windows Vista then they should NOT be included in future betas of the ME service pack and in unofficial U917344 fix. Version 5.7.0.5730, on the other hand, of the JSCRIPT.DLL and VBSCRIPT.DLL files DO register fine under Win98/ME AS LONG AS the files were obtained from the IE7 for WinXP package. I've also been running JSPROXY.DLL 7.0.5730.11 from IE 7. It has a lot more unresolved dependencies than JSPROXY.DLL 6.0.2800.1578 from Axcel's unofficial update, but it hasn't caused me any problems. Someone who actually uses IE will have to test it further. These are the only three files I've found so far that don't cripple IE 6 in some fashion, but I'm only about a third of the way through them all. I suspect that several of the IE 7 files will work under 9X. They just won't work with IE 6.

JSCRIPT.DLL 5.7.0.5730 from IE 7.0 has no unresolved dependencies. It also registers under SE. Same with VBSCRIPT.DLL 5.7.0.5730. I rarely use IE, so I couldn't swear that they're absolutely safe, but they seem to be working so far.

NO, it won't work. You can make it run on 9x, but it won't make difference, because problem in mshtml. No unresolved dependencies with MSVCRT.DLL 6.1.9847.0, however PNGFILT.DLL wouldn't register. "A device attached to your system is not functioning." I updated my system with the latest files from MESP202B7. I got the same error with WSHOM.OCX. They won't crash your system, or anything, but I'm guessing that we probably shouldn't use either one with SE.

Will the one from IE 7 work on Win98SE? It has two unresolved dependencies with MSVCRT.DLL 6.0.9782.0. Still investigating....Suggest you do the same....

Symbols for what version of the files? What's a symbol file?

Does it overwrite later versions of DZip32.dll/DUnZip32.dll? I'm using version 4.00.04 11/30/01. Not sure where I got them. Maybe they came with WinRAR. The 98SEtoME version is 3.00.18 7/3/02.