[Drugwash]

jds, on 21 December 2011 - 01:50 AM, said:

Do you know what the minimum VC version is for building KernelEx?

Not sure, but a couple years ago or so I managed to build it under VC6 Express with Windows SDK 2003. Haven't tried that lately, things may have changed.

EDIT:
Just gave it a spin and I got most components compiled, except for kexbasen.dll , kexcontrol.exe and VKrnlEx.vxd . Didn't care to alter the original project settings, I'm too tired right now.

Errors:

Linking...
Creating library Release/kexbasen.lib and object Release/kexbasen.exp
SHBindToParent.obj : error LNK2001: unresolved external symbol __imp__ILFindLastID@4
SHBindToParent.obj : error LNK2001: unresolved external symbol __imp__ILFree@4
SHBindToParent.obj : error LNK2001: unresolved external symbol __imp__ILRemoveLastID@4
SHBindToParent.obj : error LNK2001: unresolved external symbol __imp__ILClone@4
SHCreateDirectoryEx.obj : error LNK2001: unresolved external symbol __imp__SHCreateDirectory@8
SHGetFolderLocation.obj : error LNK2001: unresolved external symbol __imp__SHILCreateFromPath@12
SHGetSpecialFolder.obj : error LNK2001: unresolved external symbol __imp__SHGetSpecialFolderPath@16
Release/kexbasen.dll : fatal error LNK1120: 7 unresolved externals
Error executing link.exe.
-------------------Configuration: kexcontrol - Win32 Release--------------------
Linking...
kexcontrol.obj : error LNK2001: unresolved external symbol __imp__kexUninit
kexcontrol.obj : error LNK2001: unresolved external symbol __imp__kexDbgDumpImtes
kexcontrol.obj : error LNK2001: unresolved external symbol __imp__kexDbgDumpConfigurations
kexcontrol.obj : error LNK2001: unresolved external symbol __imp__kexDbgDumpAppSettings
kexcontrol.obj : error LNK2001: unresolved external symbol __imp__kexInit
Release/kexcontrol.exe : fatal error LNK1120: 5 unresolved externals
Error executing link.exe.
-------------------Configuration: VxD - Win32 Release--------------------
Linking...
LINK : fatal error LNK1181: cannot open input file "vxdwraps.clb"
Error executing link.exe. 

This post has been edited by Drugwash: 16 January 2012 - 04:39 AM

[loblo]

Bear in mind guys that there is much more to KernelEx than just replaced functions, those VC100 runtime files I hexed won't run if KernelEx is disabled on them even with all the missing imported functions as well as OS and subsystem version in the header "fixed", and with KernelEx enabled it's not good enough to get MFC100.dll to work.

[rloew]

jumper, on 21 December 2011 - 02:10 AM, said:

With KernelEx 4.5.1 or 4.5.2 installed, DLLHOOK reports: Unknown version of KERNEL32.DLL.

Otherwise (and demo limitations aside), it works great. It was very easy to write a DLL and export some stub functions--no DDK needed!

I made modifications to DLLHOOK.INI similar to those above and was able to call a fictitious function in Kernel32 from a test app and redirect it to my DLL. For people who don't use KernelEx, DLLHOOK plus a DLL of stubs might get them by. I imagine this is basically how the Kernel Update Project got started.

Unfortunately, since DLLHOOK doesn't coexist with KernelEx, it can't be used to extend KernelEx as I had hoped.

Obviously KernelEx Patches the code that DLLHOOK verifies before installing. They both are trying to do the same thing.
I haven't used or analyzed KernelEx so I am not sure what would be needed to make DLLHOOK compatable.
It would probably be easier to add the functionality to KernelEx as it should already be capable to doing it.
In addition, combining Commercial and Freeware Software would be problematical.

I will add a note to my FILE64 Package, on the next update, advising that it is not compatable with KernelEx.

[CyberyogiCoWindler]

Bug-Report: Argyll CMS does not work

I just tried to install the open source colour management system Argyll CMS v1.3.5 (designed for Win2k and above) on Win98SE with KernelEx v4.5.101. First it threw illegal instruction errors, but when I manually set all the EXE files KernelEx mode to Win2k or higher, the program seemed to run. (I also installed the "Argyll CMS GUI" extension.) Unfortunately it refuses to communicate with the USB port, so it can not find my Spyder 2 colour measurement probe.

The main problem seems to be that Argyll CMS consists of almost pure Linux code with a small wrapper to communicate with Windoze. The install instruction claimed strange stuff about XDG, which turned out to be a bunch of environment variables pointing to directories found in Linux systems. When I added them in AUTOEXEC.BAT, Win98SE refused to boot with error requester "not enough space for environment" no matter how high I set the "/E:" value of COMMAND.COM in CONFIG.SYS. So I wrote an external BAT file with the following content:

REM Argyll CMS Environment (by CYBERYOGI =CO=Windler)

PATH %PATH%;E:\PROGRA~1\ARGYLL\BIN
SET XDG_DATA_DIRS=E:\PROGRA~1\ARGYLL\XDG\DATA
SET XDG_CONFIG_DIRS=E:\PROGRA~1\ARGYLL\XDG\CONFIG
SET XDG_CACHE_HOME=E:\PROGRA~1\ARGYLL\XDG\CACHE
CD E:\PROGRA~1\ARGYLL

REM spyd2en -Sl E:\PROGRA~1\SpyderTV\cvspyder.dll
REM (execute this once is enough)

ArgyllCMSGUI.exe
COMMAND.COM

After entering "spyd2en -Sl E:\PROGRA~1\SpyderTV\cvspyder.dll" the Spyder 2 driver spyd2PLD.bin is compiled into my "Argyll\xdg\data\color" subdirectory, however no matter what I do, it does not recognize the probe. When I set KEX mode to Win2k, it complains that some USB stuff is not supported. With higher Windoze version settings it simply waits about 10 seconds and reports an error that it can not find the probe. I also tried to manually execute libusb1\Spyd2.inf and have set all related files KEX mode to Win2003 etc.,but the drivers won't install. Also replacing the Spyder 2 driver from system control panel doesn't work.

- Is there a fix to run Argyll CMS with KernelEx?

Can it e.g. use the unmodified cvspyder.dll like HCFR Colorimeter does? My WinDAS-fixed trinitron monitor is too red at medium saturation despite good greyscale and so needs a special ICC profile to get rid of sunburnt looking faces those prevent correct photo editing.

[jds]

jumper, on 19 December 2011 - 10:53 PM, said:

>It suggests that the breadth of KernelEx application compatibility can be usefully expanded with a few added stubs.

Rebuilding all of KernelEx just to add a stub is overkill. There should be a way to just add a small expansion dll; perhaps this is what the undocumented api was meant to address.

I would like to see an .ini file where users can add "<module name>, <function name>, <return value>, <SetLastError value>" lines that would be loaded by KernelEx and turned into new stubs on-the-fly. (Core.ini can almost do this now....)

I haven't tried building KernelEx yet because I'm still using VC5. My response to loblo' s little hex hacks was to create a tool to automate import table patching. Unfortunately it mutated into a full-blown dependency walker before I could get it released.

I'm almost done with minf, so I'll clean up and formally release ImportPatcher next, then get to work on KernelEx.

-jumper

Not wishing to take this thread too far off-topic, I've just tried the Import Patcher on the "signtool.exe" utility from http://www.microsoft...ls.aspx?id=8442 (Microsoft Windows SDK for Windows 7 and .NET Framework 4). Image file = GRMSDK_EN_DVD.iso, Path = \Setup\WinSDKTools\cab1.cab, Extract file = WinSDK_signtool_exe_B2E1011D_2F14_488D_A056_C5BD55106409_x86.

Executing 'signtool.exe' by itself (with KernelEx 4.5.2) produces the error :

The SIGNTOOL.EXE file is
linked to missing export MSVCRT.DLL:__uncaught_exception.

Executing with Import Patcher gives a bunch of "Importing from module ..." messages, but not the above message. It also produces a file "signtoo#.exe" which has patches but seems to behave the same as "signtool.exe".

In addition, a log file is produced, from which the following is an extract :

    Importing from module: 'msvcrt.dll'
        __wgetmainargs: 225 != 142 #
        _cexit: 276 != 173 #
        _exit: 354 != 215 #
        _XcptFilter: 106 != 75 #
        exit: 1167 != 607 #
        _initterm: 469 != 282 #
        _amsg_exit: 257 != 162 #
        fgetpos: 1175 != 615 #
        __p__commode: 185 != 109 #
        __p__fmode: 190 != 114 #
        __set_app_type: 210 != 132 #
        ??1type_info@@UAE@XZ: 17 != 14 #
        msvcrt.dll: __uncaught_exception (db) * No match
        memmove: 1260 != 686 #
        _unlock: 934 != 495 #
        __dllonexit: 141 != 88 #
        _lock: 578 != 329 #
        _onexit: 747 != 403 #
        ?terminate@@YAXXZ: 55 != 48 #
        _controlfp: 295 != 186 #
        isleadbyte: 1218 != 651 #
        isupper: 1223 != 656 #
        _itoa: 561 != 319 #
        islower: 1219 != 652 #
        __badioinfo: 133 != 84 #
        __pioinfo: 207 != 130 #
        _fileno: 367 != 226 #
        _lseeki64: 587 != 337 #
        _write: 1096 != 555 #
        _isatty: 478 != 287 #
        ??0exception@@QAE@ABQBD@Z: 9 != 7 #
        ?what@exception@@UBEPBDXZ: 57 != 50 #
        ??1exception@@UAE@XZ: 16 != 13 #
        fwrite: 1201 != 636 #
        setvbuf: 1287 != 708 #
        fflush: 1173 != 613 #
        ungetc: 1341 != 749 #
        fputc: 1185 != 623 #
        fgetc: 1174 != 614 #
        malloc: 1246 != 679 #
        _callnewh: 274 != 172 #
        setlocale: 1286 != 707 #
        msvcrt.dll: ___lc_handle_func (7f) * No match
        msvcrt.dll: ___lc_codepage_func (7d) * No match
        msvcrt.dll: ___mb_cur_max_func (80) * No match
        abort: 1142 != 586 #
        ungetwc: 1342 != 750 #
        msvcrt.dll: __pctype_func (ce) * No match
        __crtLCMapStringA: 138 != 87 #
        msvcrt.dll: __iob_func (93) * No match
        __mb_cur_max: 176 != 100 #
        msvcrt.dll: __crtLCMapStringW (8b) * No match
        wctomb: 1390 != 778 #

Now two questions come to mind :

1. Is there a way to pass command line parameters to "signtool.exe" when using the Import Patcher?

2. Should the "signtoo#.exe" application run OK (not exhibit the same missing import/export message)?

Joe.

PS. A really neat way to access content from ISO files (such as GRMSDK_EN_DVD.iso) is with the freeware MagicDisc driver (build 105 is the current version for W9X). Just be sure to (1) Configure the virtual drive letter(s) as desired via the MagicDisc context menu and (2) Disable its/their "Auto insert notification" option in Device Manager.

This post has been edited by jds: 04 January 2012 - 10:46 PM

[loblo]

Joe, it's the ini file that matters the most. You should find in it a section per dependency listing the missing functions as follows:

missingfunction=Y

Then you just need to replace the Y by whatever function you want to replace it and rerun the tool which will patch accordingly. (If you want no change for a missing function which is best for what KernelEx already caters for then replace Y by the missing function such as: missingfunction=missingfunction).

[jumper]

CyberyogiCoWindler, on 21 December 2011 - 05:27 PM, said:

Bug-Report: Argyll CMS does not work

...when I manually set all the EXE files KernelEx mode to Win2k or higher, the program seemed to run. (I also installed the "Argyll CMS GUI" extension.)

Thank you for reporting that Argyll CMS v1.3.5 does indeed run on Win9x with the help of KernelEx set to Win2k mode.

The rest of your post, however, is the "no Win9x drivers for my hardware" problem with a twist: the app won't use the standard drivers, wants to use its own, but doesn't support Win9x.

If KernelEx 4.5.2 doesn't support all the advanced functions needed by the Win2k drivers, you'll need to find a Win9x driver solution.

I recommend reading this Argyll Installation on Microsoft Windows page for info on using alternative drivers; and this libusb-win32 page for the last version to support Win9x.

If you need more help with the hardware drivers, please start a new topic. I have many more ideas that should help, but would be way off-topic here!

[jds]

loblo, on 26 December 2011 - 11:19 AM, said:

Joe, it's the ini file that matters the most. You should find in it a section per dependency listing the missing functions as follows:

missingfunction=Y

Then you just need to replace the Y by whatever function you want to replace it and rerun the tool which will patch accordingly. (If you want no change for a missing function which is best for what KernelEx already caters for then replace Y by the missing function such as: missingfunction=missingfunction).

Thanks, loblo.

I see now there is a new thread for Import Patcher : http://www.msfn.org/...dency-problems/

I'll try this again once version 29 is released (apparently imminent).

Joe.

This post has been edited by jds: 27 December 2011 - 08:17 AM

[Steven W]

While looking at the code from sqlite, specifically, sqlite.c from the from this file:

http://www.sqlite.or...ion-3070900.zip

I can't help but notice that someone has attempted to write implementations of LockFile, UnlockFile, and LockFileEx, of the Windows API for Windows CE. I'm wondering if that code could be modified for KernelEx? Would the license the code is under be an issue? And yes, I'm aware that LockFile and UnlockFile are already part of Windows 9x's API.

Edit:
If you Google "LockFileEX" or "UnlockFileEx" with "Windows CE", you'll find code at msdn.

This post has been edited by Steven W: 27 December 2011 - 05:13 PM

[Steven W]

Oh, apparently LockFileEx and UnlockFileEx were already implemented with KernelEx 4.5.2. My mistake.

[Xeno86]

jumper, on 19 December 2011 - 10:53 PM, said:

>It suggests that the breadth of KernelEx application compatibility can be usefully expanded with a few added stubs.

Rebuilding all of KernelEx just to add a stub is overkill. There should be a way to just add a small expansion dll; perhaps this is what the undocumented api was meant to address.

I would like to see an .ini file where users can add "<module name>, <function name>, <return value>, <SetLastError value>" lines that would be loaded by KernelEx and turned into new stubs on-the-fly. (Core.ini can almost do this now....)

I haven't tried building KernelEx yet because I'm still using VC5. My response to loblo' s little hex hacks was to create a tool to automate import table patching. Unfortunately it mutated into a full-blown dependency walker before I could get it released.

I'm almost done with minf, so I'll clean up and formally release ImportPatcher next, then get to work on KernelEx.

-jumper

There is a special mechanism added in KernelEx v4.5.1 that is exactly what you might want - that is extending system API on-the-fly.
The thing to look for is 'KernelEx API Hook infrastructure'.
I used it specifically build a DLL to log all API calls from a chosen application to a file but you can use it to test new system APIs before applying to KernelEx API Libraries.
What you need to do build a DLL (HOOK DLL) and export two functions:

int kexApiHook_initonce(void)
PROC kexApiHook_register(const char* caller, const char* target, const char* api, PROC orig)

kexApiHook_initonce is called before any DllMain to prepare the hooks.
kexApiHook_register is called for any API imported by the application; you get information about requesting module name (caller), the library from which a function is requested (target), the function name that is requested (api) and previous function to chain if any (orig)

So to add a stub or whatever function you just do strcmp on 'target' and 'api' and return it from _register if you get a match.
What is important to keep in mind is that you HAVE TO disable extensions for your HOOK DLL.
Also you have to put a check near "Enable API Hook" in advanced properties on KernelEx tab.
And lastly, you have to compile KernelEx Core project in "Core - Win32 Release APIHOOK" configuration because this mechanism is very powerful, dangerous and useful for debugging only, it is not enabled in shipped KernelEx packages.

When you have working stubs or functions just submit them to me for inclusion in KernelEx.
I've no idea if you can compile KernelEx with VC5, you can compile a HOOK DLL however with any compiler you want. Use 'ApiLog' project as a reference (hope the code is documented well enough).

[mrsk565]

This is very advanced for me, I know about Api's and somewhat of what they do. But can it improve video playback, streaming and gaming. Sorry if this seems like a dumb question. But I know loads about systems and have been working with them for years, sometimes though you can know a name or phase and not be completely sure of it actions. By the way, anybody need help let me know. Im here to contribute the best I can and also learn some things too. Peace

[rloew]

jumper, on 21 December 2011 - 02:10 AM, said:

With KernelEx 4.5.1 or 4.5.2 installed, DLLHOOK reports: Unknown version of KERNEL32.DLL.

Otherwise (and demo limitations aside), it works great. It was very easy to write a DLL and export some stub functions--no DDK needed!

I made modifications to DLLHOOK.INI similar to those above and was able to call a fictitious function in Kernel32 from a test app and redirect it to my DLL. For people who don't use KernelEx, DLLHOOK plus a DLL of stubs might get them by. I imagine this is basically how the Kernel Update Project got started.

Unfortunately, since DLLHOOK doesn't coexist with KernelEx, it can't be used to extend KernelEx as I had hoped.

I set up an experimental Windows 98SE setup and installed KernelEx 4.5.2. I have analyzed the KernelEx Interface and been able to update DLLHOOK to overlay KernelEx.

[jumper]

>...can it improve video playback, streaming and gaming.

KernelEx doesn't improve -- it enables playback, streaming and gaming for many applications that otherwise refuse to either install or run on Win98/ME.


>By the way, anybody need help let me know. Im here to contribute the best I can and also learn some things too.

Welcome to the Win9x sub-forum, mrsk565. We look forward your contributions as we attempt to grow our favorite platform's fan-base together!

-jumper

[jumper]

Xeno86, on 01 January 2012 - 11:38 AM, said:

There is a special mechanism added in KernelEx v4.5.1 that is exactly what you might want - that is extending system API on-the-fly.
...
And lastly, you have to compile KernelEx Core project in "Core - Win32 Release APIHOOK" configuration because this mechanism is very powerful, dangerous and useful for debugging only, it is not enabled in shipped KernelEx packages.

When you have working stubs or functions just submit them to me for inclusion in KernelEx.
I've no idea if you can compile KernelEx with VC5, you can compile a HOOK DLL however with any compiler you want. Use 'ApiLog' project as a reference (hope the code is documented well enough).

I made better progress today trying to build some of the sub-projects with VC5 than I previously did several months ago. ApiLog and Core are both close to building after numerous small mods to paths, pragmas, link options, pointer casts, etc.

Use of ApiHook in a special build is not what I had in mind, but might work. I'm looking for a method that will allow non-programmers to add stubs to the standard version of KernelEx by modifying an .ini file. For instance, Core.ini contains the section:

[WIN98.names]
KERNEL32.GetVersion=kexbases.1
KERNEL32.GetVersionExA=kexbases.2
KERNEL32.GetVersionExW=kexbases.2

I'd like to be able to add:

MYDLL.SomeFunction=stubs.5

to allow SomeFunction in MYDLL.dll to be replaced with function ordinal 5 in Windows\KernelEx\stubs.dll (stubs.dll is an actual dll built ten days ago containing a family of stubs along the lines of rloew's suggestions).

Well, that's it for now. I'll resume trying to get more of KernelEx to build tomorrow.

[jumper]

rloew, on 01 January 2012 - 06:01 PM, said:

I set up an experimental Windows 98SE setup and installed KernelEx 4.5.2. I have analyzed the KernelEx Interface and been able to update DLLHOOK to overlay KernelEx.

That's great news! Now folks using KernelEx will soon have the option to start creating files larger than 4GB...

...errr, does this mean I have to start adding large file support to all my programs? ...

[mrsk565]

Yes, Enables playback and gaming, Thats right I just coudnt remember thanks. KernelEX is a great project and is in fact one of the most important parts of Win9x. If we didnt have this we would be behind in progress big time. I am trying to grasp what we are talking about here but i dont know much about API hooks and all. I know that games can use this but other then that, I need some clarity on what we are doing.

[rloew]

jumper, on 02 January 2012 - 04:04 AM, said:

rloew, on 01 January 2012 - 06:01 PM, said:

I set up an experimental Windows 98SE setup and installed KernelEx 4.5.2. I have analyzed the KernelEx Interface and been able to update DLLHOOK to overlay KernelEx.

That's great news! Now folks using KernelEx will soon have the option to start creating files larger than 4GB...

...errr, does this mean I have to start adding large file support to all my programs? ...

Some maybe.
If your Program is likely to be used with large files, and needs to handle the >4GB Virtual File, rather than the segments actually stored on the Hard Drive, it could use the upgrade.
So far, I have only updated XFILE.

[loblo]

FlippX, on 26 February 2011 - 11:54 AM, said:

Heyho,
there is this software called "LMMS" ( http://lmms.sourceforge.net/ ).
Someting like an audio-midi-sequencer I guess... Looks nice..
I couldn't try it because of this (roughly translated):
"The file LIBSNDFILE-1.DLL is connected with the missing Export-MSVCRT.DLL:___lc_codepage_func."
I think I never had an error of this kind... what is this "___lc_codepage_func" ?!
Comp.-mode doesn't help. Is there anything that might help?

My system is a win98se(ger) + everything official & unofficial like RP (no theme since themes lead to bugs with recent vlc-player for example), KEX, Autopatcher "dec2008" (seems to work great with the german version anyways..) & much from MDGx's site..

Bye
Flipp

Latest version of LMMS (0.4.12) runs if msvcrt.dll is replaced by msvcr70.dll. The vsteffects.dll in the plugins folder crashes though but it can be replaced by the vsteffects.dll from the previous version of LMMS (0.4.11) and then it all runs fine.

More about replacing msvcrt.dll in this thread: http://www.msfn.org/...dency-problems/

[fortcollins]

I need to update my system to include a dshow splitter that supports .flv files with AVC content and .webm. files and a decoder for VP8.

I have Win98SE with KernelEx 4.5.2. I use Zoom Player 8, in large part because it still works on Win 98.

Does anyone have any recommendations for how I should do this?