jumper
MemberContent Type
Profiles
Forums
Events
Everything posted by jumper
-
My Browser Builds (Part 5)
jumper replied to roytam1's topic in Browsers working on Older NT-Family OSes
Bloated sites can require an increase to 4M to avoid errors. I recommend you continue cutting it in half until you see problems on any sites. -
My Browser Builds (Part 5)
jumper replied to roytam1's topic in Browsers working on Older NT-Family OSes
0xe5e5e5e5 seems to be a JIT pseudo-handle related to CVE-2020-26950. Search DLL's Mozjs and Xul. -
Xnview classic 2.13 full version support on windows 95
jumper replied to cov3rt's topic in Windows 9x/ME
Good! So v1.90 RC2 is the latest that runs. I'll compare RC3 and Final to it and look for changes that might cause the Page Fault. -
Xnview classic 2.13 full version support on windows 95
jumper replied to cov3rt's topic in Windows 9x/ME
Did you try https://web.archive.org/web/20220521054008/http://www.oldversion.com/windows/xnview-v1-90-beta-1 ? If that works, there is also 1.90 beta 2-6 and rc 1-3 before 1.90 final. -
True or False? USB2 + Win 98 + Intel 915 = Impossible
jumper replied to waltah's topic in Windows 9x/ME
In File System Properties, you can increase the read-ahead buffering on HDDs and toggle Write Caching on removable drives. I just measured 877000 Bps with System Monitor on a 30MB copy from PNY USB3 32GB in 4-port mini-hub to IBM 6GB PATA HDD over USB1.1(UHCD) on Win98fe. There is also a PNY USB2 64GB, another 16GB, and a mouse in the hub. I have a USB2 PCMCIA card, but don't use it--I'm happy enough with what I have. The hub acts as a docking port and backups (with write caching enabled) and searches are fast enough. Another copy from the PNY USB2 64GB had the same peak speed, but fluctuated slower. HDD has DMA enabled and all are Int 13 units: "If this feature is enabled for removable drives, the media must be in the drive when you start your computer." (But the 16GB works just fine when hot-plugged.) All three thumb drives use Lexar JumpDrive2 drivers, but the 16GB is labeled: "Non-Lexar USB ThumbDrive". I think this one is rloew's mod. Defragging the HDD can also help. Also test searching for text on the USB drive; this will read without any writes to the HDD (a bit faster than copying here). -
What non-https links are you testing with? Any ftp?
-
True or False? USB2 + Win 98 + Intel 915 = Impossible
jumper replied to waltah's topic in Windows 9x/ME
The bottleneck seems to be the thumb drive itself. 150/50*8=24 Mbps is about right for most budget USB2 flash drives (and doubles USB1.1). Try a USB3 drive to get better performance. -
I was unable to get any browser later than FF28 to load (and even that crashed at exit), so I wrote a small test app to raise various exceptions. I've added to Finesse basic support for several new continuable exception types, but still need to add detail reporting and make it all more robust.
-
The path to the LAPTOP shared folder has changed. Update any shortcuts to it on DESKTOP.
-
Select ntoskrn8.sys and post again.
-
Firefox 52 no longer working on XP
jumper replied to Dave-H's topic in Browsers working on Older NT-Family OSes
Bound means prelinked, a rarity these days. An address will appear there that should match the function address in the lower box. If so, the load will be faster, if not, a bit slower. Early versions of my ImportPatcher could validate bound import links. -
If it's a full driver, identify the subset of headers and link libraries needed. Include them directly into your source package. Once working, replace them with open-source versions from Wine or ReactOS. (Check for availability first!) If it's a mini-driver, the framework might not be available as open-source.
-
I found my complete FineSSE project from 2011 including a well-tested but unreleased version 30. It includes support for CC/Breakpoint and can be extended for other continuable exceptions. I also began a version 31 in 2013 that starts to add a process picker for easier attachment to any running process. For now, I'll create a version 32 from v30 that also handles exception 0x406D1388 (Name thread). I don't plan to support locales other than the system (maybe user) default at the app-level by either name or ID. There are name constants: LOCALE_NAME_INVARIANT LOCALE_NAME_SYSTEM_DEFAULT LOCALE_NAME_USER_DEFAULT and ID constants: LOCALE_INVARIANT LOCALE_SYSTEM_DEFAULT LOCALE_USER_DEFAULT that I can use to fake/minimally implement the locale API's. (See LOCALE_INVARIANT.) KernelEx already has LCMapStringW, GetLocaleInfoW, and CompareStringW so I'll see how those are handled. The InitOnce functions need more study, but can be redirected to ReactOS for now. My WinME system is SSE-only. Which browser should I try testing with?
-
Aside from the heavy looping in ucrtbase and msvcp140, all looks good--v4 is doing its job. Did these runs exit silently?
-
I believe V4 is working and the Access Violation at 0xFFFFFFEA is just the next issue. Clear the Kstub log and run without DW. It won't launch, but we should see RaiseException (and hopefully more) in the new Kstub log and in the ApiLog window. Try with and without Kex debug mode. Meanwhile, I'm updating FineSSE to handle Continuable Exceptions and display a stack dump.
-
DW seems to be struggling. I used to recommend setting DW to the same mode as the app to be profiled. You can try that.
-
Dr.Watson seems to completely disagree with Dependency Walker: Trap 03 0000 - Breakpoint trap eax=61dd11ec ebx=bff66d80 ecx=00000028 edx=9344ecbc esi=00d08f60 edi=00000000 eip=620b1c4c esp=007cf9bc ebp=007cf9c8 -- -- -- nv up EI pl ZR na PE nc cs=016f ss=0177 ds=0177 es=0177 fs=234f gs=0000 XUL.DLL:.text+0x90c4c: >016f:620b1c4c cc int 3 Exception Code: 80000003 (hardcoded breakpoint) Exception Address: 620b1c4d (XUL.DLL:.text+0x90c4d) Depends.dll is not listed as a loaded module, but neither is Concrt140.dll. Does Dependency Walker show a handled Breakpoint Trap further up in its log (before the Concrt140 process attach)?
-
Yes: RaiseException(406d1388) again. Use =v4 and hope for additional debugging text from DebugBreak or OutputDebugString in the logs before the code -1 exit.
-
The log looks good until IP suddenly jumps to high system space. A crash dialog stack dump or Dr.Watson stack unwind would be helpful here to see where execution came from. What happened to the RaiseException error? That was the reason for trying in DW and Finesse. They don't all need to be redirected. Avoid API-MS-WIN dlls as much as possible, redirecting them to Kernel32.dll itself or other system dlls. See my API-MS-Win.reg file for details. Try using KernelEx XP-Debug mode for possibly more messages in AppLog. If already doing so, try changing IsDebuggerPresent to Kexbases.0 (0:False, 1:True) in Core.ini to possibly avoid the RaiseException errors when not profiling in DW.
-
The results are different: In 16 XUL does not load. In 17 it fails much later with thread 18 quitting after successfully loading WBEMSVC.dll. Were the symptoms the same? What versions of UCRTBASE.dll have you tried? Also try using KnownDLLs to redirect UCRTBASE to MSVCR140 or lower. The code at 406012 seems to just be checking for tampering in its own header, but makes no calls to UCRTBASE. 'First chance exception 0x406D1388 (Thread was named) occurred in "c:\program files\ff54_17\XUL.DLL" at address 0x0173AF59 by thread 10 "JS Helper".' -- This shows how a debugger can handle a RaiseException and continue without crashing. Mypal68 shouldn't be making that call when not running in a debugger. Try running Mypal68 in DW or Finesse.