jimanny

I have a Dell Precision M6300 that came with Vista Business x64 on a 64GB SSD drive. Out of the box, I have no problems, except Vista uses up nearly 20GB, so I want to shrink it, which I did with vlite (thank you Nuhi ). On the vlited build, the problem comes when I try run the setup.exe for Pro/E Wildfire x64. The hourglass comes and goes without any errors or entries in the event viewer. I'm hoping someone can offer any clues. Is there something in my vlite config that's causing this? I tried to turn DEP to AlwaysOff in Vista, but no luck. Attached is my Last Session.ini file. Last_Session.ini

This time I'm working on an x86 build and notice the same thing with the "n", but different... Lines from newly built (by hand) Autounattend.xml: <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <component name="Microsoft-Windows-Security-Licensing-SLC-UX" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> and the same lines from vLite: <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <component name="Microsoft-Windows-Security-Licensing-SLC-UX" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> I guess the first "n" in NonSxS is supposed be caps and the in the second line it's upper case?

I was getting the enumeration error so went ahead a rebuilt the Autounattend.xml file in Windows System Image Manager component by component and watching for differences. This line had the difference that fixed the problem: From new Autounattend.xml: <component name="Microsoft-Windows-Security-Licensing-SLC-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> From vLite Autounattend.xml: <component name="Microsoft-Windows-Security-Licensing-SLC-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> See the difference? Take a look at NonSxS

korri, I ran into the same error. Try nuhi's suggestion to me in post 65. 1.4.RC2 works for me, except with dotnet 2.0 full instead of lite. Also, in case you're on x64, make sure you install dotnet 2.0 full x64 so that you don't repeat my mistake!

Which chip, an Intel or AMD, actually processes x64 better than the other, well, I've read somewhere the AMD may do it slightly better, but exactly how, I don't know. They're definitely both x64 "capable". But if I had to pick, I'd have to go with the dual or quad core Intel chips, but only based on my experience with how they overclock between 32-bit and x64. Last year, I had an Opteron 165 running XP SP2 (32-bit) for months without a hitch at 2.9GHz. Then I installed x64, and had to drop the overclock to ~2.7GHz to be stable again. Earlier this year I did the same thing but with a QX6700 and found it to run run equally stable at 3.4GHz on either flavor, 32-bit or x64. This and the fact that XP x64 is based on the newer and more stable kernel are the reasons I stuck with x64.

I like the stability of 2003 but settled with XP x64. Isn't XP x64 built from the same 2003 kernel? nLite works with 2003 just fine except I use the machine as a workstation and found a few but important drivers would not install on 2003 (Logitech drivers and others). Now I use nLited XP x64 and it's great. I think there are less add-ons available because not all of them work on x64 (I miss Unlocker). But x64 uses the same kernel (or similar?) as 2003, which makes the OS definitely feel more stable that XP SP2.

nuhi, thank you. I got it to work, but only with the full 2.0 x64 .Net. Before when I *thought* I had 2.0 full installed, I probably didn't cause I used ryanvm's all-in-one .Net installer (dotnetaio.exe) which probably didn't install in this XP x64 machine (I didn't check it ). Still though, Framework Lite R3 worked fine on this x64 machine all the way up to 1.4b, so maybe something changed in 1.4RC? Or maybe I was lucky and Framework Lite R3 isn't supposed to work on x64. Either way, I'm stoked that it's working again.

Ok, thanks. I didn't try that. Except I've always done it from the mapped Y: drive, so maybe something changed in 1.4RC (??)

I tried the full x64 2.0 framework (dotnetfx2_64.exe), but still came the same errors. Here's how the event viewer looks: The next two errors say: Resolve Partial Assembly failed for Microsoft.VC80.CRT. Reference error message: The referenced assembly is not installed on your system.and Dependent Assembly Microsoft.VC80.CRT could not be found and Last Error was The referenced assembly is not installed on your system.

nuhi, thanks for the release. nLite is great! I setup a vmware XP x64 SP2 "nLiter" machine, specifically to build nLited x64 images. It's been working great since v1.35. With the 1.4RC release I ran into an error. Here's what I did. Run MS update, install all available updates (there were 4 of them). Reboot. Uninstall 1.4b Install 1.4RC Launch nLite and get this: Ok, I figured maybe the Framework lite was also updated, but I see R3 like I have. Then I tried: Install R3 over the top of the existing install Launch nLite, which then ran fine (?) Then Next > Refresh, and get this: Next, I will install the full .Net 2.0 Framework and see what happens. Thanks for taking a look.

Thanks nuhi! I hope the info helps. I'm looking forward to your next release.

FYI, I narrowed the problem down to the "Network Monitor Driver and Tools" component. With it unchecked, browser.dll came back, and there's no longer the error message on bootup!

I'm trying to nLite Server 2003 SP2 R2, but get a message box at every bootup: At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details. Event Viewer shows: Event ID: 7023 The Computer Browser service terminated with the following error: The specified module could not be found. The service startup type is Automatic, but it's not started (which is normal I know). But when I go to start the service from Services, it gives: Could not start the Computer Browser service on Local Computer. Error 126: The specified module could not be found. From what I've gathered, the Computer Browser service uses browser.dll, which doesn't exist in system32, and I've no idea how it's missing. There are no updates or hotfixes, but there are components removed and tweaks added. Attached is my last session.ini. Any ideas? Last_Session.ini

I successfully slipstreamed SP2 following marek722's tutorial but I still cannot install the two subsequent updates KB907417 and KB905648 either manually or from Office Update. Is anyone else able to install these? Update: Ok, this has something to do with I'm installing Office 2003 on Windows Server 2003. I ran the same Office install on a vmware XPSP2 and had no problems installing all office updates. Just by quick inspection, I noticed in XP the service "Office Source Engine" is manual but started before doing the update from Office Update. With Server 2003 the service wasn't started but the updates still failed even after starting the service. I was going to see if I could use Server as my workstation, but it seems not feasible for me because of this and a couple other minor issues. Anyway it was worth a try, back to XP...

Great! I am very happy that I am able to contribute something useful and also happy with my luck that it worked after only 2 attempts! Basically, I went from your recommendation to have the 3 extra files in the SATARAID directory. The question was where to get the files since they aren't all in 6.69. 6.69 doesn't have NVATABUS.INF so there's only one other place it can come: 6.70 in IDE/WinXP/LEGACY. NVATA.CAT and NVCOI.DLL are already in 6.69 (in SATA_IDE) so copying those into 6.69/SATARAID were the final links to make it work for W2K3 R2. It seems it works because NVATABUS.INF calls NVATA.CAT and NVATABUS.SYS but I don't know who calls NVCOI.DLL. Perhaps NVCOI.dll is called by NVATA.CAT but I don't know cause it's compressed. Anyway, W2k3 SP1 basically equals R2 so it should work the same there too.