WORKING WITH INSTRUNET DIAGNOSTIC REPORTS
TROUBLESHOOTING > REPORT >

There are several ways to create an instruNet Diagnostic report text file, for purposes of debugging an instruNet system. This text file can easily be emailed to an instruNet supplier for comment when troubleshooting.

Generating A Diagnositic Report with instruNet World
Run instruNet World software, press the TEST tab, press the REPORT button to print the diagnostic report to the window, copy the text to the clipboard (Windows Control C), paste into an email window (Windows Control V) and then email to your instruNet supplier for comment. This report can also be generated by pressing the "SAVE DEBUG REPORT TO DISK" button within an error alert. If instruNet World crashes upon launch, then please resort to the method below.

Generating A Diagnositic Report From other Software
With version >= 1.4 of the instruNet software, diagnostic text is written to file "iNet32 Diagnostic Report.txt" within the System Directory ("Windows \ System \" on a Windows 95/98/Me computer, "Windows \ System32 \" on a Windows Nt/2k/Xp/Vs computer, or "System Extensions" on a Macintosh computer). Even if your software crashes upon launch, this file will be written and will contain useful information. One enables the generation of this report when any program that works with instruNet software is executed (e.g. instruNet World, HpVee, DasyLab, C, Basic, etc) by placing an empty text file named "iNet32 Diagnostics On.txt" into the System32 Directory. After installing the instruNet software, this file will already be in position, yet will be named "iNet32 Diagnostics Off.txt". To enable the report generation, rename this file to "iNet32 Diagnostics On.txt". One can turn the Diagnostics mode off by changing the"On" back to "Off" in the file name, or by placing the word "off" into the text file using WordPad or NotePad. Since the diagnostic file is opened and closed each time it is updated (you'll hear the hard disk making some noise during this time), this feature significantly slows down the launching of your program. It is recommended that you only do this once since it since it slows things down. After you generated that one file, you can email it to your instruNet supplier for comment.

Enabling Additional Error checking
With >= 1.31 instruNet software, one can turn on additional error checking with the following steps: create a text file named "iNetLoad.ibs" and place it in the same directory as iNet32.dll ("\windows\system\iNetLoad.ibs" for Win 95/98/Me or "\windows\system32\iNetLoad.ibs" for Win Nt/2k/Xp/Vs) or place it in the same directory as your application program. This is an instruNet Script file that is executed when you first open the instruNet driver. Inside this text file place "calibrate checkon" on line 1 and "delete all" on line 2. This will cause the iNet32.dll instruNet interface dll to do extra error checking and report more information when there is a problem. To see if this error checking is on, open the instruNet World window from within your program , press the SEARCH button in the TEST page, and look for "DevOn_" printed at the top of the window. If you see this, then it means that extra error checking is turned on.