NikiWiki - User contributions [en]

SoC Ideas

2007-02-22T13:55:39Z

Doodle: Added ideas for Triton tasks

The main SoC page is here -> [[SoC]]

Please add your ideas to this list, keeping in mind that they should be doable in a 3-month time period. They might be complete implementations, or a needed module, or anything, really.

== Ideas for the Voyager Project ==

=== Triton specific tasks ===

* Create a *nix part of the Triton Porting Layer, so Triton will be compilable on *nix
* The current Triton code compiles with OpenWatcom. Make it so that it can be compiled with GCC.
* Create OGG Vorbis plugins (OGG demuxer, Vorbis decoder)
* Improve the AudioMixer to support reverse playback, to utilize MMX/SSE where possible and to remove its audio format restrictions.

Voyager Support

2007-01-23T15:05:09Z

Doodle: /* Triton */

[[Category:Voyager]]
Voyager is a very complex project and it can only be successful when everyone contributes as good as possible. To make it easier for you to join the project, we defined some jobs where you might be able to help.

==Documentation==
Good documentation is an important part of Voyager. For various reasons we decided to do the documentation in [http://www.docbook.org DocBook]. This is an XML based format used for many publications. O'reilly books are done with that too. Many other open source projects use this format as a base. It allows us to create any kind of output out of it, like HTML or PDF but also more in the future.

The drawback is that it takes some time to get into DocBook, in the beginning it is easier to use a WYSIWYG application like OpenOffice.org to create the document. Currently two Voyager developers write their documentation in OpenOffice.org.

So, one help would be to keep [http://voyager.netlabs.org/ The Design of Voyager] up to date with the OpenOffice.org documents of the two developers. Besides this, one might also work on an 'Easy way to use DocBook on eCS'.

===DocBook Editors===
At this time of writing, the following options are available to edit DocBook in an easier way:

* [http://www.eclipse.org Eclipse] with the [http://vex.sourceforge.net/ Vex] and [http://www.xmlbuddy.com/ XMLBuddy] plugin. Vex is open source and XMLBuddy is free in the entry version which is enough for our needs. Unfortunately we do not have an Eclipse port for eCS yet so this requires to work on one of the supported Eclipse platforms right now.
* [http://www.xmlmind.com/xmleditor/ XMLmind], a standalone Java based XML Editor which seems to support DocBook as well. According to the requirements this should work on eCS but we did not test that yet. It would be nice to set up a package that can be easily installed on eCS.

At Warpstock Europe 2005 there was also a [http://warpstock.net/WSE2005/Presentations/Presentations/#docbook presentation about DocBook] on eCS by Jarda Kačer and Jirka Kosek. It would be a good idea to work together with those guys to get that up and running on eCS as well.

===DocBook Syntax===
The best way to learn DocBook is to have a look at the [http://svn.netlabs.org/v_doc/browser/DOV current book], most of the needed tags are probably already used once. Besides this, one should have a look at [http://www.docbook.org/tdg/ DocBook: The Definitive Guide], which is available online or as HTML download.

Some remarks:
* Use [http://www.docbook.org/tdg/en/html/xref.html xref] whenever possible to create a reference to another part of the document. This makes reading the book much more interactive.
* For images one should use PNG versions for the web release and PDF for the PDF edition of the book. See the [http://FIXME mediaobject] example in [http://svn.netlabs.org/v_doc/browser/DOV/ch03.xml Chapter 3]. Please make sure that the PNG versions use a size that makes sense for web publishing. We did not do many tests on PDF yet. We have to see how this works regarding scaling.
* We use Subversion to keep a history of the document, this also means that the structure of the document should not change unless there is new content. Because of its XML nature, every editor will use its own indenting for the file. The only valid format to commit to Subversion is the indenting of Vex. So, in case your editor changes the layout, please make sure that Vex did format it before it gets committed, otherwise we get very big changesets!
* There is an additional <tt>DOCTYPE</tt> declaration in each chapter, the XSLT for transforming it does not like that because it is also defined in <tt>book.xml</tt>. To create the HTML and the PDF version of the book this line gets stripped out automatically by the build process before the document is transformed.
* Do not worry about the online versions, they are done by some scripts. Just make sure your own copy builds correctly in HTML before you commit it.
* Do not forget to commit images as well to the Subversion, in case you added some.

==ToDo==
This is a list of documents that need maintenance.

===The Design of Voyager===
====Netlabs Object Model====
* [ftp://ftp.netlabs.org/pub/misc/cinc/voyager/Object-design.pdf Object Design]
* Author: Chris Wohlgemuth, <tt>cinc-ml at netlabs.org</tt>, Cinc on irc://irc.netlabs.org/netlabs

====Desktop====
* [ftp://ftp.netlabs.org/pub/misc/cinc/voyager/Desktop-design.pdf Desktop Design]
* Author: Chris Wohlgemuth, <tt>cinc-ml at netlabs.org</tt>, Cinc on irc://irc.netlabs.org/netlabs

====Triton====
* [http://svn.netlabs.org/v_triton/browser/trunk/Docs/mmio-general.pdf MMIO General] - in PDF format
* [http://svn.netlabs.org/v_triton/browser/trunk/Docs/mmio-general.odt MMIO General] - in OpenOffice 2.0 format
* Author: Peter Kocsis, <tt>doodle at netlabs.org</tt>, Doodle on irc://irc.netlabs.org/netlabs

===Object-Oriented Interface Design (CUA)===
This is the book written by IBM back in the early nineties, the original title was
* Object-Oriented Interface Design - IBM Common User Access Guidelines ISBN 1-56529-170-0

We never found a PDF version of this book, just a very poor online HTML version. With the help of some scripts we assembled a standalone version of this book. Unfortunately the HTML syntax is very poor and the book lacks the images. Good for you because you can help us with that ;-)

* Get the [http://svn.netlabs.org/v_doc/browser/CUA recent version] of this book in our Subversion
* Install [http://weilbacher.org/Mozilla/builds.html NVU] and open the xhtml file.
* Start to clean it up. The syntax should look like in the beginning, very simple but clean XHTML code, as few <tt>br</tt> as possible, <tt>h1</tt>, <tt>h2</tt> for topic formating and <tt>p</tt> for paragraphs.
* Kill all table of contents and such things in the XHTML version. We will transform the XHTML to DocBook in a second step and DocBook will take care of that.
* And if you are brave enough to try to reproduce the images, at least those that make sense. This book is still available second hand, use that as a reference. It would greatly help us if someone finds a PDF version of the original document (in case that exists). It might get pretty tricky to reproduce some of the images because IBM created some sample applications for it, use what makes sense to you. For sure the images should be taken from a recent OS/2 or eCS system.

Voyager Support

2007-01-23T14:57:10Z

Doodle: Fixed email address of Doodle and fixed link to mmio-general doc.

[[Category:Voyager]]
Voyager is a very complex project and it can only be successful when everyone contributes as good as possible. To make it easier for you to join the project, we defined some jobs where you might be able to help.

==Documentation==
Good documentation is an important part of Voyager. For various reasons we decided to do the documentation in [http://www.docbook.org DocBook]. This is an XML based format used for many publications. O'reilly books are done with that too. Many other open source projects use this format as a base. It allows us to create any kind of output out of it, like HTML or PDF but also more in the future.

The drawback is that it takes some time to get into DocBook, in the beginning it is easier to use a WYSIWYG application like OpenOffice.org to create the document. Currently two Voyager developers write their documentation in OpenOffice.org.

So, one help would be to keep [http://voyager.netlabs.org/ The Design of Voyager] up to date with the OpenOffice.org documents of the two developers. Besides this, one might also work on an 'Easy way to use DocBook on eCS'.

===DocBook Editors===
At this time of writing, the following options are available to edit DocBook in an easier way:

* [http://www.eclipse.org Eclipse] with the [http://vex.sourceforge.net/ Vex] and [http://www.xmlbuddy.com/ XMLBuddy] plugin. Vex is open source and XMLBuddy is free in the entry version which is enough for our needs. Unfortunately we do not have an Eclipse port for eCS yet so this requires to work on one of the supported Eclipse platforms right now.
* [http://www.xmlmind.com/xmleditor/ XMLmind], a standalone Java based XML Editor which seems to support DocBook as well. According to the requirements this should work on eCS but we did not test that yet. It would be nice to set up a package that can be easily installed on eCS.

At Warpstock Europe 2005 there was also a [http://warpstock.net/WSE2005/Presentations/Presentations/#docbook presentation about DocBook] on eCS by Jarda Kačer and Jirka Kosek. It would be a good idea to work together with those guys to get that up and running on eCS as well.

===DocBook Syntax===
The best way to learn DocBook is to have a look at the [http://svn.netlabs.org/v_doc/browser/DOV current book], most of the needed tags are probably already used once. Besides this, one should have a look at [http://www.docbook.org/tdg/ DocBook: The Definitive Guide], which is available online or as HTML download.

Some remarks:
* Use [http://www.docbook.org/tdg/en/html/xref.html xref] whenever possible to create a reference to another part of the document. This makes reading the book much more interactive.
* For images one should use PNG versions for the web release and PDF for the PDF edition of the book. See the [http://FIXME mediaobject] example in [http://svn.netlabs.org/v_doc/browser/DOV/ch03.xml Chapter 3]. Please make sure that the PNG versions use a size that makes sense for web publishing. We did not do many tests on PDF yet. We have to see how this works regarding scaling.
* We use Subversion to keep a history of the document, this also means that the structure of the document should not change unless there is new content. Because of its XML nature, every editor will use its own indenting for the file. The only valid format to commit to Subversion is the indenting of Vex. So, in case your editor changes the layout, please make sure that Vex did format it before it gets committed, otherwise we get very big changesets!
* There is an additional <tt>DOCTYPE</tt> declaration in each chapter, the XSLT for transforming it does not like that because it is also defined in <tt>book.xml</tt>. To create the HTML and the PDF version of the book this line gets stripped out automatically by the build process before the document is transformed.
* Do not worry about the online versions, they are done by some scripts. Just make sure your own copy builds correctly in HTML before you commit it.
* Do not forget to commit images as well to the Subversion, in case you added some.

==ToDo==
This is a list of documents that need maintenance.

===The Design of Voyager===
====Netlabs Object Model====
* [ftp://ftp.netlabs.org/pub/misc/cinc/voyager/Object-design.pdf Object Design]
* Author: Chris Wohlgemuth, <tt>cinc-ml at netlabs.org</tt>, Cinc on irc://irc.netlabs.org/netlabs

====Desktop====
* [ftp://ftp.netlabs.org/pub/misc/cinc/voyager/Desktop-design.pdf Desktop Design]
* Author: Chris Wohlgemuth, <tt>cinc-ml at netlabs.org</tt>, Cinc on irc://irc.netlabs.org/netlabs

====Triton====
* [http://svn.netlabs.org/v_triton/browser/trunk/Docs/mmio-general.pdf MMIO General] - PDF
* Author: Peter Kocsis, <tt>doodle at netlabs.org</tt>, Doodle on irc://irc.netlabs.org/netlabs

===Object-Oriented Interface Design (CUA)===
This is the book written by IBM back in the early nineties, the original title was
* Object-Oriented Interface Design - IBM Common User Access Guidelines ISBN 1-56529-170-0

We never found a PDF version of this book, just a very poor online HTML version. With the help of some scripts we assembled a standalone version of this book. Unfortunately the HTML syntax is very poor and the book lacks the images. Good for you because you can help us with that ;-)

* Get the [http://svn.netlabs.org/v_doc/browser/CUA recent version] of this book in our Subversion
* Install [http://weilbacher.org/Mozilla/builds.html NVU] and open the xhtml file.
* Start to clean it up. The syntax should look like in the beginning, very simple but clean XHTML code, as few <tt>br</tt> as possible, <tt>h1</tt>, <tt>h2</tt> for topic formating and <tt>p</tt> for paragraphs.
* Kill all table of contents and such things in the XHTML version. We will transform the XHTML to DocBook in a second step and DocBook will take care of that.
* And if you are brave enough to try to reproduce the images, at least those that make sense. This book is still available second hand, use that as a reference. It would greatly help us if someone finds a PDF version of the original document (in case that exists). It might get pretty tricky to reproduce some of the images because IBM created some sample applications for it, use what makes sense to you. For sure the images should be taken from a recent OS/2 or eCS system.

Developers Workshop 2006

2006-02-27T09:29:15Z

Doodle: /* Schedule */

The OS/2 and eComStation Developers Workshop 2006 will take place the weekend of 8. and 9. April 2006 in Biel/Bienne, Switzerland.

===News Items===
23. February 2006    Added registration information & first overview of the topics 
21. January 2006    Added hotels and some information about Biel/Bienne. 
2. January 2006     Initial website online.

----

===Registration===
The registration is open at [http://www.mensys.net/DeveloperWorkshop2006/ Mensys] now, we provide the following tickets:

* netlabs.org Developers Workshop 2006, Saturday and Sunday: 45 Euro
* netlabs.org Developers Workshop 2006, one day: 25 Euro
* netlabs.org Developers Workshop 2006, students: Free

You can register at http://www.mensys.net/DeveloperWorkshop2006/
----

===Workshop Program===
There is no program yet but one of the main topics we will talk about is [[Voyager]], beside this we will for sure talk about current projects, like Genmac, ACPI, Everblue and so on. There will be quite some time for discussions, in a workshop form, also known as sitting around computers and hacking some code :)

We will provide enough space, wired or wireless network connection and a lot of bandwith.

====Schedule====

So far we plan to do the following presentations (details follow):

* Cairo
**General overview of Cairo, its structure and its API.
**Showing the Cairo API in live through a lot of examples.
* IOProc replacement
**Introduction to a new modular playback engine concept.
**Showing what's ready, what's to be done, what are the ideas.
**Discussing future possibilities (recording, transcoding...).
*The Voyager Object Model (was SOMH): The desktop will be built on an object model similar to SOM. The presentation details the reasons for an own object model and how it's implemented.
**Tour of the OS/2 desktop
**Why not using C++, Objective C, ...
**Implementation details
**Compatibility with SOM/DSOM
**Desktop development roadmap
**Using the object model for more
* Everblue
* Voyager - A coder overview about the project
** OpenGL as backend for Voyager - current options and problems
** Voyager components - where can you contribute
** OS/2 & PM compatibility - some crazy ideas worth discussing
* A WM based on Cairo
* Coding for WPS and Voyager
* netlabs.org Certificaton Program
* Translating Software

----

===Workshop Location===
Beside famous watch companies like Rolex, Omega and Swatch the city of Biel in Switzerland is the home of one more cool company: netlabs.org! This means that the Developers Workshop 2006 will take place in the city where netlabs.org was founded in 1997. I'm proud to do the hosting at the [http://www.hti.bfh.ch/ Berne University of Applied Sciences], the place where I did my studies and where I work now as a system administrator and teacher.

Biel is a small but cute city close to Bern, the capitol city. It's the boarder to the french speaking part of Switzerland so people in Biel speak german and french, at least most of them :-)
If you have some more spare time I recommend you to do a walk in the beautiful surroundings of Biel, for example the Jura mountains or around the lake. There is plenty to discover and with a bit of luck we will have a nice spring time in april.

Links:
* [http://www.drei-seen-land.ch Drei-Seen-Land] - a nice page with a lot of information about our region.
* [http://en.wikipedia.org/wiki/Biel/Bienne Biel/Bienne] at Wikipedia.org. Available in many languages.
* [http://ktk.netlabs.org/gallery/Altstadt-Biel-Bienne Old town of Biel] - some pics from the old town in my gallery

Hope to see you there!

Adrian Gschwend 
founder of netlabs.org
====Getting to Biel/Bienne====
Biel is the gate to the french speaking part of Switzerland, located in the western part of Switzerland. It is well connected to the railway system in Switzerland and easy to reach from about everywhere.

'''By train:''' 
There are night trains to Basel, called [http://www.citynightline.ch CityNightLine], this is mainly interesting if you want to get to Biel from Germany, Holland or Austria (it works from Denmark as well some days). You reach Biel within one hour from Basel by train.

For other train connections consult your local train office, if you have to travel to Biel from an airport check the homepage of [http://www.sbb.ch/ SBB], the railway company in Switzerland. For Geneva and Zurich you have to add ''Airport'' in the search field. For Basel and Bern Belp you need to take the local airport bus anyway.

'''By plane:''' 
There is no large airport close to Biel but in Switzerland almost everything is close anyway. So you can choose one of those airports if you want to get to Biel:

* Zurich (ZRH) - The biggest airport in Switzerland, quite good connections to Biel (every 30 minutes). Takes about 1.5 hours by train.
* Geneva (GVA) - good for Easyjet. There is just one train per hour to Biel, around 1.5 hours by train.
* Basel (BSL) - also good for Easyjet. There are bus connections to Basel and from there it's one hour by train.
* Berne Belp (BRN) - this is a small local airport, close to Bern but you still need to get to Biel and that's probably not much faster than Zurich because the Bus connections from this airport to Bern are not that great. From Bern it will take 30 minutes to Biel.

The local airline in Switzerland is [http://www.swiss.ch Swiss], which offers quite good trips from bigger cities.

----

====Accomodation====
There are several classes of hotels available in Biel:

* [http://www.lagolodge.ch/ Lago Lodge] - nice backpacker hostel directly at the lake of Biel. University is quite easy to reach by bus and the walk is not that far either.
* [http://www.continental-bienne.ch Hotel Continental] - 3-star hotel close to the lake as well. The road is quite busy so make sure you get a room towards the lake.
* [http://www.metropol-biel.ch Hotel Metropol] - 3-star hotel, 15-20 minutes walk to the University or bus.
* [http://www.lindenegg.ch/ Villa Lindenegg] - a very special and cute hotel in an old villa, 2 minutes away from the University, you can't get closer than that :)
* [http://www.accorhotels.com/accorhotels/fichehotel/gb/mer/6166/fiche_hotel.shtml Mercure Plaza] - 4-star hotel in the middle of the city
* [http://www.hotelelite.ch Hotel Elite] - 4-star hotel close to the railway station. Takes less than 10 minutes to the University.

If you can't afford a hotel we offer a room at the University where you can sleep with your sleeping bag and your mattress. The room is in the old manufacturing of Rolex and there are showers available too. It's probably not really comfortable but you don't have to pay anything for that :-) Please contact Adrian Gschwend if you want to do that, we have to know how many people do it like this. Email: ktk [at] netlabs.org
----

===Gallery===

===Contact===
If you have comments or want further information about the workshop, you can always reach us by sending an eMail to: 
DevelopersWorkshop [at] netlabs.org 
Adrian Gschwend is mainly responsible for organizing the workshop. 

----
===Announcement Mailing List===
The announcement mailing list is closed now.

GpiQueryYInversion()

2005-08-10T09:49:09Z

Doodle:

Definition:

LONG APIENTRY GpiQueryYInversion(HPS hps);

This function is exported by PMGPI.DLL as ordinal 726.
You can tell the linker to import it, by adding something like this to your *.def file:

IMPORTS
GpiQueryYInversion = PMGPI.726

Notes:

I think it was introduced with the Open32 API (previously called DAPIE or DAX). It's purpose is to ease the porting of Windows applications to OS/2.

This API will return the Y-Inversion value set for the HPS previously using the [[GpiEnableYInversion()]] API. Please check that for more details!

GpiEnableYInversion()

2005-08-10T09:46:29Z

Doodle:

Definition:

BOOL APIENTRY GpiEnableYInversion(HPS hps, LONG lHeight);

This function is exported by PMGPI.DLL as ordinal 723.
You can use this function by loading it dynamically when needed, for example by the following code. (The code assumes that the program uses other Gpi* functions so PMGPI.DLL is already attached to the process!)

static BOOL APIENTRY (*fnGpiEnableYInversion)(HPS hps, LONG lHeight) = NULL;

void GpiEnableYInversion(HPS hps, LONG lHeight)
{
HMODULE hmod;
int rc;

if (fnGpiEnableYInversion)
fnGpiEnableYInversion(hps, lHeight);
else
{
// Interesting, it doesn't work with DosQueryModuleHandle(), even
// though it returns the very same handle.
// [ rc = DosQueryModuleHandle("PMGPI", &hmod); ]

// I have to load and free the module instead...
rc = DosLoadModule(NULL, 0, "PMGPI", &hmod);
if (rc!=NO_ERROR)
return;
DosQueryProcAddr(hmod, 723, NULL, (PFN *)&fnGpiEnableYInversion);
DosFreeModule(hmod);
if (fnGpiEnableYInversion)
fnGpiEnableYInversion(hps, lHeight);
}
}

Or you can tell the linker to import it, by adding something like this to your *.def file:

IMPORTS
GpiEnableYInversion = PMGPI.723

Notes:

I think it was introduced with the Open32 API (previously called DAPIE or DAX). It's purpose is to ease the porting of Windows applications to OS/2. Using this API for a given Presentation Space handle (HPS), all the Gpi functions will be inverted using the given lHeight value.

Please note that not only the coordinates will be top-left based, but the blitting and handling of bitmaps will also be inverted. For example, using the GpiDrawBits() API expects a pointer to a pixel array, which is bottom-up by default. Once this call is used on the target Presentation Space, you'll have to have the pixels top-up way in your buffer if you want to have your image to be shown correctly.

The current setting of Y-Inversion can be queried with the [[GpiQueryYInversion()]] API.

Undocumented stuff

2005-08-10T09:27:23Z

Doodle: Added links to GpiEnableYInversion() and GpiQueryYInversion()

This section contains descriptions of undocumented stuff. Undocumented means there's no official documentation or the documentation (for example included on DevCon CDs) isn't available to the public anymore.

You are very welcome to add your own tips and tricks here!

* [[Window messages]]

* [[CallHook hook]]

* [[Query the DosError() state]] (using DosSysCtl())

* [[WinQueueFromID()]], get the HMQ from PID and TID

* [[WinQueryExtIdFocus]]

* [[WinQueryQueueInfo()]]

* [[GpiEnableYInversion()]] and [[GpiQueryYInversion()]]

DOSBox Port

2005-03-10T16:50:26Z

Doodle: /* Known Bugs */

This page will help to organize the port of DOSBox to OS/2. Initially, Martin Klingenfuss offered to pay the first person that ported DOSBox to OS/2 500 EUR. He also invited other people to join in and donate some money. To organize and coordinate all activities arround the port, this page was created.

Porting DOSBox to OS/2 is currently '''NOT a netlabs.org''' project! (no project homepage, no CVS,...) However, since netlabs.org offers this great WIKI, we decided to host the page here, so everybody can contribute to the content of the page easily.

This whole thing was started here (german!):
http://www.os2.de/forum/diskussion/index.php3?all=87595

==What is DOSBox?==
[http://dosbox.sourceforge.net Homepage] of DOSBox

==Why port DOSBox to OS/2, don't we have a Virtual DOS Machine?==

" DOSBox is a DOS-emulator that uses the SDL-library which makes DOSBox
very easy to port to different platforms. DOSBox has already been ported
to many different platforms, such as Windows, BeOS, Linux, MacOS X...

DOSBox also emulates CPU:286/386 realmode/protected mode, Directory
FileSystem/XMS/EMS, Tandy/Hercules/CGA/EGA/VGA/VESA graphics, a
SoundBlaster/Gravis Ultra Sound card for excellent sound compatibility
with older games...

You can "re-live" the good old days with the help of DOSBox, it can run
plenty of the old classics that don't run on your new computer!

DOSBox is totally free of charge and OpenSource."

Addon from Martin Klingenfuss:

As a DOS-games-player I think it would be great to have the virtualised DOS-box under OS/2 for usage of seamless SVGA-graphics under PM and sound via MMPM so modern PCI-audiocard will play DOS-games sounds.

Maybe it's necessary to work on the multimedia/graphic interfaces under OS/2 to make the DOS-Box run with same quality as under Win32. Because I am no programmer, I do not know what is exactly needed for this port.

Added By Peter (related to dosbox and surfing around the internet):

Dosbox is an emulator not a virtualised dos machine. (dosbox runs on non x86 targets as well!) It's basicly a 386 DX emulator with emulated bios/ emulated dos/emulated sound blaster 16 / emulated svga card. ) This is very usuable (actually porting shouldn't that hard) but it's not super fast.

Some windows specific behaviour that is missing in other ports:
* direct serial passthrough
* ddraw output support

Things dosbox requires optional from the host(os/2) (but all present in other ports):
* a port of SDL.
* possible some low-level cdrom interface.
* a mpu-401 interface (midi)
* a c++ compiler (gcc would be very helpful)
* ports of the following optional libraries(used in win32) zlib/libpng/sdl_net/lib-ogg/lib-vorbis/sdl-sound/
* If os/2 doesn't have function like readdir and opendir (libc function) then a specific drive interface must be written

==About the Money==
===What needs to be done to receive the money===
The money will be payed to the first person or group that successfully ports DOSBox to OS/2. A full OS/2 port has to satisfy the following requirements:
* Version 0.63 or above of DOSBox must be ported
* Exactly the same features as on Windows
* Quality of gameplay is exactly the same as on Windows, yes, you can port the bugs too! ;)
* ODIN must not be used
* Source code, compile requirements and compile instructions have to be available from a public place
* if changes to the DOSBox source are required, they must be documented

The money will be paid AFTER the port is done and tested by a few people.

===How much money will be paid===
Since the first large amount of money was donated in EUR, we use EUR as the currency here. If you need to convert your currency into EUR, you can use the [http://www.bloomberg.com/analysis/calculators/currency.html Bloomberg Currency Calculator].

500 EUR Martin Klingenfuss
20 EUR Robert Henschel; OS/2 User Group Dresden; Money will be transfered to Martin
50 EUR cytan299
30 EUR milesc
50 EUR Kris Steenhaut
50 EUR Gerrit Schoenmaker

Total amount: '''700 EUR'''

If you want to donate some money, please add yourself to the list above and contact Martin Klingenfuss (info AT expert-services DOT de)! Martin will tell you when and how to transfer the money. If you want to contribute anonymously, that can be arranged as well.

People who want to sponsor the project should donate at least EUR 20 to make it worthwhile. Martin guarantees a refund in case the project should fail.

==How you can help==
You can port DOSBox to OS/2!

You can donate some money.

==Progress==
* Jochen: I got DosBox compiled and linked. It starts running.
There are some problems with starting DosBox, which I'm now investigating.
* Robert: Great, let us know if you make more progress!<
* Jochen: I now have a DOS prompt, but there is still some glitches in the LIBC, I worked around for now.
* Robert: If you feel like you need help from the LIBC developer, you can join #netlabs on irc.netlabs.org and ask
* Jochen: I have succeeded in building a first version. [http://www.joschs-robotics.de/dosbox Download from here.] Please report bugs and suggestions in section Known Bugs or email me (josch@joschs-robotics.de).
* Jochen: Alpha3 runs with the most important features
* Jochen: Alpha5 nows has support for serial passthrough and cdrom ioctl.
* Jochen: Alpha6 nows fixes a bug with the copy command. It also gets built with optimization.

==To Do==
* Midi support has to be implemented correctly. Possibly with software MIDI.
* Autotools support.
* Build instructions.
* Audio Input for soundblaster emulation.

==Known Bugs==
* Playing SimCity 2000, in Windows the mouse is "locked" in the DosBox window until CTRL-ESC is pressed, in OS/2 the mouse can leave the DosBox window, and there is some strange positioning problem (reported by Robert)
** I do not know what causes this, but from time to time, the mouse can only be moved in parts of the DosBox window
This is a bug in SDL/2. It captures the mouse, but never re-centers it. (Doodle)

==Issues==
* Starting DOSBOX results in 100% CPU usage (playing SimCity 2000 is possible, but ''very'' slow) (reported by Robert)
** This can be reduced by pressing CTRL-F8 to increase the frame skip, but then, SimCity becomes jerky
** I have not yet compared that to the Windows version, maybe this is inherent to DOSBOX
It seems to be a problem with the way SDL/2 handle SDL_PollEvent, SDL_PeekEvent and related functions. There has to be some research on that. But it seems that we can't do much here. It's very much inherent to Simulators/Emulators.

* I did a few performance comparisons on the same hardware between OS/2 and Windows the results are:
** Windows is faster, but not very much
** the sound is "smoother" on Windows, there is a difference, not a large one however
** 1 GHz Pentium 3 is not enough for Commander Keen, not even on Windows (yes, I tried all the tricks from the FAQ) :-(
** I will stop to complain about speed/performance as it seems I do not have adequate hardware for testing ;-)

==Resolved Bugs==
* I have not been able to get sound to work (resolved since Alpha 3)
* Pressing Exit in the keymapper crashes DOSBOX (resolved since Alpha 4)
* Shift with many keys doesn't work (resolved since Alpha 4)
* If the CDROM is mounted as CDROM drive, there can be problem with changing the directory (resolved since Alpha 5).
* The command ''copy con test.bat'' crashes Dosbox. The Linux version claims that file doesn't exist (resolved since Alpha 6).
* Playing Commander Keen 4, one has to press the ALT key to get this "jump stick", however, this opens the system menu of the window (works in Windows) (will be resolved in Alpha 7) Jochen: It's not a bug, it's a feature. Doodle will remove the system menu from SDL windows.
* Screenshot crashes DOSBOX (resolved since Alpha 66).

==Your Questions go here!==
Q: Where do I get the latest version of SDL for OS/2? 
A: The package of SDL version 1.2.7 has been updated on December 22nd. http://sdl.netlabs.org/index.phtml
ftp://ftp.netlabs.org/pub/sdl/

Talk:Undocumented stuff

2005-01-11T10:07:56Z

Doodle:

I propose to move this section to [http://www.edm2.com/index.php/OS2_API]
- prokushev

I agree, but the undocumented stuffs should be marked, or at least there should be a page which collects the undocumented stuffs with links to them.

Doodle

WinQueryExtIdFocus

2005-01-06T15:06:55Z

Doodle: Added info about API ordinal

Definition for 16-bit programs:

USHORT EXPENTRY WinQueryExtIdFocus(PUSHORT pSessionId);

Definition for 32-bit programs:

USHORT APIENTRY16 WIN16QUERYEXTIDFOCUS(PUSHORT pSessionId);
#define WinQueryExtIdFocus WIN16QUERYEXTIDFOCUS

Add to your *.def file, if linker complains about missing WIN16QUERYEXTIDFOCUS:

IMPORTS
WIN16QUERYEXTIDFOCUS = PMSHAPI.86

Notes:

When the Session Manager switches to another session (because of a DosSMSwitch() call), it internally calls if PM is present WinSetExtIdFocus() to notify it about the session switch.
This API can be used to query the last session told to PM.

Tests show that this API can be used to see if PM is the current foreground full-screen session. The DosQuerySysState() API with the parameter QSV_FOREGROUND_FS_SESSION should return the session ID of the current foreground session, which for PM is always 1. Unfortunately, it returns some other session ID, as it changes when the user changes the focus between windowed VIO applications.

The WinQueryExtIdFocus() returns the same session ID that is returned by DosQuerySysState() when the PM is in foreground, but returns a different one, if PM is in the background.

WinQueryExtIdFocus

2005-01-06T12:07:35Z

Doodle:

Definition for 16-bit programs:

USHORT EXPENTRY WinQueryExtIdFocus(PUSHORT pSessionId);

Definition for 32-bit programs:

USHORT APIENTRY16 WIN16QUERYEXTIDFOCUS(PUSHORT pSessionId);
#define WinQueryExtIdFocus WIN16QUERYEXTIDFOCUS

Notes:

When the Session Manager switches to another session (because of a DosSMSwitch() call), it calls internally WinSetExtIdFocus() too, if PM is present, to notify it about session switching. This API can be used to query the last session told to PM.

Experiment shows that this API can be used to see if PM is the current foreground full-screen session, or not. The DosQuerySysState() API with the parameter QSV_FOREGROUND_FS_SESSION should return the session ID of the current foreground session, which is always 1 for PM. Unfortunately, it returns some other session ID, because it changes as the user changes focus between windowed VIO applications.

The WinQueryExtIdFocus() returns the same session ID that is returned by DosQuerySysState() when the PM is in foreground, but returns a different one, if PM is in the background.

Ideas

2004-12-28T15:06:48Z

Doodle: /* Added ideas about extending public PM controls */

Note: This page is extremely unorganized like most of my todo-lists I do at home. Feel free to add your ideas here. We hopefuly organize that a bit better one day...

* eComStation is very nice in my opinion (ktk speaking here :-) but updating it is still a major pain in the ass. We need a easy and stupid proof way updating it. And *please* in a non-GUI version too!

==UnixOS2==
There is a ports-like system for UnixOS2 in the works at the moment but I'm not really happy with that one and I doubt that we will be enough people for maintaining all that stuff ourself (dependencies and so on...).

When I use Linux I often work on Gentoo, which has really the best source-based ports system I've ever seen (and I know BSD too so it's not the only ports-system I know ;).

At the moment the ports system is quite Linux oriented but at the moment there is a complete rewrite of the portage-system in progress. They call it [http://www.gentoo.org/proj/en/portage/portage-ng/systemspec.xml portage-ng]. One of the targets is cross-platform support for stuff like BSD or MacOS so I really vote for OS/2 support as well :). It's too early at the moment to really have a look at it but we should definitely do that as soon as possible.

The discussion about portage-ng is [http://news.gmane.org/gmane.linux.gentoo.portage.devel here]

Update September 04: I talked to the guys who work on portage-ng. It looks like portage-ng is not really dead but at least progressing very slowly. Meanwhile, a group of MacOS X users created a [http://www.metadistribution.org/macos/ portage for MacOS X] so it looks like it does work on BSD-like systems too. So that changes the todo list a bit:

TODO:
* set up a basic package with latest GCC and Innotek LIBC. The basic package contains all tools and libraries needed to compile Python with Innotek LIBC.
* as soon as Python compiles we need to wrap together <tt>emerge</tt> on OS/2. This might get a bit tricky because it also heavily relies on shell scripts. So whatever shell we gonna use, it must be as close as possible to bash (if not bash anyway, it looks like the stuff is not that portable to other shells).
* once we get portage to work properly we need to create ebuilds for the basic libraries. At the first stage there is no rsync server needed to do this but it will definitely get handy sooner or later (shouldn't be a problem but needs to be set up).
* implement more and more ebuilds for all kind of packages
* and in a later stage create a bootstrap-package that also compiles GCC and all other tools (that won't be an easy task :)

==PM==
We need to port some toolkits or finish the current ports:
* qt - more soon, looks good
* GTK2: Samm proposed to work on it, will give an estimate of time soon
* wxWindows: Port quite up to date but the PM parts in it are definitely not yet done or very buggy -> fix (probably dmik)
* SWT: will be done when Eclipse is done -> dmik

Also, it would be nice to have updated public PM controls. This should be done with one DLL subclassing these public controls, and extending and/or fixing their behaviour. Things to fix/implement should be:
* Remove 64K limits in most of the controls (e.g. MLE)
* Create extended MLE control (understanding HTML tags maybe?)
* Automatically drop-down list of combobox, when clicked (like DragText does)

==WPS==
* replace background image dialog, it should be possible to point that to another directory than \os2\bitmap
* replace the file dialog, Gnome 2.6 does that '''very''' nicely (screenshot will follow).
Note: File dialog not WPS issue. But it can be implementer via WPS class. I consider it is good idea to move to object world. - prokushev.

==USB==

[[USB Todo's]]

==External list==
* [http://www.os2bbs.com/os2news/OS2Wishlist.html The Warp Wishlist] maintained by [[Kris Lake]].