WiC64 Emulation in Kernal64
- LazyJones
- Thread is Unresolved
-
-
Display MoreIt now saves the settings of the panel but not the "Enabled"
From my point of view, this would be important in order to be able to call it up directly from the C64Studio.
Would it be possible to save the enable as well?
So that after a start the WiC64 is directly active?
Ok, I'll work on this. Consider that is better to use the command line options than to save a global configuration.
I added --wic64-network-name <nw name> option to configure the network interface; I will add --wic64-enabled to enable the WiC64 at startup.
-
I will add --wic64-enabled to enable the WiC64 at startup.
This is top!
-
Great work!
Now I just need a remote debugging interface
-
Hi, I added support for two new command line options:
- --wic64-network-name <network device name>
- --wic64-enabled <true/false>
So, if you want, for example, run the emulator with WiC64 enabled at startup on network device wlan0 launch the emulator with --wic64-network-name wlan0 --wic64-enabled true
I tried it with C64Studio and works as expected.
The new version is 1.7.3b8 and the url is always the same https://github.com/abbruzze/kernal64/releases/tag/v1.7.3b4
The settings can be saved as well: for C64Studio or similar use case is better to use command line options.
-
My hero! Much appreciated. I'm just preparing a sample folder for WiC64 code and this is really really helpful. Thanks!
Works perfectly!
-
-
Si Senor!
Wobei die Parameter für Cartridge und Debug auch Quatsch sind, die klappen natürlich so nicht. Wichtig ist auch der Haken bei "Forward labels to emulator" unten rauszunehmen.
Die k64.bat hatte ich bei mir angepasst, dass ein lokales Java-Runtime benutzt wird (kein installiertes):
echo off
>Das hier<
set path=%path%;C:\Users\Georg\Desktop\C64\kernal64\jdk-17.0.2\bin
>Das hier Ende<
set HOME=%~dp0
...
-
Grazias
-
-
Bound
Endurion can you provide a screenshot of the perfect settings to connect Kernal64 to the C64Studio? Thanks in advance!
That's mine:
PRG/T64: --wic64-network-name wlan0 --wic64-enabled true "$(RunFilename)"
Cartridge: --wic64-network-name wlan0 --wic64-enabled true "$(RunFilename)"
-
Bound
Endurion
Have you checked under Settings -> Remoting?
There you seem to be able to open a port for it.The question would of course be what you can do remotely
The remoting feature enables a client to connect to the server: in this way the server can be controlled locally or remotely.
To run the client use remoteclient.bat/sh <host> <port>.
-
That sounds good. But control how? Is there a protocol of some sort?
Could I actually do remote debugging similar to what VICE does? That would rock!
-
Bound
That sounds good. But control how? Is there a protocol of some sort?
Could I actually do remote debugging similar to what VICE does? That would rock!
It was an attempt, long time ago, to implement a mechanism for multiplayer game: run the game on the server and play it with 2 players, one local, one remote.
The remote debugging it's not there yet, but it could be implemented, of course.
I was looking at the C64Studio sources: it seems that the remote debugging is only possible for Vice emulator.
Having a general debugging remote interface could be a starting point.
-
Yeah, esp. since that interface for VICE is either the old text interface (which is inherently bad for technical dialog), and the new binary interface. The latter is quite a bit faster (well, duh), and would be a good starting point.
I have no problem adding some new interface, I'm sure the one I half assed in there is not even half as good as could be.
-
Hallo nochmal,
Habe ein seltsames Problem.
1) PC in der Firma - LAN, wic64 einloggen funktioniert.
2) Privates NOTEBOOK zu Hause - LAN, wic64 einloggen funktioniert
3) FIRMENNOTEBOOK im Büro - WLAN, wic64 einloggen nicht möglich. Gibt man username oder passwort falsch ein kommt die entsprechende Fehlermeldung. Herunterladen von Zeugs mit dem gepatchten c64 wic-kernal funktioniert einwandfrei.
Jemand eine Idee? Habe sämtliche Eth/WLAN im Menü ausprobiert. Im log/Debugger sieht man auch das was passiert. Extra einen 2ten User registriert mit kurzem pw, selbes Problem. Auf allen 3 Rechner die selbe Java Version. Werde privatnotebook anstatt mit LAN. Al mit WLAN versuchen.
Aktuelle kernal64 Version, heute 23.2 heruntergeladen.
Lg
swasti
-
Schon das probiert:
Du kannst im WiC64 Panel des Emulators in der unteren Statuszeile das Lokale Netzwerk auswählen. Gehe die mal durch, evtl. klappts bei dir dann. Bei mir musste ich "eth5" auswählen.
-
leider nicht. habe alles probiert. habe beide notebooks nebeneinander. beide haben eine ip aus meinem lokalen netz. das private notebook geht mit lan/wlan und ich kann mich einloggen.
das firmennotebook - kann mich per lan/wlan nicht einloggen.
am privatnotebook win10 enterprise 20H2 19042.1526 und am firmennotebook win10 pro 21H1 19043.1466 (ich darf/kann beide selbst verwurschteln wie ich mag...)
es gibt bei beiden notebooks nur 1 netzwerkinterface das meiner ip entspricht.
strange... keine idee... (falls jemand hier das log vom server auswerten möchte , der username lautet swasti1, oder gerne per pm bei mir in einen liveversuch)
beide "virtuellen" wic64 haben auch entsprechende mac adressen.
wicradio oder andere tools lassen sich mit der entsprechenden url von beiden starten.
lg
swasti
-
Bound
Display MoreUnfortunately not. have tried everything. have both notebooks next to each other. both have an ip from my local network. the private notebook works with lan/wlan and I can log in.
the company notebook - I can't log in via lan/wlan.
on the private notebook win10 enterprise 20H2 19042.1526 and on the company notebook win10 pro 21H1 19043.1466 (I may/can mix up both myself as I like...)
there is only 1 network interface for both notebooks that corresponds to my ip.
strange... no idea... (if someone here wants to evaluate the log from the server, the username is swasti1, or you can PM me in a live test)
both "virtual" wic64 also have corresponding mac addresses.
wicradio or other tools can be started by both with the appropriate url.
lg
swasti
Hi, can you attach the logs from Kernal64 WiC64's debug log window for both scenarios ?
If you can reach the portal IP or other PRGs and just the portal login phase fails, the problem could be bound to MAC address, because it's part of the user authentication process.
-
habe den bug gefunden (ob der jetzt im kernal64 oder in der richtigen hardware ist) kann ich nicht sagen.
mein rechner hat diese mac adresse:
XXYY0bb9ZZzz
laut log wird jedoch nur diese zum server geschickt (hier fehlt eine 0 - der server erwartet sich aber bestimmt eine 12 stellige zahl, oder was auch immer. er bekommt aber was falsches geliefert)
XXYYbb9ZZzz
habe das ganze mal in windoof mit dem registryhack auf aabbccddeeff gesetzt und konnte mich sofort einloggen.
lg
swasti
