I received a replacement authorization disk today. As I understand it,
there are now 2 different types of authorization keys out there. The
version I have creates a file on the HD called JFW.cps. the big
difference is, before, the only thing that would work when moving the
key was to use evmove and, at least for my setup, had to be in plane
dos to work reliably. This key works differently, this 1 requires that
you be in windows and use the hjauth file to move authorizations back
and forth. It was a little frustrating, when evmove didn't work, I
called HJ tech support. The guy over there was totally stumped too.
After playing around, looking up various error coes that evmove gave
him and check as well, he finally found out that, hjauth had to be
used. I can understand there being some confusion with the 2 different
standards out there, however, what was frustrating was the fact that I
feel that the tech support guy should have known about this. When
evmove didn't work, immediately, we should have tried hjauth. I am not
blaming the support rep, it is a problem with communication at HJ,
apparently, the tech support personel didn't know about this, or at
least, he didn't!
Anyway, I am posting this to warn you, if anyone gets a new disk and
evmove doesn't work, don't panic and call tech support until after you
have tried hjauth!
-
Visit the jfw ml web page: http://yoyo.cc.monash.edu.au/~nallan/jfw
