reactos-kernel

RE: [ros-kernel] Cleanup

[Steven E. <Ste...@ya...>]

> Maybe we can switch to a better revision control system. 
> There was an article on slashdot about bitkeeper. It has a 
> strange status (not open source), but it is used for linux kernel.

I would like to stick with cvs just because it will make importing a
fork of WINE easy.

Thanks
Steven

"Every revolution was once a thought in one man's mind"
- Ralph Waldo Emerson 

[ros-kernel] OpenWatcom

[Eugene I. <ge...@my...>]

Watcom compiler has been released as open source software.
http://www.openwatcom.org
Anyone brave enough to try to compile reactos with it? :)

ei

Re: [ros-kernel] Cleanup

[Eugene I. <ge...@my...>]

Maybe we can switch to a better revision control system. There was an
article on slashdot about bitkeeper. It has a strange status (not open
source), but it is used for linux kernel.

I don't know much about rcs, so don't kill me. Comments?

ei

----- Original Message -----
From: "Rex Jolliff" <re...@lv...>
To: <rea...@li...>
Sent: Tuesday, May 28, 2002 6:24 PM
Subject: Re: [ros-kernel] Cleanup


> At 12:34 AM 5/29/02 +0200, you wrote:
> >I have some time to do a cleanup of our code base. Is everyone using the
> >latest MinGW release (gcc-3.1, w32api-1.4) ? If not, please upgrade
> >soon. I will throw out our old Windows API headers and use MinGW
> >whereever possible to have better code sharing with WINE.
> >
> >I will start reorganizing CVS like we discussed on this list.
> >
> >Any last words, before I begin?
>
> If the reorganization of the repository is going to involve a large
> number of files, we can backdoor it by moving directories in the
> repository.  This of course will break old versions, which may not
> be a problem, but the version history will be preserved.  Of course
> the ideal approach is to move the files the cvs way, that is, with
> add/remove pairs for each file and a commit with a reasonable
> commit indicating the move.
>
>
> Rex Jolliff
> re...@lv...
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel
>

Re: [ros-kernel] Cleanup

[Rex J. <re...@lv...>]

At 12:34 AM 5/29/02 +0200, you wrote:
>I have some time to do a cleanup of our code base. Is everyone using the
>latest MinGW release (gcc-3.1, w32api-1.4) ? If not, please upgrade
>soon. I will throw out our old Windows API headers and use MinGW
>whereever possible to have better code sharing with WINE.
>
>I will start reorganizing CVS like we discussed on this list.
>
>Any last words, before I begin?

If the reorganization of the repository is going to involve a large
number of files, we can backdoor it by moving directories in the
repository.  This of course will break old versions, which may not
be a problem, but the version history will be preserved.  Of course
the ideal approach is to move the files the cvs way, that is, with
add/remove pairs for each file and a commit with a reasonable
commit indicating the move.


Rex Jolliff
re...@lv...

RE: [ros-kernel] Cleanup

[Steven E. <Ste...@ya...>]

> Any last words, before I begin?

Good Riddance =P

We still need to write the shell script for doing a import of the wine
makefiles and use the winebuild system. Currently we can use winebuild
to generate the *.defs we need.We can also use the wine resource
compiler so we don't have to fork the wine resources. What you have to
do is first feed the wine resources to wrc then feed the output of that
to windres. 

ONE MORE TIME - If anyone is feeling frisky and wants to help on my WINE
work email me already.

So what is the final outline for strucure of our cvs tree? This is the
way I think we have it but I want to double check. This is by no means a
compleate outline.

CVSROOT -
	-freeldr
	-rodocs
	-reactos.org
	-reactos
		-lib
		-tools
		-apps
		-ntoskrnl
		-services
		-hal
		-include
	-rosapps
		-sysutils
		-net
		-misc
	-win32 (wine tree + certain moved reactos/lib modules)
		-include
		-dlls
		-tools
		-programs
		?
	-psx
		-include
		?
	-React/OS2 =)
		-include
		-apps
		?


Thanks
Steven

"Every revolution was once a thought in one man's mind"
- Ralph Waldo Emerson 

[ros-kernel] Cleanup

[Casper H. <ch...@us...>]

I have some time to do a cleanup of our code base. Is everyone using the
latest MinGW release (gcc-3.1, w32api-1.4) ? If not, please upgrade
soon. I will throw out our old Windows API headers and use MinGW
whereever possible to have better code sharing with WINE.

I will start reorganizing CVS like we discussed on this list.

Any last words, before I begin?

- Casper

Re: [ros-kernel] Forward: "ReactOS is too limited"

[Eugene I. <ge...@my...>]

Now, that's a constructive discussion.

>   - why should people invest time and money on ReactOS?

To created an open source OS that is compatible with (let's hope) all
(commercial and free) Win32 software and win device drivers. I can write
pages about design features of nt/win32 that I think are superior to the
ones in Linux (and the other way too), but it's not the point. I think that
Windows will exist for the forseeable future and will be the most popular
desktop system for many years to come (despite all the recent progress of
Linux and Mac OS X), and  I think that having a windows clone is no less
important right now than having a unix clone. Plus, ReactOS is ideal for
someone who programs for Windows and wants to donate time for open source
development without first having to learn unix.



>   - how will ReactOS survive to legal actions from Microsoft?

Well, there are already several opensource projects that are intruding into
MS territory: Wine, LinuxNTFS, Samba, OpenOffice/StarOffice (+a number of
shareware msoffice clones) to name a few and there hasn't been much legal
action from MS. It may be that MS doesn't want to give these projects free
publicity or it may be just pointless to try and stop projects when hundreds
of people across the world have the source code. There are other

>   - isn't Windows too much of a moving target?

There weren't too many changes in nt kernel between Win2k and WinXP. Even
changes from NT 4 to Win2k are not that great. Same goes for Win32/GUI. Most
changes happened in server/networking components (ActiveDirectory, blah,
blah...), but these are probably not high priority areas for us right now.
As I understand the goal for the next version of windows is object-oriented
file system so we should have about 2 years to catch up with win2k.

ei

Re: [ros-kernel] Forward: "ReactOS is too limited"

[Eric K. <ek...@rz...>]

"KJK::Hyperion" <no...@li...> wrote:

> On the other hand, "my" guy makes interesting points:
>   - why should people invest time and money on ReactOS?
The question is not "why should people..." but "why do people like to...".
Because some people might like a free Windows-like OS. You don't have to
spent time and money. You can just lean back and wait until the work is
done.

>   - how will ReactOS survive to legal actions from Microsoft?
Read the 'Foundation' section on the website.

>   - isn't Windows too much of a moving target?
Do people really want a target that moves in unpredictable ways? Do people
like to pay for getting their asses kicked? I don't, and I guess there are a
lot of people out there who think the same. Think of .NET and Longhorn. Do
you need it on your PC? This *might* be useful for enterprise servers but I
don't want to run one.

Eric

RE: [ros-kernel] Forward: "ReactOS is too limited"

[Steven E. <Ste...@ya...>]

We should add this to the FAQ =P

>   - why should people invest time and money on ReactOS?
Why should anyone invest in NT/2K? Or Linux? Or anything else? Why are
we not all running VMS on VAX? The answer should be clear.

>   - how will ReactOS survive to legal actions from Microsoft?
Are they going to sue all of us? How about the over 400 copyright
holders in the WINE source tree alone? No, there will come a point where
there are more people contributing to ReactOS and Related
projects(MSYS,MINGW,WINE,etc) then there are Lawyers in M$ Legal.
Plus if we do as Jason and I want and setup ReactOS a non-profit they
wont want to touch  us for fear of more bad public relations and they
will try to act like we don't exist for as long a possible.

>   - isn't Windows too much of a moving target?
NO NO NO NO NO. I admin SCO unix boxes that are 10 years old. I work
with customers that cant give up DOS and Win3.1. Do you think MS can
change the install base overnight to .NET? Hell no, its not to much of a
moving target. I still run 16bit dos/win3.1 apps under XP. =P They have
the weekness of backward compatibltiy that we must exploit.

Thanks
Steven

"Every revolution was once a thought in one man's mind"
- Ralph Waldo Emerson 

Re: [ros-kernel] Forward: "ReactOS is too limited"

[Jason F. <jas...@ya...>]

--- "KJK::Hyperion" <no...@li...> wrote:
>On the other hand, "my" guy makes interesting points:
>- why should people invest time and money on ReactOS?

Because of the promise of application and driver compatibility.

>- how will ReactOS survive to legal actions from Microsoft?

Bill G said a Windows clone is allowable as long as their
intellectual property is protected. If we step on their intellectual
property then they should tell us how to get around it to clone what
we need to. As a monopoly, the law should give us some leeway. Also
commercial companies will fight these battles before we need to,
companies like Lindows.

>- isn't Windows too much of a moving target?

Not really. I'm sure we'll be able to keep up - as we get stronger.

- Jason






__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: [ros-kernel] Forward: "ReactOS is too limited"

[KJK::Hyperion <no...@li...>]

At 12.33 28/05/2002, you wrote:

[...]

no, no, no, please. This leads nowhere. It's a gratuitous flame bait
On the other hand, "my" guy makes interesting points:
  - why should people invest time and money on ReactOS?
  - how will ReactOS survive to legal actions from Microsoft?
  - isn't Windows too much of a moving target?

RE: [ros-kernel] Forward: "ReactOS is too limited"

[Steven E. <Ste...@ya...>]

/bitchslap 

KILL THIS THREAD NOW. We've had this discussion before and it has been
debated over and over on slashdot. If you want to argue NT vs LINUX take
it there.

Thanks
Steven

"Every revolution was once a thought in one man's mind"
- Ralph Waldo Emerson 

Re: [ros-kernel] Forward: "ReactOS is too limited"

[Stuart U. <man...@ki...>]

Koert van der Veer wrote:

>[snip]
>
>>After looking through reams of unhelpful (and sometimes contradictory)
>>
>Linux
>
>>FAQs and other DOCs, I ventured onto some Linux forums where I was told to
>>"RTFM" (by people with 5 inch thick glasses, a permanent hunch and acne
>>
>that
>
>>would make a leopard feel jealous, I have no doubt).
>>
>>The Linux command line is unhelpful, unfriendly and unforgiving. Maybe it
>>was useful in the past (to save disk space, processor power, memory, etc.)
>>to use an OS with a minimal amount of messages, but times have changed. We
>>live in an age where the minimum spec processor you can buy (at least in
>>
>the
>
>>UK) is 1 GHz and systems come with 512MB RAM standard.
>>
>>Linux may be good as a web server. Apache is an excellent program, but
>>people will be able to run the win32 version on ReactOS soon so what
>>possible use will Linux have then? (except maybe as a firewall - wow!).
>>
>
>You are exagerating here. For management tasks I prefer a commandline over a
>GUI. A commandline interface is usually easier to design, and is therefore
>often more informative. I really dislike using the mouse, and I feel I am
>forced to use it in a GUI.
>Linux is a perfect server-machine, though it has several disadvantages
>running it as a desktop OS. At home all my files are stored on my Debian
>server, which is also webserver, mail-server, filewall, router, etc... To
>work i use a windows machine. More and more often i find myself working on
>the server via Putty, because of it's wonderfull commandline interface...
>
>What use does a webserver have, wasting it's precious processorcycles on
>maintaining a desktopwindow? I guess the only enviroment that justifies a
>GUI (or more specifict to win32, the GDI) is a desktop machine.
>
>
>_______________________________________________________________
>
>Don't miss the 2002 Sprint PCS Application Developer's Conference
>August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
>_______________________________________________
>reactos-kernel mailing list
>rea...@li...
>https://lists.sourceforge.net/lists/listinfo/reactos-kernel
>
>
I suppose it depends who you're targetting Reactos for.
What i'd like to see is Reactos having an option to the end user - Do 
you want the gdi installed/enabled or not? (So if your using reactos as 
a server, the cpu isn't being "hogged" by the gdi)

I find a gui quite useful when administering things. I can actually see 
whats going on rather than looking at text on a terminal (Though it 
really depends what thing you are administering/monitoring, and if 
you're some newbie or not).
Although i do find commandlines very powerful when i want to do 
something complicated, and the gui is essentially restricted and cannot 
work for me.

What i find hard is to actually use linux as a dekstop - I just don't 
get the same feeling, and i'm constantly thinking how will i run Windows 
Game X on it, or
Y program. I simply can't get used to it, and i keep reverting to using 
windows. I'd like to use linux, but i just can't get to grips with it.

Re: [ros-kernel] Forward: "ReactOS is too limited"

[Koert v. d. V. <ko...@ic...>]

[snip]
>
> After looking through reams of unhelpful (and sometimes contradictory)
Linux
> FAQs and other DOCs, I ventured onto some Linux forums where I was told to
> "RTFM" (by people with 5 inch thick glasses, a permanent hunch and acne
that
> would make a leopard feel jealous, I have no doubt).
>
> The Linux command line is unhelpful, unfriendly and unforgiving. Maybe it
> was useful in the past (to save disk space, processor power, memory, etc.)
> to use an OS with a minimal amount of messages, but times have changed. We
> live in an age where the minimum spec processor you can buy (at least in
the
> UK) is 1 GHz and systems come with 512MB RAM standard.
>
> Linux may be good as a web server. Apache is an excellent program, but
> people will be able to run the win32 version on ReactOS soon so what
> possible use will Linux have then? (except maybe as a firewall - wow!).
>

You are exagerating here. For management tasks I prefer a commandline over a
GUI. A commandline interface is usually easier to design, and is therefore
often more informative. I really dislike using the mouse, and I feel I am
forced to use it in a GUI.
Linux is a perfect server-machine, though it has several disadvantages
running it as a desktop OS. At home all my files are stored on my Debian
server, which is also webserver, mail-server, filewall, router, etc... To
work i use a windows machine. More and more often i find myself working on
the server via Putty, because of it's wonderfull commandline interface...

What use does a webserver have, wasting it's precious processorcycles on
maintaining a desktopwindow? I guess the only enviroment that justifies a
GUI (or more specifict to win32, the GDI) is a desktop machine.

Re: [ros-kernel] Forward: "ReactOS is too limited"

[Patrick M. <ox...@st...>]

On Mon, May 27, 2002 at 01:10:38PM +0100, Nick Date wrote:

let's see this:
> > IMHO Reactos is too limited, it's doomed to an eternal pursuit to the
> > NT-based kernel functionalities, and whenever it will become a vague menace

vs. this:
> My experience of installing and using Linux includes Linux/X/one of the 5
> million window managers or whatever; not recognising three different
> graphics cards, and the one time I managed to get X to run with one of my
> graphics cards it tried to break my monitor. Nice.
> 
> After looking through reams of unhelpful (and sometimes contradictory) Linux
> FAQs and other DOCs, I ventured onto some Linux forums where I was told to
> "RTFM" (by people with 5 inch thick glasses, a permanent hunch and acne that
> would make a leopard feel jealous, I have no doubt).
> 
> The Linux command line is unhelpful, unfriendly and unforgiving. Maybe it
> was useful in the past (to save disk space, processor power, memory, etc.)
> to use an OS with a minimal amount of messages, but times have changed. We
> live in an age where the minimum spec processor you can buy (at least in the
> UK) is 1 GHz and systems come with 512MB RAM standard.
> 
> Linux may be good as a web server. Apache is an excellent program, but
> people will be able to run the win32 version on ReactOS soon so what
> possible use will Linux have then? (except maybe as a firewall - wow!).

with what right do you think you're allowed to bash his system (linux) and
on the other hand want to disallow him to bash yours (win32)?

with what right do you insult "the linux community" ("people with 5 inc thick
glasses etcpp) who you don't pay but expect them to wipe of your ass?

with what right do you argue about how I want to use my 1gb ram and 1.3ghz
cpu?

with what right do you think that the ia32-architecture is the only one around?



and how do you come to the idea that linux is the only command line oriented
OS around?

<irc class="people from linux forums">
/me wonders
</irc>

patrick mauritz
-- 
,------------------------------------------------------------------------.
>   In the Beginning there was nothing, which exploded - Yeah right...   <
|------------------------------------------------------------------------|
>       The Forthcoming OpenBIOS | www.freiburg.linux.de/openbios        <
`------------------------------------------------------------------------'
 If you gave an infinite number of monkeys an infinite number of typewr..
                         Hey! that's the internet!

Re: [ros-kernel] Forward: "ReactOS is too limited"

[Nick D. <nic...@ya...>]

Hi Hyperion,

----- Original Message -----
From: "KJK::Hyperion" <no...@li...>
To: "ReactOS-Kernel" <rea...@li...>
Sent: Sunday, May 26, 2002 3:53 AM
Subject: [ros-kernel] Forward: "ReactOS is too limited"


> my dear friend, klan-mate, and silent ReactOS advocate Juliet forwards me
> some criticism to our project from the sunny land of Usenet:

[Juliet wrote ...]

> IMHO Reactos is too limited, it's doomed to an eternal pursuit to the
> NT-based kernel functionalities, and whenever it will become a vague
menace

So NT is a limitation but Linux/Un*x isn't? I envisage the ROS kernel to be
NT compatible with a good POSIX subsystem to start with. Later on there will
always be room for additional subsystems (a feature that I believe many
developers will take full advantage of).

My experience of installing and using Linux includes Linux/X/one of the 5
million window managers or whatever; not recognising three different
graphics cards, and the one time I managed to get X to run with one of my
graphics cards it tried to break my monitor. Nice.

After looking through reams of unhelpful (and sometimes contradictory) Linux
FAQs and other DOCs, I ventured onto some Linux forums where I was told to
"RTFM" (by people with 5 inch thick glasses, a permanent hunch and acne that
would make a leopard feel jealous, I have no doubt).

The Linux command line is unhelpful, unfriendly and unforgiving. Maybe it
was useful in the past (to save disk space, processor power, memory, etc.)
to use an OS with a minimal amount of messages, but times have changed. We
live in an age where the minimum spec processor you can buy (at least in the
UK) is 1 GHz and systems come with 512MB RAM standard.

Linux may be good as a web server. Apache is an excellent program, but
people will be able to run the win32 version on ReactOS soon so what
possible use will Linux have then? (except maybe as a firewall - wow!).

> to M$, it would be badly put down with legal suits, the true alternative

How? Microsoft are an American company, and what holds up in a US court
would be thrown out in another country. Even looking at the Microsoft
license agreement raises big questions as to how legal it is and a
click-through contract isn't worth the paper it's written on. Offer and
acceptance? You can't accept something you haven't read.

Added to this, Bill Gates is probably the richest man in the world. He
brings in millions and millions of US dollars into the States every year, so
the chances are that the US government quite likes him (who wouldn't?).
Certainly over here the courts would see his company as a foreign capitalist
trying to destroy small local businesses or/and developers trying to make a
fair income.

The legality of the M$ EULA is about to be investigated by the EU, so watch
out Bill. No captialism in my back garden, thank you very much.

> would rather be building a new user-friendly frontend to
> Linux/FreeBSD/Hurd, like Apple did, only this time the frontend must be
> made open source, and errors such as the scattering of resources happening
> with Gnome vs. KDE must be avoided this time

Why? It's true that at best these window managers (? - why have more than
one in the first place?) can emulate a Mac/Win32 interface. At worst you
don't know what's going on with them half the time. A new wm would mean that
it wouldn't be complete (at least the "user-friendly" bit wouldn't be) for
quite some time so you'd have the added confusion of "yet another X wm"
(yaxwm - there you go. it's already sounding very Linux).

> Comments?

Sorry mate, but I had to say my piece. I have some serious issues regarding
the use of a clone of a 30 (?) year old operating system for anything other
than simple tasks. Live in the now, guys.

Regards,

Nick.

--
Nick Date
Bath, England, UK




---
Outgoing mail is certified virus free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.363 / Virus Database: 201 - Release Date: 21/05/2002


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[ros-kernel] CVS Commit: reactos

[Eric K. <ek...@rz...>]

services/fs/vfat/fsctl.c
    Fix to support removable media (512 bytes per sector only!).

services/stoarge/disk/disk.c
    Build a fake partition table for removable media drives.

services/storage/atapi/atapi.c
    Wait for BUSY to clear prior to selecting a drive. Disabled old code.


These changes enable the use of removable media devices such as MO (230Mb
disks tested) and Zip drives. To support larger disks, such as 640Mb or
1.3Gb MO disks, the vfat driver needs to support 1024 byte and 2048 byte
sectors.


Eric

RE: [ros-kernel] Use or not use

[Robert C. <rob...@it...>]

> -----Original Message-----
> From: rea...@li... 
> [mailto:rea...@li...] On Behalf 
> Of Jason Filby
>
>  Scott proposed we do a clean room
> implementation... but how do you do that with header files?

Same way as anything else. The person in the 'dirty room' reads
*everything* that they can without entering NDA's. They also document
everything that can be documented via reverse engineering.

They then produce a formal specification from that.

i.e. 
"image helper functions are to be defined in a C and C++ parseable
header file called imagehlp.h. The following structures must be defined
foo, bar and aleph. foo must contain exactly 5 members, with the
following symbolic names: a,b and c. a must be represented by an
unsigned 16 bit small-endian integral value... The following symbols
must be defined: beta, gamma and delta. beta must evaluate to the
integral value 16. gamma must evaluate to the integral value 45. "

And so on. Someone in the 'clean room' then reads the formal spec and
creates a set of headers. If the dirty room documenter did their job
well, those headers will interoperate for both compilation and binary
use immediately. If they didn't.... then you tell the dirty roomer that
they got something wrong, and they revise the documentation.

What happens is that the clean room person is deprived of the
implementation tricks that made the headers compact/maintable etc,
whilst still getting the interoperation information legitimatly.

Rob

Re: [ros-kernel] Use or not use

[Jason F. <jas...@ya...>]

I mailed Scott Christley, the guy who wrote windows.h, and it turns
out he did something similar. But when conferring with lawyers, they
agreed that it is still transformation. You have to get that
information from somewhere, so I figure any way you do it will amount
to transformation. Scott proposed we do a clean room
implementation... but how do you do that with header files?

- Jason

--- "KJK::Hyperion" <no...@li...> wrote:
> At 13.43 27/05/2002, you wrote:
> >3) Microsoft seems to have a policy that constants are only
> mentioned by 
> >name in the Windows DDK documentation, and they are defined in the
> header 
> >files, so I have copy/pasted them from there.
> 
> can they stop you from writing something like:
> 
> #define printconst(__x__) printf("%s = %d\n", #__x__, (__x__))
> 
> printconst(UNDOCUMENTED_CONSTANT_1);
> printconst(UNDOCUMENTED_CONSTANT_2);
> 
> /* etc. */
> 
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas --
> http://devcon.sprintpcs.com/adp/index.cfm
> 
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: [ros-kernel] crash within MmOpenMemoryAreaByAddress

[David W. <we...@cw...>]

On Tue, May 28, 2002 at 02:11:59AM +0200, Robert K. wrote:
> sorry for asking...
> but is this solution also SMP capable. AFAIK raising IRQL is processor local ?
> And may other CPUs run other processes' threads therewhile?
> 
Yes, raising the IRQL to DISPATCH_LEVEL will only block preemption on the
local CPU.

Re: [ros-kernel] Fwd: Reorganizing the cvs repository beforestarting reactos.org

[Robert K. <ro...@ko...>]

>

I have another view for all of you. What about considdering win32k with its drivers
and gdi.dll.... as a (native) graphics
_sub system_. A ss that has a kernelpart for doing some i/o ;-)

Winlogon is not essential for running programs. They're then run with all privileges,
but if some developer wants, he can
write an BeOS ss and write a logon for it.   Why bother?
Things like novell aren't possible then, but its his choice

>
>
> I consider win32k.sys as part of the Windows NT executive architecture
> and not part of the Win32 subsystem. Therefore I believe win32k.sys
> should be in the reactos module. I however, see no reason for building
> the Win32 subsystem if you are not developing or distributing this part,
> so the Win32 subsystem should go in it's own module.
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel

Re: [ros-kernel] crash within MmOpenMemoryAreaByAddress

[Robert K. <ro...@ko...>]

sorry for asking...
but is this solution also SMP capable. AFAIK raising IRQL is processor local ?
And may other CPUs run other processes' threads therewhile?

David Welch schrieb:

> On Thu, May 16, 2002 at 08:58:56PM +0200, Hartmut Birr wrote:
> > I doesn't understand your answer. I'm not sure, if my description of the
> > problem was right. The problem is the corrupted memory area queue from
> > kernel address space. Corruption of the queue is only possible, if there
> > occur two calls to a function which manipulate the queue (adding or
> > removing of entries). The queue is protected with a fast mutex of the
> > address space. This means, the corruption can only occur, if the calls
> > comes from the same thread. It is possible that a thread has locked the
> > address space and than a dpc or apc from the same thread is delivered
> > (completion function after a call to a device driver). This dpc or apc can
> > also lock the address space and manipulate the memory area queue. This does
> > corrupt the queue. The solution is to raise the irql at each manipulation
> > of the kernel address space. This disables the delivering of any dcp or apc
> > and the thread switching from irq 0.
> >
> I think I understand the description of the problem: the solution I am
> proposing if the locking is changed to a FASTMUTEX (so a thread holding
> the lock can't be interrrupted for an APC) and the functions that need to
> do address space operations from DISPATCH_LEVEL operate without touching
> the address space lock or any of the structures that are guarded by it
> then there is no need to go to DISPATCH_LEVEL (effectively a spinlock)
> when locking the address space.
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel

Re: [ros-kernel] Use or not use

[KJK::Hyperion <no...@li...>]

At 13.43 27/05/2002, you wrote:
>3) Microsoft seems to have a policy that constants are only mentioned by 
>name in the Windows DDK documentation, and they are defined in the header 
>files, so I have copy/pasted them from there.

can they stop you from writing something like:

#define printconst(__x__) printf("%s = %d\n", #__x__, (__x__))

printconst(UNDOCUMENTED_CONSTANT_1);
printconst(UNDOCUMENTED_CONSTANT_2);

/* etc. */

[ros-kernel] CVS Commit: reactos

[Hartmut B. <har...@te...>]

subsys\smss\init.c:
Fixed creation of paging file in SmPagingFilesQueryRoutine.

lib\kernel32\file\file.c:
Fixed returned file length in GetFileInformationByHandle.

- Hqartmut

Re: [ros-kernel] Use or not use

[Robert K. <ro...@ko...>]

I think there is a passus that restricts the use of the files to only
_MS_-windows developement

Since this header is exchangeable and its use is not forbidden (until now),
I'll use it for now.

Casper Hornstrup schrieb:

> man, 2002-05-27 kl. 10:15 skrev Jason Filby:
> > This actually opens a wider discussion about header files and
> > copyright in general. The only choice we really have is to go ahead
> > and use the header file information. Copy and paste doesn't make a
> > difference - since any kind of transformation still violates
> > copyright - even if you retype everything, it's still transformation.
> > We will just have to, if the time comes, defend our right to use
> > header file information for the sake of compatibility. Here's a paper
> > related to this point of view:
> >
> > http://eu.conecta.it/paper/Open_source_copyright_law.html
> >
> > My opinion at least (and the author of the paper).
> >
> > - Jason
>
> I hope that last sentence is correct; that header files are not
> completely copyrightable. Next month, I will be contributing a free
> Windows XP DDK to MinGW which is mostly copy/pasted from the Windows DDK
> documentation. Unfortunatly, some needed structures are not documented
> in the Windows DDK documentation. There are three cases: 1) The
> structures are not mentioned in the Windows DDK documentation, only in
> the header files. I have left most of these out since they are usually
> not important. 2) The structures are mentioned in the Windows DDK
> documentation, but only referenced by name from other structures. I have
> included these, copy/pasted them from the header files. 3) Microsoft
> seems to have a policy that constants are only mentioned by name in the
> Windows DDK documentation, and they are defined in the header files, so
> I have copy/pasted them from there.
> The Windows DDK documentation explicitly states that you may not copy
> any information in it without permission, but they will probably just
> state this in order to keep us from trying.
>
> - Casper
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel