Sign in
Microsoft.com
 
Resources for IT Professionals
 
 
 
Resources for IT Professionals > Forums Home > Windows Tools Forums > Network Monitor > How to set temporary capture file size and path with Netmon API?
Ask a questionAsk a question
Search Forums:
 

QuestionHow to set temporary capture file size and path with Netmon API?

  • Wednesday, October 28, 2009 3:28 AMwhossa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Using netmon API to capture traffic, there are a sequence of "roo*.tmp" files produced by netmon in my %TMP% path.

    With netmon UI, I could set that temporary capture File size and path in Tools->Option->Capture tab

    If I'd like to change temporary capture file size and path, how could I do with netmon API? Much thanks!
     

All Replies

  • Wednesday, October 28, 2009 3:46 PMPaul E LongMSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    The location of the temp files is determined by the %temp% environment variable.  The size, is not configurable.  However, the size of the tmp captures files was determined by testing to maximize performance.

    Can you tell me why you'd like to change the temp file size?

    Thanks,

    Paul
     
  • Thursday, October 29, 2009 3:11 AMwhossa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Tnanks for your quick aroud, Paul.
    We're trying use Netmon and find "roo*.tmp" file  increase very fast yet not larger than 20MB, so I'd like to find out if we could ajust the tmp file size.
     
  • Thursday, October 29, 2009 9:56 PMPaul E LongMSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I suppose the number of files is due to your network traffic.  But using the 1 meg size helps us keep up with that fast speed.  Of course, you might get to a point where you will overwhelm the API.  At this point there's no way around that probem.