Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

45 Excellent

About Techie007

  • Rank
    Computer Technician

Contact Methods

  • Website URL

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

1,852 profile views
  1. You need the \Microsoft\Windows\TextServicesFramework\MsCtfMonitor task to be running for the keyboard to work in most Metro crapps.
  2. Whoa, now we're talking! You're right, the whole thing is literally a batch file that's extracted from the EXE.
  3. It is basically the combined number of "Likes" on all your posts. I've just bumped your reputation up to six by liking your post above. The more, the merrier!
  4. That's nothing new. I've had Windows Defender/SmartScreen attack Classic Shell, IrfanView and Mozilla Firefox in the past, totally blocking installation (and for Firefox, the download as well). At least they were blocked and not removed. But it was very difficult for even a person as knowledgeable as myself to get past. I actually had to copy the installer over from another machine in the case of Firefox. Thankfully it hasn't happened since, but it makes me wary of what Microsoft is capable of. This is nothing like Norton, where with a quick right-click of its tray icon, I can suspend "p
  5. Interesting—guess I'm not the only one then. I have two laptops (a nice modern one, and an old Vista one) running Windows 10. Neither have received the upgrade yet. I'm holding out on manually upgrading because I want to see how well the automatic upgrade process goes. My modern desktop PC which was upgraded from Windows 8.1 and entered into the Insider Program at the beginning of July refused to get any Insider builds or the RS1 upgrade. A week after upgrading to Windows 10, I gave up waiting and manually upgraded it to the latest Insider Preview ISO. Still it wouldn't download later bu
  6. Haven't been paying that much attention, but I do notice that Windows 10 RS1 (1607 "Anniversary Update") now hits http://msftconnecttest.com/connecttest.txt instead of http://msncsi.com/ncsi.txt to test for Internet connectivity. Windows has used NCSI since Vista days to test for Internet connectivity. I wonder how many captive portals that change broke. Why change something that was well established and was working fine?
  7. Them rumor mills these days! It ain't gonna happen.
  8. Well that explains everything. No wonder Microsoft can't get the design right—the people influencing all the votes are hardly using their computers at all! I wonder how many of these "Insiders" hopped on only for the ride and free copy of Windows 10. Looking at Dona's (and Gabe's) Twitter feed, I see so many build junkies. I'd much rather wait for serious, tangible improvements to Windows, and help guide the process along with a number of truly dedicated users such as are here in this thread. Then gimme a build when you really have something new to show.
  9. No, not right away. It will enter guilt trip mode for a time before it is removed. No way (especially on those opted out with OptOut10). Hadn't thought of that. Currently, it doesn't look like it (it just says that the free upgrade offer has expired), but who knows in the next couple days. Don't give them any ideas! Nope, though I have the feeling there may still be ways to slip some in for free. There. I just made a few predictions. Now let's see what actually happens!
  10. I'm pretty sure it won't. First of all, the upgrade offer is good all day tomorrow on the user's local timezone. So the free upgrade offer actually ends as the calendar strikes July 30. At that time, GWX will switch to guilt trip mode. Given that it keeps popping up every couple of days now with the countdown, I won't be the slightest surprised if it automatically pops up again (at least once), only with the following message this time: At some point though, GWX will be retired by another Windows Update that will come though and remove it. Probably sometime in August. It wi
  11. Boy, that will sure teach them! Wait. . . you've gotta be kidding me! A mere $165,000? For a giant like Microsoft, that's just a cost of doing business. If forced to, they'll pay, and then it will be back to "business as usual". I'd be more interested to know exactly what the French researchers found being transmitted by Windows 10.
  12. Same for me. And then with Windows 7, when Microsoft removed the Classic style Start Menu, I went looking for, found, and started using Classic Shell. It was just icing on the cake that it works in Windows 8 and Windows 10 too. Funny how so many remember Classic Shell as the great Start Menu for Windows 8, when it was originally designed to replace Windows 7's downgrade! The feature I missed the most is the ability to cascade folders/folder shortcuts from the Start Menu. The fact that we can still cascade them from the Taskbar (where I resent the loss of space), indicates that the code is
  13. Correct, 31 wasn't a typo. As I explained in my previous post, the 32nd bit is the sign-bit (minus sign) when using a signed variable to store the memory pointer. A signed Dword can express numbers from -2,147,483,648 to 2,147,483,647 (2 GiB), while an unsigned Dword can express numbers from 0 to 4,294,967,295 (4 GiB). Memory pointers are supposed to be stored in unsigned variables, but older programs were not always written or compiled correctly because 32-bit Windows never even supported LAA (the use of the full 32-bits) per-process. For instance, Visual Basic 6 doesn't even have support
  14. Large Address Aware doesn't make 32-bit programs run 64-bit. Another simple program that can do this tweak is NTCore's 4GB Patch. Unless a 32-bit EXE has the LAA flag set, Windows will run it as 31-bit by default, limiting it to 2GiB of RAM. This was fine in 32-bit Windows because you'd never want a single process to use that much RAM anyway. But when 64-bit Windows came out, Microsoft raised that limit to include the full 32-bits. The problem is, some older programs are compiled using signed Dwords to store memory pointers. With a signed Dword, any address over 2GiB will appear negative
  15. Of course the average user wouldn't know to do this, but in such a situation, I would schedule the update for as late in the future as possible, and click [Confirm time and close]. Then I'd immediately run my OptOut10 program to cancel the reservation, clear the scheduled update, disable GWX and such upgrades in the future, followed by a reboot to ensure that the new settings take full effect. As of now, I am still not aware of an anti-10 solution that is as effective at bringing a system back from the brink after the upgrade is reserved.
  • Create New...