From FB: VICE Nightly Transfer Issues
Posted: Fri Nov 12, 2021 8:13 pm
From Bucko (Pasted from FaceBook)
"Larry asked me to post a message letting everyone know a couple of issues I am having with Vice.. So don't update to the latest Nightly just yet. What is happening is the last couple of NIghtly versions have issues transferring files via the network between , my WN4 board which runs on Linux (Ubuntu 20.04) and my Hubs both of which run on Vice WIndows 10 Lt Kernal Emulations, sending files works like a charm, receiving back does not with the newer Nightly's after 40835. BUT WIndows LTK to LTK Emulation works fine. So the jist of this message is next month The writers of Vice usually update the version number to the latest nightly which next version is 3.6, until the RS232 issues are solved OR I find a work around to it, (might have to drop the baud rate of my Hub to 19.2 or 9600) don't upgrade. If you want to do some testing on your own, update to the latest and try sending a large file and receive a large file from your connections, if it all works you are good to go. If it doesn't revert back to your original copy of Vice. I haven't been able to run a stripped down copy of Vice to test via Term programs back and forth (this is what they are requesting) yet, but once I do and if the new fixes that were added this morning fix it we are good to go. BUT IF NOT, DON'T UPDATE.. You will just take down the network and your users won't be able to multi transfer.. Any questions ask..."
Continued....
"Just a quick update. Did some testing as the writers of Vice requested with no extras installed. I transferred a 87 block file from WinVice to Winvice and the same file back with 1 bad block both ways. Linux to WIndows was a different story, first file transferred to Windows file, windows back to Linux all bad blocks. I am currently assembling a latest nightly with the old RS232 routines in it for Windows to see if it works. My suggestion is, if you want to play with the latest versions, see if your networking works bi-directionally, if it does you are ok, if it doesn't. Keep using the older version. WHen I am done testing the Windows version I am assembling without the latest RS232 files if it works fine, I am going to stick with that running my Hubs."
Thanks Bucko for the information...
"Larry asked me to post a message letting everyone know a couple of issues I am having with Vice.. So don't update to the latest Nightly just yet. What is happening is the last couple of NIghtly versions have issues transferring files via the network between , my WN4 board which runs on Linux (Ubuntu 20.04) and my Hubs both of which run on Vice WIndows 10 Lt Kernal Emulations, sending files works like a charm, receiving back does not with the newer Nightly's after 40835. BUT WIndows LTK to LTK Emulation works fine. So the jist of this message is next month The writers of Vice usually update the version number to the latest nightly which next version is 3.6, until the RS232 issues are solved OR I find a work around to it, (might have to drop the baud rate of my Hub to 19.2 or 9600) don't upgrade. If you want to do some testing on your own, update to the latest and try sending a large file and receive a large file from your connections, if it all works you are good to go. If it doesn't revert back to your original copy of Vice. I haven't been able to run a stripped down copy of Vice to test via Term programs back and forth (this is what they are requesting) yet, but once I do and if the new fixes that were added this morning fix it we are good to go. BUT IF NOT, DON'T UPDATE.. You will just take down the network and your users won't be able to multi transfer.. Any questions ask..."
Continued....
"Just a quick update. Did some testing as the writers of Vice requested with no extras installed. I transferred a 87 block file from WinVice to Winvice and the same file back with 1 bad block both ways. Linux to WIndows was a different story, first file transferred to Windows file, windows back to Linux all bad blocks. I am currently assembling a latest nightly with the old RS232 routines in it for Windows to see if it works. My suggestion is, if you want to play with the latest versions, see if your networking works bi-directionally, if it does you are ok, if it doesn't. Keep using the older version. WHen I am done testing the Windows version I am assembling without the latest RS232 files if it works fine, I am going to stick with that running my Hubs."
Thanks Bucko for the information...
