On Thu, 28 Feb 2002 23:43:07 -0400, Clarence Verge wrote: > On Thu, 14 Feb 2002 21:47:14 -0500, Clarence Verge wrote:
>> To RUN a program INSIDE debug so you can see what is happening to the >> registers as the program moves along, type G100,100 <enter> >> This means Go @ 100 (start) and then stop at the breakpoint 100. >> Then type P<enter> to proceed one step. This message never reached me... was the list off again? > Correction: > Don't type G100,100 - just type G100 <enter> > Problems running off at the mouth without looking at the book there. <g> Well I did look at the book... but the problem was not running the program into debug but to get it into debug... Just had 23 hex-codes... how to type these in? There must be an easyer way than making a BASIC program first ;-) Thanks for enlightening the cryptic instructions in the book. CU Bastiaan > When specifying breakpoints with the "go" address, you must put an "=" > in front of the start address to distinguish it from a breakpoint. > i.e. G=100,100 > But G100 does the same thing if you want to see every step. > p.s. Don't try to set a breakpoint at a rendom location. It must be > at the first byte of an instruction. > Here are most of the debug commands: (* =hardly ever used) > A (assemble) > C (compare) * > D (dump) > E (enter) > F (fill) > G (go) > H (hex) * > I (input) * > L (load) * > M (move) > N (name) > O (output) * > P (proceed) > Q (quit) > R (register) > S (search) * > T (trace) > U (unassemble) > W (write) > - Clarence Verge > - Back to using Arachne V1.62 .... -- Arachne V1.61, NON-COMMERCIAL copy, http://arachne.cz/
