ReactOS - Recent changes [en]

Wiki Maintenance

DangerGround — Thu, 09 Sep 2010 07:18:44 GMT

← Older revision		Revision as of 07:18, 9 September 2010
Line 68:		Line 68:
	::Good idea, do you've time to write such a tool? --[[User:DangerGround\|DangerGround]] 07:31, 7 September 2010 (UTC)		::Good idea, do you've time to write such a tool? --[[User:DangerGround\|DangerGround]] 07:31, 7 September 2010 (UTC)
	:::I have the time. Unfortunately, I don't have the experience to do it. --[[User:CycleGeek\|CycleGeek]] 03:11, 9 September 2010 (UTC)		:::I have the time. Unfortunately, I don't have the experience to do it. --[[User:CycleGeek\|CycleGeek]] 03:11, 9 September 2010 (UTC)
		+	::::Choose a language where you can use svn tools, do a scan over trunk, check for lang folders and which languages are in there (with), save that somewhere (this task should be done on a regulare basis, e.g. cronjob). Maintain a list with languages. As query there should be two languages, normally english as base and a language to compare, e.g. german; now you go through your list and compare dates (or if the translation exists) and use some colors to make it visible. A next step would be to exclude wine ressources from list (there is a file WINE.README which contains wine-synces parts) --[[User:DangerGround\|DangerGround]]

	== ToDo ==		== ToDo ==
	* Categorize Events, probably use a template for a event navigation		* Categorize Events, probably use a template for a event navigation

Wiki Maintenance

CycleGeek — Thu, 09 Sep 2010 03:11:52 GMT

* translation pages:

← Older revision		Revision as of 03:11, 9 September 2010
Line 67:		Line 67:
	:Would it be possible to generate this information? e.g., Let a user select a language on some i18n page which generates a list of all the directories with a lang subfolder, along with the date of the last revision to the RC file. This wouldn't provide the actual translation status, but it would be automated and have all languages in ReactOS (as opposed to the list of 9 manually updated language lists here on the Wiki). --[[User:CycleGeek\|CycleGeek]] 21:08, 6 September 2010 (UTC)		:Would it be possible to generate this information? e.g., Let a user select a language on some i18n page which generates a list of all the directories with a lang subfolder, along with the date of the last revision to the RC file. This wouldn't provide the actual translation status, but it would be automated and have all languages in ReactOS (as opposed to the list of 9 manually updated language lists here on the Wiki). --[[User:CycleGeek\|CycleGeek]] 21:08, 6 September 2010 (UTC)
	::Good idea, do you've time to write such a tool? --[[User:DangerGround\|DangerGround]] 07:31, 7 September 2010 (UTC)		::Good idea, do you've time to write such a tool? --[[User:DangerGround\|DangerGround]] 07:31, 7 September 2010 (UTC)
		+	:::I have the time. Unfortunately, I don't have the experience to do it. --[[User:CycleGeek\|CycleGeek]] 03:11, 9 September 2010 (UTC)

	== ToDo ==		== ToDo ==
	* Categorize Events, probably use a template for a event navigation		* Categorize Events, probably use a template for a event navigation

Version Status

SuperDog — Tue, 07 Sep 2010 08:24:39 GMT

← Older revision		Revision as of 08:24, 7 September 2010
Line 1:		Line 1:
	{{Warning\|If you are not a developer and you want to edit the status of a component, then ask its current developer/maintainer first. Quote him on the Discussion page. This is mandatory to make sure the information is authoritative.}}		{{Warning\|If you are not a developer and you want to edit the status of a component, then ask its current developer/maintainer first. Quote him on the Discussion page. This is mandatory to make sure the information is authoritative.}}
-
-	~~Current maintainer: [[User:D0g\|D0g]]~~
-
-	~~Something is missing ? Leave me a note on IRC (<code style="display: inline">/msg MemoServ send SuperDog <your_msg></code>) or use my [[User_talk:D0g\|Talk page]].~~

	<table class="wikitable" border="1" cellpadding="3" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; width: 90%;">		<table class="wikitable" border="1" cellpadding="3" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; width: 90%;">

Wiki Maintenance

DangerGround — Tue, 07 Sep 2010 07:31:38 GMT

← Older revision		Revision as of 07:31, 7 September 2010
Line 66:		Line 66:
	:Russian has been updated once since 2006, French hasn't been updated since 2007. They obviously do not reflect current status and do not include a lot of languages that are in ReactOS. Additionally, many translation updates are now included in bug reports and the changelogs. --[[User:RideBMX\|RideBMX]] 18:37, 21 November 2009 (UTC)		:Russian has been updated once since 2006, French hasn't been updated since 2007. They obviously do not reflect current status and do not include a lot of languages that are in ReactOS. Additionally, many translation updates are now included in bug reports and the changelogs. --[[User:RideBMX\|RideBMX]] 18:37, 21 November 2009 (UTC)
	:Would it be possible to generate this information? e.g., Let a user select a language on some i18n page which generates a list of all the directories with a lang subfolder, along with the date of the last revision to the RC file. This wouldn't provide the actual translation status, but it would be automated and have all languages in ReactOS (as opposed to the list of 9 manually updated language lists here on the Wiki). --[[User:CycleGeek\|CycleGeek]] 21:08, 6 September 2010 (UTC)		:Would it be possible to generate this information? e.g., Let a user select a language on some i18n page which generates a list of all the directories with a lang subfolder, along with the date of the last revision to the RC file. This wouldn't provide the actual translation status, but it would be automated and have all languages in ReactOS (as opposed to the list of 9 manually updated language lists here on the Wiki). --[[User:CycleGeek\|CycleGeek]] 21:08, 6 September 2010 (UTC)
		+	::Good idea, do you've time to write such a tool? --[[User:DangerGround\|DangerGround]] 07:31, 7 September 2010 (UTC)

	== ToDo ==		== ToDo ==
	* Categorize Events, probably use a template for a event navigation		* Categorize Events, probably use a template for a event navigation

Template:Чобн

DangerGround — Tue, 07 Sep 2010 07:30:25 GMT

Reverted edits by CycleGeek (Talk) to last revision by Iyeru

← Older revision		Revision as of 07:30, 7 September 2010
Line 1:		Line 1:
-	~~<noinclude>{{del}}</noinclude>~~
-
	bgcolor=#AEF9AE\| Чакащо обновяване		bgcolor=#AEF9AE\| Чакащо обновяване

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Template:Чакащ

DangerGround — Tue, 07 Sep 2010 07:30:00 GMT

Reverted edits by CycleGeek (Talk) to last revision by CCTAHEB

← Older revision		Revision as of 07:30, 7 September 2010
Line 1:		Line 1:
-	~~<noinclude>{{del}}</noinclude>~~
-
	bgcolor=#AEF9AE\| Стар		bgcolor=#AEF9AE\| Стар

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Template:Незапочнат

DangerGround — Tue, 07 Sep 2010 07:29:38 GMT

Reverted edits by CycleGeek (Talk) to last revision by Iyeru

← Older revision		Revision as of 07:29, 7 September 2010
Line 1:		Line 1:
-	~~<noinclude>{{del}}</noinclude>~~
-
	bgcolor=#F9AEAE\| Незапочнат		bgcolor=#F9AEAE\| Незапочнат

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Template:Стар

DangerGround — Tue, 07 Sep 2010 07:29:10 GMT

Reverted edits by CycleGeek (Talk) to last revision by Iyeru

← Older revision		Revision as of 07:29, 7 September 2010
Line 1:		Line 1:
-	~~<noinclude>{{del}}</noinclude>~~
-
	bgcolor=#AAAA00\| Стар		bgcolor=#AAAA00\| Стар

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Template:Wine

DangerGround — Tue, 07 Sep 2010 07:28:49 GMT

Reverted edits by CycleGeek (Talk) to last revision by Iyeru

← Older revision		Revision as of 07:28, 7 September 2010
Line 1:		Line 1:
-	~~<noinclude>{{del}}</noinclude>~~
-
	bgcolor=#dddddd\| WINE		bgcolor=#dddddd\| WINE

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Template:Качен

DangerGround — Tue, 07 Sep 2010 07:28:33 GMT

Reverted edits by CycleGeek (Talk) to last revision by Iyeru

← Older revision		Revision as of 07:28, 7 September 2010
Line 1:		Line 1:
-	~~<noinclude>{{del}}</noinclude>~~
-
	bgcolor=#00FF00\| Качен		bgcolor=#00FF00\| Качен

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Bulgarian translation

DangerGround — Tue, 07 Sep 2010 07:27:17 GMT

Reverted edits by CycleGeek (Talk) to last revision by CCTAHEB

Show changes

Talk:Wine Debugging

CycleGeek — Mon, 06 Sep 2010 23:14:24 GMT

moved [[Talk:Wine Debugging]] to [[Talk:Voting/Wine debugging]] Reflect this was a vote, not an article on Wine debugging

New page

Wine Debugging

CycleGeek — Mon, 06 Sep 2010 23:14:24 GMT

moved [[Wine Debugging]] to [[Voting/Wine debugging]] Reflect this was a vote, not an article on Wine debugging

New page

TCPIP.SYS

CycleGeek — Mon, 06 Sep 2010 23:03:50 GMT

Mark outdated

← Older revision		Revision as of 23:03, 6 September 2010
Line 1:		Line 1:
		+	{{outdated}}
		+
	It's been a long time since I edited this page. Here's where I am:		It's been a long time since I edited this page. Here's where I am:
-	~~== What needs work==~~

		+	== What needs work==
	Paste From discussion with Arty in #ReactOS		Paste From discussion with Arty in #ReactOS
-

	1) fixing irp cancellation would make the situation much better		1) fixing irp cancellation would make the situation much better
Line 36:		Line 37:


-	== Yet Newer ~~Newes~~ ==	+	== Yet Newer News ==
-		+
	We're basically good on functionality at this point, plus or minus some details. The		We're basically good on functionality at this point, plus or minus some details. The
	biggest problem right now is stability around socket close time. I've embarked on		biggest problem right now is stability around socket close time. I've embarked on
Line 43:		Line 43:

	== New News ==		== New News ==
-		+	Well I'm making slow progress on tcpip.sys. I feel more confident with it than before after cleaning up and clearing up many small allocations and much misuse of PC(Packet)->DLComplete and kin. Now each function which sends a packet takes a callback and context from the parent, and stores it someplace guaranteed not to overlap somebody else's callback.
-	Well i'm making slow progress on tcpip.sys. I feel more confident with it than before after cleaning up and clearing up many small allocations and much misuse of PC(Packet)->DLComplete and kin. Now each function which sends a packet takes a callback and context from the parent, and stores it someplace guaranteed not to overlap somebody else's callback.	+

	There's no swapping of callback info into ndis packet context area any longer. It's used by datalink/lan.c to call the neighbor, and arp back only.		There's no swapping of callback info into ndis packet context area any longer. It's used by datalink/lan.c to call the neighbor, and arp back only.
Line 51:		Line 50:

	* arp and neighbor may send a packet on the wire using the interface transmit function.		* arp and neighbor may send a packet on the wire using the interface transmit function.
-
	* Everyone else uses IPSendDatagram, which uses the same code path for all datagrams.		* Everyone else uses IPSendDatagram, which uses the same code path for all datagrams.
-
	* Neighbor takes a small hit and uses the same code path for every datagram as well.		* Neighbor takes a small hit and uses the same code path for every datagram as well.

Line 61:		Line 58:

	== Old News ==		== Old News ==
-
	oskittcp is now available as a separate userland library, and has an application in apps/tests/oskittcp		oskittcp is now available as a separate userland library, and has an application in apps/tests/oskittcp
	that uses it. Our goal is to make it work right in all cases. Royce Mitchell has volunteered to work		that uses it. Our goal is to make it work right in all cases. Royce Mitchell has volunteered to work

WinDNS

CycleGeek — Mon, 06 Sep 2010 23:02:41 GMT

Mark outdated

← Older revision		Revision as of 23:02, 6 September 2010
Line 1:		Line 1:
-	~~It's implemented by dnsapi.dll. Several things are missing that I'm putting in to try to make~~	+	{{outdated}}
-	~~everything go. The main thing I'm doing now is working on GetNetworkParams in iphlpapi.~~	+
-	~~Specifically, it needs to return a valid DNS server list.~~	+

-	I ~~took iphlpapi_main from Juan Lang's wine version and merged it~~. The ~~iphlpapi part needed~~	+	WinDNS is implemented by dnsapi.dll. Several things are missing that I am putting in to try to make everything go. The main thing I'm doing now is working on GetNetworkParams in iphlpapi. Specifically, it needs to return a valid DNS server list.
-	~~by windns~~ is ~~totally done~~.	+

-	I ~~finished off compatibility with wine~~. ~~We have our own *_reactos~~.c files that have our OS-specific stuff. These will use the NtDeviceIoControl scheme with codes IOCTL_TCP_QUERY_INFORMATION_EX and IOCTL_TCP_SET_INFORMATION_EX. I need to have these types of information taken from tcpip:	+	I took iphlpapi_main from Juan Lang's Wine version and merged it. The iphlpapi part needed by WinDNS is totally done.

-	entity type (CLASS_GENERIC/TYPE_PROVIDER/ENTITY_TYPE_ID)	+	I finished off compatibility with Wine. We have our own <tt>*_reactos.c</tt> files that have our OS-specific stuff. These will use the NtDeviceIoControl scheme with codes IOCTL_TCP_QUERY_INFORMATION_EX and IOCTL_TCP_SET_INFORMATION_EX. I need to have these types of information taken from TCP/IP:
-	entity id set (done)	+
-	interface mib (CLASS_PROTOCOL/TYPE_PROVIDER/IF_MIB_STATS_ID)	+	* entity type (CLASS_GENERIC/TYPE_PROVIDER/ENTITY_TYPE_ID)
-	tcpip mib (CLASS_PROTOCOL/TYPE_PROVIDER/IP_MIB_STATS_ID)	+	* entity id set (done)
-	route list (CLASS_PROTOCOL/TYPE_PROVIDER/IP_MIB_ROUTETABLE_ENTRY_ID)	+	* interface mib (CLASS_PROTOCOL/TYPE_PROVIDER/IF_MIB_STATS_ID)
-	address list (CLASS_PROTOCOL/TYPE_PROVIDER/IP_MIB_ADDRTABLE_ENTRY_ID, partly done)	+	* tcpip mib (CLASS_PROTOCOL/TYPE_PROVIDER/IP_MIB_STATS_ID)
		+	* route list (CLASS_PROTOCOL/TYPE_PROVIDER/IP_MIB_ROUTETABLE_ENTRY_ID)
		+	* address list (CLASS_PROTOCOL/TYPE_PROVIDER/IP_MIB_ADDRTABLE_ENTRY_ID, partly done)

	And these to be there:		And these to be there:
Line 19:		Line 18:
	Add/Delete route (both use CLASS_PROTOCOL/TYPE_PROVIDER/IP_MIB_ROUTETABLE_ENTRY_ID)		Add/Delete route (both use CLASS_PROTOCOL/TYPE_PROVIDER/IP_MIB_ROUTETABLE_ENTRY_ID)

-	Side jaunt #2: be able to add a route to the ~~reactos tcpip~~ stack (also needs iphlpapi).	+	Side jaunt #2: be able to add a route to the ReactOS TCP/IP stack (also needs iphlpapi).

-	I started the ~~tcp~~/ip part. There's some info retrieval there already but it was not hooked up. I've hooked in those functions and now am fleshing out the types of information that can be returned by IOCTL_TCP_QUERY_INFORMATION_EX. Also, I'm doing small patches to other parts of ~~tcpip~~ where applicable. I just made the 'SubnetMask' value in the registry effective.	+	I started the TCP/IP part. There's some info retrieval there already but it was not hooked up. I've hooked in those functions and now am fleshing out the types of information that can be returned by IOCTL_TCP_QUERY_INFORMATION_EX. Also, I'm doing small patches to other parts of TCP/IP where applicable. I just made the 'SubnetMask' value in the registry effective.

AFD.SYS

CycleGeek — Mon, 06 Sep 2010 23:02:29 GMT

Mark outdated

← Older revision		Revision as of 23:02, 6 September 2010
Line 1:		Line 1:
-	~~AFD Structure:~~	+	{{outdated}}

-	It was complicated before. Here's how it works now:	+	It was complicated before. Here's how it works now:

-	Each AFD_FCB has a read and write buffer which currently holds up to one packet. For better performance, we can make this buffering scheme better. For the sake of simplicity, it's the way it is now.	+	Each AFD_FCB has a read and write buffer which currently holds up to one packet. For better performance, we can make this buffering scheme better. For the sake of simplicity, it's the way it is now.

-	Each socket can have at most one send ~~irp~~ active at a time. Others either wait or do nothing depending on whether they're for stream or packet sockets. This too can be improved but again does no real harm.	+	Each socket can have at most one send IRP active at a time. Others either wait or do nothing depending on whether they're for stream or packet sockets. This too can be improved but again does no real harm.

-	Each socket has at most one receive ~~irp~~ active at a time (or listen ~~irp~~ for a listen socket). The TDI provider completes the irp when some data arrives, and we relaunch it when our buffer is empty.	+	Each socket has at most one receive IRP active at a time (or listen IRP for a listen socket). The TDI provider completes the irp when some data arrives, and we relaunch it when our buffer is empty.

-	Select is accomplished by calls to PollReeval in ReceiveComplete, SendComplete, AfdReadData and AfdWriteData. Each time PollReeval is called, a select ~~irp~~ could get completed.	+	Select is accomplished by calls to PollReeval in ReceiveComplete, SendComplete, AfdReadData and AfdWriteData. Each time PollReeval is called, a select IRP could get completed.

	Apart from that the rest is bookkeeping.		Apart from that the rest is bookkeeping.

LAN.SYS

CycleGeek — Mon, 06 Sep 2010 23:02:18 GMT

Mark outdated

← Older revision		Revision as of 23:02, 6 September 2010
Line 1:		Line 1:
-	A simple adapter neutral driver for sending and receiving packets from ~~ndis~~ adapters, querying adapters, and assigning and querying protocol addresses.	+	{{outdated}}
		+
		+	A simple adapter neutral driver for sending and receiving packets from NDIS adapters, querying adapters, and assigning and querying protocol addresses.

	It supports these operations:		It supports these operations:

-	Read -- Get the next packet that matches our target type	+	* Read - Get the next packet that matches our target type
-	Write -- Put a packet on the indicated adapter, building a link layer header as appropriate	+	* Write - Put a packet on the indicated adapter, building a link layer header as appropriate
-		+	* LookupAddress - Match a partial address (either the protocol address or the link layer address) on the indicated adapter and return the full address.
-	LookupAddress -- Match a partial address on the indicated adapter and return the full ~~address. Match can be against either the protocol address or the link layer~~ address.	+	* PushAddress - Set an address mapping, deleting previous matching protocol addresses.
-		+	* EraseAddress - Remove matching address mappings.
-	PushAddress -- Set an address mapping, deleting previous matching protocol addresses.	+	* EnumAdapters - Return an array of adapter indices.
-		+	* Bufferedmode - Set buffered mode to allow userland use of NtReadFile in lan.sys (mostly testing).
-	EraseAddress -- Remove matching address mappings.	+	* AddAddress - Set an address association for the indicated adapter. This will be considered to be a local address and will be associated with the adapter's link layer address.
-		+	* RemAddress - Remove a local address from the indicated adapter.
-	EnumAdapters -- Return an array of adapter indices.	+	* AdapterInfo - Return a struct containing information about the indicated adapter, including its ndis registry key, speed, link layer address, etc.
-		+	* Sending a packet from LAN.SYS: fill out a LAN_PACKET_HEADER and do WriteFile on it. The specified link layer address will be used as the target address. A zero-length address means broadcast.
-	Bufferedmode -- Set buffered mode to allow userland use of NtReadFile in lan.sys (mostly testing).	+	* Receiving a packet from LAN.SYS: just do ReadFile on a buffer and wait for a LAN_PACKET_HEADER to appear.
-		+
-	AddAddress -- Set an address association for the indicated adapter. This will be considered to be a local address and will be associated with the adapter's link layer address.	+
-		+
-	RemAddress -- Remove a local address from the indicated adapter.	+
-		+
-	AdapterInfo -- Return a struct containing information about the indicated adapter, including its ndis registry key, speed, link layer address, etc.	+
-		+
-	Sending a packet from LAN.SYS: fill out a LAN_PACKET_HEADER and do WriteFile on it. The specified link layer address will be used as the target address. A zero-length address means broadcast.	+
-		+
-	Receiving a packet from LAN.SYS: just do ReadFile on a buffer and wait for a LAN_PACKET_HEADER to appear.	+

Wiki Maintenance

CycleGeek — Mon, 06 Sep 2010 21:08:09 GMT

* translation pages: idea: auto-generate some of this info

← Older revision		Revision as of 21:08, 6 September 2010
Line 65:		Line 65:
	IMO they should go, not used for ages. Translators should be visible over svn commit messages. --[[User:DangerGround\|DangerGround]] 17:01, 18 November 2009 (UTC)		IMO they should go, not used for ages. Translators should be visible over svn commit messages. --[[User:DangerGround\|DangerGround]] 17:01, 18 November 2009 (UTC)
	:Russian has been updated once since 2006, French hasn't been updated since 2007. They obviously do not reflect current status and do not include a lot of languages that are in ReactOS. Additionally, many translation updates are now included in bug reports and the changelogs. --[[User:RideBMX\|RideBMX]] 18:37, 21 November 2009 (UTC)		:Russian has been updated once since 2006, French hasn't been updated since 2007. They obviously do not reflect current status and do not include a lot of languages that are in ReactOS. Additionally, many translation updates are now included in bug reports and the changelogs. --[[User:RideBMX\|RideBMX]] 18:37, 21 November 2009 (UTC)
		+	:Would it be possible to generate this information? e.g., Let a user select a language on some i18n page which generates a list of all the directories with a lang subfolder, along with the date of the last revision to the RC file. This wouldn't provide the actual translation status, but it would be automated and have all languages in ReactOS (as opposed to the list of 9 manually updated language lists here on the Wiki). --[[User:CycleGeek\|CycleGeek]] 21:08, 6 September 2010 (UTC)

	== ToDo ==		== ToDo ==
	* Categorize Events, probably use a template for a event navigation		* Categorize Events, probably use a template for a event navigation

Template:Чобн

CycleGeek — Mon, 06 Sep 2010 17:06:24 GMT

MFD: No longer used

← Older revision		Revision as of 17:06, 6 September 2010
Line 1:		Line 1:
		+	<noinclude>{{del}}</noinclude>
		+
	bgcolor=#AEF9AE\| Чакащо обновяване		bgcolor=#AEF9AE\| Чакащо обновяване

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Template:Чакащ

CycleGeek — Mon, 06 Sep 2010 17:06:20 GMT

MFD: No longer used

← Older revision		Revision as of 17:06, 6 September 2010
Line 1:		Line 1:
		+	<noinclude>{{del}}</noinclude>
		+
	bgcolor=#AEF9AE\| Стар		bgcolor=#AEF9AE\| Стар

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Template:Стар

CycleGeek — Mon, 06 Sep 2010 17:06:17 GMT

MFD: No longer used

← Older revision		Revision as of 17:06, 6 September 2010
Line 1:		Line 1:
		+	<noinclude>{{del}}</noinclude>
		+
	bgcolor=#AAAA00\| Стар		bgcolor=#AAAA00\| Стар

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Template:Незапочнат

CycleGeek — Mon, 06 Sep 2010 17:06:10 GMT

MFD: No longer used

← Older revision		Revision as of 17:06, 6 September 2010
Line 1:		Line 1:
		+	<noinclude>{{del}}</noinclude>
		+
	bgcolor=#F9AEAE\| Незапочнат		bgcolor=#F9AEAE\| Незапочнат

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Template:Качен

CycleGeek — Mon, 06 Sep 2010 17:06:07 GMT

MFD: No longer used

← Older revision		Revision as of 17:06, 6 September 2010
Line 1:		Line 1:
		+	<noinclude>{{del}}</noinclude>
		+
	bgcolor=#00FF00\| Качен		bgcolor=#00FF00\| Качен

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Template:Wine

CycleGeek — Mon, 06 Sep 2010 17:04:15 GMT

MFD: No longer used

← Older revision		Revision as of 17:04, 6 September 2010
Line 1:		Line 1:
		+	<noinclude>{{del}}</noinclude>
		+
	bgcolor=#dddddd\| WINE		bgcolor=#dddddd\| WINE

	<noinclude>[[Category:Template]]</noinclude>		<noinclude>[[Category:Template]]</noinclude>

Bulgarian translation

CycleGeek — Mon, 06 Sep 2010 16:37:29 GMT

replace Bulgarian color templates with bgcolor

Show changes

CMake

CycleGeek — Sun, 05 Sep 2010 23:35:54 GMT

copyedit: Reorganize into sections, remove: generic build commands (link through "See also" section)

← Older revision		Revision as of 23:35, 5 September 2010
Line 1:		Line 1:
-	~~Here are few steps required for compiling the branch (using Windows XP)~~:	+	[http://www.cmake.org/ CMake] is a cross-platform build system. It is a proposed alternative to [[RBuild]].

		+	== Preparing the Build Environment ==
		+	To build using CMake the <tt>cmake-bringup</tt> branch must first be [[Subversion/Using the command line client#Checking out the sources\|checked out]]. After obtaining the source, the following two subfolders must be created:
		+	* <tt>build</tt>
		+	* <tt>build-ros</tt>

-	~~1. First of all we will need CMake from the [http://www.cmake.org CMake] homepage. While installing please do not forget about adding it~~ to the <tt>~~PATH~~</tt> ~~variable. (You will probably need~~ to ~~logout from your account to apply the changes~~.)	+	Navigate to the tools subfolder in the RosBE folder and copy <tt>make.exe</tt> to <tt>mingw32-make.exe</tt>.

		+	== Building ==
		+	To build the branch the build tools must first be compiled using CMake. This needs to be done for the first build and whenever there is a change to the build tools.

-	2. ~~Checkout the branch: http://svn~~.~~reactos~~.~~org/svn/reactos/branches/cmake-bringup/ (read more about subversion [[Subversion\|here]])~~	+	cd build
		+	cmake -G "MinGW Makefiles" ..\
		+	make
		+	cd ..

		+	With the build tools compiled, ReactOS can now be compiled. In the case of <tt>CMakeLists</tt> being updated it is best to remove the content of the <tt>build-ros</tt> folder and rebuild ReactOS.

-	~~3. Create two more folders in <tt>~~cmake-~~bringup</tt>:~~	+	cd build-ros
		+	cmake -G "MinGW Makefiles" -DCMAKE_TOOLCHAIN_FILE=toolchain-mingw32.cmake ..\
		+	make

-	~~<pre>mkdir build~~	+	== See also ==
-	~~mkdir build-ros</pre>~~	+	* [[Building ReactOS]]
		+	* [[Building Modules]]

-	~~Now go to your RosBE folder and in 'tools' subfolder copy make.exe to mingw32-make.exe.~~	+	[[Category:Building]]
-		+
-		+
-	~~4. Launch the RosBE command line. First we are going to build tools (you can change <code>make</code> to <code>makex</code> to use more than one processor/core)~~:	+
-		+
-	~~<pre>cd build~~	+
-	~~cmake -G "MinGW Makefiles" ..\~~	+
-	~~make~~	+
-	~~cd ..</pre>~~	+
-		+
-		+
-	~~5. Now we can build ReactOS source using freshly compiled tools:~~	+
-		+
-	~~<pre>cd build-ros~~	+
-	~~cmake -G "MinGW Makefiles" -DCMAKE_TOOLCHAIN_FILE=toolchain-mingw32.cmake ..\~~	+
-	~~make~~	+
-	~~(cd ..) <- optionally</pre>~~	+
-		+
-		+
-	~~You can also build any of the modules separately, like:~~	+
-		+
-	~~<pre>make icu4ros</pre>~~	+
-		+
-		+
-	~~Or clean any of them, like:~~	+
-		+
-	~~<pre>make icu4ros clean</pre>~~	+
-		+
-		+
-	~~List of modules and build targets is available using:~~	+
-		+
-	~~<pre>make help</pre>~~	+
-		+
-		+
-	~~To clean the whole tree (like in RBuild):~~	+
-		+
-	~~<pre>make clean</pre>~~	+
-		+
-		+
-	~~6. As build tools are not changing very often, contents of <tt>build</tt> folder can be compiled once and does not need recompilation with every commit.~~	+
-		+
-	~~In case of any updated CMakeLists from other folders (like ReactOS headers, libraries or apps), it is best to remove content of <tt>build-ros</tt> folder, and repeat step 5~~	+

Assembly

ThePhysicist — Sun, 05 Sep 2010 15:51:06 GMT

New page

To make our assembly code compatible with both the GNU assembler and the MS assembler, a kind of meta language needs to be implemented using a mixture of preprocessor macros and asm macros.

This is an attempt to create a compatible language. This is WIP.

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%"
| Directive
| GAS
| MASM/ML/ML64
| Meaning
|-
|| .global <symbol> || .global <symbol> || PUBLIC <symbol> || Make <symbol> global.
|-
|| .extern <symbol> || - || EXTERN || Tell the assembler that <symbol> is in an external file.
|-
|| if <expression> || .if <expression> || if <expression> || Conditional compilation.
|-
|| .align <alignment> || .align <alignment> || ALIGN <alignment>
|}

User:ThePhysicist

ThePhysicist — Sun, 05 Sep 2010 15:15:37 GMT

← Older revision		Revision as of 15:15, 5 September 2010
Line 63:		Line 63:

	[[user:ThePhysicist/Hardware \| My Hardware ]]		[[user:ThePhysicist/Hardware \| My Hardware ]]
		+
		+	[[Assembly]]

	[[Bootstate]]		[[Bootstate]]

ReactOS Remote Debugger

CycleGeek — Sun, 05 Sep 2010 01:35:59 GMT

Move Description to head, section headings, misc. changes

← Older revision		Revision as of 01:35, 5 September 2010
Line 1:		Line 1:
-	== ReactOS Remote Debugger ==	+	'''ReactOS Remote Debugger''' is a debugging shell that can take protocol modules (currently only for talking to [[Kdbg\|KDBG]]), <tt>.nostrip</tt> files from the ReactOS build, and aggregate information in a way that is a bit impractical in KDBG. It is a Windows forms application (C#) with a number of window types, a simple poor man's dockability, and tabs.

-	~~=== Source code ===~~	+	It has a local variables window, backtrace, debug interaction, threads and processes. It can display a lot of info, and will become more useful as features are fleshed out.

		+	== Source code ==
	svn://svn.reactos.org/reactos/trunk/tools/reactosdbg		svn://svn.reactos.org/reactos/trunk/tools/reactosdbg

-	=== Binaries ===	+	== Binaries ==
	Unofficial download link: [http://www.4shared.com/file/128096613/1eb0dcad/RosDBG-42955.html Rev-42955].		Unofficial download link: [http://www.4shared.com/file/128096613/1eb0dcad/RosDBG-42955.html Rev-42955].

-	~~=== Description ===~~	+	== Setting it up ==
-		+	You need a full build with <code>ROS_BUILDNOSTRIP=yes</code>. Clean before building it the first time as already built (and up to date) modules will not be rebuilt. Do it like this:
-	It's a debugging shell that can take protocol modules (currently only for talking to [[Kdbg \| KDBG]]), .nostrip files from the ReactOS build, and aggregate information in a way that's a bit impractical in KDBG. It's a windows forms app (C#) with a number of window types, a simple poor man's dockability, and tabs.	+
-		+
-	~~It's got a local variables window, backtrace, debug interaction, threads and processes. It can display a lot of info, and will become more useful as features are fleshed out.~~	+
-		+
-	=== Setting it up ===	+
-		+
-	You need a full build with ROS_BUILDNOSTRIP=yes. Clean before building it the first time, as already built (and up to date) modules ~~won't~~ be rebuilt. Do it like this:	+

	make ROS_BUILDNOSTRIP=yes bootcd		make ROS_BUILDNOSTRIP=yes bootcd

-	Now that you've got symbols, select your source directory and output directory in the 'Extras\|Settings...' menu of ReactOS Remote Debugger. Set the source ~~dir~~ to the 'reactos' directory that contains your sources. Set the output ~~dir~~ to the output-i386 directory you build into.	+	Now that you've got symbols, select your source directory and output directory in the 'Extras\|Settings...' menu of ReactOS Remote Debugger. Set the source directory to the 'reactos' directory that contains your sources. Set the output directory to the output-i386 directory you build into.

-	Make sure your freeldr.ini boots ~~reactos~~ like this:	+	Make sure your <tt>freeldr.ini</tt> boots ReactOS like this:

	Options=/DEBUG /DEBUGPORT=COM1 /KDSERIAL /BAUDRATE=115200		Options=/DEBUG /DEBUGPORT=COM1 /KDSERIAL /BAUDRATE=115200
Line 28:		Line 22:
	Actually, you can use any baud rate you want as long as your cabling allows a relatively low error rate. Optionally add /BREAK to break in early.		Actually, you can use any baud rate you want as long as your cabling allows a relatively low error rate. Optionally add /BREAK to break in early.

-	Newer builds of ReactOS already have a ReactOS (RosDbg) option in ~~freeldr~~ (/KDSERIAL only).	+	Newer builds of ReactOS already have a ReactOS (RosDbg) option in [[FreeLoader]] (/KDSERIAL only).
-		+
-	~~=== Using it ===~~	+
-		+
-	~~==== With Real Hardware ====~~	+

		+	== Using the debugger ==
		+	=== Real hardware ===
	Connect your null modem cable between com ports on your two computers and connect using the serial interface.		Connect your null modem cable between com ports on your two computers and connect using the serial interface.

-	===~~= With~~ Virtual ~~Machines~~ ====	+	=== Virtual machines ===
-		+	Virtual machine specific debugging details can be found on the VM pages:
-	Virtual ~~Machine~~ specific debugging details can be found on the VM pages:	+
	* [[QEMU]]		* [[QEMU]]
	* [[VirtualBox]]		* [[VirtualBox]]
	* [[VMware]]		* [[VMware]]

-	===== TCP/IP (QEMU only) =====	+	==== TCP/IP (QEMU only) ====
-		+
	Add		Add

Line 51:		Line 41:
	to your QEMU command line.		to your QEMU command line.

-	===== Serial ~~Connection~~ (QEMU, VMware, VirtualBox) =====	+	==== Serial connection (QEMU, VMware, VirtualBox) ====
-		+
	Use the serial port output together with the com0com driver (more [[Com0com\|here]]). The ReactOS Remote Debugger is your terminal application in this case.		Use the serial port output together with the com0com driver (more [[Com0com\|here]]). The ReactOS Remote Debugger is your terminal application in this case.

-	===== Named ~~Pipe~~ (QEMU, VMware, VirtualBox) =====	+	==== Named pipe (QEMU, VMware, VirtualBox) ====
-		+
	Serial port configuration in VMWARE:		Serial port configuration in VMWARE:

	[[Image:Vmware-pipe-cfg.png]]		[[Image:Vmware-pipe-cfg.png]]

-	=== Breaking in ===	+	== Breaking in ==
-		+	If all goes well, connect to a running ReactOS instance and crash it (or hit Tab+K) and you'll break in in the debugger. The ReactOS Remote Debugger will request a number of updates from KDBG to see where things are, examine the stack, etc. If you don't see this traffic, the most likely reason is that you've booted without /KDSERIAL, and KDBG input is coming from the keyboard. Boot ReactOS with the "ReactOS (RosDbg)" option in this case.
-	If all goes well, connect to a running ~~reactos~~ instance and crash it (or hit Tab+K) and you'll break in in the debugger. The ReactOS Remote Debugger will request a number of updates from KDBG to see where things are, examine the stack, etc. If you don't see this traffic, the most likely reason is that you've booted without /KDSERIAL, and KDBG input is coming from the keyboard. Boot ReactOS with the "ReactOS (RosDbg)" option in this case.	+

	If you see garbage and you're on a serial port, the most likely reason is that you've got ReactOS Remote Debugger and ReactOS set to different baud rates. We don't support auto baud setting yet, although somebody might be able to implement it fairly easily. It could also be dangerous at early /BREAK.		If you see garbage and you're on a serial port, the most likely reason is that you've got ReactOS Remote Debugger and ReactOS set to different baud rates. We don't support auto baud setting yet, although somebody might be able to implement it fairly easily. It could also be dangerous at early /BREAK.

-	If all goes well, ~~reactos~~ will break in, ReactOSDbg will poke around, and display a number of line in backtrace (addresses followed by source file and line number), and will populate the locals and threads+processes data grids.	+	If all goes well, ReactOS will break in, ReactOSDbg will poke around, and display a number of line in backtrace (addresses followed by source file and line number), and will populate the locals and threads+processes data grids.

	You can check that your locals appear by putting an __asm__("int3"); in your code. You should see all locally scoped variables and their values in the locals window when ReactOS breaks in.		You can check that your locals appear by putting an __asm__("int3"); in your code. You should see all locally scoped variables and their values in the locals window when ReactOS breaks in.
Line 73:		Line 60:
	Unlike KDBG, ReactOS Remote Debugger uses dbghelp.dll (the wine version, that reads stabs) to read the local copy of the .nostrip files that are the byproduct of the ROS_BUILDNOSTRIP=yes build. Unlike the abbreviated rossym sections in the canoncal binaries (suitable only for line number information), these contain all the information that's normally used by GDB to examine values in a running process. Since it doesn't rely on KDBG to lookup debug info, we could run a fully stripped build and still get debug info on the host (that is; debug a release build in a sensible way), and eventually, it'll be switched to kd protocol when ReactOS supports it. After that, it could be used to debug real windows, when given appropriate pdb files and the redistributable dbghelp.dll.		Unlike KDBG, ReactOS Remote Debugger uses dbghelp.dll (the wine version, that reads stabs) to read the local copy of the .nostrip files that are the byproduct of the ROS_BUILDNOSTRIP=yes build. Unlike the abbreviated rossym sections in the canoncal binaries (suitable only for line number information), these contain all the information that's normally used by GDB to examine values in a running process. Since it doesn't rely on KDBG to lookup debug info, we could run a fully stripped build and still get debug info on the host (that is; debug a release build in a sensible way), and eventually, it'll be switched to kd protocol when ReactOS supports it. After that, it could be used to debug real windows, when given appropriate pdb files and the redistributable dbghelp.dll.

-	=== Notes and troubles ===	+	== Notes and troubles ==
-		+	The most common complaint is that the channel back to ReactOS doesn't respond. You have to start ReactOS with the "ReactOS (RosDbg)" FreeLDR option. If there is no such option, you have to add /KDSERIAL to your freeldr.ini boot options manually.
-	The most common complaint is that the channel back to ReactOS doesn't respond. You have to start ReactOS with the "ReactOS (RosDbg)" ~~freeldr~~ option. If there is no such option, you have to add /KDSERIAL to your freeldr.ini boot options manually.	+

	KDBG, being a human interaction protocol, doesn't support retransmission. Luckily, ReactOSDbg is mostly stateless and responds to reports from KDBG as they become available. When in doubt, typing 'regs' and hitting return into the command prompt should get the essential updates flowing. It'll have a better automatic mechanism for that at some point in the future.		KDBG, being a human interaction protocol, doesn't support retransmission. Luckily, ReactOSDbg is mostly stateless and responds to reports from KDBG as they become available. When in doubt, typing 'regs' and hitting return into the command prompt should get the essential updates flowing. It'll have a better automatic mechanism for that at some point in the future.

Physical serial cable

CycleGeek — Sun, 05 Sep 2010 00:27:35 GMT

MFD: Should be merged into Debugging#Real computer: Physical serial cable

← Older revision		Revision as of 00:27, 5 September 2010
Line 1:		Line 1:
		+	{{del}}
		+
	If you have the equipment, this can be the easiest method to understand, and is the only method to use for real hardware.		If you have the equipment, this can be the easiest method to understand, and is the only method to use for real hardware.

Line 4:		Line 6:

	*Plan which connections are DTE and which DCE, and which gender each has. Know which serial port (1 or 2) you're connecting on each computer.		*Plan which connections are DTE and which DCE, and which gender each has. Know which serial port (1 or 2) you're connecting on each computer.
-
	*Get the right kind of null modem. There are a few ways to make them and not all are the same.		*Get the right kind of null modem. There are a few ways to make them and not all are the same.
-
	*Use shorter cables as much as possible.		*Use shorter cables as much as possible.
-		+	*Use a serial terminal program such as HyperTerminal or Minicom to observe the remote computer. If you don't see data you can recognize, then something is wrong.
-	*Use a serial terminal program such as ~~hyperterminal~~ or ~~minicom~~ to observe the remote computer. If you don't see data you can recognize, then something's wrong.	+
-		+
	*GDB remote commands start with $ and end with ;. You'll be able to recognize them that way.		*GDB remote commands start with $ and end with ;. You'll be able to recognize them that way.
-
	*Note: use these settings (In HyperTerminal)		*Note: use these settings (In HyperTerminal)
	Bits per second: 115200<br>		Bits per second: 115200<br>
Line 23:		Line 20:

	If you don't get one of those, you can get a small null modem and gender changer and use it to connect a normal serial cable between serial ports.		If you don't get one of those, you can get a small null modem and gender changer and use it to connect a normal serial cable between serial ports.
-

	[http://JesusnJim.com/electronics/reactos-debug-cable.html Resources to build ReactOS RJ45F-DB9F debug cable]		[http://JesusnJim.com/electronics/reactos-debug-cable.html Resources to build ReactOS RJ45F-DB9F debug cable]

DNS Workaround

CycleGeek — Sat, 04 Sep 2010 05:07:59 GMT

MFD: Site issues should be addressed in a more appropriate manner (e.g., news issue)

← Older revision		Revision as of 05:07, 4 September 2010
Line 1:		Line 1:
		+	{{del}}
		+
	Since there are a lot of problems recently with reactos.org DNS, you can use this workaround to still get your mails, look into the wiki or commit to svn:		Since there are a lot of problems recently with reactos.org DNS, you can use this workaround to still get your mails, look into the wiki or commit to svn:

Shutdown messages

CycleGeek — Sat, 04 Sep 2010 05:03:56 GMT

MFD: Removed in r45822 (superseded by current shutdown logo)

← Older revision		Revision as of 05:03, 4 September 2010
Line 1:		Line 1:
		+	{{del}}
		+
	When ReactOS has been shut down and the computer is ready to be powered off, the user is told that he can safely switch off his computer. It's fun to print an appropriate quote, next to the boring "OK, you can switch off now" message. However, if every time the same quote is printed, this becomes boring in itself. So, we need a lot of quotes, having to do with shutdown/death/rebirth. Look at the [[#Messages already used]] section to get yourself in the mood.		When ReactOS has been shut down and the computer is ready to be powered off, the user is told that he can safely switch off his computer. It's fun to print an appropriate quote, next to the boring "OK, you can switch off now" message. However, if every time the same quote is printed, this becomes boring in itself. So, we need a lot of quotes, having to do with shutdown/death/rebirth. Look at the [[#Messages already used]] section to get yourself in the mood.

Dialup

CycleGeek — Sat, 04 Sep 2010 04:41:27 GMT

MFD (Any of these links of use to aicom?)

← Older revision		Revision as of 04:41, 4 September 2010
Line 1:		Line 1:
-	~~'''Dial up'''~~	+	{{del}}

-	Dial up isn't a high priority for ~~reactos~~, as dial up is going away in the next 5 years or so with the advent of broadband and other meaning of networking but ~~pppoe~~ will of course still be around a while to come.	+	Dial up isn't a high priority for ReactOS, as dial up is going away in the next 5 years or so with the advent of broadband and other meaning of networking but PPPoE will of course still be around a while to come. Here is some research for anyone who is interested in taking it on.
-	Here is some research for anyone who is interested in taking it on.	+

-	On a basic level I believe (I could be wrong please edit out my mistakes) what you would need is a	+	On a basic level I believe (I could be wrong please edit out my mistakes) what you would need is:
		+	* WINSOCK (TCP/IP) - internet --> semi complete
		+	* PPP stack - conn. with ISP --> Exists but not configured for ROS
		+	* WAN (PPP/SLIP) Interface - NDIS miniport driver --> not started
		+	* TAPI - Telephone API --> API for dialup
		+	* kernel driver for serial port - COM1 --> semi complete
		+	* Reactos Kernel - Windows compatible OS --> semi complete

-	~~WINSOCK (TCP/IP) - internet --> semi complete~~	+	== Links ==
-		+	* Microsoft PPP info - http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcedial/html/cmconpppimplementationinwindowsce.asp
-	~~PPP stack - conn. with ISP --> Exists but not configured for ROS~~	+	* win32 PPP stack - http://groups-beta.google.com/group/fm.announce/msg/c0329386acd23d7b?q=slirp+cygwin
-		+	* PPP NDIS info - http://groups-beta.google.com/group/comp.protocols.ppp/msg/ae0164d3a41ec283
-	~~WAN (PPP/SLIP) Interface - NDIS miniport driver --> not started~~	+	* TAPI for NT 4.0 - http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dntapi/html/msdn_tapiwp.asp
-		+	* Freeware serial port driver - http://debian.lcs.mit.edu/pub/winsite/winnt/programr/Tinypo22.zip
-	~~TAPI - Telephone API --> API for dialup~~	+	* win32 i/o ports programming - http://www.lvr.com/parport.htm#Programming
-		+	* Free hyperterm - http://hp.vector.co.jp/authors/VA002416/teraterm.html
-	~~kernel driver for serial port - COM1 --> semi complete~~	+	* Testing modem connection - http://help.expedient.com/dialup/hyperterminal.shtml
-		+
-	~~Reactos Kernel - Windows compatible OS --> semi complete~~	+
-		+
-		+
-	~~'''~~Links~~'''~~	+
-		+
-	Microsoft PPP info - http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcedial/html/cmconpppimplementationinwindowsce.asp	+
-		+
-	win32 PPP stack - http://groups-beta.google.com/group/fm.announce/msg/c0329386acd23d7b?q=slirp+cygwin	+
-		+
-	PPP NDIS info - http://groups-beta.google.com/group/comp.protocols.ppp/msg/ae0164d3a41ec283	+
-		+
-	TAPI for NT 4.0 - http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dntapi/html/msdn_tapiwp.asp	+
-		+
-	Freeware serial port driver - http://debian.lcs.mit.edu/pub/winsite/winnt/programr/Tinypo22.zip	+
-		+
-	win32 i/o ports programming - http://www.lvr.com/parport.htm#Programming	+
-		+
-	Free hyperterm - http://hp.vector.co.jp/authors/VA002416/teraterm.html	+
-		+
-	Testing modem connection - http://help.expedient.com/dialup/hyperterminal.shtml	+

Wiki Maintenance

RideBMX — Sat, 04 Sep 2010 03:38:46 GMT

← Older revision		Revision as of 03:38, 4 September 2010
Line 1:		Line 1:
-	The purpose of this page is to direct users to articles that ~~needs~~ attention and improvement. ~~Those~~ articles may need more information, verification, or better organization. If you plan to create a new page, make sure it is relevant to the ReactOS project (pages dealing with testing, development, or documentation).	+	The purpose of this page is to direct users to articles that need attention and improvement. These articles may need more information, verification, or better organization. If you plan to create a new page, make sure it is relevant to the ReactOS project (pages dealing with testing, development, or documentation).

	== How to proceed ==		== How to proceed ==
-		+	There is currently a need for volunteers to edit the wiki. This is a position where anyone wanting to contribute to the ReactOS community is welcome to join. All it takes to edit the wiki is to [[Special:UserLogin\|create an account]]. After creating an account, take the time to learn [[Wikipedia:Wikipedia:How to edit a page\|how to edit a page]].
-	There is currently a need for volunteers to edit the wiki. This is a position where anyone wanting to contribute to the ReactOS community is welcome to join. All it takes to edit the wiki is to [[Special:UserLogin\|create an account]]. After creating an account, take the time to learn [[Wikipedia:Wikipedia:~~How_to_edit_a_page~~\|how to edit a page]].	+

	If you are not sure what to do, here are a few things to get you started:		If you are not sure what to do, here are a few things to get you started:
Line 12:		Line 11:

	== General cleanup ==		== General cleanup ==
-
	If you do not have the time to do the cleanup yourself, simply marking articles as needing cleanup using one of the [http://www.reactos.org/wiki/Special:AllPages&namespace=10 Templates] can be helpful.		If you do not have the time to do the cleanup yourself, simply marking articles as needing cleanup using one of the [http://www.reactos.org/wiki/Special:AllPages&namespace=10 Templates] can be helpful.

Line 23:		Line 21:
	== The Plan ==		== The Plan ==
	The plan is to make the wiki to a place where you can find information about ReactOS development.		The plan is to make the wiki to a place where you can find information about ReactOS development.
		+
	=== Phase 1 ===		=== Phase 1 ===
	* Mark all pages that don't belong to the wiki as <nowiki>{{del}}</nowiki>		* Mark all pages that don't belong to the wiki as <nowiki>{{del}}</nowiki>
-	* ~~merge~~ articles that cover the same area together	+	* Merge articles that cover the same area together
-	* ~~move~~ structures, APIs, stuff for clean room reverse engineering to [[Techwiki]]	+	* Move structures, APIs, stuff for clean room reverse engineering to [[Techwiki]]

	=== Phase 2 ===		=== Phase 2 ===
	* Review existing articles.		* Review existing articles.
	* Link existing articles in articles where is makes sense, to present a flow in information search.		* Link existing articles in articles where is makes sense, to present a flow in information search.
-	* ~~use~~ [[#List of articles sorted by relevance\|List of articles sorted by relevance]] to add notes about work that has to be done~~, you may also use the~~ discussion page~~, but it maybe takes some time until someone takes notice about it~~	+	* Use [[#List of articles sorted by relevance\|List of articles sorted by relevance]] to add notes about work that has to be done. The article's discussion page may also be used.

	=== Phase 3 ===		=== Phase 3 ===
-	* ~~finally get rid of~~ orphaned pages	+	* Remove orphaned pages
-	* ~~add~~ pages that ~~are~~ would ~~be nice to have for~~ a better understanding	+	* Add supplementary pages that would provide a better understanding

	== List of articles sorted by relevance ==		== List of articles sorted by relevance ==
Line 50:		Line 49:
	=== [[Version Status]] ===		=== [[Version Status]] ===
	could get a more uniform look --[[User:DangerGround\|DangerGround]] 09:17, 23 October 2008 (UTC)		could get a more uniform look --[[User:DangerGround\|DangerGround]] 09:17, 23 October 2008 (UTC)
-		+	:Needs review after new Version Status page implemented. --[[User:RideBMX\|RideBMX]] 23:44, 26 October 2009 (UTC)
-	Needs review after new Version Status page implemented. --[[User:RideBMX\|RideBMX]] 23:44, 26 October 2009 (UTC)	+

	=== [[Kernel]] ===		=== [[Kernel]] ===
	could be extended and merged to [[Techwiki]] --[[User:DangerGround\|DangerGround]] 09:17, 23 October 2008 (UTC)		could be extended and merged to [[Techwiki]] --[[User:DangerGround\|DangerGround]] 09:17, 23 October 2008 (UTC)
-		+	:Moved information from several other pages into Kernel. Still needed to be fixed up. --[[User:RideBMX\|RideBMX]] 23:44, 26 October 2009 (UTC)
-	Moved information from several other pages into Kernel. Still needed to be fixed up. --[[User:RideBMX\|RideBMX]] 23:44, 26 October 2009 (UTC)	+

	=== [[ReactOS subsystems]] ===		=== [[ReactOS subsystems]] ===