running iqwic on mixed win2k and xp networks
Posted 12 January 2004 - 07:14 AM
Access violation at address 004595E in module "IQ.EXE". Read of address 00000198.
It doesn't matter wether the pc is connected to any iq component or not. Any idea?
Posted 12 January 2004 - 12:41 PM
The statement is an MS Windows error statement and often means the software is having trouble reading information from the Hard Drive.
I haven't heard of anything like this happening between Win2K and XP systems.
*How did you transfer the file between computers? If the file was transferred did you use a CD? Copying to a CD will change the files "Attributes" to read only.
Actually this does sound like a file sharing issue. You might check the file and folder properties of the dataframe as well.
*You should also check that all the computers on the network are running the same version of the software.
Posted 12 January 2004 - 03:02 PM
However using the same dataframe on-line with a WinXP laptop using lower resolution (1024 x 768 I think), the program is very stable.
It often seems to occur when closing a component control panel (8810C), but I haven't found any other repeatable identifiable actions that cause crashing.
The dataframe in question was started on Win98 and ported over from IQwin to IQwic, and has been through hundreds of revisions.
Have also had similar, albeit less frequent problems with various dataframes running under WinNT4. Haven't tried Win2K.
Hope this helps in the ongoing quest for bug-free perfectly behaved software!
Posted 12 January 2004 - 04:26 PM
In IQwin 5.11 our programmers increased the sensitivity of the software to certain errors that were not looked at before. Thus that version of the software showed a large number of nuisance errors. This was corrected in IQwin 5.12.
As for the resolution question I can't test it, as my computer will not give me the 1280x960 only 1280x768. I will check with the engineers and see what they say.
Posted 02 March 2004 - 01:31 PM
Is there a particular function when the Error occurs? Also have you tried a fresh dataframe to see if it happens only in the older dataframe?