submix8c

Wut???

Well, gee I just missed that... Kind of "connected" when I seen inside it "rayer".

Hmmm... you never did give a COMPLETE step-by-step over there. Which INF's did you install and in what order? I have that thread marked as "watch" so I wouldn't have to repeat your trial-and-error (having the same board). note: It APPEARS that the INF's are "altered" to work with 98SE. I say that because the "set" looks eerily familiar. If so, it may be POSSIBLE to do the same for the 965 (by comparisons)?

Nope... the "Components" section of the INI indicates "removed" components. As stated, the nLite.inf only "adds" registry entries and kicks off "nhelper" as a "runonce". I've already done a "test run" of nLite with a similar scenario to ensure I was correct in my "assumptions" (inspecting the "outcome"). I generally remove nothing since IMHO it gains little and only slip updates/drivers and maybe create a User - "KISS" method. In the OP's case they (apparently) used a Dell OEM source (like mine) to: [Tasks] Remove Components Unattended Setup Integrate Drivers Tweaks Create a Bootable ISO OptionsThe language is kind of irrelevant. I've already checked with a "translator" to compare. The "run" was done with Spanish as the Language against a Dell Spanish source (apparently based on the OP's comments and the INI).

Mmmm... sadly, the INF's in the package are all 2K and up (depending on the INF). Whether they could be "modded" and used is apparently still up for debate. It would have to be done by someone who has one of said chipsets.

I really don't know, but on this page (Posted 10 December 2008 - 03:40 AM) it implies that an older version might have them in spite of the first post (edited by galahs: 01 October 2010).edit - I have an "800 series" that includes 915/915M data approx 2004 (downloaded approx 2007) . another reference here here here here here here (implies a 945 worked) here.

@Ponch - understood @andros - granted @anyone - PLEASE don't pester for an answer already given as it sounds like an MSNBC Political Interview and the same answer will be provided re: Rule#11 - I have stated (once) before than MANY times I use caps as they are much more expedient than swipe/click/click/click OR extra leading/trailing characters... I am by nature a "Mainframer" and CAPS were heavily used on a 3270 TSO/ISPF screen interface to COBOL/PLI/ASSEMBLY/FORTRAN (etc) coding... Force of habit, especially since I'm now missing a tip of a finger. Bear with the NORMAL usage of it please - beyond that it may well be "other than" (as in ).

@!#$%^&*()_!!!!!!!!!!!! IT DOES NOT REMOVE!!!! There is NO FACILITY TO "DELETE" IT! NOTHING IS "INSTALLED"!!!! NOTHING TO "REMOVE" except that STUPID ENTRY!!!! Look inside OTHER INF FILES! THEY SELF-DELETE!!! Do you REALLY want it to no longer show? REMOVE THAT LINE FROM SYSOC.INF!!!!!! Removing "HIDE" will MAKE IT SHOW!!! LOOK INSIDE YOUR NLITE.INF - IT DOES WHAT I SAID IT DOES!!!! Learn a little about INF files and how they work. THIS IS NOT THE TOPIC FOR THAT!!!! JEEZ, dude, how many times to I have to tell you???? Use nLite or NOT!!! I don't care anymore!

Spanish SP3 source (NOT the one you originally posted)? You've removed quite a few components, which is your option. Otherwise.... so what? The first file you posted (SYSOC.INF) still indicates a Beta (Pre-RTM) source and the entry nLite = ocgen.dll,OcEntry,nLite.inf,HIDE,7 specifically says that it's "HIDE" so it should not have shown in ADD/REMOVE. The second file you posted (NLITE.INF) will still tell nothing. As has been stated, NLITE.INF only "polishes off" the Install (via NHELPER program) and sets some Registry Entries. NLITE IS NOT INSTALLED!!! I'm really not sure WHAT you expect as "answers". If the "LAST SESSION" files are from an nLite Session against a FULL UNALTERED SPANISH XP-SP3 Source (all dates of Files/Folders EXACTLY THE SAME, unless an OEM-altered Installation CD) then (again) so what... BUT if they are from the Source, then it's a "bogus" Source (already nLite'd) and components have been removed. To change to a Spanish Source you could to start with (e.g.) an English Source and apply a Language Pack. OR you could obtain a Spanish source (as well as other languages) as you appear to have (now). That is all there is to it. You have your answers.

Well, FWIW, here is the Drivers/Software (same list is apparently here). I have an original Dell XP MCE Restore DVD that MIGHT help isolating what's changed "manually". If you still have the original HDD, it MIGHT be possible to "reconstruct" an OEM CD/DVD from some of its contents (plus the one you haveas a "base") using e.g. a BartPE or LiveXP. It won't be an "exact" OEM CD/DVD but it would suffice with minimal drivers integrated. Note that my DVD is one of a two-part "set", the first being a more-or-less "Dell generic" and the second being the remainder of the Drivers/Software. This seems to be the way Dell went for XP Installation CD/DVD's supplied with PC's. I'm "somewhat" versed in Dell's since these are the majority I've had to work on (aside from Acer/HP/eMachines).I've noted that Dell doesn't (apparently) pre-install XP 64-bit so you should be good on that. For the record (pertaining to your CD's/DVD's you have) a "straight" Retail/GenericOEM (unaltered by the Manufacturer) has these as dates for ALL Folders/Files. RTM 08/23/2001 SP1 08/29/2002 SP1a 03/31/2003 SP2 08/04/2004 <-Flyer says this (or optionally Vista, probably Business) SP3 04/14/2008 The first task, though (as stated), is to ensure that your "source" CD's/DVD's are good (unaltered?) and readable via a VM. Without a good (clean) source you will be snookered. Note that a REAL OEM CD/DVD like mine is, however, good as a starting point - see link given by jaclaz to assist in recognizing one. They do NOT look the same as directly from MS. (ServicePack Level is irrelevant). This is doable - follow instructions though...

Just bear this in mind (post#12). It refers to an OEM install. There's a little more to it if it's a Retail Full or Upgrade, but the "basic" rules remain the same (except pre-activation). Come back when you get past the "glitch" for more precise help on that matter.

Is there a WINNT.SIF in the I386 folder?

Nope, dude... it's the "LAST SESSION.INI" that tells what ELSE was modified.Right at the top of this screen: It's sole purpose is to "kick off" the remainder of the "modifications" (see above RED). If you do NOT have the above file - IT IS SUSPECT! What you have provided (NLITE.INF) does NOT EVEN TELL that it's from "original WXP sp3" - it could be from ANY nLited source! Provide it or be quiet! Repeat - nLite is NOT installed! An nLited XP is installed! Review the nLite FAQ. Nuhi (the creator of nLite) is no longer available and there will be NO explanation of the "details" of this PROPRIETARY software except what may be "gleaned" from this and whatever else has been "discovered". The Source for the Program is "closed" and we DO NOT have it OR do we have Nuhi's notes and private documentation. Use it or not - Period. So... you were a Beta Tester?

Good point: There is no compelling reason to accept the idea of a "Downloads" folder inside a profile "Documents" folder, and a downloads folder at root eliminates the path length limit problem that prompted me to look for alternative directory names. But: 1) Why are you so emphatic about "NEVER ... download to a 'Profile'"? [As you say, MS thinks it is a good idea.] Is it something more than a path length limit problem? 2) It would still be nice to find a good, complete reference for WinNT.SIF, at least for the directory and path settings. 1) IMHO... I consider mine a "junk" work area, kind of like the IE folders - "to be deleted occasionally" (contents of "MY whatever")...2) See jaclaz comment... I agree about separating the user home partition from the system partition. In fact, that was another one of the reasons to search for answers about ProfilesDir (and its subdirectories, which also have registry values). But: 1) What do you mean about: ? Do you just mean to avoid the MS "My Pictures", "My Music", "My ..." silliness? Or do you mean to separate those media files from other downloads? If so, automatically during download (and, if so, how?) or just by moving files after download? IMHO, Separate, separate, separate... "Organize"! (see next part...) ? Do you mean the browser options? If not, what? If so, do you mean something more than the "download directory" option? Thanks, John In Browser Options, for downloads, set the option to "Let Me Choose". OR use a (any good Downloader, depending on WHAT you download, e.g. general "File Downloader", "Video Downloader", etc.) and set THAT one to "let me choose"/"my default folder".Example: 1)Create a "Music" folder/Partition (preferably) elsewhere 2)Within it, create "Joe", "Mary", etc.. 3)Protect each one's "modify" (whatever) for JUST "Joe" (same as "My Documents/My Music") - "Read" can be applied for "sharing" with "Mary" (and vice-versa) 4)Within the given Application (MediaPlayer) for "Joe", set the Folders to "Joe" and "Mary" 5)Each User (Joe/Mary) creates their own personalized "playlists" to their tastes - NO DUPLICATES WILL EXIST 6)The same could be done with "My Pictures" (etc) and even PREVENT access to ANOTHER sub-folder "Picture\Nunya" (Joe doesn't want Mary to see his pr0n and vice-versa ) As well as creating "Drivers" and sub-dividing into TYPES of drivers. "Organize" - and note that you don't have "spaces" AND the Depth of Folders/Files will be as shallow as possible (see jaclaz comment) I presented such a layout to my Brother (who records his band's live gigs) and he... Example: 1)"loads" from cassette into Partition "x:\JAMSIN\gigname.wav" 2)"edits" "x:\JAMSIN\gigA.wav" to "x:\JAMSOUT\gigAtune1.wav", "x:\JAMSOUT\gigAtune2.wav", etc. 3)"burns" files "x:\JAMSOUT\gigA*.wav" to CD (for travel, distribution, whatever) -AND- "converts them to MP3 to place into his "Joe" folder (see previous example) 4)"backs up" "x:\JAMSIN" to CD/DVD 5)deletes JAMSIN and JAMSOUT Contents (burned, remember?) 6)Defrags the Partition (prevents "stutters" for next "gig round") Remember that any given application has "options" for JUST THAT USER therefore don't intermingle (just like the "My Documents") since each one is "personalized". Yes, this sounds "complicated" BUT everything is highly organized and minimal partition sizes are used to reduce defrag time - enough "space" to allow for "work" or "storage". What you want is easily found as well. Only the "initial setup" is the pain in the axx. Not for the faint-hearted... (I almost wish I hadn't suggested it now...) You may keep it "basic" for e.g. your Drivers and leave other stuff alone (as 5eraph suggests). You'd choke if you seen my HDD layouts BUT I have everything organized and (almost) easily found/manipulated. submix8c - outta this! (I am a complex piece of human meat)

? Why let it "default" to a download location? Make a Directory on the ROOT and opt to download it there. Better yet, use a Downloader (e.g. Flashget). It's NEVER a good idea to download to a "Profile". Most "common" users make this mistake thinking "MS must know best". I recommend to even change the location of Videos, Music, and Pictures (it's in the Options of the Software) to even a different partition or better a different HDD. Want to defrag? Go ahead and defrag a MONSTER 1tb partition - be prepared to wait all night.

Worth a shot. Also please note that all fans are not created equal.

OK... so what kind of PSU is it (never seen that specified)? If it's not the correct type and/or does not have enough watts on the rails, it may not work. All of the info is sometimes provided on a sticker., otherwise you'll need to get the specs from the manufacturer. Have you "cracked it open" and CAREFULLY thoroughly cleaned it out? Sometimes "bulged" CAPS will function at lower demands but will fail at higher (just like a MoBo).

I see the site is also temporarily down (maintenance)? I'm also a member there (as are many members here) but have never posted. BartPE builds from XP (not PE) the same as Winbuilder-XP. This makes it somewhat irrelevant to even use WinPE as WinPE is usually just a "stripped down" Windows which ALSO uses (AFAICR) a Windows CD to build it (I have all of the PE-versions, supplied by signing up as an OEM). Not having used the later WinBuilder software I don't know how well it will work or if it allows for Passwords. Note that I don't use the WinPE's from MS anymore since the alternate method (Winbuilder) is IMHO vastly superior. Google cache of one such project as an example. Google this: winbuilder reboot.pro "pe3"

??? I haven't read the whole thread so maybe this was mentioned? The fans will will run full-throttle then "settle down" until needed at higher temperatures. It's called "Smart Fan" and usually you can turn this ON/OFF in the BIOS somewhere. This is normal (if it has Smart Fan) and a word of warning - I have a "monitor" software installed and it wreaks havoc if you set the Sensors-ID on the wrong Sensor (mine has 3).

Superseded by this (KB2705219). Seems WUD is being kept up-to-date. You can either use that one or this one. It's up to you.

BartPE, AFAIK, is similar in nature to WinBuilder ("LiveXP"). See this Wiki and this Wiki. Based on that, I'm not sure I understand the question. Your initial description suggests you used a BartPE plus an Image with which you "loaded" onto the PC's in question. I would suggest a method more like a WinRE/WinBuilder? (note: boot-land.net is now reboot.pro)

I will correct that - Your SOURCE is BETA (Specifically RC2)! All SYSOC.INF of XP-32-bit from RTM and up start at "5.1.2600.0" (RTM). Yours SPECIFICALLY STATES "5.1.2535.0". All Released Service Packs since RTM (AFAIK) also conform to the actual CD's. I would call that "suspect"... Shall I illegally download it to prove it (yes, I found it)? I might ALSO suggest that Beta keys will not (AFAIK) work with RTM and up, so have at it, my friend. Although... I guess you COULD "hack" it and make it work, also HIGHLY illegal. Besides the fact that I answered your question AND wondered about the "HIDE" part... Searching the Internet on nLite "SYSOC.INF" even suggests removing it (as jaclaz too suggested), although "tweaks" will "break" it since it's already been applied. edit - OHHHH!!!! Found this. Interesting... Still, looks like "hacks" would be required...

Not sure if Win7x64 will bite you on that or not. This is as much an nLite question as it is an Unattended question. nLite FAQ. Please be aware of the EULA for nLite (also in the FAQ, in case you missed it). Appears that you integrated the PNP-way instead of TXT-mode way. (see FAQ for difference). edit - and another poster has suggested setting nLite program to "XP Compatibility Mode" to properly function.

Intergalactic translations - you need special glasses though!

Hmmm... don't know. Have you tried clearing you cache and cookies / all history and exiting/restarting?