cluberti

The IE8 files aren't removed when you remove the feature - removing the feature only removes the shellexecute functionality. Since IE is responsible for hosting things like HTML help (in the OS, and anywhere else it's used), making the COM webbrowser control available to non-IE apps to host mshtml, etc, it's not really advisable to remove the files. If the F12 tools aren't working, it would be wiser to take a hang dump of the iexplore.exe process(es) when hung to see why they hung up in the first place.

Any particular reason you're using that one instead of this one? I'm assuming there's a specific reason.

Correct - IE's accept headers do not explicitly state support for application/xhtml+xml, therefore you shouldn't serve that to any version of IE and expect good results (as per the best practices guide linked). You should use application/xml or text/html and let the parser determine the renderer via the doctype. Note that while IE6 (to an extent), and IE7/IE8 support rendering XHTML documents, it still doesn't accept the header application/xhtml+xml.

No, make a new thread. Even if you end up rebuilding, it's always a good learning experience (so it doesn't happen on the rebuild, for instance).

Consider reading this post before you do.

Well, it is as I thought, a leak: // Running out of nonpaged pool is bad: kd> !vm *** Virtual Memory Usage *** Physical Memory: 130668 ( 522672 Kb) Page File: \??\C:\pagefile.sys Current: 786432 Kb Free Space: 714960 Kb Minimum: 786432 Kb Maximum: 1572864 Kb Available Pages: 3856 ( 15424 Kb) ResAvail Pages: 78301 ( 313204 Kb) Locked IO Pages: 140 ( 560 Kb) Free System PTEs: 252206 ( 1008824 Kb) Free NP PTEs: 0 ( 0 Kb) Free Special NP: 0 ( 0 Kb) Modified Pages: 599 ( 2396 Kb) Modified PF Pages: 599 ( 2396 Kb) NonPagedPool Usage: 32766 ( 131064 Kb) NonPagedPool Max: 32768 ( 131072 Kb) ********** Excessive NonPaged Pool Usage ***** PagedPool 0 Usage: 4081 ( 16324 Kb) PagedPool 1 Usage: 1101 ( 4404 Kb) PagedPool 2 Usage: 1128 ( 4512 Kb) PagedPool Usage: 6310 ( 25240 Kb) PagedPool Maximum: 43008 ( 172032 Kb) ********** 27235 pool allocations have failed ********** Session Commit: 967 ( 3868 Kb) Shared Commit: 1271 ( 5084 Kb) Special Pool: 0 ( 0 Kb) Shared Process: 3189 ( 12756 Kb) PagedPool Commit: 6310 ( 25240 Kb) Driver Commit: 3053 ( 12212 Kb) Committed pages: 125376 ( 501504 Kb) Commit limit: 318787 ( 1275148 Kb) // Without pool tagging enabled, I can't see the pool tags to see where it is being consumed: kd> !poolused unable to get PoolTrackTable - pool tagging is disabled, enable it to use this command Use gflags.exe and check the box that says "Enable pool tagging". // However, I did track the LPC message back to the system driver thread where the *real* error occurred: kd> !thread 825c8020 THREAD 825c8020 Cid 0004.0024 Teb: 00000000 Win32Thread: 00000000 WAIT: (WrLpcReply) KernelMode Non-Alertable 825c8214 Semaphore Limit 0x1 Waiting for reply to LPC MessageId 0003a62b: Current LPC port e15c0e38 Not impersonating DeviceMap e1004460 Owning Process 0 Image: <Unknown> Attached Process 825ca830 Image: System Wait Start TickCount 1035902 Ticks: 12 (0:00:00:00.187) Context Switch Count 86474 UserTime 00:00:00.000 KernelTime 00:00:00.750 Start Address nt!ExpWorkerThread (0x805348ee) Stack Init f8ab2000 Current f8ab1a90 Base f8ab2000 Limit f8aaf000 Call 0 Priority 12 BasePriority 12 PriorityDecrement 0 DecrementCount 16 ChildEBP RetAddr Args to Child f8ab1aa8 80500ca6 825c8090 825c8020 804f9d10 nt!KiSwapContext+0x2e (FPO: [Uses EBP] [0,0,4]) f8ab1ab4 804f9d10 825c81e8 825c8020 80553760 nt!KiSwapThread+0x46 (FPO: [0,0,0]) f8ab1adc 80598b53 00000000 00000011 00000000 nt!KeWaitForSingleObject+0x1c2 (FPO: [5,5,4]) f8ab1b14 80598c9f e15c0e38 823da770 f8ab1b4c nt!LpcpRequestWaitReplyPort+0x43d (FPO: [4,4,0]) f8ab1b2c 8060a715 e15c0e38 f8ab1b4c f8ab1b4c nt!LpcRequestWaitReplyPortEx+0x21 (FPO: [3,0,0]) f8ab1cd0 8060a876 c0000222 00000001 00000001 nt!ExpRaiseHardError+0x1bd (FPO: [Non-Fpo]) f8ab1d40 805731bf c0000222 00000001 00000001 nt!ExRaiseHardError+0x13e (FPO: [6,17,0]) f8ab1d74 805349ee 00000000 00000000 825c8020 nt!IopHardErrorThread+0x53 (FPO: [1,3,0]) f8ab1dac 805c5c84 00000000 00000000 00000000 nt!ExpWorkerThread+0x100 (FPO: [1,8,0]) f8ab1ddc 80541bc2 805348ee 00000001 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo]) 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 kd> !error c0000222 Error code: (NTSTATUS) 0xc0000222 (3221226018) - {Delayed Write Failed} Windows was unable to save all the data for the file %hs. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. It's worth noting that xpoolmap does show a large amount of nonpaged pool used to regions of KernelSpaceUsageNonPagedPoolExpansion, but all of the expanded pool is corrupted: kd> dc ffbc1000 ffbc1000 0000680d 625a5422 a868c5ff 00000000 .h.."TZb..h..... ffbc1010 7557e42b 00009aea 625a5422 a86b13c8 +.Wu...."TZb..k. ffbc1020 00000000 c6bcadd1 00001da2 625a5422 ............"TZb ffbc1030 a86b7e19 00000000 1664d797 00006e3b .~k.......d.;n.. ffbc1040 625a5422 a86ee6fe 00000000 858272a9 "TZb..n......r.. ffbc1050 00009ee1 625a5422 a870ce84 00000000 ...."TZb..p..... ffbc1060 5c08bf59 00006378 625a5422 a871a221 Y..\xc.."TZb!.q. ffbc1070 00000000 66c7f4ea 00001da2 625a5422 .......f...."TZb kd> dc 0000680d 0000680d ???????? ???????? ???????? ???????? ???????????????? 0000681d ???????? ???????? ???????? ???????? ???????????????? 0000682d ???????? ???????? ???????? ???????? ???????????????? 0000683d ???????? ???????? ???????? ???????? ???????????????? 0000684d ???????? ???????? ???????? ???????? ???????????????? 0000685d ???????? ???????? ???????? ???????? ???????????????? 0000686d ???????? ???????? ???????? ???????? ???????????????? 0000687d ???????? ???????? ???????? ???????? ???????????????? Unfortunately, you're going to have to enable Pool Tagging in your XP install and reboot, and get another complete dump, before this is going to be of real value.

I apologize for the cross-post in the Win7, Vista, and XP unattended sections, but a few of us are working on updating the MSFN unattended site with a polished, updated guide that will apply to XP, Server 2003, Vista, Server 2008, Windows 7, and Server 2008 R2. It's of course nowhere near ready, but in the meantime I'm posting random bits (some parts polished, others maybe not so much) to my personal blog in the meantime to bridge the gap. Since the XP unattended guide has gone fairly unchanged since 2004, we thought it time to update the content to include the newer operating systems as well. Please take a look, comment, pass the link along if it's good, etc. We're always open for comments and suggestions.

I apologize for the cross-post in the Win7, Vista, and XP unattended sections, but a few of us are working on updating the MSFN unattended site with a polished, updated guide that will apply to XP, Server 2003, Vista, Server 2008, Windows 7, and Server 2008 R2. It's of course nowhere near ready, but in the meantime I'm posting random bits (some parts polished, others maybe not so much) to my personal blog in the meantime to bridge the gap. Since the XP unattended guide has gone fairly unchanged since 2004, we thought it time to update the content to include the newer operating systems as well. Please take a look, comment, pass the link along if it's good, etc. We're always open for comments and suggestions.

I apologize for the cross-post in the Win7, Vista, and XP unattended sections, but a few of us are working on updating the MSFN unattended site with a polished, updated guide that will apply to XP, Server 2003, Vista, Server 2008, Windows 7, and Server 2008 R2. It's of course nowhere near ready, but in the meantime I'm posting random bits (some parts polished, others maybe not so much) to my personal blog in the meantime to bridge the gap. Since the XP unattended guide has gone fairly unchanged since 2004, we thought it time to update the content to include the newer operating systems as well. Please take a look, comment, pass the link along if it's good, etc. We're always open for comments and suggestions.

If this is XP, take a look at the unattended page.

Technically all versions of IE on XP (including IE7 and IE8) will EOL in April 2014, and all of them are in extended support. IE is considered an OS component, and follows the OS lifecycle rather than have one of it's own since it is no longer serviced outside of the OS (no IE service packs, specifically). Meaning even IE8 on XP is in "extended support". So, unless you've got some IE6-only app, drop the hammer on the IE6 users and bump 'em to IE8 to get decent web standards support - they're long past due for an upgrade .

Note that this only applies to retail copies - if you purchased a computer and Windows was installed as part of the transaction (thus a royalty OEM install), you cannot move it. It's tied to the hardware it was purchased on.

These are all minidumps (note the names all start with "Mini"). A kernel or complete memory dump will be (by default) in %windir% called "memory.dmp".

Well question - can you install it manually, outside of using SFX Maker with the same switches and have it work? If so, it would be an SFX Maker problem, as the error indicates a resource problem, not an installer problem. See if it reproduces without SFX Maker in the picture.

No, just make sure the option is set, and your paging file is on the same volume as the \Windows folder and it's at least sized RAM+50MB.

Hiren's boot cd contains non-free (as in, you have to pay the vendor to license it) software, and as such is considered warez (just looking at the list, the first 3 packages are non-free applications - it doesn't get more obvious than that). The very first rule you both agreed to when you signed up for access to the forums forbids discussion of or requesting help in conjunction with the use of warez copies of software. [both of you banned].

dotnet 3.5 package needs only the following switches - /q /norestart /lang:<language code>. For example, to install the English package silently, I used dotnetfx35setup.exe /q /norestart /lang:ENU. If you were trying to install German, I'd guess the language code would be DEU, for example.

Each and every one of these dumps shows a stop error when trying to copy data from the disk (pagefile.sys, so the paging file) to RAM - and each time, it fails with the error 0xc00000009), which is an insufficient resources error (rather than a hardware failure error, so the hardware is likely not at fault here). What I'm guessing is that there's a memory leak on the system causing the issue ultimately over time, but with a minidump none of the vm information is in the dump file so I cannot say with any certainty. Here's the stack, the error, and the reason, for what it's worth: kd> kn # ChildEBP RetAddr 00 f8895520 805c7827 nt!KeBugCheckEx+0x1b 01 f8895544 805c87a1 nt!PspCatchCriticalBreak+0x75 02 f8895574 8053d428 nt!NtTerminateProcess+0x7d 03 f8895574 804ff18d nt!KiFastCallEntry+0xf8 04 f88955f4 804fccb6 nt!ZwTerminateProcess+0x11 05 f88959b0 80500411 nt!KiDispatchException+0x3a0 06 f8895d34 80540c69 nt!KiRaiseException+0x175 07 f8895d50 8053d428 nt!NtRaiseException+0x31 08 f8895d50 75b7b3b9 nt!KiFastCallEntry+0xf8 WARNING: Frame IP not in any known module. Following frames may be wrong. 09 006afff4 00000000 0x75b7b3b9 kd> .trap 0xf8895d64 ErrCode = 00000000 eax=75b7b3b9 ebx=00000001 ecx=006afeec edx=75b489a0 esi=00000001 edi=0000000c eip=75b7b3b9 esp=006afed4 ebp=006afff4 iopl=3 nv up ei pl nz na po nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00003202 001b:75b7b3b9 ?? ??? kd> u eip 75b7b3b9 ?? ??? ^ Memory access error in 'u eip' kd> .exr 0xfffffffff88959d8 ExceptionAddress: 75b7b3b9 ExceptionCode: c0000006 (In-page I/O error) ExceptionFlags: 00000000 NumberParameters: 3 Parameter[0]: 00000008 Parameter[1]: 75b7b3b9 Parameter[2]: c000009a Inpage operation failed at 75b7b3b9, due to I/O error c000009a kd> !error c000009a Error code: (NTSTATUS) 0xc000009a (3221225626) - Insufficient system resources exist to complete the API. If you want anything deeper, you're going to have to provide a *complete* memory dump somewhere.

That would indeed be your opinion . No, I've not found any good that PerfectDisk does in my environments that Diskeeper doesn't already do, and (for me at least) Diskeeper is actually cheaper.

Your apps and settings would come along from XP > Vista > Win7, but not XP > Win7.

No, the z-order is actually *not* LIFO, and in fact an application has to "force" itself to be on top via an API call if it wants to guarantee it, otherwise the shell gets to make that determination. Note that opening a window almost always results in a topmost window, but with things like explorer, or Internet Explorer, where shell and browser extensions (and even drivers) can inject themselves to do things, this can happen. See here for an example.

Yes, but I would still suggest going through the (relative) pain of having to reinstall apps and drivers rather than bring something along to Vista, and then to Win7. It'll probably take the same amount of time too, technically, to do a clean install of 7 and then apps vs upgrading to Vista, then upgrading to Win7.

Diskeeper seems overkill for a single machine or a few boxes, but when you get into supporting literally thousands, having a product that can plug into a GPO and does do a good job of defragmenting volumes (it isn't the best, but it's good), it makes more sense. Also, I agree - religious affiliation (or any other, for that matter) matters not to me when purchasing products. It does a good job, it's not overly expensive, and it's easy to configure - that's all I need, really. It's amazing more vendors don't provide configuration in policies keys (rather than use their own GUI console exclusively for config) for their "enterprise" or "server" versions, considering these are all windows-based products, and are likely to be installed in an enterprise with an AD domain. Reinventing the wheel, it seems, rather than simply use registry policy keys that can be set via group policy.

Looks like today is your birthday dude, so happy birthday! 21 and drinking, I hope! Enjoy some cake and beer - and together, too!