Argument out of range - how to find what is causing it?


Closed Thread
Results 1 to 6 of 6

Hybrid View

  1. #1
    Join Date
    Sep 2009
    Posts
    755


    Did you find this post helpful? Yes | No

    Default Re: Argument out of range - how to find what is causing it?

    I think that this causing overflow:
    DEBUG 13,10, "598", 1310
    Comma is missing.
    So DEBUG can handle only byte, so 1310 = $51E and that is bigger then 1 byte.
    So i suppose that DEBUG should be something like this
    DEBUG 13,10, "598", 13,10
    Just find in PBP 1310, and insert comma...
    EDIT: I just read first few post's

  2. #2
    Join Date
    Jul 2003
    Location
    Colorado Springs
    Posts
    4,959


    Did you find this post helpful? Yes | No

    Default Re: Argument out of range - how to find what is causing it?

    Food for thought ...

    You can open .LST and .ASM files in MicroCode Studio, and it even highlights them.
    If you have line numbers turned on, View > Editor Options > General tab > Show line numbers in left gutter
    It's easy to find things according to the numbers in the error messages.

    When opening a file in MCS, change the Files of type: dropdown box to Assembler and List Files (*.asm;*.lst)

    Select the View > Editor Options > General tab > Prompt if file reload required option and it will ask to reload the files after a compile of the .pbp program so you're always looking at the most recent version.
    DT

Members who have read this thread : 1

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts