One correction: I was forced to build the VXD with the 98DDK. That's because of some VXDWRAP s#!t that XPDDK doesn't correctly understand (MS is well known for backward compatibility *g*)! Boy, do I love GCC (any flavor  )

The 16- and 32-bit drivers (aka DLL & DRV) work allright (98- and XP-DDK). However, my first shot was the Napalm build, so haven't had the time to do V3 and/or Banshee! Only after I see H5 work will I turn to these!

What do I need: stdlib.h, stdarg.h and string.h from the 16bit compiler. I currently use some home-made placeholders! *g* I wonder how they work

I would also like error/msg files for the 16bit CL and H2INC utility! Ohwell, they are not compulsory...

Anyone can tell me something about VCPP (processor pack?) 

You did it, WOW!!!

Really I can't wait to have these files in my hands...

Almost 10 hours of work?! ... man, I really don't have words to say... Thank you!!!...

LOL... I heared a shot but I don't know in what direction was... ???

Cya.

Here what the Microsoft Processor Pack help file says about intel.

The Pentium® III Processor and other processors such as the Pentium processor with MMX technology and Pentium II processor have instructions to enable development of optimized multimedia applications. The instructions are implemented through extensions to previously implemented instructions. This technology uses the single-instruction, multiple-data (SIMD) technique. By processing data elements in parallel, applications with media-rich bitstreams can significantly improve performance by using SIMD instructions.

You can access the Intel performance libraries at http://developer.intel.com/vtune/perflibst/.

The most direct way to use these instructions is to inline the assembly language instructions into your source code. However, this can be time consuming and tedious. Instead, Intel provides easy implementation by using API extension sets, referred to as intrinsics.

EP

Okay, guys! I've had enough of M$VC for a whole damn year! So many devsuits, with so many versions with so many conflicts... Requiring so many tools from so many packages... It makes me puke. I think I'll stick to Glide/OpenGL

Nevertheless, I managed to compile the leaked driver with XPDDK alone (no 16bit compiler, no 32bit compiler, no Win32SDK, no DXDDK, no MASM). Everything I need is in the XPDDK... Well, I hope you don't believe me! Hehehehe! Damn right! Microsoft didn't deceive me! Of course, some tools were needed from the MSVC6 installation kit. But I did it without actually installing MSVC6. >;>

BTW, I couldn't enable DX8 support... Conflicts whith DX7 headers -- which are, of course, required... I wonder how the heck they did it?!? Provided, they *DID* it...

Also, couldn't actually compile SW_TNL, because my compiler barfs at __m128 (although I've seen the token in the compiler executable -- or DLL, I forgot).

So, ladies and gents, I'll be uploading it Monday, because my poor dialup cannot handle large packages

Until then, I have to write the compilation instructions

Good work!!!!

Can you explain though what the actual benefits of this driver will be? I think I missed that bit.

New Banshee Drivers!!!!
Who would have thought they would ever see this day!!!

WOW !!!

8)
Quote:

Yeah!!!

Quote:

Whatcan I say... THX!!! dude, thank you very much!
Just only one question: is this package prepared to be compiled directly for Banshee users, or is for V3/4/5 only?

Quote:

NP...

Quote:

Yes?, where?... I don't see anything!!!.. Is it in the package too?

Quote:

Can you explain me just a little more?...

Thx again, you're a genious man...