cluberti

It looks like the app has gone into some sort of loop trying to create a file or WMI object that already exists, and isn't handling the error: 0:006:x86> kb ChildEBP RetAddr Args to Child 02d3e6a0 76eab616 02d3e73c 80100080 02d3e6e0 ntdll_77990000!NtCreateFile+0x12 02d3e744 76ea519c 00000060 80100080 00000000 KERNELBASE!CreateFileW+0x35e 02d3e7a0 771bab6f 006fe1d8 00705af8 00000000 KERNELBASE!GetTempFileNameW+0x1ef 02d3e7e0 03480ee4 02d3e7f8 034c7b34 00000000 kernel32!GetTempFileNameA+0x9e WARNING: Stack unwind information not available. Following frames may be wrong. 02d3ea10 0349c3d5 02d3eaf0 a8bf00b2 02d3ea3c FWManager!GetSdkVersion+0x2f276 02d3ec30 0349c836 034bb4a8 00000faa 03908aa8 FWManager!GetSdkVersion+0x4a767 02d3f05c 0345af33 034bb4a8 00000faa 03908aa8 FWManager!GetSdkVersion+0x4abc8 02d3f0c8 0345b6fa a8bf1c72 00000003 03908a88 FWManager!GetSdkVersion+0x92c5 02d3f0f0 03456ab2 000000e4 03457016 a8bf1de6 FWManager!GetSdkVersion+0x9a8c 02d3f164 0345327e 02d3f2f4 a8bf1d6a 77191202 FWManager!GetSdkVersion+0x4e44 02d3f208 73bc59be 0381d1f0 0000002f 02d3f348 FWManager!GetSdkVersion+0x1610 02d3f294 03810000 00000000 73cb38da 7048c175 msvcp90!std::_Traits_helper::copy_s<std::char_traits<char> >+0x1a [f:\dd\vctools\crt_bld\self_x86\crt\src\iosfwd @ 706] 02d3f2f8 03850fb5 038268fe 77db4d3a 00000020 0x3810000 02d3f2fc 038268fe 77db4d3a 00000020 0000002f CFireWallCOM!DllUnregisterServer+0x2c65f 02d3f314 03824991 77db4d12 03817f2c 00000011 CFireWallCOM!DllUnregisterServer+0x1fa8 02d3f330 038231e0 03817f18 00000000 0000004f CFireWallCOM!DllUnregisterServer+0x3b 02d3f368 0382578d 77db4dca 686123a0 02d3f418 CFireWallCOM!DllCanUnloadNow+0x16da 02d3f37c 76cd43cd 00000040 00000015 00000040 CFireWallCOM!DllUnregisterServer+0xe37 02d3f394 76cd4628 006f2184 685eecd8 00000040 oleaut32!CbSysStringSize+0x48 02d3f3b4 76cd4677 685eecd8 00655c68 02d3f424 oleaut32!SysAllocStringLen+0x5a 0:006:x86> r eax=c0000035 ebx=00000000 ecx=00000000 edx=00000000 esi=779b0054 edi=00000000 eip=779b0066 esp=02d3e6a0 ebp=02d3e744 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202 ntdll_77990000!NtCreateFile+0x12: 779b0066 83c404 add esp,4 0:006:x86> !error c0000035 Error code: (NTSTATUS) 0xc0000035 (3221225525) - Object Name already exists. 0:006:x86> dc 006fe1d8 006fe1d8 +255 006fe1d8 003a0043 0055005c 00650073 00730072 C.:.\.U.s.e.r.s. 006fe1e8 0041005c 004d0044 004e0049 007e0049 \.A.D.M.I.N.I.~. 006fe1f8 005c0031 00700041 00440070 00740061 1.\.A.p.p.D.a.t. 006fe208 005c0061 006f004c 00610063 005c006c a.\.L.o.c.a.l.\. 006fe218 00650054 0070006d 0000005c 005a005a T.e.m.p.\...Z.Z. 006fe228 1171efd4 80000000 005300f4 00720074 ..q.......S.t.r. 006fe238 006e0069 00460067 006c0069 00490065 i.n.g.F.i.l.e.I. 006fe248 0066006e 005c006f 00340030 00390030 n.f.o.\.0.4.0.9. 006fe258 00340030 00300042 0046005c 006c0069 0.4.B.0.\.F.i.l. 006fe268 00560065 00720065 00690073 006e006f e.V.e.r.s.i.o.n. 006fe278 00000000 0000006c 1171efc1 88000000 ....l.....q..... 006fe288 003a0043 0057005c 006e0069 006f0064 C.:.\.W.i.n.d.o. 006fe298 00730077 0073005c 00730079 00650074 w.s.\.s.y.s.t.e. 006fe2a8 0033006d 005c0032 00620077 006d0065 m.3.2.\.w.b.e.m. 006fe2b8 0066005c 00730061 00700074 006f0072 \.f.a.s.t.p.r.o. 006fe2c8 002e0078 006c0064 0000006c 0000006c x...d.l.l...l... 006fe2d8 1171efca 80000000 000000ff 00000000 ..q............. 006fe2e8 00000000 00000000 1171efcf 80000000 ..........q..... 006fe2f8 000000fc 00000000 00000000 00000000 ................ 006fe308 00000000 00000000 00000000 00000000 ................ 006fe318 1171eff2 80000000 00000101 00000000 ..q............. 006fe328 00000000 00000000 1171eff7 80000000 ..........q..... 006fe338 0000010a 00000000 1171eff9 80000000 ..........q..... 006fe348 00000106 00000000 00000000 00000000 ................ 006fe358 00000000 00000000 00000000 00000000 ................ 006fe368 1171effc 80000000 0000010b 00000000 ..q............. 006fe378 00000000 00000000 00000000 00000000 ................ 006fe388 1171efe0 80000000 11710115 80000000 ..q.......q..... 006fe398 00000110 00000000 00000000 00000000 ................ 006fe3a8 00000000 00000000 00000000 00000000 ................ 006fe3b8 1171efe6 80000000 00000115 00000000 ..q............. 006fe3c8 00000000 00000000 00000000 00000000 ................ 006fe3d8 00000000 00000000 1171efed 80000000 ..........q..... 006fe3e8 00000120 00000000 00000000 00000000 ............... 006fe3f8 00000000 00000000 00000000 00000000 ................ 006fe408 1171ef10 80000000 0000011f 00000000 ..q............. 006fe418 00000000 00000000 00000000 00000000 ................ 006fe428 00000000 00000000 ........ 0:006:x86> dc 02d3e6e0 02d3e6e0 00000018 00000000 02d3e71c 00000040 ............@... 02d3e6f0 00000000 02d3e708 00000000 00000000 ................ 02d3e700 00000000 00000000 0000000c 00000002 ................ 02d3e710 00700101 38185478 01ca767f 021a0068 ..p.xT.8.v..h... 02d3e720 00707c60 00000020 00000002 02d3e748 `|p. .......H... 02d3e730 00000000 00707c60 00000000 00620060 ....`|p.....`.b. 02d3e740 00000002 02d3e7a0 76ea519c 00000060 .........Q.v`... 02d3e750 80100080 00000000 00000000 00000001 ................ 0:006:x86> !handle 18 7 Handle 0000000000000018 Type Key Attributes 0 GrantedAccess 0x20019: ReadControl QueryValue,EnumSubKey,Notify HandleCount 2 PointerCount 3 Name \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\Nls\Sorting\Versions 0:006:x86> dc 034c7b34 034c7b34 5753504f 00005441 00005c2f 00005c2f OPSWAT../\../\.. 034c7b44 54535953 435c4d45 65727275 6f43746e SYSTEM\CurrentCo 034c7b54 6f72746e 7465536c 7265535c 65636976 ntrolSet\Service 034c7b64 00005c73 5c3f3f5c 00000000 74737953 s\..\??\....Syst 034c7b74 32336d65 0000005c 54535953 32334d45 em32\...SYSTEM32 034c7b84 0000005c 74737973 32336d65 0000005c \...system32\... 034c7b94 0000005c 7379535c 526d6574 5c746f6f \...\SystemRoot\ 034c7ba4 00000000 6578652e 00000000 4558452e .....exe.....EXE 0:006:x86> lmvm FWManager start end module name 03450000 03502000 FWManager C (export symbols) FWManager.dll Loaded symbol image file: FWManager.dll Image path: C:\PROGRAM FILES (X86)\COMMON FILES\PURE NETWORKS SHARED\Platform\FWManager.dll Image name: FWManager.dll Timestamp: Tue Dec 02 19:08:19 2008 (4935CDF3) CheckSum: 00000000 ImageSize: 000B2000 File version: 2.5.14.1 Product version: 2.5.14.1 File flags: 0 (Mask 17) File OS: 4 Unknown Win32 File type: 2.0 Dll File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: OPSWAT, Inc. InternalName: FWManager OriginalFilename: FWManager.dll ProductVersion: 2, 5, 14, 1 FileVersion: 2, 5, 14, 1 LegalCopyright: Copyright (C) 2004 0:006:x86> lmvm CFireWallCOM start end module name 03820000 03873000 CFireWallCOM C (export symbols) CFireWallCOM.dll Loaded symbol image file: CFireWallCOM.dll Image path: C:\Program Files (x86)\Common Files\Pure Networks Shared\Platform\CFireWallCOM.dll Image name: CFireWallCOM.dll Timestamp: Tue Dec 02 19:08:45 2008 (4935CE0D) CheckSum: 00000000 ImageSize: 00053000 File version: 2.5.14.1 Product version: 2.5.14.1 File flags: 0 (Mask 3F) File OS: 4 Unknown Win32 File type: 2.0 Dll File date: 00000000.00000000 Translations: 0409.04b0 ProductName: CFireWallCOM Module InternalName: CFireWallCOM OriginalFilename: CFireWallCOM.DLL ProductVersion: 2, 5, 14, 1 FileVersion: 2, 5, 14, 1 FileDescription: CFireWallCOM Module LegalCopyright: Copyright 2004 Given that both of these files pre-date Windows 7 by some time, I'm wondering if they're really Windows 7 compatible. It might be worth taking this data to the vendor (I guess in this case, Cisco) and seeing if they can make any more of this. I don't have time to disassemble and figure out what they're doing, honestly, and Cisco/Linksys should have symbols to do this anyway.

If you have a multi-core (or even a hyper-threaded) system, 50% CPU is really technically 100% of one core, meaning some thread in the process has gone into some sort of tight loop and is likely stuck. It's hard to say given that it's a Network Magic process (and not something we'd have symbols for, like Microsoft products or Firefox), but getting a hang dump of the process while it's chewing up your CPU time is probably the best way to look into it.

Might want to uncheck Automatically Restart in the Startup and Recovery settings of the advanced computer properties to make certain it didn't bluescreen.

You might also want to read the Microsoft KB article on the subject as well.

There's no hotfix for this, because this usually comes down to a processor/motherboard combination problem, a mismatched CPU issue (in multiple CPU systems), or a driver issue (in fact, audio drivers are the usual culprit in driver failures). However, without access to a complete memory dump of a system generated when this occurs, you're only going to get guesses, unfortunately. This has 3 possible causes (look for Event ID 37 in your logs as well - that is a clue it's a CPU issue), but the bugcheck won't give you any clues as to which (it's params are always all 0s). A memory dump analysis is the only way to be sure, short of seeing Event ID 37 also in the logs on that system.

Throw it as hard as you can, or better yet, make some sort of catapult system. It'll likely go really fast for a short bit before it becomes recyclable. Short of that, both will run Win9x or NT4 just fine if you can find drivers (I ran NT4 server on an Armada for years when I was younger for giggles, worked just fine).

That would mean indeed it's because the check for A is failing in fsutil, and using /C or /K causes a new cmd.exe process to spawn to do the check, which will return to the original cmd.exe to continue the next step in the loop regardless of whether or not the previous operation failed or not. Using cmd without switches means it runs the check in the same cmd.exe process, and thus the fsutil command being stuck will block the rest of the drive letters from being parsed. I would suggest using the vbscript I posted above, the wmic command from jaclaz or Yzowl if you must do this in a .cmd file, or make sure you call this with cmd /c or /k.

Hmmm - it actually gets to installing the update, and then hangs. Does the *whole system* hang, or just the installation process? It sounds more like a filter driver interfering with the install, and potentially corrupting system files during the install (which produces the post-reboot problems. Would it be possible to get a memory dump of the entire system once the installation hangs via the keyboard?

Generally you can only sysprep an image twice (the limit is 3, but you'll run into issues after the 3rd time so it's not worth pushing it), and if you're capturing an OEM image there may be issues with that image already. Unless you're not using volume media (and you need to keep the OEM install and activation), you'd be better off installing Vista Enterprise from your VL media and keeping that up-to-date rather than trying to use the OEM image. If you do have to keep the OEM image, you have to be very careful what you do with the system before you sysprep - and I would agree with Trip, that if you're really only adding drivers and apps, you might be better served adding the drivers offline and finding a better way to push the apps down, like a RunOnceEx. Sysprep really becomes less valuable if you aren't making the "gold" image itself.

Happy BIRTHDAY Mr. Snrub!!!!!!

I hate to burst your bubble, but using the new LSIs on some test machines show that they're at least 100MB/sec slower than a 3ware 9xxx overall (and on par with the ICH, speed-wise), and the LSI's data transfers are bursty and somewhat unpredictable, whereas the 3Ware is very stable and steady even in random read/write transfer situations. The LSI chips are a heck of a lot cheaper, but you're getting what you pay for (and not much more, if any, than an ICH, so....).

You could also get this incredibly easily with Win32_LogicalDisk from WMI and some vbscript: RunMeWithCscript() strComputer = "." Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colDiskItems = objWMIService.ExecQuery( _ "SELECT * FROM Win32_LogicalDisk",,48) For Each objDiskItem in colDiskItems If objDiskItem.DriveType = 3 Then Wscript.Echo " Volume: " & objDiskItem.Caption Wscript.Echo " Drive Type: " & objDiskItem.Description Wscript.Echo " Compressed: " & objDiskItem.Compressed Wscript.Echo " File System: " & objDiskItem.FileSystem Wscript.Echo " Volume Size: " & FormatNumber(objDiskItem.Size/1024^3, 2) & " GB" Wscript.Echo " Free Space: " & FormatNumber(objDiskItem.FreeSpace/1024^3, 2) & " GB" Wscript.Echo " VolumeDirty: " & objDiskItem.VolumeDirty Wscript.Echo " VolumeSerialNumber: " & objDiskItem.VolumeSerialNumber Wscript.Echo "" End If If objDiskItem.DriveType = 5 Then Wscript.Echo " Volume: " & objDiskItem.Caption Wscript.Echo " Drive Type: " & objDiskItem.Description If Not objDiskItem.FileSystem = "" Then Wscript.Echo " File System: " & objDiskItem.FileSystem Wscript.Echo " Volume Size: " & FormatNumber(objDiskItem.Size/1024^3, 2) & " GB" Wscript.Echo " Free Space: " & FormatNumber(objDiskItem.FreeSpace/1024^3, 2) & " GB" End If Wscript.Echo "" End If If objDiskItem.DriveType = 2 Then Wscript.Echo " Volume: " & objDiskItem.Caption Wscript.Echo " Drive Type: " & objDiskItem.Description If Not objDiskItem.FileSystem = "" Then Wscript.Echo " File System: " & objDiskItem.FileSystem Wscript.Echo " Volume Size: " & FormatNumber(objDiskItem.Size/1024^3, 2) & " GB" Wscript.Echo " Free Space: " & FormatNumber(objDiskItem.FreeSpace/1024^3, 2) & " GB" End If Wscript.Echo "" End If Next '//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ '// Subroutine: RunMeWithCScript() '// '// Purpose: Forces the currently running script to use Cscript.exe as the Script '// engine. If the script is already running with cscript.exe the sub exits '// and continues the script. '// '// Sub Attempts to call the script with its original arguments. Arguments '// that contain a space will be wrapped in double quotes when the script '// calls itself again. To verify your command string you can echo out the '// scriptCommand variable. '// '// Usage: Add a call to this sub (RunMeWithCscript) to the beggining of your script '// to ensure that cscript.exe is used as the script engine. '//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Public 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 'loop though argument array as a collection to rebuild argument string If instr(arg," ") > 0 Then arg = """" & arg & """" 'if the argument contains a space wrap it in double quotes argString = argString & " " & Arg Next 'Create a persistent command prompt for the cscript output window and call the script with its original arguments scriptCommand = "cmd.exe /k " & engineFolder & "cscript.exe """ & Wscript.ScriptFullName & """" & argString Shell.Run scriptCommand,,False Wscript.Quit Else Exit Sub 'Already Running with Cscript Exit this Subroutine End If End Sub

I guess for OEM kit you'd be safe with these: http://technet.micro...y/bb457078.aspx Yes, those will work on an OEM disc, but you'll also find you've disabled online activation with that install and will have to call the clearinghouse. I suppose if you plan on doing that and you're making an OEM reinstall CD, then that's fine, but otherwise, not a good idea.

Does it also work if you use cmd /K?

Sounds more like a device/firmware issue, or chipset incompatibility. I'll bet it's not OS specific - Linux on the device (assuming hardware RAID and not LVM) will probably repro as well.

There is no system64 - system32 is the native (aka 64bit) system folder, and syswow64 is the WoW64 subsystem system folder, containing the 32bit binaries. You would always run slmgr.vbs from system32, whether on a 32 or 64bit installation.

Agreed - never make a Windows install CD with your own key. On XP it's harder to do as there are no "obvious" default keys, so in the case of an XP or 2003 machine, don't provide a key at all. On Vista+ there are "default" keys that get used when you don't use one in setup and skip the key, and those keys can be used to make an unattend without issue (see the product.ini file inside the sources folder).

Data is stored on a RAID10 on a separate set of disks, and is also backed up to a remote location as well. Since going SSD with my primary drive I'm no longer running in RAID0, but I've run RAID0 for probably as long as Coffee (and originally on a FasTrak as well) with only one instance of drive death - and I restored from an OS backup and all was well within about an hour or so.

Getting an XP CD from another person (an actual physical disc) is a gray area in the US, but it's been a protected way to get access to things not software in the past, so this is probably in the clear. Since we're making a copy of something legally owned (that's what the CoA sticker proves), and we didn't acquire the disc by means of downloading from a source other than Microsoft, the post is legit and should be answered. I see we've made progress, but let's not go overboard here - until the courts say otherwise, borrowing an OS install disc shouldn't be considered in violation of the rules (assuming one owns a legitimate copy of said OS, of course).

If you really want to test a client/server environment, know that you can download Server 2008 R2 on a trial basis - that would be my suggestion. Hacking your OS to run as a server is 1. going to be difficult (not totally impossible, but difficult); 2. violate the EULA for use of the client OS; 3. can be done easily with downloadable trial of 2008 R2, so why work so hard to do it the hard way?

Sounds like you might want to do some required reading first, before asking more DNS questions - these are really pretty basic, and while I'm sure someone here could help, in this instance you really should help yourself. Hint - talk to hostgator about what MX records THEY need to set up so that mail sent to @yourdomain.tld is delivered to one of your IPs if that's what you want to do.

Not sure, and it's going to depend on the bluescreen errors themselves as to what is happening. However, you say that it bugchecks even when trying to reinstall from the installation media?

Sounds more like an issue with the drive or the system (are you using an ISO, or are we talking about an actual DVD disc?), or maybe even just a vLite problem. I have WIM files over 10GB on a USB key and all of my systems seem to boot from and use said WIM files just fine. I have ISOs that I use in Hyper-V that are larger than 4GB, containing WIM files larger than 4GB, and those boot/install just fine as well.

Frontpage 2002 (aka Frontpage 5.0, what it appears you are using) is 8 years old, and designs it's code for browsers from that era. That means Netscape (yes that Netscape, before it became Mozilla) 7.x, IE5.x and 6.x, and even Opera 6.x were the "mainstream" browsers at that time. If you think you need a tool to help you design sites, you would be better off with a product like Expression Web or DreamWeaver - however, learning how to do it by hand is really the best way to learn (from your mistakes), and also if you're learning to earn, you will likely need to know how to do it by hand anyway.

Do not double post.