Jump to content

ilwalaihr

Member
  • Posts

    47
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Portugal

Posts posted by ilwalaihr

  1. 4 minutes ago, win32 said:

    I don't think so. Is ntext available at this point? If not you can use the even older procedure for getting Firefox 7x/8x working by replacing the ntdll function call RtlQueryPerformanceCounter with NtQueryInformationProcess in firefox.exe using CFF Explorer.

    I got these two errors.

    Screenshot_2.png.a0f16663603eada02920d2215fedc15c.pngScreenshot_1.png.cd723a54d949c06aa929b489835bae2c.png

  2. Good news! I finally got the old version installed, I had to install Windows on pure Legacy MBR, the new version (with the installer) still breaks the OS though.

    @win32 I can only run up to Firefox Quantum 64 and it can get laggy, is this an issue with the old version of the kernel? I probably need to try the new one later

  3. 8 minutes ago, win32 said:

    I am pretty sure that it has been working on Haswell before, and the functions are largely based on those from recent Windows 7/8.1 updates.

    :dubbio:

    It's an i5 4460s, do I need to copy anything else than the dll files?

    There are other files on the "finished files" folder.

    I still have a copy of an older version, maybe I should try it?

  4. 9 minutes ago, win32 said:

    Another outstanding issue in terms of file location is the difference between a system with UAC enabled and disabled; the former will set the current directory to %winroot%\system32 by default, while the latter does not insist on changing the current directory. I had thought by adding cd /D "%~dp0" that I resolved this discrepancy, which I have tested on Vista installs with both UAC enabled and disabled.

    If I hadn't set the CD, then the system files would've been renamed (or the installer would purposely fail due to lack of ntext if it's not there) with new ones not being copied because they would no longer be present.

    I tried to copy the ddl files on the "vistaexkernsetup_11222020" folder and the OS keeps rebooting before logging in.

    So this kernel isn't Haswell ready it seems?

  5. 2 minutes ago, win32 said:

    Yes, if the installer has problems executing then yes. I do know that I had a hard time loading the services MMC snap-in and task manager among others on a Kaby Lake system.

    If I log off after installing, the OS just logs on to a black screen and I'm not able to open anything due to "missing dll".

    The installer basically seems to not find the dll files after copying them to the System files I think.

  6. 2 minutes ago, win32 said:

    No, though it seems that experiences have been mixed with the installer. Even if not giving it admin privileges things should be fine, as it wouldn't even be able to manipulate any files in that case.

    It is possible that this may be related to the Haswell+ timing issues, as it is possible that some of the commands issued by the installer failed.

    It actually gives me some errors during the installation.

    Should I try to copy the files without the installer? Thankfully I have a restore point.

  7. I tried to install the new Extended Kernel from November on my Haswell PC with the April 2017 update, using the .bat file, after rebooting, it gives me a fast BSOD (telling me USER32.dll was not found, c0000135) just before the logo animation happens.

    Did I do anything wrong?

     

    Forgot to mention that before rebooting the OS literally breaks, and I'm not able to even run apps with admin privileges since they give me a Filesystem error.

  8. 2 minutes ago, win32 said:

    I'm very puzzled by this. :dubbio:

    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. 

  9. 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? 

  10. 17 minutes ago, Ximonite said:

    I have already tried this before. It boots but only sees one device.

    My BIOS version is E7A34AMS.AE0

    Almost forgot you also had a MSI motherboard.

    It seems to me that we should wait and see if Win32 or any other can solve the problem, this seems to be a Ryzen specific issue.

  11. 3 minutes ago, Ximonite said:

    Mine are Ryzen 5 1500x, MSI B350 PC Mate, 16GB RAM, GTX 960 4GB.

    My USB issues happen when I have multiple devices plugged into the same controller.

    The nice things about these older GPUs is that they're still quite good and that they're also compatible with older operating systems.

    For me they can happen at any time, I have a variety of USB Devices plugged in to my USB ports.

    The OS can refuse to start sometimes, but I don't know if that's USB related.

  12. 3 minutes ago, asdf2345 said:

    Ryzen 7 2700X, MSI X470 Gaming Pro Carbon, 48GB of RAM (Also tried with just 16GB clocked at automatic settings), GTX 970. (I think that's basically what all matters)

    Also, screenshot showing my installed drivers

    Unti3tled.jpg

    Nice amount of RAM there! Here are mine, since I never told my complete specs:

    Ryzen 5 2600, AsRock B450M-HDV R4.0, 16GB of RAM, GTX 960 2GB.

    And I also get that BSOD sometimes.

  13. On 8/25/2020 at 3:11 PM, asdf2345 said:

    How do you know it's Haswell+, if you don't know the CPU?

    I was also trying to run Windows Vista, and trying to see if Windows Server 2008 would run on my SkyLake laptop, but since it's the same as Vista, and since there are no Graphics and USB drivers, then I must install Windows Server 2008 R2.

  14. 9 hours ago, asdf2345 said:

    I got the issues before I even installed USB drivers, even when I only used a ASMedia USB card

    Me too, even when I only used my PS/2 mouse only.

    My installation procedure is basically installing Windows Vista on my physical HDD using VMware, then, after the first reboot, complete the installation on the PC, then when I have to setup my user etc... I do it on VMware, after that I just boot it on my PC, install the USB Drivers on the Device Manger, install the newest update, NetFramework 4 for my GPU drivers, and install my GPU drivers, that's about it.

×
×
  • Create New...