ADTPro 2.0.3 exits after clicking serial icon

[zxarr]

I managed to get the correct Java installed and ADTPro 2.0.3 starts, I can see the com port, then it just exits after I click 'Serial'. I only have one COM port, COM6, using a USB cable. ADTPro sees it OK, from what I can tell.

I'm attaching the trace and the error log to this. Not sure what to do next.

ADTProTrace.txt hs_err_pid6752.log

The cable I'm using was sent to me from RetroFloppy. It's a //c system where ADT 2.0.3 starts up without issue. Running WIndows 10 with a Prolific USB-to-Serial adapter. 64-bit Java after removing and reinstalling the latest 64-bit version.

Thanks.

[david-schmidt]

It's your USB cable. Prolific is junk, sorry to say.

[zxarr]

I was afraid of that. Any recommendations on a good chipset for a USB to serial cable?

Thanks!

On Tue., Aug. 6, 2019, 10:28 p.m. David Schmidt, notifications@github.com wrote:

It's your USB cable. Prolific is junk, sorry to say.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ADTPro/adtpro/issues/81?email_source=notifications&email_token=AAPSZBWRQH6G6YPNC7BHGTLQDIXOVA5CNFSM4IJ3PLFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3XABHY#issuecomment-518914207, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPSZBXGN2VWTRNK6SVQZ3LQDIXOVANCNFSM4IJ3PLFA .

[david-schmidt]

FTDI.

[zxarr]

FTDI.

So I have an FTDI adapter now and I'm still getting the same error. It just closes. hs_err_pid14532.log

[david-schmidt]

Can you try using (pointing to) a Java 8 VM instead of 12?

[zxarr]

I did that and it didn't close this time! It said 'Connected'.

I'll attempt a disk transfer later this evening.

[zxarr]

Success! All working now.

Thanks!