cook@sybil.cs.Buffalo.EDU (John M. Cook) (11/21/89)
I was always told the dangers of writing a sloppy C programs. Where a
misplaced pointer can mean distruction. Well this must be what I did,
a quick program I wrote last month is causing problems. I'm too busy
to sit down and really check all my function for logic errors this
week but before the end of the month the error must be found. What is
this error? Well somehow my program is sending an interrupt to the
ROM on this AT clone and starts it's SETUP routine. What should the
program be doing? By the last screen display, it has just finished
editing a record in a file, (fopen,fseek,fread,fseek,fwrite,fclose).
What follows this is just a menu screen where it appears to be lock-up
but by typing a few 'A's the SETUP routine appears. Since I don't run
this program I don't the exact sequence of events before the lock-up,
but it has happen two times.
My questions to the net:
Is my first guess right?
Does it seem that maybe I'm fseeking out of bounds?
AND
If I wanted to invoke a ROM SETUP routine how could I do it?
Thanks,
John Cook