BL> I just go looking for the twit and fight my way out, I can do a
 BL> 150K packet in 1.5 seconds. If I read every message it takes 22
 BL> seconds. I tried it the sensible way first, but my way is more
 BL> fun.

 PE> Change your algorithm and you should be able to get it close to
 PE> 1.5 seconds doing it the proper way. BFN. Paul.

  You have my full attention!

  At present, I read a 30K string from the 150K packet. This is
read very quickly. Then I search the 30K string for the position
of the first "Rod Speed00" that identifies the message to be twitted. 
I then find the position of the 00 02 00 which marks the end of that
message. I write everything in the string before the 02 00 to my new
twitted file, and then go back to the packet at the end of the message
to read the next 30K string, in a loop until I find the end or run
out of twits.

  My test packet is 150K with 15 Rod Speed meessages, and it removes
them in 1.5 seconds.

  If I do the same thing, reading every message by chasing 02 00's and
then finding the ones with Rod Speed00 in them, I have to loop 100
times (100 messages) and it takes 22 seconds on my poor old machine.

  I'm a real beginner and I have to work these things out for myself.
I thought I was being clever. What am I doing wrong? What's the proper
way? I don't want you to write the code - just tell me.

Regards,
Bob
 
___ Blue Wave/QWK v2.12
@EOT:

---