You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(64) |
Oct
(438) |
Nov
(183) |
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(132) |
May
(466) |
Jun
(366) |
Jul
(392) |
Aug
(31) |
Sep
(18) |
Oct
|
Nov
|
Dec
|
|
From: <9sp...@sn...> - 2001-10-27 23:22:05
|
Hi there, This is a newbie question. I followed the documentation i could find, to compile reactos from the sources. More info about my system follows. It seems that the make process fails because included file like <dirent.h> <errno.h> <limits.h> <stdio.h> <string.h> <stdlib.h> are not in my system include directories. Where are they supposed to be? I found files with those names in subdirectories named crtdll and msvcrt but surely these aren't the right ones or the includes would have looked like <crtdll/*> and <msvcrt/*> respectively. In fact, the whole code base seems to use either of the following forms when it comes to those header files: #include <*> #include <crtdll/*> #include <msvcrt/*> Maybe i'm just too stupid, can anyone tell me what i'm doing wrong? I think it might be useful because i can then give feedback on this list about how to build reactos on NT. thanks, Stephane Directories------------ (e:\reactos\bochs) bochs-1.2.1.win32.zip (e:\reactos\gcc) gcc-2.95.3-20011023-win32.tar.gz (e:\reactos\nasm) nasm-0.98-win32.zip (e:\reactos\binutils) binutils-2.11.90-20011023-win32.tar.gz (e:\reactos\make) make-3.79.1-20010901.tar.gz (e:\reactos\reactos) 0018_source.zip setenv.cmd------------- set HOST=mingw32-windows set ROS_HOME=e:\reactos set MAKE=%ROS_HOME%\make\bin set GCC=%ROS_HOME%\gcc\bin set BINUTILS=%ROS_HOME%\binutils\bin set PATH=%MAKE%;%GCC%;%BINUTILS%;%PATH% ----------------------- >e: >cd reactos >setenv.cmd >set BINUTILS=e:\reactos\binutils\bin COMPUTERNAME=CYCLOP ComSpec=C:\WINNT\system32\cmd.exe GCC=e:\reactos\gcc\bin HOME=e:\cvsroot HOMEDRIVE=C: HOMEPATH=\users HOST=mingw32-windows LOGONSERVER=\\CYCLOP MAKE=e:\reactos\make\bin NUMBER_OF_PROCESSORS=1 OS=Windows_NT Os2LibPath=C:\WINNT\system32\os2\dll; Path=e:\reactos\make\bin;e:\reactos\gcc\bin;e:\reactos\binutils\bin;C:\WINNT\system32;C:\WINNT PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH PROCESSOR_ARCHITECTURE=x86 PROCESSOR_IDENTIFIER=x86 Family 6 Model 3 Stepping 4, GenuineIntel PROCESSOR_LEVEL=6 PROCESSOR_REVISION=0304 PROMPT=$P$G ROS_HOME=e:\reactos SystemDrive=C: SystemRoot=C:\WINNT TEMP=C:\TEMP TMP=C:\TEMP USERDOMAIN=CYCLOP USERNAME=Administrator USERPROFILE=C:\WINNT\Profiles\Administrator windir=C:\WINNT >cd reactos >make gcc -g rdel.c -liberty -o rdel.exe rdel.c:7: dirent.h: No such file or directory rdel.c:8: errno.h: No such file or directory rdel.c:10: stdio.h: No such file or directory rdel.c:11: string.h: No such file or directory rdel.c:12: stdlib.h: No such file or directory make: *** [rdel.exe] Error 1 ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: KJK::Hyperion <no...@li...> - 2001-10-27 23:12:42
|
Ok, with some voodoo the compilation went like a charm. Tested Bochs too, with the included Linux image and with MS-DOS 7.1, they both worked. The problem now is mtools: they need a setup, in the first place, and in the tutorial this wasn't mentioned. So I created the .mtoolsrc, but I get only "Can't read boot sector" or "Not a DOS image" messages. I don't know any other way to manipulate disk images (you can't directly "mount" them as disk devices, for example - apparently only directories will do), and Bochs won't directly mount disk devices (shame, shame). Any ideas? ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Phillip S. <ps...@cf...> - 2001-10-27 22:08:55
|
We need to fix that then, and have all demand zero allocations be satisfied from the zeroed pool. At 09:32 PM 10/27/2001 +0200, you wrote: >ROS hasn't a zero list. There is only a free and a used list. > >- Hartmut > > > -----Ursprungliche Nachricht----- > > Von: Phillip Susi [SMTP:ps...@cf...] > > Gesendet am: Samstag, 27. Oktober 2001 21:20 > > An: ros...@re... > > Betreff: [ros-kernel] Re: page faults in msvcrt.dll > > > > You zero the pages just for .bss? How do you know? All pages > allocated by > > user mode code are supposed to be taken from the zeroed list so that > secure > > data from another process can't accidentally be given to another. ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Hartmut B. <har...@te...> - 2001-10-27 19:36:28
|
ROS hasn't a zero list. There is only a free and a used list. - Hartmut > -----Ursprungliche Nachricht----- > Von: Phillip Susi [SMTP:ps...@cf...] > Gesendet am: Samstag, 27. Oktober 2001 21:20 > An: ros...@re... > Betreff: [ros-kernel] Re: page faults in msvcrt.dll > > You zero the pages just for .bss? How do you know? All pages allocated by > user mode code are supposed to be taken from the zeroed list so that secure > data from another process can't accidentally be given to another. ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Phillip S. <ps...@cf...> - 2001-10-27 19:26:07
|
You zero the pages just for .bss? How do you know? All pages allocated by user mode code are supposed to be taken from the zeroed list so that secure data from another process can't accidentally be given to another. At 06:24 PM 10/27/2001 +0200, you wrote: >Hi, > >sometimes, I get page faults in msvcrt.dll (and some other dlls). Some >variables are not initialized, but msvcrt assumed, that this variables are >initialized with zero (__file_rec_list, ...). Such variables are located in >the bss section. The memory manager doesn't clear pages for the bss >section. The variable is initialized with a random value. I've fixed this >problem in MmNotPresentFaultSectionView (mm/section.c). Pages for bss >sections are cleread, befor they are mapped. But the bug is in msvcrt.dll >(or other dlls). This variables must be initialized. > >- Hartmut ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Hartmut B. <har...@te...> - 2001-10-27 16:33:20
|
Hi, sometimes, I get page faults in msvcrt.dll (and some other dlls). Some variables are not initialized, but msvcrt assumed, that this variables are initialized with zero (__file_rec_list, ...). Such variables are located in the bss section. The memory manager doesn't clear pages for the bss section. The variable is initialized with a random value. I've fixed this problem in MmNotPresentFaultSectionView (mm/section.c). Pages for bss sections are cleread, befor they are mapped. But the bug is in msvcrt.dll (or other dlls). This variables must be initialized. - Hartmut ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Koert v. d. V. <05...@st...> - 2001-10-27 14:24:08
|
Probably not an bad idea to add ROSVER however, we just should not remove the WINVER. I think an APP should be able to see if it is compiled under ROS or WIN, just to generate optimizations for ROS... (yeah, i'm thinking big!) ----- Original Message ----- > No, because clients of the headers assume that setting WINVER to different > values will have different effects; they know nothing about ROSVER. > > At 12:27 PM 10/27/2001 +0200, you wrote: > >if there is something like this: > > > >#if(WINVER >= 0x0400) ... > > > >should we use > > > >#if(ROSVER >= 0x0400) ... ? > > > >regards > >Benjamin > > ==================================================== > = To remove yourself from this mailing list, go to = > = http://www.reactos.com/home/mailing.html = > ==================================================== > ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Phillip S. <ps...@cf...> - 2001-10-27 14:20:02
|
No, because clients of the headers assume that setting WINVER to different values will have different effects; they know nothing about ROSVER. At 12:27 PM 10/27/2001 +0200, you wrote: >if there is something like this: > >#if(WINVER >= 0x0400) ... > >should we use > >#if(ROSVER >= 0x0400) ... ? > >regards >Benjamin ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Casper H. <ch...@us...> - 2001-10-27 10:40:10
|
> -----Original Message----- > From: Benjamin Kalytta [mailto:bk...@we...] > Sent: 27. oktober 2001 12:28 > To: ros...@re... > Subject: [ros-kernel] General Question > > > if there is something like this: > > #if(WINVER >= 0x0400) ... > > should we use > > #if(ROSVER >= 0x0400) ... ? Where? In the microsoft headers? We can't use microsoft headers due to legal restrictions. We can only hope that we can use the published windows documentation to create our own headers. - Casper ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Benjamin K. <bk...@we...> - 2001-10-27 10:29:59
|
if there is something like this: #if(WINVER >= 0x0400) ... should we use #if(ROSVER >= 0x0400) ... ? regards Benjamin ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Robert D. <od...@pn...> - 2001-10-27 01:54:25
|
G'day GenesisXG, I looked at your webpage and I liked your icons a lot. If you designed=20 these then I look forward to your contribution to the ROS-GUI in the near future. One comment about your homepage - What is it a homepage for ? Looks very savvy and your advertiser should be very pleased (banner ad is very much centre of focus when looking at page) Oops, just realised I'm not looking at your main homepage, but the URL is still http://www.pokeonline.de/. How does one reference one of your pages when many of them come under the same url ? Now i'm thoroughly confused so I'll leave it a that. <puts on ROS-Manager hat> How about keeping this sort of thing out of the kernel list and use the more appropriate ROS-GENERAL list a bit more. I for one are subscribed to all four lists and have filters move mail to the correct mailbox. Doesn't work very well when everybody sends everything to the ROS-KERNEL list however. Rgs, Robert. At 10:02 PM 26/10/2001 +0200, you wrote: >I am for one week in holidays and i can=B4t write any email in this time! >I will write soon in 1 week! > >Please look at my news page! >Its only the first design! >www.pokeonline.de=20 > >greetz >GenesisXG > >Can you upload new screenshots? Please! > >________________________________________________________________ >Lotto online tippen! Egal zu welcher Zeit, egal von welchem Ort. >Mit dem WEB.DE Lottoservice. http://tippen2.web.de/?x=3D13 > > >o remove yourself from this mailing list, go to ttp://www.reactos.com/home/mailing.html =20 > > > ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Benjamin K. <bk...@we...> - 2001-10-27 00:50:10
|
are there any examples how to compile sources, how to create libs for = dll calls and so on ? regards benjamin |
|
From: Casper H. <ch...@us...> - 2001-10-27 00:14:58
|
> -----Original Message----- > From: KJK::Hyperion [mailto:no...@li...] > Sent: 26. oktober 2001 20:00 > To: ros...@re... > Subject: [ros-kernel] Build system broken? > > make[1]: Entering directory `E:/wwwroot/roscvs/reactos/ntoskrnl' > gcc -I./include -pipe -m386 -I./include -I./include > -D__NTOSKRNL__ -g > -Wall -Werror -I../include -p > ipe -m386 -M rtl/capture.c | ..\tools\depends.exe rtl rtl/.capture.d > zsh: command not found: ..toolsdepends.exe > make[1]: *** [rtl/.capture.d] Error 1 > make[1]: Leaving directory `E:/wwwroot/roscvs/reactos/ntoskrnl' > make: *** [ntoskrnl] Error 2 > > See? it looks like the backslashes cause trouble You can define the backslash character in rules.mak. You can set SEP := / or you can set the environment variable HOST to mingw32-linux, then this will happen automatically. - Casper ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Phillip S. <ps...@cf...> - 2001-10-26 23:46:14
|
Yes, unixish shells and apps ported with cygwin tend to screw the pooch when given backslashes. Try using cmd. As for the .d files, make will complain about them being missing the first time you build, but it will build them and work fine after that. At 07:59 PM 10/26/2001 +0200, you wrote: >Today I tried, for fun (and to be able to build some rosapps), to build >the libraries "manually" (i.e. making them one by one, instead of issuing >"make all" from the top directory), and all the build problems I always >had automagically disappeared... The only things I can't build are >ntoskrnl.exe and hal.dll, they require a long list of .d (?) files I've >found no way to build, and everything depending on them (device drivers >and win32k). I suspect my shell (a zsh port for Win32) is the problem, as >the output of a global "make all" is: > >ALDEBARAN\Hyperion [e:\wwwroot\roscvs\reactos] >::make > >[cut - targets already built] > >./tools/rmkdir ./dk >[cut] > >[cut - targets already built] > >make -C ntoskrnl >../tools/depend.mk:10: nt/.channel.d: No such file or directory >[cut - similar errors] > >make[1]: Entering directory `E:/wwwroot/roscvs/reactos/ntoskrnl' >gcc -I./include -pipe -m386 -I./include -I./include -D__NTOSKRNL__ -g >-Wall -Werror -I../include -p >ipe -m386 -M rtl/capture.c | ..\tools\depends.exe rtl rtl/.capture.d >zsh: command not found: ..toolsdepends.exe >make[1]: *** [rtl/.capture.d] Error 1 >make[1]: Leaving directory `E:/wwwroot/roscvs/reactos/ntoskrnl' >make: *** [ntoskrnl] Error 2 > >See? it looks like the backslashes cause trouble ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: KJK::Hyperion <no...@li...> - 2001-10-26 23:36:33
|
At 12.34 26/10/2001 -0400, you wrote: >What is shlwapi? Shell LightWeight API. A bunch of very useful utility functions ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: KJK::Hyperion <no...@li...> - 2001-10-26 23:34:44
|
Today I tried, for fun (and to be able to build some rosapps), to build the libraries "manually" (i.e. making them one by one, instead of issuing "make all" from the top directory), and all the build problems I always had automagically disappeared... The only things I can't build are ntoskrnl.exe and hal.dll, they require a long list of .d (?) files I've found no way to build, and everything depending on them (device drivers and win32k). I suspect my shell (a zsh port for Win32) is the problem, as the output of a global "make all" is: ALDEBARAN\Hyperion [e:\wwwroot\roscvs\reactos] ::make [cut - targets already built] ./tools/rmkdir ./dk [cut] [cut - targets already built] make -C ntoskrnl ../tools/depend.mk:10: nt/.channel.d: No such file or directory [cut - similar errors] make[1]: Entering directory `E:/wwwroot/roscvs/reactos/ntoskrnl' gcc -I./include -pipe -m386 -I./include -I./include -D__NTOSKRNL__ -g -Wall -Werror -I../include -p ipe -m386 -M rtl/capture.c | ..\tools\depends.exe rtl rtl/.capture.d zsh: command not found: ..toolsdepends.exe make[1]: *** [rtl/.capture.d] Error 1 make[1]: Leaving directory `E:/wwwroot/roscvs/reactos/ntoskrnl' make: *** [ntoskrnl] Error 2 See? it looks like the backslashes cause trouble ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Brian G. <bm...@ya...> - 2001-10-26 21:37:06
|
Is this what you want?
IDD_TESTDIALOG DIALOG DISCARDABLE 0, 0, 186, 71
STYLE DS_MODALFRAME | WS_POPUP | WS_CAPTION | WS_SYSMENU
CAPTION "Dialog"
FONT 8, "MS Sans Serif"
BEGIN
DEFPUSHBUTTON "OK",IDOK,129,7,50,14
PUSHBUTTON "Cancel",IDCANCEL,129,24,50,14
LTEXT "Static",IDC_STATIC,8,7,109,36
EDITTEXT IDC_EDIT1,8,52,167,12,ES_AUTOHSCROLL
END
--- James Tabor <jim...@ad...>
wrote:
> Hi,
> Does anyone have examples for dialogs to be use in windres format rc
> files? Dumb question!
> James
>
> ====================================================
> = To remove yourself from this mailing list, go to =
> = http://www.reactos.com/home/mailing.html =
> ====================================================
>
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html =
====================================================
|
|
From: <gen...@we...> - 2001-10-26 20:06:33
|
I am for one week in holidays and i can=B4t write any email in this time! I will write soon in 1 week! Please look at my news page! Its only the first design! www.pokeonline.de=20 greetz GenesisXG Can you upload new screenshots=3F Please! =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Lotto online tippen! Egal zu welcher Zeit, egal von welchem Ort. Mit dem WEB.DE Lottoservice. http://tippen2.web.de/=3Fx=3D13 ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Mihail G. <mg...@kc...> - 2001-10-26 19:16:11
|
Hi, JT> Does anyone have examples for dialogs to be use in windres format rc files? I have. I use BIOW32.RC in my BIOW project http://biow.kc.ru/en/ Take it. Best regards, Mihail mailto:mg...@kc... |
|
From: James T. <jim...@ad...> - 2001-10-26 18:59:46
|
Hi, Does anyone have examples for dialogs to be use in windres format rc files? Dumb question! James ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: James T. <jim...@ad...> - 2001-10-26 18:32:42
|
Casper, You can remove the debug stuff from the wine source and replace it with ros debug. Replace TRACE with DPRINT and add ros #define NDEBUG than #include <debug.h>. That's one of the most simple things to do. We do not need wine debug headers at all. Based on what I know~~~ fyi, James ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: James T. <jim...@ad...> - 2001-10-26 18:05:48
|
> Steven Edwards wrote: > > It is part of IE. Just about anytime IE pukes on a webpage its spitting something from this file. > > -----Original Message----- > From: Phillip Susi > To: ros...@re... > Sent: 10/26/01 12:34 PM > Subject: [ros-kernel] Re: Sharing code with wine > > What is shlwapi? > > At 02:51 PM 10/26/2001 +0000, you wrote: > >Hi All! > >Is there anyone else other than me porting wine to ROS? I have made > some > >progress. I'm working on shlwapi and comctl32 for now. Wow what a mess! > >With shlwapi, I've moved headers in to the local directory instead of > placing > >them in the include/wine. Worry about that later. Browsing through the > >wine headers is a chore. > > > >Need help with windres, anyone have good examples of adding texted bin > >code in the rc files? ~Icon stuff~. > > > >Remember this is not a futile effort, the objective is to have a gui up > >and running for the gui/apps programmers. For me, this is a quick way > to > >learn Windows after purposely avoiding it for so long.. > > > > > >Thanks, > >James Hi, Yeah! Stream stuff! I'm porting what I think is a minimal dll set for now. Like; dll: library: 1) comctl32 -> user32 gdi32 advapi32 kernel32 ntdll * these 5, part of the core group, lz32 is another * 2) comdlg32 -> comctl32 shlwapi winspool.drv u/g/k/n core ?) shell32 -> ole32 shlwapi comctl32 u/g/a/k/n core ,,and so on. It begins to branch off into other dll's from here on. Oh another TODO is TARGET_BASE addresses! This is my "method of madness" 8^> for target porting of wine dlls. James Lessons learned from the great BG of borg, assimilate all software. My XP slap! ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-10-26 17:15:10
|
It is part of IE. Just about anytime IE pukes on a webpage its spitting something from this file. -----Original Message----- From: Phillip Susi To: ros...@re... Sent: 10/26/01 12:34 PM Subject: [ros-kernel] Re: Sharing code with wine What is shlwapi? At 02:51 PM 10/26/2001 +0000, you wrote: >Hi All! >Is there anyone else other than me porting wine to ROS? I have made some >progress. I'm working on shlwapi and comctl32 for now. Wow what a mess! >With shlwapi, I've moved headers in to the local directory instead of placing >them in the include/wine. Worry about that later. Browsing through the >wine headers is a chore. > >Need help with windres, anyone have good examples of adding texted bin >code in the rc files? ~Icon stuff~. > >Remember this is not a futile effort, the objective is to have a gui up >and running for the gui/apps programmers. For me, this is a quick way to >learn Windows after purposely avoiding it for so long.. > > >Thanks, >James ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ |
|
From: KJK::Hyperion <no...@li...> - 2001-10-26 17:08:05
|
At 21.40 25/10/2001 +0100, you wrote: > >For those who don't beleive how nls tables are loaded, get objdir (NT DDK) > >or WinObj (from Sysinternals) and have a look into the \NLS directory >Or ReactOS own objdir... ;-) Really??? Found it: reactos\apps\objdir... wow, this project never stops surprising me :) ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: KJK::Hyperion <no...@li...> - 2001-10-26 17:04:49
|
At 13.16 25/10/2001 -0400, you wrote: >Running the 16bit code is not a problem, you just create a 16bit v86 mode >code segment selector and jump to it. That's what I meant... > It's all of the support code for 16bit apps that is difficult. [...] ... and that's something I didn't ever imagine :) So, OK, 16 bit support can wait. However, what about WinE's 16 bit support? anything usable/portable? >At 06:44 PM 10/25/2001 +0200, you wrote: >Right. Emulation of 16 bit code should be fairly trivial, anyway, since >it's mostly a feature of the Intel architecture ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |