mmortal03

Are drivers that are located in subfolders supported?

I retested the disc. As I thought, there is something that goes wrong because of the "hdc" (SP/ich5id2.inf) Intel chipset driver. Any ideas why?

When I removed the "hdc" chipset driver (SP/ich5id2.inf) and left only the "system" chipset driver (865.inf) the installation worked. I will try it with the "hdc" driver again, just to confirm that it is the problem.

I have determined that the Intel chipset driver is the culprit. It has two parts. I will try each one and see which part (or if both) are the problem.

FYI, I just tried slipstreaming this update to a Professional version, and I did MSO.msi first, and then it wouldn't let me slipstream PVMSO.msi, so it probably doesn't need it. However, I didn't try PVMSO.msi first, so I will double check that; probably doesn't matter. Edit: Nope, it wouldn't take PVMSO.msi, even if I try it before MSO.msi. FYI, I am using a Volume Licensing Version.

I don't have a RAIDed hard drive. I have a SATA hard drive, but it doesn't need a third party SATA driver. My chipset driver, along with everything else, were included when I made the disc with 1.0.1; the same as with 1.0. So why would actually HAVING the drivers included mess things up, but NOT having them work? I have nLite set to remove any other drivers. Do you suggest that I try each one separately and then let you know which one is the culprit?

Well, without any of the drivers integrated, it worked. So, what changed with 1.0.1 that would break driver integration?

Did anyone ever figure this out? I am trying to do this properly with SP2 for Proofing Tools. Should it be 1.21 GB? I can burn it to a DVD if there is no alternative.

I have now tried 1.0.1 with the same config file as above, except now without any addons except RyanVM post-sp2 2.0.7a and drivers, and it still does the same thing. I will be trying it without drivers next, just for kicks, but my system is not going to run properly without them.

I will try doing that later tonight, but honestly I don't follow why that needs to be ruled out, because this configuration, along with the extras,WORKS in 1.0 but is broken in 1.0.1. I even initially tried multiple combinations of settings and RyanVM packs before, thinking that it wasn't nlite, and none of them worked either. I didn't think that you changed any compatibilities between the two versions, but maybe you did in some subtle way?

I am still having this problem. I had to go back to nLite 1.0 so that this would not happen, which is limiting my use of the newest RyanVM updates. Any ideas?

Is there a way to get this to not happen with sysprep? A registry setting or something?

I have corrected the Compatibility list. It didn't intially include the options that were required by more than one.

I am having some issues with nLite 1.0.1. This configuration file worked with nLite 1.0, but doesn't with 1.0.1. The install works all the way to the Windows loading icon screen, and then reboots and asks to go into safe mode. I have attached the configuration file without the automated networking section. Last_Session_nonet.ini

Yep, that is what I do every time. I just left work, and at the end of the night, I had tried 1.0.1 with the same settings files from before that worked with 1.0, except that I am now also removing Bluetooth, OOBE, Secondary Logon, Modem Support, and am choosing to have a Black setup screen. Do any of those ring a bell for not being able to boot into Windows? It almost sounds like an nLite 1.0.1 bug, but I will check tomorrow by using the same EXACT settings that I used before when it worked. (that would also rule out RyanVM) FYI, tonight these are some of the ways that I tried it: I have tried both RyanVM 2.1.0 and I also went back to 2.0.7a. I tried 2.1.0 while leaving OOBE on and Secondary Logon off, and while leaving Secondary Logon on and having OOBE off. Neither worked. I didn't try Secondary Logon AND OOBE both back on, because I assumed that they are unrelated, and I am going to try the last settings that did work previously tommorrow which left both in, anyway. In the end, both 2.1.0 and 2.0.7a did the same thing, they would loop at the icon, and then would ask to go into Safe Mode. However, with 2.1.0, it wouldn't go into Networked Safe Mode, but 2.07a WOULD. If that isn't the craziest stuff... Please help if you've got any ideas!

Hmm, apparently, there is something weird that goes on if you check all of the Compatibility options, remove everything else, and then go back and look at that image without the Compatibility Options checked. That is how I decerned what I found above, however, it seems as if some of them were still removed (the new ones below that I just found doing it Nuhi's method), regardless of having all the Compatibility boxes checked. Is this a bug Nuhi? The reason I say this, is because I just went back and did it how Nuhi says, with the selecting all of them, yada, yada, and then inversing the selection, and more came up that weren't on my list, with many of them being the same ones across multiple Compatibility Options. Here are the extra ones that I found (I will integrate these into the above list as soon as I determine that there isn't some bug involved): Edited: Just had them individually checked when I went through before doing it my way. Ones that had multiple dependancies wouldn't have shown up. I have edited the above list to compensate for this. The above list should now be fully accurate.

Can anyone tell me what the MD5 Sum of 2.0.7a was? Thanks

nLite says that you can always download this later, but from where do you download it?

Did anyone ever figure out what the problem was here? I am running into a similar issue with a corporate version of Windows, except mine won't even go into Networked Safe Mode, only Safe mode and Command Prompt Safe Mode. The rest of the description is very similar to my own problem. It gets hung up at the Windows icon screen with the loading bar.

Is anyone having problems getting it to install after it integrates it? I am running into this, and I cannot pinpoint the problem. Basically, Windows will only successfully go into Safe Mode after install, and won't even go into Networked Safe Mode.

Yeah, so you can see what each one hides. They aren't obvious to figure out. I'm sure you have them memorized though, nuhi! Btw, I just ran into a problem when I removed OOBE. Windows would only go into safe mode after a clean install. Well, it was either that or it was removing Secondary Logon that did it. I am retrying it with OOBE back in. Btw, could removing OOBE from a corporate version of windows also affect the Genuine Advantage Tool? Thanks Edit: Well, it wasn't OOBE, so it must be Secondary Logon. Either that, or something went wrong when integrating the new ryanVM 2.1.0 pack.

Ok, so this means that if I check InfraRed for removal, but leave Bluetooth unchecked, then it won't remove the InfraRed support? Since Bluetooth wouldn't work without InfraRed, why shouldn't this also select Bluetooth for removal when you select InfraRed? It would be very helpful then if, instead of the description only saying "Needed for Bluetooth," that it instead said, "Needed for Hardware Support -> Bluetooth Support" and would automatically put a check next to Bluetooth Support when you place a check next to InfraRed. e.g. You can't have Bluetooth Support without InfraRed, so if you remove InfraRed, it should remove both.

Ok, here is that Compatibility List: Media Center Multimedia -> Media Center Network -> Windows Messenger Services -> Background Intelligent Transfer (BITS) Services -> COM+ Services -> System Event Notification (SENS) Mobile Phone Hardware Support -> Modem Support Hardware Support -> Ports (COM and LPT) Hardware Support -> Sony Memory Stick Remote Desktop Services -> Terminal Services Services -> Windows Firewall/Internet Connection Sharing (ICS) Windows Update Website Network -> Internet Explorer Services -> Automatic Updates Services -> System Event Notification (SENS) Services -> Background Intelligent Transfer (BITS) Services -> COM+ Services -> Distributed Transaction Coordinator (DTC) Operating System Options -> Internet Explorer Core Windows Server Core Services Hardware Support -> Smart Cards Hardware Support -> Logical Disk Manager Services -> Secondary Logon Services -> Shell Services Services -> COM+ Services -> Distributed Transaction Coordinator (DTC) Services -> Event Log Services -> Windows Management Instrumentation (WMI) Windows Activation & Sysprep Operating System Options -> Desktop Cleanup Wizard (req. for Sysprep) Operating System Options -> Out of Box Experience (OOBE) (req. for Windows Activation (non-corporate)) Operating System Options -> Internet Explorer Core Printers Hardware Support -> IEEE 1284.4 devices (Dot 4) Hardware Support -> Printer Support Hardware Support -> Ports (COM and LPT) Services -> SNMP Services -> Universal Plug and Play Prefetch functionality Operating System Options -> Task Scheduler Services -> Event Log NT Backup|Volume Shadow Copy Applications -> NT Backup Services -> Indexing Service Services -> Volume Shadow Copy Services -> COM+ Services -> Distributed Transaction Coordinator (DTC) Services -> Event Log Hardware Support -> Logical Disk Manager Internet Information Services (IIS) Network -> IIS Services -> COM+ Services -> Distributed Transaction Coordinator (DTC) Services -> Event Log Services -> Windows Management Instrumentation (WMI) Services -> Internet Authentication (IAS) Operating System Options -> Jet Database Engine Operating System Options -> MDAC DHCP Network -> Map Network Drives / Network Places Wizard Network -> Network Setup Wizard Services -> DNS Client Services -> Network Provisioning Services -> TCP/IP NetBIOS Helper Services -> Wireless Zero Configuration Services -> DHCP Client Services -> IPSEC Policy Agent Services -> Windows Firewall/Internet Connection Sharing (ICS) Services -> Event Log Services -> Windows Management Instrumentation (WMI) Services -> Internet Authentication (IAS) Cameras and Camcorders (and Scanners) Hardware Support -> Video Capture Hardware Support -> Widnows Image Acquisition (WIA) Hardware Support -> Sony Memory Stick Editted to correct for initially not including compatibilities that were required for more than one Compatibility Option.

Does removing OOBE from a corporate version of windows affect the Genuine Advantage Tool?

Thanks nuhi. One question that was not answered: If you remove OOBE from a non-corporate version, does it still ask you to activate but it is broken? Thanks