shearer@cis.udel.edu (Rob Shearer) (09/25/90)
Hello Again.... Thank you to everyone that responsed to my question about the stack segment... I have been to busy to try it yet.. or to respond... But I do have another question (I am still in the "paper" mode..) I need to determine how many Clock Ticks my routine uses as overhead so that I can decide if it is even worth it!... I bought a book on 386 assembly so that now I can calculate the # of clock ticks my routine uses... but... How can I calculate the# of clock ticks per second?? Each machine is different correct (meaning 25Mhz 386 compared to a 33Mhz 38 compared to 12Mhz 286 etc).. Is there a formula that I can use to determine the number of clock ticks there are per second based on known information.. (this does not need to be coded...this data is just needed for the design stage...) I found a book that said a 16Mhz machine has 1 clock_tick every 67.5ns (then their drawing of thw square wave, showed a 62.5ns clock_tick!) Another problem I am having: I have been playing around with speeding up the call to INT 0x08... and the machine at work will crash out/lock up on me when I fool with it... (DecStation 333c - 386 33Mhz Running MSDOS 3.3) but the EXACT same program at home (Gateway 2000 386 25Mhz MsDos 4.0) kicks some real tail.. - no problems! The Decstation has also locked up on me with a malloc under certain conditions... my ram tester doesn't report any errors... (CheckIt)... anyone think of a program I can use to report the error to try to get it fixed?? (I sometimes get Memory Parity error when playing with the INT 0x08 interrupt...) Thanks Again!... You guys don't KNOW how much you have helped me! Robb Shearer shearer@sol.cis.udel.edu