Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



NoelC

Member
  • Content count

    5,054
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    235

NoelC last won the day on October 4

NoelC had the most liked content!

Community Reputation

1,371 Excellent

3 Followers

About NoelC

  • Rank
    Software Engineer

Profile Information

  • OS
    Windows 8.1 x64
  • Country
  1. Windows 10 - Deeper Impressions

    Why bother if it's going to "match" the one that's already native to that device? Microsoft thinks that they can just follow what people have already done, with nothing innovative or different whatsoever, and because it's them they'll be wildly successful? -Noel
  2. Official - Windows 10 Worst Crap Ever!

    LOL, I finally got my Win 10 test system to update, and courtesy the newest VMware Workstation release I can go back to full-screen immersion on all 3 monitors. My plan was to give v1703 a real workout, once I got the latest update, using it as my primary system for a few days just as I do my Win 8.1 host system. Now a new problem has arisen... I absolutely can't make it see the shares on my Win 7 server system. It just won't connect. I have put much effort into it, and I know a thing or two about Windows networking. Apparently Win 10 and Win 7 just aren't speaking the same language. The Win 7 system can see the Win 10 shares. The Win 10 system can see the Win 8.1 shares. But the Win 10 system can't see the Win 7 shares. My server is named SVN. All my systems have been able to see \\SVN\C for example (a share of drive C, where administrators have full permissions). All systems use the same username/password, and that user is a member of Administrators on all systems. It's very well integrated - when it works. The Win 10 system can't see shares on \\SVN at all. Instead it requires me to enter \\SVN.carboni.lan (my local domain) to be able to sense there's a computer out there at all, and it incessantly asks for a username and password. When is a local account not the same as what a local account used to be? The crap intensifies. -Noel
  3. Why Windows builds are so different

    Most executable code gets dates built into it (if nothing else, into the security signature tacked onto the end). If an .exe or .dll file has 10 megabytes in it and time it was built causes it to be considered different, it's not all 10 megabytes that are different, yet I'd imagine most tools would consider the whole thing needing to be updated. You bring up a good point, though... Being able to generate EXACTLY the same image used to be considered a good thing, once upon a time in software engineering. Now everyone pretty much extends a leap of faith that their compilations, which may differ a little from build to build, work consistently. -Noel
  4. Official - Windows 10 Worst Crap Ever!

    I don't think it was really all that "right",,, There are things I can name that are better in other versions. It's just that Windows 8 had a fundamental UI flaw and WIndows 10 is so "wrong" that nobody wants it on its own merits. One of the prime reasons for getting Windows 10 runs along the lines of "my computer died and the new one came with Win 10". Only a few of us geeks have felt the good in Darth Win8er and managed to turn it back to the good side of the force. People generally don't want to have to be degreed in computer science and work that hard to make their OS acceptable for use. -Noel
  5. Official - Windows 10 Worst Crap Ever!

    They've been "dumbing down" windows - whether for touch use or just because the poor dear users get cognitive overload if there are more than 5 things on the screen - since way back. Many of us reconfigured those things to maximize working area and minimize fluff. The difference is that now the configurable parts for geeks / power users have just been made unavailable. They've lately focused on making it important that UI elements can move themselves around depending on what kind of screen you have (tiny phone screen in portrait orientation to massive multi-4K monitor setups). They forgot to consider that you just can't do the same things on both of those systems. LOL, I am looking over my big Photoshop workspace - 14 panels, each of which has tabs, plastered across 3 monitors - and imagining that if that were all shrunk down to, say, a 480 x 750 pixel desktop on a tablet App, what would actually be possible... -Noel
  6. Official - Windows 10 Worst Crap Ever!

    I'd say it means you're not trying to actually do anything useful with those systems. I think that's the only way Windows 10 continues to hang together - when it's only tasked with updating itself. -Noel
  7. Is ReFS ready for prime-time?

    It's like they got it most of the way there then just abandoned polishing the edges so it could be used mainstream. For what it's worth I've never had a lick of trouble with it. I ended up using ReFS for years on both external and internal data drives. One of them is chronically full, and it seemed to me it didn't get as bogged-down as NTFS does when you run a drive nearly full, but honestly I've not done any objective testing to give that feeling any credence. -Noel
  8. Aero Glass for Win8.1+ 1.4.6

    I'm also running Aero Glass on Win 8.1. Ribbon-enabled windows, such as Explorer and WordPad, use an entirely different method to paint the title bar, and thus are not handled by the normal DWMGlass.dll. Big Muscle released some additional components that work with Aero Glass and allow you to resurrect the glow, but there are some downsides. This is from my all too frail memory, but I believe UxThemeSignatureBypass64.dll and UxThemeSignatureBypass32.dll circa March 8, 2015, invoked via the AppInit_DLLs key will color the titles of ribbon-enabled windows. Here's what I see (note that my text is set to be white and the "glow" backing in my theme atlas is actually dark): As you can see in the Beyond Compare Options dialog at the upper-right, it essentially causes any text that uses the same API calls the ribbon-enabled windows use to be painted with the "glow" backing. It's a minor inconvenience I can live with to have the more integrated title bars. It's been a long time since I set this up, but I see I left myself an "InstallSignatureBypass.reg" file... This is what's in it: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows] "AppInit_DLLs"="C:\\AeroGlass\\UxThemeSignatureBypass64.dll" "LoadAppInit_DLLs"=dword:00000001 "RequireSignedAppInit_DLLs"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows] "AppInit_DLLs"="C:\\AeroGlass\\UxThemeSignatureBypass32.dll" "LoadAppInit_DLLs"=dword:00000001 "RequireSignedAppInit_DLLs"=dword:00000000 Note also that I stayed with Aero Glass 1.4.5, not the latest, as I saw some visual glitches with 1.4.6. The above is 100% stable for me. I get long uptimes between Windows updates that mandate reboots. -Noel
  9. Windows 10 Regressions

    You can stop unattended Windows Update by stopping and disabling the Windows Update service. There are also some scheduled tasks that seek to re-enable it, and those tasks get re-enabled by an actual Windows Update, so you have to be vigilant. I run a nightly script that logs half a megabyte of data showing the system state so that I can compare with prior runs and see if anything has been changed. In my case I also reconfigure my (3rd party) firewall so that the system can't possibly reach the update servers unless I reconfigure it to do so. It's a good thing I do that because I caught an application install (TurboTax of all things) once re-enabling and starting Windows Update even though I had it disabled. But rest assured it's possible to stop it from doing what it wants. You're still in control, though you have to get geeky to get there and stay there. -Noel
  10. Windows 10 Regressions

    At this point I don't know the detail of what's sending it into these conditions, and it miffs me that I can find no log or error message that describes what went wrong. It may be there, but to be honest I've grown weary of trying to make Windows 10 work right (and by right I mean with the configuration and disabled parts I want). Every new version that comes out I decide I don't want it on my actual hardware, so I think for now I'll just ignore this and continue to run .520 or whatever it is stuck at for testing and whatnot. They have a few more years to make it attractive enough to adopt in place of my Win 8.1 setup, which still works quite well. -Noel
  11. Windows 10 Regressions

    Turns out that's tied to the SuperFetch service, which is supposed to self-disable (and often even does) on SSD-equipped systems. New regression I've discovered: The latest cumulative Windows Update won't install on my test VM. It gets to 98% then reports: I cannot find a reason listed in any log file, at least not one readable by someone who can get pretty geeky as needed. -Noel
  12. Details can matter... Did you get the exact folder name right? Did you match your machine code character for character with the one you submitted? Are you running released code? -Noel
  13. Official - Windows 10 Worst Crap Ever!

    Hard to imagine "much better" when Aero Glass on Win 8.1 works fine and lasts a long time, but I too would be interested in hearing about others who've solved the problem of bringing back style to Win 8.1 desktops... -Noel
  14. Official - Windows 10 Worst Crap Ever!

    Yes indeed, ~28 processes. Well done. Functional and with minimal fluffery. Remember XP? You could get it in the high teens. I don't even remember how many I had tweaked NT 4 down to or the versions before that. God I've been tweaking Windows a long time. First version I remember fooling with was on a PC XT. -Noel
  15. I only have Workstation 11, with an overlaid VMware Tools package from a newer version. I'm waiting until whatever they release this Fall to see whether I want to upgrade. I'm guessing it'll be version 14? -Noel
×