bphlpt

Seems you have been "demoted" to merely a Sponsor. Cheers and Regards

Well, yeah. There might be a good reason that was hidden in the wizard. When most folks disable/remove SFC in nLite they don't plan on using it. Of course files will be missing if you try to re-enable it later. This is often true regarding any feature that you remove through nLite. Many features cannot be added back in later without practically starting over. Which is what folks have been advising you to do as well, though I understand your reluctance to do so. Keep in mind that you still might find more missing stuff later, such as a registry entry or something. Just sayin' Cheers and Regards

Do you have a valid Donation key? Have you put it where it needs to go? Cheers and Regards

@whocares, What you, I, Kel, or anyone else believe about the legality of using any particular piece of software, (or music or video for that matter), is totally irrelevant. What each of us chooses to use on our own machines in the "privacy" and "anonymity" (if such a thing truly exists these days) of our own homes is up to us and is no one else's business. Period. I'm sure Kel would agree with that as well. BUT ... In public, such as on this forum, we feel very strongly about abiding by the rules of wherever we are, and those rules are different depending on where you are. For example, I would assume your behavior in your bedroom with your beloved, or at a football game, or at the local bar, is probably different than when you are at church, unless you go to a very interesting church. The same people behaving differently at different places does not make those people "bad" people or hypocrites, it just means they are following the rules of where they are. Different forums have different rules. Here at MSFN, discussing warez of any kind, or helping anyone resolve problems that concern or are caused by warez, or even if it is proven that warez is in the picture in any way though not directly involved with the issue at hand, is not allowed. This also includes the use of "activators" of any kind to avoid the official activation methods for any software. And it includes the distribution of any software except though officially approved channels. So no sharing a torrent link to a release of any version of MS Windows, even if the MD5 matches the one from Technet and no keys are shared. Hiren's is a problem because of the included MiniXP as you surmised. Yes we know it is referenced in many places, but we don't allow it here. The use of any software in any way that is specifically forbidden in its EULA or terms of use, such as the use of nLite in a business application, non-profit or not, for example, is also not supported. We know all these rules are very strict and some may disagree with them since "everybody else does it", or whatever. Sorry, but those are the rules, and every member that signs up here agrees to them when they sign up. They are not up for debate or discussion. Anyone who disagrees and wants to pursue those kinds of topics is politely asked to do it elsewhere. Those that continue to discuss it here anyway are banned. There are other forums that have different rules, but you'll have to find those other forums on your own. Problems and installation challenges of a mix of products on a variety of hardware are of interest to many here, and the solutions found can be of benefit to others. If you can pose your questions so that the "forbidden" topics are not mentioned then the discussion can continue. If any problem is specifically caused by the use of some "forbidden" software or one obtained through unapproved channels, then you are on your own to find the solution. We will usually ask about the software involved, and if you disclose that it is one of "those", or if you refuse to say, then be aware that often we will simply tell you to get an officially released copy, try that, and then come back if you still have a problem. Frustrating I know if you truly believe that the particular piece of software is not the issue, but there you are. Personally, I think that the issues you are discussing in this thread and in http://www.msfn.org/board/topic/171435-allow-lowercase-on-multiboot-dvd/, are interesting and I would love to see the solution that you find that solves all the problems you ran into, if you can do it without mentioning any of the "forbidden" topics, of course. Cheers and Regards

https://www.schneier.com/blog/archives/2014/02/somberknave_nsa.html http://leaksource.files.wordpress.com/2013/12/nsa-ant-somberknave.jpg So doesn't appear to be anything new. Cheers and Regards

Yeah. That's pretty much how MS/BG worked back in the day. Cheers and Regards

You still have not answered most of our questions. Cheers and Regards

Probably not, but it looks like MetroMix will no longer be neeeded. Cheers and Regards

Thanks. So there is still value to running both, and they still "play nice" together? If so, it might be helpful to some to give some suggested settings to best take advantage of the features of both. But that's just my opinion. Cheers and Regards

Hey, at least you confirmed that the firewall did its job, even if it wasn't what you expected. And I suppose there is a setting you can adjust so that COMODO allows the requested activity. Cheers and Regards

Out of curiosity, are you aware of anything that StartIsBack can do that Classic Shell cannot besides "Search network shares added to Libraries"? I had always believed that there were advantages to having both apps installed, and I think that used to be true, but if StartIsBack doesn't add any capabilities then I'm starting to wonder if that is still true. Cheers and Regards

You can also see if you have any older, no longer needed drivers hanging around that you can remove. Cheers and Regards

I would be happy (so many years in the field and I had always thought that you cannot have an edit and save option for a read only file ) Only thing I can think of is default behavior is read only, but you have the option to open it in edit mode? ie as a default it opens as a viewer, but you can also open it in the editor. But that's just a guess. Cheers and Regards

Hey Kel, Did you happen to check if my suggested code replacement caused the same errors? myselfidem said it worked, but apparently he decided not to use it for some reason. [NOTE: I think this is the same segment. I haven't looked too closely, but I'm sure you can see what I intended anyway. Mainly I got rid of the while and the break statements.] Cheers and Regards

For best response, please post your question in the WinToolkit subforum over at WinCert. Cheers and Regards

Sorry. You're right of course. I've got a heck of an ear infection and am on all kinds of pain meds is my only excuse. Thanks for straightening me out. Cheers and Regards

You can look here - http://www.ryanvm.net/forum/viewtopic.php?t=9162 But a better definition is that it describes how to enable hotfixes that should be able to be installed on XP64, but were artificially blocked to only allow installation on Win2K3 for whatever reason, even though XP64 and Win2K3 share the same code base. Cheers and Regards

Welcome to MSFN! Cheers and Regards

I think many people just don't trust free software. If they charge money for it, it must be worth it, right? Of course if they read this thread then fewer folks would trust MS. Cheers and Regards

See here - http://ss64.com/nt/syntax-variables.html - for standard Windows Environment Variables definitions. Cheers and Regards

And let's not forget the Cuyahoga River, at one time one of the most polluted rivers in the United States famous for being "the river that caught fire", resulting in the Clean Water Act and the creation of the federal Environmental Protection Agency (EPA). When I lived in Cleveland, it was a joke that the river was so polluted that - "Walking on water is no big deal, anybody can do it." Cheers and Regards

Welcome to MSFN! Cheers and Regards

Welcome to MSFN! Cheers and Regards

The "big deal" is that Jody, and others, believe that using an OS that is no longer officially "supported" is not as secure and therefore puts them more at risk to viruses, hacker's attacks and other malware, and they want their computing environment to be as safe and secure as possible. That is a perfectly valid desire and they are correct in their belief. But I, and others, believe that the amount of additional risk they will be subjected to is so minimal as to not be a factor for the average user, provided that the OS and other software they run meet their needs with the hardware they use, the other software is kept up-to-date, and they protect themselves with a good router with a hardware firewall, use an up-to-date software firewall, anti-virus and anti-malware, and most importantly pay attention and be a smart computer user and don't do anything stupid, since the biggest weakness in computer security is always the user. As the users of Win9X and Win2K will attest, the daily use of "unsupported" OS will get more difficult as time goes on, but in general it is more likely to be because of harder to find drivers for newer hardware, changing web standards making older browsers not fully functional on newer web pages, or evolving media standards making it harder to play newer media smoothly, than because of security issues. I don't at all mean to say that security issues are not important, especially these days, but following the above advice should minimize the impact for the average XP user for quite awhile. Cheers and Regards

@TrevMUN, since, to my knowledge, there are no "DDR4 drivers" for any version of Windows today, I don't know how we can guess what those "drivers" will be like when the motherboards eventually arrive that need them. But as was implied above, I really don't think you will see specific "DDR4 drivers" at all, but rather you will see chipset drivers that happen to support DDR4. ie I can't remember ever seeing standalone DDR2 or DDR3 drivers, but I could be wrong. And I don't see the mainstream motherboard or chipset mfgs producing a chipset driver that supports XP64, unfortunately. Whether one could be modified to support XP64 like BlackWingCat has done for some drivers for Win2K also remains to be seen. Cheers and Regards