[Cancelled by the Author] Extended Kernel for XP (ExtendedXP)

[Dibya]

14 minutes ago, jaclaz said:

I was asking if your compiled  VKrnlEx.sys actually worked on XP like the VKrnlEx.vxd does on 9x.

jaclaz

Lol

You speak too much in round about fashion ...

I have not tested yet...

[jaclaz]

56 minutes ago, Dibya said:

I have not tested yet...

Just to give you some benchmark references/scale:

1) compiled AND tested AND working=good  [1]

2) compiled NOT tested=meaningless

3) compiled AND tested AND NOT working=bad 

jaclaz

[1] at an improbability level of two to the power of two hundred and seventy-six thousand to one against

[Dibya]

Any one know where can I get generic gfx driver src code to play around with nvidia pascal gpu?

[dencorso]

Yes.

[TuMaGoNx]

"VKrnlEx makes modification of kernel32.dll file on disk unnecessary by patching the image directly in memory from kernel space before the shell starts
To build VKRNLEX project you need Microsoft Windows 98 Driver Development Kit (DDK) or Microsoft Windows 2000 Driver Development Kit (DDK)."

Hooo... you realise you talk about two different thing no? 9x != NT
it can't be just recompiled, also i imagine how stricter NT compared to 9x, if that easily done then Xeno would made it already (for the sake of GOAT OS)
https://en.wikipedia.org/wiki/Native_API

There are lot of POSIX emulation library around, but most are for higher level use case.

[Dibya]

nasm dislikes db        unicode, '\My Games',0000h    how to fix

[dencorso]

try db       '\My Games',00h

[Dibya]

17 minutes ago, dencorso said:

try db       '\My Games',00h

It does compile but output came ANSI 

[roytam1]

5 hours ago, Dibya said:

nasm dislikes db        unicode, '\My Games',0000h    how to fix

3.4.5 Unicode Strings

The special operators __utf16__, __utf16le__, __utf16be__, __utf32__, __utf32le__ and __utf32be__ allows definition of Unicode strings. They take a string in UTF-8 format and converts it to UTF-16 or UTF-32, respectively. Unless the be forms are specified, the output is littleendian.

For example:

%define u(x) __utf16__(x) 
%define w(x) __utf32__(x) 

      dw u('C:\WINDOWS'), 0       ; Pathname in UTF-16 
      dd w(`A + B = \u206a`), 0   ; String in UTF-32

The UTF operators can be applied either to strings passed to the DB family instructions, or to character constants in an expression context.

from http://www.nasm.us/doc/nasmdoc3.html

[Dibya]

Thanks roytam1.  Any one can suggest a good linker for nasm to convert .objects to binary  (dll)? 

[roytam1]

17 minutes ago, Dibya said:

Thanks roytam1.  Any one can suggest a good linker for nasm to convert .objects to binary  (dll)? 

GoDev linker/binutils ld/MS link.exe will work.

https://forum.nasm.us/index.php?topic=969.0

[Dibya]

1 hour ago, roytam1 said:

GoDev linker/binutils ld/MS link.exe will work.

https://forum.nasm.us/index.php?topic=969.0

I will use link.exe

I think it will be perfect

link ExKernel.obj /OUT:EXKERNEL.DLL /SUBSYSTEM:CONSOLE /ENTRY:start

I need a hooking engine that will redirect Missing API into my Exkernel.dll

I have written it in assembly with alink but alink seems to be extremely weird in binary compilation ,

EXKERNEL.dll

I previously preferred http://www.masm32.com/ but MASM became to old now whereas NASM still gets update . 

Edited August 26, 2017 by Dibya

[roytam1]

8 minutes ago, Dibya said:

I will use link.exe

I think it will be perfect

link ExKernel.obj /OUT:EXKERNEL.DLL /SUBSYSTEM:CONSOLE /ENTRY:start

I need a hooking engine that will redirect Missing API into my Exkernel.dll

I have written it in assembly with alink but alink seems to be extremely weird in binary compilation ,

EXKERNEL.dll

I previously preferred http://www.masm32.com/ but MASM became to old now whereas NASM still gets update . 

I think you should check how ReactOS link its kernel32.dll

[Dibya]

I am getting some link error

"unresolved external Symbol "  

Alink never said it

I declared extern

5 minutes ago, roytam1 said:

I think you should check how ReactOS link its kernel32.dll

 

EXKERNEL.ASM

[Dibya]

Hi in nasm when I am using -fobj  (which is obsolete ) code compiles but when I use fwin32 I get parser instructions expected and error symbol redifined such and such errors. 

Edit :: I have to find a easy way to define dll import in nasm under -fwin32.  If some one help I will be much helped. 

Go Link seems to produce much cleaner code , I will use it . -fwin32 required for goasm, ms link. 

I have to find a good hooking engine to redirect api calls. It will be awesome if that library has .ini to define which functions for which dll. (IAT)

 

Edited August 26, 2017 by Dibya