If you can run Giga Studio after the QS exception:
Take one .gig file and put it in a new directory (with no directories below it - it searches recursively) and select that directory in the QS Advanced window (from the main QS window) in order to narrow the QS search. If you still get the exception, you will know it is not a bad file (unless you just happened to choose the bad one [img]images/icons/shocked.gif[/img] )
Also, maybe the QS database (that it builds for you) is corrupted. From the Advanced page, push the button that tells QS to recreate its database. This would delete the original database file and create a new one. Along these lines, if you can\'t run GS after the QS exception, search for the QS database file on your PC. I suppose it would have \"quick\" in its name and have a recent date - whenever it was last updated. If you find it, rename it then run QS. If even stranger thing happen, name that file back to its original name (oops!).
easiest way I\'ve found is to just rename the whole \'DB\' folder in Program files/Nemesis/Gigastudio to \'DB Old\' - then just re-launch gigastudio, forcing it to completely rebuild the database from scratch. Works every time for me....