Jul 28

So the other day I realised that there was something very unusual happening to my HP 2540p – it has been blindingly fast, but just recently it seemed that it was on strike – I also found that it would effectively hang when trying to suspend.

So it seemed that this was around the Power Management side of things and I couldn’t find anything in the Event Viewer to isolate what was causing it – in the past I have found that this sort of issue can be sometimes caused by BIOS related issues – and while this does not explain why the symptom suddenly appeared, I can report that my original BIOS was F.02 and upgrading this to the latest version does seem to have resolved this.

This is certainly good news – as I was starting to think that I might need to rebuild to clear this (mind you that was going to be a good excuse to rebuild with the new SP1 :) )

HP Notebook System BIOS Update (ROM Family 68CSU)

image

  • Share/Bookmark

written by dcaddick

Apr 05

Some while back I was really wishing it was possible to boot to a USB Stick from within a VM – and now it is possible – great news because it just adds that little bit extra in the way of functionality

Great tip how-to boot from USB stick inside of VMware Workstation

A tip pointed by Ivo Beerens. By using my RSS Reader to stay updated on blogs in the Virtualization Sphere I checked this post from Ivo. It’s a great tip. What’s about?

Basically when you want to test ESXi 4 installation to the USB Stick (or this Video post too…) you’ll want to follow my post, which I’ve done in the past and that’s it.

But if you want to test unattended installation of ESXi 4 on USB stick then you would want to boot your VM which is executed in your VMware Workstation, from an USB stick too.Well you can’t. Even the version 7 of VMware Workstation does not support that.

Here comes the help tip from Ivo. Basically what do you have to do is a work around.

01. Download boot manager from PLoP
02. Use the Iso in the boot manager as a boot device to boot your VM
03. Add an USB adapter to your VM (if not already done).

add-usb-and-enable
03. Insert your USB stick with ESXi 4 installed in it.
03. When your VM boots from that ISO, just select USB from the menu.

Boot your VM in VMware Workstation from USB with plop boot manager

Well not all the credit goes to IVO, because the original help provided was from Ulli Hankeln from sanbarrow.com. -:)

Great tip how-to boot from USB stick inside of VMware Workstation

  • Share/Bookmark

written by dcaddick

Jan 16

***UPDATE***
If you would like to follow this – check the discussion at XDA Developers

I recently purchased an LG GM730f as a new mobile – specifically because I thought the form factor was quite good, it also used a microUSB as a connector AND it was being advertised as being able to be updated to WM 6.5 in the New Year. So I sent an email to LG Australia in the first week of Jan asking when they might be releasing it and I got a reply back at the start of the week saying it was ready.

So this is my experience and hopefully it will save you from wasting some time? And if someone from LG would like to contact me I’d be glad to get things resolved? :)

But it appears that in some cases that the Web Site doesn’t work accurately?

This was sent from LG after I discussed with them that the web page they first sent me to failed to work correctly:

Dear David Caddick,

Thank you for emailing LG Electronics Australia.

We apologise for the problem you have experience with trying to access our website, please try the following website address:

http://au.lgmobile.com/web/web.support.laf?q=201011412401

I hope this has been of some assistance.

So this should bring you to this location at http://au.lgmobile.com/web/web.support.retrieveSoftwareDownload.laf:

clip_image004

So by clicking on Download you should get this tool:

clip_image006

If you have already installed this it will be shown as a desktop Icon like this:

clip_image008

And when up and running it looks like this:

clip_image010

So I started clicking on the “Start Updating for Smartphone (Windows Mobile)” as this seemed to be the most appropriate place to start? J This then pops up with:

clip_image012clip_image014

Click on Next get you a reminder to save your data:

So at this point the phone changes to a black screen with:

                   !

Emergency Download

And on the computer you see:

clip_image016

So clearly at this point – even though ActiveSync was working fine before this there is some need/requirement for LG’s “process” to use a specific driver to communicate with the Phone when it is placed in “bootloader” mode? So at this point I clicked on OK, and then tried to install the USB Driver

clip_image018clip_image020clip_image022

So then at this stage you’d think you should be able to go back and check that the Modem Driver is installed:

clip_image024

And then I should now be able to Start the Update?

clip_image026clip_image028

But as you can see by the screenshot above this first checks comms with the mobile – and as a consequence it initiates another install sequence of the USB Modem Driver:

clip_image030

So now we are completely in a loop – I could remove the USB Modem Driver, but then regardless of whether it’s installed or not – the process ALLWAYS tries to install the Driver before starting the update.

I can cancel, but this doesn’t help in trying to get anywhere.

Why can’t LG just do this like all other WM Vendors?

  • Download a ROM update
  • Plug phone into PC
  • Start ActiveSync
  • Run ROM update executable

I have been using Windows Mobile devices since 2003 and this would have to be one of the *worst* Update mechanisms I have ever experienced

Anyway, if you keep at it long enough and manage to get it in to the “Bootloader” mode then you can try using “Start Updating” without the Smartphone side of things (I know, but by this stage I was willing to try anything?) and it does appear to get going

clip_image032

It also looks like It does download a 107Mb ROM image and that would be about consistent with my experience?

clip_image034

And then goes ahead and flashed the phone

clip_image036clip_image038clip_image040

clip_image042

So eventually this gets to 91% or better and the phone starts booting to WM 6.1….. <sigh>

So I have now tried this 6 times or so, from Windows 7 and XP Pro and even though the Web Site clearly indicates that there is a new Update available, and that’s what I was told from LG, it’s clear that they still need to do some work to get this out? I for one am sick and tired of reflashing my Mobile Phone only to find it *STILL* on WM 6.1…………..

If I hear any news I’ll update at the top of this post

  • Share/Bookmark

written by dcaddick

Oct 12

Just something worth mentioning that I have come across recently that might be of some help?

I was recently hunting down the exact reason for why a 2533 running RGS across WiFi was struggling to be able to deliver the video content and found that I had to do quite a bit of logging and then gathering the raw data in to an excel sheet to make sense of it all – in the process I ditched PerfMon – in part because it wasn’t working under XPe, but also because I feel its performance can’t be relied on when things are already going wrong, so I had started using TYPEPERF.EXE which is actually installed by default on everything from at least XP onwards.

Then on one of my initial builds of Windows 7 on my laptop I found that on resume it would occasionally appear quite sluggish and when digging deeper this appeared to be caused by 50% of the CPU being consumed by DPC’s (Deferred Procedure Calls). So after ascertaining that Typeperf wouldn’t cut it I started looking deeper for a tool that would help identify exactly what driver was causing this. clip_image002

So I then discovered this article Measuring DPC time that highlighted the latest tool being Xperf – the main difference is that this is not installed natively in the OS, so you’ll have to go and download it and install it.

The really neat part of this is that it comes with an XPerf viewer that allows you to intuitively drill through the results, highlight particular time slices, overlay multiple graphs, etc.

And as if this isn’t enough, it also allows you to download symbols on the fly exactly like the latest debugging tools so that you can drill in to find the offending file/driver, etc. There is also a similar tool that will allow you to do similar performance tracking at boot time, and from what I can see it is this set of tools that has assisted MS in getting on top of the performance issues from Vista to Windows 7. My understanding at this stage is that this *should* work to capture info in XP (failed for me so far…) 

XPerf:
Windows Performance Toolkit (WPT) – Download
Two Minute Drill: Introduction to XPerf
Using Xperf to take a Trace
Xperf support for XP

Typeperf:
Although it’s not installed/supported in XPe by default it is possible to run it direct from any drive (Temp, USB, etc. ) and collect data
See Two Minute Drill: TYPEPERF for more details

Example:
Check your Total CPU usage every second:
C:\>typeperf "\processor(_Total)\% Processor Time"
"(PDH-CSV 4.0)",\\2K8SRV\processor(_Total)\% Processor Time
"04/13/2009 09:50:04.359","2.509119"
"04/13/2009 09:50:05.360","0.754295"
"04/13/2009 09:50:06.360","2.899090"
"04/13/2009 09:50:07.360","1.534207"
"04/13/2009 09:50:08.360","0.559314"
"04/13/2009 09:50:09.360","10.113409"
"04/13/2009 09:50:10.360","10.113409"
"04/13/2009 09:50:11.360","3.094071"
"04/13/2009 09:50:12.360","0.559314"

I hope this is of some use? ;-)

  • Share/Bookmark

written by dcaddick

Sep 13

This arrived in my inbox at work courtesy of a colleague at work and it looked too useful not to share… I hope it’s useful?

Useful Sources

Windows Server 2008 R2

Core

For PowerShell, Cluster.exe & Scripting see that section.

Deployment, Migration & Upgrades

For deployment guides for a specific resource (Exchange, File Server, Hyper-V, Print, SQL, Other) or for deployment using PowerShell, Cluster.exe or scripting, please visit that section.

Exchange Server

File Server, DFS-R, DFS-N & NFS

Hyper-V

Miscellaneous

Multi-Site Clustering

Network Load Balancing

Other Resources & Workloads

For information about a specific resource (Exchange, File Server, Hyper-V, Print, SQL), please visit that section.

PowerShell, Cluster.exe & Scripting

Print Clustering

SQL Server

Utilities

  • Share/Bookmark

written by dcaddick

Sep 13

It seems that although I have been running various early releases of Windows 7 since around late January I have had no real problems at all – but just prior to being out of the office for an event I found a few issues:

  • VPN wasn’t working for some reason
  • I didn’t have the time to troubleshoot it
  • The event was Tech Ed 09 and as it was sort of like a soft Launch for Windows 7 I thought I’d do a final build with proper release code from MSDN

It seems that although the USB was working correctly through all the previous releases – it was this final release that tipped it over the edge and for some reason caused the USB subsystem to quite erratic and would only recognise very few devices.

And so the answer was to update the BIOS :)

I have not touched the BIOS since I got the device originally so it was still on F.0 – the latest currently available is F.14

When I went to install F.14 I was warned that I needed to upgrade to F.10 first…

Once this was installed ALL USB was working exactly as advertised.

I just thought it worth mentioning that before or after installing Windows 7 that it’s worth making sure the BIOS is up to date as well? :)

  • Share/Bookmark

written by dcaddick

Aug 18

Some while back one of my US based colleagues passed on some advice about checking out some details on how to get the best out of Wireshark

For anyone interested in getting their feet wet using Wireshark the network protocol analyzer.  This knowledge can be useful to have when dealing with network anomalies.

www.chappellseminars.com/s-wireshark101.html

Download the latest 1.2.1

As you may or may not know this was originally called Ethereal, and then morphed in to Wireshark, and has recently had quite a number of improvements and has moved from ver. 0.9 to now 1.2 plus in the last few months. There has been quite a number of additions including the ability to graph throughput etc from within the tool, as well as it now supporting GeoIP DB’s so that you can carry out extensive mapping of where the packets are going to or coming from.

http://wiki.wireshark.org/HowToUseGeoIP

Running Windows 7?

If you are running Windows 7 – then do be aware that the WinPcap driver (the component that does the sniffing) will fail to install by default – but if you modify the executable to run in Vista SP1 compatability mode then all should be fine – as detailed below:

I’ve just downloaded WinPcap 4.1 beta5 from here: WinPcap, the Packet Capture and Network Monitoring Library for Windows Set the compatibility mode to Windows Vista (right click on the installer executable then select Properties; on the Compatibility tab, check "Run this program in compatibility mode for", select Windows Vista SP1 from the dropdown list, then finally click OK =)) and it will install as it should.
For me it worked flawlessly so far.

Further reading

I then followed this up a bit further and noted that after a recent Sharkfest event there were a number of presentations made by a chap called Ray Tompkins (CEO of Gearbit) and these are available at:

At Sharkfest 2009 gearbit presented 3 sessions::
Finding the Latency:
How Protocols Work:

Wireshark Charts & IO Graphs:
OSTU – Wireshark IO Graph for Response Time Analysis:
Understanding the Need for Protocol Analysis: HYPERLINK
OSTU – Wireshark Case Study: Benchmark Test
OSTU – Wireshark TCP Stream Graphs
OSTU – Wireshark Capture Filters
OSTU – Wireshark Display Filters
OSTU – Identifying Zero Window with Wireshark

If you do find that you have to dig in on a Customers Site to start doing some serious troubleshooting around Networks then I would seriously recommend the first two presentations in PDF format as they do appear to explain things in a very simple and matter of fact way.

Wireless Issues:

Now this should in no way be any sort of substitute for a proper Wireless Survey, but when you find that you are up against some issues then try using inSSIDer as a very good starting point? And it works on Windows 7 straight out of the box ;-)

image

  • Share/Bookmark

written by dcaddick

Jan 17

I recently was doing some final testing after installing a number of BladePC’s and I was pretty sure that I had connected to blade-003 via an RDP connection only to find the file that I was looking for wasn’t in the C:\Temp location at all – and I was certain that the Altiris Console had just reported the File Copy job that I had just started had gone through clean……  So what was going wrong?

It turned out that when I checked the host name of the Blade I was actually on blade-051 and not 003 after all (we were still just finalizing the images and hadn’t added BGInfo at this stage, so it wasn’t immediately obvious)

As I started to dig in to this with the local Admin it became clear that quite a lot of changes had happened to the system in the past few months and there was a still a lot going on, but the upshot of it was that the DHCP and IP address info I had received on my Laptop was inconsistent with what the servers were using.

The Altiris Server was using:

  • Primary DNS – A
  • Secondary DNS – B
  • WINS – A
  • WINS – B

    And the DHCP info that my Laptop was using was:

  • Primary DNS – A
  • Secondary DNS – B
  • WINS – C
  • WINS – B

    It looked like everything would work correctly if I had used the FQDN or long name to connect to the blade, but when using the short name it resolved this from an older server that was inconsistent with the realities in the Network

    *TIP* When you change the Primary and/or Secondary DNS or WINS server always take some time to check they all have the correct info – AND – make sure you update the DHCP scopes as well as all the Servers?

    Don’t forget that AD itself relies on this being correct or you could face even bigger issues?

    • Share/Bookmark

    written by dcaddick

    Jan 12

    A colleague of mine was after some info on a tool that I had mentioned before and while I was at it I had some extra tools and links and other handy stuff that I thought I’d share?

    The details regarding Fixed Mode below have proven to be very useful today in getting PXE working across multiple VLAN’s – very nice to see it burst in to life :-)

    Gui tool to check AD/LDAP context etc. (30 day free trial)

    Softerra LDAP Browser

    Altiris DS 6.8 Docs… (Very useful for additional info)

    chapter-1-preparing-your-server-ds68sp2-installation
    chapter-2-installing-deployment-solution-68sp2
    chapter-3-introducing-ds-console
    chapter-4-introduction-imaging-using-pxe
    chapter-5-ms-dos-a-pxe-automation-option
    chapter-6-winpe-pxe-automation-option
    chapter-7-hidden-bootworks

    Troublshooting PXE

    Altiris KB – PXE not crossing subnets or VLANs
    Altiris KB – Configuring PXE to work across VLANs
    Altiris KB – Error: PXE-E53: No boot filename received (very comprehensive list of 11 possible causes and 14 possible resolutions, and a reminder that when using Wireshark filter down to BOOTP packets to focus on PXE)
    Installing Altiris Deployment Server and Altiris PXE Server in a VLAN Environment this lead me to this link of a PDF (PXE Modes of Operation) regarding setting PXE in “Forced Mode” that has just worked a treat in a multi VLAN environment and essentially it means that you simply set Options 60, 66, 67 and 43 on the DHCP with the relevant details of where to find the PXE Server

    Now setting the Option 43 correctly is not quite that simple, so I have added my explanation here:

    All figures/values need to be in HEX
    Example: 06 01 0B 08 0F AA AA 03 C0 A8 02 C8 C0 A8 03 68 C0 A8 01 66

    06 01 0B 08 and AA AA are set by Altiris and should not be changed

    0F = Specifies the number of octets that exist to be read after this one (the fifth octet) in this particular case it’s 15

    03 = Number of PXE Servers, change as needed, in this example there are 3 PXE Servers

    C0 A8 02 C8 C0 A8 03 68 C0 A8 01 66 = the IP Address of each PXE Server, defined in HEX, octet by octet

    C0 A8 02 C8 = 192.168.02.200

    Once you have crafted the Value of Option 43 as described above you simply need to add a zero value of 00 to indicate the end of the Value and then add this to the DHCP Server, paying particular care not to add any spaces or CR’s?

    Alternatively I have also discovered a tool that can help in making this calculation at PXE Forced Mode Utility

    • Share/Bookmark

    written by dcaddick

    Dec 27

    Interesting? I’m already running an earlier release of Windows 7 under VMware Workstation as described in an earlier post so it’s good to hear that the Beta will be out shortly as this will put the code through a more vigorous round of testing and should seriously shake the bugs out? Although the latest update would appear to indicate that MS has pulled back from an early Jan. release I’d be guessing that it will be out earlier rather than later?

    Windows 7 Beta download will be available before January 5th

    Ed Bott, a good friend of mine, recently predicted that Windows 7 Beta bits are going to be publicly unveiled on January 13, during CES. Some late night scrounging around revealed that Windows 7 could be available sooner — via download links slipped into the next Microsoft Action Pack Subscription quarterly update kit, which starts shipping January 5, 2009. Word internally is that the beta build was already baked a while ago, we just have to be patient.

    Update (Dec 23): Microsoft has removed all mention of Windows 7 Beta.

    What is also interesting to note is the amount of time and effort that Microsoft is taking to “eat their own dog food” as well as make sure people know they are focusing on both the actual performance as well as the perceived performance? :)

    Squeezing Every Drop of Performance Out of Windows 7

    In accordance with users’ expectations

    Windows 7

    In the sense in which Microsoft is building Windows 7 as the evolution of Windows Vista, the next iteration of the Windows client will perform as if on steroids, compared to its precursor. Steven Sinofsky, senior vice president, Windows and Windows Live Engineering Group, along with Michael Fortin, one of Microsoft’s Distinguished Engineers and head of the Windows Fundamentals feature team, revealed that the Redmond company had a strong focus on delivering a high level of performance for Windows 7, comparable with end users’ expectations. And Microsoft should make no mistake about it, Windows 7 performance expectations are as high as they can be. 
    “We’ve been building out and maintaining a series of runs that measure thousands of little and big things,” revealed Sinofsky and Fortin. “We’ve been running these before developer check-ins and maintaining performance and responsiveness at a level above which all that self-host our builds will find acceptable. These gates have kept the performance and responsiveness of our daily builds at a high enough level that thousands have found it possible to run their main systems on Windows 7 for extended periods of time, doing their normal daily work.”

    Microsoft underlined that the perception of performance was just as important as the actual performance delivered by the operating system. In fact, what managed to hurt Vista the most was this perception of poor performance compared to Windows XP, despite the fact that benchmarks from the software giant placed the two operating systems on par.
    “We’ve been driving down footprint, reducing our service costs, improving the efficiency of key code paths, refactoring locks to improve scalability, reducing hangs, improving our I/O efficiency and much more. These are scenario driven based on real world execution paths we know from our telemetry to be common,” Sinofsky and Fortin added.
    In addition to the actual efforts poured into building the Windows 7 bits, Microsoft is also collaborating closely with original equipment manufacturers (OEMs), independent software vendors (ISVs) and independent hardware vendors (IHVs) in order to ensure that Windows 7 will deliver a top performance in concordance with the hardware resources it is made available with. But at the same time the Windows developing team is keeping a close eye on the milestones of the operating system as they are deployed internally.
    “Within the Windows dev team, we’ve placed a simple trace capturing tool on everyone’s desktop. This desktop tool allows each person to run 24×7 with performance tracing enabled. If anything seems slow or sluggish, they can immediately save the last minute-or-so of activity and send it for automated analysis. Additionally, a team of people visually inspect the traces for new issues or issues not yet decipherable by our automation. The traces are incredibly rich and allow us to get to the root of top issues most of the time,” Sinofsky and Fortin said.
    In the end, Microsoft does not rely exclusively on monitoring tasks performed as an integral part of the dogfooding of Windows 7. The company is also centralizing telemetry from the testers participating in the Windows 7 pre-Beta program and will continue to do so throughout the Beta and Release Candidate stages. In addition, the software giant will take into account micro-benchmarks and specific performance scenarios for Windows 7, on top of the system tuning it is already introducing.
    "For all Pre-Beta, Beta and RTM users, we’ve developed a new form of instrumentation and have used it to instrument over 500 locations in the operating system and inbox applications. This new instrumentation is simple in concept, but revolutionary in result. The tool is called PerfTrack, and it has helped confirm our belief that the client benchmarks aren’t too informative about real user responsiveness issues," Sinofsky and Fortin stated.

    • Share/Bookmark

    written by dcaddick