August 26, 20206 yr Author Is this Tidal a 32 bit or 64 bit program? Only a 64 bit version of shell32.dll is available at present.
August 26, 20206 yr Author Then, it will not work until the 32bit version of shell32.dll is released. It may take some time because its functions are very buggy.
August 28, 20206 yr Author File temporarily pulled due to quality control issues. I have just uploaded two new files: osloader.exe (winload.exe) and ntkrnlmp.exe (ntoskrnl.exe). Two modifications have been made: -Code integrity checks have been disabled -Version number of ntkrnlmp.exe is 6.1.6002 To use these files, copy them to your system32 folder (x64 only, of course!). Then enter CMD and do these commands: bcdedit /copy {current} /d "Windows Vista Unlocked" Keep note of the value you get in this form: {91274567-89ab-cdef-00ff-nca000ffffff}. Replace yours with whatever value you get. bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} nointegritychecks 1 bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} path \Windows\system32\osloader.exe bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} kernel ntkrnlmp.exe Installation media with these files replacing the existing MS ones may be capable of loading unsigned drivers, like USB 3.x drivers. The version change to 6.1 was done because I found out that some drivers react negatively to the "wrong" OS version number. For example, some NVIDIA XP drivers fail to load on pre-reset Longhorn builds because they're NT 6.0, AMD drivers seem to arbitrarily reject Windows 8 and new NVIDIA drivers do the same for early Windows 10 releases. I'd like to hear results from Ryzen and NVIDIA Pascal series GPU users. Edited August 28, 20206 yr by win32
August 28, 20206 yr On 8/28/2020 at 3:27 PM, win32 said: I have just uploaded two new files: osloader.exe (winload.exe) and ntkrnlmp.exe (ntoskrnl.exe). Two modifications have been made: -Code integrity checks have been disabled -Version number of ntkrnlmp.exe is 6.1.6002 To use these files, copy them to your system32 folder (x64 only, of course!). Then enter CMD and do these commands: bcdedit /copy {current} /d "Windows Vista Unlocked" Keep note of the value you get in this form: {91274567-89ab-cdef-00ff-nca000ffffff}. Replace yours with whatever value you get. bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} nointegritychecks 1 bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} path \Windows\system32\osloader.exe bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} kernel ntkrnlmp.exe Installation media with these files replacing the existing MS ones may be capable of loading unsigned drivers, like USB 3.x drivers. The version change to 6.1 was done because I found out that some drivers react negatively to the "wrong" OS version number. For example, some NVIDIA XP drivers fail to load on pre-reset Longhorn builds because they're NT 6.0, AMD drivers seem to arbitrarily reject Windows 8 and new NVIDIA drivers do the same for early Windows 10 releases. I'd like to hear results from Ryzen and NVIDIA Pascal series GPU users. Nice! I will try it on my Ryzen PC and I will give you feedback! @win32I have two boot options on my HDD now. "Microsoft Windows Vista" And "Windows Vista Unlocked" Which one should I boot on?
August 28, 20206 yr 11 minutes ago, win32 said: I got this error when booting from it. Booting on the "Microsoft Windows Vista" Still works though. Edited August 28, 20206 yr by ilwalaihr
August 28, 20206 yr Author I'm running on this kernel right now. What's your level of updates and version number of current ntoskrnl.exe? Edited August 28, 20206 yr by win32
August 28, 20206 yr 9 minutes ago, win32 said: I'm running on this kernel right now. What's your level of updates and version number of current ntoskrnl.exe? Updated to Vista EOL, and ntoskrnl is 6.0.6002.19741
August 28, 20206 yr Author 4 minutes ago, asdf2345 said: Updated to Vista EOL, and ntoskrnl is 6.0.6002.19741 So, the same as me. What results do you get when you run bcdedit (without parameters) in CMD?
August 28, 20206 yr 7 minutes ago, win32 said: So, the same as me. What results do you get when you run bcdedit (without parameters) in CMD?
August 28, 20206 yr 51 minutes ago, win32 said: I'm running on this kernel right now. What's your level of updates and version number of current ntoskrnl.exe? I think one of these but I may have to check tomorrow to be sure. KB4467706 KB4458010 Any of these shouldn't have any problem right? Since they're from Windows Server 2008. Edited August 28, 20206 yr by ilwalaihr
August 28, 20206 yr Author I'm very puzzled by this. I repeated my own steps - success. Replaced the ntkrnlmp file with the one from the mega folder - success. Then I noticed that I had detecthal = yes which none of you had. So I changed one to no (0) and I got the same error. So, I'll add this to the instructions bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} detecthal 1
August 28, 20206 yr 2 minutes ago, win32 said: I'm very puzzled by this. I repeated my own steps - success. Replaced the ntkrnlmp file with the one from the mega folder - success. Then I noticed that I had detecthal = yes which none of you had. So I changed one to no (0) and I got the same error. So, I'll add this to the instructions bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} detecthal 1 Alright, I will try this tomorrow and I will give you feedback as soon as possible.
Create an account or sign in to comment