User talk:Xeno

Infoboxes on Microsoft Bob

You can use the "Infobox software version" template for Microsoft products. I will add it to the pages for you. ToMi (talk | contribs) 07:32, 9 February 2021 (UTC)

Forgot to reply, but thank you for letting me know! I'm still new to MediaWiki's tools - Xeno (talk | contribs) 07:32, 9 February 2021 (UTC)

You're welcome. ToMi (talk | contribs) 18:48, 18 February 2021 (UTC)

Themes on 4042.main

Hey Xeno, I know this is pretty random, but did you get the theme service working normally on the main compile of 4042? Not sure if you even tried the build but I tried to upgrade many times and when I did, the theming service would be messed up. Something about missing files. --ATeamInc (talk) 23:29, 9 March 2021 (UTC)

I'll have to take a look myself sometime tomorrow then. When I did my upgrading, I wasn't able to get an upgrade to 4042. What build are you upgrading from? Xeno (talk) 23:31, 9 March 2021 (UTC)

I don't really remember but I think it was 4039 or 4040. On your BA thread you tried to upgrade from 4033 IIRC. What bothered me is that this happened for me even on a clean install as well (not sure why, I mean it could be hardware related but it happened on both VMware 7 and 15.5). But I am pretty sure that this build had this problem although not one-hundred percent sure about the upgrade thing.

Actually, I might as well give it a try. Why not. ATeamInc (talk) 23:37, 9 March 2021 (UTC)

Yeah let me know how it goes! I'll give the upgrade sometime tomorrow. Xeno (talk) 23:38, 9 March 2021 (UTC)

Script Errors for 408x and 4093

If you want script errors, open up services.msc and you will see that it is not normally usable in the "Enhanced" mode, complains about some error in the scripts. Some registry entry fixes this, but I have not been able to actually properly reproduce this yesterday because I kept getting Access is Denied error each time I tried to import the 4074 registry and then override with 4093's one (which worked fine in the past).

Opening the .NET Framework snap-in (I actually forgot its name whoops) also doesn't display properly because it actually shows the source HTML for the snap-in. You can actually see that over 50% of the snap-ins are not even properly registered and they won't show up in the Add Snap-Ins command. ATeamInc (talk) 06:29, 15 March 2021 (UTC)

The only real issue I had with snap-ins on a clean install was Disk Management crashing Computer Management Xeno (talk) 22:05, 15 March 2021 (UTC)

Guess I can hate Longhorn in peace then for ruining my day, seriously the amount of bugs I encountered today must be illegal. --ATeamInc (talk) 22:07, 15 March 2021 (UTC)

How are you running these builds? VM or on a physical machine? Xeno (talk) 22:08, 15 March 2021 (UTC)

VMware Workstation 7.1.4. I was able to actually do a lot and stuff worked fine in the past but today I am plain unlucky (same PC, same VM specs, same ISOs too).

If you're curious: What I do to 4093 is grab a directly installed copy of it and then copy everything in the system folders to an i386 directory, get the filerepository and delete all component.man files before copying everything to the same i386 directory (without overrides). I install 4074 on a VM with the same specs and then I copy its drive over, and I override every found file with a one in the i386 directory created earlier. And then I simply copy the 4093 installed copy over this hack-a-job, delete everything on the system drive except the System Volume Information, put all those directories and boot the VM. Once I boot back in I import a copy of 4074's SOFTWARE registry and then I directly override it with the one for 4093.

This crazy procedure worked in the past and helped me get rid of a lot of bugs and stabilized the system a lot but I can't get it to work anymore. Yesterday I kept getting Access is Denied errors and today explorer would plain not start after the file copy and before the registry thing. So I just gave up.

What's odd is that the system date has strange effects on what bugs I got. Not fun. --ATeamInc (talk) 22:34, 15 March 2021 (UTC)

Interesting. I've just been doing clean installs on my Dell Dimension (Specs on main page). To me, swapping out files with other builds isn't really fun. Except when upgrading, that can work wonders in upgrading to some builds that cannot normally be upgraded to. Xeno (talk) 22:37, 15 March 2021 (UTC)

A more accurate representation for this would be a proper directory build. When Windows can't find the files it needs, stuff get messed up. Most of the files are located in the filerepository so what you would do with this is basically install Windows manually in some way. The only leftovers from 4074 would be stuff like sysprep, unmanaged DWM which doesn't work, and some device drivers which are oddly missing from 4093. I suspect a file swap would allow the safe mode to work, by the way. --ATeamInc (talk) 22:41, 15 March 2021 (UTC)

Upgrade error from build 5000 to build 5259 screenshot

That is weird, the new version of the screenshot that you uploaded still has the old version from 24 February 2021. --BGRComputers.co (talk | contribs) 02:01, 27 March 2021 (UTC)

Windows XP build 2600 RTM bug

Why do you think that some installs has a bug that may result in a zero-day activation, which is similar fashion to Windows Vista build 3790.1232? --BGRComputers.co (talk | contribs) 21:08, 2 April 2021 (UTC)

And also, there is a chance that attempting to activate Windows will result in no installation ID being generated, making the system unusable unless it is upgraded to Service Pack 1 or Service Pack 2 in some installs. --BGRComputers.co (talk | contribs) 21:11, 2 April 2021 (UTC)

I have no idea why, it seems to be mainly affecting XP OEM licenses . Almost I'm trying out SP1 RTM now, as the bug still exists in XP SP1 betas. Xeno (talk) 21:13, 2 April 2021 (UTC)