Defrag: Return of Gov, Removing Network Drives, Security Essentials 4

Play Defrag: Return of Gov, Removing Network Drives, Security Essentials 4

The Discussion

  • User profile image

    Physical memory not available above the 4gig limit because it's not addressable?


  • User profile image

    Wow, never knew about the problem step recorder.  Cool show, thanks guys.

  • User profile image

    It's only until recently that I discovered Defrag; wondering how I could miss this. From any episode I can learn something new. And I love (should I say "hate") that other have the same problems that I do Perplexed

    In many of the solutions presented procmon is used as the source to find the cure. May I ask for a Defrag special about how to effectively use this tool and maybe some other from the Sysintenals suite. IMHO that would be great!


  • User profile image

    @StefanM: Larry and I are working on a new series that will delve (really) deep in to each of the troubleshooting tools we use in Microsoft Support - a lot of the tools will be Sysinternals tools. Stay tuned.

  • User profile image

    One thing I liked about mesh was the ability to sync arbitrary folders. Skydrive needs everything to be rooted in the special skydrive folder. I already had all my music in a different folder and didn't want to move it so I just the sysinternals Junction.exe tool to make a symlink from the skydrive "music" folder to where it actually lives. Works perfectly.


  • User profile image
    David G

    Just curious if there are any key differences between the new Skydrive app and LiveMesh.

  • User profile image

    Also, to not even lift your hand from the keyboard for the UAC window,

    Alt + C


  • User profile image

    @evildictaitor: I think Gov omitted Address Windowing Extensions (AWE) because it requires that the application be coded to use it (SQL Server being the major example of an application that does support AWE).

    x86 applications by default can use 2Gb, and with /3Gb and IMAGE_FILE_LARGE_ADDRESS_AWARE can use 3Gb (on x64 they can use 4Gb). With AWE, they can map more memory, but at any one time, can only have <3Gb mapped.

    As far as physical memory goes (and as Gov said), some RAM is never going to be available if it located at an address that is also hardware mapped - as it simply isn't addressable.

  • User profile image

    [12:15] - Can memory above 32bit limit be used for anything.


    google for PAE Patch. evildictaitor posted what PAE is. I've used it for a while and for 4GB RAM the patch is a good way to use all RAM, becasue the 64Bit OS uses over 500MB more than a 32Bit Windows so you have no benefit. But only try it if you DON'T use an Intel GPU. Their buggy drivers don't work.

    [16:45] - Pick of the Week: Windows Security Essentials 4 released

    it is now a bit better and no longer freezes the Explroer all the time, but it destroys the boot prefetcher of Windows (ReadyBoot) all the time and slows down boot extremely.

  • User profile image

    It's also possible to use something like SuperSpeed's ram disk drivers to create a ram disk up to 4 GB (I believe) and have it use unaddressable memory (those above 4 GB limit, as well as the unusable memory between 3.2 and 4 GB).  (Use at your own risk, I've never used the software, only read about it.)

  • User profile image

    @Algorithum: please give an example of how to use this shortcut?

Add Your 2 Cents