submix8c

You're missing the point - the keyword is running system. If you have upgraded 98 with XP, then you must upgrade to SP1a first or SP3 will be blocked (needs SP1a on a running system). For your purposes, the CD is not a running system it's simply an Install/Upgrade CD. All fixes on the SP3 include all prior fixes. You are slipstreaming the SP3 into the CD's contents (replacing/adding/removing what's in the original) thus, in essence "creating" an XP with SP3 Integrated (as if you bought an XP Pre-Integrated/Slipstreamed SP3 CD). Maybe the terms "slipstream" and "integrate" are confusing you. (?) IOW - 1 - Integrate/Slip SP3 into the Original Upgrade per instructions 2 - Install (or not...) 98 3 - Upgrade (if "not" in step 2, provide the 98 CD when requested) 4 - Voila! XP with SP3 is now "running"

Well, this may/may not help - nLit\I386\AU.IN_ Content+Size nLit\I386\DOSNET.INF Content+Size nLit\I386\FONT.IN_ Content+Size nLit\I386\HIVECLS.INF Content+Size nLit\I386\HIVEDEF.INF Content+Size nLit\I386\HIVESFT.INF Content+Size nLit\I386\HIVESYS.INF Content+Size nLit\I386\HIVEUSD.INF Content+Size nLit\I386\INTL.INF Content+Size nLit\I386\QMGR.IN_ Content+Size nLit\I386\SFCFILES.DL_ Content+Size nLit\I386\SYSOC.IN_ Content+Size nLit\I386\TXTSETUP.SIF Content+Size nLit\I386\WBEMOC.IN_ Content+Size nLit\I386\WMP.IN_ Content+Size Orig\I386\NHELPER.EX_ SourceNotFnd <-Helper Orig\I386\NLITE.IN_ SourceNotFnd <-Directive nLit\I386\SYSSETUP.DL_ Content+Size <-Temp for nLite nLit\I386\SYSSETUP.IN_ Content+Size <-Temp for nLite Orig\I386\SYSSBCK.DL_ SourceNotFnd <-Backup Orig\I386\SYSSBCK.IN_ SourceNotFnd <-Backup nLit\I386\APPMGR.DL_ TargetNotFnd nLit\I386\CLOCK.AV_ TargetNotFnd <-(ignore) nLit\I386\CONF.AD_ TargetNotFnd nLit\I386\GPEDIT.DL_ TargetNotFnd nLit\I386\GPEDIT.MS_ TargetNotFnd nLit\I386\GPRSLT.EX_ TargetNotFnd nLit\I386\GPTEXT.DL_ TargetNotFnd nLit\I386\GPUPDATE.EX_ TargetNotFnd nLit\I386\HISECDC.IN_ TargetNotFnd nLit\I386\HISECWS.IN_ TargetNotFnd nLit\I386\INETCORP.AD_ TargetNotFnd nLit\I386\INETRES.AD_ TargetNotFnd nLit\I386\INETSET.AD_ TargetNotFnd nLit\I386\RSOP.MF_ TargetNotFnd nLit\I386\RSOP.MS_ TargetNotFnd nLit\I386\RSOPPROV.EX_ TargetNotFnd nLit\I386\RSOPSNPW.CH_ TargetNotFnd nLit\I386\RSOPW.CH_ TargetNotFnd nLit\I386\SECPOL.MS_ TargetNotFnd nLit\I386\SWTCHBRD.BM_ TargetNotFnd nLit\I386\SYSTEM.AD_ TargetNotFnd nLit\I386\WMPLAYER.AD_ TargetNotFnd nLit\I386\WSECEDIT.DL_ TargetNotFnd nLit\I386\WUAU.AD_ TargetNotFnd nLit\I386\YAHOO.BM_ TargetNotFnd <-(ignore)The above is what nLite did when I removed ADM Templates, GP MgmtCons, and: Lcl Security Settings - Part of Administrative Tools which can be used to easily edit: - Password Policy - Account Lockout Policy - Audit Policy - User Right Assignment - Security Options Needed for: - Group Policy Management Console Some differences are obvious based on removal. I could upload the INF's if that would help; don't think just those would violate any rules... Really stoopid question - What's the Security within the Registry? Allowed to modify (e.g. Admin rights as a Logged-on Admin)? EDIT (to answer myself) Obviously do, since register/reregister a/l one DLL...

Upload that file to virustotal.com and tell us which AV products detect it as malicious.Hmmm.... "File Unknown"...

KB923561 mentions a permissions/work-around problem. I note that you're showing the C-drive in that post. What method of delivery of the CMD and hotfixes? Copy-and-run (click on CMD) all fixes for each PC? Copy CMD only and run from a mapped drive? User Logon Script? Help us to help you. Please give more info on methodology. Just a script without a delivery method (100 PC'S!!!) doesn't help us understand "what's going wrong"; All above info provided by "Helpers" thus far is correct. BTW, this indicates that the mentioned "fix" has been superseded. Maybe you can't apply a hotfix after a newer one has been installed. However (noting the contents mentioned from the link given), may/may not be correct (the fix you mention has additional components). You are installing in the correct order aren't you? Have you tried the MBSA yet to assist in getting the complete updates list? (Please note again that I haven't done mass-rollouts of Hotfixes.)

Did you not see my comment requesting more info? You presume too much.IOW, what Hardware does OP have and have access to (Another PC? Maybe not...)? What OS's are being installed (other than 98SE). Did I not mention "Bootdisk-DOT-com" (provided a Floppy is there)? Such a long post/rant with so little little to go on. DUDE! Take either the Red Pill or the Blue pill! (Jet lag I presume?)

Sheesh! Several "unnecessary dross"! Java Updates+Quickstart could be disabled for example (in the Console). There may be some installed that have Services (not familiar with one or two) that you may have to Disable. Otherwise, CCleaner and/or SpyBot would work for the "Startup" and "Run" types (they "move" the StartupFolder/Registry entries). You might want to check what you really need. EDIT - see next post. and thank you, Yzöwl, for the clarification of Disabled vs Manual.

Windows Updates Downloader (WUD) and/or using several lists (usually links available) gets all/most updates. Also, Microsoft Baseline Security Analyzer (MBSA) from MS may/may not help. There's no (AFAIK) script available for actually applying the updates to a running system automatically. This you may have to write yourself and it would all depend on what is/isn't already on a given PC. Only other alternative is perhaps nLite+the updates+rollout-reinstall. Even slower (would have to go to each PC to run) would be AutoPatcher (not an MSFN member project, but sometimes recommended). What do you mean by "temp folders left behind"? Referring to the "Windows\SoftwareDistribution" folder? edit (before even posting) - OOPS! You can't use nLite for a Commercial Rollout, but it may be good for using to help understand what would be needed. nLite is NOT allowed to be used for other than Personal Use (in the EULA). Tools/lists for obtaining the updates are fine for your purpose since the updates come directly from MS (in line with MS' EULA). edit - (SEE NEXT POST) - There ya go! The method of delivery will be up to you and probably will (not tried myself since I do unattended) either re-install or be ignored (if already installed). Also note Hotfixes are different than App Installs (e.g. IE7/8/9, WMP10/11, DotNET, etc.) so set your BAT/CMD up accordingly (switches, order of install, etc.).

The poster apparently wants to install 98SE and -other OS- (dual-boot) has no boot floppy to allow for partitioning. In addition, the 98SE is apparently an OEM Bootable, which by default will want to create a partition occupying the whole Physical Disk (runs OEMSETUP).You could just go ahead and install, then defrag, then use a gParted CD (free Linux-based) to re-partition (shrink 98SE then create new). If you have a Floppy, go to BootDisks-dot-com and download an appropriate boot floppy image. Please explain your intentions/objective more clearly for more accurate assistance.

Does this work for XP as well? Appears to be for Windows 7. Poster requested help with XP, not Seven...

This is the Unattended Subforum - this suggestion does no good.

Found elsewhere (not giving link because this had proprietary files) explaining how to add to XP Home. Apparently, what's in XP Pro. • Copy the following files to %WinDir%\System32\ folder : • appmgmts.dll • appmgr.dll • fde.dll • fdeploy.dll • gpedit.msc • gpedit.dll • gptext.dll • Create the following folders (if they do not already exist): • %WinDir%\System32\GroupPolicy • %WinDir%\System32\GroupPolicy\ADM • Copy the following files to %WinDir%\System32\GroupPolicy\ADM\ folder : • system.adm • inetres.adm • conf.adm • Open a command prompt window by opening Start Menu → All Programs → Accessories → Command Prompt. In the command prompt window type the following commands pressing Enter after each line. regsvr32 %Windir%\System32\gpedit.dll regsvr32 %Windir%\System32\fde.dll regsvr32 %Windir%\System32\gptext.dll regsvr32 %Windir%\System32\appmgr.dll regsvr32 %Windir%\System32\fdeploy.dll • That's it. Now you can open Group Policy Editor by opening Start Menu → Run, typing gpedit.msc and pressing Enter. HTH

Will TeamViewer work for you/help in any way? I've used it along with a cousin in Florida to fix the sound on his PC after he "upgraded the OS" on it. The Full Version download and an accompanying package (unnecessary) can be used free for home use. Additionally, you can run it and tell it to run StandAlone without install. Worked pretty good and claims to be supported 98 thru 2k8 (as seen in the link). Browse around the site for more info. P.S. Very similar to Remote Assistance (two-ended execution with a "session-id" and "password") but not exactly (more features). Also claims to allow for multi-networking (more than just two interacting PC's). (GUI - not text)

Hmmm - This which will lead to this indicates a possibility of Simple File Sharing being a culprit. As I remember (maybe not so good), if SFS is installed/enabled, the Network Setup Wizard has to run, thereby sharing the "Shared Folder" (a "pointer" seen in the Network) across the network. Without it, you can manually share using the Share File/Folder functions but you won't automatically (I think, anyway) get the All-Users/Shared Folder (have to do manually). Being aware that without SFS, Private Folders have to be manually done via the ACL(?) of the folder. (IOW, adding a password to the signed-on UserID won't provide "Make My Folders Private" option.) Ehhh, could be totally off my rocker - been a month or so since I fiddled with some of this. I'm sure someone smarter than me will smack my hand for passing out bad info. BTW, Network Setup Wizard default fills in MSHome but it can be changed to whatever you want as a workgoup ("WORKGROUP"). One of the side un-benefits of it ignoring the already-set value (duh!). Side note - SFS is the "standard" for 9x systems.

Please read the big bold red sentence at the top above, otherwise no-one has a clue as to what/how you integrated. IOW, how can anyone help with the scant info you provided? It could be any number of reasons. It might also help to provide computer specs (MoBo, HDD/CD connection eg IDE/SATA, etc.).

Heh, I remember one Major Manufacturer of CD's that installed a rootkit. Go figger.My 2-cents. Agree with the "your decision" response. And the suggestion of the "sandbox" if it's going to cause a conflict. Finally, true that some files are considered "trojans/viruses", etc, but even a UPX'd file (perfectly legit) can be flagged (repeating jaclaz' assertion). Bottom line, do what's best and consult with Mom. If she wants to "take the chance", then SANDBOX and teach her how (in addition to a fail-safe backup of a stable/clean system). Don't forget ye-olde warning about storing passwords, card account #s, etc. Everyone has an opinion, just like they have a (you-know). May clash with "technical", but, hey, you get what you ask for.

Needs updated and a minor correction... ONE of the MP-11 fixes is NOT for MP-11 (I checked the KB#'s while attempting to "slip").

May the Great One take her by the hand and walk her in. Hang, brother, and smile when you think of her.

There's a sticky (somewhere) for a list of all the Win2K fixes. Search that sub-forum. A link is given to another site that has everything as-of the "dropping of support". edit (and see next post) - look here also.

No, I want to integrate all XP and other updates that go with XP using nLite and make a master XP install DVD, but that doesn't seem possible, as I've read an integrated update breaks something or the update can't be integrated. I already have an XP CD with SP3 slipstreamed. At this point, I'm just playing the waiting game, and in late 2014 when XP updates are done and the mod makers smooth it all over, that's when I'll do that.Uh, uh! nothing "breaks". You just have to do subsequent integrations "fresh" as if done for the first time, not "integrate on top of a previous integration". Fresh only! No Probs! Where did you read "it breaks stuff"? Never seen it...Have you read nLite instructions? It specifically states "start from untrammeled source" and it's been stated everywhere repeatedly. (sheesh!) Integrate yes! Re-integrate NO! (make up my mind... I thought you stated you didn't want to integrate because of all the future updates. is the fear of not being able to integrate future updates the problem? start afresh each time and voila!)

Never said what caused the "!". Conflicts (or not)? I just finished doing battle with a modem under 98SE (just got a newer mobo/cpu) and had to switch to an Agere because the NetoDragon insisted on using a memory range already occupied.Ennyhoo, good luck! (currently battling a "not-phantom" drive (really is Fat32, and OK under XP, but "unformatted" in 98SE).

1 - Get WinImage (Trial Version will do) 2 - Read Disk#1 and save it as an IMA (not IMZ) 3 - Copy all Files/Folders from the Floppy to a "Hold" folder 4 - Copy all Files/Foders from Floppy#2 to the same "Hold" folder 5 - Change Format of the IMA in WinImage to 2.88 6 - Import the contents of the "Hold" Folder into WinImage 7 - Save new 2.88 under another name - - (you already have the original 1.44 floppy set as "backups, so no prob) There are only a few files/folders in the Floppy#2 that are not on Floppy#1 (wouldn't have fit onto 1st 1.44). The Autoexec.BAT is exactly the same between them. You might have to alter it so it doesn't ask for Disk#2 (don't remember). Most Burning Software allows you to specify an IMA (NOT A COMPRESSED IMZ) as the Boot Image ("expert" feature). Norton/Symantec does this with their AntiVirus CD's. 1 CD with a 2.88mb Image to boot from (in the CD "boot sectors"). Um, hope all of those PC's have the same Network Card, otherwise it's gonna get "hairy"... (note: can't remember if you need "floppy emulation" or "no emulation") EDIT! DOH!!! TurricaN, this is an ANCIENT topic you bumped...

Not performance but compatibility/functionality.Some things may "fail". You could just turn off the "web integration" parts or just go with the standard "Lite" instead of "Sleek".

uh, not if you can "slipstream" them.I've also done "repair" installations of XP with integrated/slipstreamed SPs/updates on a few XP computers and I had no huge problems with them. sure some personal settings may get resetted but it's no big deal. vipejc wants to not slipstream so as to "keep updates separate from the install". I would, however (with that in mind), go along with slipstreaming the SP3 (if pre-SP3).

Honestly, I've never heard of it being done any other way (successfully). An "over the top" reinstall (aka "upgrade in-place") usually works but you have to reinstall all of subsequent the SP's/hotfixes again and (maybe) retest all of your apps (to make sure nothing got clobbered). I've done this before and haven't found a problem with it. Just time-consuming (which is what you're massively losing right now - time!).

Did you try the "off" parameter?