Leaderboard

Hello I am French I am a fan of Windows Longhorn and Windows Vista RTM here is my config

NTOSKRNL Emu_Extender Library of missing functions for Windows XP/2003/Vista/7 NTOSKRNL.EXE Project is intended to help in porting drivers from Windows 7/8/8.1/10 for work with Windows XP/2003/Vista/7 How-To: Compile sources to make ntoskrn8.sys Make corrections to target driver XXX.sys so that it loads ntoskrn8.sys instead of the original ntoskrnl.exe If XXX.sys is driver made for Windows 8, change security_cookie to random value, security_cookie is constant 0x4EE640BB(x32) / 0x32A2DF2D992B(x64) inside file, change only first match ! Place ntoskrn8.sys to X:/Windows/system32/drivers/ folder Compiling: 1) Install Windows 7 DDK v7.1.0 (download from Microsoft site) 1a) Original DDK header files has mistake with definintion of MmAllocateContiguousMemorySpecifyCacheNode, apply fix to two files \WinDDK\Win7\inc\ddk\ntddk.h and \WinDDK\Win7\inc\ddk\wdm.h: replace: #if (NTDDI_VERSION >= NTDDI_WIN2K) typedef ULONG NODE_REQUIREMENT; to: #if (NTDDI_VERSION >= NTDDI_VISTA) typedef ULONG NODE_REQUIREMENT; 2) Download project files to any local folder git clone https://github.com/MovAX0xDEAD/NTOSKRNL_Emu 3) Choose Target OS (XP, 2003, Vista or WIndows 7) for which OS Emu_Extender will be compiled. Keep in mind that depending on the target operating system the way of exporting the functions changes, if a function already exists in the kernel it will be simply redirected without injecting emulation code 4) Run shell: "Start Menu\Programs\Windows Driver Kits\Win7 7600.16385.1\Build Environments\Windows XXX\YYY Free Build Environment" (XXX - target OS, YYY - target CPU) 5) In shell change current directory to local project folder 6) Use shell command BLD to compile project 7) Compiled ntoskrn8.sys will be in ntoskrn8/objfre_XXX_x86/YYY folder STORPORT Windows 7 Emu_Extender This is Library of missing functions for Windows 7' STORPORT.SYS v6.1.7601.23403 to emulate Windows 8' STORPORT.SYS How-To: Compile ntoskrnl Emu_Extender Place storpor8.sys to X:/Windows/system32/drivers/ folder Make corrections to target xxx.sys so that it loads storpor8.sys instead of the original storport.sys Place backported storport.sys from Windows 7 to X:/Windows/system32/drivers/ folder Ported drivers: Windows 7's WDF 1.11 for Windows XP/2003 x32 Last version for Windows XP/2003 is 1.9, but possible to backport 1.11 version: 1) Get files from Windows 7 Updates (KB3125574): WDF01000.SYS v 1.11.9200.20755 WdfLdr.sys v 1.11.9200.16384 2) In WDF01000.SYS replace string ntoskrnl.exe to ntoskrn8.sys in import section 3) Recalc checksum If need coexist with original WDF1.9 drivers: 4) Rename WDF01000.SYS->WDF01_W8.SYS, WdfLdr.sys->WdfLdr8.sys 5) In WDF01_W8.SYS replace string WdfLdr.sys to WdfLdr8.sys in import section 6) In WdfLdr8.sys replace unicode string \Registry\Machine\System\CurrentControlSet\Services\Wdf%02d000 to \Registry\Machine\System\CurrentControlSet\Services\Wdf%02d_w8 7) In WdfLdr8.sys replace hex pattern F6 78 1B F6 to F6 EB 1B F6 (x32), ** ** to ** ** (x64) 8) In target driver XXX.sys replace string "WdfLdr.sys" to "WdfLdr8.sys" in import section 9) In .INF of ported driver add creating new service: AddService=WDF01_W8,, WDF.AddService .... [WDF.AddService] DisplayName = "Windows Driver Framework v1.11 for XP/2003" ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %12%\WDF01_W8.SYS LoadOrderGroup = Base Recalc checksum of all edited *.sys Windows 7's Storport.sys for Windows XP x32 Storport was released since Windows 2003, but possible to backport Windows 7 version: 1) Get files from Windows 7 Updates (KB3125574): storport.sys v 6.1.7600.23403 2) In storport.sys replace string ntoskrnl.exe to ntoskrn8.sys in import section, now storport.sys will import all kernel functions only from Emu_Extender 3) Storport uses MSI interrupts, need to force use only legacy/compatible interrupts x32 - replace hex pattern 8B 8E 3C 01 00 00 to B9 00 00 00 00 90 (mov ecx, [esi+13Ch] -> mov ecx, 0) x64 - replace hex pattern 8B 83 C0 01 00 00 to B8 00 00 00 00 90 (mov eax, [rbx+1C0h] -> mov eax, 0) 4) Recalc checksum Windows 7's NVMe driver for Windows XP x32 1) Get files from Windows 7 Updates (KB3125574): stornvme.sys v 6.1.7600.23403 2) MS Win7 NVMe driver require Win7 Storport.sys, use backported one Windows 8's USB3 driver for Windows XP x32 1) Get required files from Windows 8 (KB4534283/4556840, KB2984005, RTM ISO): ucx01000.sys v6.2.9200.22453 usbhub3.sys v6.2.9200.21180 usbxhci.sys v6.2.9200.22099 wpprecorder.sys v6.2.9200.16384 usbd.sys v6.2.9200.20761 from Vista Beta/Longhorn 5456.5: ksecdd.sys v6.0.5456.5 2) In files ucx01000.sys, usbhub3.sys, usbxhci.sys, wpprecorder.sys, usbd.sys change security_cookie to random value 3) In files ucx01000.sys, usbhub3.sys, usbxhci.sys, ksecdd.sys replace string name "ntoskrnl.exe" to "ntoskrn8.sys' in import section 4) Rename ksecdd.sys->ksecd8.sys, usbd.sys->usbd_w8.sys 5) In usbhub3.sys replace string name "ksecdd.sys" to "ksecd8.sys' in import section 6) In usbhub3.sys replace string name "usbd.sys" to "usbd_w8.sys' in import section, 7) recalc checksum Windows 8’s STORAHCI driver for Windows XP x32 STORAHCI driver requires storport.sys from Windows 8, but possible to use storport.sys v6.1.7601.23403 from Windows 7 Storport.sys from Windows 7 more compatible with Windows XP/2003 because it still call required PoStartNextPowerIrp when processing power IRPs. Microsoft removed calls to PoStartNextPowerIrp in Windows 8's storport.sys, without this call Windows XP/2003 kernel cannot finish current power IRP and start next IRP => it generate BSOD (0x0000009F). Also storport.sys from Windows 7 has compatibility mode to allow old XP/2003 kernels write crashdumps through storport based disk drivers. In storport.sys from Windows 8 compatibility mode was removed, writing crashdumps possible only with new kernels. Take attention: Windows 8's STORAHCI + Windows 7's STORPORT may have significal performance drop and high CPU usage, there is no fix yet 1) Get files from Windows 8 (RTM ISO): storahci.sys v 6.2.9200.16384 2) In storahci.sys replace string storport.sys to ntoskrn8.sys in import section 3) Storahci.sys was compiled with Windows 8 DDK's storport.h and writes values to new fields of _PORT_CONFIGURATION_INFORMATION struct, these fields not exist in Windows 7's storport.sys. Need to skip these writes to avoid damaging other structures in memory x32: Replace hex pattern 83 A6 C8 00 00 00 00 to 90 90 90 90 90 90 90 (and dword ptr [esi+0C8h], 0 -> nop) Replace hex pattern 83 8E CC 00 00 00 03 to 90 90 90 90 90 90 90 (or dword ptr [esi+0CCh], 3 -> nop) x64:Replace hex pattern 44 89 B7 D8 00 00 00 to 90 90 90 90 90 90 90 (mov [rdi+0D8h], r14d -> nop) Replace hex pattern 83 8F DC 00 00 00 03 to 90 90 90 90 90 90 90 (or dword ptr [rdi+0DCh], 3 -> nop) If you want compile storahci from sources (from Windows 8 DDK Samples), comment two lines ConfigInfo->BusResetHoldTime = 0; ConfigInfo->FeatureSupport |= STOR_ADAPTER_FEATURE_STOP_UNIT_DURING_POWER_DOWN; 4) In storahci.sys change security_cookie to random value 5) Recalc checksum Windows 7’s MSAHCI driver for Windows XP x32 1) Get files from Windows 7 Updates(KB3125574): atapi.sys v 6.1.7600.23403 ataport.sys v 6.1.7600.23403 msahci.sys v 6.1.7600.23403 pciidex.sys v 6.1.7600.23403 2) In ataport.sys, pciidex.sys replace string ntoskrnl.exe to ntoskrn8.sys in import section 3) Pciidex.sys uses MS Internal/Undocumented HalDispatchTable way to call functions from Kernel/HAL, for Windows XP/2003 need to use compatible variant: x32: Replace hex pattern FF 50 3C to FF 50 40 same in asm code: mov eax, ds:HalDispatchTable ... call dword ptr [eax+3Ch] => call dword ptr [eax+40h] x64: Replace hex pattern FF 50 78 to EB 2A 90 Replace hex pattern at offset +2Ch: CC CC CC CC CC CC CC CC to FF 90 80 00 00 00 EB CF, same in asm code: mov rax, cs:HalDispatchTable ... call qword ptr [rax+78h] => jmp patch orig: mov r10d, eax patch: call qword ptr [eax+80h] jmp orig 4) Recalc checksum 5) MSHDC.INF from Windows 7 conflict with original mshdc.inf from Windows XP/2003. msahci.sys enumerates IDE/SATA channels as "Internal_IDE_Channel" and compatible ID is "*PNP0600". Original mshdc.inf from Windows XP/2003 for compatible Device ID "*PNP0600" will install wrong "Standard IDE/ESDI Hard Disk Controller" driver Intel RSTe (Enterprise/Premium) AHCI/RAID driver 4.7.0.1098 for Windows XP/2003 Intel RST AHCI/RAID drivers (any version, last compatible is 16.8.3) for Windows XP/2003 These drivers require storport.sys from Windows 7, use backported version. 1) In file iaStorA.sys/iaStorAC.sys/iaStorAVC.sys replace string “ntoskrnl.exe” to “ntoskrn8.sys” in import section (do not change second string “NTOSKRNL.exe”) now these *.sys will import kernel functions only from Emu_Extender 3) Recalc checksum Implemented Func List v60: _chkstk _i64toa_s _i64tow_s _itoa_s _itow_s _ltoa_s _ltow_s _makepath_s _snprintf_s _snscanf_s _snwprintf_s _snwscanf_s _splitpath_s _strnset_s _strset_s _strtoui64 _swprintf _ui64toa_s _ui64tow_s _ultoa_s _ultow_s _vsnprintf_s _vsnwprintf_s _vswprintf _wcsnset_s _wcsset_s _wmakepath_s _wsplitpath_s _wtoi _wtol DbgkLkmdRegisterCallback EmClientQueryRuleState EtwActivityIdControl EtwEventEnabled EtwProviderEnabled EtwRegister EtwRegisterClassicProvider EtwUnregister EtwWrite EtwWriteString EtwWriteTransfer ExAcquireRundownProtectionCacheAware ExAcquireRundownProtectionCacheAwareEx ExAllocateCacheAwareRundownProtection ExDeleteLookasideListEx ExEnterCriticalRegionAndAcquireFastMutexUnsafe ExEnterCriticalRegionAndAcquireResourceExclusive ExEnterCriticalRegionAndAcquireResourceShared ExEnterPriorityRegionAndAcquireResourceExclusive ExEnterPriorityRegionAndAcquireResourceShared ExFreeCacheAwareRundownProtection ExfReleasePushLockShared ExfTryToWakePushLock ExGetFirmwareEnvironmentVariable ExInitializeLookasideListEx ExInitializeRundownProtectionCacheAware ExReInitializeRundownProtectionCacheAware ExReleaseFastMutexUnsafeAndLeaveCriticalRegion ExReleaseResourceAndLeaveCriticalRegion ExReleaseResourceAndLeavePriorityRegion ExReleaseRundownProtectionCacheAware ExReleaseRundownProtectionCacheAwareEx ExRundownCompletedCacheAware ExSetFirmwareEnvironmentVariable ExSizeOfRundownProtectionCacheAware ExWaitForRundownProtectionReleaseCacheAware IoAllocateSfioStreamIdentifier IoConnectInterruptEx IoDisconnectInterruptEx IoFreeSfioStreamIdentifier IoGetActivityIdIrp IoGetAffinityInterrupt IoGetDevicePropertyData IoGetIoPriorityHint IoGetSfioStreamIdentifier IoInitializeWorkItem IoQueueWorkItemEx IoSetActivityIdIrp IoSetDevicePropertyData IoSizeofWorkItem IoUninitializeWorkItem IoUnregisterPlugPlayNotificationEx KdRefreshDebuggerNotPresent KeAcquireGuardedMutex KeAcquireGuardedMutexUnsafe KeAlertThread KeAreAllApcsDisabled KeEnterGuardedRegion KeExpandKernelStackAndCallout KeGetCurrentNodeNumber KeGetCurrentProcessorNumberEx KeGetProcessorIndexFromNumber KeGetProcessorNumberFromIndex KeInitializeGuardedMutex KeInvalidateAllCaches KeInvalidateRangeAllCaches KeLeaveGuardedRegion KeQueryActiveGroupCount KeQueryActiveProcessorCount KeQueryActiveProcessorCountEx KeQueryDpcWatchdogInformation KeQueryGroupAffinity KeQueryHighestNodeNumber KeQueryLogicalProcessorRelationship KeQueryMaximumGroupCount KeQueryMaximumProcessorCount KeQueryMaximumProcessorCountEx KeQueryNodeActiveAffinity KeReleaseGuardedMutex KeReleaseGuardedMutexUnsafe KeRevertToUserAffinityThreadEx KeRevertToUserGroupAffinityThread KeSetActualBasePriorityThread KeSetCoalescableTimer KeSetSystemAffinityThreadEx KeSetSystemGroupAffinityThread KeSetTargetProcessorDpcEx KeTestAlertThread KeTryToAcquireGuardedMutex LdrResFindResource LdrResFindResourceDirectory LpcReplyWaitReplyPort LpcRequestWaitReplyPortEx LpcSendWaitReceivePort memcpy_s memmove_s MmAllocateContiguousMemorySpecifyCacheNode MmAllocateContiguousNodeMemory ObDeleteCapturedInsertInfo ObfDereferenceObjectWithTag ObfReferenceObjectWithTag ObGetObjectType ObQueryNameInfo PcwAddInstance PcwCloseInstance PcwCreateInstance PcwRegister PcwUnregister PoDisableSleepStates PoEndDeviceBusy PoGetSystemWake PoReenableSleepStates PoRegisterPowerSettingCallback PoSetDeviceBusyEx PoSetSystemWake PoStartDeviceBusy PoUnregisterPowerSettingCallback PoUserShutdownInitiated PsAcquireProcessExitSynchronization PsEnterPriorityRegion PsGetCurrentProcessWin32Process PsGetCurrentThreadProcess PsGetCurrentThreadProcessId PsGetCurrentThreadTeb PsGetCurrentThreadWin32Thread PsGetCurrentThreadWin32ThreadAndEnterCriticalRegion PsGetProcessSessionIdEx PsIsProtectedProcess PsIsSystemProcess PsLeavePriorityRegion PsReleaseProcessExitSynchronization PsSetCreateProcessNotifyRoutineEx RtlCheckPortableOperatingSystem RtlGetIntegerAtom RtlGetThreadLangIdByIndex RtlIsNtDdiVersionAvailable RtlQueryElevationFlags RtlQueryRegistryValuesEx RtlSetPortableOperatingSystem SeReportSecurityEventWithSubCategory SeSetAuditParameter SeSetAuthorizationCallbacks sprintf_s sscanf_s strcat_s strcpy_s strncat_s strncpy_s strnlen strtok_s swprintf_s swscanf_s vsprintf_s vswprintf_s wcscat_s wcscpy_s wcsncat_s wcsncpy_s wcsnlen wcstoul ZwAllocateLocallyUniqueId ZwAlpcConnectPort ZwAlpcSendWaitReceivePort ZwQueryLicenseValue ZwQueryVirtualMemory Download Sources https://github.com/MovAX0xDEAD/NTOSKRNL_Emu

For web pages displayed in russian or in chinese, there is 2 solutions : https://msfn.org/board/topic/178380-extreme-explorer-360-chromium-78-general-discussion/?do=findComment&comment=1174038 https://msfn.org/board/topic/178380-extreme-explorer-360-chromium-78-general-discussion/?do=findComment&comment=1175311

Not sure if i understood properly, but... Do not try to pull the motherboard side connector, you may break the traces leading to it (and do other damage too). Better to directly solder the cable to its pins. Or pull the pins out of the battery connector, wrap each in some isolation, and plug them in this way. Make notes of the polarity - connecting in reverse may fry the mobtherboard! FYI 3-pin batteries have either one pin unused, or two of the pins shorted. You can just change the connector and use them. If there is enough space, you can get a battery holder and connect that instead. Then you can easily change just the cell.

Usually there is some double sided sticky tape to hold the CMOS battery. Get anyway the specific service manual: http://tim.id.au/laptops/asus/s96j.pdf each model may be slightly different. jaclaz

We have absolutely no idea how long it takes. It could take a full week or it could take 12 hours. We have no idea. This is what I mean with speculation. Did he ever share any info regarding what it takes to update? How big of a chance is there even that this can cause bugs? And if a lot of bugs can be there does he have a very solid way of fixing these with some kind of debugging software perhaps? And having an application without bugs is pretty logical yes. I don't see how that changes anything in this particular situation. We still don't know how much testing is actually done each update. Also, the application is not free. If you can pay for it how is it free? Unless you can pay for the application and your payment changes nothing. You would have the exact same feature set with no downsides. That's what we call an donation. This is clearly a trial/demo. Anyway, I appreciate what BigMuscle is doing because I think this isn't an easy task. He is probably doing this for himself and a small group of people. At least I think so. Like I said, I'm speculating just as much as all of you. I just wanted to get this off my chest. I understand most of the people present on this section of the forum will probably disagree with me or think I don't appreciate what he has created. There is no need for me to make everyone uncomfortable (hopefully I didn't) for a long period of time with replies going back and forth. I really don't want that. The world is already in a full epidemic at the moment. So I just wanted to share what I think, considering this thread was somewhat steering towards the topic. So yeah, be safe and sorry for waltzing in here with my skepticism. I'm just a user like all of you and I can be a bit harsh with what I say. Good day everyone! EDIT: Thinking about it a bit more, I think I might've been a bit too harsh/distrustful. See it as simple food for thought for now, or something. I'm probably overthinking things.

I seems like that specific Asus model has a "standard" battery connector, but you need to check anyway before ordering it, basically there are both 2 pin and 3 pin connectors, the s96J seems like having a three pin one: http://www.genuine-cmos-battery.com/asus-s96j-cmos-battery.html but it could also have a 2 pin one: https://www.bonanza.com/listings/Asus-G60-G60J-N55S-W7J-W5000-K50i-X70A-U47A-W2-Bios-Cmos-Rtc-Battery/845575237 but you can never trust these sources and must verify what you have on your hands. For the record, besides the "normal" CR-2032 there is also a version with terminals pre-spot-welded that can be used in these cases: https://uk.farnell.com/panasonic-electronic-components/cr-2032-hfn/battery-lithium-2pin-horiz-cr2032/dp/1298246 jaclaz

I personally do think it's weird that the moment I purchased a premium license for this software it was already out of date. Since I knew about AeroGlass it has been out of date. I'm "freaking out" because it does take him so long to update a paid product. I could only use it for some time because I had 1903. You can call it donating but we all know it isn't. The "free" version (trial) is a stripped down version. You need to pay to unlock all it's features and for most make it a viable option to use daily. Having fancy glass windows while having an ugly (Opinion of mine but also a lot of others) watermark on your desktop is for most not really a win. And that's very done on purpose. Cosmetic micro transactions in games also influence the game by a very large portion. It doesn't influence the gameplay with stats but it does influence the game itself. Cosmetics and making something look good is for a lot of people more important than functionality. Hence why cosmetics in those games are so popular. I'm not an id*** though. I know there is Corona epidemic going on and I also know that updating AeroGlass is probably not 10 mins of work. But this is what you get when you're not transparent in what you do. People are going to ask questions. The way AeroGlass is now is beneficial for BigMuscle, not us. He has all the benefits of developing free software with the added benefit of receiving "donations". Which aren't really donations. Most of those donations are really done to get the full version with an added "good feel" effect because you have the impression you're supporting the development of AeroGlass. While in reality, that extra 10 euro you just donated might've absolutely no influence at all. My assumption is is that BigMuscle will likely stop updating this once it takes too much of his time, the donations aren't high enough and people are generally not that interested anymore. But that 10 euro I mentioned might've not changed that in any shape or form. Even better, not updating AeroGlass for some time is probably beneficial to him. I'm not saying he has ill intend or that he's doing it on purpose but not updating AeroGlass will get people to donate yet again. That's all fine. But then I think he should be transparent in regards to what's up. Tell us SOMETHING. Not be quiet for months and months. Give us an ETA. Keep us up to date in regards to plans or innovations. Maybe you found a way to update AeroGlass quicker? Or maybe you wanna make sure that we know that it will take awhile because you're expecting Windows to release an update soon that might break it yet again? Who knows, I'm not developing this software. Everyone is just guessing at this point and everyone who says they know what BigMuscle is thinking is just speculating. In regards to transparency, listing how much is approximately donated each month, an explanation what exactly needs to be done each update and how much time that costs would already go a long way. Of course combined with some quick communication here and there. For all I know he gets over a €690 each update and it takes him an hour or 2 to get it working for the latest version of Windows because he's got it all set up now and optimized for quick successful updates. In terms of optimizing the updating of software, there is a lot you can do. Of course, the €690 isn't based on realism, but I hope you understand what I'm trying to say. Or maybe he indeed only needs about 3-4 hours for each minor update, and 7 for major updates? Or maybe minor or major updates don't matter in terms of time? Or maybe he's just very busy with his 6 jobs? Who knows. The things I mentioned above would take about 10 mins. Quick communication in regards to what's up, how much was donated last month and a quick explanation what needs to be done if an update needs to be released for AeroGlass and the complications some things might bring to updating the software.

Old hardware probably powers most bare-metal Windows 98 systems. An example of patching worn out hardware, which can result in years of extra service. This system uses an ancient IBM MO09K PS/2 three button ball mouse with a centre toggle switch instead of a scroll wheel, similar to the top row third mouse linked below. Presumably > 20 years old, got it used for free years ago. https://www.oldmouse.com/pics/ibm/IBMgroup.jpg The mouse has been maintained and repaired many times. The roller ball is easy to remove, cleaned by using a little spit or water, just rub and roll off accumulated lint and dust into the garbage. Every couple/few years disassemble the mouse, single screw, and remove any built up lint, hair, plastic wear debris and corrosion from the rollers, sensors, switches and electonics. The most commonly used left-click button micro-switch still works great but does accumulate dust, just a dab of isopropyl alcohol on a cotton tip to wipe away the dust. Careful not to saturate the tip and get liquid alcohol into the assembly. The plastic outer casing button, which depresses the left-click micro-switch, wore a concavity several years ago where it strikes the micro-switch. This prevents the micro-switch from engaging, resulting in missed clicks. An ~ 5 mm piece of scotch tape was spanned across the wear area to compensate for the plastic wear. This has been performed twice in about four years and works flawlessly on this heavily used mouse, including gaming. Another issue is that one of two plastic positioning pins broke inside the mouse, responsible for holding a small ~ 1 cm square conductive pad in place underneath the centre toggle switch. Query damaged due to fatigue or 'aggressive' mouse use. The conductive pad needs to be kept clean for good contact, again with alcohol, then carefully slid back into proper position using tweezers. When the scroll function stops working well, gently rotating the exterior toggle switch lines things up again.

Yes, that's best if you can find a compatible battery. There are several types of connectors used, also different cable lengths (new cable may be too short), not to mention the various cell sizes. From the pictures i found it can't be seen how much free space is there for the battery in this model. When i can't find a suitable battery, i do something similar to this video, but with a few differences. I don't cut the original packaging (heatshrink tube i get around is often too thick), but stretch it with pliers from inside, until the cell can be pulled out. Same for the ring piece. When i'm done replacing the cell, i put these back and with some heat they shrink to the previous size. I also use some conductive tape like in this video, and a drop of glue on top. If there is a new battery, but with a different connector (or too short cable), cutting the connector and soldering the original one in its place works too (unless the cable has to go through tight channels).

Can't you just export the old battery and import the new one? At least that's what I did with my previous laptop.

The blue thing with red+black cable is the battery. Could be CR2032 or thinner ( CR2016? ) inside. To replace just the cell you need to use spot welding (точкова заварка) as if you try to solder it normally it will explode. Can also try with glue. Barely visible blue thing under the right heatsink pipe on this pic.