ab> PROBABLY you've missed to INC(ctr) somewhere in your code, but if 
ab> that is not the case, read on..
ab> I need more information; how are the following variables declared:
Well what a ya know! I was looking for something weird and it was staring me 
in the face! Yes, I had forgot to inc the counter that goes through the 
key...kinda strange that it worked in 16 bit and not 32, but it needed the 
fix because the routine wasn't working as I expected until I fixed the 
counter. The results we predictable where there weren't before.  
ab> Also, why the IF (charbyte0 or 32) etc it is meaningless in the 
ab> code above you do the same thing weather there is a #0 or #32 or 
ab> #anychar. I guess that along the way you discovered that it was kind 
ab> of hard DEcrypting when you found the value #32 and you did not know 
ab> weather this was a real space or if it was another char to be 
ab> decrypted ;-)
Well, this is a routine I worked on in a College class once. I found that 
encrypting a file full of spaces would reveal the password (assuming it was 
all text) in reverse case. I have also had some problems in the past with #0 
since it is used as a end of string marker. Can cause strings and files to be 
cut off prematurely. So, I don't encrypt them which means that they only way 
to know what to do comming back is not have any created that werent supposed 
to be there...what a confusing mouthful..  
Basically, I don't encrypt them or let any encryption result in them. 
Therefore, I don't have to worry about them and my routine encrypts on the 
first pass and decrypts on the second pass without problems or revealing the 
password. 
Gotta run...thanks for the feedback...it is working now :) 
Steve
--- FreeMail 1.07b
(1:203/21)
---------------