| |
The Phantom
Registered: Jan 2004
Posts: 360 |
WinVice & Windows 10 error
OK. I've dealt with this for a week or two and it's time to see if a solution is available.
WinVice 2.4 (win64 x64 mingw)
Anytime I double click a .d64, I get this error:
VICE Error!
Cannot startup logging system.
I hit enter (or click OK) and that is that. I haven't had any issues with Vice, just this silly error.
Any way to fix this? I can deal with hitting enter, but would rather Vice just boot up without my having to do so. |
|
... 30 posts hidden. Click here to view all posts....
|
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Can't produce this. When I select SID settings, nothing weird happens and I can quit VICE gracefully:
Cannot open winio32.dll, trying direct PCI I/O access.
Cannot use direct PCI I/O access on Windows NT/2000/Server/XP/Vista/7/8/10.
Detecting dll assisted PardSIDs.
Cannot open inpout32.dll.
Detecting direct I/O PardSIDs.
Cannot use direct I/O on Windows NT/2000/Server/XP/Vista/7/8/10.
Detecting ISA SSI2001 boards.
Cannot open inpout32.dll, trying direct ISA I/O access.
Cannot use direct I/O access on Windows NT/2000/Server/XP/Vista/7/8/10.
Sound: Closing device `dx'
Sound: Opened device `dx', speed 44100Hz, fragment size 2.9ms, buffer size 101ms
reSID: MOS8580, filter on, sampling rate 44100Hz - resampling, pass to 19845Hz
Exiting...
Sound: Closing device `dx'
Perhaps this has something to with parallel ports, my VM doesn't expose those.
Looks like another job for our Windows maintainer. |
| |
bepp
Registered: Jun 2010
Posts: 265 |
Necro-posting to this old thread if someone finds it on google (like I did).
I just started to get the "Cannot startup logging system" in Win10. It turns out I had a faulty entry in the setting for LogFileName, pointing to a folder/file that did not exist. Simply removing this line from vice.ini (which is stored in %appdata%\vice\3.1\vice.ini) did the trick for me. Maybe it can help someone that stumbles upon this. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
For VICE 3.3+ the vice config dir is in %appdata%/vice, we removed the "$major.$minor" subdir. So on my box it's C:\users\comp*x\appdata\roaming\vice.
The 'roaming' bit is currently hardcoded, if someone can explain why it's sometimes 'roaming' and sometimes 'local', or even 'LocalLow', our Windows maintainer would be much obliged :) |
| |
soci
Registered: Sep 2003
Posts: 479 |
Use SHGetFolderPath with CSIDL_APPDATA instead of hardcoding the path within the profile directory. Or even SHGetKnownFolderPath if supporting XP is not a concern. |
| |
Stryyker
Registered: Dec 2001
Posts: 468 |
In relation to error: lib_stralloc(NULL) not allowed
Some of the recent issues with Windows 10 can be because of winpcap being installed and not detecting network interfaces. The same can be witnessed in Wireshark. Uninstall winpcap and use npcap instead. Alternatively a vice build without ethernet |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quoting sociUse SHGetFolderPath with CSIDL_APPDATA instead of hardcoding the path within the profile directory. Or even SHGetKnownFolderPath if supporting XP is not a concern.
Thanks, will check out these functions. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quoting StryykerIn relation to error: lib_stralloc(NULL) not allowed
Some of the recent issues with Windows 10 can be because of winpcap being installed and not detecting network interfaces. The same can be witnessed in Wireshark. Uninstall winpcap and use npcap instead. Alternatively a vice build without ethernet
I had some suspicions the lib_stralloc(NULL) might be coming from a failure to enumerate network adapters via winpcap.
Of course on my box any Windows update doesn't trigger any pcap errors or UAC prompts, so it's a little hard to debug on my end. |
| |
Stryyker
Registered: Dec 2001
Posts: 468 |
I recently done a test in a fresh VM of Windows 10, 1809 as a standard users and r35878 seemed to work fine. No need to start as admin or any UAC issues. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Nice, and I assume this was with npcap, disabling the tick mark in the installer for 'require admin' and enabling the tick mark for 'wpcap API compatibility'?
That worked for me at least.
If so, we need to update our docs to tell people to use npcap and not wpcap. |
| |
Stryyker
Registered: Dec 2001
Posts: 468 |
no npcap or wincap installed. I guess the VM exposes the NICs a little differently.
In a 2nd native install on a system with Realtek with Windows 10, 1809 it ran fine - no need for admin.
The 1st native install was on a system with Intel NIC using 23.5 Intel ProSet drivers using the new Windows 10 driver model. |
| Previous - 1 | 2 | 3 | 4 - Next |
