How to Install Windows Movie Maker 6.0 on Windows 7

If you'd gotten quite used to 'Windows Movie Maker' in Windows Vista, you'll probably notice right away after you start using Windows 7, that the new so-called 'Windows Live Movie Maker' is pretty crap!!! to put it mildly...

here's an excellent solution:
How to Install Windows Movie Maker 6.0 on Windows 7

Although as far as I could make out, this depends on you having access somehow, to the old 'Windows Movie Maker' files from a Vista machine.

10 Windows 7 commands every administrator should know

Reposted: http://www.techrepublic.com/blog/10things/10-windows-7-commands-every-administrator-should-know/

Upgrading Windows Vista sp2 to Windows 7...chronicle...

Finally took the plunge and upgraded my 22 month old win Vista sp2 machine to Windows 7:

Downloaded and installed Windows 7 upgrade advisor....and my PC passes all tests.
(Ran my anti-virus before hand, as advised, and then disabled it before beginning win7 setup)

It went something like this:

Inserted upgrade DVD and clicked on Setup.exe

After selecting the "Upgrade" option (as opposed to "Custom")...

5-point-menu displayed (Started at 12:30pm):

#1.Copying Windows files

#2.Gathering files, settings & programs.
machine does an auto restart after #2 after 30 mins (1pm)

#3.Expanding Windows files.

#4.Installing features & updates.
after a further 30mins, another auto restart (1:35pm)

#5.Transferring files, settings & programs. (install spends ages upon ages at "694374MB of 949330MB transferred"), then after 62% - 714027MB -(3.39pm) another auto restart.

949073 (72%) copied as of 4pm. ...and again, spends ages (30mins) at "949073MB of 949330MB  transferred "!

949330MB, finally done at 4:28pm. Another auto restart!

Resumed with request for vista product key:

Three choice menu
1. Install all latest updates (i.e. use recommended settings)
2. Install only important updates
3. Ask to Install updates later

(I choose option 2)

Date & time setting appears.

Network choices are next:
1.Home
2.Work
3.Public

(4:40pm) Windows 7 logon screen...yea!!! Yeehah!!! Woohoo!!! Yippeee!!!

The very 1st dialog I see after logging on is: "Setup has detected that the .Net framework version 4 needs to be repaired. Do not restart your computer until Setup is complete."

4:47pm, taskbar finally appears...mousing over the update icon shows "Windows is downloading updates"

4:58pm, yet another auto restart!
"Logging off..." screen is displayed for ages! (13 mins)
I finally give up and push reset button. Had to do this twice as 1st restart appeared to hang on black, blank screen (panic!!!)

Finally, (5:20pm, back at the Win7 desktop....Woohoo!!!)

Every thing seems to be working just fine, as before. So far I've hardly had to re-install any of my previous programs, applications, games, device drivers, etc., Swell!

Don't forget to click on 'Start Menu' -> right-click 'Computer' -> select 'Properties',
(alternatively goto Control Panel->System and Security->System), then under "Windows activation" entering your new product-key and then click to "Activate" your new copy of Windows 7.

Oh, and also don't forget to re-enable anti-virus.

For anyone having any doubts about upgrading...I say go for it. Hopefully your experience will be fairly painless as mine has been.

PS: I noticed hours later - I did need to re-install Windows Movie Maker (needs to be downloaded and is now part of package called Windows Live Essentials).

Also, strangely enough, I had IE9 installed previously, and this got rolled back to IE8 by the Win 7 install...quite odd!

The HTTP status codes in IIS 7.0 and in IIS 7.5

When you try to access content on a server that is running Internet Information Services (IIS) 7.0 by using HTTP, IIS 7.0 returns a numeric code that indicates the status of the response. The HTTP status code is recorded in the IIS log. Additionally, the HTTP status code may be displayed in the client browser.

The HTTP status code may indicate whether a request is successful or unsuccessful. The HTTP status code may also reveal the exact reason that a request is unsuccessful.

Log file locations
By default, IIS 7.0 puts log files in the following folder:
inetpub\logs\Logfiles

This folder contains separate directories for each World Wide Web site. By default, the log files are created in the directories daily, and the log files are named by using the date. For example, a log file may be named as follows:
exYYMMDD.log

The HTTP status codes
This section describes the HTTP status codes that IIS 7.0 uses.

Note: This Microsoft Knowledge Base entry (kb943891) does not list every possible HTTP status code as dictated in the HTTP specification. This article includes only the HTTP status codes that IIS 7.0 can send. For example, a custom Internet Server API (ISAPI) filter or a custom HTTP module can set its own HTTP status code.


1xx - Informational
These HTTP status codes indicate a provisional response. The client computer receives one or more 1xxresponses before the client computer receives a regular response.

IIS 7.0 uses the following informational HTTP status codes:
• 100 - Continue.
• 101 - Switching protocols.


2xx - Success
These HTTP status codes indicate that the server successfully accepted the request.

IIS 7.0 uses the following success HTTP status codes:
• 200 - OK. The client request has succeeded.
• 201 - Created.
• 202 - Accepted.
• 203 - Nonauthoritative information.
• 204 - No content.
• 205 - Reset content.
• 206 - Partial content.


3xx - Redirection
These HTTP status codes indicate that the client browser must take more action to fulfill the request. For example, the client browser may have to request a different page on the server. Or, the client browser may have to repeat the request by using a proxy server.

IIS 7.0 uses the following redirection HTTP status codes:
• 301 - Moved permanently.
• 302 - Object moved.
• 304 - Not modified.
• 307 - Temporary redirect.


4xx - Client error
These HTTP status codes indicate that an error occurred and that the client browser appears to be at fault. For example, the client browser may have requested a page that does not exist. Or, the client browser may not have provided valid authentication information.

IIS 7.0 uses the following client error HTTP status codes:
• 400 - Bad request. The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 400 error:
o 400.1 - Invalid Destination Header.
o 400.2 - Invalid Depth Header.
o 400.3 - Invalid If Header.
o 400.4 - Invalid Overwrite Header.
o 400.5 - Invalid Translate Header.
o 400.6 - Invalid Request Body.
o 400.7 - Invalid Content Length.
o 400.8 - Invalid Timeout.
o 400.9 - Invalid Lock Token.


• 401 - Access denied.

IIS 7.0 defines several HTTP status codes that indicate a more specific cause of a 401 error. The following specific HTTP status codes are displayed in the client browser but are not displayed in the IIS log:
o 401.1 - Logon failed.
o 401.2 - Logon failed due to server configuration.
o 401.3 - Unauthorized due to ACL on resource.
o 401.4 - Authorization failed by filter.
o 401.5 - Authorization failed by ISAPI/CGI application.


• 403 - Forbidden.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 403 error:
o 403.1 - Execute access forbidden.
o 403.2 - Read access forbidden.
o 403.3 - Write access forbidden.
o 403.4 - SSL required.
o 403.5 - SSL 128 required.
o 403.6 - IP address rejected.
o 403.7 - Client certificate required.
o 403.8 - Site access denied.
o 403.9 - Forbidden: Too many clients are trying to connect to the Web server.
o 403.10 - Forbidden: Web server is configured to deny Execute access.
o 403.11 - Forbidden: Password has been changed.
o 403.12 - Mapper denied access.
o 403.13 - Client certificate revoked.
o 403.14 - Directory listing denied.
o 403.15 - Forbidden: Client access licenses have exceeded limits on the Web server.
o 403.16 - Client certificate is untrusted or invalid.
o 403.17 - Client certificate has expired or is not yet valid.
o 403.18 - Cannot execute requested URL in the current application pool.
o 403.19 - Cannot execute CGI applications for the client in this application pool.
o 403.20 - Forbidden: Passport logon failed.
o 403.21 - Forbidden: Source access denied.
o 403.22 - Forbidden: Infinite depth is denied.
o 403.502 - Forbidden: Too many requests from the same client IP; Dynamic IP Restriction limit reached.


• 404 - Not found.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 404 error:
o 404.0 - Not found.
o 404.1 - Site Not Found.
o 404.2 - ISAPI or CGI restriction.
o 404.3 - MIME type restriction.
o 404.4 - No handler configured.
o 404.5 - Denied by request filtering configuration.
o 404.6 - Verb denied.
o 404.7 - File extension denied.
o 404.8 - Hidden namespace.
o 404.9 - File attribute hidden.
o 404.10 - Request header too long.
o 404.11 - Request contains double escape sequence.
o 404.12 - Request contains high-bit characters.
o 404.13 - Content length too large.
o 404.14 - Request URL too long.
o 404.15 - Query string too long.
o 404.16 - DAV request sent to the static file handler.
o 404.17 - Dynamic content mapped to the static file handler via a wildcard MIME mapping.
o 404.18 - Querystring sequence denied.
o 404.19 - Denied by filtering rule.
o 404.20 - Too Many URL Segments


• 405 - Method Not Allowed.
• 406 - Client browser does not accept the MIME type of the requested page.
• 408 - Request timed out.
• 412 - Precondition failed.


5xx - Server error
These HTTP status codes indicate that the server cannot complete the request because the server encounters an error.

IIS 7.0 uses the following server error HTTP status codes:
• 500 - Internal server error.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 500 error:
o 500.0 - Module or ISAPI error occurred.
o 500.11 - Application is shutting down on the Web server.
o 500.12 - Application is busy restarting on the Web server.
o 500.13 - Web server is too busy.
o 500.15 - Direct requests for Global.asax are not allowed.
o 500.19 - Configuration data is invalid.
o 500.21 - Module not recognized.
o 500.22 - An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
o 500.23 - An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
o 500.24 - An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
o 500.50 - A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
Note Here is where the distributed rules configuration is read for both inbound and outbound rules.
o 500.51 - A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
Note Here is where the global rules configuration is read.
o 500.52 - A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
o 500.53 - A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.
o 500.100 - Internal ASP error.


• 501 - Header values specify a configuration that is not implemented.
• 502 - Web server received an invalid response while acting as a gateway or proxy.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 502 error:
o 502.1 - CGI application timeout.
o 502.2 - Bad gateway.


• 503 - Service unavailable.

IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 503 error:
o 503.0 - Application pool unavailable.
o 503.2 - Concurrent request limit exceeded.

(http://support.microsoft.com/kb/943891)

"proj" cannot be opened because it's project type (.csproj) is not supported by this version of the application

If you are using VS2008 pro and get this error it could be you have some un-installed but required components. Re-run an installation while checking to make sure all required components are selected for install.

Also discovered quite by accident, that you'll get the same sort of error...

'C:\Users\Username\Documents\Visual Studio 2010\Projects\ProjectFolder\Projectname\Project.csproj cannot be opened because it's project type (.csproj) is not supported by this version of the application'

...if you are using Visual Basic 2010 Express and do something silly, like try to open a C# solution (.sln file) that was created and saved in Visual C# 2010 Express --- of course!!! The proj file would have been saved with a .csproj extension, and so the .sln file has a reference to a .csproj file.

The specified named connection is either not found in the configuration, not intended to be used with the EntityClient provider, or not valid.

You may run into this error when you attempt to reference and consume an Entity Data Model that has been created in a stand-alone project as a class library, from a new 'client' project such as a Windows Forms project, Windows Console App, or an ASP.Net project.

FIX:
The reason for the error is, after you add a reference in the consuming project to the Entity Data Model DLL, you mustn't forget to either:

a) create your own .config file in the consuming project and add the connectionstring entry of the Entity Data Model,
or
b) copy the App.config file from the Entity Data Model project, into the consuming project (by right-clicking the Project > Add Existing Item > Navigating to the Entity Data Model project and selecting its App.config file).

Also worth checking to make sure that the model's MetaData Artifact Processing property is set to 'Embed in Ouput Assembly' which effectively ensures all the required schema files are embedded into the compiled DLL as resources, and are also made a part of the connection string for the model. (In the Entity Data Model project, double-click to open the model and check it’s MetaData Artifact Processing property in the Properties window, by default this should already be set to ‘Embed in Output Assembly’).

Sequence in which events are raised for Pages, UserControls, etc...

...understanding the page life cycle...
during a debugging session, this information came in handy, but rather than re-create it all here, I figure it's best to just link to the original forum post here >> 

Reading embedded resources in .Net

I always forget the first important step; i.e. remember to mark the Build Action property of a resource to "Embedded resource"

Then use:

Assembly myAssembly = GettingExecutingAssembly();
Stream myStream = myAssembly.GetManifestResourceStream(name-and-path-string-to-embedded-resource);


Where name-and-path-string-to-embedded-resource is the full namespace string of the resource e.g. "myproject.images.image.png"

Error code 0x80070035 The network path was not found, or Windows cannot access (my PC)

Windows Error 0x80070035 while trying to connect to shared folders on a desktop PC from a laptop, both on a wireless network (and both running Vista). And yes, the folders were definitely shared on the desktop PC.

Zone Alarm installed and running on both machines in addition to Windows Firewall. And both machines also running AVG antivirus software.

I tried all the fixes I could think of, as well as every suggestion I could find online;

• checking via ipconfig/all for, and PINGing, ip address and machine name of each machine (PING from desktop to laptop would time out, but no problems PINGing desktop from the laptop)
• making sure all required services are running on both machines -  DNS Client, DHCP Client, Computer Browser, TCP/IP NetBIOS Helper, FDResPub, SSDP Discovery, etc, Automatic WLAN Configuration(Vista), Wireless Zero Configuration(XP), WLAN AutoConfig(Win7).
• making sure Windows Firewall exceptions are enabled for File and Printer Sharing, and Network Discovery
• making sure Network Discovery is turned on in Vista's "Network and Sharing Center"
• etc

FIX:

In this particular case, as it turns out, what was required was quite simply to stop the Zone Alarm instance running on the client machine (laptop), and the problem was resolved. Could now PING laptop from desktop command prompt, but more importantly, could now also access shared folders on desktop from the laptop!

I would assume it's possible to tinker with the settings/configurations within Zone Alarm on the client without having to turn it off altogether, but was happy for now to just turn it off so I could get on with other stuff.


Additional options:

Enable NetBIOS over TCP/IP on all computers:

1)   Go to “Control Panel\Network and Internet\Network Connections”.

2)   Right-Click on the connection and choose Properties.

3)   Click “Internet Protocol (TCP/IP) Version 4” in the list.

4)   Click Properties, and then click Advanced.

5)   On the Advanced TCP/IP settings windows, go to “WINS” tab.

6)   Under NetBIOS setting, click “Enable NetBIOS over TCP/IP”, and then click OK.

2.    On the Windows 7 and Windows Vista computers, please go to “Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings” and ensure that the following items are turned on:

Network Discovery

File and printer sharing

And this one is OFF:

Password protected sharing

social.technet.microsoft.com

The device closed remote access function, you are forbidden now.

If you get this error when you try to log into a (siemens gigaset se587) router's web admin interface, check that you are trying to log in to the LAN IP of the router and not the public IP:

e.g. 192.168.1.1/

notice there is no port number (for example :200) or any additional url string or url parameters after the backslash following the ip address.

You can verify your router's ip address by checking for the default gateway. From the command prompt (in Vista this is: Start Menu->All Programs->Accessories->Command Prompt), type in ipconfig /all. Part of the resulting 'Windows IP Configuration' listing should show what your Default Gateway is.