Jump to content

Printing with KernelEx 4.5.1


diamant

Recommended Posts

Great, I can print with Sumatra PDF 1.9 (method 4b / ImportPatcher). :thumbup

I have printed successfully with Firefox 3.6.28 and Seamonkey 2.6.1, too. :thumbup

Firefox 3.5.19 crashed once during testing.

Seamonkey 2.0.14 isn't stable in order to print.

Edited by schwups
Link to comment
Share on other sites


I have printed successfully with Firefox 3.6.28 and Seamonkey 2.6.1, too. :thumbup

Seamonkey 2.0.14 isn't stable in order to print.

Hi Schwups,

based on my previous experiences in getting Seamonkey 2.0.14 reliably to print and since I don't want to play around with the registry I did the following.

1) In <winsysdir>, copy original COMDLG32.DLL to COMDLG00.DLL.

2) Place ComDlg32.dll in app folder AND into Windows Kernel Ex folder !!!

When SM 2.0.14 is running open the print preview - wait a few seconds - close the preview and after that I can print without any problems. But this may be working only for me because I changed many things on my system before finding this awesome board !!

Thank you very much Jumper and everybody else !!

Oh by the way Schwups, on higher versions than 2.0.14 websites look like crap on my system !! Is it working for you ??

Edited by MiKl
Link to comment
Share on other sites

Higher versions of SeaMonkey work for me with comp. mode Win XP (Win ME / KernelEX 4.5.2 / CPU SSE2 or 3). Recently visited addresses, history, bookmarks and the Java Sun plugin don't work.

Fixed with KernelEX 4.5.2: Firefox 4+ : Freeze when drawing a non-blank page. Seamonkey versions 2.1 - 2.6.1 are based on the same Gecko engines as Firefox 4 - 9.0.1 and should work. KernelEX Wiki

Edited by schwups
Link to comment
Share on other sites

It doesn't work for PDF XChangeViewer. The progam crashes in order to print. Tested with versions 2.5.201, 2.5.192, 2.0.42.3. Pdfxcview has caused an error in unknown module. It is the same error as before without the update.

Link to comment
Share on other sites

I get an error message in order to print with Palemoon. It can also be after printing of one page. Palemoon caused an error in Kernel32.dll. Palemoon will now close. Tested on some ME machines.

Link to comment
Share on other sites

I get an error message in order to print with Palemoon. It can also be after printing of one page. Palemoon caused an error in Kernel32.dll. Palemoon will now close. Tested on some ME machines.

What were the error details and Kernel32.dll version?

If we cross-reference the instruction address/EIP value with Kernel32.dll function export addresses using a PE viewer, we should be able to determine what function was running. (In the case of your previous post, the Stack dump should reveal what module--and possibly function--might have jumped into unknown memory.)

If you have VC++ installed, click on [Debug] in the error dialog to launch it. Then View->Debug Windows->Call Stack to see the calling sequence.

I'll try to write a JIT debugger (based on FineSSE) that looks up the call sequence (and maybe offers a live recovery attempt!).

Link to comment
Share on other sites

It is the orig. Win ME Kernel32.dll 4.90.0.3000 / 08.06.2000 17:00

According to this link:


LoadLibraryA("KERNEL32.DLL") - returns BFF70000h on w98se
- returns BFF60000h on winME
- returns 77E80000h on w2k

Google translates the error message to:


Palemoon caused an error by a
invalid page
in module KERNEL32.DLL at 01ef: bff6a4e9
...
Stack dump:
00650050 00000000 004c000c 004c0000 004c985c
00000040 00000000 00000b19 000004ca 0095e748
bff6a6b1 004c0000 004c985c 00000018 00000040
00000013

Subtracting bff60000 from bff6a4e9 and bff6a6b1 and looking up those addresses for Kernel32.dll in Dependency Walker indicates that the error happened in a support function called by IsBadWritePtr.

Apps usually load at 00400000, so all those 0040xxxx values on the stack are probably data pointers within Palemoon.

Link to comment
Share on other sites

According to this link:


LoadLibraryA("KERNEL32.DLL") - returns BFF70000h on w98se
- returns BFF60000h on winME
- returns 77E80000h on w2k

Here's a small app that returns the load address of any library.

Usage: loaddr libraryname.dll

Hope it may be useful.

It returns kernel32.dll's load address = 0x7C800000 on XP SP3.

@all: Please do test it on 9x/ME, to confirm it works OK.

LOADDR.7z

Edited by dencorso
Replaced buggy app with fixed one.
Link to comment
Share on other sites

Maybe I'm using it incorrectly, but W98SE loader reports it is improperly linked with alignment less than 0x1000 and refuse to load.

:blink: No, you're doing nothing wrong.

I forgot to link it the way 9x/ME likes... My bad, sorry! :blushing:

Redownload, please, I've fixed it now.

Thanks for the swift feedback. You rock! :thumbup

Link to comment
Share on other sites

According to this link:


LoadLibraryA("KERNEL32.DLL") - returns BFF70000h on w98se
- returns BFF60000h on winME
- returns 77E80000h on w2k

@all: Please do test it on 9x/ME, to confirm it works OK.

So now we have:


LoadLibraryA("KERNEL32.DLL") - returns BFF70000h on Win 95 OSR2.5 (determined by LoneCrusader)
- returns BFF70000h on Win 98SE (confirmed by dencorso and snuz2)
- returns BFF60000h on Win ME (confirmed by loblo)
- returns 77E80000h on Win 2k
- returns 7C570000h on Win 2k Adv Srv (determined by tomasz86)
- returns 7C800000h on Win XP Pro SP3 (determined by dencorso)

:angel Well, now that LOADDR.EXE is working right...

@LoneCrusader: would you please determine the value for Win 95 OSR2.5,?

@loblo: would you please confirm the value for Win ME?

@jaclaz: would you please confirm/determine the value for Win XP Pro SP2?

@tomasz86: would you please confirm the value for Win 2k (or determine a new value, since you use a server version, right?)?

Link to comment
Share on other sites

@LoneCrusader: would you please determine the value for Win 95 OSR2.5,?

Tested with 95C OSR2.5 with all official USB updates installed (USB Updates contain a major KERNEL32 version change)

And using the last KERNEL32.DLL for Windows 95, v4.03.1216.

loaddr v.0.1, freeware by dencorso, 2012

kernel32.dll's load address = 0xBFF70000

When I get a chance I will test again on an installation without USB (=v4.00.1112)

Tested on Pre-USB OSR2. Result is the same.

EDIT - Added Pre-USB 95 test results.

Edited by LoneCrusader
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...