submix8c

...or do you mean his Post#5? (Hmmm, tomasz86 is usually correct...) Go this route if you're having problems (read it thoroughly). Using this, I believe either HFSLIP or nLite could be used. BTW, if you download Fixes using a Downloader (e.g. Flashget and get the links AFTER canceling the Download and use Direct Link), you can "sort" the Fixes in nLite to ensure Install Order according to oldest->newest. Normally, I tend to "shy away" from Update Packs (again, read the provided link). edit - And since you already reinstalled, might I suggest that you "split" your HDD and do another install (the same way, or get a utility to "shrink" it, e.g. Gparted Live ISO burned to CD and booted to). That way you can "test" your SlipStreams (however you do it) on the second (to be defined) Primary Partition.

Be sure to note Posts#2+#4 (Tripredacus' MSFN link) - you need a TEMP "folder" (any name will do) to load a HIVE (same as using Regedit as in my post above).

Cheater! I know how you did that... -X- got the set directly from the Acer website (not Intel, as Ponch pointed to). They will be fine, BUT, you have to "extract" BOTH the Original AND -X- ZIP file. I used WinRAR to decompress the Acer, but you can "run" the Setup program inside (do NOT install, but STOP at "Welcome"), go to your "C:\Documents and Settings\<YourUserID>\Local Settings\Temp\pftA7~tmp\xp" (or whatever TEMP folder is created), copy the folder CONTENTS to the same folder as -X- folder containing the INF's, and select the "852.INF" (found it searching for "855" and it has the "855GM" within, NOT the "855.INF"). You shouldn't need the other ones within.[Strings] INTEL="Intel" INTEL_MFG="Intel" PCI\VEN_8086&DEV_3580.DeviceDesc="Intel(R) 82852/82855 GM/GME to Processor I/O Controller - 3580" PCI\VEN_8086&DEV_3584.DeviceDesc="Intel(R) 82852/82855 GM/GME to Processor I/O Controller - 3584" PCI\VEN_8086&DEV_3585.DeviceDesc="Intel(R) 82852/82855 GM/GME to Processor I/O Controller - 3585" PCI\VEN_8086&DEV_3581.DeviceDesc="Intel(R) 82852/82855 GM/GME Processor to AGP Controller - 3581" Yes, just "integrate" the SP3.EXE file (there is no "remove SP2" in nLite), then all of your Drivers.

Win2K/XP/2k3 How-To (for sharing between 9x and those) with a nice explanation. Bottom line, Win9x needs those ports (IPv4 only - NetBios over TCP/IP) for Sharing (in addition to UserID's/Passwords/MS-Networking/File+Printer Sharing), along with the same thing for the other OS. Ain't TCP/IP Communications wonderful?

I use a built LiveXP, run "Regedit", "Load Hive", export the Loaded (or a portion of it) to a REG file, then do a global edit of the Exported REG file (to remove the Temporary "folder" name I gave it during Load). Load Hive The Same (plus HIVE names).

Grow up.Use the "Edit" Button, or does it not exist? Post following post following post?Rule #11#10, ok???

Nu-uh.... more than just that, but also includes that... Wiki.To get "just that" you need the whole thing to extract those items. Jaclaz (here on MSFN) referred to a tool to Mount the ISO Image remotely to allow for getting "just that" (to avoid the complete download), but don't have the Topic/Post logged, so you just need to "search". HTH...

[snark]Still kicking your post count I see... [/snark]

Hmm... found v4.38(a) here...Direct link from ViaArena... edit - and the OP's problem was solved - Bad RAM...

Clear - "Clean" Home SP3 -> Pro SP3 (slipped) Upgrade works (as probably "Clean Pro SP3" would, since apparently "Full") Preexisting XP Home (with all of your settings, added software, etc.) -> Pro Upgrade does not. Due to the following message Read this. Hopefully, you have backed up the ORIGINAL install and can restore it for another attempt. (note: don't bother with the link given within the link I gave; irrelevant). As you can see, some piece of Hardware (or Driver for Hardware) is working with Home but not Pro (very odd...). Perhaps integrating the specific drivers in Home into your Pro may "cure" the problem, i.e., go here, select XP as OS, and download them, "unpack" them (for integration purposes - requires "start from scratch" if you slipped SP3 with nLite - if manually then use the slipped one with nLite) by whatever means (find Universal Extractor on MSFN and use it - ). Find each Folder after "unpack" that has an INF-suffixed file and during integration of Drivers, point to each INF file (the "Intel INF Installation" one FIRST!).Please note that if you have any add-in cards (PCI, PCI-e, or USB-attached Hardware (Printer, etc) that drivers will need to be "found" for them. Some may not integrate (e.g. HP Printers). Here is the "odd" thing - if Drivers are working on XP Home, then the should not matter during Upgrade as the Drivers are already there - See this{/url] (MS Upgrade Advisor). That would leave some piece of Software that's hosing you. You may have to uninstall your Software (non-MS...) and reinstall later, so be prepared (CD's, Install EXE's, etc. and keys). ...an epiphany - you might be able to do a Boot to CD and do a "Repair" Install to successfully upgrade. However, you may have to "trick" Home into thinking it's Pro to do it. WARNING! I have never done the "trick" so be forewarned! (??? odd, very odd...) Final note - you might want to use Device Manager and "Show All Devices" to find out if some piece of Hardware WAS installed that never worked and was subsequently removed. Also (curiosity) what is the nnnnn-XXX-(whatever) X-value in your Control Panel->System? (you could be trying to upgrade an OEM version - is the X-value OEM?). It's one thing to be able to Clean Install, it's another to do an Upgrade - we'll try to help you through (jeez, I hate stabbing in the dark... AND being wordy...).

I might get more and more confused here (still need some sleep) but... is it not what the OP tries to do ? An upgrade of his running (but not "clean/out of the box") XP Home SP3 ? ... and now I'm confused... maybe a language barrier?1 - You started with XP Home(?) SP2 (which had SP3 installed...) / Home SP3(?) 2 - You want to install an XP Pro RTM Slipstreamed with SP3 as an "upgrade"(?) or do you mean EMPTY HDD/"Clean"(?) (repeated for clarity) If you have Home already installed then you may Upgrade (with either a Full/NotVolume(?but should if Vol) or an Upgrade Version) to Pro while Home is running ("chose upgrade") and it should "change" your Home to Pro. Your SETUPP.INI indicates it is not a Volume Version or an OEM Version (i.e. Full or Upgrade). Upgrade Version should not allow a "clean" (booted to with an empty HDD the installed) without having some preexisting proof of qualifying Upgrade Path (see link given). Full Version will do either Upgrade or "Clean". There is a "tool" to "decompile" (decrypt) the OEMBIOS.CAT that might help confirm that it's not OEM or Volume (in spite of the SETUPP.INI contents). There is also a tool to check your 25-character Product Key to confirm whether it's OEM or not (Google - chkpids XP - it's on SourceForge). Now... can you clarify which operation your intent is? (I'm fairly familiar with XP/2K3, but don't really recognize the "extradata" line in your attached file - APPEARS to be the Pro). DOH!!! Simpler! - Post the Volume Label of your XP Pro CD!!! When you put it in the CD-Reader, just "Exit" the AutoPlay and use Explorer to display it. Look here for "known labels"... (wow!!!)

Avast - Nod32 - don't know... Without KeX - this may help...

WHAAA????You've gone fruit-loops! I've been running a PC-CHIPS MoBo with VIA North/South+Intel-CPU for two years and not one whit of a problem. In addition, the last MoBo was a GigaByte with Via North/South+AMD-CPU (4 years) and also not a whisper. Not to mention other older PC's having VIA Chipsets... You MUST have used the wrong drivers/version!!! P.S. and triple-booting 2K3, XP, and Win98SE on both! (wow!!!)

More specifically this (a link within your link)... Firewalls have to have some allowances for this (Local and Remote, depending on what you want to allow); Port 139 is specifically File Sharing. Played heck getting Symantec to play nice with everything/"everyone" (all 3 ports) plus "ping"...

In process of burning "stuff" off of my HDD to make "room". Willing to test in a VM/VPC as soon as finished.

First, it's unwise to nLite directly from "C:\"... Make a folder named anything (e.g. C:\nLiteXP) and put XP CD contents in that (minimum the WIN51 files in it and the complete I386 folder next) since it "collects" everything within the folder (your C DRIVE!!!) for the ISO creation. (Ponch said...) Second, temporarily turn OFF you AntiVirus as it will sometimes cause problems (as you just seen) because Real-Time Scan could clobber you by checking stuff while nLite is running. Third, nLite should never be in the same folder created above (you already knew that). Last, just create the ISO from nLite instead of having it burn it, then burn it afterward. I find this to be much safer, especially when you may want to reduce the Burn Speed (max usually 8x)... try ImgBurn (free) for that purpose. It also allows you to "mount" the ISO in any free ISO mounter and inspect it.

I don't understand that statement. However, VPC, by design, will always use the Host Clock. It occasionally checks (and updates) to keep people from "setting the clock back" for Trial Software.

Then the only problem that may remain may lie in the actual USB SkypeMate hardware...

MS-DOS Mode

(sigh...) Appears that your Product Key (that you DO NOT want to EVER post anywhere!) "jives" with the SETUPP.INI to allow only an Upgrade rather than Clean Install. Usually, you can attempt a Clean Install and "swap" the "previous OS" CD in (temporarily) to allow it to go "clean". Apparently, not in your case(?). There may be a way to "hack" it, but I doubt it would work anyway... (and don't want to go into/discuss it) ...and you said "The slipstreamed CD did ask if I wanted a upgrade or a clean install.". It probably meant(?for clean) on another partition (if available)? The only attempt I've made at using Upgrade vs Full was to use a different key (using XP Home) and swapping the SETUPP.INI between them. Been a while, but I might have just used the Full and the Upgrade Key. Bottom line, with an Upgrade Key, you're probably "stuck" with Upgrade Only.

So we are limited to mentioning a particular piece of software are we, it's not that the version of Opera I am talking about isn't supported or anything. Ahem.... "Last Versions of Software for Windows 98SE", i.e. that which works, not that which has problems... Once "fixed", then post it here. The only reason the Monitor SW is mentioned is for that which worked/didn't work and +/- of each, not to "help fix why don't work".Per "Opera", you've posted in two Flash Player topics, here (KernelEx), and other sundry places about Opera. I think this particular thread is getting cluttered, nonetheless... PLEASE stop beating topics up... and PLEASE use the "EDIT" button rather than posting, posting, posting... (sheesh!) HERE is the way you should have gone about this - start a Topic named "Opera, and problems I have with Flash, KernelEx, and Sundry" and stick to it... Now you're "personalized"...

SpeedFan... (barf!) HWMonitor works fine for monitoring purposes. RivaTuner gives no additional benefit unless you want to "tweak" (and potentially destroy your Vid). Tray for HWMonitor "Free" (?) (after noticing there is a PRO version with Tray built in) here. (have NOT tested, so your own risk...) Pro's latest version unknown on Win9x (which version?) and puts "trial" in some fields until purchased and registered.

Then in your original you were using warez which means we cannot, will not and are not allowed to help you!If you don't know where it is, then you didn't create it. Either that, or it's an OEM(?) CD (sometimes having said file - I have DELL E521 MCE2005 here with that)...A hint... (Translation - The file in question is NOT used and is IGNORED, but a NEW one is created). Due to the fact that potentially you're using warez, you do the investigation on where to find the CD's "key" which will have to be input into nLite... (e.g. "where's the key stored for unattended")As for "RunOnce", do a little reading about some of nLite and look here for screenshots. The Screen says when it executes. Google around a bit and/or look at given link (given by Ponch) to see what it's used for. edit - P.S. You can't nLite a CD that has already been nLited...

@UltimateSilence - be so kind as to change title to "Solved" leaving this as an FYI topic plus a nice utility to do said function.

Errr... bear in mind, folks that "MS-DOS Mode" is strictly DOS (as like in Safe Mode, Command Prompt Only) but utilizes a (special) set of CONFIG.SYS and AUTOEXEC.BAT specifically for this (like for DOS Gaming with a specific set of compatible drivers being loaded), unlike the aforementioned "Safe Mode" which uses the standard ROOT directory ones. (just an FYI/reminder) Look here...