Jump to content

Chuterix

Member
  • Posts

    9
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

1 Follower

About Chuterix

Profile Information

  • OS
    Windows 7 x64

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Chuterix's Achievements

4

Reputation

  1. From MyDigitalLife.net. The original topic can be found here By backporting the generic display driver from Windows 8 build 7963 (a beta which has both x86 and x64 builds), in which it can support both UEFI GOP and Legacy VGA BIOS, the benefits of the generic driver can work in Windows 7 and UEFI class 3 systems that can't support UefiSeven can receive display output. Even if the driver files fail and nothing actually happens, we can backport some display miniport drivers from build 7963 too. What we need is to fix/mod the .inf file. Here are the results with vanilla driver: The .inf fix/mod hasn't been done yet; please discuss here. Then for the internal modding: Original watchdog.sys doesn't work; we need the one from Build 7963, in which we will change the file to link to build 7963's watchdog.sys by renaming it watchdog8.sys and changing the import. Missing import in ntoskrnl.exe found; we must use ntoskrn8.sys (NTOSKRNL_Emu, found here [fork]) to fix this. Before: After: No missing imports found (AFAIK). WIP Files (x86 not verified real imports, also .inf needs to get fixed if it's possible). Mirrors: https://forums.mydigitallife.net/attachments/mbda_7_wip-7z.61664/ https://mega.nz/file/WlwwVLqa#5sIt_25-9qRR6zMZLAlQSn_5GVBGcHtPgq22NWev_n4 For MyDigitalLife, see also the thread link at the beginning of this post.
  2. yeah. but because i tried that, i'm requesting the post to be deleted.
  3. what software do i use to change imports? cff explorer i'm trying. how do i recalculate checksum? del
  4. sometime in 2022 the page reported an error before, but now as of today the board page is back, but everything just says this: Information Come back soon! (Please) i never got a chance to visit this forum when it was still open and i only started joining windows forums in april 2022 can anyone give me a reason why that board died? i’m new
  5. i could then say hypothetically that driver killer breaking drivers is the user's fault, but due to it's nagging and closed source pay to use full software it's not what I recommend at all
  6. yeah, that happened to me before (despite this is a almost 2 year comment), so it means go search for the touchpad driver, otherwise stick with the default generic one (that can't handle touchpads correctly but better than not being able to move it at all)
  7. great, someone bumped the thread, so i guess i'll have to tag along too i've never used driver crapper or probably any io bit software snappy driver installer (origin) downloads driverpacks, then it would install the drivers it finds. it would try to find the most optimal driver (even older versions, and should recommended be signed) and then install it. sometimes it comes across unsigned drivers, or drivers that don't work (e.g. installation of ivy bridge graphics driver doesn't work, have to manually do it from the ivy bridge guide here) probably because the driverpacks thinks something is something, idk. for modern systems running older os, it maybe incompatible (for instance, it discovers modded ryzen chipset that has directory of windows 10 on a windows 8.1 system, unsigned and it failed to install, until i found out about the modded driver on winraid for 7 & 8.1) and almost certainly the incorrect ryzen chipset driver for vista it also installs unsigned keyboard & other hid drivers on modern os this is at the fault of the driverpacks, or you (most certainly), not sdi(o) itself so either create your own driverpack (pack into .7z format) or recommended you find the compatible driver first (this is prerequisite for packing) and then install it example: https://mega.nz/folder/qtxS2KaS#Tsm4EHhoz5fhLdPMK8P87w if there are no drivers for such hw and sdi doesn't install it correctly, then you're truly out of luck. please i'm begging you, please stop with the opinions but everything is YOUR RESPONSIBILITY, and enough is enough. bye.
  8. Do you have CSM/Legacy Booting in your BIOS/UEFI? Enable that and the default generic VGA graphics driver can render. If not try using UefiSeven https://github.com/manatails/uefiseven If not then you're out of luck, unless you manage to find solution (like overwrite default VGA driver with manufacturer driver) P.S. If you enable CSM/Legacy Boot, then make sure that UEFI application start is set first, unless you want to go for MBR mode.
  9. There is also a generic USB 3 driver made by the same user that made the AMD USB 3 driver. See here (must be logged in!) https://forums.mydigitallife.net/threads/windows-vista-drivers-etc-for-modern-hardware-collection.85899/ I can also provide direct links https://www.mediafire.com/file/fgpxbkt9ly6i4py/WinPE_KB2864202++USB3x.7z/file https://drive.google.com/file/d/1MoRwTRdvbOTG88PV3_CervB235YJVkZm/view?usp=sharing https://www.icafe8.top/usr/uploads/2021/04/3331464833.rar You can also swap boot.wim with the one from Windows 7 with the USB 3 drivers integrated. (use NTLite or Simplix Update Pack Tool) There's a way to integrate drivers into install.wim but it's difficult. (Does Load Driver installation even work?) You can also use WinNTSetup from a WinPE environment (Windows 10 PE?) to deploy the Vista install.wim with the drivers added. For UEFI Class 3 systems, UEFISeven could work. Untested. https://github.com/manatails/uefiseven A generic NVMe driver that supports Vista; (from chinese forum) here's it's mirror: https://mega.nz/file/bwY3kKqJ#EjcvJk2023Vy3eOkxT8w2Q6UW7u4Tsp1y2pQPPvjw8s See the MDL forum topic for more details. I'm very noob at ARM CPUs so IDK what to say. WDYM by "use dedicated GPU and disable integrated graphics because with the integrated graphics CSM doesn't work?" Does it mean you're stuck with the default generic VGA driver since there are no IGPU drivers for Vista? MSFN, why can't you implement a redo function when making a post? Once I ctrl+Z my post, there's no going back and it's worse with my OCD here.
  10. it is actually possible to run obs 28.0.1 in windows 7, thanks to patched qt6 files found here 28.0.0, i was able to update from last supported windows 7 version of obs. but when i received new 28.0.1 update, i had to manually install it using the installer app and repatch files since the update checker blocks windows 7 from updating anymore can we please move obs studio to requires mod to work on win7?
×
×
  • Create New...