Christopher Grey

I'm also finding that sometimes just deleting the Port entry and readding it just results in a crash and thus I can't modify or edit the port entry. The only way I was able to avoid this was to "reboot" VTS by deleting the vts3.cfg file and allow VTS to regenerate that info which seems to work without crashing. So the good news is I now have a way to limp VTS along within Linux via WINE. It's not pretty, but it at least works. I messed around with VTS enough to realize there's a feature needed or...

I was able to get a little more success. There is still some GUI bugginess with the Port Configuration window while running in WINE. However I was able to add an IP port and select the ethernet port I wanted, get it saved, and then I was able to actually send packets using it. However I cannot edit the port due to the GUI display issues that prevent proper painting of the IP tab. So to "edit" the port, I have to delete the old one and readd a new one. But that's at least better than nothing. However...

Well with a good bit of debugging, I've been able to glean a good number of the DLLs that are required just to get VTS to launch. Most of them were installed by vcredist_x86.exe, however the one that was holding up the show was mfc42.dll. That one was evidently needed by nb_link_settings.dll. I copied it and mfc42u.dll over to the same folder VTS.exe is in and now I have VTS launching in Linux by WINE! However this only got me to the next stumbling point. When I go to Edit>Ports to configure for...

I'm trying to see if I can get VTS to run on my Ubuntu 14.04 (32-bit) Linux machine with WINE installed. I've been able to install the vcredist_x86.exe, but VTS.exe doesn't seem to do anything. It doesn't throw any errors, it just doesn't work. It seems to have some error and then quietly exit but without indicating what the problem is. Usually the problem with programs that don't run correctly under WINE are related to missing or outdated DLL files. To solve these problems, the failing program usually...