jmonroe0914

LOL

Perhaps you're having difficulty reading, as I never once belittled the OP... to the contrary, I gave them a compliment. On a side note, I could care less how many posts you've made, who you are, or your hubristic perspective... your social skills are horrendous, and I really would encourage you to research how to interact with people in an amicable fashion. By all means, you can continue to behave in this childish manor and you'll be ignored.

I'd encourage you to learn how to interact with people and read up on social skills... To believe anyone is going to pay any attention to someone with the tonality in your last post is ignorant to say the least. If you're an adult, act like it... if you're a child, gain some maturity. One would have to choose to install CCC, as it doesn't just magically appear. If someone wants to, in your words, "obliterate it period", that's generally referred to as an uninstall. CCC is installed as it's management software for AMD graphics cards, however, editing the registry to simply prevent it from starting is going overboard. I don't remember if CCC is a required install for AMD drivers since AMD no longer uses CCC. If it is a required install, in your words, "obliterating it" will more than likely lead to issues while utilizing the discrete graphics card.

That is totally not what I'm doing.Per your previous post, "I want to be able to delete them keys to stop Catalyst from starting up with windows 10". There are far easier ways to do this than by editing the registry directly I'm confused by the rest of your post, as it's not about disabling startup entries/services, which is all I was addressing in my previous post.

When taken into the context of your replies to my posts over the past two hours, one would not infer that was your reasoning.

And you repeatedly ask if I have real world experience? Are you sure you're not projecting? dism /export-image /sourceimagefile:z:\install.wim /sourceindex:1 /destinationimagefile:z:\install.esd /compress:recovery /checkintegrity One could also download the ESD2WIM zip file that's been on this forum for years, which includes it's own DISM folder and cmd script.

Since you seem really intent on someone, as you put it, "trying to prove us idiots", expensive, in the way it was used, implied monetary cost. Something can not be monetarily expensive when it's free. By all means, launch into the conspiratorial, tinfoil hat, nonsensical replies about nonexistent points... you and others are superb at it. I however, have far more important things to do that waste time with individuals partaking in this type of nutjob absurdity. Have a wonderful day =]

As I said before, I've wasted enough time discussing meaningless nonsense. Have a wonderful day =]

Around here allot of people aren't happy with that little he might want less than two gigs I was asking how small they wanted it in order to offer suggestions on how to ensure it's a smaller image... normally, one would construe what I asked as meaning that. ESD was mentioned because it has a more efficient compression ratio.

Until something is proven as inaccurate by Microsoft, or any company, then you must accept what is said at face value... we're not talking about something crazy or major, we're talking about the reason an update was pulled for a few hours. Why anyone would choose to be conspiratorial about that and rant about it is beyond comprehension. I assume members on this forum are intelligent, but choosing to argue a nonexistent point, giving in to conspiratorial ideologies and the belief that corporations are out to personally get you while wearing a tinfoil is simply absurd and ludicrous. There are sites for that line of thinking... this is not one on them. Saying that a company supports something when they say they don't is absurd... let's make the assumption you're perspective is accurate. It's simply bad business for the manufacturer, and since board manufacturers are in business to make as much of profit as possible, to not list OSes that are supported, as it would affect profit margins. This is another non-existent point... I don't know you, you don't know me, and as far as I know, you don't work for the board manufacturer(s). Without some sort of evidence from a manufacturer that the information you claim to be right is indeed right, one must trust the source [the manufacturer] and not a third party [you or any other user]. To believe otherwise is simply ignorant and a recipe for disaster in life. Either way, it's a beautiful day and I've spent as much time as I'm going to spend on this discussion, trying to show rationale and logic where it's seriously lacking. You will probably disagree, and that's ok... we will simply have to agree to disagree. Best of luck to you =]

You asked one question [in this thread], of which I repeatedly ignored due to the obvious. If you don't understand why it was ignored, please re-read my previous post above and/or simply glance at any post I've made... the answer is in every post.

The Task Manager has the ability to disable/enable startup items. Services.msc allows configuring the auto startup of services. Nirsoft and Sysinternals both offer free programs to manage startup entries. There's no right or wrong way to disabling startup programs, and the way you're doing it isn't wrong... it's simply making more work for yourself than needs to be exerted to get what you want.

To believe my posts are "trying to prove us idiots" really demonstrates looking at forum posts with the absolute wrong perspective. How one could formulate such an opinion based on what I've written is beyond perplexing. I'd encourage you to re-read posts I've written with a neutral perspective instead of one of hubris, believing someone, or anyone, is trying to what? embarrass you? argue their right and you're wrong? what? I couldn't care less who's right and wrong... i care about factual information. When I'm wrong, I have no problem admitting it... when you're wrong, you're wrong... it's really as simple as that. However, to read from a perspective of hubris will lead one to respond with hubris.

Totally misread that... my bad (previous posts have been edited)

misread, my mistake

Again, show me a desktop board that says a server OS is a supported OS for the board... there's a reason why there's two different boards for the two different types of OSes and it's more than just drivers. Edit: I've opened up 5 random desktop motherboard pages from both Asus and Gigabyte, and not a single one says it's compatible with a server OS. The second one I looked at has drivers for several desktop OS. http://b2b.gigabyte.com/products/product-page.aspx?pid=4468#dl Now answer me do you have any real experiences? Per the Specifications: OS Supported Windows Server 2008 SP2 (x86) & R2 (x64) Windows Vista SP2 (x86/x64) Red Hat Enterprise Linux 5.6 (x86/x64) Red Hat Enterprise Linux 6.11 (x86/x64) SUSE Linux Enterprise Server 11.1 (x86/x64) VMware ESXi 5.0 / 5.1 / 5.1 U1 / 5.1 U2 Totally misread, my mistake

Actually in Windows NT systems Desktop OS and Server OS are historically EXACTLY THE SAME with just a bunch of very minor changes, mostly due to Commercial/Licensing reasons. It is entirely possible that the yet to be released Server 2016: https://en.wikipedia.org/wiki/Windows_Server_2016 will be not remotely similar to Windows 10, but allow me to doubt it. jaclaz Everyone is welcome to their opinions, however, I ask again: Please show me a desktop board that says a server OS is a supported OS for the board... there's a reason why there's two different boards for the two different types of OSes and it's more than just drivers.

Again, show me a desktop board that says a server OS is a supported OS for the board... there's a reason why there's two different boards for the two different types of OSes and it's more than just drivers. Edit: I've opened up 5 random desktop motherboard pages from both Asus and Gigabyte, and not a single one says it's compatible with a server OS.

Show me a desktop board that says a server OS is a supported OS for the board... there's a reason why there's two different boards for the two different types of OSes and it's more than just drivers. You can run a gas car engine on E85, even when it's not compatible with E85. It will cause fuel injector failure over time, among other things. Simply because one can run an OS on a board that wasn't designed for it does not mean it's a good idea and should be done.

Starting when? jaclaz I'd like to know that too I ran server 2003 as a desktop OS for awhile. I missed the "generally" that should have preceded the first part: "server OSes cannot generally run on PC motherboards", as the last part had it included "just as server boards can generally not run desktop OSes" Post has been updated.

Right, that must be what motivates me. It couldn't be actual experience, knowledge, or insight. This site has, quite wonderfully, a large collection of people on whom BS doesn't work. Adult people, and even young ones with uncommon sense. I've been Microsoft's staunchest supporter throughout my near 40 year software engineering career. Ask anyone around here - only a few short years ago I sounded a lot more like you, jmonroe, looking for the good. Unfortunately, there isn't any to be found. I have Windows 10 running like a well-oiled machine and I'll wager I know how to do that as well as or better than you do. Guess what? By ANY objective or subjective measure it's STILL not better than - nor arguably even as good as - its predecessors, which I ALSO have running like well-oiled machines. Stirring up trouble on forums can be fun, just try to stop accusing others, directly or indirectly, of being motivated by something other than reality. Sometimes reality just bites. -Noel I'm not sure what it is with you and hubris and hostility... I really would encourage you to read things with a different perspective than you have been. Simply because someone shares information that shows your perspective and/or opinion is factually inaccurate or you're misinformed, is not a personal attack... which appears to be how you take anything that runs contrary to what you believe or write. One can either entertain conspiratorial ideologies and believe Microsoft is out to personally get you, or one can look at the facts of a situation and go from there. The facts are b1511, prior to being pulled, inadvertently exposed the advertising id and other personal information to third parties (i.e. app devs), even though a user may have disabled that, and other, information from being shared. This was fixed within a short period of time and b1511 was again pushed to WU servers. I ask again, would anyone rather they left it up and not informed users of the inadvertent privacy settings reset? My hunch is, you, and others, would be here ranting about that if it had occurred. You appear to be under the impression this is a who's right contest... it isn't. I couldn't care less who is right and who is wrong, I simply care about facts over opinions and ensuring accurate information is discussed. I would hope that's how any person on this forum would view conversations, seeming as this forum caters to the intelligent (a compliment, not a criticism).

You're making the disabling of startup items and services far more complicated than it needs to be. There are legitimate uses for editing the registry directly... this is not one of them, mainly because you are literally making what you're trying to accomplish far more difficult than it needs to be.

Have you come across this issue on Windows 10? You still appear to have a massive misunderstanding as to what the pagefile is and why it's needed. I really would encourage you to read the technet blog I linked to.

Perhaps you meant to type pagefile and not RAM, as you can't seriously believe someone wouldn't need more than 16GB, or have a use for more than 16GB. Simply because someone is knowledgeable in their field of study does not mean they know everything, or do not have inaccurate understandings of different things. To believe otherwise is to be a fool.

Perhaps I'm missing something, but not only does fragmentation not matter with SSDs, with HDDs every file operation will cause fragmentation over a short period of time. This is why you should have a task run once a week to defrag your HDD, much the same as you would set *nix cron jobs on a zpool to scrub the pool, run smartctl on your disks, etc. It's common maintenance for your HDD, much the same as oil and brake changes are for your car. The page file is used by Windows to hold temporary data which is swapped in and out of physical memory in order to provide a larger virtual memory set. This may help you understand what it is and why it's needed. See last sentence above. You appear to have an factually inaccurate understanding of what virtual memory is for and why it's needed. As far as over-provisioning goes, while you can physically set this on SSDs (it's a requirement for the health of the drive), on HDDs it's common knowledge to not fill the drive beyond 90% capacity. I'm not aware of anything that allows you to physically set over provisioning on an HDD, however I'd be interested to learn of a way if you're aware of any that exist. What issue are you implying you would or would not have? You also appear to have an factually inaccurate understanding of what virtual memory is for and why it's needed.