Archive for the ‘Sys. Admin.’ Category
Monday, October 26th, 2009
Update (15/11/2010): the drivers listed in this post are out of date and may cause a BSOD, several alternatives are listed in the comments; however Microsoft appear to have approved 64-bit drivers on Windows Update.
I am typing this on my Acer Aspire 5102WLMi which is one of the popular (if flawed) Acer Aspire 5100 series; I rescued this one from the Balconi Test by putting a bit of rubber (it was a cut down rubber foot) on top of the South Bridge chip set, that however is not the story I am telling today.
I never bothered to install the Card Reader driver on this laptop while I was running the Windows 7 Beta, mainly because I am lazy, but also I didn’t have a need for it so it never came up. With the release of Windows 7 I wanted to get the system perfect, seeing as hopefully it will last a good year in it’s present state, and I wanted to be able to re-arrange the SD card from my Acer PDA.
Windows 7 x64 was unable to identify a driver for this particular card reader, this left me with three unknown devices in Device Manager:
The Acer website was a bust, as far as Acer are concerned this laptop won’t even run Vista x64, so I had to dig deeper. From past experience of looking for drivers without using Windows Update I knew that I could probably identify the manufacturer from the Hardware and Device ID’s available through Device Manager. If you want to follow along here are the steps:
- Open up Device Manager (Right Click “Computer”, Choose “Manage”, Select “Device Manager”)
- Identify your unknown devices (They will look similar to the image above, although the text will differ)
- Right click one of them and select “Properties”
- Switch to the “Details” tab
- Change the property drop down box to read “Hardware Ids”
What that will give you is one or more strings looking something like this
I have marked the two important parts in bold, the four digits after “VEN_” tell you the PCI Vendor number, the four digits after “DEV_” tells you device number these two numbers should uniquely identify the driver.
There are several sites that allow you to lookup these numbers, I tend to use the publicly available PCI Vendor and Device Lists at PCIDatabase.com. Which has always given me good results with minimum fuss and adverts.
Armed with the above I identified the manufacturer of the Card Reader was ENE Technologies, sometimes this is all you need to find the driver. You can Google/Bing the name and click the download or support links and get the latest drivers. This isn’t always the way, as some OEMs don’t offer drivers leaving that down to the system integrator to offer that service.
So some time with Bing, I found some drivers for various ENE Devices, however the drivers available from VersionTracker seemed promising. After downloading and unzipping the contents of the file to a folder on my Desktop, I was able to point Device Manager at these files for each of the unknown devices I was left with three working devices and a fully operational Card Reader.
Hope this helps some other people with similar laptops or Card Readers, post in the comments with your experiences, please include the manufacturer and model of the laptop/netbook you have succeeded with and hopefully you will help someone else with the same devices.
Friday, October 23rd, 2009
I have been updating this blog post over the years since I first discovered the issue with my computer in Windows Vista, now I am on Windows 8 and also on FTTC broadband; Path MTU Discovery seems to just work. I have tested the process so the approach and the commands still work in Windows 8, I however no longer need to use this process personally.
For some reason that has escaped me Path MTU Discovery (PMTUD) in Windows just doesn’t seem to figure out the MTU for a given path (something to do with routers being poorly configured to not respond to ICMP requests). So Windows uses the default. For the most part this doesn’t affect anyone, however if it does affect you, it really annoys you. Failure of PMTUD will result in some websites not loading correctly, having trouble connecting to normally reliable online services and general Internet weirdness.
The resolution is to set your default MTU to one lower than the Ethernet default of 1500. Here is how:
Step 1: Find your MTU
From an elevated Command Prompt in Vista/Windows 7 or the same elevated Command Prompt in Windows 8 enter the following command:
netsh interface ipv4 show subinterfaces
You should get something like this
MTU MediaSenseState Bytes In Bytes Out Interface
---------- --------------- --------- --------- -------------
4294967295 1 0 13487914 Loopback Pseudo-Interface 1
1500 1 3734493902 282497358 Local Area Connection
If you are using Ethernet cable you will be looking for “Local Area Connection” or “Ethernet”. If you are using Wireless you will be looking for “Wireless Network Connection”. The MTU is in the first column.
Step 2: Find out what it should be
In the Command Prompt type:
ping www.cantreachthissite.com -f -l 1472
The host name should be a site you can not reach, -f marks the packet as one that should not be fragmented the -l 1472 sets the size of the packet (1472 = Ethernet Default MTU – Packet Header, where the Ethernet Default MTU is 1500 and the Packet Header is 28 bytes)
If the packet can’t be sent because it would need to be fragmented you will get something similar to this:
Packet needs to be fragmented but DF set.
Keep trying lower packet sizes by 10 (i.e. -l 1460, 1450, 1440, etc.) until you get a successful ping request. Raise your packet sizes by one until you get a “Packet needs to be fragmented but DF set.”. The last successful value plus 28 will be your MTU value.
In my case a packet size of 1430 succeeds but 1431 fails, so 1430 + 28 = 1458.
Step 3: Set your MTU
Now you have identified the interface you need to change and the ideal MTU for you, now it is time to make the change. Again from an elevated Command Prompt type the following replacing my MTU of 1458 with your own value:
netsh interface ipv4 set subinterface "Local Area Connection" mtu=1458 store=persistent
Or if you are using a Wireless connection:
netsh interface ipv4 set subinterface "Wireless Network Connection" mtu=1458 store=persistent
If all has gone well you should have a perfectly working internet connection.
Thursday, October 22nd, 2009
Windows 7 turned up in the post today. The red box is Visual Studio 2008 which is there to show that the boxes have a similar profile to the old style hard cases.
I have been running the Beta since it was first available to the general public, and I have had Windows 7 Business at work for a couple of weeks now. Bought Windows 7 Home Premium for about £45 from Tesco. One copy for the main PC which I will probably re-build at Christmas and one copy for the laptop which is re-built now. Scott Hanselman described Vista as an operating system that stabs you in the eye a thousand different ways, I would have to agree with that. Windows 7 is different, things work how you think they should and don’t seem to randomly break when you least expect it.
As for the title of this blog post, I have mostly been installing Windows 7 to Vampire Weekend which Kev introduced me to. The track M79 seems to have taken some inspiration from the Sailor’s Hornpipe better known as the Blue Peter theme tune, seems to cut off just at the moment I am expecting it to carry on into the main part of the music. Maybe there is a Mike Oldfield link in addition to the lyrical Peter Gabriel link.
If I am moved to over the course of the next couple of week I shall try and point out some of the new features available in Windows 7 that are cool. For the time being try the following hold down Alt, while still holding down Alt press “Alt Gr” (The other side of the space bar) then press Tab. For some reason you get the old XP style Alt-Tab window. Utterly pointless?
Thursday, February 5th, 2009
Having done a little experimenting with Visual Studio Extensions for WSS (VSeWSS), I wanted to start actually developing features for our intranet site. I try and add everything that is even slightly important into source control (Subversion). VSeWSS creates normal looking solutions, however when you deploy your project to a SharePoint site it created an additional directory alongside “bin” and “obj” called “pkg”.
This “pkg” folder contains the manifest.xml, soloution.xml and feature.xml files that are used to create the feature to be deployed into SharePoint. Initially I was including this folder in my commits however, I noticed that any tweaks made to feature.xml were overwritten when you deployed the package again. After some searching around I came across an article that suggests deleting the “pkg” folder under certain circumstances. From this I assume that the contents of the “pkg” folder is generated each and every time you package and deploy your solution (or indeed project), thus it does not need to be added to source control.
While writing this post I did come across another blog that suggests adding the “pkg” folder to source control. There does appear to be little advice out there regarding VSeWSS and Source Control. I would be interested to hear others experiences on the subject.
Tuesday, November 25th, 2008
Typemock are offering their new product for unit testing SharePoint called Isolator For SharePoint, for a special introduction price. it is the only tool that allows you to unit test SharePoint without a SharePoint server. To learn more click here.
The first 50 bloggers who blog this text in their blog and tell us about it, will get a Full Isolator license, Free. for rules and info click here.
Monday, September 8th, 2008
For my regular day job I am a Systems Administrator, my team and I manage a network with 7 servers and approximately 600 workstations, 200 laptops and 2500 users. All clients are Windows XP SP2 or SP3 and all servers are Windows 2003 SP2 or Windows 2003 R2 SP2.
I am sure I am not alone in knowing least 5 commands that I use day in and day out to manage workstations or servers on the network. I thought I would take the time to share some of these with you now.
Tuesday, July 22nd, 2008
The SMART .notebook format is simply a zipped set of XML and SVG files, This may be common knowledge but it is certainly the first time I have come across it.
To test it you can create a file in SMART Notebook rename the extension from .notebook to .zip, double click to open, you will be presented with several files named pagen.svg where n is a number, as well as a series of other files and folders including settings.xml, preview.png and metadata.xml.
The XML and SVG files can be edited in notepad, or perhaps more useful for the SVG files in a program such as Inkscape.
Saturday, September 1st, 2007
Seeing as Catherine and I finally bought our own house and it looks like we might be staying here for much longer than we have ever stayed anywhere else, we are looking at options for home networking, our current solution involves a 802.11b Wireless Network for laptop connectivity and a cable for my PC, that has to be removed each night to close the living room door.
Wednesday, August 29th, 2007
I am currently trying to diagnose several Windows XP SP2 computers with severe network problems, the bottleneck is in the network. Whilst deploying a group policy object the Windows Installer Service crashed due to a network time-out, and this was the resultant response from Error Reporting:
So there you go the problem with Windows XP is Windows Vista!
Wednesday, August 29th, 2007
Recently purchaced and installed a new HP ProLiant DL320s to run as the site primary file server, had some issues with Windows 2003 R2 32-bit as it repeatedly BSODed before getting into graphical setup, tried the drivers for the SAS controller also tried the disc on a different computer to no avail. After chatting with a few people someone asked why I wasn’t going for 2k3 R2 64-bit, the main reason for not using it was it I had not had a chance to test it out in a test environment and wasn’t overly happy putting it into a live environment, looked at the software that was going on the File Server and all seemed ok, installed the ProLiant Support Pack migrated files, setup file screening and quotas. All was well, server running very fast and very happy.
Came to install BackupExec 10d yesterday, BIG mistake seeminly when I checked to see if BackupExec supported Windows 2003 R2 64-bit on a x64 Architecture I got confused, yes remote agents are supported on that architecture and the media server is supported on IA64 Architectures, however the media server is not supported on Windows 2003 R2 64-bit (x64)… wooops.
Fortunatly it seems that all is not lost as BackupExec 11d looks like it will work and the options from 10d can be upgraded to 11d, now all I have to do is cost it all up. Note to self and other system Administrators read Symantecs compatability lists VERY carefuly.