Menu

#38 command line issues

1.0
open
nobody
None
2019-10-10
2019-08-05
Paul
No

If I load a PRG from within the c64 debugger then everything loads and runs fine. However if I specify the PRG using -prg via the command then it is loaded but the first 2 bytes appear to be both 0 and not the values which they should be, so no basic appears. I can still manually type SYS and run the code, but if I add -jmp 2061 to the command line then the PRG does not appear to get loaded or maybe is loaded into a wrong memory location.

Am I doing something wrong ? ... it'd be really useful to be able to use the command line features.

Many thanks

Paul

Discussion

  • Paul

    Paul - 2019-08-05

    Should have said that I'm using version 0.64.56.6 and I'm on a Mac

     
  • Paul

    Paul - 2019-08-07

    actually .... if I add -jmp 2061 then the prg is loaded at the correct address, with the first 2 bytes intact, but the code is executed with the screen blanked - only the 'border' is displayed for the entire C64 screen

     
  • Jesse Litton

    Jesse Litton - 2019-09-12

    I can confirm this bug. I'm using version 0.64.56.6 compiled from source on Linux.

    Just a guess, but is the -prg parameter loading the code into the memory map before the system initializes? I believe the soft reset NEW's-out the first two bytes of BASIC RAM.

     
    • slajerek

      slajerek - 2019-10-10

      Yes, this seems to be related to the fact that Kernal is initialising. You can wait a bit for the Kernal to finish initialise by adding -wait <ms> parameter, also I suggest to apply a "Fast kernal patch" in Settings, so the init is quick. Normally around 500ms should be enough to get the Kernal going.</ms>

      Please confirm if adding -wait parameter fixed your problem.

      I have a plan to rewrite this and add a quick init based on snapshots, anyway this is still WIP.

       

      Last edit: slajerek 2019-10-10

Log in to post a comment.