So I configured my new Sharepoint 2007 farm to use kerberos using Configure Kerberos authentication (Office SharePoint Server) and I ran into some undocumented problems. I got 401 errors when trying to access some Sharepoint urls on the internal network. This was because I configured more than one url binding on an IIS website. Even though i configured both SPN’s on the service account that was running the Sharepoint application, it was not working using IIS 7 and kerberos. Kerberos will only work on one URL in the binding list, which ever you will try to access first. In order to fix this you have to create a new IIS website using the extend web application function in Sharepoint Central Administration. I was not able to figure out if this is an IIS 7 bug or that this is ‘by design’. Configuring multiple SPNs on one service account however, is not a problem.

The second kerberos problem I ran into gave me more trouble to find out what is going wrong. Kerberos constrained delegation from the ISA to the sharepoint site was not working. I was a bit puzzled by this because kerberos logging didn’t have a clear answer. It gave me a Kerberos Pre-Authentication Error. As expected ticking the box on the service account ‘Do not require Kerberos preauthentication’ didn’t gave me a solution.

The problem is that IIS 7 has a new feature called Kernel Mode Authentication. Kernel Mode Authentication uses the SPNs on the computer account, even if the application pool runs on a different service account. This is a problem when you are running a Sharepoint farm with more than one frontend webserver. Since SPNs can only be registered once as you already now.
So even if you are running a Sharepoint Farm on one server, consider it best practise to disable Kernel Mode Authentication, on all sharepoint related websites in IIS that have kerberos authentication enabled, including Office Server Web Services. You can disable Kernel Mode Authentication in the IIS MMC on the website select Authentication -> Windows Integrated Authentication -> Advanced Settings.

• FEATURE: Better visitor experience when clicking on a link/search or commenting. Especially when the server or the connection is slow. It is configurable in the WP Admin Panel. Thanks to Vijayendra Mohanty for suggesting it
• FEATURE: You can now disable the Left-Sidebar to have a bigger main column. Thanks to Becky Lai for the idea that is showed on www.sockparade.com

• FEATURE: About text and link is configurable in WordPress Admin Panel
• ENHANCEMENT: The number of Recent Posts in the Slide Ticker is now configurable.
• ENHANCEMENT: The post tags are now also in the post itself.
• ENHANCEMENT: Code for the WP Ajax Connector Framework is now in it own files.. It also has its own Admin Panel page.
• ENHANCEMENT: The comment submit button is immediately disabled when your clicked on it, so double clicks because the visitor is inpatient can not occur.
• ENHANCEMENT: History (back and forward navigation) in Internet Explorer finally works! It was really a pain to get the workaround working right with a minimum amount of coding…
• BUGFIX: An error message can be displayed if something went wrong with the comment submitting.
  Merged the commenting code of WordPress 2.2 which should be backwards compatible.
• BUGFIX: Double title in Categories when not using widgets. Thanks to Martin Böttinger for reporting it. I failed to notice it
• BUGFIX: Image preloading didn’t really loaded all images on a very fast visitor pc.
• BUGFIX: Anchors should now be working right (not getting a 404 page not found anymore)
• VISUAL: Changed the bullet.gif so It won’t contain a dot inside… Didn’t really like it

Sorry, no notes on 1.3 to 1.3a I was too busy fixing bugs and lost track of all the changes committed

Upgrade note:
If you are updating from 1.2, please note that some files have been renamed! Also, if you enabled the Slide Ticker on your site, please go to the WP Admin Panel -> Presentation -> AjaxBerlee Options and change the value of the Slide Ticker to a number, for example 15.
You also might want to change the about text since it is now controlled in the WP Admin Panel

Download AjaxBerlee 1.3a

• FEATURE: Configurable options in WordPress Admin Panel!
• SUPPORT: WordPress Widget support
• ENHANCEMENT: Made the TextSlider code much nicer. And works much better now.

• ENHANCEMENT: Replaced WordPress functions for the theme that where deprecated in WordPress 2.1 and no longer supported. This means there no WordPress 2.0 support anymore in this theme!
• ENHANCEMENT: When one of the membership options under General Option (in WordPress Panel) is set an Login/Logout Register/Site Admin will appear on the left sidebar. (when not using widgets)
• ENHANCEMENT: When a blog is accessible with more than one URL, it will all be redirected to the blog URL defined in WP-admin since the Ajax functions must obey the Same Origin Policy: http://www.mozilla.org/projects/security/components/same-origin.html
• BUGFIX: Fixed timing issue only occourred with Internet Explorer with a # link… Because it executed the javascript faster than the page could load… This would bring up an Navigation cancelled dialog box.
• BUGFIX: Some characters in the title with accent or circumflexes or just a plane ‘ quote would be displayed as HTML character entities. (for example " & < >)
• BUGFIX: Images with a space in the URL are not preloaded.
• BUGFIX: An URL to an external page containing your blog url as a parameter are treated like an internal page. Resulting in a 404 Page not found.

Installation

It’s pretty straight forward, just put the whole directory AjaxBerlee (and content in it of course) to the wp-content/themes. After that, goto Presentation -> Current Theme Options and select the options you like.

Big Tip
Use WordPress Widgets! You can download it from http://automattic.com/code/widgets after that copy the widgets from the plugins/widgets to the widgets directory on the webserver and active them.This allows you to use all components in the sidebar that currently statically exists, to use them very dynamically!

A minimal, simple, crisp, clear and light 3 column design. This plugin independent theme highlights the excerpt of the latest article on the home page.

AjaxBerlee is based on the Brajeshwar theme, but it’s much faster and it comes with interesting AJAX features such as Instant Comment, Instant Search, Page and Image preloading and an article slider.

Changes

• Loads of little code enhancements in the WP Ajax Connector Framework to make it more robust and better compatible with Firefox
• Preloading of images when a visitor hover over an article link that contains images
• Navigation on the front page (older articles)
• Merged some of the code of Brajeshwar 7.2.2
• Added support for some plug-ins… See TIPS in ReadMe.txt

Compatibility
AjaxBerlee Theme and the WP Ajax Connector Framework are compatible with WordPress:

• WordPress 2.0.x
• WordPress 2.1.x (tested up to 2.1.3)
• WordPress-MU (tested up to 1.2.1)

Tested on browsers:

• Internet Explorer 6 & 7
• Firefox 2.0.0.3
• Opera 9.20

Please the latest version!

Common Problem!
It’s very important that you fill in the right WordPress and Blog address in the WordPress Admin Panel under options:

While this sounds a bit obvious, when your site is www.berlee.nl please double check this value in the Admin Panel to see if it really says http://www.berlee.nl and not http://berlee.nl because that results in a unbrowseable website

Because of security issues Ajax request works only from the url that is configured in the WordPress Admin Panel.

• Boot with PXE boot
• Write down the last four MAC digits
• Change the computer name in the ghost console configuration
• Clone the new pc’s with a configuration template (for domain etc)

Especially step 2 and 3 are time consuming… This started me to think about a solution. The easiest way was to ask for a computer name during PXE boot and give that computer name as a parameter to NGCTDOS.exe (which is the Ghost Console client for dos). NGCTDOS then would deliver the computer name to the ghost console.

Nice huh? Except for one thing… there is no such parameter. I asked this question on the Symantec Forum and Nigel Bree (a really great Principal Software Engineer for the Ghost Solution Suite) kindly replied it would be a fairly natural extension.

This started me to think about other ways to get this done, without a pain. I came up with a solution involving ghconfig (which is part of the PXE boot image), change.com (a 19 year old text replacing utility of 737 bytes!) and wbat.exe (a dialog box utility by Horst Schaeffer).

The end result is a dialog box with mouse support, which asks for 15 seconds for a computer name. If no input is given during that period or cancel is pressed, the Ghost Console Client will behave as a normal Ghost Console dos client. If a computer name is entered, the computer name will be set after the ghost image process.

If you also want to speed up your new pc’s deployment process, follow the following steps:

1. Go to the ghost console and pick a Machine configuration. Change the computer name in REPLACE (in capitals). Change other settings to the settings you want on your new pc’s.
   
   Export the configuration, and name the file: ghregupd.reg
2. Download ghost-console-new-pc.zip and unpack the zip file
3. Open the 3Com Boot Image Editor (which is part of the 3Com Boot services on the Ghost install CD)
   
   Edit the sys pxe file that was created by the Ghost Boot Wizard
   
   Place the just unpacked files (from the downloaded zip file) in the root of the boot image. And put ghregupd.reg in the GHOST directory.

You are done.

Please note that if you are now deploying new pc’s the pc’s will appear in the folder New Computers on the Ghost Console initially with their MAC addresses. But after you run a successful task with the following steps:

• Clone
• Execute Command in Ghost Boot Partition: ghconfig.exe /a
• Configuration Refresh
• (Optionally packages, but absolutely not Configuration!)

The computer names will magically appear.

Please note that because Ghost Console is normally in charge of creating or resetting the computer domain account. This means that the new computers are probably not a domain member. You can fix this by running a configuration task with a configuration template afterwards.

Good luck!

So here you are, faced with a problem. You only want to maintain one image, but that image contains a Ghost Console membership certificate, which means if you are going to deploy that image using other Ghost Consoles, clone tasks will fail, because all computers will contact the Ghost Console on which the image is created.

Luckily Ghost Clients can discover a console. This works as follows according to the Symantec Knowledge base:

Ghost Clients find the Console using two methods. First, Method 1 is tried, and if that fails, Method 2 is attempted.

Method 1: Multicast
The client sends a Multicast packet to an address and port number that the Console is expecting. All Consoles register their interest in this traffic by sending IGMP (Internet Group Management Protocol) messages. Properly configured routers and switches pass this traffic to the Console. Ensuring that the routers will pass Multicast traffic is usually all that is necessary to get this method working.

Method 2: WINS
Details of this method are shown below for your interest. However, this method relies on a WINS infrastructure existing and working between the networks in question. Usually, if you can browse a computer in the remote site using My Network Places in Windows Explorer, then this method COULD work.

This means that if your routers are only passing multicast traffic to the VLANs they suppose to, it should work if you delete the pubkey.crt during the mini setup sysprep install of the new clients. You can do this by creating a cmdlines.txt in the i386$oem$ directory. The content of cmdlines.txt could be something like this:

[Commands] 
"c:\windowssystem32\wscript.exe c:\sysprep\InSysprep.vbs"

 In that same sysprep directory create a file called InSysprep.vbs with the following content:

Set objFS = CreateObject("Scripting.FileSystemObject") 
objFS.DeleteFile "C:\Program Files\Symantec\Ghost\pubkey.crt", True

This will delete the membership with the console during the Sysprep Mini-Setup. Since the ghost client service isn’t started when the Mini-Setup runs, Ghost Client will search for a Ghost Console the first time it will boot up Windows successfully.
In an Ideal world, this would be enough to encourage clients to pick the right console. But I ensure you, when you are ghosting a lot of clients at the same time, some will fallback to the 2th method of server discovery…. WINS…

So what can we do about that? Well, the answer is simple. Use a Firewall.. If you have the luxury of layer 4 Routers use them to block Ghost Client traffic (NOTE: port 1346 and 1347 are switched in stage 2 and 3) between VLANs to Ghost Consoles.

If not, please don’t download the first personal firewall you can find! Use build in Windows tools. IPSec is build into Windows since 2000. The interface is a bit overcomplicated, so I will use ipseccmd to show you how to only allow Ghost Clients that are on subnets you define. Ipseccmd is part of the support tools that can be downloaded from microsoft:

• Windows XP SP2 Support Tools
• Windows 2003 SP1 Support Tools
• Windows 2000 Support Tools

Run the following commands on your ghost consoles after you have installed the Support Tools (or extracted the ipseccmd.exe from the support tools):

ipseccmd.exe -w REG -p "Ghost Console Clients" -r "Block all Ghost Clients on non defined subnets" -f *=0:1345:UDP -f *+0:1347:UDP -f *+0:1347:TCP -n BLOCK -lan 
ipseccmd.exe -w REG -p "Ghost Console Clients" -r "Allowed Ghost Clients on based on a subnet" -f 10.1.0.0/255.255.0.0=0:1345:UDP -f 10.1.0.0/255.255.0.0+0:1347:UDP -f 10.1.0.0/255.255.0.0+0:1347:TCP -n PASS -lan 
ipseccmd.exe -w REG -p "Ghost Console Clients" -x

The first ipseccmd line blocks all Ghost Client traffic to the console. The Second line needs to be repeated for every subnet you want to allow. In this example only allows clients in the subnet 10.1.0.0/255.255.0.0 to connect to that ghost console… replace it for your allowed subnets…. The last line is there to tell IPSec to enable the rules.

If you screwed up, you can always run:

ipseccmd.exe -w REG -p "Ghost Console Clients" -o -y

To clear and disable the IPSec rules.

If the clients on the same subnet as the console and they are not suppose to be connecting the Ghost Console, the first and second line are different because they need to disable multicast discovery:

ipseccmd.exe -w REG -p "Ghost Console Clients" -r "Block all Ghost Clients on non defined subnets" -f *+0:1345:UDP -f *+0:1347:UDP -f *+0:1347:TCP -n BLOCK -lan 
ipseccmd.exe -w REG -p "Ghost Console Clients" -r "Allowed Ghost Clients on based on a subnet" -f 10.1.0.0/255.255.0.0+0:1345:UDP -f 10.1.0.0/255.255.0.0+0:1347:UDP -f 10.1.0.0/255.255.0.0+0:1347:TCP -n PASS -lan

Good luck!

So you finally download, unpacked and updated your Broadcom BCM57xx or Intel Pro 100/1000 NDIS2 drivers using Ghost Boot Wizard but Ghost doesn’t suggest / autoselect your just updated drivers like it does with the default shipped ones! What’s that all about?

In order to detect networkcards, Symantec ghost needs to know on a per driver bases the PCI device IDs. PCI device IDs are normally stored in inf that are packed with the drivers. Those inf files tells Windows for which device the drivers are and how to install them. I have extracted the PCI device IDs from the inf’s and formatted them into the Ghost file format.

If you updated the BCM57XX driver go to the directory: C:Documents And SettingsAll UsersApplication DataSymantecGhostTemplateBCM57XX (some directories might be hidden) or if you added a template replace the last directory by the template name of the template you added.

Edit the mcassist.cfg and replace all the PCI-TAG lines with the following lines: (these are based on the Broadcom BCM57XX 9.81 driver:

PCI-TAG = 14e4 1600 : Broadcom BCM5750A1$ 
PCI-TAG = 14e4 1601 : Broadcom BCM5750A1M$ 
PCI-TAG = 14e4 1644 : Broadcom BCM5700$ 
PCI-TAG = 14e4 1645 : Broadcom BCM5701$ 
PCI-TAG = 14e4 1646 : Broadcom BCM5702$ 
PCI-TAG = 14e4 1647 : Broadcom BCM5703$ 
PCI-TAG = 14e4 1648 : Broadcom BCM5704$ 
PCI-TAG = 14e4 1653 : Broadcom BCM5705$ 
PCI-TAG = 14e4 1654 : Broadcom BCM5705A2$ 
PCI-TAG = 14e4 1658 : Broadcom BCM5750$ 
PCI-TAG = 14e4 1659 : Broadcom BCM5750A1$ 
PCI-TAG = 14e4 165D : Broadcom BCM5705M$ 
PCI-TAG = 14e4 165E : Broadcom BCM5705MA2$ 
PCI-TAG = 14e4 1668 : Broadcom BCM5714$ 
PCI-TAG = 14e4 1669 : Broadcom BCM5714S$ 
PCI-TAG = 14e4 166A : Broadcom BCM5780$ 
PCI-TAG = 14e4 166B : Broadcom BCM5714S$ 
PCI-TAG = 14e4 166e : Broadcom BCM5705F$ 
PCI-TAG = 14e4 1672 : Broadcom BCM5750A1M$ 
PCI-TAG = 14e4 1673 : Broadcom BCM5750A1DMOBILE$ 
PCI-TAG = 14e4 1676 : Broadcom BCM5750$ 
PCI-TAG = 14e4 1677 : Broadcom BCM5750A1$ 
PCI-TAG = 14e4 1677 : Broadcom BCM5750$ 
PCI-TAG = 14e4 1678 : Broadcom BCM5714$ 
PCI-TAG = 14e4 1679 : Broadcom BCM5714S$ 
PCI-TAG = 14e4 167A : Broadcom BCM5750A1$ 
PCI-TAG = 14e4 167B : Broadcom BCM5750A1$ 
PCI-TAG = 14e4 167C : Broadcom BCM5750A1$ 
PCI-TAG = 14e4 167D : Broadcom BCM5750$ 
PCI-TAG = 14e4 167E : Broadcom BCM5750A1F$ 
PCI-TAG = 14e4 167F : Broadcom BCM5750A1F$ 
PCI-TAG = 14e4 1693 : Broadcom BCM5750A1M$ 
PCI-TAG = 14e4 1696 : Broadcom BCM5705A2$ 
PCI-TAG = 14e4 169A : Broadcom BCM5750A1$ 
PCI-TAG = 14e4 169B : Broadcom BCM5750A1$ 
PCI-TAG = 14e4 169c : Broadcom BCM5788$ 
PCI-TAG = 14e4 169d : Broadcom BCM5789$ 
PCI-TAG = 14e4 16a6 : Broadcom BCM5702$ 
PCI-TAG = 14e4 16a7 : Broadcom BCM5703$ 
PCI-TAG = 14e4 16A8 : Broadcom BCM5704S$ 
PCI-TAG = 14e4 16C6 : Broadcom BCM5702$ 
PCI-TAG = 14e4 16C7 : Broadcom BCM5703$ 
PCI-TAG = 14e4 16DD : Broadcom BCM5789$ 
PCI-TAG = 14e4 16F7 : Broadcom BCM5750A1$ 
PCI-TAG = 14e4 16FD : Broadcom BCM5750A1M$ 
PCI-TAG = 14e4 16FF : Broadcom BCM5750B0M$ 
PCI-TAG = 14e4 170D : Broadcom BCM5901$ 
PCI-TAG = 14e4 170E : Broadcom BCM5901$

If you updated the Intel Pro 100 driver go to the directory: C:Documents And SettingsAll UsersApplication DataSymantecGhostTemplateIntel Pro 100 (some directories might be hidden) or if you added a template replace the last directory by the template name of the template you added.

Edit the mcassist.cfg and replace all the PCI-TAG lines with the following lines: (these are based on the Intel Prodos 11.2 driver:

PCI-TAG = 8086 1037 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 103C : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 103D : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 103E : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 2459 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 245D : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1059 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1050 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1051 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1052 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1053 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1054 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1055 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1056 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1057 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1064 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1065 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1066 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1067 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1068 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1069 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 106A : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 106B : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 27DC : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1091 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1092 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1093 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1094 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1095 : Intel(R) PRO/100 Adapter$ 
PCI-TAG = 8086 1029 : Intel(R) PRO/100 M Mobile Connection$ 
PCI-TAG = 8086 1059 : Intel(R) PRO/100 M Mobile Connection$ 
PCI-TAG = 8086 1031 : Intel(R) PRO/100 VE Network Connection$ 
PCI-TAG = 8086 1032 : Intel(R) PRO/100 VE Network Connection$ 
PCI-TAG = 8086 1033 : Intel(R) PRO/100 VE Network Connection$ 
PCI-TAG = 8086 1034 : Intel(R) PRO/100 VE Network Connection$ 
PCI-TAG = 8086 1035 : Intel(R) PRO/100 VE Network Connection$ 
PCI-TAG = 8086 1036 : Intel(R) PRO/100 VE Network Connection$ 
PCI-TAG = 8086 1038 : Intel(R) PRO/100 VE Network Connection$ 
PCI-TAG = 8086 1039 : Intel(R) PRO/100 VE Network Connection$ 
PCI-TAG = 8086 103A : Intel(R) PRO/100 VE Network Connection$ 
PCI-TAG = 8086 103B : Intel(R) PRO/100 VM Network Connection$ 
PCI-TAG = 8086 1229 : Intel(R) 82557 Based Adapter$ 
PCI-TAG = 8086 2449 : Intel(R) PRO/100E Adapter$

If you updated the Intel Pro 1000 driver go to the directory: C:Documents And SettingsAll UsersApplication DataSymantecGhostTemplateIntel Pro 1000 (some directories might be hidden) or if you added a template replace the last directory by the template name of the template you added.

Edit the mcassist.cfg and replace all the PCI-TAG lines with the following lines: (these are based on the Intel Prodos 11.2 driver:

PCI-TAG = 8086 1000 : Intel Pro 1000$ 
PCI-TAG = 8086 1001 : Intel Pro 1000$ 
PCI-TAG = 8086 1004 : Intel Pro 1000$ 
PCI-TAG = 8086 1008 : Intel Pro 1000$ 
PCI-TAG = 8086 1009 : Intel Pro 1000$ 
PCI-TAG = 8086 100C : Intel Pro 1000$ 
PCI-TAG = 8086 100D : Intel Pro 1000$ 
PCI-TAG = 8086 100E : Intel Pro 1000$ 
PCI-TAG = 8086 100F : Intel Pro 1000$ 
PCI-TAG = 8086 1010 : Intel Pro 1000$ 
PCI-TAG = 8086 1011 : Intel Pro 1000$ 
PCI-TAG = 8086 1012 : Intel Pro 1000$ 
PCI-TAG = 8086 1013 : Intel Pro 1000$ 
PCI-TAG = 8086 1015 : Intel Pro 1000$ 
PCI-TAG = 8086 1016 : Intel Pro 1000$ 
PCI-TAG = 8086 1017 : Intel Pro 1000$ 
PCI-TAG = 8086 1018 : Intel Pro 1000$ 
PCI-TAG = 8086 1019 : Intel Pro 1000$ 
PCI-TAG = 8086 101D : Intel Pro 1000$ 
PCI-TAG = 8086 101E : Intel Pro 1000$ 
PCI-TAG = 8086 1013 : Intel Pro 1000$ 
PCI-TAG = 8086 1018 : Intel Pro 1000$ 
PCI-TAG = 8086 1019 : Intel Pro 1000$ 
PCI-TAG = 8086 101D : Intel Pro 1000$ 
PCI-TAG = 8086 101E : Intel Pro 1000$ 
PCI-TAG = 8086 1026 : Intel Pro 1000$ 
PCI-TAG = 8086 1027 : Intel Pro 1000$ 
PCI-TAG = 8086 1028 : Intel Pro 1000$ 
PCI-TAG = 8086 1049 : Intel Pro 1000$ 
PCI-TAG = 8086 104A : Intel Pro 1000$ 
PCI-TAG = 8086 104B : Intel Pro 1000$ 
PCI-TAG = 8086 104C : Intel Pro 1000$ 
PCI-TAG = 8086 104D : Intel Pro 1000$ 
PCI-TAG = 8086 105E : Intel Pro 1000$ 
PCI-TAG = 8086 105F : Intel Pro 1000$ 
PCI-TAG = 8086 1060 : Intel Pro 1000$ 
PCI-TAG = 8086 1075 : Intel Pro 1000$ 
PCI-TAG = 8086 1076 : Intel Pro 1000$ 
PCI-TAG = 8086 1077 : Intel Pro 1000$ 
PCI-TAG = 8086 1078 : Intel Pro 1000$ 
PCI-TAG = 8086 1079 : Intel Pro 1000$ 
PCI-TAG = 8086 107A : Intel Pro 1000$ 
PCI-TAG = 8086 107B : Intel Pro 1000$ 
PCI-TAG = 8086 107C : Intel Pro 1000$ 
PCI-TAG = 8086 107D : Intel Pro 1000$ 
PCI-TAG = 8086 107E : Intel Pro 1000$ 
PCI-TAG = 8086 107F : Intel Pro 1000$ 
PCI-TAG = 8086 108A : Intel Pro 1000$ 
PCI-TAG = 8086 108B : Intel Pro 1000$ 
PCI-TAG = 8086 108C : Intel Pro 1000$ 
PCI-TAG = 8086 1097 : Intel Pro 1000$ 
PCI-TAG = 8086 1098 : Intel Pro 1000$ 
PCI-TAG = 8086 109A : Intel Pro 1000$ 
PCI-TAG = 8086 10A4 : Intel Pro 1000$ 
PCI-TAG = 8086 10B5 : Intel Pro 1000$ 
PCI-TAG = 8086 10B9 : Intel Pro 1000$ 
PCI-TAG = 8086 10BA : Intel Pro 1000$ 
PCI-TAG = 8086 10BB : Intel Pro 1000$ 
PCI-TAG = 8086 10BC : Intel Pro 1000$ 
PCI-TAG = 8086 10C4 : Intel Pro 1000$ 
PCI-TAG = 8086 10C5 : Intel Pro 1000$

After you are done editing the files, restart the Ghost Console. Now your Intel or Broadcom chipbased networkcard are getting recognized again!

The great thing about is is that google let you write your own gadgets if you can’t find what you are looking for. Take the hello world example on http://www.google.com/apis/gadgets/docs-home.html and modify it to fit your needs. If want to adjust the height of the plugin take further look in the API… It is really very easy…

I made two gadgets I want to share with you. The first one is a 3FM Live radio stream player (Dutch) I created it because when I start my computer, I do that because I want to figure something out, and don’t want to be bothered by going to a website for webradio (that’s a secondary goal)

The second gadget has something to do with the first one. When you have webradio on a page, you want to keep hearing it after you click on a link on the Google Homepage… Open links in a new window helps with that. As it contains a small javascript that forces the browser to open every link in a new tab/window. Note, after you add it click on the OK link. You can drag and this gadget, but you have to reload the website, because if you don’t, the gadget won’t work.

AdSense works as follows. The Mediapartners-Google spider indexes the site, when visitor now requests one of your pages it will load the external JavaScript from the Google domain. In that JavaScript the text advertise is displayed.

So far so good. An AJAXified page will initially display the AdSense advertise very well (because the pages are backwards compatible). The visitor clicks on a link and now only a part of the page get reloaded, but not the AdSense advertise. Because it’s possible to load an JavaScript into JavaScript, but its not possible to reload JavaScript into JavaScript (for scripts that aren’t build for it).

I suspected that Google had some kind of a refresh function build in where I could specify which URL the currently displayed AJAXified site was. So when you click on an AJAXified link, the Ajax JavaScript calls a Google refresh function. (this is actually how the Google Analytics support works in the AJAX JavaScript)

I was surprised to find out that there was not such a function in the AdSense JavaScript. So I tried to find out how AJAXified sites like Google Maps and GMail works with AdSense. Well, actually, they don’t!

GMail has some uses some AJAX function to display realtime new incoming messages, but the actually displaying of mail goes thru frames and plain old loading of pages! And Google Maps actually doesn’t use AdSense at all… Well, they do, but its parsed into the page and doesn’t use external JavaScript at all, as described above.

I found one workaround by Kevin Cho who used an iframe. In that iframe the AdSense got loaded with the keywords of that page specially dedicated for AdSense for that site. You need to type these manually, which is a hell of a job if you have a lot of pages. And it’s probably against the Program Policies which are very clear about cloaking.

I decided not to implement that workaround because of the Program Policies violation. But I will publish a modified ajax.js that is compatible with AdSense but does not have the enhanced page loading.

With proud I present to you ….. my theme. I finally decided it’s works good enough to be used by others. My theme is based on brajeshwar with some small visual adjustments. The biggest changes are under the hood:

• Instant Search (Gives you results when you type!)
• Instant Comment (Page does not reloaded when you submit your comment)
• Advanced Ajax page loading see My improved website response with Ajax and Solved latency problems with Ajax

All driven by my own build very light weighted framework which I will release hopefully later this week separately with a howto to adapt it to your own WordPress theme.

I released the theme and framework under GPL.
Please the latest version!
Please read the readme.txt before putting it on your site.
AjaxBerlee depends on a modified pagesnav version of Adi Sieker which you can download here

Note: for everyone whole I going to change things in the theme: Please go to line 26 of ajax.php and put // before ClientCache();

This will prevent the browser of displaying and old cached version of the theme (the content of WordPress is in any case up to date!)

TIP: Google Analytics support is build in. Take a look at footer.php:
Remove on line 7 <!— and —>
Remove on line 11 & 13 /* and */
And fill your UA number from Google analytics on line 12.