submix8c

Semantics... CDA is the "pointer" (if you will) to a WAV file playable in a "normal player". Many CD-burning programs will convert MP3 (and other formats) to WAV when the correct options are set (in addition to creating an AUDIO cd, not DATA cd). Just check in "bloated" burner software (e.g. Nero) in the "view tracks" - there's a WAV track for each CDA "pointer".

I wouldn't mess with the Swap File unless you do a little reading on the subject first. You could lock your computer up, depending on how much RAM you have.

FWIW, there is a German nLite forum (win-lite.de). (near-wasted post in the context of the topic/discussion; just felt this needed added).

I tend to agree with herbalist. Doing a search on just "tenga virus" (without quotes) yields some interesting results, one of which is "downloader.dnx" (and very little on this one; did you mention it already? didn't notice). It indicates multiple variations of several trojan/viruses using various methods of attack. Somewhere in your Registry is a Run/RunServices/Runonce in HKLM and/or HKCU (or maybe even Default?) that could even be legitimate name but already infected. Risking another isolated OS connected (however done) to the isolated infected one may indeed help. If possible, maybe you could dump the 98's registry in DOS using REG.EXE then inspect it and compare the file sizes in the entries in question to unaffected ones (maybe in DOS using DIR). You're going to have to Sandbox sufficiently (radically) to detect, isolate, and destroy it. Mainly, if the OS is infected and connected to the internet in any way then you're subject to further infection by other "tenga" variations. You have a real nasty there... Good luck! edit - also worthy of note is LiveXP to get a copy of the System Hives to an uninfected PC for inspection. Remember that "stealth" trojans tend to erase (e.g. RunOnce) registry entries to avoid detection of their true names. edit2 - beware! search on "tenga virus" also yields more than a few very suspicious sites.

Find the topic on "OEM Preactivation". There you'll find the info (maybe) you need to use your preexisting HP-install to create a useable HP cd. edit- the bad part is that if you can't get anything off of that HDD, you may be screwed. edit2 - you may have answered your own question in post#5. Often the OEM's will supply a "near-RTL" CD with "certain items" that may be different. Google a little to find the final answer. I don't want to give specifics here...

Uhhh... XOSL errp... correction - see next post (obviously)

Look again (inside Precopy2.cab, LAYOUT.INF and "find" it). It's there... (in WIN98_54.CAB)

LoneCrusader - Posts=156 / Joined=11-May 09 jaclaz - Posts=5,824 / Joined=23-July 04

Won't swear to this, but it might be the Explorer Folder Options "Use Web Style" is ticked. I use the Classic/Custom, so mine doesn't react that way (different message).

Make sure the one you want to install to is the Primary. Boot to the Legit CD. Choose "Install". The current OpSys (on the HDD) will be detected. Choose "Repair" (maybe Upgrade, depending on what's already there) and go. Do-Not choose "Repair" on the first screen(s). Since you now have a Legit, you can Upgrade (and perhaps "fix") the XP Home -OR- "overlay" the "bad" one with the Legit. One or the other... (OR wipe the "bad" one and install "clean" on a new HDD - all your choice.)

FYI - go here, scroll down to "WIN98 VXD BUG" (about 3/4 the way down). 3 tools for manipulating VMM32.VXD/VXD's plus a "how-to" link for rebuilding. Use at your own risk. edit (to answer your post) - One of them will "de-construct" it so you can see the contents. Just copy the VMM32.VXD to another folder, copy the appropriate program to it, open an MS-DOS prompt, switch to that folder and run it. Read that section to understand how they work and how to use them. I guess I could take time out to do this again to give specific instructions, but I believe you can run the program(s) with "/?" as operand and get specific Help (same as most other programs). And again, VMM32.VXD is BUILT.

That would be me... Explanation - VMM32.VXD is "built" during installation. Within VMM32.VXD are the actual VXD's that are "merged" into a single file (VMM32.VXD). There is a utility (somewhere) that will "un-build" it, but it's a little irrelevant in the context. The point was to indicate that it was an "initial unblemished build" of VMM32.VXD. If you look in Device Manager and see "VMM32.VXD" for any given Device (in Driver Details), you'll also see the Sub-VXD's listed. An example is the Display Driver - look in Driver Details and you'll see the Sub's within parenthesis. Further reading through the thread, you'll get more information on the rationale behind giving this information. Do read the whole thread. Also note that I'm not the only one to list it that way... HTH

1 - Use VORCK as the "list" (maybe another, e.g. MSFN, for comparison?) 2 - Collect the files from the WUD download (or manually via any given "list") 3 - Compare WUD to VORK (or "other") for discrepancies (if any) 4 - Try it (the slipstream + test install) 5 - Go to MS for scan (note - may be necessary to install ALL from ADD/Remove) There have been, in the past as in the present, conflicting reports of the "complete" list and where to obtain "it", so I suggest you just try it yourself.

Misinformation - perhaps due to confusion. Hostility - personal perception only. The solution/patch was for RTM and requested further investigation into the later OEM versions.Forgot to mention - all in that thread (but one) have been around a long time, are extremely knowledgeable, and have high respect for one another.

I'm not really sure the OP intended to "open it up"...Since someone suggested Ghost, marry that with my Original Suggestion (LapLink cable), and use the Peer-to-Peer option. 1 - Connect the cable 2 - FloppyBoot Target PC (waits for "client") 3 - FloppyBoot Source ("client") PC 4 - Ghost-away!!! No matter which way you slice it, there's no "free"/"simple" way to do it. - An external solution requires purchase of associated hardware and opening the Laptop. - A Software solution is... (think I just said that) but requires purchase. * Alternative Software solutions that work like Ghost (as above)? Dunno... In summary... Was I arguing/disputing?

Why the suggestions to use USB ("removal" would work)? Did I miss something?

Looks like that's the one... Lots of extraneous stuff there you may not want (e.g. the OEM folder). Probably the DRV folder is the OEM drivers, APPS is the pre-installed "Extras", and SP is additional HotFixes. The method (as depicted) appears to just "rebuild" the HDD (pre-install) then copy the folders onto it. To clarify, a normal I386 folder has - (files as seen) ASMS COMPDATA DRW LANG SYSTEM32 WIN9XMIG (not needed?) WIN9XUPG (not needed?) WINNTUPG (not needed?) Won't swear to this, but nLite may accept it "as-is" (renamed, as MrJinje stated above).

Yes, (brother's PC). You'll need to get rid of it via Clean Install on another HDD then "MBAM" the offender before it can be used again. Lots of cleanup afterward even after being MBAM'ed. The culprit was undoubtedly that file. Other files are just floating all over under wierd names and run again from the Registry ("runonce", part of the "cleanup"). BTW, you need LSPFIX because that's what's preventing the updates (I believe). Since you already reloaded....

?another PC using LapLink (COM/LPT ports, "copy" not "image")? Note: You can usually find most prebuilt Linux components, but you still need to boot to Linux to use them. Did you plan to re-size the HDD??? Anyone else???

An example (from pre-Vista) (Documents and Settings/Me/SendTo folder)... Please note this is info-only (what I have)... 3 items (compressed, desktop, mail) are "directed" (maybe just the Icon indicators?) via the contents of DESKTOP.INI (and I believe the registry as well). 1 item (My Documents) appears to be strictly a registry setting (not in DESKTOP.INI). 2 items are shortcuts. FWIW, never heard of actually copying the app to the SendTo folder. New one on me...

Sounds like "exotic" (informational, and agree with Ponch, but could be wrong)... As a general rule, these types have some sort of "image". The contents of the "image" usually has the I386 (etc.) within. To nLite something like this, you should make a "copy" of it from the HDD (so you don't accidentally wreck the original). Find it, compare the file-list to your friend's Dell disk (or to any Retail). Note that contents will not be "equal" if of a different SP-level. Also some files may not be in the I386 folder (intentionally) but will be elsewhere "decompressed". Bottom line, you need a "complete I386" to work with. Find the thread on Manufacturer Preinstalled/Preactivated (?) for additional info (but just a little more, re: "some files"). Other than that... Sorry, you may be on your own (getting the "complete I386", that is).

Additionally, it may depend on the app in question as to how it "exits" and/or whether it calls other subroutines (e.g. dual-extract/execute... one-inside-the-other)???Perhaps this is the reason the original recommendation was "start /wait" (cover all the bases, regardless). Ennyhoo, a good learning experience with relevant information as to "how/why". Aaannnd... Edit!!! I re-read above; only says "removed wait"(See Next Post/Prev Posts)...

Go Here Scroll to "Search - Advanced Options (Set as Default)" Get the REG file next to the first "Tip" Remove the last 2 lines of the REG file. I use this and works fine without ticking the "Advanced". If after the RegEdit fix, you do by chance tick the "Advanced", you'll see the others are already Ticked. HTH (works for me)

Info/clarification only... No new one would be generated. WinME might (don't remember off-the-top-of-head). Generally, a minimum (not "required"; can be "null") file-content for any TXT-type file (including above) is CR/LF or more specifically "x0Ax0D" (ASCII), similar to manual typewriter "pushing the bar to the left right" placing the next "input" left and down. This "combination" is the "delimiter" used to detect (loosely) "end of input" (exception "null" which is ignored, i.e. "empty/0-length file" or "no input"). True - EmptyLines=CR/LF=NothingToProcess (GoToNextInput). If you want to keep any lines (say, for posterity) just put ":: " at the beginning (same effect as "REM "). The same can be done in CONFIG.SYS (to "keep" old entries) by using either "; " or "REM " (?). Using the alternative-to "REM " makes it more readable (IMHO).

AFAICR (been a while), it breaks them down the same way WU/MU would (Critical, etc.), hence the FolderNames (?may be wrong). I believe it uses the XML from MS to determine where in MS' File Repository to download the Files directly into the associated folders. The method of slipstreaming is at your discretion. The list of fixes necessary for your "flavor" of OS is posted multiple places/threads, also sometimes broken down into categories. Sometimes it's a matter of experimentation. WUD is primarily a method of getting everything "it" knows about in a convenient way. It uses the MS-method that MS' MBSA (search MS for that) uses except it doesn't scan your computer for "what you need", it just downloads all "latest" fixes. Cross-reference any given list against what WUD (all of files) downloads and proceed accordingly. HTH