cluberti

I stand corrected - MS06-024 I guess did have a package. I went through all of my old KB article saves, and there was never a reference to a Win9x package, but I guess one did exist for a time. Wierd .

That's because if you install a version of 5.x on an XP SP2 system newer than 5.1.2600 (say, 5.2.3790.xxxx from visiting a 2K3 TSWeb page), the install of XPSP3 doesn't remove the control, and with some page control you can still force an SP3 system to load the 5.x control rather than the 6.x control. It's to make sure people using an older (unsupported, on XPSP3, btw) control are still patched. The thing that catches most folks is that the v6 control is *disabled* by default when XPSP3 is installed, due to the fact that it's considered insecure (more secure than 5.x, but still an insecure control due to the lack of integrity levels on XP). You could always just use v7 of the connection software as well.

Well, I would suggest providing a list of the installers (package names) that were integrated, and then a list of the 6 of those 10 that still show up once installed is a start. Next, if you were able to run dism against the .WIM file (and image index) that these packages were integrated into showing a list of packages that are in the image, that'd be useful as well: To mount the WIM: Dism /Mount-Wim /WimFile:D:\Win7\ISO\sources\install.wim /index:1 /MountDir:D:\mount To get the package list: Dism /image:D:\mount /Get-Packages /Format:Table To unmount the WIM: Dism /Unmount-Wim /MountDir:D:\mount /discard Again, replace "D:\Win7\ISO\sources\install.wim" with the path to the WIM file we're talking about, replace the # in "/index:#" with the index # of the instance inside the WIM you actually slipstreamed the packages into, and replace "D:\mount" with the folder you'd like to use to hold the WIM file while mounted.

Look in the registry editor, specifically at the HKEY_CLASSES_ROOT\txtfile key, and see what's under \shell\open\command\ subkey. The (Default) expand value, by default on an XP install, should point to "SystemRoot%\system32\NOTEPAD.EXE %1". This key (txtfile) is where the right-click "Open with" menu is built from, so it's highly likely this location in the registry has been modified for some reason and no longer contains a valid command key and value.

Looks like a bug: http://blogs.msdn.com/7/archive/2009/12/03...audit-mode.aspx I've got this spawning from another script I have running at the user's desktop as a SynchronousCommand, and I'll see if it works.

Since WinPE doesn't have a file explorer, and those dialogs are part of explorer, there aren't any unless you've managed to hack explorer.exe onto a PE image.

No need to use vLite if all you want to do is package up the image onto an installable medium (or make an ISO out of it for burning to DVD) - that's what oscdimg.exe from the WAIK is for. To make a Win7 bootable ISO via oscdimg, you would execute the following command from a "Deployment Tools Command Prompt" under the Windows AIK folder in the start menu (where D:\Win7\ISO is the folder containing the Win7 source you've modified, and D:\Win7.iso is the ISO file you want to create - change as necessary/desired): oscdimg -u2 -m -o -h -lWIN7 -b"C:\Program Files\Windows AIK\Tools\PETools\amd64\Boot\etfsboot.com" D:\Win7\ISO D:\Win7.iso Note the above command assumes you're doing this to an x64 installation of Windows - if you're running the command on a 32bit (x86) installation source, replace "amd64" in the above command with "x86" (everything else is the same). This command takes the Windows 7 DVD source from "D:\Win7\ISO" and creates a bootable ISO image "D:\Win7.iso" that you can burn to DVD (or test in a VM, etc).

Honestly, not sure - would be worth asking over at the Deployment Guys' blog. However, if you had a portable partition/format app that ran as an .exe, you could probably insert it into the task sequence before that point and disable the task sequence pre-existing partition/format step. It could work, I would think.

There's no need to double-post (in fact, it's a violation of rule 2.b, so consider this a warning). If someone knew the answer to your question, they would have responded. Give it time.

We locked down the DB and it happened again. If something happens to this account in the near future, I would strongly suggest simply using a different user name just as a test - we're looking into it, but it's pretty much the twilight zone with this one.

Then what about images? I know it's an old version, but it smacks of poor design.

What is OOBE not automating, i.e. what's being prompted?

MS06-024 was only released for Windows 2000 and XP/2003, and MS06-026 was available for Win98 and WinME at one point but it's no longer publicly available (it was removed around July of 2007).

I've already tracked it to a driver, and there was no indication the CPU was overclocked - it's a stock E8500: 0: kd> !sysinfo cpuinfo [CPU Information] ~MHz = REG_DWORD 3166 Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0 Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0 Identifier = REG_SZ x86 Family 6 Model 23 Stepping 10 ProcessorNameString = REG_SZ Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz Update Signature = REG_BINARY 0,0,0,0,4,a,0,0 Update Status = REG_DWORD 2 VendorIdentifier = REG_SZ GenuineIntel MSR8B = REG_QWORD a0400000000 3.16GHz is stock for an E8500: http://processorfinder.intel.com/details.aspx?sSpec=SLAPK http://processorfinder.intel.com/details.aspx?sSpec=SLB9K Not every crash is a hardware problem, but the OP should check to make sure the CPU is within thermal spec. If so, I'd suspect driver, not hardware.

Here's a little hint - if your SQL server is using the paging file at all, you've got serious performance issues - if you're swapping to disk from SQL *at all*, you probably actually need to revisit your tuning and consider turning *down* the max memory size parameter. If that doesn't help, you've underprovisioned the memory in the server and need to add memory and re-tune. If this is an x86 server, you'll have a bit more of a job doing the actual tuning during test to make sure you find the sweet spot between max memory for SQL and the amount of RAM needed on the system than you would on an x64 server, but you have to do it either way. I heard once that "tuning paging files on a SQL server is akin to arranging deck chairs on the Titanic", and it's pretty much spot on. The only reason you would need a paging file at all is to make sure you have enough paging file configured on the Windows volume in the event there's a system crash that needs to generate a memory dump (so paging file == RAM + 64MB, give or take) - it shouldn't matter at all how large it is, where on the disk it is, etc (you most certainly are NOT placing your databases, logfiles, etc on the Windows \ Program Files volume, right? They're all going on separate volumes for DB, logfiles, etc...... right????? ). In a nutshell, there's your SQL tuning hint for the day - if you need more, visiting SQL DBA sites and the Microsoft SQL sites on Technet are your next best option - and you can even call Microsoft for help, as they do provide (for a fee) services such as this.

How large are you making your browser window? For example, first picture is a FF 3.5.7 window at 1024x835 (note the codebox extension outside of the post window container), and the second picture is the same browser, same machine, same site, same page, but at 1123x865, which shows everything "fine". Also note it does it with IMAGES inline too, third picture (it's a picture of this post before I edited it, and so far the fabric of space/time hasn't been rent in two, yet... ):

Given it's 4GB of RAM, unless he needs x64 (or plans on upgrading this to Win8 in the future), he doesn't need x64. I would always recommend it over 32bit in a situation like this, but if you've already got a retail copy of another version of Windows and that Windows is not XP, it should be just fine.

Note that a paging file (virtual memory pages on disk) is in no way related to a kernel memory pool (paged pool or nonpaged pool). In a 10,000 ft view, a kernel memory pool is a location that drivers and other kernel modules can allocate (and hopefully de-allocate when finished) chunks of address space. The only real difference between the paged pool and the nonpaged pool (other than size - paged pool is always much larger than nonpaged pool) is the fact that the paged pool can all be paged to disk if the memory manager deems it necessary, but nonpaged pool MUST always reside in RAM (hence "paged pool" and "nonpaged pool"). As to the paging file on a SQL server, I believe the SQL performance whitepapers discuss this subject, and I would strongly suggest following that guidance.

A sufficiently large codebox causes it in IE8 and FF, and I'd be willing to wager a lot of the overflow-x and overflow-y CSS is causing it. It's one of the very specific areas IE and FF are actually similar, and given the exact behavior between the two (which is rare), I'd say it's probably not easily fixable. Again, "smaller" code boxes seem to look just fine - but when they get large, they overflow.

It's a part of the Windows Live Essentials bundle now, specifically it gets installed when you install the Windows Live Toolbar: http://download.live.com/

Yes, you are remembering correctly - in the beta, if you clicked the icon again it would "lock" it's preview bar. However, that never made it past the beta (it was gone in RC1).

Paged pool memory is a kernel resource - I suggest strongly, if you're going to be getting into doing low-level system optimization, to purchase or borrow Windows Internals' 4th Edition (5th if you are looking at Vista or Win7 machines).

Run resmon to see what the RAM is actually "doing". You'll see whether or not it's actively in use, on the standby list (idle pages that are marked as paged, but not paged to disk yet because load doesn't require it), and actual "free" memory. In general, there should be no "free" memory (this is normal) due to Windows 7's caching, and the standby and in use pages will probably be the bulk of what is "used". The modified list is simply pages that have been modifed, but haven't been used in a time and are no longer counted against the process working set of the process that created the allocations - these are similar to pages on the standby list.

The last I saw it was back in 2007, and unless you're running a laptop that needs it (and I don't really think most laptops other than Thinkpads do) it's not worth having, honestly.

Aaaah - SQL does it's own memory management and hosts it's own cache. What I stated won't apply for SQL (and in fact, a 64K cluster size in certain scenarios is actually correct). I always forget about SQL .