- Aug 30, 2016
- 393
- 685
The Windows in the I disk is not a Windows that I actively use. Before purchasing an SSD for the computer, I was using windows installed on the hard disk. I then bought an SSD and did a clean install of Windows. I am using this SSD now as C disk and system disk.My previous post just said how to do it without explaining it, which seems to cause some confusion, so let me explain it first.
1.) After implement number 3, StudioNEOV2 is in vanilla state, that is, BepInEx does not work, and there is no plugins / mods / AutoTranslator. At this time, StudioNEOV2 is the original illusion StudioNEOV2.
2.) winhttp.dll is the entry point for BepInEx to injects the unity game. After renaming winhttp.dll to winhttp.dl_, unity game will not be able to load BepInEx's winhttp.dll, but will load windows winhttp.dll, which will disable BepInEx.
3.) As long as the unity game (HoneySelect2 / StudioNEOV2 here) runs smoothly and there is no problem, then Fatal, Error, Warning, Message, Info in the output_log.txt or console log can be ignored. Having Fatal, Error, Warning does not mean that there is a file corruption or program error.
Back to the problem.
I saw turbojoe's question about your computer's I drive. Then I went back to your posts.
So your I drive is the system drive (Maybe a multiboot system drive that isn't hidden?), or is the system drive no longer used as a data drive? The system drive refers to the drive with the operating system installed. As long as the settings are correct, it can be used to boot. After booting, it will be the C drive.
Move the entire HS2-R13 folder to a non-system drive, and change winhttp.dl_ back to winhttp.dll. If your BetterRepack R13.7z is still there, you can also directly decompress a new HS2-R13 to a non-system drive. Then double-click StudioNEOV2.exe to see if StudioNEOV2 can work normally and whether the interface is in English. If so, congratulations, the problem is solved. If not, then we will implement number 5 to see if the problem can be solved.
So when I turn on the computer, the running Windows version is Windows installed in the SSD C: disk. So it's not the old windows installed on the "I" disk. Could this still be causing a problem?