في [ويندووس] [فيستا], مستعملات يستطيع يتلقّى واسعة نظامة صحة تقرير تحرّيت يلد ل هم في يساعد أداء وإعتمادية إصدارات على [بك] هم أو أن يرى كيف يصحّ [بك] هم يكون في جنرال. للمستعملة معدّلة, لن يعني هذا على الأرجح أيّ شيء. غير أنّ ل ي, أنا النوع المستعملة أنّ حقّا رغبات يتلقّى القدرة أن يخلق تقارير أنّ يقولني حول [بك] ي لذلك أنا كان حقّا أثرت أن يجد هذا قدرة في [ويندووس] [فيستا].

مساء اليوم قرّر أنا أن يلد تقرير على ي رئيسيّة مكتب [بك] [فور ث فيرست تيم] ورأيت ماذا هو يقول. أن ولد يتلقّى نظامة صحة تقرير:

1. فتحت بداية قائمة الطعام.
2. [ريغت-كليك] على "حاسوب" وطقطقة "خاصية".
3. طقطقت في النظام خاصية نافذة, فوق ك [ويندووس] خبرة فهرسة تقدير.
4. تقدّم في الأداء معلومة وأدوات نافذة, تحت "مهام" في ال [لفت-هند] خيارات لوح طقطقة "أدوات".
5. ولدت تحت أدوات متقدّمة نافذة يختار "نظامة صحة تقرير" في القعر.

يلد التقرير بعد حوالي 60 ثانية من يختبر. هنا ي نظامة صحة تقرير أنا ولدت مساء اليوم:

بما أنّ أنت يستطيع رأيت, عرضت أيّ نوع الأخطاء أو إنذارات لنظامتك

…

اليوم, شقّ يقول أنت حول بعض تحديثات إلى الأدوات في مكروسوفت مكتبيّة تحسين حزمة ([مدوب]) من برشلونة, إسبانيا في [تشد] هو ساحة. أنا مؤخّرا تلقّيت فرصة أن يعطي واحدة من العناصر ال [مدوب] - مكروسوفت تشخيص وإستعادة [توولست] ([درت]) 6.0 - محاولة. [درت] مجموعة ممتازة أدوات ل هو محترفات أن يتحرّى [بكس] [أونرسبونسف] ويزيل حميات و [ملور] من يعدى [بكس] في بيئتهم. يتلقّى [درت] 6.0 أيضا الآن القدرة ل هو محترفات أن يوصل إزالة [أفّلين] من [ملور] وحميات من يعدى [بكس].

The first thing I noticed when I started using DaRT is that it provides two options to the IT Professional: a way to analyze crash files from unresponsive PCs through the Crash Analysis Wizard, and a way to create a startup disc with the necessary tools in fixing an unresponsive PC that is unable to boot into Windows called ERD Commander.

I first took a look at the Crash Analysis Wizard.

The Crash Analysis Wizard allows an IT Professional to take a crash dump file (*.dmp files associated with a system crash) and analyze it and get important bits of information that could

…

Today, Nick told you about some updates to the tools in the Microsoft Desktop Optimization Pack (MDOP) from Barcelona, Spain at TechEd IT Forum. I recently had a chance to give one of the components of MDOP - the Microsoft Diagnostic and Recovery Toolset Read More……(read more)

I recently received the following via email. I responded, but never heard back. Hopefully the information will be of use to others…

Hi, Found your name on the web when I was looking at some stuff on slashdot and I thought maybe you might have a moment to point me in the right direction.
I have a custom app which I have zero access to in terms of the developer. When the app was run on new hardware, a few users would periodically get a bizarre error, but never on their old hardware. Main difference seems to be core 2 duo on the new laptops.
Anyway, this error causes a total reset of the internal windows database system used by the app and then there’s an error in msvcr80.dll. Is there a way I can tell from the data below what routine went bad in that module? I could at least then tell the guy who guards the gates to tell the developer a little bit more. At this point the “guard” is convinced it is just because the dll is not the latest version. I think it is probably not that simple.

[app].exe signature
Appname [app].exe App. Ver. 0.0.0.0

…

(TROUBLESHOOTING) It has been reported that Dreamweaver 8.0 might crash or freeze on some Windows Vista systems while browsing for files. This is caused by Office Groove that bundled with Office 2007 Ultimiate. To resolve this, you simply need to uninstall MS Office Groove. According to Adobe’s website, this issue will be resolved in the next Dreamweaver release (Spring, 2007) since Dreamweaver 8 was released long before the debut of Windows Vista and Office 2007.
Here’s a complete instruction on how to uninstall Office Groove 2007 component within Windows Vista:

(more…)

Previously (here and here), I’ve written about isolating shared services so that they run in their own process, with a specific focus on the Windows Update Automatic Updates Service (wuauserv) that typically runs in the NETSVCS SVCHOST.EXE instance. One thing that can be done once this is accomplished is to lower the priority of the process so that when the service winds up consuming 100% of the CPU, the system doesn’t become unresponsive.

Since we’re dealing with a service, setting the priority of such a SVCHOST.EXE process can become problematic - the service may already be running, or, because it is a service, it is not started as non-service processes are, so one is not able to use START / [LOW NORMAL HIGH REALTIME ABOVENORMAL BELOWNORMAL] to impose a priority when the process starts. One can use a utility like Task Manager or Process Explorer to set the priority of a process on an ad hoc basis, but when the service restarts or the system reboots one has to remember to set the priority again.

Though not an ideal solution the following scripts (VBS using WMI, and PowerShell) can be used to set the

…