cluberti

Try disabling all non-Microsoft shell extensions via ShellExView, and see what happens. If the error goes away, you can try the 50/50 method to re-enable / disable extensions until you narrow it down.

That'd be great - the only thing I'd caution is if the file is executable, the delay is probably checking the file stream. A wireshark would show us though.

Win7 shipped with WMP12, so you won't be able to install WMP11 (Vista shipped with 11, and it was available as a redist package for XP). If you removed WMP from Win7 using vLite or similar, you should post there about how to get it back (although I'm fairly certain you can't get something back once you've removed it from the install with vLite).

Hard to say, until we know what's happening. Are the machines in a homegroup? Do you happen to have a network trace from both machines simultaneously while the delay is occurring, perchance? It'd be really beneficial to see what was happening over the wire on both the host machine and the requester at the time of the delay.

You could always just do this from svcpack.inf with the stock IE8 installation package (renamed to 8.3 constraints, of course). That should work - there's documentation on how to use svcpack.inf in the XP unattended guide.

Clive, after considering all of your posts about Win7 builds since this one, it seems likely that your assistance is due to needing to finish and deploy these images for an employer. If I'm correct, I would very strongly suggest you not put your employer's installations of Windows 7 in an unsupported state by doing this. It would be better to use either the Enterprise or Ultimate SKUs - yes, Professional can be hacked (as can any version) to install LIPs fairly easily, but it's not supported by Microsoft officially - and if/when this employer may ever try to get support from Microsoft on one of these builds, and they see you're using a LIP on a Professional SKU, they're going to refuse to help you until you remove it. I'm not sure it's worth the hassle to do this to ~450 machines when there are easier (supported) ways to do it with a different SKU of the OS. If your employer can afford Win7 across 450+ PCs, they can afford to purchase the correct version they need if they need multiple languages on a single install. If I'm wrong and this is just for your own personal machine(s), feel free to hack away to your heart's content and ignore everything prior to this line .

We discussed the second game for you already here. Please re-read that post - the StarForce protection driver that ships with the game is incompatible with Windows 7, and XP-Mode isn't going to help you with running that game (well) either, as it's a DirectX game. DX games on emulated video will run poorly, and this would be no exception (the same holds true for the first game as well). It would be better to dual-boot with XP to run this, otherwise you're going to find running either in a VM will be very, very painful. If you want to further discuss the B-17 game, it would probably be best to continue the thread you started here. I'm not sure the above recommendation of dual-booting will change for this game either (it's a DX7 game, and was written for Win9x - the fact it works in XP is a miracle of backwards compat, and it isn't going to install or run properly on Win7), but it's worth discussing. Let's keep that thread moving.

If that's the return code from the application failing to execute, it looks like an inpage I/O error: # for hex 0xc0000006 / decimal -1073741818 : STATUS_IN_PAGE_ERROR ntstatus.h # The instruction at "0x%08lx" referenced memory at # "0x%08lx". The required data was not placed into memory # because of an I/O error status of "0x%08lx".Either there's something wrong with a device attached to the system, or there's a problem copying the program's contents to memory. If it's always and only that application failing on the system, it would seem that perhaps the installer is bad?

If a screenshot doesn't show it, that would indicate the problem isn't in the data in the DWM memory buffer, but exists in the memory in the video card or it's driver (or both). If it's not a hardware issue, it's definitely a driver one.

It looks like that laptop ships with Vista Home Premium (by default) from Sony - given it's a Core2 Duo with 4GB RAM, your best bet is to install Vista or Windows 7 on it (7 if you can) and run Virtual PC to load and use your Server 2008 R2 / Sharepoint install. If you absolutely must run Server 2008 R2 natively on it, see if you can use Vista or Win7 drivers - if not, you're out of luck (and should again revisit my suggestion).

Technically they need to be in boot.wim, but if you want them available in the full OS you'd want to inject into install.wim as well. I'd suggest rebuilding your WinPE image, download the latest Broadcom drivers from the link I provided, and try integrating again to see what happens.

To user mynmiseman, you've managed to violate forum rules on first post, specifically rule 13. Banned.

Given most will compress PDF and DOC files about the same, it would come down to what else you'll use it for. For a free app, 7Zip seems to be the best; for a non-free app, WinRAR is the best in my opinion.

Agreed - knowing more about what games we're talking about here, and whether they're Win32 or DOS, would help as well. If they're DOS games, you could simply run DOSBox to emulate them without issue on Win7.

This works: ' Get an account SID via Win32_Account Option Explicit Dim strComputer, strUser, strSID, strMouseSpeedValue, strMouseThreshold1Value, strMouseThreshold2Value Dim intMouseSpeedValueData, intMouseThreshold1Value, intMouseThreshold2Value Dim objWMIService, objShellApp, objItem Dim colItems, gErrData '// Ensure that cscript is the engine used to run this script: RunMeWithCScript() '// Set error handling: On Error Resume Next strComputer = "." '// Reg values we're going to modify: strMouseSpeedValue = "MouseSpeed" strMouseThreshold1Value = "MouseThreshold1" strMouseThreshold2Value = "MouseThreshold2" '// Values we're going to set them to: intMouseSpeedValueData = "0" intMouseThreshold1Value = "0" intMouseThreshold2Value = "0" '// Create objects: Set objShellApp = CreateObject("WScript.Shell") Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") '// Connect to WMI and get the list of Account/SID info: Set colItems = objWMIService.ExecQuery("Select * from Win32_Account",,48) '// Find the SID for the user: For Each objItem in colItems If objItem.Name = "Administrator" Then strUser = objItem.Name strSID = objItem.SID End If Next WScript.Echo strUser & "'s account SID is:" WScript.Echo strSID '// Change the registry values for the user: objShellApp.Exec("reg add ""HKU\" & strSID & "\Control Panel\Mouse"" /v " & strMouseSpeedValue & " /t REG_SZ /d """ & intMouseSpeedValueData & """ /f") If Not Err.Number = 0 Then gErrData = gErrData & vbCrLf & "Error writing " & strMouseSpeedValue & " to " & strUser & "'s registry - reason: " & Err.Number & " - " & Err.Description WScript.Echo gErrData Err.Clear Else WScript.Echo "Registry edit to add " & strMouseSpeedValue & " for user " & strUser & " as data " & intMouseSpeedValueData & " was successful." End If objShellApp.Exec("reg add ""HKU\" & strSID & "\Control Panel\Mouse"" /v " & strMouseThreshold1Value & " /t REG_SZ /d """ & intMouseThreshold1Value & """ /f") If Not Err.Number = 0 Then gErrData = gErrData & vbCrLf & "Error writing " & strMouseSpeedValue & " to " & strUser & "'s registry - reason: " & Err.Number & " - " & Err.Description WScript.Echo gErrData Err.Clear Else WScript.Echo "Registry edit to add " & strMouseThreshold1Value & " for user " & strUser & " as data " & intMouseThreshold1Value & " was successful." End If objShellApp.Exec("reg add ""HKU\" & strSID & "\Control Panel\Mouse"" /v " & strMouseThreshold2Value & " /t REG_SZ /d """ & intMouseThreshold2Value & """ /f") If Not Err.Number = 0 Then gErrData = gErrData & vbCrLf & "Error writing " & strMouseSpeedValue & " to " & strUser & "'s registry - reason: " & Err.Number & " - " & Err.Description WScript.Echo gErrData Err.Clear Else WScript.Echo "Registry edit to add " & strMouseThreshold2Value & " for user " & strUser & " as data " & intMouseThreshold2Value & " was successful." End If On Error GoTo 0 Sub RunMeWithCScript() Dim ScriptEngine, engineFolder, Args, arg, scriptName, argString, scriptCommand ScriptEngine = UCase(Mid(WScript.FullName, InstrRev(WScript.FullName, "\") + 1)) engineFolder = Left(WScript.FullName, InstrRev(WScript.FullName, "\")) argString = "" If ScriptEngine = "WSCRIPT.EXE" Then Dim Shell Set Shell = CreateObject("WScript.Shell") Set Args = WScript.Arguments For Each arg in Args If InStr(arg, " ") > 0 Then arg = """" & arg & """" argString = argString & " " & Arg Next scriptCommand = "cmd.exe /k " & engineFolder & "cscript.exe """ & WScript.ScriptFullName & """" & argString Shell.Run scriptCommand, , False WScript.Quit Else Exit Sub End If End Sub

Yeah, setting the registry does the same thing. If you know you're always going to do it the same way, you can just write a reg_multi_sz string into it in that format and it'll pick it up on reboot. I prefer using scripts and user input to do things like that only because I tend to re-use all of my one-off scripts in many places, and it's easier to use an HTA or a VBS to handle it.

Yup, seems to throw it off. I've updated and tested the script, and it'll handle a system-managed paging file now (although after you delete the file and set it back to system-managed, it'll always find the paging file as 0 size with 0 used (and this is incorrect), because the registry reflects this as 0 0. It seems to only work the first time properly detecting file size and usage... it doesn't break the script, just worth noting - I saw it and thought it was pretty funny . One thing to note, it does NOT delete the paging file itself if you delete it with the script - it's locked, and you can't delete the file (usually pagefile.sys on C:) until after the reboot. Just FYI - it sets the paging file to 0, but doesn't actually delete the file itself; you must do that manually.

I designed it on a Win7 x64 box, so it worked fine on x64. However, it appears that having a system-managed paging file causes it to blow up, because that SELECT statement for Win32_PageFileSetting will return 0 if you have a system-configured paging file (which I wasn't checking for). You can see that there is a ? in this value if that is the case: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management Value: PagingFiles Type: REG_MULTI_SZ Win32_PageFileUsage will return data, but this can't be used to configure it - I'll have to tweak my script a bit - you can still set a paging file with it currently, though - it'll still work if you enter data and reboot.

When specifically do you want it to run, and what is "it"?

I honestly can't think of a VM software package that can't do that - you'd just need to create a new virtual drive, attach it to the VM (shut down, of course), and then bring up the VM and format the new virtual drive.

Good catch! I found this link that has links to all Broadcom's device drivers by DEV ID, and the Netlink (DEV 1692, chipset is BCM57780) points to this page. The Win7 and Vista drivers on that site both appear to point to the same package (K57_vista_2k8_<arch>). The driver name is indeed k57nd60x.inf/.cat/.sys, k57nd60x.sys is digitally signed by Broadcom (Thursday, February 11, 2010 11:34:13PM), the driver version is 14.0.0.7, and it does appear to support DEV ID 1692 (as well as some others) - it even has your SUBSYS of 040D1028: ;******************************************************************************* ; Copyright 2001-2010 Broadcom Corporation. ; ; INF for x86 platform (Vista and LongHorn). ; ; InfVersion 14.0.0.7A ; ;******************************************************************************* [Version] Signature = "$Windows NT$" Class = Net ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318} CatalogFile = k57nd60x.cat Compatible = 1 Provider = %BRCM% DriverVer=02/12/2010,14.0.0.7 [Manufacturer] %BRCM% = Broadcom, NTx86.6.0, NTx86.6.1 ... [Broadcom.NTx86.6.1] ... %F_NAME0% = DEV_KEY2.NTx86.6.1, PCI\VEN_14e4&DEV_1692&SUBSYS_040D1028 ... Given your results, I'm making an educated guess that the driver package you're integrating is not this particular one. Otherwise, you shouldn't be getting those errors.

You run sysprep /generalize to generalize the machine, and then use imagex to capture it to a WIM file from a Windows PE environment. WDS allows creation of a capture image that can be used to boot to the network and capture the machine to a separate partition or remote share, but if you don't have WDS you can use a USB key or CD to boot WinPE and capture it to another partition or disk locally - we have a thread here in the WinPE section specifically for doing this.

You might want to remove the machine or the user from the OU that's applying the printer(s) (a test OU with all inheritance blocked and no GPOs is usually the best way to do this), and then gpupdate /force and try to remove it. It's very possible that the driver/queue is locked by policy processing.

There's no need to double-post. Please continue your other thread.

What happens if you make a new WinPE image (using copype.cmd), put it on a CD or USB stick, and boot from it on those machines with this driver installed? I'm guessing it might still fail, but it would at least remove WDS from the picture and make troubleshooting easier.