Microsoft has released Windows Vista build 5536.16385 on Windows Connect only. Microsoft calls this a Pre-RC1 Build. This means that this built will have part of the improvements that will be set for RC1. This build is not available for public download. According to first Experiences:

1. Performance has much improved. Vista now consumes a bit less memory on startup. Applications are more responsive and there are fewer crashes.
2. New Icons are now being used in the Control Panel and MMC; all the old dialog boxes have been removed and replaced with new and more advance ones.
3. Vista installs much more quickly now, accordingly, if you have a very fast machine, it takes only 22 minutes.
4. Lots of issues with drivers have been corrected. Now, all drivers work well with Vista. WDDM drivers also recover gracefully from crashes.
Microsoft has said that in previous builds, performance was not a huge issue, but now, as the RC1 is nearing in, it is. Microsoft admitted that because of the new SDL (Security Development Lifecycle) that they adopted for Vista, they could not lose any more time on Performance issues. Now that all of the codes have been already written, they can concentrate on the performance issues now. Vista build 5536 does promise a great Experience.

Internet Explorer 7 RC1 has also been released. You can get it here:
http://www.microsoft.com/windows/ie/downloads/default.mspx

However, I won’t even have a look at the final version, since I have got Opera.

Dani AI

Generated

A short, practical checklist for anyone testing early Vista releases — complements ’s summary and answers ’s request for more technical detail. These notes focus on making test runs repeatable, capturing the right evidence when things fail, and packaging reports so developers can reproduce issues quickly.

Before you install: make a rollback plan (full disk image or VM snapshot). Use a dedicated test PC for driver and graphics work; VMs are fine for quick compatibility checks. Capture a baseline inventory: exact build string (from winver), BIOS/firmware, and a full driver list. Export system info with msinfo32 and keep a plain-text copy of drivers so you can attach them to bug reports.

When something breaks, collect precise evidence. Save Application and System logs from Event Viewer, preserve any minidumps or kernel dumps, and record exact reproduction steps with timestamps. Use Sysinternals tools (Process Explorer, Process Monitor) to trace hangs and leaks. For driver instability, run verifier.exe selectively to provoke faults that produce useful dumps. For performance work, run the same task several times and record simple counters (CPU, free RAM, disk latency) so you have before/after comparisons.

When filing a report to Microsoft or a vendor include: exact build string, reproduction steps, attached .evtx and .dmp files, driver names/versions and hardware IDs, and whether the test ran on VM or physical hardware. Compress logs into one archive and label files clearly. Final caution: do not run pre‑release code on a primary machine — always test on disposable hardware or under snapshot-protected environments so you can roll back cleanly.

Nice post on Vsita development - Can u post more tech articles on what applications you are planning to implement on Vista since it seems more focused on desktop segment than having real features of a Data center server. Appreciate your time - please write more about your Vista experiements.

Storage Area Networking Job opportunities- interesting blog on Storage area networking jobs http://storage-jobs.blogspot.com

<a href'=http://storage-jobs.blogspot.com/2006/08/storage-job-interview-questions-for.html'> Storage Job interview Questions </a>

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.