User talk:Ezra

(Redirected from User talk:Gamerappa)

Question about the "Builds that I have tried" section of profile[edit source]

Is that a beta upgrading project or is it the builds that you tried? BGRComputers.co (talk) 03:08, 8 August 2021 (UTC)

Maybe? I was recording both Build 6469 and 6519 for a video. -Gamerappa (talk) 03:10, 8 August 2021 (UTC)

Windows 10 9900 demo image[edit source]

Why did you revert my edits on the build 9900 demo picture? My version is perfectly fine. Wabbah (talk) 23:04, 11 August 2021 (UTC)Wabbah ( TerrificConnect on YouTube)

The original one was perfectly fine. Gamerappa (talk) 23:04, 11 August 2021 (UTC)

Not this again...[edit source]

A user Creek951 has created a page "X69" which is basically a vandal. BGRComputers.co (talk) 02:32, 15 August 2021 (UTC)

don't worry, he's bill gates :P -Gamerappa (talk) 02:35, 15 August 2021 (UTC)
I also told Hounsell that I wish that page was deleted. BGRComputers.co (talk) 02:36, 15 August 2021 (UTC)
jokes aside, are you sure you are sending this to the right person? -Gamerappa (talk) 02:41, 15 August 2021 (UTC)
Yes, I am. BGRComputers.co (talk) 02:42, 15 August 2021 (UTC)
alright then... so. wasn't creek the kid that that "Hi and this is awesome" article? -Gamerappa (talk) 02:45, 15 August 2021 (UTC)
Yes, it is that same person/user who created that page which is spam. BGRComputers.co (talk) 02:47, 15 August 2021 (UTC)
Action will be taken by the BetaWiki staff. -Gamerappa (talk) 02:52, 15 August 2021 (UTC)

New demo image on the last pre-RTM build of Windows XP[edit source]

Will it be okay if I make a new demo image of the last pre-RTM build of Windows XP with the Luna theme, being properly cropped, and not having custom stuff? Wabbah (talk) 19:09, 16 August 2021 (UTC)Wabbah

sure Gamerappa (talk) 19:32, 16 August 2021 (UTC)
Okay, I'll do the image on August 24. Wabbah (talk) 21:04, 16 August 2021 (UTC)Wabbah

Longhorn 4074 kernel swapping?[edit source]

Is there a particular reason some stranger and then you decided to remove my attempt at showcasing that the build can boot off of a more up to date kernel? It's obviously not a vanilla thing to do for the OS, but neither is running these builds at all, so I felt that any attempt to bring them some stability would have been welcomed when I decided to add the snippet. I even gave room with the extra section for others to post their own findings, and explicitly did so on the page for build 4074 because I didn't want to clutter other pages with what might have been explicitly a 4074 thing - I don't know yet. I mean I completely understand if it sounds like an absurd thing to have done, but this level of experimentation comes off of a background of growing up with Windows and Linux both, so these are the kinds of tinkerings you're going to see from me when it comes to Windows. And I've got the proof, you can go do this yourself if you just didn't believe it was legit: https://files.joshuadoes.com/Windows%20Longhorn%204074%20(Powered%20by%20NT%20Kernel%20from%20Windows%207%20SP1%207601).png — Preceding unsigned comment added by JoshuaDoes (talkcontribs)

This isn't Kernel Swapping Wiki, that's entirely out of the wiki's scope and a use case that a good 0.0001% of users will ever have. Orbitron (talk) 06:03, 12 January 2023 (UTC)
Again, this isn't Kernel Swapping Wiki, so it's better to post your findings elsewhere. NaraInsider1694 (talk) 06:18, 12 January 2023 (UTC)
OS mods are out of scope. And since this is essentially an OS mod, well... --Ryuzaki (talk | contribs) 10:15, 12 January 2023 (UTC)
The build number being reported is 4074. If I remember correctly, winver and the desktop watermark get the build number from the kernel that’s in memory. Basically, despite the kernel file from 7601 being put in system32, it has not replaced the 4074 one in memory. Booting 4074 with tbe 7601 kernel will crash. -Gamerappa (talk) 11:54, 12 January 2023 (UTC)

Booting 4074 with the 7601 kernel does not crash, you can again test this yourself and even see the video mode reset during bootanim if you're using VMWare at least. And apparently in this case no, winver pulls from either another file or from registry, clearly not ntoskrnl.exe. But understood about not posting mods then, just keep up that energy for everyone else too please, I've seen others wanting to reference different projects as well (such as TWIWMTB and Reloaded etc) with some considerations JoshuaDoes (talk) 17:40, 12 January 2023 (UTC)

I have a feeling that the Windows File Security Protection thing or whatever it's called had reverted the file swapping, thus giving the impression that this "hack" worked. -Gamerappa (talk) 21:32, 12 January 2023 (UTC)

I just feel that if that was the case, the file wouldn't have persisted across multiple reboots, even after removing the .old listed in that screenshot JoshuaDoes (talk) 22:10, 12 January 2023 (UTC)

Sorry for the double comment but it's verified the 7601 file when checking with the VM image mounted too, and I also did the replacement in this same way, not from within the OS JoshuaDoes (talk) 22:14, 12 January 2023 (UTC)

I'm pretty sure the system will instantly crash when booting with the new kernel. Remember, Longhorn build 4074 is from 2004, while Windows 7 SP1 (build 7601) is from 2010, so it's clear that you cannot boot build 4074 with a kernel from six years later. NaraInsider1694 (talk) 01:54, 13 January 2023 (UTC)
It's worth noting that Windows does not have a stable syscall interface across versions, in fact not even Service Packs. It is almost certain that Windows ends up booting with the original kernel for one reason or another. --Ryuzaki (talk | contribs) 09:19, 13 January 2023 (UTC)

I've done some further investigation, and I was wrong full stop - but not for the main reasons we originally thought, it's just that my particular setup chainloads into ntkrnlpa.exe instead of ntoskrnl.exe. You are right that it's unstable also and not compatible out of the box, given the 6 year stretch of time in-between the changes. I've shifted to making attempts to compile the leaked 2003 kernel source code instead, as it's likely to be a lot closer in API and then I can see about restoring the remaining missing methods (if any) JoshuaDoes (talk) 01:13, 14 January 2023 (UTC)