Update:

I've been using this build for a few hours now.  I did the upgrade as Microsoft suggested - direct from XP SP2.  I did a clean XPwSP2 install with my T40 DVD, before attempting the upgrade.  Took about 1.5-2 hrs on my T40.  ugh.

Anyway - with the exception of a few glitches during setup (very minor, like the SAT not running properly) - all seems good.

Previous builds resulted in a slower computer for me - but this time, my system is running like it did in XP, except now with nice searching features, and a nicer UI.  I still wish my video card worked EXACTLY as it did in XP - there's no real excuse for this, IMO.

So far, so good.  Quite a nice build.

Update 2:

StarCraft works.  Skype works better.  All my programs work, except Daemon-Tools.  And I mean, EVERYTHING.  I've wiped XP off my other partition and I'm using this exclusively.

I still have Windows 2003R2 for testing/development, of course.

Unless there are some serious regressions, build 5536 onwards should be very usable, even for the average joe.  I think it all boils down to the driver support.  There are a few pesky annoyances - but nothing BREAKS, other than the drivers.

Give it a try, if you can.  You shouldn't regret it.  My current install is an UPGRADE from XP SP2, and I'm REALLY impressed.

This is an x86 release ONLY.  An x64 build will not be available.

We are pleased to announce the release of Pre-RC1 build 5536.16385!  This build represents significant progress incorporating your Beta 2 and 5472 feedback.  We ask that you please download, burn and install a copy of this build as soon as possible.  Immediately afterwards we ask that you report any problems you encounter.
Upgrade!
 
If you have the time, please install Windows XP Professional or Home and upgrade.  This is the preferred test path for this build.  If you cannot upgrade from XPSP2 then clean installs or upgrades from Beta 2 X86 are OK too.  Upgrades from any other X86 build are not supported, not of interest to us, and should not be performed.

In general, the order of importance is as follows:
 
1.       Install/upgrade blocking bugs
2.       Stability/Security/Reliability bugs
3.       "Self-host" blockers - issues that prevent you from using the system as a primary OS
4.       Leaks and critical app/device problems
5.       New problems you notice in this build
6.       Regressions / things marked as fixed, but are happening again
7.       ANYTHING with a bluescreen / memory dump!  Even if you aren't sure what you did - bug it anyway.  Please title those bugs with the phrase Bugcheck:  in front of your bug title.
8.       Please focus on bugs that meet the above criteria until Tuesday, August 29th so that we can focus on these most critical issues first.

Direct Microsoft Connect Link to X86 release: (login obviously required)
https://connect.microsoft.com/windows/Downloads/DownloadDetails.aspx?DownloadID=2789

Get Internet Explorer 7 Release Candidate 1

http://www.microsoft.com/windows/ie/downloads/default.mspx

Looking for a wireless router?  Don't just buy a random unit.  Know what to look for:

If you can get ahold of it new, still: any WRT54GS version 1.0 to 3.0.  You can tell from the serial number of the unit; you want prefix (starting with) CGN0, CGN1, CGN2, CGN3, CGN4, or CGN5.  (as per http://en.wikipedia.org/wiki/Wrt54g#Hardware_revisions)  These units all have 8 MB of flash memory with a 200+MHz processor.  Note that units with CGN6 or higher are not upgradeable to 3rd party firmware and therefore not recommended. Buy the more expensive WRTSL54GS (for even more features, like a USB port for a HDD to be shared on the network), or the cheaper WRT54GL, and add on the "Speedbooster" via dd-wrt, or equivalent firmware.

If you can't find these 'older' revisions, get the WRTSL54GS, with S/N prefix CJK0.  This is also a solid looking device.  Canada Computers has this router listed at $119 + tax.  This unit has a USB port on the back, allowing you to put a HDD on the network, stream video, etc.
http://www.canadacomputers.com/index.php?do=ShowProduct&cmd=pd&pid=009794&cid=NT.489

The Asus WL500G Premium is also good, although I haven't personally used any Asus router hardware.  I'd still be tempted to go with a Linksys one, just because I've used their stuff (yes, brand preference - guilty as charged.)  I understand that the Belkin units have lifetime warranty, so the Belkin F5D7230-4 (v1000, v1010, v1111) may also be worth considering.

If you still can't find any of this hardware, consider: (in order)

• Asus WL 500G Deluxe
• Buffalo WHR G54s
• Linksys WRT54GL

I would check up on reviews for all of these products, paying attention to the reception/performance/distance.  I know that the WRT54GS v1-v5 and WRT54GL are very good for range; the WRTSL54GS with only 1 antenna may have distance issues.  Check out http://www.dd-wrt.com/wiki/index.php/Installation#Supported_Devices for some other options.

I'd stay away from N routers until the technology is ready.  I'm all for using the latest stuff - but make sure you don't lose functionality!  Most tested draft-n devices (Netgear, Buffalo, and Linksys) are showing WORSE performance than comparable MIMO pre-n devices.  Go figure.

Of course, these devices I mentioned are the powerful ones.  That means you can load DD-wrt on them.  (http://www.dd-wrt.com/) which, as of v23 SP1, seems quite usable to me.  I don't have any complaints yet.

Bottom line: Tight budget?  Get the WRT54GL.  (Retail at $69 CDN, with a rebate.  Should bring it down to $49 CDN + tax.)  If you can't afford that, then you should probably get some ethernet cable =).
Alternative (cheaper) devices will probably compromise your wireless experience, and will result in constant/frequent disconnects and reboots.  Fun, eh?

I've been doing quite a bit of work (for fun) on getting SNMP monitoring updated to include all my devices attached to the network.  I was using mrtg before, but now I'm upgrading to rrdtool.  Slowly. =)

In particular:

• My WRT54GS (version 1.0) was upgraded to ddwrt for SNMP support.  This took some time to do properly, and for me to test for stability.  It was key that there be no impact on my existing production environment.   (I've been holding out on the retail firmware...)  The latest v23 SP1 was finally deployed on the device today (Aug 17th).
• My Dell PowerConnect 27xx switch is now also supported
  • Via http://www.iqcc.se/ - Nice perl script which collects the RMON data thru the HTTP interface and records it into the rrdtool database (redundant term, but oh well.)  I'm still fiddling with this... =)
  • I also noticed that netmrg has stuff in the SVN tree (http://svn.netmrg.net/trunk/contrib/powerconnect27xx/powerconnect27xx.php) that collects information and logs it.
• Started playing with WMI collection to my Windows servers to collect more information, beyond the NIC information.

I'll post some more details later =).

Some DNS servers - if you know your ISP's DNS servers are causing problems.  Perhaps useful as secondary/tertiary DNS servers?

208.67.222.222
208.67.220.220

Safer = OpenDNS can identify and stop sites trying to phish (steal) your personal information or money.
Faster = Huge DNS caches in Seattle, New Yor, washington DC, and Palo Alto
Smarter = .og becomes .org

The catch = OpenDNS makes money by serving clearly labeled advertisements on search results pages where we cannot resolve your intent (i.e., not a known typo).

System status page = http://208.67.219.60/
Home = http://www.opendns.com/
What we do = http://www.opendns.com/what/
FAQ = http://www.opendns.com/faq/

Revision Information:

Posted August 10th 2006
Updated August 17th 2006

Post:

Samsung X820 GSM Phone

http://www.mobile-review.com/review/samsung-x820-en.shtml

http://www.pcmag.com/article2/0,1895,1993435,00.asp

Continuous talk time: 6 hours 26 minutes
Jbenchmark 1: 1759
Jbenchmark 2: 133
Jbenchmark 3D HQ: 85

Updates:

Nice keypad, nice size, solid feeling case.  Like all the reviews you find out there: nice phone.  The larger D820 may be better for more battery life.  Nice camera quality.

Only complaints: battery life isn't fantastic, but you know what you're getting into.  Reception isn't any WORSE than the Nokia that was in use before, but it is certainly not any better.  Kinda hoped it would be.

Having used one of these devices for the past 2 days for testing/setup and for deployment, I have made several discoveries:

• Hardware
  • The keys on this device are horrible.  The two buttons under the screen (used for Done/Cancel, etc. as part of the menu/navigation) are horribly shaped, with uneven activation points.  I frequently had issues pressing these buttons, and had to relocate my thumb/finger back where the "dot" is on the button.  Why doesn't the WHOLE button surface work?
  • The spacebar is also flaky and makes a cheap clicking noise when gently tapped.  Having used it, I also discovered a similar problem: the button's activation area is biased to the right, and there is a rather large percentage of the space button which does not function.
  • The screen is surprisingly bright and readable.  Given the resolution of similar (and previously deployed) devices, I must say this one allowed me to read emails rather nicely.  It was readable under most conditions I've subjected it to, even in bright sunlight.
  • The scroll button on the right is very poor.  It skips over items frequently, and didn't allow as fine/granular control as I have come to expect from these devices.
  • The overall casing (and the battery cover, in particular) is inferior to Samsung's X820's glass fibre casing.  This MotoQ made me wince; the casing feels cheap and well... like plastic that's going to break.
  • While we're on the topic of recent hardware: the Samsung's X820's body is far surperior.  Ignoring the fact that these two devices are not in the same class, that device's buttons are far more solid, and that suggests that this MotoQ is not properly constructed.  It's possible to make quality plastic casing, and it's possible to have a body that feels solid.  And the X820 is about 1/3 the thickness of this MotoQ.  Enough said.
  • The device charges when plugged into USB.  And it can start routing over USB/computer's internet.
• Software
  • Cool.  I can walk around with my email and contacts now.  And my phone uses the SAME contact list.  No duplication of information.
  • The UI needs more work.  The "back" arrow is inconsistently used; it can usually be used to "go back" but this is NOT always the case.  You have to resort back to the "cancel" button under the screen sometimes to get out of certain screens.
  • Exchange ActiveSync was a breeze to setup - just needed the Telus root cert. update, and then to install my root cert issued from LiteSSL.  Took about 30 mins to discover this due to the poor documentation, but now takes ~30s to deploy a unit.
  • Dialing a number does a direct lookup on your synchronized contact list, as you're typing the number.  This is nice.
  • The device seems slow.  Slow to start up, slow to do look ups on your contact list (what's with the LAG as I'm typing a phone number in?!) and slow to shut down.  Put the Telus startup screens away, please... or give us the option to turn it off!
  • For up-to-the-minute synchronization, this phone relies on SMS messaging; the heartbeat as part of Exchange 2003 SP2 is obviously not implemented on this device.  Ugh.

In general, not bad.  I've been avoiding these devices for a number of reasons, one of which was that I didn't feel the technology was mature enough.  While I'd need more time to make a more thorough analysis, I can say:

• These devices are addictive and not good for human health.  You don't need to check email while you're eating dinner.
• If you must, Smartphones at least saves you pain, compared to the Blackberry devices; emails that you send on this thing are synched to your Exchange mailbox.  Inbox is synched.
• Smartphones are better than a Blackberry in my book, but I'm not sure the MotoQ is the way to go due to the substandard hardware.  What (a) junky keyboard/buttons!
• The latest SmartPhones (or Palm Treo/Active-Sync COMPATIBLE devices) are good for the mobile professional who needs to check his email while on the go.
• The phone is nice; the dream of not having to re-enter/synchronize contacts on your phone/computer/PDA is now a reality, given that you have the infrastructure (Exchange, and tech support) to keep you going.
• This MotoQ is not worth the money; it's far too flimsy/cheap/clicky feeling, and I think the hardware needs a bit more work.
• Telus Mobility offers close to no support on these units when deployed against an Exchange server.  Wake up people.  That's what people use them for.  Time to get some Microsoft PSS involvement?
• Microsoft ActiveSync 4.2 kicks ass on the desktop.  The RIM Desktop Redirector is a piece of junk.
• Did I mention the keys feel really gross?

Telus Mobility MotoQ and ActiveSync Against Exchange 2003 SP2.  How do you get ActiveSync to work!?

Place the following 4 files in /Storage on the device:

secpolicies.cab from http://direct.motorola.com/ENG/q-certificate-patch.asp?Country=CND&language=ENS&productid=30546

VZW_SpAddCert.exe from http://support.microsoft.com/kb/841060 via http://motorola.custhelp.com/cgi-bin/motorola.cfg/php/enduser/std_adp.php?p_faqid=12932&p_topview=1

Your root certificate .cer file, packaged into CAB format, via http://blogs.msdn.com/windowsmobile/archive/2006/01/28/making_a_root_cert_cab_file.aspx

Same root certificate, in simple .CER format.

Run secpolicies, then the packaged CAB, then use the VZW... utility to import all your root certificates as well.  Reboot as instructed.

Server side changes:

If you have a single Exchange 2003 server, http://support.microsoft.com/kb/817379/.  I followed these ripped off instructions: http://www.petri.co.il/problems_with_forms_based_authentication_and_ssl_in_activesync.htm

Ensure ISA server doesn't block the new directory you created, and that it publishes it correctly.

Next, go into Exchange System Manager and ensure Push is enabled.  (General, Global Settings, Mobile Settings, Properties, and check off all applicable boxes.)  Ensure also that the user is permitted to access these functions.

HTTP and HTTPS access is necessary to directories - read the access path details CAREFULLY and see also http://msexchangeteam.com/archive/2006/04/03/424028.aspx .

Revision Information

Originally posted August 14th 2006
Updated August 17th 2006

Product Information

Delivering an average of 35mbps of encrypted throughput.

Earlier powerline networking gear had a reputation for being susceptible to interference from household appliances, but when I turned on a microwave oven between the connection points, it was the Wi-Fi connection that dived _ to a third of its previous speed _ while the HDX101 (NetGear) held steady.

Source:
http://www.washingtonpost.com/wp-dyn/content/article/2006/08/09/AR2006080901146.html
More reviews will be linked soon.

Purchase: 
http://www.insight.ca/apps/productpresentation/index.php?alert=categoryresults&product_id=NGJ89245

Product page: http://www.netgear.com/Products/BridgesAccessPointsandExtenders/PowerlineWallPluggedExtenders/HDX101.aspx

Update 1 - August 17th 2006:

The product arrived DOA yesterday.  One of the adapters failed to function.  Contacted the retailer (insight.ca) and contacted Netgear directly.

Called Netgear today - got case looked at over the phone.  My first call disconnected while I was on hold.  Hung up, called again.  Opened case again, asked details again, and asked to explain failure, despite my opened ticket.  I was then asked, "How many network jacks do you have at the back of this product?".

After being escalated twice, I was transferred to the RMA department, who gave me an RMA number.

I then called my retailer back, and provided them with this RMA number.  We'll see what happens now.  The details (and all the dirty work) has been done; I hope Insight gets this fixed.

Update 2 - August 25th 2006:

Got my replacement adapters.  The defective units were shipped back earlier this week.

I'll do some throughput tests this weekend.

Update 3 - August 26th 2006:

Very nice.  I tried these two units in several scenarios, and two of them are worth mentioning.

a) I tried two units across a phase change in the power.  I tried one unit in the main patch panel, and the other across a 220V, plugged into a jack on a separate panel.
Result: I got a sustained transfer of about 3kb/s, with an average of 11kb/s, maxed out at 70kb/s.  (The speed quickly drops down after an initial burst.)  Useless.  I would recommend a carrier pigeon instead.

b) The second scenario worth mentioning in with the two units plugged into the same board, on separate fuses.
Result: I just transferred 338.33 mB in 2 minutes, 37 seconds.  Average transfer rate 2.15 mB/sec, with maximum speed of 3.49 mB/sec.

Well... it relieves my already overloaded wireless network! =)

Post Revisions

• Posted February 28th 2006
• Updated August 14th 2006

Links

• 10 Security Tips: Defend Your Code with Top Ten Security Tips Every Developer Must Know
• Secure Coding Guidelines for the .NET Framework
• Designing Application-Managed Authorization
• Using the Strsafe.h Functions
• XSS, Cookies, and Session ID (added August 14th 2006)

More: http://msdn.microsoft.com/security/securecode/default.aspx

Insecure
void DoSomething(char *cBuffSrc, DWORD cbBuffSrc) {
    char cBuffDest[32];
    memcpy(cBuffDest,cBuffSrc,cbBuffSrc);
}

Secure
void DoSomething(char *cBuffSrc, DWORD cbBuffSrc) {
    const DWORD cbBuffDest = 32;
    char cBuffDest[cbBuffDest];
#ifdef _DEBUG
    memset(cBuffDest, 0x33, cbBuffSrc);
#endif
    memcpy(cBuffDest, cBuffSrc, min(cbBuffDest, cbBuffSrc));
}

Need to verify DNS and MX records, and SMTP functionality?
CheckDNS.net - A very useful service to check your domain, DNS, Mail and Webservers

http://www.checkdns.net/quickcheck.aspx?domain=justinho.com&detailed=1

http://www.dnsreport.com/

Free wireless hotspot packages

Booted a system, trying to install Windows 2003 R2 Server.
It hung at, "Setup is loading Windows..." during textmode setup.
This is after it installs all the drivers for the system and is about to prompt for additional information.

Found some stuff in the MSKB; quite the vague KB article:
http://support.microsoft.com/?kbid=234772 (Windows 2000)
Other instances of this article exist - addressing different OSes.

In this case, the drivers for my Adaptec 1210SA HostRAID card (2 port) was the problem.  Only when the driver was loaded did the system freeze.

Rolling back to build 10 of the driver resolved the problem.  Strangely the WHQL signed failed to work!

Error

Joining a brand new Windows 2003 R2 Server to an existing Windows 2003 Active Directory domain generates errors (via dcpromo).

"The version of the Active Directory schema of the source forest is not compatible with the version of Active Directory on this computer."

dcpromo claims that "the forest is not prepared for installing Windows Server 2003." and you're told to run the "Adprep command-line tool to prepare both the forest and the domain."

Solution

What is this silly dialog box talking about?  You are running Windows 2003 Server.  But not R2. =)

Windows 2003 Server R2 contains additional schema updates/extensions that must be applied before an R2 server can become a DC.

Pop the 2nd R2 disc into an active domain controller, and journey into \CMPNENTS\R2\ADPREP.  Run adprep /forestprep and/or /domainprep again, from this updated source.

Useless (obscure/unclear/vague) error messages, anyone?

From F-Secure:
Centrino is not just a processor, it integrates WLAN and other features for laptops. The vulnerabilities are not related to the processor itself but to the wireless features.

The vulnerabilities are pretty awful. Worst of them "could potentially be exploited by attackers within range of the Wi-Fi station to execute arbitrary code on the target system with kernel-level privileges". So at least in theory, somebody could write a WLAN virus that would jump from one laptop to another if the laptops are too close to each other.

Patch now.

IBM/ThinkPad users - Run software installer and get the latest software patches now.
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4ZKMCT

Otherwise, grab this ridiculous 129 MB installer file here, from Intel: http://support.intel.com/support/wireless/wlan/sb/CS-023065.htm