MiKl

Hi Jumper, I am also using an unaltered flash 19.0.0.245 like Loblo. I always use the zip-versions of the different SeaMonkey-versions and after unpacking and setting the comp-modes I ran the exe and at first it wanted RtlAssert -> then RtlConvertSidToUnicodeString. So I added these to kstub822.ini [ntdll.dll]. But anything seem to be wrong with RtlCreateEnvironment. Oh by the way, when you have the time, can you maybe update the 'printing with kernelex' thread with the best possible solutions ? I tried today the 'kernelex-folder' way from post #15 but this is indeed not working or is it ? But it is also of course possible (and likely) that I was finally just confused with all these different versions of comdlg32.dll and comdlgex.dll, renaming this to that and when to use exactly which installation method.

Hi Jumper, it is definetely a flash-issue again !! SeaMonkey crashes only when there is flash-content in any tab. In the meantime I have tested several versions of SM (2.1, 2.2., 2.3.3 and 2.6.1) and flash-plugin in different comp-modes. I even tried iphlpapi.dll 5.00.1717.2 in win/sys. But the crashing continued. But it works beautifully when using kernelex.dll v9. Besides that issue SeaMonkey loads now up to 2.8 for me. Thank you. For 2.9.1. I needed to add to kstub.ini: -> ntdll.dll RtlAssert (seem to work) RtlConvertSidToUnicodeString (seem to work) but RtlCreateEnvironment (seem to be not 'recognized' - maybe because of the kernelex.dll issue ?) When trying to start SM 2.10.1 I get the following: SEAMONKEY verursachte einen Ausnahmefehler c000000dH in Modul MSVCR80.DLL bei 016f:78178ad2.Register:EAX=9e9ef4b0 CS=c1c6016f EIP=78178ad2 EFLGS=00000282EBX=00000000 SS=630177 ESP=0063ebbc EBP=0063ebf8ECX=00000002 DS=83b20177 ESI=0063fd05 FS=81f743ffEDX=81f96614 ES=630177 EDI=bff9637b GS=85390000Bytes bei CS:EIP:83 c4 14 83 c8 ff e9 a1 00 00 00 8b 45 0c 3b c3Stapelwerte:78178ad2 00000000 00000000 00000000 00000000 00000000 bfa4100e 81f96880 00000000 00401235 0063ec0c 0063ec0c 00000001 0063ec28 0063ec0c 0063fc38

Hi Jumper, just when I thought to ask you politely if you maybe could add 'ntsetinformationprocess' !!! Thanks. On first test all kernelex-dependent apps work except SeaMonkey !! It crashed while opening the tabs. After downgrading kernelex.dll to the one from release 9 it works fine again. Datum 11/27/2015 Uhrzeit 13:37SEAMONKEY verursachte einen Fehler durch eine ungültige Seitein Modul bei 0000:00000009.Register:EAX=0164e000 CS=018f EIP=00000009 EFLGS=00010246EBX=ffe144fb SS=0197 ESP=0201f7ec EBP=0201f824ECX=01638148 DS=0197 ESI=01c390e0 FS=5c0fEDX=00000000 ES=0197 EDI=8234bfe4 GS=0000Bytes bei CS:EIP:00 6b 0a 65 04 70 00 65 04 70 00 54 ff 00 f0 79Stapelwerte:00000197 0306afe9 00000005 0164e000 00002000 0201f814 01638148 0306815c 4e4d454a 00000008 8234bfe4 0164e000 00000000 00002000 0201f894 030614de

I have c&p'ed the installation folder from XP over to my Win98SE system where 7zip 9.20 was installed. After renaming of the folders and setting comp. mode of only 7zFM.exe and 7zG.exe to win2000 everything seems to work. Right-click version check, drag&drop, etc. Edit: After a reboot the context menue entry is gone Trying Loblo's method now.

Thanks Loblo that explains it, but for me every dll that runs because of KernelEx is a kernelex-dll. @ Jumper On run I got an error message because I have iphlpapi.dll (4.90.3000.2) in my system folder because otherwise SeaMonkey crashes when trying to play a flash-file !! So Kexport created a ini for iphlpapi3.dll but not for iphlpapid4.dll. Should I better use iphlpapi3.dll in KernelEx ?

Hi Jumper, I have sent the folder containing the portable SeaMonkey 2.6.1 to Kexports but I get result 0 and no INI. At least I do not find one. Does it mean that SM 2.6.1 is as compatible to the current KernelEx built as possible ?

I think I have tried everything now regarding the floppy and sata-speed issues but this mobo seem to be cursed or whatever ... However, on ASUS' website there is also a Beta-Bios as the last version for the p4p800-x. But is it wise/clever to test a Beta-Bios ? Does anyone have any experiences with this ?

Hi Jumper, browsing the internet is getting harder and harder almost every day now with my old SeaMonkey 2.0.14 and the browser printing problem returned also with my dedicated print server !! (My old desktop file/print-server died a few weeks ago ...) So I was wondering if there will be any more updates of KernelEx ?

No, there is absolutely no activity !! The FDD-LED does not light up at boot. Nothing happens when I insert a floppy. Nada .... I will check the drive with another data-cable during the weekend because I don't have a spare one and have to open another PC just to get one. Hmmm, the FDD-LED should at least once light up at boot no matter if the data-cable is connected or not, shouldn't it ? So is it possible that only the power cord to the FDD is damaged ? I really start to hate that mobo - but on the other hand it was quite cheap so I might just put it away as a back-up machine.

The BIOS update (via USB) went smoothly but unfortunately the floppy drive still does not work. Maybe the fdd's power cord is damaged ? Will check that later but any other suggestion would be most welcome. And I checked the system with Everest and it tells me that the SATA is running at UDMA5 ! Shouldn't it be at least UDMA6 ? Is there anything else that I still need to change in BIOS and/or Win98SE to get better speed ?

Thanks again for all the helpful posts !!! I will see if I try to update the BIOS again or just leave it that way because the mobo seem to work otherwise fine. Oh by the way, I have found a nice offer for sata-ssd's on the German Ebay. Now with Rloew's patch installed I can use sata-ssd's without further problems, can't I ?

Thanks for the help guys but this time it was 'only' a dying sata !! It was there one time yesterday evening but now the drive makes only clicking noises. Weird though that S.M.A.R.T. never gave any alarm. Regarding the AMI Bios issue. I checked for updates for this mobo and as I wanted to update it I noticed that the floppy drive, although passing BIOS test, is just not working. I tried a different floppy drive as well. Same result. What a strange machine. Can I update a BIOS using an USB stick ?

Hi guys, didn't wanted to start a new thread so - don't laugh - but I purchased RLoew's great SATA patch just a few days ago and it works great and one of the first things I wanted to do was backing up this win98SE installation onto another SATA. But as soon as I attach the second SATA-HDD the system won't boot. BIOS tests are done but then there is only a black screen with a blinking cursor. After removing the second drive the system boots normally again. The mobo is a jumperfree Asus P4P800-X and I tried several settings in BIOS and different cables, etc. ! Nothing worked. Any suggestions would be really appreciated.

O.K., finally the easiest way to do what I needed to achive was using the HP tool !! But I could only install hp2pm98.exe.! Versions 3.x, 4.x. and 5.x all failed to install with the above already mentioned error. I googled a little bit and found the following in post #5. https://community.flexerasoftware.com/showthread.php?136727-isrt-dll-access-denied-could-not-be-removed-at-end-of-install-uninstall Apparently anything from Window XP Hotfix Q328310 was causing this. So I think it is necessary to downgrade certain files to ME or maybe even 98SE versions again. Unfortunately I could not find the contents of this hot fix. Does anyone maybe know where to find more infos ? Thanks

Yeah, finding this tool was indeed a pita. I could send you version 4.00.01. Of course, I tried all possible kernelex-comp-modes but installation always failed. Anybody knows where to find 5.x ?

I tried to install the HP tool (4.0) but it failed with a message I have not seen so far. "Installation Support File C:\windows\temp\{ ... }\isrt.dll could not be installed. Access is denied." ISRT.DLL is a XP file, right ?

SumatraPDF 3.1 does not seem to work anymore at all on Win98SE.

Hi Drugwash, I have not tried the HP solution yet because I would like to find a way within Windows first. In my registry there is a section 'network -> persistent' with an entry for LPT1 !! Do you know if I can just enter there the networkpath to the printer ? Not that I corrupt anything ... (Net.exe from ME does not support persistent as well. Net.exe from XP does not run on 98SE)

The other day I have purchased a print server (IC104 by SEH here from Germany) and it works perfectly !! And with the 'net use' command I assigned LPTs for some old apps to print. So far so good. But after a reboot these connections are lost. I googled a little bit and found the persistent switch but this seem to not work on 98SE. So I put a little batch file in autostart that creates these ports during each boot. But I was wondering if there is not a way to make it persistent under 98SE ? Maybe with a file from WinME ? Net.exe ? Has anyone ever tested this ?

No new thread necessary because it was only caused by, maybe corrupted, files left in the Win-Temp folder. After putting a small script in autoexec.bat which deletes all files in the temp folder during boot my shutdown problems are history.

Awesome !!! Does the patch also fixes the protection fault-issue with PCI-E cards ??

Hi Jumper, are there any further updates for psapi and uxtheme planned ??

Sorry to bother you, but have tried to do that with HxD .... I can't find that line... "Impossible to find 16B1E0 55" You need to find 16B1E0 and change the value at this address from 55 to C3. Did a quick check with the xvi32 resource hacker and it was immediately found.

O.K., the shutdown issue returned even with IFSMGR.VXD v4.10.2225 and CACHEWRITEDELAY=4000 so I think it is safe to say that the problems in this system are not hardware/driver/settings releated but are caused by something else!! I think/hope that I now know what it is but this would be off-topic. I may start a new thread later on after more tests. Thank you all for the great feedback !!!

Hi Drugwash, wouldn't it be much more easier and flexible if you'll just add an option - maybe as a dropdown menue with values from 2000 to 8000 in steps of 250 or 500 - to your patcher ?? I mean, one system may still have shutdown problems with 4000 msec but not any longer with 4500 msec or whatever !! So anybody who do not dares to touch the registry can increase "CacheWriteDelay" step by step until the perfect value is found.