Doesn't work without connecting video cable.

[FrancescoGd]

Hi, first of all thank you for this useful tool!
I've got a little problem and I don't know if it's just me or if it's intended behaviour: if I boot up my Amiga without connecting the video cable, VNC doesn't work, which kind of defeats the purpose of this invaluable tool (at least for me) because I have a single monitor and I want to use the Amiga from the PC.
PC is on Win10 and I use UltraVNC as client, monitor is connected through DVI, Amiga is a SAM440EP mini-itx with this configuation from ShowConfig:

PROCESSOR:	AMCC PPC440EP
EMULATED:	CPU 68020/68881fpu
CUSTOM CHIPS:	NONE
VERSION:	Kickstart version 54.30, Exec version 54.30, Disk version 53.18

[rolsen74]

Hi not sure if you are still around... I forgot all about this bug report... but if you are still around, did you have a chance to test my latest release? alot have changed since last release.

Sorry about long reply time

[FrancescoGd]

Don't worry, thanks for replying... the problem is still there but I'm starting to suspect that that's an Amiga OS own problem, not yours... I tried both disconnecting the cable from monitor only leaving it connected to the Amiga, and then disconnected it completely but the problem remains with both combinations. I believe the Amiga sends some wrong info to the client because it connects but then the client window is black and smaller than it should be (maybe it's the default UltraVNC window size, I don't know).
If I boot the Amiga normally and then disconnect the cable, everything works. If i Boot the Amiga with cable connected but monitor powered off, everything works too, so it could be the Amiga not "sensing" what to send without a cable plugged when the server starts (I start it from network-startup script).
On the other hand, the new version is faster, so thank you for this 🙂

[rolsen74]

Thanks for the explanation that’s very helpful.

I’ve just finished rewriting the config file loader/saver code, and during that work I noticed that Server AutoStart is currently OFF by default. The documentation says otherwise, so that’s on me. As a result, you’ll need either a config file with AutoStart enabled or an ARexx script to start the server automatically at boot.

Regarding the display issue: I’ll need to see if I can reproduce it here. I haven’t yet tested booting without a monitor cable connected, but I'll do that before the next release.

Thanks again for the report and I’m glad to hear the new version feels faster 🙂