Enabling DCE

[JadeWolf324]

fr1sk3y do i put those things anywhere special?

[.Joa]

Jadewolf324: you dumbf*ck!! You said you were close to getting DCE to work but

1. You don't have the needed dll's for it

2. Don't know where to place them

People like you should be banned

[Cool4]

Jadewolf324: you dumbf*ck!! You said you were close to getting DCE to work but

1. You don't have the needed dll's for it

2. Don't know where to place them

People like you should be banned

people with Penguins in their avatars shouldn't be trusted :p :laugh:

[JadeWolf324]

ok what the hell is that about. i have the DLL's and they are in the right place but IT DIDNT GO THE RIGHT WAY IT JUST SHOWED ALL THE HIDDEN COLORS.

so

I FIGURED I DID SOMETHING WRONG. AND YES I DO HAVE THE ****ING DLLS AND I DO KNOW WHERE TO PLACE THEM, AS A MATTER OF FACT THEY ARE WHERE THEY BELONG AND THE ****ING THING STILL DIDNT WORK, I SUPPOSE MY CARD ISNT "FULLY SUPPORTED" BY DX9 EVEN THOUGH ITS ADVERTISED AS IT IS AND FOR BEING AN ASS IM NOT GOING TO EVEN TRY THIS **** ANYMORE.

[Coolme]

Microsoft showed DCE on builds that are from Lab_06 and apparently, 4051 and 4053 are main builds so maybe that?s the problem. Lab_06 builds have something that the main builds don?t have. So until a build from Lab_06 leaks out, you can?t activated DCE (I think that a build from lab 06 will leak soon.)

[michaeltal]

@Coolme:

I like your sig! :yes:

Michael

[d0tn3t]

So until a build from Lab_06 leaks out, you can?t activated DCE (I think that a build from lab 06 will leak soon.)

I wanna piece of that crystal ball!

[Coolme]

I meant you can't activate DCE properly. And about the build_06. I think that since there is so many builds leaked there might be a build_06 build that will be leaked.

[fr1sk3y]

I meant you can't activate DCE properly. And about the build_06. I think that since there is so many builds leaked there might be a build_06 build that will be leaked.

3683 if from lab06_n - we can test it there, can't we?

[Coolme]

3683 if from lab06_n - we can test it there, can't we?

M$ first demostrated DCE on Lab_06 build 4008 I believe and I think that is when they first implanted it into LH. Unless 3683 has SBCtl.exe and other DCE related dlls/exes.

[fr1sk3y]

3683 doesn't have sbctl.exe but it contains milrender.dll, i'm not very sure if they firtly demostrated dce on lab06 4008 - i think it is 4015 (the winhec one)

[glix81]

Hey

Yeah I was thinking something arround the same lines. In reguards to dce, whats the difference between 4015 and 4029. I wonder if there is any differences.

[y_notm]

ok what the hell is that about. i have the DLL's and they are in the right place but IT DIDNT GO THE RIGHT WAY IT JUST SHOWED ALL THE HIDDEN COLORS.

so

I FIGURED I DID SOMETHING WRONG. AND YES I DO HAVE THE ****ING DLLS AND I DO KNOW WHERE TO PLACE THEM, AS A MATTER OF FACT THEY ARE WHERE THEY BELONG AND THE ****ING THING STILL DIDNT WORK, I SUPPOSE MY CARD ISNT "FULLY SUPPORTED" BY DX9 EVEN THOUGH ITS ADVERTISED AS IT IS AND FOR BEING AN ASS IM NOT GOING TO EVEN TRY THIS **** ANYMORE.

way to flip out over nothing. running the two sbctl.exe commands are supposed to do exactly what you described. the nifty special effects aren't enabled with those two commands.

[fr1sk3y]

hi again. i haven't been here for a long time but i've tryed many ways to enable dce. i dragged milcore in winhex and use the specialist->gatehr text utility and then found strings that mention 'log' of the dce initialisation. can someone who tried alphaalien's dcebeta 2 package send me a log file, named 'milav.log' and the dll 'MF.DLL'. these files may contain the information that we need. the dce package can be downloaded here: http://users.pandora.be/aldatillian/LONGHO...es/dceBeta2.rar

also, i'm not sure and that's why i'd like to ask: is geforce fx5200 directx9 compatible?

btw. anyone has any progress on workin' it out?

:edit:

here you are a zip with milcore and milrender's strings i've found using winhex

Text_mil.dll.zip

[cpu killer]

hi again. i haven't been here for a long time but i've tryed many ways to enable dce. i dragged milcore in winhex and use the specialist->gatehr text utility and then found strings that mention 'log' of the dce initialisation. can someone who tried alphaalien's dcebeta 2 package send me a log file, named 'milav.log' and the dll 'MF.DLL'. these files may contain the information that we need. the dce package can be downloaded here: http://users.pandora.be/aldatillian/LONGHO...es/dceBeta2.rar

also, i'm not sure and that's why i'd like to ask: is geforce fx5200 directx9 compatible?

btw. anyone has any progress on workin' it out?

:edit:

here you are a zip with milcore and milrender's strings i've found using winhex

I currently have 4051 installed and am interested in getting DCE working, would be willing to help u out - contact me via MSN:

[email protected]

thanks :).

[nuka_t]

yes teh fx is dx9 comp but dont expect great performance. longhorn final with all the eyecandy would require about a 9600xt/9800pro. but for now, the 5200 should be enough to test out lh as long as you dont play games with dce enabled.

[fr1sk3y]

so, i opened the mil.bat from AA's dce beta 2 package and found 'mistakes' in almost every rundll call. i've corrected all, except the following ones [in milcore.dll]:

MILFactoryCreateRDPClient

MILFactoryCreateRemoteCompositor

MilCreateCompnode

MILBitmapScalerInitialize

MILBitmapSetPalette

MILBitmapSetPixelFormat

MILCompositorBeginBatch

MILRenderDebug

MILCompositorEndBatch

it seemd the mistakes in the rundll32 calls with the functions above are in the entry points. that's what i can't get. i need a way to find these functions' entry points. any ideas on getting the entry points?

[cpu killer]

so, i opened the mil.bat from AA's dce beta 2 package and found 'mistakes' in almost every rundll call. i've corrected all, except the following ones [in milcore.dll]:

MILFactoryCreateRDPClient

MILFactoryCreateRemoteCompositor

MilCreateCompnode

MILBitmapScalerInitialize

MILBitmapSetPalette

MILBitmapSetPixelFormat

MILCompositorBeginBatch

MILRenderDebug

MILCompositorEndBatch

it seemd the mistakes in the rundll32 calls with the functions above are in the entry points. that's what i can't get. i need a way to find these functions' entry points. any ideas on getting the entry points?

OllyDBG + ASM Programmer

:).

They can probably be found using OllyDBG but its pretty hard to read unless you understand assembly...

I've been trying to fugre this out for a while now, and its not easy :blink:

[fr1sk3y]

so, i've tested my fixed package and realised that rundll32 in c:\windows\system32 can be some type of corrupted/messed up, because whatever function you call in whatever you want dll it crashes. that's why, i think, we can't run the functions in mil.bat and some of the ones in dce-start.bat. i've tried using rundll32 from xp but it says ' an exception occured while trying to run 'blablabla''. maybe we need a fixed rundll32. if someone can run the functions in mil.bat without getting the crashes, please tell me. also, i've opened it in depends.exe and found out that 2 dlls, RPCSHIM.DLL and msjava.dll, are missing, which are required by rundll32. and that's what, i think, cancels the executions of the functions.

[Aldatillian]

:edit:

here you are a zip with milcore and milrender's strings i've found using winhex

Did you know this text can be found in there in French, German and English?

A l l   h u m a n   b e i n g s   a r e   b o r n   f r e e   a n d   e q u a l   i n   d i g n i t y   a n d   r i g h t s .   T h e y   a r e   e n d o w e d   w i t h   r e a s o n   a n d   c o n s c i e n c e   a n d   s h o u l d   a c t   t o w a r d s   o n e   a n o t h e r   i n   a   s p i r i t   o f   b r o t h e r h o o d .   E v e r y o n e   i s   e n t i t l e d   t o   a l l   t h e   r i g h t s   a n d   f r e e d o m s   s e t   f o r t h   i n   t h i s   D e c l a r a t i o n ,   w i t h o u t   d i s t i n c t i o n   o f   a n y   k i n d ,   s u c h   a s   r a c e ,   c o l o u r ,   s e x ,   l a n g u a g e ,   r e l i g i o n ,   p o l i t i c a l   o r   o t h e r   o p i n i o n ,   n a t i o n a l   o r   s o c i a l   o r i g i n ,   p r o p e r t y ,   b i r t h   o r   o t h e r   s t a t u s .   F u r t h e r m o r e ,   n o   d i s t i n c t i o n   s h a l l   b e   m a d e   o n   t h e   b a s i s   o f   t h e   p o l i t i c a l ,   j u r i s d i c t i o n a l   o r   i n t e r n a t i o n a l   s t a t u s   o f   t h e   c o u n t r y   o r   t e r r i t o r y   t o   w h i c h   a   p e r s o n   b e l o n g s ,   w h e t h e r   i t   b e   i n d e p e n d e n t ,   t r u s t ,   n o n - s e l f - g o v e r n i n g   o r   u n d e r   a n y   o t h e r   l i m i t a t i o n   o f   s o v e r e i g n t y .   E v e r y o n e   h a s   t h e   r i g h t   t o   l i f e ,   l i b e r t y   a n d   s e c u r i t y   o f   p e r s o n .

Anyone knows if MS puts this text in every dll? Kinda funny..

[nuka_t]

they spelt color the brit way. also, i dont think you guys should bother enabling DCE with this build, a new one is coming in may 4/5 (maybe even leaked earlier) which would have a completely new method of enabling DCE and noone would bother with 4051.

[tomwarren Veteran]

Nuka has a point, i'm sure you guys have noticed a lot of the changes from even 4051 to 53. Considering the WinHec build will be probably be 4070-5 then that's nearly 20 builds of change. Good luck though ;)

[Chris123NT]

Would be nice if MS gave the devs the dce.cmd file that we saw at winhec last year to enable dce in the handout build :)

[tomwarren Veteran]

Would be nice if MS gave the devs the dce.cmd file that we saw at winhec last year to enable dce in the handout build :)

It doesn't contain anything more than what has been found out ;)

[Chris123NT]

It doesn't contain anything more than what has been found out ;)

Well it obviously has the correct milcore/milrender calls with the correct entry points. And as far as I know the entry points for the milcore calls hasn't been found out yet.