Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Discussions

earnshaw earnshaw Jack Sleeps
  • Those Annoying Disappearing Desktop Icons

    TSPDesigner launches when I in the start menu, type 'Troubleshooting'.   No cigar.  Also, your reply is too telegraphic to be of much use.  If you go to Control Panel and type in troubleshooting you can click Troubleshooting.  Under system and security there is run maintenance tasks.  This describes itself as "clean up unused files and short cuts."  Under "Advanced" you can uncheck "Apply repairs automatically, "  which is one time only and reverts back to "Automatically".  Also there is "Run as system administrator."  There is no "Disable this feature permanently" option.   There exists, possibly, a daemon (I know "service") that can be disabled, but I don't know its name.  Standard replies:  Nobody else has complained about this.  Those who have complained report they have a work around.  And we're working hard on Windows 8 and have no time for maintenance issues on Windows 7.

  • Those Annoying Disappearing Desktop Icons

    If you connect to your office LAN from your home office you probably have a VPN Client.  The VPN Client logs you into the office LAN with a password.  As part of its duty to prevent office data from leaking to the Internet, the VPN Client blocks access to your home office LAN.  The once-a-day desktop icon cleanup senses the inability of these desktop icons to reach their destinations, so it deletes them.  I then laboriously put them back.     My printer is reached through a link in the Active Directory.  So I cannot print whilst connected to the office LAN.   Naturally, all of this happens without so much as a "How do you do?"

  • Those Annoying Disappearing Desktop Icons

    Numerous people have reported the W7 "feature" that causes certain types of icons on the Windows Desktop to disappear over time.   It turns out there is a background service that periodically scans the computer for things it determines are deleterious to a computer that runs shipshape and in Bristol fashion.  Icons that represent shortcuts to a central server, especially a central server that is temporarily unreachable, are erased.   This is deemed proper by the powers that be.   How can that reasoning pass muster?   I have a folder that originates in my  account's user Desktop folder thatI keep for copying back to the actual Desktop each time I discover my handy-dandy shortcuts have gone missing.    Perhaps the policy that the "feature" implements deserves a review.

  • So Ya Wanna Run Hyper-V? -- Guess What Windows 2008 Server Has to Say About That!

    An error occurred while attempting to start the selected virtual machine(s).
    New Virtual Machine (in quotes) could not initialize.
    The virtual machine could not be started because the hypervisor is not running.
    New Virtual Machine (in quotes) could not initialize.  (Virtual machine ID blah-blah-blah)
    The virtual machine could not be started because the hypervisor is not running.
    The following actions may help you resolve the problem:

    1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.

    2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled
       in the BIOS of the physical computer.

       (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on.
       Resetting the physical computer is not sufficient.)

    3) If you have made changes to the Boot Configuration Data store, review these changes to ensure
       that the hypervisor is configured to launch automatically.

     

    In my case I had no way of knowing whether my expensive server contains hardware for hardware-assisted virtualization (supported version or NOT).  It isn't printed on the system unit case.  It isn't reported by any of Microsoft's tools.

     

    It turns out there is a BIOS setting that is DISABLED by default.  That means I must ENABLE it to run Hyper-V.  Presumably those computers that have it enabled take a performance hit.   But you won't find information on that.  

     

    The phrase "the hypervisor is not running" refers to what?   A hypervisor is an operating system that hosts operating systems.  If it isn't running, what do I gotta to do get it running?  And what do I care if it is running or not?   That's a problem for Hyper-V to deal with.  

     

    There is a note about BOOT.INI, which has transmogrified without notice into the Bootstrap Configuration Data store.  Apparently Hyper-V is dependent on one or more (we don't know which) settings inside the aforementioned store that is (are) responsible to launch the hypervisor automatically.

     

    In an ideal world, this aside from Hyper-V would include by reference documentation that is specifically written to help people who are new to Hyper-V to use Hyper-V.  Alas, there is no such reference.  Pity.

  • Burner Schmerner

    Suppose you have a read-only Blu-Ray optical disk drive.
    Suppose you put a BD-R blank optical disk in that drive.
    What does Windows 7 do?
    Answer.  It suggests that you drag files and folders to be burned into Windows Explorer.
    All goes swimmingly until you click the Burn link.
    Then the drive opens and a dialog box instructs:
    "Insert a disc."
    "Either the disc in the CD or DVD burner isn't a writable disc or it's full."
    "Please insert a writable disc into drive E:."
    Well, it happens that drive E: is NOT a burner, so the suggestion that that problem is with the medium is FALSE.
    Is it not possible for Windows 7 to detect whether an optical disk drive is capable of burning?
    Is it possible for Windows 7 NOT to mislead the end user?

    It isn't always obvious that the black thing with the button is or is not a burner.

  • Diagnostic Messages and Quality ​Documentati​on

    Two things need to be addressed in our industry.   1) Error messages need to be upgraded to diagnostic messages.  2) There need to be established minimum quality standards for documentation.   The industry standard today is that a program is conformant should it be evident that it  handles every inconvenient internal state with any message at all that conveys the notion that the user's request has been rejected.  There is no need for an error message to suggest what may have gone wrong.   This is no need for an error message to suggest how the end user may provide a remedy.   As to documentation, volume trumps quality.  Anybody who is hired to write a technical book is required to write at least 1,000 pages of often dense, barely comprehensible, barely cohesive, not necessarily germane material.  It need not cover obvious, vital, and necessary issues as long as it consumes at least 1,000 pages.   Got a question you think a book should answer?   Don't expect to find what you seek through the convenience of the Table of Contents or Index.   Nobody seems to know whether a given "document" is good or bad.  Nor care much.  Why is that?

  • Windows 7 At Your Service

    AndyC said:
    earnshaw said:
    *snip*

    "Also new in Windows 7, you can map a network share to a drive letter and Windows 7 will not reliably recognize it in the command shell.   NET USE works reliably to do the same thing."

     

    Elevated command prompts (and elevated processes in general) won't see drive mappings that were made un-elevated (and vice-versa). This is partially down to the mechanism used by Windows to perform elevation and partially down to the fact that relying on drive mappings being available in both contexts would cause a whole raft of compatibility issues when using over-the-shoulder elevation.

    I withdraw my "thousand pardons."   If you change the Start In directory in a shortcut on the desktop, it works as it should.   If you change the same thing in a shortcut on the Start Menu, the change you make is IGNORED.  This is a capital BUG.   I expect a fix for this will appear within a week on Update Tuesday.   By the way, what is an "Over-the-Shoulder" elevation?

  • Windows 7 At Your Service

    CannotResolveSymbol said:
    Sven Groot said:
    *snip*

    Same here.  I tried it on Windows 7 before I posted to make sure that it works.

    A thousand pardons.   I tried it AGAIN here and now it works.   After all, it SHOULD work.    

  • Windows 7 At Your Service

    W3bbo said:

    "So, what is the official received way to get the initial current working directory the way I want it in CMD.EXE?"

     

    cmd /k "cd %1"

     

     

    Excellent.  It works exactly the way I wanted it.  Thank you. 

  • Windows 7 At Your Service

    CannotResolveSymbol said:
    Sven Groot said:
    *snip*

    Or just set the "start in" directory of the shortcut you're using to open cmd.exe.

    Or just set the "start in" directory...

     

    That is the first thing I tried.   It doesn't work on Windows 7.

     

    Also new in Windows 7, you can map a network share to a drive letter and Windows 7 will not reliably recognize it in the command shell.   NET USE works reliably to do the same thing.