@serjer
Yes and no.
I've been testing it intensively over the past week and the ntoskrnl.exe of this latest build has some issues. It has been generating a lot of stop errors as of late for myself and a few others I know. Mainly:
stop error: 0x0000000A
I managed to fix it by running by win2K boot/installer CD (with SP2) and then going through repair mode (R). Emergency repair didn't do anything, so I opted for manual repair. There go through the changes that you think are responsible. I was a little lazy and opten for all changes, and then I only had to re-install OfficeXP because it removed a couple of registries from it (but had I taken the time to be more selective I could have avoided that). So basically I'm on a hybrid version of win2K a la SP2 & SP4 lol.
Still not everyone I know had these issues, so could be software or hardware we have installed. If you run into issues I suggest you try this method of repair, however, if your PC is running fine now, leave it be!!
Good luck.
