« A Quest: Tracking down an Exchange problem | Main | California Ballot Analysis - June 8, 2010 »

May 05, 2010

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8357ac57769e2013480838634970c

Listed below are links to weblogs that reference Powershell surprise in Windows 7:

Comments

Account Deleted

I can't believe I'm reading this! I spent ALL last night, 11:30pm to 4:00am, unable to set script permissions for my first time using Windows Powershell! It is a wonderful addition to the .NET Framework (well I guess it is, the MS Windows 7 documentation seems to think so).

But I had the same dilemma as you, and could NOT figure out what to do: Which of the four choices should I use with my 64-bit non-prof'l Win7 OS:
Powershell plain,
Powershell x86,
Powershell ISE plain or
Powershell ISE x86?

Seemed like the non-x86 version is correct for 64-bit. But when I tried to run my own simple unsigned script, I could NOT convince Powershell to change my user Execution Policy from Restricted to Remote Signed!

I tried relogging as Admin, rewriting and running the script in Powershell x86, but Win7 chose that moment to hang. Now I really like Win7, but sadly, it abends rather frequently.

But things were bad now: all Aero light from my brand new 18.4" laptop screen with the nVidia 360M graphics card was completely extinguished. Dark. Couldn't invoke Task Manager and no choice other than power off to shut down, twice! Finally got Safe Mode prompts, messed around trying to do diagnostics, nothing would work, so I looked for a recovery point, system hung again. Last straw: restart and I don't even get a VGA 640x480 display with Safe Mode this time. Instead: operating system can not be found. Couldn't even do a screen capture. I was gazing at a white line cursor a thick non-integrated graphics, VT220 style line on a black background. I pulled out the battery, returned 10 hrs later, and now all is well. I'm running with no problem, nor with Powershell.

Thanks so much for your post about the Powershell Surprise. I'll try your approach after dinner.

windows 7 backup

To Ellie K:

In your case Powershell x86 is better.

Thomas Shaw

Doe it enable you to access other data stores, such as the registry and the digital signature certificate stores, as easily as you access the file system?
MIIIFS

cisco ccna training

It came in surprise! But sad to say, I don't have any idea on how and what to use them so I deleted them. That's another surprise! Lol!

Ute Tray

There's a new windows that will blow your mind. It's windows 8! You can use it to make things easier for you!

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

ABOUT STEVE

  • Steve Friedl is a software and network security consultant in Southern California. He has been a C and UNIX developer since 1981 and has an exceptionally broad background in this area. Some areas of expertise include:

    • C and C++ systems software development on the UNIX and Win32 platforms
    • Communications, including serial and TCP/IP based controllers
    • Enterprise internet security administration and configuration
    • Penetration tests, audits, and network reviews
    • Security forensics, reverse engineering, and tools development
    • General UNIX and Windows system/network administration
    • The Windows Printing System
    • Database software development
    • Technology problem solving and research
    • Technical writing and standup training

Unix Wiz

Stephen J. FriedlSoftware ConsultantOrange County, CA USASteve@unixwiz.net