[ros-dev] Reactos Dev Help

[Eric Kohl]

Thomas Larsen wrote:

> “Reactos´s Bootcd” Just wondering why those files are not include
> because many apps depends on them and they are made?
>  
> olepro32.dll
> oledlg.dll
> odbc32.dll

I guess it is simply because these DLLs aren't used by ReactOS yet.
Otherwise someone would have added them to the list of installable
components.


> Is it necessary to apply files in patches when you made a whole dynamic link file?
> My mind lay on inetcfg.dll and other files witch only are ugly stubs in Reactos CVS.

New files don't need to be published as patches. But if you change an 
existing file send a patch.


> Is there a tool to do the diff-patch job anyone can recommend?

The command-line CVS does a good job for creating patches from your 
local tree. Run 'cvs -z9 diff -u -N -R >patch.diff' from the root of 
your ReactOS source tree and patch.diff will contain all changes 
including new files.

For use with local files you can get diffutils and patch from here:
http://gnuwin32.sourceforge.net/packages.html


> Who are able to get CVS Write Access and how?

You can get CVS write access after you submitted some (read: more than 
one) useful patches to the developers mailing list. You have to show 
that you are willing and able to become a contributor to ReactOS. We 
don't want to give write access to someone who submits only two patches.


> Got Dependx86 running on my own Patched Version of Reactos with allot of patch fixing

Please submit your patch to the deleopers mailing list.


> So you can se the depends that files uses but wondering
> 
> Every application using the open dialog from e.g. “Wordpad.exe” crash/halt the application and
> make Reactos unstable it’s the same with depends.exe.
> 
> Cant really find the mistake in comdlg32.dll comctrl32.dll just hoped that any one know about that
> maybe a patch or some.

You will have to build a small testcase that does nothing but call the 
FileOpen dialog in order to find out what's wrong.



> Reactos identify itself as some old Windows Version but if any apps should be able to run it
> should be at least Windows 2000 know about
> 
> BuildLab
> CSDVersion
> CurrentBuild
> CurrentBuildNumber
> CurrentVersion
> 
> Tried to change it to be Windows 2000 but still the apps identify it as some old NT version and
> that really irritates me, made a lot of patch and new dll´s but can really test their use and
> function be cures of that so hoped anyone know about where files check the Windows Version

There is more than one way to retrieve the current Windows version and 
all of them need to be fixed.


> My last question is
> 
> I start and application but if the application gets missing exports lets say NTDLL.RtlAlloc
> The Reactos Gets very unstable I know windows do some other things when a exports missing it shows
> and dialog saying either NTDLL.DLL is missing or the Function NTDLL.RtlAlloc is missing and then
> terminate the application..

The loader, a part of ntdll (see lib/ntdll/ldr), should stop loading the 
application and report an error. At least it should happen if you start 
the application from the command-line. If you start an application from 
explorers 'Run' dialog a message box should report the error. If it 
doesn't Explorer needs fixing.


Regards,
Eric