Slashdot Mirror

Does that mean you're going to buy a Zune?

Nothing at all.

Listening to shared music was a feature of Microsoft's P2P experiment, "threedegrees" [as in three degrees of separation.]

Windows Home Server products will be available from HP and others along about September. Includes a free {or vanity plate] Windows Live! address. Free SDK to develop your own home server apps available now.

Windows Home Server

The rules are really quite simple. You want to be an internet radio broadcaster or an internet music distributer? Then get the appropriate license. You want a risk-free download? Go to a known-good source like iTunes.

iss Screen Capture

BOOT: Couldn't find NTLDR

LI

Error Occurred(0)

DISK BOOT FAILURE: INSERT SYSTEM DISK AND PRESS ENTER.

i could see this being useful in CRM software...

Seriously. Morons like you HARM the Open Source movement more than help it

You are right and I wish people would not typecast me or the rest of the open source community to kids like this.

People who use a GNU/Linux system excursively almost never talk about Microsoft unless its Linux related and when it is Linux related then it is usually Microsoft saying some BS so all you hear is pissed off Linux users that Microsoft are Trolling.

Welcome to /. where false information can sadly get you a +5 informative moderation.

WoW has always been multithreaded on both Mac and PC. It was only with the 2.0.1 patch that Multithreaded OpenGL support was added, and then only to the Intel Mac client. There is no Direct3D equivalent, and from this technote, likely no equivalent from DirectX 9.

It is true that the PC version is faster than the Mac version on similar hardware in certain situations. Most of these involve video driver issues; think Vista driver problems but with the video card companies in less of a rush to get better drivers out.

Go here for some more video information by both blues and greens.

I think Linus is right and you are wrong on Java:

1. Sun still retains "control" over Java-the-platform through the JSR/committee process. GPL'ing the reference implementation doesn't affect their control of the trademark.

2. The Microsoft lawsuit was settled for a LONG time before Sun started talking seriously about GPL. In the meantime MS was committed to .Net and won't touch Java with a ten-foot pole.

3. The 'it factor' was in danger of permanently moving away from Java. F/OSS was picking up Mono, Ruby, and Python instead.

4. Once Kaffe/Sabre/Classpath/etc. were about to run Eclipse, Sun got very serious about GPL'ing the JDK.

Java's reputation as "the new COBOL" was turning it into a platform that pays the bills but is otherwise very uninteresting.

Well MS did this with the 360 and XNA Game Studio Express. http://msdn2.microsoft.com/en-us/directx/aa937794. aspx

Only alchemists and very poor cooks feel the need to have secret recipes. Look how little mark they leave on the world.

You mean like Sir Isaac Newton?

People can have all the benefits of open source code in their closed source products, they just need to stay away from the stinkin' communists who fly to Communist enemies of the free world and write wierd songs about their trips there while brainwashing the youth of America to give up the competitive advantage that their forefathers faught and severely died for to be used by a country with a population three times larger than ours, further empowering our modern day robber barons to ruin the lives of all of generations of Americans to come. Take what you want and tell the Communist or Self-Serving foreign open source people to S.T.F.U.

Where are you pulling you $1 billion a month figure from?

From Microsoft. They spent 2,191,000,000 in three months according to the quarterly report filed September 30, 2006. More recent reports have more and that's what I remember, nearly a billion dollars a month in sales and marketing. Spending more on marketing than anything else! That's insane unless you are selling carbonated sugar water.

All M$ reports are kind of slushy. The sited report has a strange 1.6 billion for "cost of revenue" and a further 1.8 billion in "research", much of which we can assume lands in "get the facts" reports. It sure did not put new features into Vista.

I wonder what the PA police would make of Gordon Bell http://en.wikipedia.org/wiki/Gordon_Bell/ and the MyLifeBits project http://research.microsoft.com/barc/mediapresence/M yLifeBits.aspx/?

*i am laughing at you*

http://java.sun.com/javame/reference/apis.jsp
http://www.microsoft.com/downloads/details.aspx?fa milyid=83A52AF2-F524-4EC5-9155-717CBE5D25ED&displa ylang=en
http://www.access-company.com/developers/downloads /palmostools.html

You say a couple small apps you wrote, so you must be familiar with an SDK. Where have you seen that code you write on one SDK won't work in ANOTHER COUNTRY! Where did you the the PalmOS and Windows Mobile and J2ME came from?

You do not need to install Windows Desktop Search to search in Outlook 2007 in XP. In fact, I opted against it and unticked the checkbox for it to stop asking me.

You can still use the traditional Advanced Find by visiting the Tools Menu -> Instant Search -> Advanced Find, or CTRL-SHIFT-F, or probably a whole pile of context menus.

They might not be. Safari in windows probably uses win-specific APIs and resources, e.g. common dialog items such as open/save dialog, progress bar, scroll bars, input fields. you know, things like these here: http://msdn2.microsoft.com/en-us/library/ms646829. aspx
All these by default have open holes in them unless the programmers explicitly sanitize user input, keep track of memory, etc. instead of assuming the OS will handle all these.

Over 90% of script kiddes/coders have no idea that the example code they copy/paste gives up security for the sake of simplicity and is not meant to be used as production code. (And no, these are not windows-specific; you used to be able to get root shell from MacOS X.2 login window by typing a 4097-character-long username [place your mug on your keyboard and come back in a few mins at high keyboard repeat rate])

I've seen the list of key Vista features

Vista

I'd say Microsoft's list doesn't have much substance.

Leopard

Here's one: http://windowsupdate.microsoft.com/

I'm fairly certain that when I upgrade to the Ultimate version that it will cost more than $129.

If you applied the same demented logic to Windows, the "Ultimate" version with "server niceities" would cost you...well, hell, I don't know. You try to figure it out.

It is true that when people say "Open Source" they are primarily thinking of GPL'd code. There are other Open Source licenses and the BSD license may be what you're looking for if you want to use other people's code without giving anything back. I wouldn't call that "helping" however.

If you write code that links to GPL'd code you must release that code under the GPL but if your code does not link to GPL'd code you can keep it proprietary if you wish. Further, if you want to link to something like the KDE libraries which are released under the GPL you can still purchase a license from Troll Tech (the copyright owners) that will allow you to keep the code base closed.

I know people developing code using Mono which is a Linux implementation of some of the ECMA/ISO standards that Microsoft uses in its .NET technologies. Mono allows them to keep their source closed.

So there are ways to develop programs that run on Linux without opening your source. If you don't want to give back code then don't extend GPL'd code.

I have seen this one. It's actually a lot easier to use then the more traditional version.
Microsoft Research made the one based on cats. You can find it here: http://research.microsoft.com/asirra/
The hot or not version is just cooler.

Microsoft researchers have developed an alternative captcha that asks Internet users to view nine images of household pets and then select just the cats or the dogs.

Yes, congratulations. However, they are building on years of effort by the Kindergarten to 12th grade Linux project, and other such projects. The K12Linux Project was originally started for the Multnomah County Education Service District, using hardware donated by Intel. (Intel does some of its processor design in a big facility which is also in Portland, Oregon, USA.)

Perhaps 8 years ago, one of the founders of the K12Linux project told me that the total cost of maintenance of Linux was less than half that of Windows. (He gave a figure much less than half, but I don't remember the actual figure.)

My experience with Windows is that it is sloppily coded, and lots of things cause Windows to need maintenance. For example, the CPU hogging bug in Firefox, which seems to be worse in Firefox version 2.0.0.4, sometimes causes Windows XP Professional SP2 to become unstable and require re-starting the computer. When Firefox hogs the CPU under Linux, it is only necessary to kill Firefox. Linux remains stable.

If Microsoft paid schools $100 per copy to take Windows, the cost of Windows would still be far higher than K12Linux.

The K12Linux Project home page gives links to other Linux-in-schools projects, also.

A side benefit of Linux is that it is much more secure, partly because of its design, and partly because students are less likely to know how to tinker with it, I was told.

It is far easier to maintain a terminal server with numerous simple terminals, than separate stand-alone computers, too, and Linux is fast enough to be used that way.

I feel a little uncomfortable with what I said above, because I am vastly understating the savings of using Linux rather than Windows. Microsoft can't even make "Microsoft Genuine Advantage" work correctly; that is a GENUINE disadvantage of Windows. (I am using the word "genuine" in its honest sense, not in its abusive public relations spin sense.)

Another problem with a Windows system is hiring people who are willing to work with products from a company such as Microsoft that is so abusive. It's tiring to work with abusiveness.

Again, I still feel uncomfortable because I am understating the case. My company has had considerable trouble with error messages from Windows Update, for example. We've had about 8 different kinds of problems, some of which have required hours to solve. Judging from the many, many complaints on the newsgroup, there seem to be many other kinds of Windows Update problems we haven't had.

People who work in IT sometimes like Microsoft because the sloppy Microsoft products give them more work.

Yes, congratulations. However, they are building on years of effort by the Kindergarten to 12th grade Linux project, and other such projects. The K12Linux Project was originally started for the Multnomah County Education Service District, using hardware donated by Intel. (Intel does some of its processor design in a big facility which is also in Portland, Oregon, USA.)

Perhaps 8 years ago, one of the founders of the K12Linux project told me that the total cost of maintenance of Linux was less than half that of Windows. (He gave a figure much less than half, but I don't remember the actual figure.)

My experience with Windows is that it is sloppily coded, and lots of things cause Windows to need maintenance. For example, the CPU hogging bug in Firefox, which seems to be worse in Firefox version 2.0.0.4, sometimes causes Windows XP Professional SP2 to become unstable and require re-starting the computer. When Firefox hogs the CPU under Linux, it is only necessary to kill Firefox. Linux remains stable.

If Microsoft paid schools $100 per copy to take Windows, the cost of Windows would still be far higher than K12Linux.

The K12Linux Project home page gives links to other Linux-in-schools projects, also.

A side benefit of Linux is that it is much more secure, partly because of its design, and partly because students are less likely to know how to tinker with it, I was told.

It is far easier to maintain a terminal server with numerous simple terminals, than separate stand-alone computers, too, and Linux is fast enough to be used that way.

I feel a little uncomfortable with what I said above, because I am vastly understating the savings of using Linux rather than Windows. Microsoft can't even make "Microsoft Genuine Advantage" work correctly; that is a GENUINE disadvantage of Windows. (I am using the word "genuine" in its honest sense, not in its abusive public relations spin sense.)

Another problem with a Windows system is hiring people who are willing to work with products from a company such as Microsoft that is so abusive. It's tiring to work with abusiveness.

Again, I still feel uncomfortable because I am understating the case. My company has had considerable trouble with error messages from Windows Update, for example. We've had about 8 different kinds of problems, some of which have required hours to solve. Judging from the many, many complaints on the newsgroup, there seem to be many other kinds of Windows Update problems we haven't had.

People who work in IT sometimes like Microsoft because the sloppy Microsoft products give them more work.

Nope, Vista has indexing that is always running. That is why Google is complaining. Are you saying that Google's engineers couldn't figure out how to turn of an indexing service if it could be turned off? The problem is that Vista will always be doing some type of indexing for changed files, new files, etc. If you install Google's desktop search, you are now doing the same job twice which leads to poor performance.

You are thinking of the indexing service that came over from XP. Vista has something called Instant Search that cannot be turned off. It is a "feature" and part of the OS.

Supported in the .NET framework the way mouse events are supported in Cocoa. A little bit of digging seems to provide an answer: up to five mouse buttons are now thus supported, by enumeration, which seems pretty fucking primitive compared to Cocoa's eschewal of enumeration in favor of something more extensible. But maybe I'm not looking in the right place?

As for why it matters, I remember having to simulate mouse buttons in an Exposé clone by setting the trigger as an unused function key, then setting the extra mouse buttons to simulate keypresses in the mouse driver, which is lame but consistent, in its lameness, with PC culture.

I'm not sure what you think really happened, but you've got some of the major facts wrong here.

First, the presentation of VC-1 to SMPTE always hat the explicit goal of standardizing WMV9, and everyone knew it. The working name for it for quite a while was VC-9 in explicit recognition that it was a standardized version of WMV9. WMV9's bitstream was locked down with the Corona launch back in 2001, well before H.264 was complete. If anything, H.264 got more from WMV9, for example the addition of variable block sizes to H.264 High Profile (although just 4x4 and 8x8, not including the 4x8 and 8x4 modes from VC-1). I wasn't at Microsoft at the time, but was part of c24, and saw how all this unfold. You really should go back and research this point - what happened was exactly according to the plan all parties signed onto in the first place. For example:

http://www.microsoft.com/presspass/press/2004/apr0 4/04-19BroadcastOverallNAB04PR.mspx

Sorenson Media licenses our Format SDK for incorporation into their product to make WMV files. There's also good guys, and we cooperate in a number of ways.

We use VC-1 because it was a codec designed to do what we wanted a codec to do :). We certainly support H.264 where appropriate, for example in the Zune (for podcast playback), in the Xbox 360 (file-based playback, and in the HD DVD player), and in the MSTV IPTV solutions.

Having uninstalled Messenger I had to use the command-line utility FSUTIL USN to remove the USN journal in order to get efficient disk fragmentation back on my NTFS pre-formatted disk. http://support.microsoft.com/kb/311724 - use method 2.

For example: better NFS client / serving from Windows server, Office being able to read (not write) ODF, running Linux applications on Windows, stuff like that. Things that help people migrate OFF Linux. There may be a side effect that some things in Linux will work better with MS, but that is a side effect and not intended behavior.

Just as a FYI, Windows Server 2003 R2 has the Services For UNIX component built-in so you don't have to worry about adding them after the fact. NIS schema modifications and NFS client/server components are included. I had to use the actual SFU 3.5 installer since we were using R1 at work and we only installed the NFS server component to allow communication with a HP-UX server. We found out that copying from HP-UX to Windows through NFS was horribly slow (5 gigs took 1.25 hours) but copying in the other direction took far less (10 gigs took 27 min). Supposedly the problem is due to cached writes being disabled in Windows 2003 and the client is responsible for compensating. Luckily our one time use for the application will involve a UNIX to Windows copy (of 300 gigs).

Won't this money-hungry company have to prove intricate knowledge of HOW to solve the security vulnerability? How can you do that effectively with (presumably) closed-source targets? It seems like this is a large task to take on: beating the vendors to the fixes to their security holes.

Now, in the case of holes in open source systems, they may be able to pull off staying ahead of the developers, but c'mon, it's open source-- how can they possibly expect to force people to pay up for patching open source?!?

And won't this put a whole new slant on the bounties for zero-day security holes? Imagine, if patents could force these vulnerable vendors to pay these pirates big dollars for patent compliance just to patch their software, there will suddenly be a HUGE black market for zero-day sploits. That's the last thing the world needs.

IPv6 FAQ

Q. How do I disable IPv6 in Windows Vista and Windows Server 2008?

A. Unlike Windows XP and Windows Server 2003, IPv6 in Windows Vista and Windows Server 2008 cannot be uninstalled. However, you can disable IPv6 in Windows Vista and Windows Server 2008 by doing one of the following:

- In the Network Connections folder, obtain properties on all of your connections and adapters and clear the check box next to the Internet Protocol version 6 (TCP/IPv6) component in the list under This connection uses the following items.

This method disables IPv6 on your LAN interfaces and connections, but does not disable IPv6 on tunnel interfaces or the IPv6 loopback interface.

- Add the following registry value (DWORD type) set to 0xFF:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip6\Parameters\DisabledComponents

This method disables IPv6 on all your LAN interfaces, connections, and tunnel interfaces but does not disable the IPv6 loopback interface. You must restart the computer for this registry value to take effect.

For additional information about the DisabledComponents registry value, see Configuring IPv6 with Windows Vista.

If you disable IPv6, you will not be able to use Windows Meeting Space or any application that relies on the Windows Peer-to-Peer Networking platform or the Teredo transition technology.

Even if the USPTO does, it won't matter:

"... the system takes, on average, seven years to churn out a new patent. The vendor has to have deep pockets so it can pay damages, and your solution has to be simple enough to be explained to a jury."

So,not to be TOO obvious, but ...

1. by the time they patent it, it will be obsolete;
2. if its simple enough to explain to a jury, it may be too simple to patent (patents have to be for non-obvious inventions);
3. looks like free/libre software gets a free ride (target must have deep pockets).

Isn't it funny how one of the biggest patent trolls sounds custom-made as the target.

"You should also consider that ODF's license is written by SUN"

Actually OpenDocument was developed by OASIS and published as an ISO standard. As such Sun, or any other single company don't own it. Microsofts covenant only promises not to sue for certain parts of the covered specification that are convienently not defined in the license. Why it's split up into chunks like this is curious.

"So basically it seems that the licensing issues surrounding ODF and OpenXML are pretty much equivalent"

Essencially what it means is that if you create a completely independent working specification, the do_not_sue covenant don't apply. On the other hand anyone can create their own implementation of ODF from the published specs and the do_not_sue covenant from SUN still applys.

Both yours an Microsofts definition of open standard seems to be different that everyone elses. According to Bruce Perens MS open standards would fail the test.

Fair Enough? (Score:5, Interesting)

But really can you look yourself in the face and say this isn't a battle for commercial gain between Microsoft and Sun/IBM/Google?

The differences between the licensing of OpenXML and ODF is really about hair splitting about the only differences I can discern are, one was written by Microsoft and the other by Sun.

At the moment I would say Microsoft is almost looking like the party that is playing the most fairly. Read this...

http://www.microsoft.com/presspass/press/2007/may0 7/05-20UOFODFPR.mspx?rss_fdn=Press%20Releases

Basically Microsoft are providing ODF support in Office, so where is the corresponding support for OpenXML in OpenOffice and Google's online Office suite?

Yeah, and for a $GRAND, it should pretty much do your laundry for you too.

Uh, its not the like the poor guy is stuck hacking on Office and Windows.

http://research.microsoft.com/research/default.asp x

Microsoft does fund real research just like any other research lab.

AppVerifier will do memory stuff as well as a few other things.

http://technet.microsoft.com/en-us/library/bb45706 3.aspx

Microsoft's Application Verifier is a great tool for diagnosing lots of problems (on Windows mind you) including doing verification on your not overflowing bounds. Best part is you don't even have to change your code or recompile, it does completely run-time diagnostics. http://www.microsoft.com/technet/prodtechnol/windo ws/appcompatibility/appverifier.mspx For the memory validation, every time you allocate memory it'll put it in it's own page with guard pages around it such that if you write past your buffers even by a single byte you'll immmediately AV inside the offending code (rather than crashing later on in some unrelated code or inside the heap manager). Dead simple to use, and has saved me countless hours. A similar tool is the Driver Verifier, which is actually included with most releases of Windows under C:\Windows\System32\verifier.exe. It does essentially the same kinds of things but for drivers, so if you've been getting lots of blue screens with stuff like BAD_POOL_HEADER etc, run verifier, wait a few minutes for the driver to do it's dirty deed, and take a look at the crash dump to see which driver is to blame.

who do i thank for that?

Microsoft, perhaps? I didn't see any popup when I went there, but then I'm also using Firefox.

Perhaps not so easily obtained if your computer is down or what you need is the known-good set of drivers that shipped with your OEM Dell.

I would begin with the vendor: lost dell windows recovery cd [May 26, 2007]

Monad -> Windows PowerShell, and has been available for ages.

> what fucking rock were they hiding under?

This one

Microsoft publishes a list of trademarks. As you guessed, Windows is a registered trademark and Windows Vista is considered a trademark.

Following MS tools are absolutely free:
- Use umdh that is a part of the Debugging tools for windows to track memory leaks. http://www.microsoft.com/whdc/devtools/debugging/i nstallx86.mspx. Following article explains how to use it http://support.microsoft.com/kb/268343/en-us.
- Whatever you do make sure you have proper symbols. Following article explains how to get symbols from MS symbol server. http://www.microsoft.com/whdc/devtools/debugging/d ebugstart.mspx
- Use paged heap to track all other issue like memory overruns, double free and all other sorts of heap corruption. http://www.microsoft.com/technet/prodtechnol/windo ws/appcompatibility/appverifier.mspx
- Please note that if you run you application with app verifier checks on you need to run it under a debugger. I would strongly suggest windbg or cdb instead of visual studio because it has extensions that would greatly help you to track down the issue ("!analyze -v" "!avrf" "!heap -p -a "). For more details see windbg help. If your application is a service then you might consider running your machine under kd, which would trap all unhandled exceptions and application verifier reports.
- Following link has a very good windbg tutorial http://www.codeproject.com/debug/windbg_part1.asp.
That is all you need to debug any kind of heap issues.

Following MS tools are absolutely free:
- Use umdh that is a part of the Debugging tools for windows to track memory leaks. http://www.microsoft.com/whdc/devtools/debugging/i nstallx86.mspx. Following article explains how to use it http://support.microsoft.com/kb/268343/en-us.
- Whatever you do make sure you have proper symbols. Following article explains how to get symbols from MS symbol server. http://www.microsoft.com/whdc/devtools/debugging/d ebugstart.mspx
- Use paged heap to track all other issue like memory overruns, double free and all other sorts of heap corruption. http://www.microsoft.com/technet/prodtechnol/windo ws/appcompatibility/appverifier.mspx
- Please note that if you run you application with app verifier checks on you need to run it under a debugger. I would strongly suggest windbg or cdb instead of visual studio because it has extensions that would greatly help you to track down the issue ("!analyze -v" "!avrf" "!heap -p -a "). For more details see windbg help. If your application is a service then you might consider running your machine under kd, which would trap all unhandled exceptions and application verifier reports.
- Following link has a very good windbg tutorial http://www.codeproject.com/debug/windbg_part1.asp.
That is all you need to debug any kind of heap issues.

Following MS tools are absolutely free:
- Use umdh that is a part of the Debugging tools for windows to track memory leaks. http://www.microsoft.com/whdc/devtools/debugging/i nstallx86.mspx. Following article explains how to use it http://support.microsoft.com/kb/268343/en-us.
- Whatever you do make sure you have proper symbols. Following article explains how to get symbols from MS symbol server. http://www.microsoft.com/whdc/devtools/debugging/d ebugstart.mspx
- Use paged heap to track all other issue like memory overruns, double free and all other sorts of heap corruption. http://www.microsoft.com/technet/prodtechnol/windo ws/appcompatibility/appverifier.mspx
- Please note that if you run you application with app verifier checks on you need to run it under a debugger. I would strongly suggest windbg or cdb instead of visual studio because it has extensions that would greatly help you to track down the issue ("!analyze -v" "!avrf" "!heap -p -a "). For more details see windbg help. If your application is a service then you might consider running your machine under kd, which would trap all unhandled exceptions and application verifier reports.
- Following link has a very good windbg tutorial http://www.codeproject.com/debug/windbg_part1.asp.
That is all you need to debug any kind of heap issues.

Following MS tools are absolutely free:
- Use umdh that is a part of the Debugging tools for windows to track memory leaks. http://www.microsoft.com/whdc/devtools/debugging/i nstallx86.mspx. Following article explains how to use it http://support.microsoft.com/kb/268343/en-us.
- Whatever you do make sure you have proper symbols. Following article explains how to get symbols from MS symbol server. http://www.microsoft.com/whdc/devtools/debugging/d ebugstart.mspx
- Use paged heap to track all other issue like memory overruns, double free and all other sorts of heap corruption. http://www.microsoft.com/technet/prodtechnol/windo ws/appcompatibility/appverifier.mspx
- Please note that if you run you application with app verifier checks on you need to run it under a debugger. I would strongly suggest windbg or cdb instead of visual studio because it has extensions that would greatly help you to track down the issue ("!analyze -v" "!avrf" "!heap -p -a "). For more details see windbg help. If your application is a service then you might consider running your machine under kd, which would trap all unhandled exceptions and application verifier reports.
- Following link has a very good windbg tutorial http://www.codeproject.com/debug/windbg_part1.asp.
That is all you need to debug any kind of heap issues.

Application Verifier comes in x86, ia64 and amd64 flavors.

This tool allows you to enable PageHeap for your process, which is heap corruption detection built into the OS heap implementation. Upon freeing a block of memory, PageHeap will break into your debugger spewing tracing that a block has been corrupted. It can also provide the call stack when the block was allocated. Newer heap validation features are available in progressively more recent OS releases.

Following MS tools are absolutely free:
- Use umdh that is a part of the Debugging tools for windows to track memory leaks. http://www.microsoft.com/whdc/devtools/debugging/i nstallx86.mspx. Following article explains how to use it http://support.microsoft.com/kb/268343/en-us.
- Whatever you do make sure you have proper symbols. Following article explains how to get symbols from MS symbol server. http://www.microsoft.com/whdc/devtools/debugging/d ebugstart.mspx
- Use paged heap to track all other issue like memory overruns, double free and all other sorts of heap corruption. http://www.microsoft.com/technet/prodtechnol/windo ws/appcompatibility/appverifier.mspx
- Please note that if you run you application with app verifier checks on you need to run it under a debugger. I would strongly suggest windbg or cdb instead of visual studio because it has extensions that would greatly help you to track down the issue ("!analyze -v" "!avrf" "!heap -p -a "). For more details see windbg help. If your application is a service then you might consider running your machine under kd, which would trap all unhandled exceptions and application verifier reports.
- Following link has a very good windbg tutorial http://www.codeproject.com/debug/windbg_part1.asp.

That is all you need to debug any kind of heap issues.

Following MS tools are absolutely free:
- Use umdh that is a part of the Debugging tools for windows to track memory leaks. http://www.microsoft.com/whdc/devtools/debugging/i nstallx86.mspx. Following article explains how to use it http://support.microsoft.com/kb/268343/en-us.
- Whatever you do make sure you have proper symbols. Following article explains how to get symbols from MS symbol server. http://www.microsoft.com/whdc/devtools/debugging/d ebugstart.mspx
- Use paged heap to track all other issue like memory overruns, double free and all other sorts of heap corruption. http://www.microsoft.com/technet/prodtechnol/windo ws/appcompatibility/appverifier.mspx
- Please note that if you run you application with app verifier checks on you need to run it under a debugger. I would strongly suggest windbg or cdb instead of visual studio because it has extensions that would greatly help you to track down the issue ("!analyze -v" "!avrf" "!heap -p -a "). For more details see windbg help. If your application is a service then you might consider running your machine under kd, which would trap all unhandled exceptions and application verifier reports.
- Following link has a very good windbg tutorial http://www.codeproject.com/debug/windbg_part1.asp.

That is all you need to debug any kind of heap issues.

Following MS tools are absolutely free:
- Use umdh that is a part of the Debugging tools for windows to track memory leaks. http://www.microsoft.com/whdc/devtools/debugging/i nstallx86.mspx. Following article explains how to use it http://support.microsoft.com/kb/268343/en-us.
- Whatever you do make sure you have proper symbols. Following article explains how to get symbols from MS symbol server. http://www.microsoft.com/whdc/devtools/debugging/d ebugstart.mspx
- Use paged heap to track all other issue like memory overruns, double free and all other sorts of heap corruption. http://www.microsoft.com/technet/prodtechnol/windo ws/appcompatibility/appverifier.mspx
- Please note that if you run you application with app verifier checks on you need to run it under a debugger. I would strongly suggest windbg or cdb instead of visual studio because it has extensions that would greatly help you to track down the issue ("!analyze -v" "!avrf" "!heap -p -a "). For more details see windbg help. If your application is a service then you might consider running your machine under kd, which would trap all unhandled exceptions and application verifier reports.
- Following link has a very good windbg tutorial http://www.codeproject.com/debug/windbg_part1.asp.

That is all you need to debug any kind of heap issues.