Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 11/29/2020 in Posts

  1. Status Update: I am mostly ready to release Beta 3 of KernelXE. Here is what I have done so far: kernel32: Removed "mov edi, edi" from the beginning of some functions. ntdll: I reset development for ntdll and started from "scratch" (WildBill's ntdll). Added exports for: NtLockProductActivationKeys RtlLogStackBackTrace _swprintf Added functions: NtDeleteBootEntry NtModifyBootEntry NtAddBootEntry NtEnumerateBootEntries NtQueryBootEntryOrder NtQueryBootOptions NtSetBootEntryOrder NtSetBootOptions NtEnumerateSystemEnvironmentValuesEx NtTranslateFilePath NtQuerySystemEnvironmentValueEx NtSetSystemEnvironmentValueEx RtlDllShutdownInProgress RtlInterlockedCompareExchange64 RtlInterlockedPushListSList RtlIsCriticalSectionLockedByThread RtlNewSecurityObjectWithMultipleInheritance RtlGetLastNtStatus RtlGetLastWin32Error EtwEventRegister EtwpCreateEtwThread RtlRunOnceComplete Nt/ZwReleaseKeyedEvent (Code redirection to ntoskrnl) RtlInitializeConditionVariable RtlInitializeSRWLock RtlRunOnceInitialize RtlWakeAllConditionVariable RtlWakeConditionVariable _CIcos _CIlog _CIsin _CIsqrt _alloca_probe_16 _alloca_probe_8 ntoskrnl: Added functions: Nt/ZwReleaseKeyedEvent (Not exported, added to KiServiceTable) ExfAcquirePushLockExclusive ExfAcquirePushLockShared ExfReleasePushLock Added exports for: ObSetSecurityObjectByPointer SeTokenObjectType NtAssignProcessToJobObject NtCreateJobObject NtOpenJobObject NtQueryFullAttributesFile NtQueryInformationJobObject NtQueryInformationThread NtSetInformationJobObject NtTerminateJobObject ZwAssignProcessToJobObject ZwCreateJobObject ZwOpenJobObject ZwQueryFullAttributesFile ZwQueryInformationJobObject ZwSetInformationJobObject ZwTerminateJobObject NtOpenThread To-do before release: kernel32: Try a few things to maybe fix CreateActCtxW ntkrnlmp, ntkrnlpa, ntkrpamp: Everything done to ntoskrnl Plans for future: Fix Dependency Walker and CFF Explorer crashes (this one has been around since the original KernelXE and I still haven't figured out why they happen) Add PAE through "/PAE" in boot.ini
    2 points
  2. The ones not affected by this would have some dried-up capacitors by now anyways. It isn't that hard to replace faulty capacitors, and the blown-up ones are much easier to spot than the dry ones. The only real issue would be damage around the capacitor caused by the leaked electrolyte.
    1 point
  3. Based on further review of Chromium behaviour, it seems that on both Vista and 7 it does the same procedure to check for locales, using functions introduced in Vista or earlier. The error message indicates that the default locale is defined, but default data is not, presumably referring to the manifest data for the extensions. The nuclear solution would be to modify ntoskrnl and set its RtlGetVersion (also PsGetVersion to be sure, even though it is obsolete as of XP) to 6.1.7601, thus everything in kernel mode would think they are running on Windows 7. Personally I connect my GPU to my 15 year old monitor with DVI, and use Realtek onboard HD audio. On another note, the user-mode version check bypass in ntext is not as effective as possible, as I realized that VerifyVersionInfo functions call RtlVerifyVersionInfo which is presently only in ntdll, and thus uses ntdll's RtlGetVersion. However, RtlVerifyVersionInfo is a bit of a handful, and with the limitations on implementing ntext functions, it will take awhile.
    1 point
  4. Thank you for your reply, Alacran. I understand the points you made, but to me it would still be useful if Grub4UEFI could support my scenario on GPT, similar to the way I use Grub4DOS on MBR now (and have done for years). I like to have a few Windows operating systems on seperate (indepentant/ hidden) partitions. For example: one for "work", one for dev, one for testing, etc. I also liked the Grub4Dos/ GFXCustomizer boot menus (as I've mentioned before). I would also like to reverse the question: "Why would Grub4UEFI -not- support it?". When the different OS's are independent and invisible from each other, it's easier to make OS image backups (Terabyte, etc.). Thanks again for your reply, I know you're more interested in the VHD approach, but I hope that if you ever find some hints to my desired solutions, you will share it with us in this or other topics, as I'm sure you will. I hope you're having fun booting!
    1 point
  5. Hey all, my name is Andy, but my screen name is Anshu. I live in the United States, and I daily drive Windows 7 and Windows Vista. God bless you all, and I hope to be a great help to the community!
    1 point
  6. Aside from myself, I believe there are several other people around these parts who use Athlon XP machines, which lack SSE2, yet do feature SSE. I appreciate @roytam1 doing regular builds for these old processors.
    1 point
  7. Your avatar (or whatever it's called) says you are on XP so the answer is "neither", use the "real" version that has no SSE or IA32 in the name. Technically the answer is determined by your CPU and not your operating system. Use the "real" version unless your computer is so old that it came with Win 98 or Win 2000. If it came with Win XP then the SSE and the IA32 aren't for you. At least that's how I understand it.
    1 point
  8. It worked like that before the extended kernel. This game is based on x86 architecture, even without kernelex it works fine for me, only giving an error at the beginning, which does not affect the work in the future. And it works because the game itself is made on net. framework 4 which supports Windows Vista
    1 point
×
×
  • Create New...