home.social

#ultimate-64 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ultimate-64, aggregated by home.social.

fetched live
  1. Could a different kernel cause the datasette to not even rewind? It's totally non-responsive...as if it's not even plugged in.

    #RetroComputing #Commodore #Ultimate64

  2. #Commodore has released firmware 1.1.0 for the #C64ultimate and it seems to contain the fixes from Gideon's #Ultimate64 3.14d firmware (including more robust #JiffyDOS support) while retaining the more refined system menus from the Commodore branded computers.

    #C64 #C64U #U64

  3. Responding to myself responding to myself:

    I borrowed the KERNAL, Basic, and Char ROMs from a VICE installation, after which the updated #Ultimate64 booted up as expected. I can’t say for sure whether all issues are gone, but Mayhem in Monsterland, which would never load successfully with #JiffyDOS earlier on this machine started up like nothing; and Gunship, which would inevitably crash at an arbitrary point in loading, has come right up into flight mode. Awesome!

  4. Experimenting with #JiffyDOS on my #Ultimate64 - it seems to be pretty hit-or-miss. The webpage had a note recommending what seems to be CIA timing settings:

    > Can I utilize JiffyDOS on the Ultimate II?
    >
    > Yes. Customers have noted that settings PH1=140 and PH2=80 work well.

    I don’t see any way of finding nor tuning these settings, though. Have I misunderstood something?
    #c64 #c64ultimate #c64u

  5. All you Ultimate 64 users come share your story and pictures of your build.
    Here is mine:

    My Aldi 64 Ultimate!
    For my Ultimate 64 I wanted it to have a little bit of unique appeal like so many others have done....
    [read more, click the link]
    8bitboyz.com/messageboards/pos

    #c64 #Commodore #commodore64 #Aldi #Ultimate64 #Gideon

  6. Oh yeah! I'm lovin the REST API:

    PUT /v1/machine:writemem?address=0277&data=52554e0d&address=00c6&data=04\r\n
    HOST: 192.168.1.64\r\n
    \r\n

    You don't need to issue a single PUT for each RAM insertion, multiple pairs are totally valid! The above inserts chars on the keyboard buffer $0277 (631) and then the number of chars in $C6 (198). This allowed me to "type" on the U64 from my Linux box. I sent these via ncat and input redirection. The `\r\n' were the actual bytes ASCII 13 and 10, not escaped 'r' and 'n'.

    (FWIW, this is on the earlier Ultimate 64 Elite board, not the new C64U.)

    #RetroComputing #Commodore #C64 #Ultimate64