Was working fine under 8.1, fails to launch under Win 10. Tried compatibility troubleshooter, no luck. Windows error log shows:
Faulting application name: BasiliskII.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: BasiliskII.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0002c4a6
Faulting process id: 0xae8
Faulting application start time: 0x01d0cca5bbdd10a3
Faulting application path: C:\Program Files (x86)\BasiliskII\BasiliskII.exe
Faulting module path: C:\Program Files (x86)\BasiliskII\BasiliskII.exe
Report Id: 581e99ad-a8f9-46ba-8243-c048aee9edde
Faulting package full name:
Faulting package-relative application ID:
Version is BasiliskII for Windows 20-02-2015.
Basilisk II does not start with clean install of Windows 10
Moderators: Cat_7, Ronald P. Regensburg
Re: Basilisk II does not start with clean install of Windows
Hi,
I can't reproduce your error. I know it is not much help, but the latest Basilisk works fine here in Windows 10.
Best,
Cat_7
I can't reproduce your error. I know it is not much help, but the latest Basilisk works fine here in Windows 10.
Best,
Cat_7
Re: Basilisk II does not start with clean install of Windows
Got it working. Deleted Prefs in folder I didn't know about:
C:\users\username\Appdata\local\VirtualStore\Program Files(x86)\Basilisk II
The folder is related to UAC settings, which changed when I updated to Windows 10.
C:\users\username\Appdata\local\VirtualStore\Program Files(x86)\Basilisk II
The folder is related to UAC settings, which changed when I updated to Windows 10.
Re: Basilisk II does not start with clean install of Windows
Hi,
Good to know. I did a clean install of Windows 10 and Basilisk and don't have that folder/file.
Thanks,
Cat_7
Good to know. I did a clean install of Windows 10 and Basilisk and don't have that folder/file.
Thanks,
Cat_7
Re: Basilisk II does not start with clean install of Windows
The root cause was that I had put the Basilisk folder in the Program Files (x86) folder in Windows. Windows uses the Virtualfolders method when programs try to modify the Program Files folder contents. Moving the Basilisk folder to C:\Users\username fixed the issue for good. SheepShaver has the same issue with being in the Program Files (x86) folder.