All Activity

i looked at it in doxygen QueryWorkingSet and Ex are doing partly the same thing they call up NtQueryVirtualMemory where then both access the either "MemoryWorkingSetList" or "MemoryWorkingSetListEx" as parameter // typedef enum _MEMORY_INFORMATION_CLASS { MemoryBasicInformation, MemoryWorkingSetList, // <-- this MemorySectionName, MemoryBasicVlmInformation, MemoryWorkingSetExList // <-- and this } MEMORY_INFORMATION_CLASS; however on msdn they might look different: (QueryWorkingSet) typedef struct _PSAPI_WORKING_SET_INFORMATION { ULONG_PTR NumberOfEntries; PSAPI_WORKING_SET_BLOCK WorkingSetInfo[1]; } PSAPI_WORKING_SET_INFORMATION, *PPSAPI_WORKING_SET_INFORMATION; (QueryWorkingSetEx) typedef struct _PSAPI_WORKING_SET_EX_INFORMATION { PVOID VirtualAddress; PSAPI_WORKING_SET_EX_BLOCK VirtualAttributes; } PSAPI_WORKING_SET_EX_INFORMATION, *PPSAPI_WORKING_SET_EX_INFORMATION; the parameter sizes are the same, so a linking to that function works, just maybe not fully functional that we should keep an eye on if it behave different if they behave different you have have to write a code that redirects to QueryWorkingSetEx to -> NtQueryVirtualMemory with that MemoryWorkingSetExList xp might got this function parameter

Thanks !!! Never know what one will discover from MSFN. I've been estimating based on Publication 15 Circular E and Tax Schedule X/Y.

I changed pref. dom.ipc.processCount from default 1 to 4 (no multi-process enabled for now, browser.tabs.remote.autostart: false). Is it just my imagination, or do websites load better and Serpent 52.9 uses memory less wastefully and actually recovers it after closing memory-hog sites?

The hate for the Ribbon toolbar died quickly. I remember how initially there was even a paid add-on to put a normal toolbar into Office. I don't even have Office 2010; it is fairly chunky. My operating system is Windows 2008 R2, so those updates are not applicable. Well, I hope it can at least recover some text that I can reformat if needed. My only other alternative is Office on a Xiaomi smartphone, which can open X and save to another format. I don't even get how that program could be used productively.

I was never able to correctly open all *.???x files with either Office XP or Office 2003 using the Compatibility Pack. As a result, I moved to Office 2010 with UBitMenu. Another problem with Excel on these previous versions of Office is that they were unable to correctly handle more complicated spreadsheets, such as Glenn Reeves' Excel IRS Form 1040.

"This is a pre-release version of the Compatibility Pack and can only open pre-release Office 2007 files." = This is a problem with MSVCRT.DLL in Windows 2000. I have created Update KB926436-v2 to fix this issue in Windows 2000. You can use the latest version. MEGA Thanks for the information from 2013. https://msfn.org/board/topic/161323-msvcrtdll-without-_resetstkoflw-w2k/

Is not reliable to trust. The RAM can still pass it, but not load Windows.

What of it? It doesn't fix Vista, it's in Alpha mode.

Yes it does, and it worked fine until 1990. Checkpoint Charlie, ring any bells? https://en.wikipedia.org/wiki/Checkpoint_Charlie

Never noticed the replies to this. Thanks, guys. I used Memtest86+ ranges and added (beginning adjusted for first bad logged address [xxxx000] and end for last bad logged address [xxxxfff] ) it to SYSTEM.INI > [386enh] > EMMExclude=xxxx000-xxxxFFF I see that I have a reduced total amount of ram, listed under properties. It is equivalent to the quantity listed in EMMExclude= Memtest86+ placed the bad memory at about 50mb thru to 65mb. If in Dos only, I use XMSDSK (not at top of memory), create a 75mb ram disk, and then ignore it. I initially thought EMMExclude has something to do with reserved UMB regions. Much latter, when exploring this machine again, I knew better. Anyway, that is what I have done. If you have any corrections, advice, or warnings, I'm all ears. EDIT: I had to use HIMEMX, as HIMEM.SYS complains about the detected bad memory; and prevents the loading of Windows.

Detailed explanation of this issue on WinXP SP3: https://github.com/3dyd/pyinstaller-builds/issues/2#issuecomment-3464525813 Excerpt form PyInst-6.0.0 documentation: https://pyinstaller.org/en/v6.0.0/CHANGES.html#incompatible-changes The psapi.dll in question (with the missing function) is the system one, while the one inside the "_internal" dir (which isn't being loaded when PyInst-6.16.0-xpmod has been used) is PSAPI.DLL, one of the four wrapper DLLs (kernelXP.dll, ntextl.dll, psapi.dll, ws2_xx.dll) that are used to backport py3.11.4 to XP ...

Or you could copy a Psapi.dll with that API (Vista/ROS/Wine/KernelEx) to the local directory. Patching might be the best option -- this is one case where dropping the "Ex" from the end actually works (same three parameters). Using a hex editor, change "QueryWorkingSetEx" to "QueryWorkingSet" by replacing the "Ex" with two nulls.

I had a compatibility pack v4 from 2009 and was unable to open this example file. Registering ole32.dll didn't resolve the problem. The event log has a report saying that Wordconv.exe had crashed every time I try to open a DOCX. Unfortunately on my system crashes are silent like that. Installing this older compatibility pack v2 from 2006 was sucessful. I can now open the files I have on hand including this test file with my avatar. I do remember this pack v4 actually working because it is the only one I have. But that was on 32-bit WinXP. I was not able to open a new thread in this forum, which I initially wanted to do. I remember that was discussed some months ago. The error from the forum was "something went wrong".

My Office is 2007, so I may not be of much help. But maybe this will fix your issue (article cites your exact issue but on Windows 2000) -- https://superuser.com/questions/1504407/office-2003-cant-open-newer-office-files More specifically, solution was to use "version 2" of the compatibility pack (linked in superuser article) -- https://www.malavida.com/en/soft/microsoft-office-compatbility-pack/download

Please give more exact and accurate information! I use Office 2003 with Windows 10 x64, no problems with Compatibility pack. But this Compatibility pack can not open all docx-files (more specs are *somewhere* on the Internet). For now I made you a test file in Word, saved as docx with Compatibility pack. Feel free to try. Test file for Compatibility pack.docx

I had to downgrade to PyInstaller 5.13.2, instead of using PyInstaller 6.16.0 for XP from 3dyd... I got a nasty error when launching the `onedir` build. yt-dlp said: [PYI-1228:ERROR] Failed to load Python DLL 'C:\bin\_internal\python311.dll'. LoadLibrary: Kan opgegeven procedure niet vinden. (can't find procedure) See Issue 2.

Good question! I installed Microsoft 365 (Word, Excel, PP, OneNote). The Image did not contain Outlook but I can test it later for you. In general, you definitely need to activate before using, since I noticed that Word and Excel tend to crash without proper pre-activation. PowerPoint requires some dlls from Windows 10 to work. by the way, I noticed that 365 does no longer work on 1507/1511 as well. Here, I receive the same errors as on 8.1. I guess Microsoft won‘t make an official statement regarding older Windows 10 versions.

I've tested and verified it with v2.40.4519. Serpent 55 starts and runs.

does outlook work? for me it crashes upon opening any email

I have installed Office 2000 SP-3 and the XML format compatibility pack for opening DOCX and XLSX files. The operating system is 2008 R2 x64. Lately this setup cannot open anything. I remember it worked in the past, but I used it very rarely. "There was an error opening file." from Microsoft Word. Has the DOCX format changed recently or is my installation broken? What is the talk of updates here? Can I get a new version that works?

Didn't help!

HKCU settings should go to HIVEDEF.INF, not to the HIVECLS.INF but you talk about RunOnce and I don't see an .inf with RunOnce. What I'm missing here? If you look to my addon I add driver signing settings to the HIVESFT.INF under the root key HKLM,"SOFTWARE\Microsoft\Driver Signing",,0x00000010 using [ExtraFileEdits] to keep entries in order not to the end of the huge [AddReg] block.

This can be done by changing just three bits! What you need: Oleaut32.dll 2.40.4519 (31 July 2006 6:12:40 pm GMT, checksum: 000A2534) A hex editor Dependency Walker Steps: Open Oleaut32.dll in the hex editor change 00000004: 03 to C3 (create ret opcode in unused DOS header) change 00087760: 00 to 04 (direct Ordinal 327 to above) Save and verify. Optional to adjust the checksum: also change 00000118: 34 to F8 (000A2534 to 000A25F8) Verify addition of Ordinal 327 (and checksum) with Dependency Walker.

No, that's for bi-directional parallel ports. Select your quoted text and search on Google. An HP printing support forum has the answers. Or try a standard LaserJet driver as I suggested.

In case anyone was wondering how the current Office status is on Windows 8.1: I installed the latest Microsoft 365 (v2509) on Windows 8.1,which indeed is the 31th Post-EOL Feature Update (v2301) for this System and ... Surprise -> it works! The new icons match very well with the OS. I like them. Look for yourself tho: imgur.com/a/kR2cdyl In terms of stability, I would recommend using Office 2024 LTSC. It is supported until 2029 (when Premium Assurance ends for NT 6.3) and includes modern standards yet excluding Copilot (which is great in my opinion)