Remember the WinXP emulation threads from a few days ago?/v/751343089/v/751627407The current state of XP gaming on modern hardware is a mess:86Box: Cycle-accurate, which means single-thread bottlenecked to hell for anything past a Pentium II.QEMU-3dfx: A CLI/WHPX nightmare held together by guest-side wrapper duct tape and sketchy binaries.VMware / VBox: Dropped proper legacy 3D support years ago and pollute your host with ring-0 kernel driver bloat.Got tired of bitching about it and started building Y2KBox: a containerized, click-and-play WinXP emulator with native-ish 3D acceleration and zero host driver clutter.Repo: https://github.com/AhayriSG/Y2KBoxHere's the twist: the repo is structured for completely hands-off, autonomous LLM development. The README.md acts as a self-contained architecture spec, build guide and task queue.If you have Claude (even just the web version connected to GitHub), literally just point it at the repo and tell it: "Read the README, pick an open task, build/test it, and open a PR." That's it. you don't have to write a single line of code or babysit it. You can give it the prompt, close your browser, and let it run in the background.PRs are wide open.
>vibe coded slopUh... yeah. No thanks, bro.
>>751738046Bruh.. the alternative is waiting another 10 years for two autistic wizards on a forum to finish reverse-engineering GeForce 4MX in their spare time.
>>751738181>GeForce 4MXYou don't need it.
>>751738343yeah yeah, whatever..
>>751736912Pretty cool but you would unironically get more traction shilling this on Reddit. /v/ is too overrun with brownoids that only care about jerking off to gachashit now
>>751739565>/v/ is too overrun with brownoids that only care about jerking off to gachashit nowYeah, I guess so. It's kind of tiring to even look at the catalog nowadays.
>>751739565Fuck reddit tho.Bc Reddit isn't even a sewer; it's a septic tank with an echo chamber
>>751738181>Import upstream QEMUSo, it's just rebadged QEMU.I don't get what's the point. Most Windows XP games run fine on modern systems, and if they don't it's easier to just use some fan patches.Windows 3.0/3.1 and Windows 95/98 games are in a bigger need of a new compatibility tool.Besides that, emulationg a whole 2000's x86 machine is unnecesary overkill when you are going to run that emulator on a x86 PC. The performance is going to be abbysmal.
>>751740227>Windows 3.0/3.1 and Windows 95/98 games are in a bigger need of a new compatibility tool.Win9x is already solved. 86Box, DOSBox-X and DOSBox Pure handle D3D1-7 and Glide easily. XP and D3D8-9 is the actual blind spot right now.>I don't get what's the point. Most Windows XP games run fine on modern systems, and if they don't it's easier to just use some fan patches.>>751344670
>>751740532I don't think that a vibecoded QEMU modification is a right way for futureproofing Windows XP games. D3D8-9 already have various wrappers like dgVoodoo 2 and a vibecoded emulaot full of spaghetti code neither efficent nor possible to maintain over long periods of time.
>>751740968>full of spaghetti codeYeah, I'm having Claude gut the bloat: stripping out hypervisor related stuff, legacy archsslop, and unrelated subsystems to lock it strictly to x86-64-v3 hosts (Windows/Linux) and 32-bit XP guests (up to SSE2 CPU emu). Lean, optimized, improved TCG + vGPU, nothing else.>I don't think that a vibecoded QEMU modification is a right way for futureproofing Windows XP emulationCompared to what tho? Literally nobody else is building a dedicated XP emulation solution. Right now our only option is running games natively on modern Winblows through WoW and wrappers, which is a ticking time bomb. Microsslop silently breaks legacy stuff, hooks, DRM, and old D3D behavior with every major update. I believe self-contained emulator solution is the only real futureproofing.https://emulation.gametechwiki.com/index.php/Windows_NT_5.x_emulators#Recommended_solutions:~:text=Intel%E2%80%99s%20proposed%20x86,UserRegisterWowHandlers%20case.