cluberti

Here: http://www.reasonco.com/vista/vistadowngraderights.htm http://download.microsoft.com/download/d/2...grade_chart.doc http://forums.microsoft.com/genuine/showpo...6&siteid=25 jaclaz Right - only system builders and VL customers can downgrade - you do not get downgrade rights when you buy FPP or OEM packs from a retail vendor. The OP is looking at buying OEM from a retail vendor, so no downgrade rights.

I would suggest using autoruns from sysinternals and shellexview from nirsoft.net to disable all non-Microsoft items, and see if the problem continues. If so, we'll probably need to see some data in the form of dumps of explorer.exe to tell you more. But first, try disabling non-Microsoft startup items (autoruns) and non-Microsoft explorer shell extensions (shellexview) and see if that changes the behavior.

I had a 24 + 2x19s for awhile, and I still choose the single 30 .

Downgrade rights?

I could tell you someone did, but I'd be lying . Yes, unfortunately, math is necessary...

I've done both, and I found that 2 monitors were very useful when I had two, but now that I've gotten used to one big monitor (and yes, one 30" is about as big as you want to go unless you want to do your computing a few feet away from your desk), I find that the middle break is annoying. I am limited to where I put windows (nothing can be right in front of me, I have to look right and left) and maximizing windows is something I rarely do - normally I just set a size, close and reopen, and keep it that way.

The Commit number in task manager is not memory usage in RAM, but the (peak/total/current) amount of pagefile-backed virtual address pages in use. These can be in RAM, but these can also be paged out into the pagefile (and thus, not RAM usage), and can also include pages in the dirty and standby lists as well that are backed, but have no mapping page in RAM (nor in any running process). Also, this doesn't count pages that are memory-mapped without backing (like kernel nonpaged pool, potentially the executive, event log data, etc).In short, it's not an accurate measurement of a RAM footprint in the OS, because it only takes into account pages that are pagefile-backed and makes no distinction as to where these pages are, or if they're even still valid process-associated pages. This counter can be somewhat accurate at times, but it could be wildly inaccurate as well and you have no way of knowing for sure without using the method I mentioned above (that is always close to accurate no matter what). Convention doesn't always = correct. Again, it's a metric, but I don't think it accurately measures what fdv is actually trying to measure, as per my comment above.

According to that event log event, thread 80 in the system process (ProcessID 4) did something (scheduled a DPC, called a power state function, something along those lines) that caused the system to disable (in code) certain power management features that your processor exposes to the OS that it supports, but Windows has determined that attempting these functions will cause system instability or worse, hardware problems.I would contact the server vendor for microcode updates (if available) for the CPU, and perhaps a BIOS upgrade as well. If there aren't any, perhaps you should have them investigate these issues on their end to see if they can find the potential hardware problem.

I prefer 1 30", as that's about as much screen real-estate as I can keep straight in my mind .

If you want to find real "RAM" usage, not just commit, you're better off using perfmon counters for a more accurate (less guessing) accounting of RAM/memory used.

The error would have nothing to do with the imaging, per se - the windows kernel itself throws the bugcheck when it determines that the OS has failed to initialize properly (in this case it was Session3, there are Sessions 1-5, bug checks 0x6D to 0x71). The only thing relevant in the bugcheck is the first parameter (please post), as this tells us the status code that caused the kernel to conclude that the initialization of Windows has failed.

Merging two topics here that are the same. Do NOT double-post.

You're falling for one of the biggest scams in the industry - dynamic contrast ratio numbers are not always on the up-and-up, and I see no difference in my Hanns-G vs my Dell 3008WFP for most games, and only when displaying true black and true gray do I see a hint of difference. And I attribute that more to the brightness in the room (and the fact that the $2000 Dell is a better quality monitor than the Hanns-G). But for $600, it comes really close to the Dell in most things.Just don't be fooled by everything you read, especially contrast ratio #s.

Registry entries added to HKU\.Default affect the logon desktop (the desktop you see when you press CTRL+ALT+DEL, or has the user list on it if FUS is enabled). If you want to make sure all users get this, you need to load up the registry hive ntuser.dat from the \Documents and Settings\Default User\ folder, make the changes, and then unload the hive. This KB article was written for NT4, so the paths to the user profile listed in the KB are no longer valid anymore, but the steps for loading the hive itself and making changes are still relevant.

Are they on different subnets? NetBIOS is not a routable protocol (well, not without router trickery) and a WINS server is needed if this is the case with your setup.

Again, correct .

Correct - CAS is for OWA and RPC over HTTP(s) and such, but not SMTP.

It's more than just the file version, it's also QFE vs GDR version of the file. The fix is ONLY in the QFE version, and 872789 includes only the QFE version (which is why it was suggested). However, 925902 also includes the QFE version, but it includes the GDR version (it's public, so it includes both) and GDR is the default install unless you've already got QFE binaries on the box (once QFE, you stay QFE until the next SP when everything goes back to GDR).He could install 925902 manually with the /B:SP2QFE switch to install the hotfix QFE (and get the fix from that package as well), but it's included in XP SP3 (or is supposed to be), but I don't know if it's in 3311 (RC2) or not. If you have this file version and you have SP3 RC2, I would suggest waiting until RTM. If you install SP3 RTM (which should include these two fixes) or go back to SP2 and get the QFE of this on your box as previously mentioned, and the problem still occurs, then either this isn't the actual problem, or the fix isn't working (my money would be on a, but b is always possible - not probable, but possible) and a call to Microsoft (it's free if it's for a hotfix not working case) should help. However, if you aren't married to SP3, or you need to go back to SP2, you will need to install 925902 manually with the /B:SP2QFE switch, or attempt to install 872789.

Office Communicator was released after Office 2007 went RTM, so you have a license for it - but it isn't on the disc. You can get it with your license agreement, obviously you've got licenses for Enterprise, but it's separate. Stop looking on the disc .

I went and did some digging, and the SP1 or SP2 requirement is for INSTALLING on a running system, not slipstreaming. That's why I can seem to slipstream it - because Service Packs are cumulative, and yes, unless they change RC2 before RTM to disallow it, you can indeed slipstream SP3 into an RTM source.

Well, technically in Exchange lingo for 2007 it's not front-end anymore, it's CAS. If you want to move from a one-server setup to a CAS server and Mailbox server setup, you simply add another 2007 server as the CAS role, and remove it from the mailbox server. It's in the documentation, I believe, on how to setup a CAS server.

I would say that 26-28" is probably the middle of the bell curve now - I can find decent ones for under $600 if you aren't a hardcore gamer. I have a Hanns-G 28" that works just fine for regular work and some light gaming with Halo2, and was about $600. I wouldn't use it for Crysis or anything (nor would I play Crysis, but that's not surprising), but it works fine for Halo2 and Half-life, etc.

The beta will only (reliably) install on XP SP2 (although SP3 seems to work, if you're running b3311), 2003 SP2, Vista RTM, Vista SP1, or Server 2008 RTM. If you're running anything else (a beta, a RC, etc), it'll fail with either an error about not being the correct service pack level, or that you are missing updates.

I'm not sure this applies to every user type, though. I tend to have a whole crapload of windows open at any one time, so a 30" is far better than 2 20" monitors would be, but I doubt that everyone is a multitasker like that. I do find that anything less than 24" is utterly ridiculous to try and use now, but that's due to being spoled.

I've successfully done a few hfslip hacks thus far, so if it's important to you I can try to slip in some time in my weekend to figure it out. I know the structure pretty well now, so it shouldn't be that hard. Do you want QFE or GDR binaries?