Posts Tagged ‘driver’

Block.Drift: Ken Block Gymkhana II – The Informercial

June 8th, 2009 No comments

If you’re into cars and don’t know who Ken Block is then you’re just not into cars. If your not into cars, then you probably want to learn what drifting is because let me tell you, Ken can Drift. (what kind of an intro is that aye?)

I posted his ‘Gymkhana Practice’ video a little while ago and this is a followup to that.

If you thought the first was a blast, your in for a treat. Don’t want to ruin it. Just strap yourself in, turn up the volume and be ready for a wild ride.

(Highly recommended you checkout the HD version)

Makes me wish I had my WRX STi back again (the Liberty‘s great if you want drive from A->B), though the days of attempting drifts around Essendon DFO carpark are long gone now – with an old mid-80s Celica which was RWD, before that a friends ancient Datsun 200B Sedan, oh the memories!

See more on the DCShoes website.

{lang: 'en-GB'}

Engineering Windows 7: Just a few more changes from Beta to RC

March 14th, 2009 No comments

In addition to the changes made from the Windows 7 Beta release to the soon-to-be-released Release Candidate, a fresh new list of changes were posted today.

Asside from the visual tweaking going on, some important system level changes have taken place:

23. Partition size reduction

In Windows Vista, configuring features such as Windows Recovery Environment and Bit Locker required significant customer interaction.  Also, a significant amount of drive space was reserved. The Windows 7 System partition enables features to be configured to work “out of the box” so very little customer interaction is needed to configure and utilize them.  Based on feedback and telemetry data received through the beta, it became clear that we could cut the drive size in half (from 200M to 100M).

24. Reserved System Partition naming

The system partition is created automatically by Setup when installing on a machine with no existing partitions.  During the Beta the existence of this partition on default installs confused many people and feedback indicated that a label telling them that this is space reserved for the system would be helpful when browsing disk configurations, and further help prevent it’s accidental deletion by enthusiasts. We will now label is “System Reserved”.

25. Dual Boot partition drive letter assignment

For a dual boot configuration for the Beta, the other Windows OS wouldn’t get a drive letter and therefore wouldn’t show up in explorer.  We heard overwhelmingly from Beta customers that the lack of a drive letter was confusing and even caused some to believe that their secondary OS was lost. Assigning the drive letter makes it visible in explorer and aids in navigation across OS installations.

26. Pagefile reduction

Through extensive use of Beta telemetry data, we have determined we can slim down the Windows disk footprint further by reducing the default page file size to be 100% of the available main memory.  It used to be “Memory + 300MB” so on a 1GB RAM system there was an extra third allocated that is no longer required.  The pagefile on some occasions will increase in size if required, but we just pre-allocate less.

27. Improved driver support

Based on telemetry data received from the beta, we identified networking drivers that were not available inbox.  We worked with ecosystem partners to achieve increased inbox driver coverage across wireless and wired with significant coverage for some of the new ATOM-based laptops

Interesting changes to the pagefile pre-alloc reduction.

The release candidate is going to be bootilicious 🙂

{lang: 'en-GB'}

Youtubing: Ken Block Gymkhana Practice (MY06 Subaru WRX STi)

November 18th, 2008 3 comments

Now thats what I call skills, Gymkhana encapusulates everything to show your true skills in handling a car – in this case a MY06 Subaru WRX STi. Damn I miss my MY03 STi 🙁 – not that I could pull _any_ of those styles of driving (except maybe a half-assed powerslide).

{lang: 'en-GB'}

TIP: Quick tip on how to Debug ASP.NET Web Application Deployed in IIS

September 8th, 2008 1 comment

Heres a real quick tip (+ info) on how to debug a ASP.NET Web Application/Site when running inside IIS itself. After the launch of Whidbey (Visual Studio 2005) we didn’t really need to have Internet Information Services (IIS) installed thanks partly to the bundled hosting engine (based on Cassini). But sometimes – just sometimes  🙄 – when you deploy your ASP.NET web apps to IIS you’ll find things break – like we just experienced – unlike running via the internal web-server.

To debug an already running IIS process – with the project loaded.

  1. Debug > Attach to Process
  2. Select either aspnet_wp.exe or w3wp.exe. (see note below)
  3. Enter a break-point somewhere in your code
  4. Visit the page/refresh.

Sometimes you may need to untick “Enable Just My Code (Managed Only)” in the Options > Debugging list.

Why the aspnet_wp.exe and w3wp.exe difference?

If the IIS server is running under IIS 5.0 Isolation Mode, then you need to attach to the ASP.NET Worker Process (aspnet_wp.exe) where as if your running under the Worker Process Isolation Mode (which is the default in IIS 6.0) you will need to attach to the w3wp.exe process.

From the TechNet Documentation:

Worker process isolation mode delivers all the benefits of IIS 6.0 new architecture: robust application pooling; automated restarts, scalability, debugging; and finely-tuned performance tuning. Web applications run with the Network Service identity, which provides a security advantage: the Network Service account has lower access privileges than LocalSystem.

In version 5.x of IIS the ASP.NET ISAPI Filter (aspnet_isapi) which is an unmanaged piece of code that runs within the inetinfo.exe process that offloads the work to the ASP.NET Worker Process (aspnet_wp) that trickles the workload down the rabbit hole.

However in IIS 6.x the process is a little different, specifically we have a kernel mode HTTP driver (http.sys) which ships apart of the Windows Networking subsystem. This acts as the gateway for the incoming requests for the web-server. It first parses the request and dispatches it to the IIS 6.0 Worker Process (w3wp.exe) which then loads the ASP.NET ISAPI (aspnet_isapi) and follows on down the rabbit hole.

Read the TechNet articles on more information about the HTTP Protocol Stack in IIS 6.0.

Just how far down does the rabbit hole go?

If your interested in learning more about the internals of the ASP.NET Worker Process and inparticular how ASP.NET works ‘under the hood’ you’re best to look at Rick Strahl‘s *excellent* article – A Low-Level look at teh ASP.NET Architecture which just got updated late last month (24th)!

{lang: 'en-GB'}