Hi,
Just like to let you know that the latest cvs code does not compile out of the
box using mingw on a debian testing box.
$i586-mingw32msvc-cc --version
i586-mingw32msvc-cc (GCC) 3.4.2 (mingw-special)
The problem is some functions are re-declared in the string.h (line 169,
wchar_t() ) and stdio.h (line 269, putwc() )files. Also the loadlib.c test
file failed to compile since it was not including stdlib.h and could not find
the mbstowcs function.
This is the latest cvs code from 5:30'ish GMT.
Cheers,
Damian
output from cvs diff:
Index: apps/testsets/loadlib/loadlib.c
===================================================================
RCS file: /CVS/ReactOS/reactos/apps/testsets/loadlib/loadlib.c,v
retrieving revision 1.2
diff -r1.2 loadlib.c
26a27
> #include <stdlib.h>
Index: include/msvcrt/stdio.h
===================================================================
RCS file: /CVS/ReactOS/reactos/include/msvcrt/stdio.h,v
retrieving revision 1.8
diff -r1.8 stdio.h
269c269
< int putwc(wint_t wc, FILE* fileWrite);
---
> //int putwc(wint_t wc, FILE* fileWrite);
Index: include/msvcrt/string.h
===================================================================
RCS file: /CVS/ReactOS/reactos/include/msvcrt/string.h,v
retrieving revision 1.6
diff -r1.6 string.h
169c169
< wchar_t* wcsdup(const wchar_t* wsToDuplicate);
---
> //wchar_t* wcsdup(const wchar_t* wsToDuplicate);
Hay!!!!
greatlrd(a)cvs.reactos.com wrote:
> CVSROOT: /CVS/ReactOS
> Module name: reactos
> Repository: reactos/include/
> Changes by: greatlrd(a)mok.osexperts.com 04/11/28 16:15:24
>
> Added files:
> reactos/include/: dinput.h
>
> Log message:
> first port of wine directx support to reactos
I want to commit my port of msi.dll from wine!
8^)
James
PD: Humm, send me a contact mail and i will send you
the files ziped.
Best Regards,
Lucio Diaz
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Could Someone with autorization to edit the
Reactos.com Web page look at my FAQ and Howto, to
decide if he/she likes it and what have to be changed
so it could be in the web page.
I think it is a improvement over the actual texts. The
texts i did are thought for everybody, even with
screenshots to guide the people with little
experience.
Thankyou,
Lucio Diaz.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
>While attempting to guess the location isn't going to
>be successful
>100%
>of the time, it would probably be better then the 99%
>incorrect that
>you
>get with always defaulting to 1 set zone.
>Also, are there any other user-set preferences that
>come before the
>date/time page (How do you call the different parts
of >Setup?) that
>might help determining location?
It seems a pain in the @ss to code the whole thing,
taking in acount ALL the countries and their probable
timezones(countries with diferent timezone areas) for
something as easy to the user as to look at his watch
and set the time. I dont mind what standard (if GMT -8
or GMT 0) you chose, but i believe that making it more
elaborate does not worth today when many other things,
quite more important, are waiting to be implemented
(like Networking). I am sure that time will come for
those details.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Hi!
I have written a tool to configure the ReactOS source tree (customize
the build) It builds a GUI interface from an XML file which lists all
the possible options and how they are "realized" (in which file a value
has to be changed to make the build-system do what is wanted, i.e. set
KDBG in config to 1)
I would like to add the possibility of configuring things like
WHOLE_PAGE_ALLOCATIONS or TAG_STATISTICS_TRACKING (from ntoskrnl/mm/npool.c)
It would be good if such defines were moved into a file like
ntoskrnl/include/config.h which is then included by ntoskrnl.h and looks
like this:
/* Enable tracking of statistics about the tagged blocks in the pool */
#undef TAG_STATISTICS_TRACKING
/*
* Put each block in its own range of pages and position the block at the
* end of the range so any accesses beyond the end of block are to invalid
* memory locations.
*/
#undef WHOLE_PAGE_ALLOCATIONS
I don't want to make the tool edit the C files directly.
If anybody is against this please let me know, otherwise I will do it.
(Note: The tool is written in python and will thus not be allowed into
the reactos tree but I will provide it for whomever is interested)
Thanks,
blight
>The most intelligent solution is to stick to GMT 0.
>Best regards,
>Alex Ionescu
I agree, is both the easier and the most logic option
(also i live at GMT 0 ;)
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Hi Hartmut!
You have changed the w32 callback to save the FPU state, this is wrong I
think!
I was wondering too wether it should be saved so GvG suggested to check
myself and I modified our winhello app...
It prints out the FPU control word, calls CreateWindow and printf the
FPU control word again.
In the callback for the WM_CREATE message (produced by CreateWindow) it
also prints the control word, then modifies it (and prints the modified one)
This is the output on windows2000:
Original FPU control word: 0x8001f
WM_CREATE: Original FPU control word: 0x8001f
WM_CREATE: Modified FPU control word: 0xa001f
FPU control word after CreateWindow: 0xa001f
Of course I have attached the program.
I am not sure but I think in the KiClearFloatingPointState which you
have added you have to set KPCR->NpxThread to NULL if it's CurrentThread
before you do the fn/xsave because it could raise a delayed FPU
exception (which will be ignored when KPCR->CurrentThread is NULL and be
delivered when the saved FPU state is restored for the thread)
I think I have made the same mistake in tskswitch.S - I am pretty sure
it has to be fixed there because we don't want a FPU exception to be
raised while we are in a cli/sti block and switching to another task.
- blight