LoneCrusader

@osiff You're already getting the best advice, so the only thing that I would add is do not be discouraged if changing the various settings in SYSTEM.INI does not fix your problem. I tried all of those things in the past, and none of it ever worked for my system either. I'm a firm believer in RLoew's RAM Patch.

Thanks for the info, although this has long been solved. I didn't want to remove IE, just stop the forced install because it was freezing up and never completing due to RealPlayer. Replacing the IE4 files with IE4.01 SP2 files fixed the crash and the install completes, or you can edit the file I mentioned above to stop it completely. Also, for installing IE5+ with Active Desktop enabled, I have created a much faster and simpler solution here.

RLoew's RAM patch can be used to solve this problem, and will allow you to use all 4 GB of RAM. R. Loew Electronics Consulting See This Thread for more info. Welcome to MSFN!

No problem, glad to be able to help.

Try this, I had this archived but now I don't remember whether or not I used it on any of my systems But the .INF inside lists 1371 and 1373 specifically.

Any feedback on this yet? If anyone can test it, it should work for NT4 as well.

I think you're onto something here, I run Adblock Plus on my Firefox.

Well, to expand a bit more on the issue since someone else has encountered it... When I experimented with the USP on one of my test machines, it rendered it unbootable, but I don't remember the exact circumstances or error. Judging by the links that nyvicky posted, I assume he is having errors related to VMM32.VXD. Now, there are several potential VMM32.VXD issues with Windows 95 here, because: VFBACKUP.VXD from AMDK6UPD (included in FIX95CPU) will crash WININIT.EXE when it tries to combine VXD's unless the modifications specified in the Slipstreaming instructions are followed exactly. The USBSUPP.EXE update (alone, and included inside the USP) makes several changes to VMM32.VXD and rebuilds it when installed. The failure of either one of these, or a combination of errors resulting from some "conflict" between the two could theoretically result in the error at hand. If anyone experiments with this issue, please post your results here. I am personally not a fan of Unofficial Service Packs, but I welcome any input from and/or to help those who want to use it.

I have also had problems with the Windows 95 Unofficial Service Pack. I do not recommend it, and it appears, from my experience and yours, to be incompatible with FIX95CPU. My advice would be to manually install any Updates and/or HotFixes that you need, and do not rely on the USP.

I do use Yahoo Mail Classic, always have, but the error I am referring to is not related to Yahoo Mail, it happens anywhere and everywhere at random. It has even happened on this forum before.

I'm having this problem on an increasingly regular basis with 98SE as well, so it's not 95-related. Had 3 of them in the past 5 minutes. Anyone have any suggestions on stopping this?

FYI, If you wish, you can run Firefox 2.0.0.20 or even 2.0.0.22pre on Windows 95. See This and This.

I don't know how "comprehensive" this is, but here's what I'm using: Don't recall where I originally downloaded it from now... All files extracted from a SFX archive: msie55sp2.exe 88,210,142 bytes Here's a DIR listing of the expanded contents. IEMIL_3 CAB 1,943,239 07-24-01 4:15p IEMIL_3.CAB ADVAUTH CAB 72,534 07-24-01 4:13p ADVAUTH.CAB AOLSUPP CAB 170,763 07-24-01 4:13p AOLSUPP.CAB AXA CAB 656,426 07-23-01 9:58p AXA.CAB AXA2 CAB 84,601 07-24-01 4:14p AXA2.CAB AXA3 CAB 207,529 07-23-01 9:58p AXA3.CAB BRANDING CAB 8,886 07-24-01 4:14p BRANDING.CAB DCOM95 EXE 1,228,544 07-23-01 9:58p DCOM95.EXE DXDDEX CAB 35,993 07-23-01 9:58p DXDDEX.CAB DXMINI CAB 339,279 07-23-01 9:58p DXMINI.CAB FONTCORE CAB 762,249 07-23-01 9:58p FONTCORE.CAB FONTSUP CAB 643,814 07-23-01 9:58p FONTSUP.CAB FULLSW CAB 2,619,137 07-23-01 9:58p FULLSW.CAB GSETUP95 CAB 286,985 07-24-01 4:14p GSETUP95.CAB GSETUPNT CAB 261,863 07-24-01 4:14p GSETUPNT.CAB HELPCONT CAB 366,307 07-24-01 4:14p HELPCONT.CAB HHUPD CAB 690,173 07-23-01 9:58p HHUPD.CAB ICW CAB 479,663 07-24-01 4:14p ICW.CAB ICWCON CAB 477,029 07-24-01 4:14p ICWCON.CAB IE_EXTRA CAB 208,385 07-24-01 4:12p IE_EXTRA.CAB IE_S1 CAB 1,448,221 07-24-01 4:12p IE_S1.CAB IE_S2 CAB 1,457,957 07-24-01 4:12p IE_S2.CAB IE_S3 CAB 1,457,957 07-24-01 4:12p IE_S3.CAB IE_S4 CAB 1,457,957 07-24-01 4:12p IE_S4.CAB IE_S5 CAB 546,382 07-24-01 4:12p IE_S5.CAB IE4MFC40 CAB 529,372 07-24-01 4:14p IE4MFC40.CAB IE4SHL95 CAB 906,219 07-23-01 9:58p IE4SHL95.CAB IE4SHLNT CAB 1,107,861 07-23-01 9:58p IE4SHLNT.CAB IE5COMP EXE 76,416 07-24-01 4:14p IE5COMP.EXE IE5OEM EXE 510,592 07-24-01 4:14p IE5OEM.EXE IE5SETUP EXE 511,616 07-24-01 4:14p IE5SETUP.EXE IEAK5 EXE 2,804,472 09-27-00 3:50p IEAK5.EXE IEAK5CD EXE 2,824,832 07-24-01 4:14p IEAK5CD.EXE IEAK5OPT CAB 3,324,529 07-24-01 4:14p IEAK5OPT.CAB IECIF CAB 16,837 08-03-01 7:05p IECIF.CAB IEDATA CAB 71,646 07-24-01 4:14p IEDATA.CAB IEDATAJA CAB 9,865 07-24-01 4:14p IEDATAJA.CAB IEDOM CAB 109,906 07-24-01 4:15p IEDOM.CAB IEEXINST CAB 22,819 07-24-01 4:15p IEEXINST.CAB IELPKAD CAB 122,295 07-23-01 9:58p IELPKAD.CAB IELPKAR CAB 305,214 07-23-01 9:58p IELPKAR.CAB IELPKIW CAB 312,913 07-23-01 9:58p IELPKIW.CAB IELPKJA CAB 2,885,870 07-23-01 9:58p IELPKJA.CAB IELPKKO CAB 2,296,003 07-23-01 9:58p IELPKKO.CAB IELPKPE CAB 1,936,091 07-23-01 9:58p IELPKPE.CAB IELPKTH CAB 411,248 07-23-01 9:58p IELPKTH.CAB IELPKVI CAB 444,709 07-23-01 9:58p IELPKVI.CAB IELPKZHC CAB 2,869,539 07-23-01 9:58p IELPKZHC.CAB IELPKZHT CAB 4,125,349 07-23-01 9:58p IELPKZHT.CAB IEMIL_1 CAB 1,321,886 07-24-01 4:15p IEMIL_1.CAB IEMIL_2 CAB 2,593,372 07-24-01 4:15p IEMIL_2.CAB ACTSETUP CAB 142,330 07-24-01 4:13p ACTSETUP.CAB IENT_S1 CAB 1,266,935 07-24-01 4:11p IENT_S1.CAB IENT_S2 CAB 1,457,959 07-24-01 4:11p IENT_S2.CAB IENT_S3 CAB 1,457,959 07-24-01 4:11p IENT_S3.CAB IENT_S4 CAB 1,457,959 07-24-01 4:11p IENT_S4.CAB IENT_S5 CAB 742,831 07-24-01 4:12p IENT_S5.CAB IESETUP INI 104 07-23-01 10:16p IESETUP.INI IEW2K_1 CAB 1,507,475 07-24-01 4:12p IEW2K_1.CAB IEW2K_2 CAB 1,718,383 07-24-01 4:12p IEW2K_2.CAB IEW2K_3 CAB 2,708,338 07-24-01 4:12p IEW2K_3.CAB JAAIME CAB 3,820,622 07-23-01 9:58p JAAIME.CAB KOAIME CAB 232,925 07-23-01 9:58p KOAIME.CAB MAILNEWS CAB 1,518,337 07-24-01 4:12p MAILNEWS.CAB MDAC_IE5 CAB 2,295,653 07-23-01 9:58p MDAC_IE5.CAB MOBILE95 CAB 416,943 07-24-01 4:12p MOBILE95.CAB MOBILENT CAB 391,763 07-24-01 4:12p MOBILENT.CAB MPCDCS CAB 567,271 07-23-01 9:58p MPCDCS.CAB MPLAYER2 CAB 1,322,008 07-23-01 9:58p MPLAYER2.CAB MSN_AUTH CAB 54,909 07-24-01 4:12p MSN_AUTH.CAB NM30 CAB 1,549,418 07-23-01 9:58p NM30.CAB OAINST EXE 477,936 07-23-01 9:58p OAINST.EXE OEEXCEP CAB 19,738 07-24-01 4:12p OEEXCEP.CAB README CAB 26,737 07-24-01 4:12p README.CAB SCAIME CAB 2,377,395 07-23-01 9:58p SCAIME.CAB SCRIPTEN CAB 504,615 07-23-01 9:58p SCRIPTEN.CAB SETUPNT CAB 756,215 07-24-01 4:12p SETUPNT.CAB SETUPW95 CAB 953,408 07-24-01 4:12p SETUPW95.CAB SWFLASH CAB 168,225 07-23-01 9:58p SWFLASH.CAB TCAIME CAB 658,724 07-23-01 9:58p TCAIME.CAB TS95 CAB 159,493 07-24-01 4:12p TS95.CAB TSNT CAB 162,552 07-24-01 4:13p TSNT.CAB USP10 CAB 148,376 07-23-01 9:58p USP10.CAB VBSCRIPT CAB 321,796 07-24-01 4:13p VBSCRIPT.CAB VGX CAB 812,828 07-24-01 4:13p VGX.CAB VMX86_01 CAB 2,465,378 07-23-01 9:58p VMX86_01.CAB VMX86_02 CAB 2,609,956 07-23-01 9:58p VMX86_02.CAB WAB CAB 557,203 07-24-01 4:13p WAB.CAB WEBFLDRS CAB 1,180,904 07-24-01 4:13p WEBFLDRS.CAB 89 file(s) 89,354,945 bytes

Ahh, the thrill of victory! I successfully modified SETUPSLT.EXE, removing the old REGSVR32.EXE and the reference to it in the .INF. Now it installs without any prompts or errors. And, to add to the success, I have successfully modified the IE5SETUP.EXE from IE 5.5 SP2 to install the Windows Desktop Update by default. No more installing IE4 and then having to upgrade again to IE5.5 for 95 users who want the update. See here for more info on this. Section: "Installing Windows Desktop Update...." All changes listed in Method #2 have been integrated into this new installer. Tested successfully on Windows 95C OSR 2.5.

Wow, I never knew I possessed any arcane knowledge.. Hope it has been of assistance to everyone.

Agreed But I have no clue how to do that. I can extract the files and modify the .INF, no problem, but other than some quick reading about IEXPRESS, I know nothing about compiling an installer.

When I first posted this thread, I was working with W95Y2K.EXE and W95EURO.EXE, trying to slipstream the updated files inside and so on. I have since learned a bit more about them. First, W95Y2K.EXE makes a lot of registry modifications, and these are not contained in W95Y2K.INF, so I was wondering how these were achieved. I now know from MiTeC EXE Explorer that "Y2KSETUP.EXE" is being run instead of W95Y2K.INF, so obviously that executable is responsible for the changes, but that doesn't help me when it comes to slipstreaming. Second, I was having trouble getting the Euro € character to be properly available in Windows 95 after slipstreaming the updated files from W95EURO.EXE. I found out that "EUROPAT.EXE" was being called instead of EURO.INF. I thought the EUROPAT executable was responsible for manually patching some file, but I have discovered this was the result of differences amongst various versions of GDI.EXE and/or GDI32.DLL, and a possibly "crippled" HotFix. So, the Euro problem has been worked around, at least for the moment, but the Y2K registry entries still remain a mystery. I have now also encountered another problem. A self-extracting executable SETUPSLT.EXE (inside WIN95_22.CAB, also Here NOTE the linked version is SLIGHTLY different) is set to run in SETUPC.INF during Windows 95 installation. It contains an old version of REGSVR32.EXE. I slipstreamed a newer version (from SPEU.EXE) into my 95 CABs, and now I'm getting a "Version Conflict" prompt during install. When SETUPSLT is called, It asks me to keep my newer file, which obviously I want to do. It is called with the /Q switch in SETUPC.INF already, and changing it to "/Q:A" "/Q /A" or any of the standard switch combinations either a)causes an error and SETUPSLT will close without installing (/Q:A), or b)it will "appear" to run, and not give an error, but actually does nothing at all (/Q /A). So now, I am faced with dealing with the Version Prompt during every install, or trying to "hack" SETUPSLT to accept the proper switches, or repack SETUPSLT without the old version of REGSVR32.EXE inside.

I gave it a try with version 1.5, no luck. It wouldn't even extract files from one particular update that dates from the IE3 era, and can be opened with WinZip or WinRAR I'll take a look at things with ResourceHacker, I looked some of the files over with another tool that dencorso referenced in another thread (MiTeC EXE Explorer) and it will show what program or INF is set to run, which helps some, but still isn't exactly what I need.

submix8c or someone else may be able to give you instructions for setting those things in MSBATCH if it's possible, personally I would look for the INF's that set things that way to begin with. I have completely eliminated the installation of AOL, CompuServe, Prodigy, and so forth from my Windows 95 install by simply editing MSINFO.INF and MOS.INF, I don't know offhand if these same INF's are present in 98 or used for the same things, but take a look around. Search for the string "msn internet access" inside your CABs, and take a look at any files that contain that string or a reference to something else you want to alter. It's too bad all of the work I'm doing in this department right now is with Windows 95, I haven't gotten to 98 yet, or I could be of more help. This all comes down to personal preference. On a clean install, I first install DX9C, then IE6SP1, then WMP7. Then I would apply any specific hotfixes or addons I need, like NUSB for example. I don't like "Unofficial Service Packs" because they always want to replace my Notepad or change my icons or tweak my settings etc etc, and often they do not play well with other updates or patches.

Well, you've come to the right place. This is the home of all the die-hard Windows 9x'ers. Sorry I didn't get back to your other post, I didn't know you had added anything else. But you have what you're looking for now. ^^^^ Welcome aboard

All of the CAB files are "linked" together, and files are "split" between them so that each CAB can be the same size, originally to fit on DMF formatted (1.68MB) floppy disks. Similar to splitting up a large file/archive with WinRAR, etc. To change one of them, you would basically have to rebuild the whole set. (That's what I've been doing in the thread submix8c referred to, using tools I purchased from rloew.) Any updated/altered file placed in the \WIN98 folder that already exists inside the CABs will be picked up by the installer instead of the "older" one inside the CABs. Obviously you have your own legal copy of Windows 98 to experiment with, but as submix8c stated earlier, you will need a product key that is appropriate for the install type.

My post wasn't really directed to you, it was for the OP, I'm sure you are aware of that particular method. I just thought that would be the easiest way to get around the problem at hand. A modified extracted SETUPX.DLL will be picked up by the installer like any other "updated" file placed in the install directory, no "need" to edit LAYOUT.INF, but it's whatever you prefer.

The GDI.EXE madness continues. In order to have support for the Euro € symbol in Character Map, one has to use the GDI.EXE from W95EURO.EXE. It makes sense to a point because it does have the latest version number... but on the other hand has the earliest timestamp. The GDI.EXE's from Q229670 and MSAA do not display the Euro € symbol in Character Map. It would seem that the last GDI.EXE (4.01.971) for 95 is inside W95EURO.EXE, and the last GDI32.DLL (4.01.970) is probably the one from MSAA. Leave it to Microsoft to make things overcomplicated, I wonder why they started a "4.00.1111" style versioning for OSR2 in Q229670 and then reverted back to the Original 95 style versioning? EDIT: It appears Q229670 has been the victim of some "editing" by Microsoft. The Hotfix file for Windows 95 does not contain the proper versions for 95 Original as I mentioned before, and also the files inside for OSR2 do not match the size attributes listed in the article. The Hotfix versions for 98 and 98SE seem to match the attributes in the article. I believe Microsoft may have purposely crippled this particular update for 95... Also, bristols sent me a copy of this Hotfix earlier, and it is totally different from the one available now, and apparently somewhat older than the one described in the article. Anyone else have a copy of this?

Is there a way to "disassemble" a self-extracting update or hotfix to see what specific instructions are carried out by the installer? I know how to simply "unpack" them with WinZip or WinRAR, etc, but I would like to be able to see the steps performed by the installer. I also know that most of what goes on is controlled by the .INF file inside, from examining them and also from reading some documentation on IEXPRESS at MDGx's. However, I have encountered a couple of updates that perform other tasks that are not listed in the .INF, and I'd like to see how they're doing it.

AFAIK All of the CAB's are the same, so long as you have a "full version" CD and not an upgrade. The only thing that is different and that determines the "Type" of install is contained in SETUPX.DLL like Petr explained here. Modify that file to make it whichever you want.....