search

xlar54 / ultimateii-dos-lib

cc65 library for accessing the DOS and network functions of the Ultimate II+ cartridge and Ultimate 64 motherboard
GNU General Public License v3.0
60 stars 13 forks source link

Sample program not working with U2+ Updated to Latest Firmware #56

Closed 8bit-Dude closed 2 years ago

8bit-Dude commented 2 years ago

Hi there!

I have a C64G and U2+ which has been updated to the latest firmware (3.10a). My IP settings use DHCP, and I have an IP showing up in the main menu.

But when I give the u_sample.prg program a try, unfortunately everything comes up blank... No IP detected (everything 0.0.0.0), and blank results for all tests.

Is there any particular setting on the U2+ that needs to be setup for the program to work??

LeifBloomquist commented 2 years ago

I've found that there is a sensitivity with the Turbo modes with the new 3.10a firmware, anything over 10MHz gives me a problem here with similar symptoms to what you are describing. Try 1MHz? Then increase to see is there is an optimal setting.

sblendorio commented 2 years ago

Also, please make it sure you're using the latest release of UltimateTerm https://csdb.dk/release/?id=207440

bvl1999 commented 2 years ago

In C64 and settings.. make sure you have the ultimate command interface enabled (and make sure it only says enabled, and not something like 'version 1.x'. ), and save the config. power cycle your c64, press the middle button to enter the u2+ menu, press f4, and scroll down to cartridge information, and check what it says there. It will tell you if you have a cartridge enabled which inhibits the ultimate command interface, if so, you need to disable that cartridge (action replay, epyx and fc3 for example) or pick one which does not inhibit use of the ultimate command interface (super snapshot and retro replay for example), and save your config.

8bit-Dude commented 2 years ago

Ah it worked! I had the Epyx Fastload cart enabled, which indeed inhibits the command interface. It could be a good idea to update the readme.txt file with a short description of this potential issue. Thanks for the quick support!!