Menu
▾
▴
reactos-kernel
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: Casper H. <ch...@us...> - 2001-10-07 11:49:23
|
On Saturday 06 October 2001 22:10, KJK::Hyperion wrote: > At 00.32 06/10/2001 -0700, you wrote: > > >From what I've read, this seems to be the best structure: > > > >user tutorials > >user reference > >application developer tutorials > >application developer reference > >kernel developer tutorials > >kernel developer reference > >architecture > > > >Comments? > > maybe something for sysadmins, between user and developer categories It sounds like you want ReactOS to be like the server editions of Windows NT. I don't think that ReactOS should go that way. Putting too many applications into "core" ReactOS will bloat it. IMHO, ReactOS should be distributed like the linux kernel, small and compact. Then the diffrent distribution companies (which will be there at some point!?!) can tailor their distribution to specific needs. Much like the way companies like RedHat, VA linux, Suse, etc. does with linux now. - Casper ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Richard C. <rc...@ca...> - 2001-10-07 11:36:43
|
New List question and app compatI also tried CDing to the dir, sorry I = forgot to add that. I tried submitting a new app report, but apparently that is broken. ----- Original Message -----=20 From: Steven Edwards=20 To: 'ros...@re...'=20 Sent: Sunday, October 07, 2001 6:03 AM Subject: [ros-kernel] New List question and app compat try ros...@re...=20 also just cd to the dir of the app your trying to run. for = applications compatiblty try the driver and app compatiblity database at = http://65.8.134.110 =20 -----Original Message-----=20 From: Richard Campbell=20 To: ros...@re...=20 Sent: 10/7/01 5:49 AM=20 Subject: [ros-kernel] New List?=20 Anyone ever thought about creating a new mailing list for App=20 compatibility?=20 Just an idea.=20 = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=20 =3D To remove yourself from this mailing list, go to =3D=20 =3D http://www.reactos.com/home/mailing.html =3D=20 = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=20 |
|
From: Steven E. <Ste...@kn...> - 2001-10-07 11:06:51
|
I'm not at my test box right now, but I think my C:\ partion is a 2.1 gig fat16. CVS builds from 2:30 AM and 12:30 PM -5 GMT OCT-06-01 Steve -----Original Message----- From: Hartmut Birr To: 'ros...@re...' Sent: 10/7/01 4:16 AM Subject: [ros-kernel] AW: is vfat broken again? > After pulling down the latest cvs and doing a build my test system now > hangs. it gets to the point of vfatfs loading and detects the hardrive > speacs but then hangs. After a few retrys it may make it passed this point > only to hang at loading the regitry files. The last changes doesn't work correct on a fat32 partition. In GetNextCluster is a dead lock, when there is no space on the disk and FAT32FindAvailableCluster can't find a free cluster over number 0xffff. I will fix the problem. - Hartmut ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-10-07 11:04:06
|
Thanks for taking the time to answer all of my questions. I'm going to hold off on trying to port anymore stuff and just fix with I have now. Also as soon as the vfat stuff is fixed again I will resume application testing for self-hosted builds. Steven |
|
From: Steven E. <Ste...@kn...> - 2001-10-07 11:01:52
|
try ros...@re... also just cd to the dir of the app your trying to run. for applications compatiblty try the driver and app compatiblity database at http://65.8.134.110 -----Original Message----- From: Richard Campbell To: ros...@re... Sent: 10/7/01 5:49 AM Subject: [ros-kernel] New List? Anyone ever thought about creating a new mailing list for App compatibility? Just an idea. ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Richard C. <rc...@ca...> - 2001-10-07 10:19:50
|
Hi all,
I tried to run a couple console programs that are on a win9x machine and
couldn't get reactos to 'see' that they were there. I tried typing the
complete name (e.g. c:\dir\program.exe) but it wouldn't see anything outside
the reactos dir. Is this intentional or a bug?
====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html =
====================================================
|
|
From: Richard C. <rc...@ca...> - 2001-10-07 09:50:54
|
Anyone ever thought about creating a new mailing list for App compatibility? Just an idea. ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Hartmut B. <har...@te...> - 2001-10-07 08:21:29
|
> After pulling down the latest cvs and doing a build my test system now > hangs. it gets to the point of vfatfs loading and detects the hardrive > speacs but then hangs. After a few retrys it may make it passed this point > only to hang at loading the regitry files. The last changes doesn't work correct on a fat32 partition. In GetNextCluster is a dead lock, when there is no space on the disk and FAT32FindAvailableCluster can't find a free cluster over number 0xffff. I will fix the problem. - Hartmut ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Jason F. <jas...@ya...> - 2001-10-07 07:26:31
|
We can put architecture in kernel reference if thats what everyone wants.... but it might be a nice to have a seperate book that looks at the 'big picture'. - Jason --- waltert3 <wal...@to...> wrote: > Sounds ok, but doesn't architecture fall in line with the Kernel > reference > itself. I'm not > trying to start anything. I'm just trying to figure the way that > wastes the > least amount of > resources. > > ----- Original Message ----- > From: "Phillip Susi" <ps...@cf...> > To: <ros...@re...> > Sent: Saturday, October 06, 2001 10:53 AM > Subject: [ros-kernel] Re: Proposed books for rosdocs > > > > Sounds good to me. > > > > At 12:32 AM 10/6/2001 -0700, you wrote: > > > >From what I've read, this seems to be the best structure: > > > > > >user tutorials > > >user reference > > >application developer tutorials > > >application developer reference > > >kernel developer tutorials > > >kernel developer reference > > >architecture > > > > > >Comments? > > >- Jason > > > > ==================================================== > > = 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 = > ==================================================== > __________________________________________________ Do You Yahoo!? NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Jason F. <jas...@ya...> - 2001-10-07 07:22:06
|
I doubt we'll have anything to put in that book for quite some time. We can implement it when the need arises. - Jason --- "KJK::Hyperion" <no...@li...> wrote: > At 00.32 06/10/2001 -0700, you wrote: > > >From what I've read, this seems to be the best structure: > >user tutorials > >user reference > >application developer tutorials > >application developer reference > >kernel developer tutorials > >kernel developer reference > >architecture > > > >Comments? > > maybe something for sysadmins, between user and developer > categories > > ==================================================== > = To remove yourself from this mailing list, go to = > = http://www.reactos.com/home/mailing.html = > ==================================================== > __________________________________________________ Do You Yahoo!? NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Richard C. <rc...@ca...> - 2001-10-07 04:33:55
|
is vfat broken again?The exact same thing happened to me. System Specs: Pentium 233 MMX 64 MB RAM 6.4 GB HD using a single FAT32 Partition. It hangs either after showing the partition specs or after (attempting) = to load the registry files. ----- Original Message -----=20 From: Steven Edwards=20 To: 'ros...@re...'=20 Sent: Saturday, October 06, 2001 11:16 PM Subject: [ros-kernel] is vfat broken again? After pulling down the latest cvs and doing a build my test system now = hangs. it gets to the point of vfatfs loading and detects the hardrive = speacs but then hangs. After a few retrys it may make it passed this = point only to hang at loading the regitry files. Thanks=20 Iso=20 |
|
From: Steven E. <Ste...@kn...> - 2001-10-07 04:15:15
|
After pulling down the latest cvs and doing a build my test system now hangs. it gets to the point of vfatfs loading and detects the hardrive speacs but then hangs. After a few retrys it may make it passed this point only to hang at loading the regitry files. Thanks Iso |
|
From: KJK::Hyperion <no...@li...> - 2001-10-06 21:12:55
|
At 00.32 06/10/2001 -0700, you wrote: > >From what I've read, this seems to be the best structure: >user tutorials >user reference >application developer tutorials >application developer reference >kernel developer tutorials >kernel developer reference >architecture > >Comments? maybe something for sysadmins, between user and developer categories ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: waltert3 <wal...@to...> - 2001-10-06 21:08:38
|
I think breaking it down into sections might be a more attentive way to do it. Persons seeking to make ReactOS development easier can then do it via writing books or web sites dedicated to such oversimplification. Although, again I think we can all agree that type of involvement is a ways off. ----- Original Message ----- From: "Frank D. Engel, Jr." <fd...@ya...> To: <ros...@re...> Sent: Friday, October 05, 2001 9:45 AM Subject: [ros-kernel] Re: rosdocs > Sounds good, but you might consider breaking down that third book into > "Application Development" and "Kernel Development" sections, or into > separate "books". > > --- Phillip Susi <ps...@cf...> wrote: > > I agree, and favor the three book system. > > > > At 05:30 PM 10/4/2001 -0400, you wrote: > > >Personally I think we should have either a two book or three book > > system. > > > > > >1) For end-user documentation including command and usage > > > > > >2) For developer documentation including API Reference and Kernel > > Internals > > > > > >or > > > > > >1) Quick Command and Usage Reference > > > > > >2) A More inept system reference (i.e. For systems administration) > > > > > >3) An in-depth kernel and API reference specifically geared towards > > >developers and active ReactOS team members > > > > > >As far as the laymen's tutorials that can be done to some degree > > later on > > >when the system is more complete. > > > > ==================================================== > > = To remove yourself from this mailing list, go to = > > = http://www.reactos.com/home/mailing.html = > > ==================================================== > > > > > ===== > ======= > Frank D. Engel, Jr. > Please note my new address: fd...@ya... > > __________________________________________________ > Do You Yahoo!? > NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. > http://geocities.yahoo.com/ps/info1 > > ==================================================== > = 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: waltert3 <wal...@to...> - 2001-10-06 21:06:41
|
Possibly, though I was thinking the OS theory (a.k.a. The guts) could be spread out as sort of a tutorial in the begining of the book and ReactOS, Win32, etc. API could be presented as a reference towards the back of the book. Of course the other two book method could also work. ----- Original Message ----- From: "KJK::Hyperion" <no...@li...> To: <ros...@re...> Sent: Friday, October 05, 2001 9:34 AM Subject: [ros-kernel] Re: rosdocs > At 17.30 04/10/2001 -0400, you wrote: > >Personally I think we should have either a two book or three book system. > [...] > >3) An in-depth kernel and API reference specifically geared towards > >developers and active ReactOS team members > > I'd split the last one into at least two books: > - Win32 API (and well-known extensions) > - The guts: OS structure, the Executive, device drivers, kernel services > interface, subsystems, and general kernel-mode programming > > since they are two very different and non-comparable fields, requiring > distinct abilities and knowledges > > ==================================================== > = 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: waltert3 <wal...@to...> - 2001-10-06 21:05:04
|
Sounds ok, but doesn't architecture fall in line with the Kernel reference itself. I'm not trying to start anything. I'm just trying to figure the way that wastes the least amount of resources. ----- Original Message ----- From: "Phillip Susi" <ps...@cf...> To: <ros...@re...> Sent: Saturday, October 06, 2001 10:53 AM Subject: [ros-kernel] Re: Proposed books for rosdocs > Sounds good to me. > > At 12:32 AM 10/6/2001 -0700, you wrote: > > >From what I've read, this seems to be the best structure: > > > >user tutorials > >user reference > >application developer tutorials > >application developer reference > >kernel developer tutorials > >kernel developer reference > >architecture > > > >Comments? > >- Jason > > ==================================================== > = 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: Eric K. <ek...@rz...> - 2001-10-06 18:22:57
|
Steven Edwards <Ste...@kn...> wrote: > Thanks Eric, it does help to answer some of the questions I have. I also was > able to get the programs to compile without a console. It ended up being a > typo in my makefile. > > Ok I'm still really new at this so feel free to tell me to shut up and guide > me to what book i need to read. I've been attempting to build the comctrl > lib that you wrote for wine under mingw but have a few questions before I > waste alot of time on it. > > 1. Wineserver emulates WinNT by default right? I understand the whole > Wraping X11->GDI and POSIX->Win32. But how generic is this? Should porting > these higher level libs be very hard? > Not exactly. Wine can emulate various windows versions (see '--winver' parameter). Wineserver is a single server instance that manages kernel objects and ipc, much like ntoskrnl. AFAICS, it should be pretty easy to port a high level dll. But stay away from the low level dll's, like ntdll, kernel32, advapi32, gdi32 and user32. They include the ugly X11<->GDI/USER and POSIX<->Win32 stuff which is *NOT* portable!!!! Some parts of ole/com are not portable too because they (will) use the wineserver. > 2. There is some redundant declarations in comctrl.h most of the redunacy > occurs in include/messages.h and defines.h. Also some declarations lacking > in windows.h that are wines winuser.h. How should this be aranged? > The common controls should only use 'windows.h', 'commctrl.h' and perhaps dll internal header files. Declarations that are missing in the reactos header files should be added to the reactos sdk header files. Unfortunately we are still using the old mingw header files. Extensive rework is needed to update the header file structure. > 3. From what I have already seen the UNICODE stuff looks like it will be > hard to fix. So the finaly queston is once again, am I going to be wasint my > time trying to port this? No, it is not that hard! Last week I had a long discussion with Guy Albertelli about missing and undocumented features in the common controls. We agreed on a method to implement the Unicode messages in ListView and TreeView. But this will take a few weeks since we are both busy with other tasks. Another problem is that someone (me!?) will have to check which controls are up-to-date and what is missing (e.g. balloon tooltips). At present it is a waste of time to port comctl32 or shell32 to reactos. :-( - Eric ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Phillip S. <ps...@cf...> - 2001-10-06 14:57:43
|
Sounds good to me. At 12:32 AM 10/6/2001 -0700, you wrote: > >From what I've read, this seems to be the best structure: > >user tutorials >user reference >application developer tutorials >application developer reference >kernel developer tutorials >kernel developer reference >architecture > >Comments? >- Jason ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Jason F. <jas...@ya...> - 2001-10-06 07:34:41
|
>From what I've read, this seems to be the best structure: user tutorials user reference application developer tutorials application developer reference kernel developer tutorials kernel developer reference architecture Comments? - Jason __________________________________________________ Do You Yahoo!? NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-10-06 05:53:16
|
Thanks Eric, it does help to answer some of the questions I have. I also was able to get the programs to compile without a console. It ended up being a typo in my makefile. Ok I'm still really new at this so feel free to tell me to shut up and guide me to what book i need to read. I've been attempting to build the comctrl lib that you wrote for wine under mingw but have a few questions before I waste alot of time on it. 1. Wineserver emulates WinNT by default right? I understand the whole Wraping X11->GDI and POSIX->Win32. But how generic is this? Should porting these higher level libs be very hard? 2. There is some redundant declarations in comctrl.h most of the redunacy occurs in include/messages.h and defines.h. Also some declarations lacking in windows.h that are wines winuser.h. How should this be aranged? 3. From what I have already seen the UNICODE stuff looks like it will be hard to fix. So the finaly queston is once again, am I going to be wasint my time trying to port this? Thanks for all your help Steven |
|
From: Eric K. <ek...@rz...> - 2001-10-06 01:06:04
|
Steven Edwards <Ste...@kn...> wrote: > I dont really understand the way the headers are organized in ReactOS. > > I saw the messages the other day about getting rid of ReactOS's headers and > just using mingw's. Can someone please explain to me what the deal is with > the structure. > The header file organization is indeed a little confusing. :-) ReactOS uses a single header file tree instead of two separate (SDK and DDK) trees. I'm sure M$ uses a similar system to build Windows. Basically we have five different classes of header files: 1) module internal header files 2) ddk header files 3) sdk header files 4) common header files The type 1) header files are only used inside of a module (synonyme for sys, exe or dll file). The directory 'ntoskrnl/include/internal' contains internal header files for ntoskrnl. The type 2) header files are used by user mode (win32) modules (exe and dll files). The most important (main) header file is 'include/windows.h'. The type 3) header files are used by kernel mode moduless and and some user mode modules. They reside in the 'include/ddk' directory. The main header file is 'include/ddk/ntddk.h' The type 4) header files contain common definitions (mostly constants and type declarations) that are used by kernel mode and user mode modules. The common header files can be found in 'include/ntos'. The header file structure is a little outdated and needs some rework but this must be done very carefully. I hope this answers your questions. - Eric ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Eric K. <ek...@rz...> - 2001-10-06 01:04:35
|
Steven Edwards <Ste...@kn...> wrote: > Hey Eric, I changed the lines in the Makefile of the programs but the > programs still spawn a console window on load. These were all winelib > programs so do I need to change something else in the code? I tested this a few minutes ago. It works on my machine. Did you rebuild the executable properly? To rebuild progman you'll have to run 'make progman_clean' and 'make progman'. - Eric ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-10-05 23:53:17
|
Hey Eric, I changed the lines in the Makefile of the programs but the programs still spawn a console window on load. These were all winelib programs so do I need to change something else in the code? -----Original Message----- From: Eric Kohl To: ros...@re... Sent: 10/3/01 6:35 PM Subject: [ros-kernel] Re: Here you go Zeno, simple gui tests needs comdlg32.dll Steven Edwards <Ste...@kn...> wrote: > > I'm still learning C so most of these have had very little changes. > I've attached a program manager clone. (thanks to Eric Kohl for fixing the > resource isssues)Icons dont work, plus I havent figured out how to get rid > of the damn console window when running any of the apps I've ported from > wine. Oooops, I guess this is my fault. I started progman from the command line only, so I didn't realize that it is still a console app. To make progman a gui app, you have to add '-Wl,--subsystem,windows' to the linker run. The fixed makfile rule to build progman is: progman.exe: $(OBJECTS) $(CC) $(CFLAGS) -Wl,--subsystem,windows $(OBJECTS) $(LIBS) -o progman.exe $(NM) --numeric-sort progman.exe > progman.sym > Zeno you want to help me with porting the comcrtl and commdlg libs from > wine? We need these before we can have a working shell. If you port the Wine comctl32 to ReactOS you have to be aware of the fact that some controls - mainly listview, treeview, rebar and toolbar - are still under construction and major rewrites will happen in the future. Treeview and listview don't handle unicode messages yet and adding unicode support results in a major rewrite of these controls. If you fix any bugs in the common controls, please make sure you submit patches to the Wine project too. - Eric Kohl ==================================================== = To remove yourself from this mailing list, go to = = http://www.reactos.com/home/mailing.html = ==================================================== |
|
From: Steven E. <Ste...@kn...> - 2001-10-05 23:40:20
|
I dont really understand the way the headers are organized in ReactOS. I saw the messages the other day about getting rid of ReactOS's headers and just using mingw's. Can someone please explain to me what the deal is with the structure. |
|
From: Steven E. <Ste...@kn...> - 2001-10-05 23:37:00
|
I dont really understand the way the headers are organized in ReactOS. I saw the messages the other day about getting rid of ReactOS's headers and just using mingw's. Can someone please explain to me what the deal is with the structure. |
8 messages has been excluded from this view by a project administrator.
