cube
Junior Member
Posts: 58
|
Post by cube on Feb 23, 2007 0:52:06 GMT -5
Looks like line noise to me... John
|
|
|
Post by Jim Brain on Feb 23, 2007 1:07:39 GMT -5
Although my VICE knowledge is a bit rusty, VICE sprouted real com port support quite a while back, and then WinVICE added IP support, but did not bring the com port support over. I think we asked why, and it was not someone's itch to scratch.
However, the problem is a bit tougher with WinVICE.
If you pair WinVICE up with tcpser or tcpser4j, then you have a emu-modem to answer the calls, and send the correct AT stuff to WinVICE (and to the app reading the "com" port.). But, there is currently no way in WinVICE for the emu-modem to signal lines like DCD. So, some BBS apps won't work, as they look for DCD to change state when a call arrives.
Anthony Tolle patched tcpser and WinVICE 1.19 to support these features, so that's a possible option. I rolled the patches in my working copy for rc11, but I need to look at them.
Jim
|
|
|
Post by expertsetup on Feb 23, 2007 12:37:11 GMT -5
Although my VICE knowledge is a bit rusty, VICE sprouted real com port support quite a while back, and then WinVICE added IP support, but did not bring the com port support over. I think we asked why, and it was not someone's itch to scratch. However, the problem is a bit tougher with WinVICE. If you pair WinVICE up with tcpser or tcpser4j, then you have a emu-modem to answer the calls, and send the correct AT stuff to WinVICE (and to the app reading the "com" port.). But, there is currently no way in WinVICE for the emu-modem to signal lines like DCD. So, some BBS apps won't work, as they look for DCD to change state when a call arrives. Anthony Tolle patched tcpser and WinVICE 1.19 to support these features, so that's a possible option. I rolled the patches in my working copy for rc11, but I need to look at them. Jim Thank you for this information Jim, I am getting up to speed with the data on this page now: gcns.com/vice/vice.htmlI should be up and running soon
|
|