Call log error with qmetatype.h?

Similar Questions

• View call logs, but with contact phone numbers, name, and not only

  I have to be able to show that a list of the call connects to my request.  But for thosenumbers who have a name in the address book, instead of simply to view phone numbers, I have to be able to show the name of the

  number.  (just like the native blackberry app call log done)

  Up to now the following seems to work OK, as long as the amount of data is small:

  • When the main screen is first created, walk the database by calling PIM.getInstance () .openPIMList)
  • Adds a new entry in a hash table for each unique telephone number in the database that points to the name of the contact
  • After that the Hashtable is fully charged, list of call logs
  • As the newspapers call list is displayed, phone numbers search in the hash table, replace with name when a match is found

  But when the Contact database grows, as the order of 500 entries, it takes a lot of time for

  walk from the database to generate the hash table (10 seconds), and while what the application is blocked

  and things seem stuck to the user. This must occur before the first screen is displayed and so after

  the user clicks on the icon and the first screen is being built, the user is thinking ' what's going on..?

  until the screen finally opens.

  Is there an API I can tap in which already provides this mapping for me?  (given a call number journal or by phone,

  Efficiently search the name of the contact with that phone number, if necessary).  That way I wouldn't have to build

  the hash table.

  Or, possibly, some advice on a simple signal of progress to the user while loads of app... This might be simpler than

  trying to tackle the problem with a multi-threaded approach.

  Unfortunately there is no way, I was. I tried to re - implement research of the phone application and came across this as well, as well as some other hidden implementations that are much faster then the public APIs.
  You can try to work with itemsByName, it is also not very fast, according to the number of entries you have.

  Maybe PhoneCallLogID methods can help you?

• T500 w Vista hangs light w HDD and event log error iastor with ID 9 (Device\Ide\iaStor0)

  Summary

  Edited: This problem was finally resolved by Intel Matrix Storage Manager driver 8.6.3 sent by Lenovo, January 13, 2009

  It is an intermittent problem on 500/T400 with XP or Vista 32.

  Vista 32: the HARD drive light stays on for several minutes, sometimes never goes. The machine crashes immediately, or it may continue to work for a while sometimes sluggish performance w. In all cases the operating system stops not completely so that the HARD drive light is forcing a hard stop with the keyboard, button on / off.

  XP: random BSOD of iastor.sys.

  In the log window of the events is an event of error each time passed than the HDD light grip. Source is iastor, Id is 9, and the text is "the device, \Device\Ide\iaStor0, did not in the expiration time. See below for a description of how show all events iastor error 9 in your event log.

  The problem has appeared since the second or third week of December. The likely source is an update of the Intel Matrix Storage Manager, driver version 8.6.0 delivered on 4 December.

  This driver has been after December 4, distributed via Thinkvantage System Update. T400/500 made in December were also shipped with this driver installed. Since then, lenovo has withdrawn the driver, drivers, T400 and page software here and the T500 here page now shows the driver for Vista 32 and XP as version 8.2.4.

  The experience is that this problem is solved in the restaurant or by installing the 8.2.4 version of the Intel Matrix Storage Manager driver. If the 8.6.0 driver was installed through system update, go to Device Manager and open the Intel(r) ICH9M-E/M SATA AHCI Controller. On the driver tab, make sure that 8.6.0 is installed, and then click the roll back button.

  If the T400/500 has been shipped with the 8.6.0 driver installed, first driver to download the 8.2.4 and run the extract in the c:\drivers folder. Update driver then choose Device Manager. On the second screen appearing to ensure you choose "Let Me pick from a list of drivers on the computer' - in the case otherwise, he will tell you, best driver is already installed when you click Next. In the next screen, select Intel(r) ICH9M-E/M SATA AHCI Controller and click on "disk" and on the next screen, specify the path c:\drivers\win\imsm.

  PS review iastor in case connection error messages comparing them to the update system install history as follows:

  1. in Control Panel, in administrative tools, open the Windows event log. If this is not the first time, you use the newspaper, you may need to select the local newspaper - the top left - line for the Summary window to open in the Middle, you can maximize this window down.

  2. Select the error line in the Middle window and click Show all instances of this event on the right side. All error events are now listed in the Middle window.

  3. click on filter the current view on the right side. In the new menu, enter 9 in the field of event ID, select ok and then Yes.

  4. you should now have a list of all occurrences of the error in iastor event. Scroll through the list and note the timestamp of the first occurrence of the error.

  5. open Thinkvantage System Update, then select historical spectacle of installation. Scroll the window to the right you see the timestamps. Examine your updates, just before the message in iastor appeared first in your event log.

  __________________________________________________________

  Original entry

  My new T500 a few days after the execution of the first update of the system began to hang once or twice every 24 hours with light on HARD drive and "the device, \Device\Ide\iaStor0, did not in the expiration time" in the registry.

  ,

  iastor is the Intel Matrix Storage Manager (MSM) for their device RAID/AHCI controllers. The Intel AHCI controller listed in as installed for the T500 shows version 8.6.0 Device Manager, which is the current version according to the Intel web site.

  There are zero warnings to disk in the event log errors, I ran the drive diagnostic - the drive is healthy. I don't think that this is a problem of DVD or disc, it's the MSM which is a failure.

  Googling on the MSM error message there is a certain. A batch is since last year and concerns of Intel THAT MSM supporting properly - l/min, this has been fixed in MSM 7.5.0 see http://www.intel.com/support/chipsets/imsm/sb/CS-025783.htm

  A second batch was held earlier this year for Dell laptops that, without looking into the details, seems to have been caused by an incompatibility between the BIOS and the MSM reported. (Update system to update my BIOS to 1.20 - 1, 01).

  Other solutions to this problem found on the web include the removal of iastor/MSM settings in the Windows registry to disable l/min and turn off AHCI in the BIOS.

  It would be nice to be able to verify that this isn't a hard drive problem by disabling the AHCI and therefore the Intel controller. How to do that in T500 BIOS Setup and what are the implications on the performance of my drive (Hitachi 160 GB at 7200 RPM)?

  
  

• Try to buy the trial period in a different e-mail - message error "error in your account order has been registered for another country. Please log out and log in with an existing account for this country. OK ".

  Try to buy the trial period in a different e-mail - message error "error in your account order has been registered for another country. Please log out and log in with an existing account for this country. OK @.

  Hi boags2014,

  Please refer to this link and get to know the alternatives for the same:

  How to complete a purchase when I get an incorrect error 'country '?

  Kind regards

  Ana Maria

• Call log for a small Service providing companies with

  I work for a small company that repairs to the mobile homes. I have been tasked with finding a log of calls to our company and were surprised by the difficulty of a task, this turns out to be! We use Excel for years and we would really like to have a call log that is mobile and can be opened (not as just a 'read only' copy) on up to 4 computers at the same time (but generally only 2 computers). As I researched I found only call logs for cell phones, or for call centers with many fancy features that it is not enough. All we want to enter the call log is the customer's name, address, telephone number, claim #, adjuster, which is why we call, address email, how they heard about us, and the outcome of their appeal. Any suggestions would be welcome!

  Thank you

  Carissa

  [email protected]

  Thank you for the reply, I did briefly search suggestions; but ultimatly found a better fit for our company. I really wish that someone would have suggested it earlier, we now use Google Reader (FREE). We put the last call of the month sign in here and we are all able to access and edit at the same time! We keep it small so it doesn't take too many GB but it's been great! We can have open in several places and can access even on our mobile devices!

• BlackBerry Smartphones Call Log problem - lists only the missed calls

  I have the curve 8900 with t-mobile and I'm having the same exact problem that this user has:

  http://supportforums.BlackBerry.com/Rim/Board/message?board.ID=8900&message.ID=3200

  My call log lists only the missed calls (dialed or received calls). He did this for a few weeks now. I received the error message 'exception: java.lang.NullPointerException eception' a few times as well.

  I checked all available software updates and I use the most recent software.

  Please help me if you can.

  Thank you

  Mike

  I fixed it!  It took about an hour on the phone with t-mobile, but we thought about it.   For me, the problem was probably a few information corrupted in my call history.  I need to delete all the call history, and then it was fine.  To do this, you need to install the blackberry desktop manager on your computer if you have not already (be it from the cd that came with the phone or the Web site).  Open Fund Manager and connect the blackberry to the computer.  Select the backup and restore option.  Then, select the advanced option.  On the right side of the screen, there will be a list of all the features of the phone.  Scroll to phone call logs.  It lists the number of records in the phone.  All I had to do was remove all records from phone call and it was corrected.  Now my lists of newspaper calls dialed, received and missed and I no longer get the error message.  I hope it helps you too!

• IPhone 7 call log missing

  Hi, I noticed for the upgrade of iphone6 that now when I get a missed call that does not appear in the call logging so I have no idea its been missed. How can I get this working again?

  Hi there, ste_richards!

  Thank you for joining the communities Support from Apple! It seems that you are having problems with the app phone on your iPhone. I know how it is important to be sure you see what calls are missed at any time. First of all, don't forget when you look in the phone application when you are in the log of recent calls, choose ' All'. Then, check out this article with the steps to restart your iPad, iPhone or iPod touch.

  The next thing you might want to try going in settings of the iPhone, then the general and reset. Once there, tap reset all settings. This will reset the settings of the iPhone, but does not erase personal information such as pictures, music or contacts. However, it will remove a connection Wi - Fi and VPN settings, so do not forget, you have these settings and passwords ready for iPhone upward starting.

  If this does not work, it would be a good idea to make sure that there is not a problem of software as the cause of this for you.

  1. Read this article to know the steps for backing up your iPhone, iPad, and iPod touch.
  2. Use this article for steps to use iTunes on your Mac or PC to restore the iPhone, iPad or iPod to factory settings.
  3. Once this done, set the phone like new and the phone to see if the issue is still being tested. Follow this link to restore your iPhone, iPad or iPod touch from a backup

  See you soon!

• After installing iOS 9.3.3 two iphones on the same apple ID are evidence of the other device call log.

  I use two iphones on the same apple ID. After installing ios 9.3.3 two iphones show the other call log also. In my view, that is a bug in ios9.3.3, because this problem started after the new ios.

  No this is by design, and it was not introduced with 9.3.3 much earlier

• Satellite L350-214 - error with the software Reeltime

  Hello

  I have a Satellite L350-214 with Windows 7 Pro and have encountered an error with the software Reeltime, I uninstalled and reinstalled and still get the error below. Any help or assistance would be great

  Tony Miller

  Log name: Application
  Source: Windows Error Reporting
  Date: 2010-11-30 12:27:58
  Event ID: 1001
  Task category: no
  Level: Information
  Keywords: Classic
  User: n/a
  Computer: Tony-TOSH
  Description:
  Fault bucket 1223018385, type 5
  Event name: CLR20r3
  Answer: No available
  Cabin ID: 0
  Signature of the problem:
  P1: tosreeltime.exe
  P2: 1.0.0.0
  P3: 4a769d0e
  P4: WindowsBase
  P5: 3.0.0.0
  P6: 4b5950b7
  P7: a86
  P8: 18
  P9: System.InvalidOperationException
  P10:
  Attached files:
  C:\Users\Tony\AppData\Local\Temp\WER7C9E.tmp.WERIn ternalMetadata.xml
  These files are available here:
  C:\Users\Tony\AppData\Local\Microsoft\Windows\WER\ ReportArchive\AppCrash_tosreeltime.exe_25c5a6496c7 ad44943ce88637e3389e8a80bd45_07f0c745
  Symbol of the analysis:
  Recheck for solution: 0
  Report ID: d5b71327-fc74-11df-a596-00266c333aed
  State: 0
  The event XML:
  
  
  
  1001
  4
  0
  0 x 80000000000000
  
  37886
  Application
  Tony-TOSH
  
  
  
  1223018385
  5
  CLR20r3
  Not available
  0
  tosreeltime.exe
  1.0.0.0
  4a769d0e
  WindowsBase
  3.0.0.0
  4b5950b7
  A86
  18
  System.InvalidOperationException
  
  
  
  C:\Users\Tony\AppData\Local\Temp\WER7C9E.tmp.WERIn ternalMetadata.xml
  C:\Users\Tony\AppData\Local\Microsoft\Window s\WER\ReportArchive\AppCrash_tosreeltime.exe_25c5a 6496c7ad44943ce88637e3389e8a80bd45_07f0c745
  
  
  0
  d5b71327-fc74-11df-A596-00266c333aed
  0
  
  
  My system specs

  Hey,.

  If you get this error Reeltime, you should try Ccleaner. There may be a registry problem and CCleaner might solve this problem. This great freeware and easy tool which you can download here:
  http://www.Piriform.com/

  Check this box!

• iPhone more outgoing 6s "Call Failed" error - network Airtel

  Recently, I brought the iPhone 6 s more than the United States and use it in India Airtel network. Since the last 1 week or two, I guess that since the time he had an update iOS 9.2.1 I started to have this "Call Failed" error whenever I tried to make outgoing calls. This happens all the time, but sometimes only. When it happens that he does not make outgoing calls for at least an hour or more. Ultimately some how outgoing calls start working again on its own sometimes and sometimes it starts to work 10 minutes after the function "reset all settings". I checked with Airtel carrier several times and they have confirmed that no problem with the network. I put Airtel myself another SIM card in the iPhone, and even this sim did not work during down time. At the same time, I put my sim card into another Android phone, and it works perfectly without a sim card. This leads me to believe that there is a problem with the hardware/software phone itself and not any problem with the carrier. Anyone had any permanent resolution of these intermittent failures?

  Try resetting your device. This will not erase your data stored on that device.

  • Press and hold the sleep/wake button
  • Press and hold the Home button
  • Press and hold both buttons until the display turns off and on again with the Apple logo on the subject.

  Alternatively, you can go to settings - general - reset - Reset all settings

  Restore your device to factory settings. Please note that this will delete the data on your device.

  Take a look this Apple Support article: use iTunes to restore the iPhone, iPad or iPod to factory settings - Apple Support.

  If these steps do not work, contact Apple and ask for help. Maybe it's a hardware problem.

  https://www.Apple.com/support/iPhone/contact/

• The call log is displayed on another phone

  Phone call made on 5 phone to appear in the 4S another phone call log

  1 stop sharing with Apple ID

  2 settings > phone > application to other devices > make sure that the iPhone 4S is not listed

  Even with Messages & FaceTime

• Call dll error 1097

  Hello

  I'm reading the data from a capture card in my slot PCIe card. When I call the "Initialize" function from the .dll file that I got with the card, I always get error 1097. 1097 means that the called function threw an error. When I run the program supplied with the acquisition card, the acquisition card still works.

  If I have everything just omit the "initialize" function call and continue with the function that will be called after the "Initialize" function, LabVIEW block (program stops without any warning).

  I also had a LabVIEW program that uses the dll that was supposed to work. But here I get the same error.

  Do you have any idea what normally causes this behavior and how can I solve this problem?

  I have the second post of nathans. 1097 error is almost always an error in the configuration of the right to call library node. And in some cases, there is no right to set up and you need a wrapper DLL to convert between what the library node call allows and what needs your DLL. The reason why it works sometimes and other times not, actually is that it never really works, but sometimes the error that gets caused cannot be detected by the operating system and LabVIEW does not get an exception according to. This can change according to LAbVIEW version, runtime system or development and even recompilation of the code after the small seemingly unrelated changes in demand.

• The K910 - VibeUI 2.0 call log problem

  It's maybe something ridiculously simple, but still... I can't understand:

  For some reason when I place a call OUTGOING, and the other side picks it up, the event is held as 'UNKNOWN' in the call log - I can see the duration of the call, but cannot see the actual number I composed. No matter if the number dialled is part of my address book or is a random number - if it is connected, it is still 'UNKNOWN '.

  Interesting - in composition, it's all good, when the other side picks up and the Timer (timer), I see the appearance of 'UNKNOWN'. Really strange!

  Everything that happened after that I upgraded to VIBE UI 2.0 (1437 at present). I can be in line with the same with older versions - 1433, 1435.

  I hope that someone will be able to help!

  Just to share an update... With the SIM card of another operator, it works fine. So I don't know what's the problem with him. I have just gone to the operator and asked to change my SIM card, but it does not help.

  And when I put the same card in the SIM 2 slot, it works very well. Very strange indeed

• Missed calls log

  So, after all this time, I finally have a little question. All of a sudden my phone will not register my missed calls. No problems with ongoing calls. Right at the entrance.

  Anyone has any ideas.

  Thanks for any input.

  SOLVED

  I started to see the poor battery and more missed calls log. Then, I found it all started when I installed Kaspersky on the phone. I had checked to hide incoming calls and so no report in the paper was visible.

• Measurement and Automation does not open and generates the MAXKnownException error with an unknown exception.

  Measurement & Automation does not open and generates the MAXKnownException error with an unknown exception.

  Heres the log

  Context where the exception was taken:
  (No context - the unhandled exception)

  Size version of Base module
  -------------------- -------- -------- ------------------
  NIMax.exe 00400000 0006 has 000 4.6.0.49152
  ntdll.dll 770E0000 00180000 6.1.7601.18247
  00110000-76060000 6.1.7601.18409 Kernel32.dll
  KERNELBASE.dll 74E00000 00047000 6.1.7601.18409
  SYSFER. 74830000 00072000 12.1.1101.401 DLL
  1BFB0000 0001 NiMaxImp.dll B 000 4.6.0.49152
  Shell32.dll 74E50000 00C4A000 6.1.7601.18429
  Msvcrt.dll 76830000 000AC000 7.0.7601.17744
  74 00000 00057000 6.1.7601.17514 SHLWAPI.dll
  76740000 00090000 6.1.7601.18275 Gdi32.dll
  00100000 76480000 6.1.7601.17514 User32.dll
  Advapi32.dll 75DD0000 000 A 0000 6.1.7601.18247
  sechost.dll 76CC0000 00019000 6.1.7600.16385
  000F0000 rpcrt4.dll 76980000 6.1.7601.18205
  SspiCli.dll 74AE0000 00060000 6.1.7601.18443
  CRYPTBASE.dll 74AD0000 0000 C 000 6.1.7600.16385
  LPK.dll 76470000 0000 has 000 6.1.7601.18177
  USP10.dll 768E0000 0009D 000 1.626.7601.18454
  Ole32.dll 75F00000 0015C 000 6.1.7601.17514
  Msvcp90.dll 739F0000 0008E000 9.0.30729.6161
  Msvcr90.dll 73DB0000 000 has 3000 9.0.30729.6161
  74470000 00009000 6.1.7600.16385 VERSION.dll
  IMM32. 00060000 60000 74 6.1.7601.17514 DLL
  000CC000 76BB0000 MSCTF.dll 6.1.7600.16385
  74320000 00021000 6.1.7600.16385 Ntmarta.dll
  Wldap32.dll 00045000 763E0000 6.1.7601.17514
  Uxtheme.dll 6EB20000 00080000 6.1.7600.16385
  NiMaxUI.dll 1C2D0000 00269000 4.6.0.49153
  Msvfw32.dll 6BE30000 00021000 6.1.7601.17514
  73970000 00032000 6.1.7601.17514 WINMM.dll
  Comctl32.dll 73E80000 0019E000 6.10.7601.17514
  Wsock32.dll 73DA0000 00007000 6.1.7600.16385
  74DC0000 00035000 WS2_32.dll 6.1.7601.17514
  NSI.dll 75AA0000 00006000 6.1.7600.16385
  Oleaut32.dll 76580000 0008F000 6.1.7601.17676
  6D8E0000 003 Mfc90u.dll has 1000 9.0.30729.6161
  MSIMG32.dll 6EBA0000 00005000 6.1.7600.16385
  dwmapi.dll 6EB00000 00013000 6.1.7600.16385
  MFC90ENU. DLL 6EAF0000 0000 D 000 9.0.30729.6161
  NiMaxRes.dll 1BFD0000 0007 has 000 4.6.0.49153
  BtMmHook.dll 10000000 00038000 6.4.0.2900
  PSAPI. DLL 76440000 00005000 6.1.7600.16385
  DCIMAN32. DLL 6E1F0000 00006000 6.1.7601.18177
  MXS.dll 1 B 240000 4.6.0.49152 0000F000
  mxsutils.dll 1B4D0000 00041000 4.6.0.49152
  Msvcp71.dll 7C3C0000 0007C 000 7.10.6030.0
  7 360000 00056000 7.10.6030.0 Msvcr71.dll
  mxsout.dll 1 B 400000 00075000 4.6.0.49152
  64600000 00014000 4.257.3.0 nirpc.dll
  Mswsock.dll 73A 90000 0003C 000 6.1.7601.18254
  profapi.dll 76460000 0000B 000 6.1.7600.16385
  mxMax.dll 1BF20000 00086000 4.6.0.49152
  58000000 00240000 6.5.0.3005 AsstntUI.mxx
  MFC80U. DLL 71210000 8.0.50727.6195 0010F000
  MSVCR80.dll 0009B 000 8.0.50727.6195 72E50000
  Comdlg32.dll 20000 75 0007B 000 6.1.7601.17514
  71180000 00087000 8.0.50727.6195 Msvcp80.dll
  ATL80. DLL 6BD70000 0001 B 000 8.0.50727.6195
  MFC80ENU. DLL 730F0000 8.0.50727.6195 0000E000
  59000000 00582000 6.5.0.3005 mxwTask.dll
  00011000 74180000 6.1.7601.17887 Netapi32.dll
  74170000 00009000 6.1.7601.17514 netutils.dll
  74150000 00019000 6.1.7601.17514 srvcli.dll
  wkscli.dll 74140000 6.1.7601.17514 0000F000
  56000000 00148000 6.5.0.3005 mxwRCEng.dll
  mxcal.mXX 1 A 110000 00056000 4.6.0.49152
  mxcat.mXX 1BE20000 000AB000 4.6.0.49152
  nidmfuiu.mXX 04360000 0010D 000 1.11.0.49152
  NIPALU.dll 64000000 00057000 2.1025.3.0
  64500000 00006000 2.1025.3.0 nipalut.dll
  NIPAL32.dll 00007000 1F700000 2.1025.3.0
  SETUPAPI.dll 76240000 0019D 000 6.1.7601.17514
  CFGMGR32.dll 75DA0000 00027000 6.1.7601.17621
  76220000 00012000 6.1.7601.17621 DEVOBJ.dll
  6 280000 00031000 1.9.0.49152 nimdbgu.dll
  6 000000 00017000 1.9.3.49152 niorbu.dll
  nimstsu.dll 6E180000 0001 has 000 1.11.0.49152
  nimhwcfu.dll 6DFD0000 000 B 6000 1.11.0.49152
  6 050000 0001E000 1.9.0.49152 nidimu.dll
  nimxdfu.dll 0003E000 1.10.0.49152 6D0F0000
  nimxpu.dll 6E1B0000 0000 000 1.11.0.49152 B
  Iphlpapi.dll 74280000 0001C 000 6.1.7601.17514
  WINNSI. DLL 74270000 00007000 6.1.7600.16385
  74B 40000 001BD000 11.0.9600.17126 WININET.dll
  76A 70000 API-MS-Win-Downlevel-User32-L1-1-0.dll 00004000 6.2.9200.16492
  770B 0000 API-MS-Win-Downlevel-shlwapi-L1-1-0.dll 00004000 6.2.9200.16492
  75AB0000 API-MS-Win-Downlevel-Version-L1-1-0.dll 00004000 6.2.9200.16492
  76430000 00003000 6.2.9200.16492 API-MS-Win-Downlevel-normaliz-L1-1-0.dll
  normaliz. DLL 76450000 00003000 6.1.7600.16385
  iertutil.dll 75AC0000 00219000 11.0.9600.17126
  76610000 00005000 6.2.9200.16492 API-MS-Win-Downlevel-advapi32-L1-1-0.dll
  76200000 00017000 6.1.7601.17514 USERENV.dll
  nidmxfu.dll 04470000 0049F000 1.12.0.49152
  nimru2u.dll 6EC70000 00044000 2.10.1.49152
  nimmgluu.dll 69830000 0001E000 1.11.0.49152
  nimercu.dll 6DFB0000 00019000 1.11.0.49152
  MFC71. 00106000 140000 7 7.10.6101.0 DLL
  MFC71ENU. 360000 5 0000E000 7.10.3077.0 DLL
  niGPIBui.mxx B 6, 000000 0008E000 2.7.0.49152
  niIVIui.mxx 02CE0000 000D 0000 4.2.0.49152
  niPXIui.mxx A 671 0000 000BC000 2.1280.1.49152
  niRemPXI.mxx 1 A 270000 00057000 4.6.0.49152
  mxRmCfg.dll 1 has 000000 00090000 4.6.0.49152
  niRMui.mxx 1AD70000 000FD000 4.6.0.49152
  NISRLUI.mxx 6B 500000 00061000 3.4.0.49154
  63800000 00010000 2.7.0.49152 NiSpyLog.dll
  niSWui.mxx 1A3B0000 00072000 4.6.0.49152
  niVISAui.mxx 63360000 0017D 000 4.1280.0.49152
  62 30000 0002E000 4.1280.0.49152 niVISAres2.dll
  RICHED32. DLL 40000 00006000 6.1.7601.17514 6FC
  Riched20.dll 61F70000 00076000 5.31.23.1230
  Wshtcpip.dll 73A 80000 00005000 6.1.7600.16385
  nisysapi.dll 68 has 00000-000B 2000 5.5.2.49152
  Dbghelp.dll 70F20000 000EB000 6.1.7601.17514
  -------------------- -------- -------- ------------------

  Application: C:\Program Files (x 86) \National Instruments\MAX\NIMax.exe
  User name: administrator
  OS version: 6.1.7601 (Service Pack 1)
  Exception code: C06D007E
  Exception addr: 74E0C42D

  Sender's address: 74E0C42D
  Function name: RaiseException
  Module name: KERNELBASE
  Parameters: 00000000 00000001 0518FD84 C06D007E
  Source file: (not available)

  Sender's address: 68A3C6F7
  Function name: DllUnregisterServer
  Module name: nisysapi
  Parameters: 00000000 0518FD50 005F59B8 0000001E
  Source file: (not available)

  Sender's address: 68A53D87
  Function name: DllUnregisterServer
  Module name: nisysapi
  Parameters: 00000350 68A791B8 005F59B8 00000000
  Source file: (not available)

  Sender's address: 68A0DC65
  Function name: nisysInitDiagnosticsByValue
  Module name: nisysapi
  Parameters: 68A 01680 00000001 68A93BB8 FFFFFF01
  Source file: (not available)

  Sender's address: 68A0DFC4
  Function name: nisysInitDiagnosticsByValue
  Module name: nisysapi
  Parameters: 005E2C40 00000000 00000001 00000001
  Source file: (not available)

  Sender's address: 68A 01698
  Function name: nisysInitDiagnosticsByValue
  Module name: nisysapi
  Parameters: 005E2C40 00000000 00000001 00000001
  Source file: (not available)

  Sender's address: 1BE27A73
  Function name: mxGetProvider
  Module name: mxcat
  Parameters: 020469F0 02047084 0518FED0 1BE76CBA
  Source file: (not available)

  Sender's address: 1BE30D2E
  Function name: mxGetProvider
  Module name: mxcat
  Parameters: 02029FA8 02047748 0518FF34 1BE21D4C
  Source file: (not available)

  Sender's address: 1BE35780
  Function name: mxGetProvider
  Module name: mxcat
  Parameters: 00000000 00000000 02047818 020469F0
  Source file: (not available)

  Sender's address: 1BE21D4C
  Function name: (not available)
  Module name: mxcat
  Parameters: 02029FA8 1BE6264D 0518FF7C 73DD3433
  Source file: (not available)

  Sender's address: 1BE21CDC
  Function name: (not available)
  Module name: mxcat
  Parameters: 02030018 00000000 00000000 9192C45C
  Source file: (not available)

  Sender's address: 73DD3433
  Function name: endthreadex
  Module name: MSVCR90
  Parameters: 00000000 0518FF94 7607338A 02047818
  Source file: (not available)

  Sender's address: 73DD34C7
  Function name: endthreadex
  Module name: MSVCR90
  Parameters: 02047818 0518FFD4 77119F72 02047818
  Source file: (not available)

  Sender's address: 7607338A
  Function name: BaseThreadInitThunk
  Name of the module: kernel32
  Parameters: 02047818 00000000 00000000 775D5D69
  Source file: (not available)

  Sender's address: 77119F72
  Function name: RtlInitializeExceptionChain
  Name of the module: ntdll
  Parameters: 02047818 00000000 00000000 73DD345E
  Source file: (not available)

  Sender's address: 77119F45
  Function name: RtlInitializeExceptionChain
  Name of the module: ntdll
  Parameters: 02047818 00000000 00000000 73DD345E
  Source file: (not available)

  If I could come with the OS discs for the thing, I think I'd do a new install of Windows 7.

  Mike...