submix8c

Courtesy of jaclaz - http://www.911cd.net/forums//index.php?showtopic=24370&st=0&p=168043entry168043 From this thread - "HKU" vs "HKCU" - Do you see the point now? Do read up on how a registry ONLINE is built from Individual OFFLINE Files.

Rest in peace, Joe South. http://www.youtube.com/watch?v=PojXf-spKKM

Have a baaaad feeling this may apply anyway since its based on Server 2k3 code (which may also have the problem - untested).SRV2K3 SP2 = 2007 XP X64 SP2 = 2007 XP x86 SP3 = 2008 side note - dug a little - makes somewhat sense now (cd-boot->setupldr.bin->winnt.sif)

What I said is part of the Information. #2 of what tomasz86 said is the other part. HKU consists of System-oriented and the CURRENTLY logged on user and does NOT include any/all users that exist/are-defined. Try looking in "Documents and Settings" folder. Now look in the sub-folders. See the "NTUSER.DAT" files? Those are the Profiles. DO NOT MESS WITH NON-USER ONES! The "Default User\NTUSER.DAT" is the DEFAULT for any/all NEW USERS (no matter WHEN defined) - it is the SOURCE of the New Users (copied right in there to any new user AFTER defined THEN logs on FIRST TIME). User Profile Folders DO NOT EXIST until the USER-ID's are DEFINED - AND (see that AND AND AND) - The USER-ID Logs On FIRST TIME! Try it! Define a New User and see if the Folder exists! Now Log On as that User - BINGO! Folder and NTUSER.DAT (from DEFAULT) now exist. Either you have to MODIFY the DEFAULT one and "copy" it in -OR- Modify it via tomasz86' suggestion. Please do try "Google"....

? e.g. DIR /S /AHThis "bug" must appear in CMD.EXE as well... edit - see next post - (xp) DIR x:\WINDOWS /s /a /on /p yields the hidden $HF_MIG$ and subfolders (hidden) and sub-subfolders/files (not hidden).

Nope... Not in my DRIVER.CAB. First appears in SP2a and still appears in SP3 in both I386 and SP2/SP3 CAB files.Something is reeeeaaaalllly fishy about your "source" if it magically "moves" from the original location. Better check that SP2/SP3.CAB for "FSQUIRT.EXE" again. I call BULLS**T!!! edit - Must be an "HFSLIP" source... More info - http://msdn.microsoft.com/en-us/library/windows/desktop/aa362932%28v=vs.85%29.aspx "Microsoft Bluetooth support begins with Windows XP with Service Pack 1 (SP1)" http://support.microsoft.com/kb/323183 "Availability of Windows XP Service Pack 1 Support for Bluetooth Wireless Devices" (no FSQUIRT mentioned) http://support.microsoft.com/kb/811805 "Reinstall the Bluetooth stack. To do this, go to Windows Update and download any updates (specifically, any that mention Bluetooth). If you are using Windows XP, install the Windows XP Service Pack 1 Support for Bluetooth Wireless Devices or any newer service pack, which will contain the service pack." Maybe it's in one of these? http://catalog.update.microsoft.com/v7/site/Search.aspx?q=bluetooth%20xp Hmmm... doubt it... BUT... http://support.microsoft.com/kb/883259 (at bottom) "Blue Tooth File Transfer Wizard" AND... http://support.microsoft.com/kb/891595 Nonetheless... (Psssttt - HFSLIP'ed source)

Silly me... Guess I need to start digging...

Well, it's all getting confusing... As stated, there is no SP3 for XP 64-bit. It shouldn't matter whether you run nLite on x86 or x64 as long as you run it on less-than-Win7 (sp1 seems to be the most error-prone culprit?). I just retested on an x86 OS (not-Win7) against an XP 64-bit w/SP2 and got the same results (WINNT.SIF looks ok). Really silly question... are you running this from BOOT TO CD (WINNT.EXE) or are you running it from a Windows OS (WINNT32.EXE)? If the latter, the WINNT.SIF won't be "picked up". You need to run the WINNT32.EXE from a Command Prompt and specify the "WINNT.SIF" for the Unattended (ref. UNATTEND.TXT). Reference this thread. edit - AND... don't know if this is true or not...

What OS are you running this on? What version of WinRar? (see Version History / OS supported) Winrar v4 Help

Hmmmm... maybe they're transferring to another server and the files are "temporarily unavailable"? I had tried (see original "complaint") at that time and got a "not found"...

? For funsies, I used yours w/XP-SP2, added additional User-ID/autologon, provided a key (both items are in another INI), and see absolutely nothing wrong. Heck, the original INI looked good... Only difference was the dotNet version and the OS that I ran on... Not an "original" source? (edit - DANG IT! I made an additional post... AGAIN!) edit2 - DOH! (see below...)

1 - Don't nLite in Win7 - failure is known to occur - install XP in a VM and nLite within it 2 - nLite from Original Source (untouched) every single time 3 - Why SP2? Get and use SP3 4 - nLite - use "Unattended" selection - CD-Key inserted into [userData] Section 5 - True - VL versions are not available to the general public (and generally irrelevant except in certain "quirks") 6 - Yep! Need that INI (says so right at the TOP) --- Key NOT inside THAT one (note the filename and instructions above - NOT PASTE) On that note (#5 and above post) if its a "bogus" * (a - "hacked" warez / b - pre-modded/slipped warez / c- nLited warez / d - "stolen" warez) one you'll get no further help... MSDN Image (subscription), Purchased OEM/Retail CD, OEM-Provided CD, or OEM HDD I386-Source (Recovery) are the basic legitimate/legal sources. HTH edit - AH! Posted already...

How odd! I just used that with the "direct links", chose downloading with FlashGet and the "direct link" was used (same as previous attempts) BUT the Referrer was filled in this time (blank when "New Download") with "http://archive.org/web/web.php". Weird! Anyhow, got both of them (I386/AMD64 ENU).Starting to look like we'll need a "Direct Links" text file for any/all 2K3 and XP files. Post-SP2/SP3 would be fine. Would be real nice to have HBR's stored "somewhere" as well (wink-wink) along with the associated KB#-text. We're already having problems with Win2K files (both Pro and Server). Seriously looks like MS is swiftly "pulling the plug" on a lot of stuff. Gotta love the "cloud"... edit - BTW, "InstEd It!" is a great MSI editor (as opposed to ORCA). Some minor mods DO work better with ORCA, however.

I said that a LOOOONG time ago...It's in the SP3.CAB (uncompressed). I'm really unsure of why it would be in both places. The Source I checked is an MSDN XP-SP3 and the "culprit" for the "overlay" is DRVINDEX.INF. It's the exact same file bit-for-bit (including the date/time). Dump the CAB to someplace, replace also that one (uncompressed) are recreate the CAB. Info on how to use MAKECAB is all over the place on MSFN and Microsoft/Technet. Search instead of asking someone to for the footwork for you. You COULD have used XP's "search" on your Source and found that out yourself. Instead, I DID IT FOR YOU (by opening the CABS, btw)! Happy now? PLEASE, Sir BLASH, quit being so lazy!

Please do so at first opportunity. Suggest putting links to all drivers that "work" along with - maybe put in Post#1 (leave original text). This applies to all of the Models in question (not listed) using this MoBo (including mine).

Notepad is the program?

I had never heard of it before, and you're right! I've located the I386 one but not the AMD64 one - both direct links are dead (found them). Also appears to be just for SP1 and won't install on SP2? In addition, apparently some folks (example) found that the AMD64 one won't install (maybe because of SP2?)... Here is apparently an alternative. <-have not tried yet...

(noting that DDO's all install and function "differently",) Clarifications, explanations, and confirmations accepted. No need to specify which... Got it! TY.

I did gone there but could not found "Home Edition" written any where. PLEASE CLEAR THIS.What, exactly, are you trying to do? "Fake" a Home Edition from a Pro Edition? That doesn't even make sense! What are you doing - compiling a "cheat" list? I know of NO reason to change that String from Home to Pro WHEN PRO HAS MORE FUNCTIONS and ANY Software that installs on Pro CAN BE INSTALLED on Home.No sense! Unless you have Keys for Home in which case CHANGING THOSE VALUES WILL NOT HELP YOU - the files between the Editions are DIFFERENT and NOT interchangeable! PERIOD! There is NO SUCH THING as "Home VLK", as some hackers" try to tell you "exists", and the "hacks" used (if you find the references - and NO I will NOT give them to you) DO NOT WORK! From a Command Prompt, type "WINVER.EXE" - see the results? Open the "WINVER.EXE" in a Hex Editor - See what files it links to and the Functions it calls? I TOLD you that "hacking" an OS goes DEEEEEEP into the System, didn't I? AND told you that mucking around with it would potentially BREAK it! HERE are the RTM File Differences, Sir Goofy! As for the "text" for Home vs Pro - CHANGE "Professional" To "Home" - VOILA! DAYUM, dude! Can't you figure out that ALL THAT I GAVE provides ALL INFO (combined) to produce what System Properties give? Now...

That's good! The intent of the query/comment got an answer.What about CD/DVD, USB, etc? My understanding of a DDO (even if just in the MBR) indicates that this code is NECESSARY in order to properly translate the LBA. My research indicated that one of them allowed for the Code to be "inserted" so that any CD/DVD booted would properly recognize it, as well as Floppy. It seems that somewhere the BIOS code would be best "overlayed" to provide proper support (provided the Controller could deal with it?). I guess I must be missing something. It's been a while since I used a DDO (MBR-style). note: not trying to pry proprietary info from you... I have no desire to write a MBR code. also, comment about "boot loaders" due to finding article about "how to" with xosl.

OK... followup. The BIOS absolutely has to support 48-bit LBA. No known DDO's (except maybe rloew's, which I do not have so can't say) can overcome this since this is an entirely different bit-scheme. Some DDO's do not allow for booting to anything other than the HDD and some you have to enter with special keys to change to another device outside of the BIOS order. The first type is absolutely useless since you're stuck with HDD only. Some actually create an additional first Primary Partition that's booted to first (reducing the number of Primaries you can allocate). Using a DDO creates headaches when using e.g. XOSL or BootIt-NG since they require using the MBR to boot from first (BootIt-NG also uses a small partition). Worse, some DDO's are a PITA to remove at a later date AND appear to only be good for the "up to" 48Bit-LBA barrier. An alternative of "patching" the BIOS to support 48-bit LBA probably don't exist - good luck with that (Controller is a limiting factor?). It appears that the only option is to "limit" the HDD to the maximum the BIOS supports (non-48BitLBA) as you've done OR use rloew's DDO (note stipulation of Boot Devices above), since others apparently (and I haven't tried them yet AND have I believe most/all of them) don't support it and/or "suck up" a First Partition. Done!

Missed that. See above comment.Short answer - DON'T nLite an nLited Source!

As a general rule, I Sort by Date (wget downloader retains original dates) when using the UDC script. 1 - Use UDC Script all by itself, i.e. JUST the contents of the ZIP file in a Directory 2 - Add ONLY EXE files, then Sort Date Ascending 3 - Add WMP CABS one-by-one in order by FileName (* note - see below for WMP11) 4 - Add "Other" CABS one-by-one (name/date irrelevant) 5 - If slipping IE8 5a - Create the Add-On then Add at end 5b - REMOVE those marked in the List as "IE6 Replace" 5c - Add the IE8 one-by-one in order by FileName 6 - Continue with nLite process As for WMP11, Use WMP11 SlipStreamer process BEFORE using nLite then 1 - Proceed as above but DO NOT include the WMP11 Cabs (Step#3 above) 2 - Get the corresponding ORIGINAL "EXE" files (see contents of Script) 2a - EXCEPT KB952069 (does NOT apply to WMP11) 2b - Add WMP11 "EXE" files in order by FileName * note - above in essence replaces the Step#3 HTH

Riddle me this, Batman... On the XP in Device Manager, does it say EXACTLY what it is? There is NO SUCH THING a "Generic nVidia" (or something like that)...