tag:blogger.com,1999:blog-9481975.post2531651172307307999..comments2024-02-12T03:38:12.487-05:00Comments on Popular Technology.net: Irresponsibly Ripping Apart WindowsUnknownnoreply@blogger.comBlogger17125tag:blogger.com,1999:blog-9481975.post-6162240227349533002007-06-18T16:49:00.000-04:002007-06-18T16:49:00.000-04:00Any service can be disabled without ripping it out...Any service can be disabled without ripping it out.<BR/><BR/>There is no same priciple as Linux because Windows is not built openly and thus you have no idea of the consequences of your actions.<BR/><BR/>There is no way to do the research with Windows to determine what core components you can be safely removed because there is no documentation on this from Microsoft!Andrewhttps://www.blogger.com/profile/05170143101028077396noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-43307690278386941882007-06-17T15:24:00.000-04:002007-06-17T15:24:00.000-04:00Well, say what you will, I suppose. But I use nLi...Well, say what you will, I suppose. But I use nLite to take out Windows Movie Maker, Windows Media Player, Accessibility Options, Outlook Express, and a few other programs that I wouldn't use under any circumstances. I also remove all the Remote Registry and other RPC based remote access services to tighten security. I've yet to suffer any ill effect. <BR/><BR/>Granted, it's possible to causeAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-9481975.post-11180278319670670862007-06-09T14:11:00.000-04:002007-06-09T14:11:00.000-04:00The features go missing for various reasons.Micros...The features go missing for various reasons.<BR/><BR/>Microsoft removed PDF creation from Office 2007 due to Adobe threatening them with legal action.<BR/><BR/>WinFS was not working right ect...<BR/><BR/>Beta Testing has to do with finding bugs, it is not were Microsoft expects to "rip out files", the ones in the final release are all included for a specific reason. The ones that are removed are Andrewhttps://www.blogger.com/profile/05170143101028077396noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-61745043759419650152007-06-09T12:36:00.000-04:002007-06-09T12:36:00.000-04:00If Beta testing has nothing to do with "ripping ou...If Beta testing has nothing to do with "ripping out files" - why do features go missing after RTM? Where did the ability to create PDFs in Office 2K7 go? It was ripped out of the build. What happened to WinFS in Vista??<BR/><BR/>As for asking the person(s) who wrote a particular feature - that's why we have MSDN, Technet and the rather marvellous blogs from the likes of Raymond Chen and Larry Adam Thompsonhttps://www.blogger.com/profile/14369869232893560747noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-12507107762026642372007-06-09T10:29:00.000-04:002007-06-09T10:29:00.000-04:00Before anyone starts talking about "developer docu...Before anyone starts talking about "developer documentation" and "tracing function calls" please show me where the community of hacks is doing this and attempting to clearly document their findings with sources from Microsoft and the potential implications of such. Last time I checked programs like nLite gave no such explanations, warnings or consequences for ripping out component "x"<BR/><BR/>Andrewhttps://www.blogger.com/profile/05170143101028077396noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-85517194204793214652007-06-09T10:20:00.000-04:002007-06-09T10:20:00.000-04:00One person or a few allegedly having "no problems"...One person or a few allegedly having "no problems" by ripping out components justifys and proves nothing. Once you remove something from the default install in a way Microsoft does not specify and run into ANY issues later down the line you can never be sure that it was not because of your actions.<BR/><BR/>The Windows XP Embedded Team has direct access to the programmer(s) and team(s) who wrote Andrewhttps://www.blogger.com/profile/05170143101028077396noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-39800744292586051522007-06-09T10:07:00.000-04:002007-06-09T10:07:00.000-04:00I am well aware Windows was not developed by one p...I am well aware Windows was not developed by one person but when an internal programmer wants to know how something works they talk to the person(s) who developed it to accurately understand the implications of it.<BR/><BR/>Release Candidates and Betas are to hunt for bugs and unusual activity not picked up by internal Beta testing. It is a refinement process and has nothing to do with ripping Andrewhttps://www.blogger.com/profile/05170143101028077396noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-44848561524185725472007-06-09T09:58:00.000-04:002007-06-09T09:58:00.000-04:00You can simply disable services via the built-in s...You can simply disable services via the built-in services GUI: services.msc<BR/><BR/>This will have the same effect on security and boot performance. However the TaskScheduler Service needs to remain set to automatic for optimal Windows and application load times.<BR/><BR/>Ripping them out does nothing but cause potential compatibility problems. You actually can cause more errors by ripping them Andrewhttps://www.blogger.com/profile/05170143101028077396noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-59088073801026666592007-06-09T08:48:00.000-04:002007-06-09T08:48:00.000-04:00That's not the point andrew. Some users want the c...That's not the point andrew. Some users want the choice of installing files and services. The fewer services are run and are present, the better the overall security of the system. Fewer code means fewer bugs. <BR/><BR/>Now that MS choose not to document most of it's files and services is not the programmers error. We want to have a choice !idiotequehttps://www.blogger.com/profile/07196221728624348162noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-68990803913655490372007-06-08T23:55:00.000-04:002007-06-08T23:55:00.000-04:00Unless you were the programmer, you are by default...Unless you were the programmer, you are by default - ignorant?<BR/><BR/>Well, in that case - everybody is ignorant. Windows isn't developed by one person on their own.<BR/><BR/>As for trial and error - if bits of Windows didn't get included/excluded by trial and error - why the need for Release Candidates and Betas?Adam Thompsonhttps://www.blogger.com/profile/14369869232893560747noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-91369057137970930052007-06-08T19:08:00.000-04:002007-06-08T19:08:00.000-04:00XP can be as customizable as one wants it to be. A...XP can be as customizable as one wants it to be. After all, Microsoft do have "XP Embedded" that developers that don't work for Microsoft can use to build their own customized version of Windows XP by adding/removing whatever components they deem necessary. nLite is doing the same thing but in reverse, working with the full pre-built file set and removing the files associated to specific tasks. <Arnehhttps://www.blogger.com/profile/17031748493572387511noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-33868682821549752812007-06-07T10:29:00.000-04:002007-06-07T10:29:00.000-04:00Unless you were one of the programmers who placed ...Unless you were one of the programmers who placed the file there you are by default ignorant. You may know of A function or some functions of a file but it is simply impossible for you to know them all unless you were the one who put it there. The fact that you think you know makes you even more ignorant. Windows may be a multi-purpose OS but in use only. It is not a customizeable OS outside of Andrewhttps://www.blogger.com/profile/05170143101028077396noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-76888298839360754072007-06-07T10:20:00.000-04:002007-06-07T10:20:00.000-04:00fools errand? Just because it doesn't appeal to yo...fools errand? Just because it doesn't appeal to you doesn't make it insane. Not everybody that that rips windows is totally ignorant of the risk and not everyone totally strips his system. we do know of the functions of certain files and if they are useless to our purpose why keep them? Program compatibility is the reason we stick with Windows. Some of you seem to be running Windows for Windows; Unknownhttps://www.blogger.com/profile/02908151980681059227noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-11319633681978329312007-06-05T06:23:00.000-04:002007-06-05T06:23:00.000-04:00Trial and Error is completely useless. It is impos...Trial and Error is completely useless. It is impossible for Trial and Error to determine why a file exists, only the programmer(s) who put it there know why. You cannot determine every application that relies on these files being present. A perfect example is the Windows XP Task Scheduler Service which is necessary for the performancing enhancing Prefetch feature to work properly yet many Andrewhttps://www.blogger.com/profile/05170143101028077396noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-44421361454896733692007-06-05T04:26:00.000-04:002007-06-05T04:26:00.000-04:00I must say that trial and error is far from useles...I must say that trial and error is far from useless in this case, though I agree with you in part. If someone wants a faster OS than XP, they shouldn't bother using XP. Either go for an OS designed to be insanely fast, or get a last-generation OS. Though the latter option can be risky if you don't bother too much about your own security...Anonymoushttps://www.blogger.com/profile/06471602239255611971noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-26482354422855382992007-06-05T03:10:00.000-04:002007-06-05T03:10:00.000-04:00That is idiotic. The files were not added by trial...That is idiotic. The files were not added by trial and error and trial and error does not determine why they were added. Until that is known completely and fully you can make no such judgements and trial and error is useless.Andrewhttps://www.blogger.com/profile/05170143101028077396noreply@blogger.comtag:blogger.com,1999:blog-9481975.post-21243136634420615832007-06-05T01:22:00.000-04:002007-06-05T01:22:00.000-04:00Try trial-error...Try trial-error...Yohttps://www.blogger.com/profile/10626571288338428652noreply@blogger.com