BikinDutchman

Since I have never gone beyond the main windows, what do I do to get to that next level, please? Likely: use arrow keys to highlight the entry and hit Enter If you think that you changed smthing on the way just make sure that you do not save settings when you exit the BIOS

We need to see what is under Serial-ATA Configuration, your pic shows one level higher (You may still need SATA-non-RAID drivers)

Your BIOS screen shot does not necessarily provide any information on the RAID controller. It might just say that your drives are connected to the onboard SATA connectors. Update: if everything else fails try the manual: http://dlsvr01.asus.com/pub/ASUS/mb/socket...2n-e_manual.pdf Open BIOS > Advanced > Onboard Device Configuration > Serial ATA Configuration and take another screen shot As far as I can see you can do pretty complicated things there .

I don't want to sound dumb but... How do I take an image of the bios screens, if I am not in windows with print screen? Digi. Camera??? I have never done anything like that before, so I am clueless. This is really gonna be a learning experience! TY! Yes a digital camera is the way to go. We do it all the time to document BIOS settings.

Can you make a picture of all BIOS screens that deal with hard drives, IDE, SATA, RAID?

Well, even with 2 physical drives connected to a RAID controller, 2 disks can show up under windows (JBOD ). MizzTang: You really need to look in the BIOS, something like "Configure SATA as" for which are three possibilities: -IDE (no drivers needed) -SATA, no RAID, often indicated as AHCI (SATA non-RAID (AHCI) driver needed) -SATA, RAID (SATA driver needed) Alternative: look in the Windows Device Manager to see what is connected to the IDE controller (often CD, DVD), and what is connected to the SATA or RAID controller. The SATA, no RAID (AHCI) mode might be just faster than IDE, not a bad idea for desktops. In the SATA, RAID mode it would make sense to configure the 2 physical disks as RAID 0 or RAID 1. In that case they show up as 1 disk under windows indeed .

You can: -make shortcuts from an INF file: here -create them with nircmd: Here -use a small command line utility: Here -edit the installer package (*.msi with orca). I do not recommend simple copying, moving of shortcuts because that gives problems with the uninstall script and sometimes triggers reinstall repairs. Hope it helps, good luck

I think that the most problematic parts of Windows XP HDD driver method are: the special textmode treatment and the handling of txtsetup.oem. One good thing of VISTA is that is handles HDD drivers much more like the other drivers. So far I have been able to figure it out for several different systems but had to go in the deep (inspect inf files, use devcon). This is clearly an ongoing source of trouble. Maybe it is time for a small tutorial. Will think about that.

Actually have no problems : I have a Quad Core 2 Q6600 on a D975XBX2 mobo, so a SigmaTel HDAudio. I have SP2 already slipstreamed in my WinXPx64 RTM (never do that with nLite; SP2 is the only clean source I use). After that I DO integrate with nLite: Booggy's WMP11, a small QFECheck add-on, and a Dell monitor driver. I moved the contents of the WDM folder of the 11/06/2006, 5.10.5258.2 driver into AMD64\$oem$\$1\Drivers\Intel\SigmaTel. I specified the location of that driver with the official MS method (winnt32 /unattend:%AnswerFile% or WinNT.sif). After unattended setup everything looks fine and works . Windows update gives one update to the 8/16/2005 Microsoft UAA Bus Driver for High Definition Audio. It is funny that this was not included in SP2 . I think nLite integrates drivers much the same way as in the MS method; I make the split for practical reasons. I guess the problems have something to do with the order of integration (SP2, SigmaTel driver).

Papu123 First make sure you have the most recent ICH6R driver files; you need the contents of the F6 floppy, here. Integrate that in nLite as textmode driver. This should go automatic. You will have to answer a question which configuration you want. Make sure you selected RAID for the IDE configuration in the ASUS BIOS. If it does not work you may try to obtain the identifier of your RAID device; it should be: PCI\VEN_8086&DEV_2652&CC_0104. You can find that identifier after booting into DOS or WinPE, and use devcon. RaGhul: I believe Windows can use a small part of the hard drive without having the proper drivers. It is like being able to use the video display without the official driver.

HKLM\Hardware is fairly simple and not related to editable files. It contains mainly pointers to subkeys in HKLM\SYSTEM\CurrentControlSet\Control. I sometimes go there to fix problems with USB devices. I think HKLM\SYSTEM\CurrentControlSet\Control might be more like what you are looking for. You might search for "enum" and see what shows up. Note I am not a real expert I just collected all I needed to fix hardware and installation problems .

andreyvul I have been out of UNIX for a long time so I do not know about any registry equivalents in UNIX. HKLM\Hardware is generated dynamically during startup. There is no file where this info is stored. There are actually only two real registry hives: HKLM and HKU.

andreyvul It is not quite that simple (unfortunately). For the details really: see my attachment. However everything that you change under the HKCU key BEFORE the first (Administrator) logon ends up in all user registry settings, so also in HKU\.Default. HKU\.Default has the user registry settings of the SYSTEM account. The Default User registry settings are not normally loaded. You have to do that with a load hive command.

HKCR is a symbolic link to a subroot of HKLM HKCU edits applied before the first user logon propagate to all users. For more explanaition and details see short notes I made some time ago: attached Registry_structure.doc

As far as I understand Nuhi made some special support for integrating kb888111xpsp2.exe in nLite >1.3. Nothing wrong with the Ryan pack but if you are stuck you might try without Ryan's pack, integrating kb888111xpsp2.exe with nLite 1.35, and adding the WDM subfolder in the Dell package as driver. Just to see if that works.

I have several Intel SigmaTel systems. I routinely add the KB888111 hotfix with nLite. There are several posts on this topic, look for KB888111. You can find file kb888111xpsp2.exe in Intel SigmaTel packages. I do not understand how the Dell package handles this. Good luck.

Assuming "SFP" = "nLite > Options > SFC": -I never touch that, which means: I left it enabled and no problems. However, I do not use ISO/CDs; always install directly on HDD under WinPE 2.0 with the nLited WinXP files on a net location, using WinNT32.exe. I was also able to apply the IE7 tweaks with the official MS $OEM$\cmdlines.txt method. But I agree that some work should be done on IE7 integration and the most important TWEAKS.

This link provides a customizable, true add-on. Also follow the link in "About IE7 tweaks" for more info, and look at my posts and replies. Good luck

To my best knowledge the shark installer has no Google toolbar. I run his installer after first logon (together with a whole bunch of others that cannot be integrated). I think no one bothers to publish a shockwave addon because the versions change so quikly. You can try to make an addon yourself with the shark installer and see if it work in GUI mode, look at the addon instructions it is simple really.

for Shark007 repository files, follow the link in my signature. Please search the forums before posting.

Good job, You probably know you can put more HKCU statements (HKCU...) under one key ([Add....]) Your proxy settings are applied upfront and may be overwritten in finalization of IE installation by Active Setup You might consider IE customization as shown here

I used the regedit construction before and it works but I do not remember how I specified the path for the reg file. You may have the enter the absolute path. regedit /s hkcu.reg: means the hkcu.reg folder is in the default location (whatever that may be) regedit /s .\hkcu.reg: means the hkcu.reg folder is in the same folder as CMDLINES.TXT Something that I know worked for me, and a little more professional, was having a CMDLINES.TXT as follows: [Commands] "cmd /c rundll32 setupapi,InstallHinfSection DefaultInstall 128 .\hkcu.inf" The hkcu.inf is again in the same location as CMDLINES.TXT but should contain the registry settings in inf format. You may control where your installation files end up on the hard drive by putting them in special $OEM$ folders such as $OEM$\$1 (C:\) or $OEM$\$$ (C:\Windows). If you are not familiar with above look do some google.

Try: "REGEDIT /S .\hkcu.reg"

http://www.ryanvm.net/msfn/updatepack.html Search for WGA addon

Use RyanVM DirectX 9.0c add-on: http://www.ryanvm.net/msfn/updatepack.html