Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Arutz Tele

Member
  • Content Count

    27
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Arutz Tele

Profile Information

  • OS
    Windows 8.1 x64
  • Country

Flags

  • Country Flag

Recent Profile Visitors

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

  1. This kinda reminds me of what I've done in 2018, trying to boot the XP x64 installer on my HP desktop but I got a ACPI error. I'm not sure if it'll solve the ACPI errors if I use the textmode drivers.
  2. So I decided to install the x64 version of Windows Server 2008 (R1), which is basically the Server edition of Windows Vista. Enterprise version. I'm quite surprised I don't get the initialization flaws, but I'll have to see in the next couple reboots. It works okay. Any user who wants to use Vista post-Haswell should try Windows Server 2008 R1 for x64 version, you can transform it to Vista. UPDATE: Got the services bug again, "Failed to create security dialog" thing showed up. UPDATE 2: Rebooted, services still start okay. Just installed Wireless LAN Service and it works. UPDATE 3: Although the OS installed properly, there will be some boot attempts where you get the "Logon Process Initalization Failure" screen, just click OK and it'll get you to the logon screen. I'm installing updates but I don't think it will have any effect on the problems. Some services also won't start. UPDATE 4: Modified the Intel Skylake Graphics driver to make it work, it installed successfully but cannot run. Installing Platform Update had no effect, but I cannot install the Supplement, but I doubt it wouldn't have a effect neither.
  3. What I've also found out is a screenshot from DeviantArt from awhile back showing proof that Vista x64 worked on a Haswell machine: https://www.deviantart.com/a11ryanc/art/Desktop-Screenshot-Core-i7-4790k-w-Vista-SP2-623466851 It's kinda ironic that his works, but in the comments I've seen no proof how he got it to run perfectly fine. There could be a possibility.
  4. Also a reminder if you wanna install Vista on anything newer, don't go for x64 version (for now), as it causes so many issues with Services. You are better off with the x86 version.
  5. And that's kinda awkward because I find it ironic how would Windows Vista x64 run with many failures on Skylake, while I ran Windows 7 RTM (before installing SP1) and it loaded without any issues what so ever. I wonder what about Windows XP x64? I think XP x64 could run natively without issues, but requires some more work. I might look into that.
  6. That is the issue, and I don't know if there will be a fix other than to use the x86 version of Vista. And what if you wanna restart or shutdown the computer? Well, if you don't get Windows Security, you have to force shut it off manually
  7. Looks like I'll have to reinstall with x86 Vista media, but I'm afraid about GPT. It looks like I'll have to wipe my entire hard drive for MBR support...
  8. and this is what I got on some boots while trying to open Windows Security:
  9. So I have decided to use a old ThinkPad image I did from a year back and restored it to my partition via Clonezilla, however I still get the service errors, and Logon failures and startup failures as well. I think it didn't help.
  10. So I was installing Windows Vista on my Skylake DELL laptop again, and I just got the "Windows Setup could not configure Windows to run on this hardware" message.
  11. So I see here. Because when I installed it before deleting the partition when I gave up, I didn't have the Platform Updates (I had SP2 though), but I would see a little chance of it getting fixed, even installing the Platform Update. My DELL laptop is newer and uses UEFI, and for macOS, we all heard of Clover, it is a tool that bypasses Apple restrictions and allows macOS to boot on non-Apple hardware. It's easy to restore both, actually in that case. About Platform Update, I might reload Windows Vista later on and see if it's going to have a slim chance to work.
  12. I think that is true, because the API functions weren't introduced until at least Windows 7+. I'm not sure if there are any Windows Vista updates that add these compatibility layers. I'm doing this on a triple-boot configuration (with Windows 7/POSReady and macOS), so if I'm installing on a VM, how could I clone it with Ghost or some other tool without destroying my Windows or macOS?
  13. Hi guys, it's 2020 and I wanna talk to you about something. A few months back I decided to experiment installing Windows Vista on my Skylake, Dell Inspiron 5559 laptop. The OS works, but it would not start up properly at some times. It would also not shutdown properly. What I managed to get working was sound, WiFi (via DW1560 card upgrade), and a higher screen resolution. But another key problem here is that the Display Driver would not work. I took the Windows 7 setup file for the Intel HD Graphics 530 and modified it to make it work with Windows Vista. It did install properly with warnings, but even with Disable Driver Signature Enforcement the drivers wouldn't load, and it would be much worse. If anyone has solutions on how to make Vista work better on Skylake and Kaby Lake and other processors, let me know
  14. That's really crazy! How'd you do that? And how'd you get the Intel USB drivers working, was it the modded drivers or you took the Windows 7 drivers and modified the INFs so that it'll install on Vista? I'm thinking on installing Vista on my Skylake laptop or Kaby Lake desktop in the near future soon... Tell me all about how you got everything to work on maybe a PM or here, up to you. Speaking about x64 is a no-no, that means that I could only install the x86 version? I remember last time when I booted the x64 version, on Setup it gave me a blue screen.
×
×
  • Create New...