Search the Community
Showing results for tags 'dongle'.
Found 2 results
Q: I’m currently working on a model run on a previous build, 2009 07 AE iSP, and I’m experiencing a WDRVR.DLL dongle error. A: Tuflow builds 2009-07, 2008-08 and 2006-06 predate the newer WIBU CodeMeter dongles and can thus show a WDRVR.DLL error as they look for the old Softlok dongle. Updates for these old builds were released to recognise the new WIBU dongles. These can be found here: http://www.tuflow.com/Tuflow%20Previous%20Release.aspx Release notes detailing these updates are found here: 2009-07: http://www.tuflow.com/Release_Notes_2009_07.htm#8 2008:08: http://www.tuflow.com/Release_Notes_2008_08.htm#12 2006-06: http://www.tuflow.com/Release_Notes_2006_06.htm
Hi, We have a large model running which takes about 12 days. We are 4 days into two of the runs and my PC detached from the network where we have a network licence for ISIS. The run log says: "Seeking licence for ISIS-TUFLOW-PIPE link...Licence code 4 unobtainable. Dongle read error code 0 Please attach the dongle and hit return." I ensured I was reattached to the network but when I pressed return on one run and the model run just closed. The second is still paused awaiting my input, I'd rather not lose 4 days run time if possible. Is there a way to continue running the model having lost and regained network connection? Thanks, Lucy