Goodmaneuver Posted June 9, 2019 Share Posted June 9, 2019 (edited) OK thanks, I have read the unpack procedure and the differing psapx file . I will try the batch or shortcut idea but not for a month or 2. Edited July 1, 2019 by Goodmaneuver Too slow to test Link to comment Share on other sites More sharing options...
Goodmaneuver Posted June 9, 2019 Share Posted June 9, 2019 (edited) ~?Aiko?Chan?~; I assume you mean the character code is not showing the character (glyph in a font). My received emails had some glyphs not shown. This can be a wrong character like a rectangle/box or it could be the character code as with your K-Meleon Html5Test picture. I installed more fonts to fix this but Marlett is different with later OSs than XP, so if the email or web page uses characters from Marlett for example, then the characters or glyphs might be displayed as boxes. If you are missing the font then it would display the character code but not the glyph unless the out of memory idea I had said happens. BabelPad is supposed the be a font editor and perhaps a new font can be produced or edited. I only know of Marlett that does not work in ME as I have updated ones from win10 as well. TTCs don't work as well though I am not sure as some were included with unofficial service pack but without the SP (not sure with SP) then boot logged text says failed. So we miss out some symbols from Cambria.ttc. Some fonts to consider updating would be symbol.ttf, webdings.ttf, wingding.ttf and seguisym.ttf. If charmap.exe is used as I explained 2/3 down on page 4 then KEX NT40 settings need to be set and msvcr80 is in use not mscvr90 on HDD I am using at the moment. Edited June 10, 2019 by Goodmaneuver Link to comment Share on other sites More sharing options...
loblo Posted June 9, 2019 Share Posted June 9, 2019 (edited) @Goodmaneuver, I'm using JRE 7 update 76 without any psapi hack, this might well be obsolete with newer KernelEx, I had completely forgotten about it. Edited June 9, 2019 by loblo Link to comment Share on other sites More sharing options...
Goodmaneuver Posted June 9, 2019 Share Posted June 9, 2019 Jre1.7u0 is the one that nearly fully installs from the MSI. Link to comment Share on other sites More sharing options...
loblo Posted June 10, 2019 Share Posted June 10, 2019 20 hours ago, Goodmaneuver said: ~?Aiko?Chan?~; I assume you mean the character code is not showing the character (glyph in a font). My received emails had some glyphs not shown. This can be a wrong character like a rectangle/box or it could be the character code as with your K-Meleon Html5Test picture. I installed more fonts to fix this but Marlett is different with later OSs than XP, so if the email or web page uses characters from Marlett for example, then the characters or glyphs might be displayed as boxes. If you are missing the font then it would display the character code but not the glyph unless the out of memory idea I had said happens. BabelPad is supposed the be a font editor and perhaps a new font can be produced or edited. I only know of Marlett that does not work in ME as I have updated ones from win10 as well. TTCs don't work as well though I am not sure as some were included with unofficial service pack but without the SP (not sure with SP) then boot logged text says failed. So we miss out some symbols from Cambria.ttc. Some fonts to consider updating would be symbol.ttf, webdings.ttf, wingding.ttf and seguisym.ttf. If charmap.exe is used as I explained 2/3 down on page 4 then KEX NT40 settings need to be set and msvcr80 is in use not mscvr90 on HDD I am using at the moment. BabelPad is not a font editor, it's an (advanced) unicode text editor. You can't use TTC fonts but you can split them into TTF fonts which you can then use, TTC being several TTF fonts merged into one file. Several tools let you do that. Check out TTCTools, UniteTTC, FTMaster or FontForge. 1 Link to comment Share on other sites More sharing options...
shorterxp Posted June 11, 2019 Share Posted June 11, 2019 Quote How you really browse the web on 98/ME in 2019 By upgrading to XP and installing k-meleon LOL It could even work on 98 / Millenium Edition. Try it. Link to comment Share on other sites More sharing options...
roytam1 Posted June 22, 2019 Share Posted June 22, 2019 On 5/9/2019 at 1:29 AM, jumper said: The crash is because LoadLibraryA is called with a null pointer instead of a filename string, resulting in the page fault in LoadLibraryExA. I'd like to know where do LoadLibraryEx called with NULL. Link to comment Share on other sites More sharing options...
jumper Posted June 23, 2019 Share Posted June 23, 2019 The OllyDbg screencap shows the NULL pointer in EAX came from the first parameter. The code wants to check the first two bytes (WORD) of the input string for the disk designator sequence: "\\" (5C5C). Location of crash is in LoadLibraryExA_fix because LoadLibraryA_fix is: return LoadLibraryExA_fix (pLibFileNameA, 0, 0); Also, this is the last line in KM_ApiLog.txt: 4 fff78645 [XUL.DLL]02c0323a:LoadLibraryA(bfa4bb8c) bfa4bb8c is in Kexbases.dll (version 4.5.2016.20), so Kex wrapper of LoadLibraryA is called from XUL.DLL with return address of 02c0323a. Crash happens before LoadLibraryA returns. Kexbases.dll (version 4.5.2016.21) now contains a NULL-pointer check to prevent such a crash. (Note: over-explained in places for the benefit of non-programmers trying to learn.) Link to comment Share on other sites More sharing options...
roytam1 Posted June 23, 2019 Share Posted June 23, 2019 how can you debug it using ollydbg? when I start program from olydbg 1.10, it says msvcr80.dll can't be started. Link to comment Share on other sites More sharing options...
roytam1 Posted June 25, 2019 Share Posted June 25, 2019 BTW how to setup debuggers to work with KEx? So I can debug why palemoon26-vc8 crashes in Win98SE-KEx. Link to comment Share on other sites More sharing options...
jumper Posted June 26, 2019 Share Posted June 26, 2019 Debuggers must attach after KernelEx has loaded the app or plugin: In Ollydbg: File > Attach In VC5/6: Build > Start Debug > Attach to Process..." In Ollydbg: Options > Just-in-time debugging In VC5/6: Tools > Options > Debug > Just-in-time debugging Debuggers can also be manually configured in Win.ini or HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion to attach upon crash: [AeDebug] Auto=0 Debugger=C:\OllyDbg\OLLYDBG.EXE -AEDEBUG %ld %ld ;Debugger=C:\DevStudio\SharedIDE\BIN\msdev.exe -p %ld -e %ld ;Debugger="C:\Program Files\finesse.exe" -v -p %u -e %u 2 Link to comment Share on other sites More sharing options...
Destro Posted June 27, 2019 Author Share Posted June 27, 2019 (edited) roytam1 is a legend. if anyone can get newmoon 26 running on 98se he can. If he actually got that running 98se would be a viable operating system in 2019. Edited June 27, 2019 by Destro Link to comment Share on other sites More sharing options...
roytam1 Posted June 27, 2019 Share Posted June 27, 2019 19 hours ago, jumper said: Debuggers must attach after KernelEx has loaded the app or plugin: In Ollydbg: File > Attach In VC5/6: Build > Start Debug > Attach to Process..." In Ollydbg: Options > Just-in-time debugging In VC5/6: Tools > Options > Debug > Just-in-time debugging Debuggers can also be manually configured in Win.ini or HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion to attach upon crash: [AeDebug] Auto=0 Debugger=C:\OllyDbg\OLLYDBG.EXE -AEDEBUG %ld %ld ;Debugger=C:\DevStudio\SharedIDE\BIN\msdev.exe -p %ld -e %ld ;Debugger="C:\Program Files\finesse.exe" -v -p %u -e %u alright there is "Debug" button in invalid page fault dialog now, and I got this: Link to comment Share on other sites More sharing options...
jumper Posted June 27, 2019 Share Posted June 27, 2019 (edited) I've never used OllyDbg, but try scrolling the Call stack window down until Called from shows the most recent call from a non-system DLL. Maximizing the Call stack window would give the best big picture. Edited June 27, 2019 by jumper typo Link to comment Share on other sites More sharing options...
roytam1 Posted June 28, 2019 Share Posted June 28, 2019 4 hours ago, jumper said: I've never used OllyDbg, but try scrolling the Call stack window down until Called from shows the most recent call from a non-system DLL. Maximizing the Call stack window would give the best big picture. as you see, the call stack has been already reached the end. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now