cluberti

Perhaps a screenshot to show - I would consider going back to a restore point before the issue occurred to start, though.

It does not, but you can use GImageX to export all of the indexes from all of the .WIM file images you want as sources to combine them into one new .WIM file that you can use, that will work.

The first question has already been documented on the unattended guide here. The second question would require you to either do it in a PE environment before starting the XP setup and script it yourself, or use an automation tool like Microsoft Deployment Toolkit (MDT) to do this.

If so, remember to follow the forum rules. No warez, no redist of files, etc.

If disabling the audio service boosts your CPU performance, you have a malfunctioning driver, not a Windows problem. This service is responsible for hosting the driver framework for audio on the system, meaning if you have problems with it enabled you have problems with your audio driver and should consider investigating that. If it works for you, great, but I should point out disabling the service disables all system sounds, which some of us would find unacceptable.

I'd guess this comes down to the fact that the command interpreter on 9x is "real" 16bit DOS, whereas on 2K it's just a 32bit NTVDM, and quotes have special meaning on an NT system whereas they would not on a 9x system if I remember back correctly. Technically, anything (literal, spaced text, or strings) that you want to pass as a parameter to an executable in a batch on an NT-based system is indeed the proper way to do it (you may not have to depending on the binary being run, but it would seem nircmd may need it - check the setfiletime command line from the site), so this may just be down to the command interpreter differences between a 9x system and one in an NTVDM.

Well, that would depend. If you're doing this for anything other than personal use, you shouldn't be using vLite or nLite anyway - it's a violation of the licensing agreement. I would instead suggest using the Microsoft Deployment Toolkit (MDT) as it can do what you are trying to do, has a fairly easy-to-use GUI, and is much more configurable with regards to how and when things get executed as compared to vLite.

Myself typing this. Perhaps if I keep typing, keep listening, keep typing..... nope, nothing wierd happened. Oh well, was worth a shot. Like saying biggie smalls 3x into the mirror on Halloween, nothing happened.

Depends, really - considering XP and up don't need IE to do automatic updates, not sure why it's a problem. Autopatcher might be a viable solution for you.

Correct, there's no direct API to do anything other than query information from the security center (or register your app with it) that isn't behind an NDA and licensing agreement with Microsoft. It's still controllable via the registry, but there's no other "easy" way at it anymore.

Adding dword values to HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting\ExcludedApplications that match the .exe names you want to exclude from WER will exclude those binaries from WER checking/tracking. If you're actually looking to completely disable WER, the previous links will work, although I've never been a fan of disabling it entirely as it has it's uses (getting dump files and trace data automatically is pretty useful stuff when an app stops working, in my opinion).

@nge769: First, just remember that most of us aren't like you, and as such expect potentially odd answers on an initial post with such little information to go on. Second and to the problem in your posts, have you reported this to Microsoft via a support case or on connect? Waiting for them to fix it is likely fine, but if they don't know that it's such a problem I sincerely doubt they're looking into it. I have a particular Dell monitor that always defaults to 59Hz, no matter what video card or driver is used, but if I use the specific Dell monitor driver from Vista it works fine. This would seem to me that perhaps there is either an issue with Win7 detecting the monitor refresh rate properly, or it is possible the monitor is not reporting properly and the addition of the Dell driver "fixes" it so that Windows gets the correct response. Hard to say, but it's worth opening a support case (if you bought Win7 from a retail shop or online, you will get the support case for free).

The ISOs are for updating machines that are offline or can't get to a WU server, but they're also useful for grabbing all the updates as well. I personally use WUD, but the ISO would work as well.

It looks like the lan, but my parents had this router initially and the range was always pretty good - if you could get to the street outside the house, you could easily get signal and an IP address (considering the lock down was WEP only). If you could crack WEP (didn't take long either) you could get to the web page and simply change everything. It is a pretty harmless hack (they have reset buttons, etc, so if you got locked out you could reset it), but it would be pretty annoying at the least. Suffice to say when I heard about this I sent them a Linksys router running tomato, and got them set up pretty quickly. The fact this "hole" existed on an SMC device doesn't surprise me, nor that TW likely knew about this but shipped them anyway because they were cheap.

I'd say it's likely an issue with a controller firmware or the BIOS, honestly - the install isn't doing anything drastic or different than what you're doing manually, although it is doing it faster. I had an issue with my xw6600s when the Intel Matrix was set to RAID before a BIOS update during the Win7 beta timeframe, so it's still possible.

# for hex 0x801f0005 / decimal -2145452027 ERROR_FLT_INVALID_NAME_REQUEST winerror.h # An invalid name request was made. The name requested cannot # be retrieved at this time. # as an HRESULT: Severity: FAILURE (1), FACILITY_USERMODE_FILTER_MANAGER (0x1f), Code 0x5 # for hex 0x5 / decimal 5 ERROR_ACCESS_DENIED winerror.h # Access is denied.So either you don't have access to that directory (or whomever the app is impersonating doesn't have access), or there's something wrong with the request being made. Perhaps procmon.exe running while the app fails would tell you more as to what actually failed.

Looks like it's either failing due to accessing the hard disk, or there is a problem with the media itself. Assuming the media works properly on other machine types as you've stated, that would indeed come down to some issue with the disk controller configuration, or the underlying hardware - it's one or the other, and you really should get with HP on this one. See the following: From setupact.log, showing the "ERROR_IO_DEVICE" error being thrown: 2009-10-27 15:35:08, Info [0x06009e] IBS DeployWIMImage:Calling IDepWIMImageResolved::Apply... 2009-10-27 15:35:08, Info [0x0606cc] IBS Calling WIMApplyImage (flags = 0x184)... 2009-10-27 16:31:54, Info [0x0600ae] IBS ApplyWIMCallback: Retrying on file [C:\Windows\System32\Recovery\winRE.wim] GLE is [1117] 2009-10-27 17:12:37, Error [0x0600af] IBS ApplyWIMCallback: Error applying C:\Windows\System32\Recovery\winRE.wim. GLE [1117][gle=0x0000045d] 2009-10-27 17:12:37, Error [0x0606cc] IBS WIMApplyImage failed; hr = 0x8007045D[gle=0x0000045d] 2009-10-27 17:12:37, Error [0x0600a1] IBS DeployImage:Image application failed; hr = 0x8007045D[gle=0x0000045d] From earlier in setupact.log and the corresponding lines in diagwrn.xml, showing that setup couldn't find the processor stepping information: 2009-10-27 15:34:50, Warning [0x070026] DIAG Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0 2009-10-27 15:34:50, Info [0x07005e] DIAG HARDWARE CONFIG=Ram in KB: Total phys=8371580 avail phys=7706092 Procs=2 Arch=9 Family=178 Width=64 Speed=3166 MHz 2009-10-27 15:34:50, Info [0x07002d] DIAG Logging MachineHardWare to BB <rs:data> <z:row Cls="D" Sev="50331648" Maj="diagnostic" Min="Def" LN="93" Fil="" Fun="CAccessWMI::LogErrorMessage" Uid="50790438" Msg="Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0" PID="744" TID="748" Con="" Exe="X:\Sources\setup.exe" Mod="diagnostic.dll" Err="0" MD="" DT="2009-10-27T15:34:50"/> <z:row Cls="D" Sev="50331648" Maj="diagnostic" Min="Def" LN="93" Fil="" Fun="CAccessWMI::LogErrorMessage" Uid="50790438" Msg="Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0" PID="744" TID="748" Con="" Exe="X:\Sources\setup.exe" Mod="diagnostic.dll" Err="0" MD="" DT="2009-10-27T15:34:51"/> </rs:data> The second error in diagwrn.xml isn't critical, I don't think, but it certainly isn't normal. I'd strongly suggest you contact HP, otherwise you're going to have to run setup with a checked Windows build and hope it catches it. Since those models are fairly standard HP models, they should be able to repro this as well and tell you what's wrong with their drivers or hardware that's causing the I/O and/or processor errors.

According to Apple, OS X 10.4 and up support accessing SMB shares on 2003 servers.

Yes - all of the Office 97 applications will run properly on Windows 7 in compatibility mode except one, Outlook 97. It will not run on Windows 7 properly, no matter what you do. If you need Outlook, you'll need at least Outlook 2000 (and even then, it takes some hacking to make it work). Basically, if you're going to be running Office 97, consider running a Windows 7 version that includes the XP Mode Virtual Machine, where you can install and run your Office 97 applications.

You will need to create a new .WIM file by exporting all the image indexes of any existing .WIM files you want into a new WIM file. Consider GImageX and it's export tab to make it easier.

PM sent.

Note this is documented in KB 927521, in case you need reference to where the files and folders are.

They are indeed.

No, but does Shift+F10 give you a command prompt at that point? If so, get the Panther directory copied off to a USB key and we can take a look to see what's happened/happening. Everything about setup is logged to files in the Panther folder, both on the PE virtual volume and the installation volume.

I personally use an xw6600 and have no such issues, and have a dc7800 model here as well that also works properly. Have you injected any drivers or packages into your Win7 media at all before you attempt this? My testing has never gotten a problem on any of the xw6xxx or dc7xxx models I've used here in my testing of Win7 unattend, which you've found. Perhaps it has to do with the ICH controller? I know I have mine in RAID, although I've had no trouble in AHCI either...