Jump to content

Aemony

Administrator
  • Content Count

    285
  • Joined

  • Last visited

  • Days Won

    52

Everything posted by Aemony

  1. You're out in uncharted waters with too many unknown factors -- there's almost no guarantees that can be made. The general gist of it though, if even possible, is to convert the Win7 iso to a USB stick (Google for instructions on how to do so) and then boot using the USB stick and install Windows 7 on a separate partition/drive through there.
  2. Well, my strongest recommendation would be to, well, not install Windows 7 at all. But if you really have to, I imagine installing it after Windows 10 should hopefully do the trick. Although be mindful that something might go wrong and you might have to reinstall both OSes to fix it in the worst case scenario.
  3. https://social.technet.microsoft.com/wiki/contents/articles/14286.converting-windows-bios-installation-to-uefi.aspx But it's not something I'd recommend undertaking -- especially not before your new system arrives as the action can (and most likely will) make the disk unbootable on your existing system.
  4. Because of the lack of that row, I'm assuming the OS is installed in legacy BIOS mode.
  5. Is there no more rows below that? That row you've highlighted is the "SMBIOS Version" shown on the page I linked to. The actual row "BIOS Mode" you need to look for is two (or possibly more) rows below that one.
  6. Not necessarily as it could very well be that your motherboard is configured to use legacy/BIOS/compatible boot and not UEFI boot. The legacy option was often the default on older machines as well as on components sold separately. It was mostly only pre-built machines that had UEFI boot enabled by default. See this for how you can determine whether Windows 7 is booting in UEFI or legacy BIOS mode: https://docs.microsoft.com/en-us/archive/blogs/home_is_where_i_lay_my_head/how-to-check-in-windows-if-you-are-using-uefi
  7. According to the FAQ, at least 3 edits to existing pages and an account life of at least 6 hours is required before a new page or file can be created.
  8. Please clarify whether this file is from the unpatched, original ToCA2 from the CD-ROM or the patched 4.1 version.
  9. Not necessarily -- it all depends on which boot manager is being invoked, and whether that boot manager recognizes the other OS automatically or not. If it does not, you should be able to create the missing entry from the booting OS by using bootrec. There's also a possibility that your new OS is configured to use UEFI to boot, while your Windows 7 is configured and installed as legacy/"BIOS". If that's the case you might not be able to boot Windows 7 until you put the BIOS/UEFI in legacy/compatibility mode, and might or might not have to once again recreate the boot entry usi
  10. We have a tiny search bar on the front page? I never use that one.
  11. This only applies to games running in classic exclusive fullscreen mode, where the fullscreen optimizations of Windows 10 aren't being used nor is the game running in (borderless) window mode. This is, to be honest, a bit of a hit or miss. HDR support is still in its infancy with various alternative methods available which affects how or whether a game will enter HDR mode automatically or not. For example, Nvidia exposes HDR through their NVAPI that some games utilizes, yet there's also the native built-in support in Windows as well. I still haven't really fully grasped whi
  12. We actually had a SwiftShader page back in 2012 but it was removed due to lack of content, and honestly I sorta don't see it go any different this time around. From the looks of things, SwiftShader is essentially turning graphics APIs and calls into software rendering -- that is, being rendered and executed on a CPU and not the GPU. It is intended for enabling 3D rendering on systems that otherwise can't fully support hardware-accelerated rendering, and was developed by Google to allow 3D web content to be available even to those users without proper GPU capabilities. It makes i
  13. After extensive discussion, I think we're close to finalize the details of how we would cover it best. The way I see right now is a multi-parameter approach like the DualShock 4 parameters under input, where we both track support (native, hackable, etc) separately from the mode supported itself (DirectSound3D, Windows Spatial, etc). Inputting e.g. "EAX" into the mode field would interpret it as DirectSound3D and show it as such.
  14. As for FF8, I was about to say that it looks to be the Steam version but the support page mentions how up to 3 machines can be activated simultenously: https://support.jp.square-enix.com/faqarticle.php?kid=70429&id=9221&la=0&ret=faq&pv=20&page=0&c=0&sc=0&so=0 Basically it sounds as a non-Steam SecuROM PA protected title, same as Square Enix had available for FF7.
  15. The non-Steam version of FF7 is already covered on the article: https://www.pcgamingwiki.com/wiki/Final_Fantasy_VII_(2012) It's the "Retail" row in the availability table as well as the note below the table.
  16. From: https://techraptor.net/gaming/news/doom-eternals-latest-update-breaks-game So based on the sounds of it, hopefully a fix for Proton will be implemented soon.
  17. Ah yes, so should our "XInput-compatible controllers" rows (pertains to the XInput API for controllers), and the DualShock 4 rows (pertains to DirectInput / DS4 HID APIs), as well as the "Generic/other controllers" rows as well (pertains to, well DirectInput as well, I guess). After all, you can't interface with a controller without using some form of API... The "Steam Input API Support" row should definitely not solely go in the API section since it pertains to Steam Input support as a whole, which is covered by it as well as the rest of the rows under the Input header. I ain
  18. An hour later and I've finally, hopefully, mostly, finished consolidated the information and replaced the Editing Guide sections on the infobox game and infobox non-game with their underlying respective documentations. Casualty of war was details pertaining to Infobox game/row/date as that is just too much to properly showcase in the table in either docs, and so details are now placed on its own documentation instead. Note to future self on this particular subject: Replace infobox non-game with infobox software entirely? Infobox controller, company, and console ne
  19. This is simply because I lost track of it after having spent a couple of days reworking the template documentation among other things. I have, for a while now, intended to essentially move/replace/merge the Editing Guide with the actual template documentations so the same stuff is present on both places. This is easier said than done though, as I need to go through all existing information on both pages and consolidate them as they have had a few years to drift away from one another in terms of what they document or the degree of information they provide. While also doing that, especially
  20. Wasn't that what broke the old plugin to begin with? It had a very simple parserfunction-style call that somehow was enough to break stuff that weren't even supposed to run at the same time.
  21. I don’t see why we shouldn’t try it out. I never did understand why we used a custom extension when there were multiple ones available. But perhaps it was a different time back in the day.
  22. That was primarily to prevent the section from taking up huge space on top of the article while still allowing it to grow to whatever space is deemed necessary by editors to properly document the various alternative methods available. I sorta fail to see the relevance of having an entirely new section dedicated to that right now. Does anyone actually choose what game to (re)play based on whether the cutscenes of the game are skippable or not? Right now the mention of that new sections and tracking the cutscenes sounds more like an attempt to validate moving the skip intro sectio
  23. “Essential” as a word is fine IMHO, and attempting to separate it into two is just going to cause more confusion. For patches, only the latest patch is usually the one being included, and it is essential because updating a game to the latest version /is/ essential. It doesn’t matter what the patch itself includes, just that information on how to update an outdated copy is available. Our articles are also meant to reflect the latest patches alone, and so outdated fixes are removed from the article when a patch have fixed them. So to actually read the article properly, an updated copy is
  24. Pretty much what Mirh said. When I was a wee bit newbie just starting out with PCGW editing I also brought it up and was subsequently outvoted. But nowadays I would actually argue to leave it alone over moving it. It is often mentioned as one of the key enjoyments of PCGW, meaning it should be featured more prominently than stuffed away in a rarely seen section. As Mirh mentioned it is also for many games the one fix/improvement we provided. And another, for me critical, reason to retain it as is is that it also serves a triple-purpose in basically: provides a basic and
  25. This, pretty much. The discussion, as short as one would be, could mostly be boiled down to whether a game was released before or after on a platform after said platform received support for achievements. If before, very rare to have support for achievements. If after, rare to not have support for achievements. Provided the game includes achievements on any other platform to begin with, of course.
×
×
  • Create New...