Xeno86

Member
  • Content count

    128
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Xeno86

  • Rank
    KernelEx Creator
  • Birthday 06/15/1986

Contact Methods

  • Website URL
    http://kernelex.sourceforge.net

Profile Information

  • OS
    98SE

Recent Profile Visitors

1,091 profile views
  1. With all due respect, of course it would: when the 8th character is a space, one patches 0x00 to 0x20. But if there are 8 characters, it's simply a question of using an incomplete 7 characters string at build time, and then patching the final 0x00, added by C++, with the right value for the 8th character. Yes, but that would require generating a separate 7 Character string when the Identifier is 8 Characters. That would defeat the purpose of using the util.h Macro as is. It would also require specifying the eighth Character to the Patcher. VMM.H defines these Macros also, but Microsoft specifies a separate "quote_name" argument in addition to using a "name" argument. OMG. What is the problem? The driver works as is... so why patch, why bother?
  2. KernelEx does build properly under both Windows 98 SE and Windows 7 Pro x64. Just follow the instructions here: http://kernelex.sourceforge.net/wiki/Building_KernelEx No virtual machine is needed. Autoexec.bat changes aren't needed. Just set up the paths correctly inside VC6! VC6 is 100% compatible with Windows 7 x64. The guide applies to vanilla v4.5.2 only, cannot warrant that it will work with 3rd party mods.
  3. You can already create debug installer package with the following command-line: "c:\Program Files\NSIS\makensis.exe" /D_DEBUG KernelEx.nsi As for debugging, put wdeb386.exe from 98ddk\bin under C:\WINDOWS and execute this command-line: wdeb386.exe /n /c:1 /r:19200 win.com On second computer run a serial port terminal - hyperterminal / putty / whatever.
  4. Actually you only need wdeb386.exe and no other files for debug output. Physical machine is also okay. You only gotta connect two machines with serial cable. Also I suggest moving this discussion to a separate thread...
  5. Drugwash, While I've added these files to repository a couple of days ago to the repository I didn't update source code packages which I'm correcting now. I've just updated source code distribution on SourceForge to include the files in question. http://sourceforge.net/projects/kernelex/files/KernelEx/4.5.2/ --- Jumper, KernelEx.sdb is a special database containing Microsoft Installer (MSI) transform files. These files allow the system to modify the MSI files on the fly so you don't have to mess with Orca by hand, eg. remove VersionNT dependencies. Having that said, KernelEx.sdb needs to be recreated only if new transforms are added. Currently there are transforms for: Google Earth 5.1 Google Earth 5.2 Google Earth 5.2.1 Google Earth 6 beta Office 2007 File Format Converters Word Viewer 2003 Excel Viewer 2003 Office 2003 Professional Acrobat Reader 7
  6. As I've seen many people have problems building the project, I've written instructions on how to configure your build environment. http://kernelex.sourceforge.net/wiki/Building_KernelEx
  7. This just ensures me that I did a good thing by leaving the 9x scene. People are so angry and disrespectful for your work that it's actually a pain to read all that stuff. You got all the system enhancements for free and open sourced and I never asked for money. What do I get in return? Swears, disrespect. And all that not for the first time... What I've learned is that people shouldn't receive anything for free because then they don't respect the stuff they get. Sad but true.
  8. Say hello to LLXX. Rule #7.b Just to clarify and clean my name. LLXX didn't influence my work. Ever. And I didn't base my code on any code originating from her. For those who don't remember, the original idea for KernelEX came in 2005 from a small Portuguese project called Win98updt0001 (http://rwinds.no-ip.org/file/win98updt0001.zip) which implemented three API functions in just a few lines of assembly and my urge to run Need For Speed Most Wanted under Windows 98. Based on the success I expanded the code into first Kernel Update Project, then early KernelEx and what evolved into current KernelEx series in 2009. All of the work was done by my and Tihiy's research, some parts were borrowed from Wine project. You have absolutely no right to insult me and call me a thief because you clearly don't know the history and basic facts! Having that said, share with us, Hu$tle, what was your contribution to Win9x scene?
  9. Well you haven't made a single attempt to contact me... Anyway, it's nice to see some developer actually interested in continuing the project. While I'm not actively developing the project myself anymore, I can help in getting started with the project. Just PM me.
  10. 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).
  11. I was too lazy to check, anyone willing to bother?
  12. Actually, I don't think we're talking about the same thing. What I wanted to tell in that post is that the new KernelEx v4.5.2 *COULD* possibly conflict with some copy protection engine, which does compare in-memory file image with what it can find on disk and notices a difference. On the other hand previous releases, including v4.5.1 were modifying a file on disk, so in-memory image would be the same as actual file on disk. As I have no possibility to check all copy protection engines, I bring this to public attention, so that we can find the problem quicker. Hope this clarifies my previous post a bit. If your drive wasn't working properly with previous versions, eg. v4.5.1 and especially without KernelEx then there are good chances that it's a faulty drive problem. Thank you for kind words. Happy user keeps me motivated and more willing to put my effort! Cheers
  13. The problem with opening links in Opera is known to me. This new release is targeted on making Mozilla Firefox running on 9x again.
  14. With the new release KernelEx v4.5.2 the special build of Firefox - Aurora shouldn't be required anymore. KernelEx v4.5.2 can now run official Mozilla Firefox 8.0 build. Keep in mind that these limitations still apply: no bookmarks no browse history no address bar history
  15. KernelEx v4.5.2 Release announcement Hi there! This is a maintenance release to allow running the recently released official Mozilla Firefox 8.0 build. Greets to aceman and felicitas for discovering the nature of the problem which prevented it from working. What is not working yet: recently visited addresses, history and bookmarks. KernelEx enters the dark world of VMM and kernel drivers. In this release KernelEx doesn't make any modifications to system files on disk. Instead all patching is done on-the-fly in memory, while the system is performing the startup via a specialized driver. Please report if you find any problems with copy protection-engines - like SecuROM, SafeDisc etc. that you didn't have in v4.5.1. What's new: Added KernelEx Virtual Device (VKrnlEx.vxd) project which makes modification of kernel32.dll file on disk unnecessary by patching the image directly in memory from kernel space before the shell starts Implemented a fix for a crash occuring when accessing a locked file through file mapping object Some programs shouldn't complain about not having admin privileges anymore Various bugfixes Apps fixed / now working: Now working: Mozilla Firefox 8.0 KernelEx home page: http://kernelex.sourceforge.net/ KernelEx Wiki: http://kernelex.sourceforge.net/wiki/ Download: http://sourceforge.net/projects/kernelex/files/