submix8c

VLC is now at version 1.1.6 This from Google - /L=1033 /S for silent install using dutch language I believe that this is a NSIS install package with embedded MSI file. If you need FireFox support, you may need the Full package (different files used from IExplorer when used as a Web Plug-in). I also assume that the MSI is multilingual. That's all I've gathered so far. And... the notation above (the /L switch) may be incorrect. Relevant link here and here. edit - I may mean NSI, not MSI.

Compatibility. Do some digging on AGP 1x/2x/4x/8x slots. And, yep, voltage requirements are different.

Question 1 - Precopy1.cab "slides into" Precopy2.cab ("split"/"spanned" file via DIAMOND compression) you have to "re-cab" both using the correct DDF. Or unpack Precopy1 only (with both Precopyx in the given folder) then "re-cab". Repeat for Precopy2 - expect the CAB sizes to be different from the original. In addition, go look at LoneCrusader's thread for a tad more info. Question 2 - read LoneCrusader's (and my) post #43 above. Short answer - yes. I assume this is an "experiment" (an exercise in knowledge) since it's unnecessary for Clean Installs to modify ("hack") Setupx. That is, unless you intend/need-to "upgrade" a pre-98SE. I really don't think this is going to change your results (MSBATCH entries). I'm pretty sure I tested mine with a Retail 98SE and got the same results. The differences between versions has already been stated/linked (the OPK items are in all versions AFAICR).

Not delving into "warez", but there's a minor correction (AFAIK). Kind of... The "folder" mystically appears when slipstreaming pre-SP2 XP Professional since it (apparently) doesn't understand that it's not Media Center Edition (the second cd contains this folder). Retail non-MCE SP2 (and up) don't contain this folder at all. It's useless unless you have a version of MCE. And fair warning - if you have a version of MCE, better not "slipstream" SP3; it'll "undo" some components that aren't included in Retail non-MCE SP3 (e.g. Media Player 10). It's only useable on a running MCE. Nonetheless, safe to delete (MCE is a different "beast").(had to respond just to clarify...)

DDR = Double-Data-Rate (of FrontSideBus) 667x2=1333... Mine is DDR at 166x2=333

Well, FWIW... Apparently an OEM version "requires" extra entries, whereas a Retail one doesn't. I haven't tried this as I have been "reloading" old PC's using the OEM set; it's what they came with. I guess it's your personal option - extract and X-edit the SETUPX or just use a functional MSBATCH. I prefer the MSBATCH method as this doesn't involving "hacking" (as it were). BTW, statement stands - if you X-edit, then you need a functional Retail key. Kind of puts a google-search and retest-retest-retest on folks, don't it? Heck, even the Select and MSDN versions need a "specific" key. Win95 can be "cheated" directly via the MSBATCH (re the Key/Type; I've done it), whereas any Win9x above that can't. I may be wrong, since there's an "extra" set of entries that I don't use (and may do just that). @wsxedcrfv - Just try my version and remove any references to Presave and Postsave (they're similar to the XP version of TextMode and FirstBoot) to get a "clean" (no fixes, updates, etc) install, and insert/change those "extra settings" that you have; leave the rest in. You'll be surprised as all of the "optional crap" kind of "disappears". edit (before even posting!) - Aw, KRAP! the MSN is not "killed" until after FirstBoot (via a REG entry). Well, "sigh", I guess the UBCD topic will need to be revisited with Samples. I'm not sure how complicated it might get if you insist on installing from CD (Hard-Wired Letter Assigned, remember? Done via DRVCOPY.INF on Boot Floppy). I'll check into how to isolate specific processes for specific items. Anyway, here's the REG file - REGEDIT4 ; kills the MSN icon - i mean really kill, not just delete or anything wussy like that. [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Desktop\NameSpace\{88667D10-10F0-11D0-8150-00AA00BF8457}] [-HKEY_CLASSES_ROOT\CLSID\{88667D10-10F0-11D0-8150-00AA00BF8457}] [-HKEY_LOCAL_MACHINE\Software\CLASSES\CLSID\{88667D10-10F0-11D0-8150-00AA00BF8457}] Be sure to have a "blank" at the end to prevent failure (I think). edit2 - and here is the OEM stuff. You'll need to modify your Boot Disk. It "defaults" to the OEMSETUP in the CD-Boot (and the OEM Floppy Boot). If you use this method, Win98 "honors" the settings inserted into the HDD CONFIG.SYS/AUTOEXEC.BAT and that's what gets "set" in Device Manager. I don't know if this will "work" with a CD/CD-Boot Install (never tried it)... edit3 - WOOHOO! found some samples (on my HDD) of "Push" installs (for Intel NIC Network Install) that are relevant. And some more DRVCOPY.INF stuff. I'll/We'll get back to you if you have any more problems.

I'm not sure if ResourceHacker would show what you want. WEXTRACT is the prepended module; other data/processing is created during the IEXPRESS process. Been a while since I fiddled with it (IEXPRESS, I mean).

How much can I cram in here and reference properly; hmmm... After googling for...I came across...information....Windows 98 Upgrade (etc.)... Um, really? Fine, just what I said but with embellishments/AFAIK's. But if you reread, I kind of said that (i.e. "search"); you got specific; kool... Oh, and BTW, when you find those strings (with a hex-editor), extract and modify the LAYOUT.INF (also in a PRECOPYn.CAB, section [sourceDisksNames]) to point to the WIN98 folder (example at top of file, e.g. SETUP.EXE to prevent "extraction search") for SETUPX. The LAYOUT.INF is always picked up by SETUP.EXE. Not sure if this is actually necessary, but I'd rather do it that way (for testing purposes - I have stated versions).FYI, some Retails CD's did NOT boot and had a separate Boot Floppy (AFAIK). I have a Win98FE and it boots as well. Also, WinME Bootable has almost all 98SE files and 98SE has a couple of 98FE files. Better look at my "sample" again.The PID is generated based on the key and SETUPX.DLL (for which you must use the associated Key Type, i.e. ProductType). As I said, if you "fill it in", then that's what displays, regardless of the Type (it over-rides "Generated"). Not so "secret", kind of irrelevant maybe... The ProductKey has to appear in that same section as well to prevent interruption. The first occurrence is for "user entry", the second occurrence is the OEM Over-Ride (just like the PID). Absolutely necessary! Issues/Questions: 1 - Try adding this in the [system] section (see my sample) - DisplChar=16,800,600 ; DisplChar=Colordepth, x, y I haven't had a problem as long as it's a PnP monitor. If not PnP, I'll have to refresh my beanie... It's good to have the INF for it (if not in the MONITOR inf's) anyway (with INFINST). 2 - Section [OptionalComponents] "The Microsoft Network"=0 The other is the Internet Connection Wizard (ICW). Check out the [Run.Installed.Components] Section (2nd set). If you want, just "trace down what gets processed" in that part and keep anything "pointed to" in. In addition, check out the other two "sets" of entries to remove stuff and/or set stuff. 3 - I'll have to get back with you... It "disappears" somewhere (a/l w/UBCD)... edit - YOU POSTED BEFORE I DID!!! And I again recommend reviewing mine. It does all of that and Pre-(during TextMode) and Post-(after FirstBoot) processing. I'll have to look the BAT files over for that to give examples. As I said, this is "basic info" being provided from the now-defunct UBCD thread. edit2 - DANGIT! I don't know if the [installLocationsMRU] section is relevant or not (I rechecked you INF; should be nearly correct). BTW, you did add the OPK stuff in the [install] section right?

Have you, by chance, installed SE-to-ME? The ME "explorer.exe" (AFAIKR ) has a side-effect to it that keeps forcing you back to "View As Web Page". If you did, go to the MDGx website and take a look; I believe there's some info on that...

Here (more-or-less accurate). And there are differences in file content as well, e.g. Type 112 is actually (AFAIK) a "Step-Up" and is "incomplete" (steps FE to SE). Select and MSDN are almost (literally) the same as Retail, as is Upgrade (but not necessarily). There are ways to "cheat" for installs (same as the OEM's did) but I'm not saying (info is already on WWW). An example is the Type=120 where the OEM's used the MSBATCH.INF (perhaps using Select?). AFAIK, MSDN and Select used MSBATCH.INF for the Product Key. Not really sure about the 103,104 (Floppy? Not so sure as that's a lot of floppies!), and 105. They may be more relevant to the Win95-series. I've yet to see any of them or types 116 or 120 (except the 120 using MSBATCH.INF). I'm assuming this has to do with the full OPK, even though it "appears" to be on the single Cd, I'm betting there's a second one containing further info and software (e.g. PISETUP.EXE? Not Picture-It! on the HP OmniBook Recovery CD). Rather not go into all of the details. It beat my po-widdle-head to death figuring this out. I have (so this info is more-or-less accurate) - Retail Upgrade MSDN Select OEM Step-Up (incomplete - cabs are definitely different)

Yes, I'm aware of the OPK stuff (mkcwrt). No, the OPK doesn't tell you everything. Yes, some items the OEM had to subsequently "manually" modify and/or "run" during setup. I have a "sample" (somewhere) that allows selection of Win95 or Win98 for the OS to use (uses a MINI-Win). Unnecessary for your purposes (unless you just want to fool around). Suggestion... Take mine, compare to yours, ignore anything irrelevant, and insert into yours anything relevant (and missing). The OEM portions are the most significant (as to the notations). The "ProductType" entry is for OEM usage and is irrelevant (yes, inserted from the SETUPPP.INF). They sometimes used an "upgrade" variation and used it to "reset" it to OEM (or whatever). Explanation - OEMDrivers is to "point" to where you put your Drivers on the HDD. Appears to have to hard-code the locations... Some OEM's "hard-wired" the Installation CD to a certain CD-ROM so it "worked". OPKInstall is to pre-set certain values. Bear in mind that OEM's were required to display some kind of EULA and potentially would force a Buyer to enter their Name and Org or have something like "Valued XXX Customer". Fiddling with this is the way I/We discovered the "required to prevent interruption". So... YES! Give the changes you say a shot. Proceed... you have the idea

And inside the the IMA is TXTSETUP.OEM, which loads the drivers (both of them) PriorTo/During TextMode! If you GOOGLE on the Filename MS is the first website to pop up - the info is there. Why are you bothering us to repeat MS?Dude, have you even bothered to look inside? Use it, don't use it... your option. No "Cave Man Explanation" is available since a "Cave Man" needs to understand HOW fire is made BEFORE trying to MAKE fire! Best to obtain Prerequisite Knowledge (other Topics, even at MS website) before accusing "Author" of leaving info out (intentionally, I might add, since info is available elsewhere). This is an "extension" of other Topics addressing a specific solution, not an "All-Encompassing" Topic. ..am I missing the boat? reference is here. honestly haven't tried this out yet, but my other statements stand. (err, cdob posted same thing as I edited this)

Well, off-topic (kind of)... Interestingly enough, IE6SP1 doesn't include that particular CAB file (AFAIK) but does have the NT-version. You have to "plug it in" from the IE55SP2 set. Th reason being is that it's "assumed" that the 9x series already has IE installed (excluding 95 RTM without it) and these are all simply "updates/upgrades". IOW, you must have at minimum IE4.01 and maximum IE55SP2 installed before IE6 (AFAIKR). Best one to install is the IE55SP2 (unless you "jigger" IE6SP1 to include it) then "upgrade" (depends on the version of 9x in question). OK, Nuff said... "Move on, nothing to see here..."

Thanks for that mate! That was all I needed, and means I do not have to continue my vain search, not to mention that file was nice and small for my poor little Aussie internet connection THX, LoneCrusader! Was just looking for the correct one to point to... Done!

Just to let you know... 1 - You didn't even bother to look in Explorer before you posted (and then edited). 2 - Yes, "far stupider", but persistent stupidity yields somewhat "persnickety" responses. 3 - If you'd have looked in the Stickies, there's one that points to another topic giving a whole slew of Stickies, one of which contains a list of every known "fix" for 9x systems (including one that references Icons). 4 - If you want to understand 9x you should have installed and maintained a 9x system previously (have you?). 5 - Common knowledge that the Desktop is "controlled" by Explorer (at least I thought it was). And last... 6 - I will apologize for being "persnickety" provided you do more research before insisting someone else do your legwork. (I just KNOW a Moderator is going to spank me sooner or later...) edit - And... 7 - I note that you've Double-Posted! Here's your Sticky. (ref. Hotfixes, Patches + Updates) edit #2 - Private message sent to clarify... let's not beat the dead horse, as it were. Spank Me Not - unnecessary...

Uhhh, DUDE! Didn't I tell you EXPLORER.EXE? GET it and LOOK INSIDE... They are there! Links provided on MSFN - go look... (in the Win9x section STICKIES!) (SHEESH!!!)

To Question Number Two - Yes, they are OEM.To Questions One and Three - Please, please, PLEASE REREAD my MSBATCH.INF notes (inside) that SPECIFICALLY references your particular problem. (YES, I re-inspected mine and it's an OEM version and even told you which sections are "missing".) I don't even have to touch it as it runs Fully Unattended. MS does NOT tell you everything in KB's, the rest is within the OPK (of which I have no clue where this Win9x "package" is as it seems to not exist).

OK, you want a whole SET of Icons that MIGHT be scattered throughout the system. That particular Icon is within EXPLORER.EXE. Easily found in multiple versions of Win9x and/or IE4/5/6. (EDIT - also within several MS Update packages, links provided on MSFN - go look...) Please do NOT ask for "uploads". You want, go Google. We don't upload proprietary software here. Maybe you'd better do a Google search on any particular Icon Name that you want to find out which module it's in before asking for it. All we'll do is point you to a legitimate link, and even at that you're asking US to do the legwork for YOU!

"Resource Hacker"... (a legitimate and widely used file resource editor)

READ the posts again. DOWNLOAD the package and unzip. LOOK inside the IMA file (any IMAGE utility here)... inside is a "txtsetup.oem"... OPEN it with editor and look inside. READ the first post as to what needs to be added and/or changed. As was stated, the F6 is unnecessary as the BOOT TO ISO will AUTOMATICALLY "read" the IMA file (simulated floppy) during SETUP (from the ISO). It's all there... (re-read jaclaz' "basic vs advanced"). This forum doesn't "spoon-feed" anyone. It ASSISTS; after that you're on your own... (yes, YELLING, as you are not listening/reading...) edit - provide links to "useful" free utilities.

?Is your shell32 broken?

Then you didn't read the whole thing.1 - You need (if you don't have) the Update File installed. (REQUIRED) 2 - There are multiple "We''ll Fix It For You" clickies, either "Disable" or "Enable"... Go back and take a look-see...

There was another "fix" at one time that was part of MS Updates (can't remember which/when) that changed the behavior. Look here for some more info (and another "fix") that may be relevant.

Now you're in a different subject/problem. SATA Controllers requires special drivers. Try going into the BIOS and change the SATA Mode.