From: address@nospicedham.not.available   
      
   Bill,   
      
   > In the actual (greater) program (not posted) it does work fine the first   
   > time   
      
   Yes, I read that.  And it makes it less likely that stack overwriting is the   
   cause of the problem.   
      
   > Since it works the first time there must be some other problem.   
      
   Yep.   
      
   So, did you already check the other thing I wrote about (a non-existing   
   memory-to-memory copying instruction) ?     And ?   What did you find ?   
      
   Also, have you already displayed the contents of the int13pkt record, to see   
   if it matches what you think it should contain ?   Does it ?   
      
   In short: do some checking to see if what you get is what you expected.   
   If needed, pull your program thru a disassembler and compare with the   
   sourcefile.   
      
   > In my 'boot sector' I have the following   
   >   
   > mov ax, 0   
   > mov ss, ax   
   > mov sp, 0x600   
   > mov ds, ax   
      
   Yes, I was already wondering about with what DS and SS where set.   It shows   
   that your stack area is well below your program (and its data), and not   
   likely to be overwritten.   And that your DS matches (as expected) your   
   programs CS (otherwise you strings would not have displayed).   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)