Jump to content

mahcih03

Member
  • Posts

    8
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Morocco

Posts posted by mahcih03

  1. 1 minute ago, Tripredacus said:

    What hardware are you testing on or are you using a VM?

    I remember not seeing any systems with UEFI capability in the desktop boards until 2011, so there was no way for me to test these capabilities when Vista (or even SP1) came out. It was a thing on Server boards, but the ones I remember having UEFI 2.0 would only allow an EFI boot with RAID enabled. And then by 2011, I was only trying to get UEFI PXE boot to work. I recall those "early" days of UEFI 2.3.1, it took manufacturers a bit of time to iron out the bugs in their implementation. If you are using hardware for testing, you probably want to use something from 2013 or newer.

    I've used VMware Workstation 14, which uses UEFI class 2 since it's still using the legacy graphics driver

  2. 6 hours ago, jaclaz said:

    Without an exact date when the image was made it is meaningless.

    If it is BEFORE March 9 2006, then its "Windows Vista Beta 2 will have ..." is just outdated material: 

    https://en.wikipedia.org/wiki/Development_of_Windows_Vista

    if it is after that, it may be accurate or not.

    Logically, Vista Beta 1 had not such support (otherwise the slide would have said "will improve" instead) 

    Vista Beta 2 - besides - came in three different builds (April 19, 2006 with a build number of 5365,  May 1, 2006 with a build number of 5381, May 18, 2006 with a build number of 5384) so, even If it had the EFI/UEFI support, it is possible that one builf had it andf another had it not.

    To further add to the confusion, it seems like in Vista Beta 1 there are some EFI related files, and seemingly even in some (specific) builds of XP MCE:

    https://forums.macrumors.com/threads/windows-xp-pro-sp2-does-have-efi-support.173183/

    http://www.cdrinfo.com/Sections/News/Details.aspx?NewsId=8628

    but possibly the EFI files in Vista Beta 1 were a leftover of the experimenting and were not functional or fully functional for booting on EFI/UEFI (and since the change of plans was mainly due to the overlapping of the switch from EFI 1.10 to 2.0 around the same period, it is likely that those files if they work at all, work only on a specific firmware).

    jaclaz

     

     

    I've just tried loading Vista Beta 1's EFI files in the shell, but it gives an "IA32 not supported by this x64 shell", maybe the Beta 1 was supporting Itanium's EFI instead of UEFI

    Also, it would make sense that 5384 supports UEFI since WinHEC 2006 was on May, I'll try it and see if that's true

    UPDATE: I've just installed Vista Build 5384 x64 using Windows 7's UEFI PE, and after replacing winload.efi, it boots! There's only "an error while editing boot entries", but it booted up in EFI mode!

  3. Is it possible to create user accounts (like in Windows OOBE) directly from Minisetup? There's only a step about the user and organization names, but that's not what I'm looking for.
    I'm choosing Minisetup instead of Windows Welcome because it detects PnP devices before anything else. I'm also using it because I'm working on a project of making Windows XP on par with modern OSes in as many aspects as possible, and I need to sysprep it in order to capture it and install it from PE.

    PS: Found the user account creation dialog in syssetup.dll using ResHacker (Dialog 56 : 1033), but for some reason it never shows up on neither Windows XP nor Server 2k3

  4. On 11/01/2018 at 3:47 PM, Kmuland said:

    These are great news Dibya. Currently Using a Bay-Trail M computer with windows 7 because I cannt find drivers for vista or XP. I cannt get XP installed on this machine due to BSOD duirng install.. but vista works perfect and smoother than 7. Only video drivers are missing, so Ill be glad to give a try to your driver when ready.

    About brightness, yeah it is a must!!! The new LED screens are very brighty and it hurts your eyes

    May I know which BSOD error code you are getting during the install?

  5. Hi. I've successfully installed both Windows 2000 and Windows XP x86 on my Kaby Lake laptop, at the cost of ACPI, USB and more..

    However, when I try to boot the 64bit edition of Windows XP from a DVD, it goes directly to the F5 menu without pressing any key.

    In the menu, I can find "ACPI Uniprocessor PC", "ACPI Multiprocessor PC" and "Other", which requires a floppy drive. There's no such option as "Standard PC" like in the 32bit version. So I tried both of the ACPI options, they both give me a 0xA5 blue screen (BIOS not fully compliant with the ACPI specifications -since it's too recent-)

    I tried to press the F7 key when the setup says "Press F6", but it still redirects me to the F5 menu. I really need the XP x64 version to run so I can test an Intel HD Graphics I've recently modified, it gives a "platform" error on the 32bit version.

    My BIOS doesn't have any ACPI options, I've tried to change the AcpiOptions value in the txtsetup.sif file to 0, still no luck.

    Any idea on how to solve the problem?

×
×
  • Create New...