- Ros-dev - ReactOS.org

Patch to bug #2517
by carlo.bramix 01 Aug '07

01 Aug '07

Hello. This bug contains an useful patch that removes a large amount of duplicated code from taskmgr. Sincerely, Carlo Bramini ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

card.dll images partly copied from windows
by Timo Kreuzer 01 Aug '07

01 Aug '07

There was a patch on bugzilla replacing some of the greyscale images from wine's card.dll with colored ones. http://www.reactos.org/bugzilla/show_bug.cgi?id=2476 Ged noticed that they looked exactly like windows images. The wine images seem to be windows images converted to greyscale. Maybe we should replace these images. I have found an opensource project with nice images: MacSolitaire http://sourceforge.net/projects/macsolitairex

2 1

??: Winetests
by Aleksey Bragin 01 Aug '07

01 Aug '07

Noone (with exception to a few reactos devs) really bothered to actually heavily use those tests to check the developed code for errors. If they were used from the beginning, there would be lots more supported apps by now. Speaking on topic, updating is important, but 2 years ago means that that test isn't really updated in wine. Wbr, Aleksey. -----???????? ?????????----- ??: "Daniel Reimer" <reimer.daniel(a)freenet.de> ????: "ReactOS Development List" <ros-dev(a)reactos.org> ??????????: 30.07.07 22:14 ????: [ros-dev] Winetests Hi, I dont talk very often here, but this is, in my eyes, quite urgent. Some days ago Magnus said he was able to fix some bugs thanks to the old winetests we have in SVN. When I looked at the tests I saw that some had their last update in r16000, TWO Years ago. I know its some work to port the tests, but dont you agree that newer tests could help to find even more bugs in ROS and that a update should be performed? If I could, I would do so, but I'm not skilled enough yet... Daniel "EmuandCo" Reimer _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

4 3

??: Re : ??: Re: ??: Re: Winetests
by Aleksey Bragin 31 Jul '07

31 Jul '07

While i'm away, it would be cool to listen to what other devs think about it. Like James, Thomas, etc. I don't have a pc here, but I feel cautious about any significant changes into .s generation. But, if it is possible to generate .s once, it would be good. Aleksey. -----???????? ?????????----- ??: "Sylvain Petreolle" <spetreolle(a)yahoo.fr> ????: "ReactOS Development List" <ros-dev(a)reactos.org> ??????????: 31.07.07 13:15 ????: [ros-dev] Re : ??: Re: ??: Re: Winetests Agreed, having it generated one time reduces wrong version and renders the whole process more reliable. ----- Message d'origine ---- De : Magnus Olsen <magnus(a)greatlord.com> À : ReactOS Development List <ros-dev(a)reactos.org> Envoyé le : Mardi, 31 Juillet 2007, 12h26mn 31s Objet : Re: [ros-dev] ??: Re: ??: Re: Winetests At moment we are genreate the win32k.S 2-3 times I do not whant it be genreate more that one time. that reason I whant a lib instead for allot genreated win32k.S, I will need a lib later for win32k testkit for dx. ----- Original Message ----- From: "Aleksey Bragin" <aleksey(a)reactos.org>

2 1

Re: [ros-dev] card.dll images partly copied from windows
by theUser BL 31 Jul '07

31 Jul '07

>Ged noticed that they looked exactly like windows images. The original grayscale comes from http://nifty.stanford.edu/2004/EstellCardGame/ if I remember right. Also used by projects like http://arainyday.se/projects/python/DeckOfCards/ >Maybe we should replace these images. I have found an opensource project >with nice images: MacSolitaire Nice idea. The cards there looks much better then the completly black and completely red cards. Greatings theuserbl _________________________________________________________________ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden!

1 0

Re : card.dll images partly copied from windows
by Sylvain Petreolle 31 Jul '07

31 Jul '07

this means we should delete its contents or make it unavailable, for legal/ip reasons. Kind regards, Sylvain Petreolle (aka Usurp) --- --- --- --- --- --- --- --- --- --- --- --- --- Run your favorite Windows apps with free ReactOS : http://www.reactos.org Listen to non-DRMised Music: http://www.jamendo.com ----- Message d'origine ---- De : Timo Kreuzer <timo.kreuzer(a)web.de> À : ReactOS Development List <ros-dev(a)reactos.org> Envoyé le : Mardi, 31 Juillet 2007, 16h17mn 44s Objet : [ros-dev] card.dll images partly copied from windows There was a patch on bugzilla replacing some of the greyscale images from wine's card.dll with colored ones. http://www.reactos.org/bugzilla/show_bug.cgi?id=2476 Ged noticed that they looked exactly like windows images. The wine images seem to be windows images converted to greyscale. Maybe we should replace these images. I have found an opensource project with nice images: MacSolitaire http://sourceforge.net/projects/macsolitairex _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

1 0

??: Re: Winetests
by Aleksey Bragin 31 Jul '07

31 Jul '07

Moving lists to appropriate places sounds good to me too. As for the lib, why would it be better than the current solution? -----???????? ?????????----- ??: "Timo Kreuzer" <timo.kreuzer(a)web.de> ????: "ReactOS Development List" <ros-dev(a)reactos.org> ??????????: 31.07.07 11:32 ????: Re: [ros-dev] Winetests The lib thing is exactly what I had in mind. I just also suggest moving the lists (win32ksvc.db and sysfuncs.lst) from the folder where the nci tool is to the folder where the function implementations are (win32k and ntoskrnl)

3 2

Re : ??: Re: ??: Re: Winetests
by Sylvain Petreolle 31 Jul '07

31 Jul '07

Agreed, having it generated one time reduces wrong version and renders the whole process more reliable. ----- Message d'origine ---- De : Magnus Olsen <magnus(a)greatlord.com> À : ReactOS Development List <ros-dev(a)reactos.org> Envoyé le : Mardi, 31 Juillet 2007, 12h26mn 31s Objet : Re: [ros-dev] ??: Re: ??: Re: Winetests At moment we are genreate the win32k.S 2-3 times I do not whant it be genreate more that one time. that reason I whant a lib instead for allot genreated win32k.S, I will need a lib later for win32k testkit for dx. ----- Original Message ----- From: "Aleksey Bragin" <aleksey(a)reactos.org> To: "ReactOS Development List" <ros-dev(a)reactos.org> Sent: Tuesday, July 31, 2007 12:23 PM Subject: [ros-dev] ??: Re: ??: Re: Winetests > I do not like the idea of fully switching to such a lib. > But for regression testing - let Timo do it then. > > Aleksey. > --- > > If some does not like the idea create a lib call > win32ksyscall.a let me hear it now, I will implement > it today night or tomoring other wise, it will be allot > easy for our testapps apps and gdi32/user32 using > a lib instead a genreated win32k.S for each apps. > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

1 0

??: Re: ??: Re: Winetests
by Aleksey Bragin 31 Jul '07

31 Jul '07

I do not like the idea of fully switching to such a lib. But for regression testing - let Timo do it then. Aleksey. --- If some does not like the idea create a lib call win32ksyscall.a let me hear it now, I will implement it today night or tomoring other wise, it will be allot easy for our testapps apps and gdi32/user32 using a lib instead a genreated win32k.S for each apps.

2 1

??: Re: suggestion: moving wine dlls
by Aleksey Bragin 31 Jul '07

31 Jul '07

I dislike the idea, I'll tell reasons when I'm back. -----???????? ?????????----- ??: "James Tabor" <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> ????: "ReactOS Development List" <ros-dev(a)reactos.org> ??????????: 30.07.07 08:58 ????: Re: [ros-dev] suggestion: moving wine dlls Timo Kreuzer wrote: > I have a suggestion: > Move all wine shared dlls to dll/wine or dll/3rdparty/wine, only kepping > our own dlls (gdi32, user32, kernel32, syssetup, newdev, console, hid, > mmdrv, ...) in dll/win32. > Reason is, we just lost a few earlier commited translation of wine dlls > with the latest winesyncs. > With this we would make sure everone would directly see that the > component is synched with wine and should not be touched. Another point > is that it's quite annoying to have >100 folders under the win32 folder > that expand in the file browser, when you browse to one of our dlls. > > Greetings, > Timo >

5 6

Re: [ros-dev] Bug #2494 fixed
by carlo.bramix 31 Jul '07

31 Jul '07

Hello, I posted a new patch for this bug, as requested into bugzilla. Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Mon, 30 Jul 2007 15:32:58 +0200 Subject : [ros-dev] Bug #2494 fixed > Hello, > the patch posted into this bug shoul fix the defect. > > Sincerely, > > Carlo Bramini > > > ------------------------------------------------------ > Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom > http://click.libero.it/infostrada > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

Win32/Gdi32 rewrite
by James Tabor 31 Jul '07

31 Jul '07

Hi all, I'm giving in to the idea of having two dc_attrs. From, Windows Graphics Programming Win32 GDI and DirectDraw -> 3.8 GDI KERNEL MODE DATA STRUCTURE -> Device Context in the GDI Engine, second to the last paragraph: Field pdcattr points to the DC_ATTR structure for that device context in user mode address space, which contains most device context settings. The DCOBJ structure has a duplication of it in its dcAttr field. It's possible the GDI designers want setting DC attributes to be efficient, with as little kernel mode code involvement as possible. This requires a DC_ATTR structure in user mode. But they also want to be able to access it easily in kernel mode, which requires a copy of DC_ATTR in kernel mode. Certain flags may be used to synchronize the two copies of DC_ATTR. typedef struct { // ......snip...... void * pdcattr; // point to user mode DCATTR DCLEVEL dcLevel; // 0x030 0x1B8(440) bytes DC_ATTR dcAttr; // 0x1C8(456) bytes // ......snip...... } DCOBJ; I did set up Ros DC structure to have the dc_attr pointer stored. I guess it's time to move the old WIN_DC_INFO stuff over to the new kernel mode dc_attr and use the dirty flags for synchronizing. This will fix my memory access problems too. I did an experiment to test the idea of just copy if it was dirty and all my problems went away. FYI, James

4 5

Bug #2494 fixed
by carlo.bramix 30 Jul '07

30 Jul '07

Hello, the patch posted into this bug shoul fix the defect. Sincerely, Carlo Bramini ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

Re : setup's fat32 format
by Sylvain Petreolle 30 Jul '07

30 Jul '07

Hi Tom, Your fat32format utility works beautifully here. One point must be approached : You released it under the GPL, but your zip files dont include the license text file. Please add it asap. Kind regards, Sylvain Petreolle (aka Usurp) --- --- --- --- --- --- --- --- --- --- --- --- --- Run your favorite Windows apps with free ReactOS : http://www.reactos.org Listen to non-DRMised Music: http://www.jamendo.com ----- Message d'origine ---- De : Gabriel ilardi <gabrielilardi(a)hotmail.it> À : ros-dev(a)reactos.org Envoyé le : Samedi, 28 Juillet 2007, 14h53mn 23s Objet : [ros-dev] setup's fat32 format Dear devs, There's a current limitation in xp, setup can format hds in fat32 at maximum 32gb, this is a setup format limitation, I've found an open source utilty to format fat32 with its native limitation (2tb). Hope it can be be of use to reactos. http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm WBR, Gabriel ilardi gabriel_it _________________________________________________________________ C'è una nuova amica su Messenger E' Doretta! http://www.doretta82.it/banner/index.html _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

1 0

suggestion: moving wine dlls
by Timo Kreuzer 30 Jul '07

30 Jul '07

I have a suggestion: Move all wine shared dlls to dll/wine or dll/3rdparty/wine, only kepping our own dlls (gdi32, user32, kernel32, syssetup, newdev, console, hid, mmdrv, ...) in dll/win32. Reason is, we just lost a few earlier commited translation of wine dlls with the latest winesyncs. With this we would make sure everone would directly see that the component is synched with wine and should not be touched. Another point is that it's quite annoying to have >100 folders under the win32 folder that expand in the file browser, when you browse to one of our dlls. Greetings, Timo

2 1

Re: [ros-dev] [ros-bugs] [Bug 2323] Display Version Number check box has no effect
by Magnus Olsen 29 Jul '07

29 Jul '07

it only should show after a reboot like windows does it. I have not tested this feature long time now, last time it did work like windows you need it a reboot. before this change taken effect. ----- Original Message ----- From: <ReactOS.Bugzilla(a)www.reactos.org> To: <ros-bugs(a)reactos.org> Sent: Sunday, July 29, 2007 9:46 PM Subject: [ros-bugs] [Bug 2323] Display Version Number check box has no effect > http://www.reactos.org/bugzilla/show_bug.cgi?id=2323 > > > > > > ------- Comment #3 from gabrielilardi(a)hotmail.it 2007-07-29 21:46 CET ------- > Probably this is the description (at least behaves as described): > Right click on the taskbar, settings, "display version number". > > > -- > Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are the QA contact for the bug, or are watching the QA contact. > You are the assignee for the bug, or are watching the assignee. > _______________________________________________ > Ros-bugs mailing list > Ros-bugs(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-bugs

1 0

Re: [ros-dev] [Bug 2501] Tuxpaint installer, windows class path issue ?
by Magnus Olsen 29 Jul '07

29 Jul '07

The werid thing it hang on this one for me. I do not getting any more msg that goes wrong, it seam the program freze whole reactos ----- Original Message ----- From: <ReactOS.Bugzilla(a)www.reactos.org> To: <greatlord(a)reactos.com> Sent: Sunday, July 29, 2007 7:36 PM Subject: [Bug 2501] Tuxpaint installer, windows class path issue ? > http://www.reactos.org/bugzilla/show_bug.cgi?id=2501 > > > w3seek(a)reactos.com changed: > > What |Removed |Added > -------------------------------------------------------------------------- -- > Status|NEW |RESOLVED > Resolution| |INVALID > > > > > ------- Comment #1 from w3seek(a)reactos.com 2007-07-29 19:36 CET ------- > This is not a bug. This is how the Delphi VCL is designed. Before it registers > window classes for VCL controls it does a call to GetClassInfoEx() to check if > the class exists. That's why you see the messages that a window class doesn't > exist. "It's not a bug, it's a feature!" > > > -- > Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter.

2 1

Re: [ros-dev] Bug Status
by Aleksey Bragin 27 Jul '07

27 Jul '07

Will you commit them maybe? (Let me know if you have no time, we should reassign this to some other developer then). WBR, Aleksey Bragin. On Jul 23, 2007, at 8:28 AM, James Tabor wrote: > Hi, > These patches look okay and all from Zavyalov Alexey (aka Generex) > reactos (AT) ilimschool.ru. > > http://www.reactos.org/bugzilla/show_bug.cgi?id=2368 > http://www.reactos.org/bugzilla/show_bug.cgi?id=2374 > http://www.reactos.org/bugzilla/show_bug.cgi?id=2382 > > Thanks, > James

2 1

"WINE_WARN" macro undeclared!!!
by carlo.bramix 26 Jul '07

26 Jul '07

ReactOS cannot be compiled! It returns the following error: [CC] base\applications\winhelp\hlpfile.c cc1.exe: warnings being treated as errors base\applications\winhelp\hlpfile.c: In function 'HLPFILE_DoReadHlpFile': base\applications\winhelp\hlpfile.c:346: warning: implicit declaration of function 'WINE_WARN' mingw32-make: *** [obj-i386\base\applications\winhelp\hlpfile.o] Error 1 Infact WINE_WARN macro is missing. It should be added somewhere for source compatibility. Sincerely, Carlo Bramini ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

Main.cpl cannot be compiled with VC
by carlo.bramix 26 Jul '07

26 Jul '07

Hello, bug #2479 describes a bug into ja-JP.rc and it includes a very simple correction. Sincerely, Carlo Bramini ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

Vacation
by Aleksey Bragin 26 Jul '07

26 Jul '07

Hello, I'll be on vacation, starting from tomorrow (25th of July) and lasting till 1st of August. Have fun with development while I'm away! WBR, Aleksey Bragin.

2 1

Remaining 0.3.3 logs
by Ged 25 Jul '07

25 Jul '07

There are still some developer changelogs missing from the wiki, so I've made files for each developer listing their changes. The devs in question are: Eric, Thomas, Hervé, Timo, hto, Sylvain and winesync(anyone want to volunteer for this?) The files can be found here : http://svn.reactos.org/temp/dev_logs/ If any dev doesn't have the time (or interest) to complete their own logs, can you state so in a reply to this mail and perhaps we can tender out your changes as a foreigner ;) Even if the individual devs don't care about taking credit for the work they've done, getting these changes in is quite important for ReactOS from a publicity aspect. Regards, Ged. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Amteus Secure Communications Ltd 57 Cardigan Lane, Leeds, LS4 2LE t: +44 (0) 870 8368770 f: +44 (0) 870 8368701 Registered in England No 4760795 http://www.amteus.com

2 1

Fixes to italian translation of powercfg applet
by carlo.bramix 24 Jul '07

24 Jul '07

Hello, bug #2467 has an attachment which fixes some translation errors missing translations unaligned or too small controls Sincerely, Carlo Bramini ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

Re: [ros-dev] ReactOS 0.3.3 RC1
by theUser BL 24 Jul '07

24 Jul '07

>we just released the first pre-release (RC1) of the upcoming 0.3.3. ... and it still have the Vista-notepad icon copyrighted by Microsoft. I already mentioned it http://www.reactos.org/archives/public/ros-dev/2007-May/009378.html and the answers where: http://www.reactos.org/archives/public/ros-dev/2007-May/009379.html http://www.reactos.org/archives/public/ros-dev/2007-May/009380.html http://www.reactos.org/archives/public/ros-dev/2007-May/009382.html If you have no Vista, you can google for "Vista icons" under "pictures" , then you find it. under http://www.istartedsomething.com/wp-content/uploads/2006/09/vista256.jpg the icon is in the middle of it the same in small size: http://www.istartedsomething.com/wp-content/uploads/2006/09/vista256_s.jpg http://www.vistaultimate.com/vista-5728-wallpapers-icons.htm An other side, which show the icons: http://www.crystalxp.net/news/img/18.jpg there the notepad icon is on the left side. and again: http://img519.imageshack.us/img519/6818/vistahighpx7rj.jpg It is ok,. if you use code and/or icons from other OpenSource-projects. But if you hear, that there is something not legal, then I think, you have to delete the illigal parts (code or icons) so fast as possible. But I believe, that there comes the time, where your audit http://www.reactos.org/wiki/index.php/Audit wil be ended and the Microsofts notepad icon is still part of ReactOS. Greatings theuserbl _________________________________________________________________ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden!

3 2

Ouch! another (small) bug into windres?
by carlo.bramix 23 Jul '07

23 Jul '07

Hello. Bug #2397 has been closed, but while the winemine icon bug has been fixed, it still persists into solitaire. If you launch solitaire into Windows or ReactOS, you will see that icon is wrong on the upper left corner of the title bar. I compiled solitaire with MSVC and the good icon is visible. I converted RES file into COFF format, I linked solitaire with RosBE and icon is ok too. I generated COFF file again with windres and again the icon is wrong. Suggestions? Sincerely, Carlo Bramini. ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

Bug Status
by James Tabor 23 Jul '07

23 Jul '07

Hi, These patches look okay and all from Zavyalov Alexey (aka Generex) reactos (AT) ilimschool.ru. http://www.reactos.org/bugzilla/show_bug.cgi?id=2368 http://www.reactos.org/bugzilla/show_bug.cgi?id=2374 http://www.reactos.org/bugzilla/show_bug.cgi?id=2382 Thanks, James

1 0

ReactOS 0.3.3 RC1
by Aleksey Bragin 22 Jul '07

22 Jul '07

Hello, we just released the first pre-release (RC1) of the upcoming 0.3.3. Certainly, it contains even more bugs than the alpha-quality software could contain, but we are still doing our best to reduce amount of certain glitches and misbehaviour. IMPORTANT: This releases is not intended for a press/media reviews, since it surely has more unwanted things that we want to have in a release. Anyway, the 0.3.3-series is now preferred over 0.3.1 for new people to try out. Don't forget to file bugs in our bugzilla (http:// www.reactos.org/bugzilla) it it's not already there. The prerelease is accessible from the sourceforge.net's download page as always (http://www.sourceforge.net/projects/reactos). I think mirrors didn't have time to cache the files yet, so be careful. You can find a link to the changelog at the download page too. Developers! Finally, those who still didn't bother to summarise your changes - please do! With the best regards, Aleksey Bragin.

4 3

[ros-diffs] [greatlrd] 27767: fixed so metafile works bit better,
by James Tabor 22 Jul '07

22 Jul '07

Hi! We need to re-think Metafile trash inside win32k! Hint: Win32k Gdi rewrite? If developers are going to help me do this, help me do it right! Remove metafile from win32k and implement it in gdi32 where it is done in real windows. I did place examples in the tree on how to do this. Poorly coded code built up upon poorly implement code equals more poorly implemented code on code, or just trash code! Thank you for your cooperation, James

2 2

Re: [ros-dev] ReactOS 0.3.3 RC1
by Aleksey Bragin 22 Jul '07

22 Jul '07

Dear Mr. Betov, Why don't you sign your messages with your real name? Betov is just a nickname. Are you hiding something? First of all, I'm not aware about ReactOS-fanatics terrorizing your wikipage. It was removed because you did not react to our requests about usage of a ReactOS trademark, and general strangeness of your project. It was said a number of times that ReactOS does not want to be in ANY relations with your project, because the only thing which RosAsm was doing for that amount of years is using ReactOS name to advertise, gain publicity and importance. ReactOS uses a lot of code from other projects, released by GPL- compatible licenses, knowledge gained from books, MSDN, DDK, websites, etc, etc, etc. We try to care about legality of information sources as much as we can. However, we usually don't thoroughly research which information sources did other projects use whose GPLed code we include in ReactOS (that would mean going into legal cleanness of Linux, Wine, and dozens of other projects - we don't neither have time or will to go into this). Secondly, we never hide and never intend to hide anything, so your highly arrogant ("I give you a week") is very stupid, I will never deal with you, that would mean a betrayal of all developers who work on ReactOS. It's very funny to read about some time estimates you're giving me (you must be really crazy to order me what to do and to give me time estimates). In legal terms it has a clear name: "blackmail", by using fabricated "proofs". Next you're going to tell you're banned from this list, etc, etc. Trust me, I heard about your behaviour, you're never targeting good goals, you only want to give something bad to people. Try to rethink your life goals. With the best regards, Aleksey Bragin. On Jul 22, 2007, at 11:13 AM, Betov wrote: -= skip =-

1 0

Re: [ros-dev] Strange code into ToUnicodeEx().
by carlo.bramix 22 Jul '07

22 Jul '07

I did a quick test: I bypassed that test and now, apparently, it finally works perfectly. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Sat, 21 Jul 2007 01:07:44 -0500 Subject : Re: [ros-dev] Strange code into ToUnicodeEx(). > carlo.bramix wrote: > > Hello, > > I debugged a bit on ReactOS because I wanted to understand why my (newer upcoming) version of ReactOS Calc doesn't work when you press some keys on the keyboard. > > The cause of the problem is this piece of code: > > > > int STDCALL ToUnicodeEx( UINT wVirtKey, > > UINT wScanCode, > > PBYTE lpKeyState, > > LPWSTR pwszBuff, > > int cchBuff, > > UINT wFlags, > > HKL dwhkl ) > > { > > int ToUnicodeResult = 0; > > > > if (0 == (lpKeyState[wVirtKey] & KS_DOWN_BIT)) > > { > > ToUnicodeResult = 0; > > } > > else > > { > > ...... > > > > In other words, a key can be translated only if it's pressed and not during the release stage. > > Is there a reason for this choice? > > > > Sincerely, > > > > Carlo Bramini > > > Oh!!!! Yuck! it's a wine thing'y! > > dlls/winex11.drv/keyboard.c:2365: * ToUnicodeEx (X11DRV.@) > dlls/winex11.drv/keyboard.c:2382:INT X11DRV_ToUnicodeEx(UINT virtKey, UINT scanCode, LPBYTE lpKeyState, > > dlls/user32/input.c:631:INT WINAPI ToUnicodeEx(UINT virtKey, UINT scanCode, LPBYTE lpKeyState > > > Maybe we need to update our code tree? > James > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

Montenegro
by Aleksey Bragin 21 Jul '07

21 Jul '07

Hello, I will be visiting Montenegro country (25th of July, for a week, Tivat, Budva, surroundings), and I will have some free time there. So if someone has a will to meet regarding ReactOS - feel free to drop me an email. WBR, Aleksey Bragin.

1 0

Strange code into ToUnicodeEx().
by carlo.bramix 21 Jul '07

21 Jul '07

Hello, I debugged a bit on ReactOS because I wanted to understand why my (newer upcoming) version of ReactOS Calc doesn't work when you press some keys on the keyboard. The cause of the problem is this piece of code: int STDCALL ToUnicodeEx( UINT wVirtKey, UINT wScanCode, PBYTE lpKeyState, LPWSTR pwszBuff, int cchBuff, UINT wFlags, HKL dwhkl ) { int ToUnicodeResult = 0; if (0 == (lpKeyState[wVirtKey] & KS_DOWN_BIT)) { ToUnicodeResult = 0; } else { ...... In other words, a key can be translated only if it's pressed and not during the release stage. Is there a reason for this choice? Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Wed, 18 Jul 2007 11:14:45 +0000 (GMT) Subject : [ros-dev] Re : r27709 breaks first stage setup > this part of hivesys change is wrong : (duplicate key) > > +HKLM,"SYSTEM\CurrentControlSet\Control\NLS\Language","0414",0x00000000,"l_intl.nls" > HKLM,"SYSTEM\CurrentControlSet\Control\NLS\Language","0813",0x00000000,"l_intl.nls" > HKLM,"SYSTEM\CurrentControlSet\Control\NLS\Language","0414",0x00000000,"l_intl.nls" > > > Kind regards, > Sylvain Petreolle (aka Usurp) > --- --- --- --- --- --- --- --- --- --- --- --- --- > Run your favorite Windows apps with free ReactOS : http://www.reactos.org > Listen to non-DRMised Music: http://www.jamendo.com > > > > > ----- Message d'origine ---- > De : Timo Kreuzer <timo.kreuzer(a)web.de> > À : ReactOS Development List <ros-dev(a)reactos.org> > Envoyé le : Mercredi, 18 Juillet 2007, 0h33mn 13s > Objet : [ros-dev] r27709 breaks first stage setup > > > the change in hivesys.inf makes ros freeze when trying to import hivesys.inf > bug 2414 > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

2 1

Re : r27709 breaks first stage setup
by Sylvain Petreolle 18 Jul '07

18 Jul '07

this part of hivesys change is wrong : (duplicate key) +HKLM,"SYSTEM\CurrentControlSet\Control\NLS\Language","0414",0x00000000,"l_intl.nls" HKLM,"SYSTEM\CurrentControlSet\Control\NLS\Language","0813",0x00000000,"l_intl.nls" HKLM,"SYSTEM\CurrentControlSet\Control\NLS\Language","0414",0x00000000,"l_intl.nls" Kind regards, Sylvain Petreolle (aka Usurp) --- --- --- --- --- --- --- --- --- --- --- --- --- Run your favorite Windows apps with free ReactOS : http://www.reactos.org Listen to non-DRMised Music: http://www.jamendo.com ----- Message d'origine ---- De : Timo Kreuzer <timo.kreuzer(a)web.de> À : ReactOS Development List <ros-dev(a)reactos.org> Envoyé le : Mercredi, 18 Juillet 2007, 0h33mn 13s Objet : [ros-dev] r27709 breaks first stage setup the change in hivesys.inf makes ros freeze when trying to import hivesys.inf bug 2414 _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

1 0

r27709 breaks first stage setup
by Timo Kreuzer 17 Jul '07

17 Jul '07

the change in hivesys.inf makes ros freeze when trying to import hivesys.inf bug 2414

1 0

Another question about patches
by carlo.bramix 17 Jul '07

17 Jul '07

Hello, After r27704 the resource files of winemine changed, so I'm wondering if I should re-do the patches posted for bug #2397. There were also some fixes for italian translation. In my opinion it was wrong: in the game you must search mines and not flowers. Instead, the translation into the WINE CVS seems correct. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Fri, 13 Jul 2007 15:03:10 +0200 Subject : [ros-dev] Bug #2397 (partially) fixed. > The patch sent to Bugzilla fixes the signaled bugs. > The missing WineMine icon into the aboutbox has been fixed only into english and italian versions, so the fix should be applied to all other languages as I described into bugzilla. > > Sincerely, > > Carlo Bramini > > ---------- Initial Header ----------- > > >From : ros-dev-bounces(a)reactos.org > To : "ros-dev" ros-dev(a)reactos.org > Cc : > Date : Thu, 12 Jul 2007 13:45:22 +0200 > Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > > > Hello, > > your windres works well too. > > Finally, I can see the light at the end of the tunnel. > > BTW, do you have this warning too? > > > > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > > windres: warning: 5: "CHOOSE_FONT": 1026: duplicate value > > windres: warning: 5: "CHOOSE_COLOR?n": 1026: duplicate value > > > > It seems it happens into cdlg_Bg.rc > > > > Sincerely, > > > > Carlo Bramini > > > > ---------- Initial Header ----------- > > > > >From : ros-dev-bounces(a)reactos.org > > To : "ReactOS Development List" ros-dev(a)reactos.org > > Cc : > > Date : Thu, 12 Jul 2007 13:11:44 +0200 > > Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > > > > > Hi, > > > > > > Yesterday in the #reactos IRC channel, some other users had the same > > > problem. > > > At the end, we also identified "windres" as the problem. > > > > > > Probably, we all do not use the same version of RosBE. EmuandCo published > > > around 4 RosBE versions, which all got the version number 0.3.6. Some of > > > them use different "windres" versions. > > > Hopefully, RosBE 0.3.7 will solve this mess. > > > > > > I currently uploaded the "windres" version I use to > > > http://reactos.colinfinck.de. This is the version that works for me. > > > For all Unix/Linux users: The "windres" version bundled with my RosBE-Unix > > > 0.3.6 also works for me, so the resources should be compiled correctly here. > > > > > > The regedit problem you had was caused by saving some resource files as > > > UTF-8 instead of ANSI. > > > But this problem should be fixed in current trunk. > > > > > > Best regards, > > > > > > Colin > > > > > > > > > > -----Original Message----- > > > > From: ros-dev-bounces(a)reactos.org > > > > [mailto:ros-dev-bounces@reactos.org] On Behalf Of carlo.bramix > > > > Sent: Thursday, July 12, 2007 10:18 AM > > > > To: ros-dev > > > > Subject: Re: [ros-dev] Re : ReactOS doesn't compile well > > > > > > > > After reading these messages I believe I didn't explain my > > > > problems very well... > > > > So I try to correct what I said... > > > > Switching to older (the 2006 one) windres really *solved* all > > > > these problems: > > > > > > > > [WRC] obj-i386\base\shell\cmd\cmd.coff > > > > [WRC] obj-i386\base\system\expand\expand.coff > > > > [WRC] obj-i386\dll\cpl\intl\intl.coff > > > > [WRC] obj-i386\dll\cpl\intl_new\intl.coff > > > > [WRC] obj-i386\dll\cpl\sysdm\sysdm.coff > > > > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > > > > [WRC] obj-i386\dll\win32\hhctrl.ocx\hhctrl.coff > > > > [WRC] obj-i386\dll\win32\shdocvw\shdocvw.coff > > > > > > > > The problem not solved was another one, when the > > > > listview/treeview controls into regedit sometimes disappear > > > > (but into current revision, it's ok too). > > > > > > > > Sincerely, > > > > > > > > Carlo Bramini. > > > > > > _______________________________________________ > > > Ros-dev mailing list > > > Ros-dev(a)reactos.org > > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > > > > > ------------------------------------------------------ > > Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom > > http://click.libero.it/infostrada > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > ------------------------------------------------------ > Leggi GRATIS le tue mail con il telefonino i-mode di Wind > http://i-mode.wind.it/ > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

More resource problems
by Timo Kreuzer 17 Jul '07

17 Jul '07

There seem to be some more problems with resources intl.cpl: errors while compiling, it only shows the first language (cz) and control panel shows nothing. If you remove all other languages than one or comment out the stringtable in all resources, then it compiles without errors and the control panel works again. intl still doesn't start on XP (some other cpl also don't work on xp) sysdm.cpl: shows text in different languages in ros (German text although selected language is English)

3 3

web page for WINE tests results
by Paul Dufresne 16 Jul '07

16 Jul '07

I forgot to give the link for the tests results. Here it is: http://www.reactos.org/wiki/index.php/Wine_Test_Results -- http://www.fastmail.fm - Email service worth paying for. Try it for free

1 0

New WINE test results for r27665
by Paul Dufresne 16 Jul '07

16 Jul '07

First, I'd like to thanks EmuandCo for the work he did on that wiki page. Now that I have passed through all the tests for version 27665, I do realize how time consuming it can be. I have rewrite in a wiki table the work EmuandCo had done, in the hope that it will be easier to add simply a new column for tests on a new version. I have made progress in green, semi-problematic one in yellow, and clear regressions in red. I intend in the future, to retake only on kernel32 and user32 tests, and other tests that were in regression, rather than all tests, except maybe once by month or about. I intend to isolate tests causing HANG or ERROR, and make sure they are listed in bugzilla. I hope you will use these tests to figure out the sooner possible what is the causes of regressions, and eliminate them. -- http://www.fastmail.fm - Same, same, but different

1 0

Re: [ros-dev] More resource problems
by Aleksey Bragin 16 Jul '07

16 Jul '07

Hi, try to remove usewrc="false" in those rbuild files. Dmitry Chapyshev reported that it fixes this problem, however I didn't investigate this myself (what's the problem with using WRC or not, I only checked that intl.cpl's resource files are of the correct syntax, which is confirmed by opening resources in MSVC 2005 SP1). WBR, Aleksey Bragin. On Jul 16, 2007, at 1:57 AM, Timo Kreuzer wrote: > There seem to be some more problems with resources > > intl.cpl: errors while compiling, it only shows the first language > (cz) > and control panel shows nothing. If you remove all other languages > than > one or comment out the stringtable in all resources, then it compiles > without errors and the control panel works again. intl still doesn't > start on XP (some other cpl also don't work on xp) > > sysdm.cpl: shows text in different languages in ros (German text > although selected language is English) > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev

1 0

Re: [ros-dev] More resource problems
by Aleksey Bragin 16 Jul '07

16 Jul '07

I just opened intl.cpl in MSVC 2005 SP1 - no problem, I can edit resources, no error messages. WBR, Aleksey Bragin. On Jul 16, 2007, at 2:34 AM, Magnus Olsen wrote: > The rc syntax in intl.cpl are wrong, > only way to fix that problem is make that apps complie with vc > when I open it with vc it compain wrong rc syntax > > > ----- Original Message ----- > From: "Timo Kreuzer" <timo.kreuzer(a)web.de> > To: "ReactOS Development List" <ros-dev(a)reactos.org> > Sent: Sunday, July 15, 2007 11:57 PM > Subject: [ros-dev] More resource problems > > >> There seem to be some more problems with resources >> >> intl.cpl: errors while compiling, it only shows the first language >> (cz) >> and control panel shows nothing. If you remove all other languages >> than >> one or comment out the stringtable in all resources, then it compiles >> without errors and the control panel works again. intl still doesn't >> start on XP (some other cpl also don't work on xp) >> >> sysdm.cpl: shows text in different languages in ros (German text >> although selected language is English) >> >> >> _______________________________________________ >> Ros-dev mailing list >> Ros-dev(a)reactos.org >> http://www.reactos.org/mailman/listinfo/ros-dev > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev

1 0

Bug #2397 (partially) fixed.
by carlo.bramix 13 Jul '07

13 Jul '07

The patch sent to Bugzilla fixes the signaled bugs. The missing WineMine icon into the aboutbox has been fixed only into english and italian versions, so the fix should be applied to all other languages as I described into bugzilla. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Thu, 12 Jul 2007 13:45:22 +0200 Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > Hello, > your windres works well too. > Finally, I can see the light at the end of the tunnel. > BTW, do you have this warning too? > > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > windres: warning: 5: "CHOOSE_FONT": 1026: duplicate value > windres: warning: 5: "CHOOSE_COLOR?n": 1026: duplicate value > > It seems it happens into cdlg_Bg.rc > > Sincerely, > > Carlo Bramini > > ---------- Initial Header ----------- > > >From : ros-dev-bounces(a)reactos.org > To : "ReactOS Development List" ros-dev(a)reactos.org > Cc : > Date : Thu, 12 Jul 2007 13:11:44 +0200 > Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > > > Hi, > > > > Yesterday in the #reactos IRC channel, some other users had the same > > problem. > > At the end, we also identified "windres" as the problem. > > > > Probably, we all do not use the same version of RosBE. EmuandCo published > > around 4 RosBE versions, which all got the version number 0.3.6. Some of > > them use different "windres" versions. > > Hopefully, RosBE 0.3.7 will solve this mess. > > > > I currently uploaded the "windres" version I use to > > http://reactos.colinfinck.de. This is the version that works for me. > > For all Unix/Linux users: The "windres" version bundled with my RosBE-Unix > > 0.3.6 also works for me, so the resources should be compiled correctly here. > > > > The regedit problem you had was caused by saving some resource files as > > UTF-8 instead of ANSI. > > But this problem should be fixed in current trunk. > > > > Best regards, > > > > Colin > > > > > > > -----Original Message----- > > > From: ros-dev-bounces(a)reactos.org > > > [mailto:ros-dev-bounces@reactos.org] On Behalf Of carlo.bramix > > > Sent: Thursday, July 12, 2007 10:18 AM > > > To: ros-dev > > > Subject: Re: [ros-dev] Re : ReactOS doesn't compile well > > > > > > After reading these messages I believe I didn't explain my > > > problems very well... > > > So I try to correct what I said... > > > Switching to older (the 2006 one) windres really *solved* all > > > these problems: > > > > > > [WRC] obj-i386\base\shell\cmd\cmd.coff > > > [WRC] obj-i386\base\system\expand\expand.coff > > > [WRC] obj-i386\dll\cpl\intl\intl.coff > > > [WRC] obj-i386\dll\cpl\intl_new\intl.coff > > > [WRC] obj-i386\dll\cpl\sysdm\sysdm.coff > > > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > > > [WRC] obj-i386\dll\win32\hhctrl.ocx\hhctrl.coff > > > [WRC] obj-i386\dll\win32\shdocvw\shdocvw.coff > > > > > > The problem not solved was another one, when the > > > listview/treeview controls into regedit sometimes disappear > > > (but into current revision, it's ok too). > > > > > > Sincerely, > > > > > > Carlo Bramini. > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > ------------------------------------------------------ > Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom > http://click.libero.it/infostrada > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

ReactOS 0.3.3 Changelog
by Aleksey Bragin 12 Jul '07

12 Jul '07

Dear developers, it's time to put all your great achievements into the 0.3.3 changelog. For your convinience, Colin Finck made the SVN logs (0.3.1 -> 0.3.3) available on his site: http://reactos.colinfinck.de . Changelog itself is located here: http://www.reactos.org/wiki/ index.php/ChangeLog-0.3.3 I'd appreciate it a lot if you fill your changes as soon as possible, since we're branching this week for a release. Thanks, Aleksey Bragin.

4 4

Re: [ros-dev] Re : ReactOS doesn't compile well
by carlo.bramix 12 Jul '07

12 Jul '07

After reading these messages I believe I didn't explain my problems very well... So I try to correct what I said... Switching to older (the 2006 one) windres really *solved* all these problems: [WRC] obj-i386\base\shell\cmd\cmd.coff [WRC] obj-i386\base\system\expand\expand.coff [WRC] obj-i386\dll\cpl\intl\intl.coff [WRC] obj-i386\dll\cpl\intl_new\intl.coff [WRC] obj-i386\dll\cpl\sysdm\sysdm.coff [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff [WRC] obj-i386\dll\win32\hhctrl.ocx\hhctrl.coff [WRC] obj-i386\dll\win32\shdocvw\shdocvw.coff The problem not solved was another one, when the listview/treeview controls into regedit sometimes disappear (but into current revision, it's ok too). Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Thu, 12 Jul 2007 09:49:23 +0200 Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > SVN bootcd ISO seems to work. > I still don't understand why it doesn't compile well on my PC. > I will try to understand more althought I'm a bit out of idea at the moment. > > Sincerely, > > Carlo Bramini > > > ---------- Initial Header ----------- > > >From : ros-dev-bounces(a)reactos.org > To : "ReactOS Development List" ros-dev(a)reactos.org > Cc : > Date : Wed, 11 Jul 2007 20:55:52 +0200 > Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > > > > BTW, when I tested that link I got an "error 404". > > > > Ah sorry, the link contained a typo. > > This link should work: http://reactos.colinfinck.de/getbuilds/ > > > > Of course, you can still also download the ISOs directly from our server at > > http://svn.reactos.org/iso, but the Web interface is nicer :-) > > > > Best regards, > > > > Colin > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > ------------------------------------------------------ > Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom > http://click.libero.it/infostrada > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

3 2

Re: [ros-dev] Re : ReactOS doesn't compile well
by carlo.bramix 12 Jul '07

12 Jul '07

Hello, your windres works well too. Finally, I can see the light at the end of the tunnel. BTW, do you have this warning too? [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff windres: warning: 5: "CHOOSE_FONT": 1026: duplicate value windres: warning: 5: "CHOOSE_COLOR?n": 1026: duplicate value It seems it happens into cdlg_Bg.rc Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Thu, 12 Jul 2007 13:11:44 +0200 Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > Hi, > > Yesterday in the #reactos IRC channel, some other users had the same > problem. > At the end, we also identified "windres" as the problem. > > Probably, we all do not use the same version of RosBE. EmuandCo published > around 4 RosBE versions, which all got the version number 0.3.6. Some of > them use different "windres" versions. > Hopefully, RosBE 0.3.7 will solve this mess. > > I currently uploaded the "windres" version I use to > http://reactos.colinfinck.de. This is the version that works for me. > For all Unix/Linux users: The "windres" version bundled with my RosBE-Unix > 0.3.6 also works for me, so the resources should be compiled correctly here. > > The regedit problem you had was caused by saving some resource files as > UTF-8 instead of ANSI. > But this problem should be fixed in current trunk. > > Best regards, > > Colin > > > > -----Original Message----- > > From: ros-dev-bounces(a)reactos.org > > [mailto:ros-dev-bounces@reactos.org] On Behalf Of carlo.bramix > > Sent: Thursday, July 12, 2007 10:18 AM > > To: ros-dev > > Subject: Re: [ros-dev] Re : ReactOS doesn't compile well > > > > After reading these messages I believe I didn't explain my > > problems very well... > > So I try to correct what I said... > > Switching to older (the 2006 one) windres really *solved* all > > these problems: > > > > [WRC] obj-i386\base\shell\cmd\cmd.coff > > [WRC] obj-i386\base\system\expand\expand.coff > > [WRC] obj-i386\dll\cpl\intl\intl.coff > > [WRC] obj-i386\dll\cpl\intl_new\intl.coff > > [WRC] obj-i386\dll\cpl\sysdm\sysdm.coff > > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > > [WRC] obj-i386\dll\win32\hhctrl.ocx\hhctrl.coff > > [WRC] obj-i386\dll\win32\shdocvw\shdocvw.coff > > > > The problem not solved was another one, when the > > listview/treeview controls into regedit sometimes disappear > > (but into current revision, it's ok too). > > > > Sincerely, > > > > Carlo Bramini. > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

2 1

Re: [ros-dev] Re : ReactOS doesn't compile well
by carlo.bramix 12 Jul '07

12 Jul '07

SVN bootcd ISO seems to work. I still don't understand why it doesn't compile well on my PC. I will try to understand more althought I'm a bit out of idea at the moment. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Wed, 11 Jul 2007 20:55:52 +0200 Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > > BTW, when I tested that link I got an "error 404". > > Ah sorry, the link contained a typo. > This link should work: http://reactos.colinfinck.de/getbuilds/ > > Of course, you can still also download the ISOs directly from our server at > http://svn.reactos.org/iso, but the Web interface is nicer :-) > > Best regards, > > Colin > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

Unable to get up to the Desktop with SVN build images of this week even on QEMU
by Paul Dufresne 12 Jul '07

12 Jul '07

Hi! I am new to ReactOS. I'd like to understand the current state of the SVN images. Is it normal that I get stop by bug #2290, making me unable to use Live-CD images. Do everyone have it, or are we just a few to be hit by that? Also, when I use install CD, on QEMU (I am very afraid to use it on real hardware, last time I tried, it installed over my Linux partition -was seeing my 10G drive as 4Gb-, and after that, it made me unable to go to my BIOS, or boot, even if I had reset my RTC on the mobo, reflash the BIOS -that was still available on Asus-; I finally discovered that disconnecting the HD allowed my to get to the BIOS, there deactivate the HD, and then boot Linux CD and access the HD even if it was deactivated in the BIOS), when I reboot after installation, I go only to the first wizard, but no mouse cursor, or pressing Alt-N to do next does nothing. So, I feel a bit frustrated to see that SVN build seems useless. Others don't seems to have the same problems. Do you? -- http://www.fastmail.fm - The professional email service

1 0

Compile error when linking syssetup...
by João Jerónimo 12 Jul '07

12 Jul '07

There is a syntax error in the file dll/win32/syssetup/lang/de-DE.rc that causes WCR to display a bunch of error messages like this: syssetup.syssetup.rci.tmp:2566:1: Warning: Newline in string constant encounterd (started line 2565) The error is in the 14th line counting from the end. Basically, the following German sentence has no opening quote: "Setup kann erst fortgesetzt werden kann, wenn ein Computername eingegeben wurde." Thanks, JJ __________________________________________________ Fa�a liga��es para outros computadores com o novo Yahoo! Messenger http://br.beta.messenger.yahoo.com/

1 0

Re: [ros-dev] Re : ReactOS doesn't compile well
by carlo.bramix 11 Jul '07

11 Jul '07

Hello, yes, I did a clean, I verified that it was really clean and then I launched "make". The problem still persists. I will try to download an SVN ISO and I will test what happens. BTW, when I tested that link I got an "error 404". Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Wed, 11 Jul 2007 16:08:16 +0200 Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > > About COMDLG32, the problem is locking all functionalities > > for open/close file dialogs. > > If I launch, for example, notepad and I select File->Open, > > nothing happens. > > I have no such problem. > > Just tested latest trunk (compiled myself and compiled by our BuildBot) and > both builds do not show this problem. > You can try it for yourself by downloading an ISO from > http://reactos.colinfinck.de/gebuilds > > Did you try a clean build after updating to latest trunk? > > Best regards, > > Colin > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

2 1

Re: [ros-dev] Re : ReactOS doesn't compile well
by carlo.bramix 11 Jul '07

11 Jul '07

About COMDLG32, the problem is locking all functionalities for open/close file dialogs. If I launch, for example, notepad and I select File->Open, nothing happens. Perhaps, a quick, temporary solution could be making a script file or a small executable called windres which executes MS RC from Visual Studio Express and then it executes the true windres for converting the RES into COFF format. I'm just guessing... Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Wed, 11 Jul 2007 12:37:20 +0200 Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > > That's not reasonable, you would loose all Unicode characters except > > Latin 1 ones. So please don't save as Latin 1 (aka ISO-8859-1) except > > for special cases (languages like EN, DE, and other european > > lnaguages). > > We would first have to check if our resource compiler supports Unicode. > > Also just take a look at the RC files in reactos/dll/win32/comdlg32. They > are all saved with Latin 1 encoding, even the ones in eastern languages such > as russian and chinese. > We imported them from Wine and it looks like there are no problems using > them. > I assume, this is done by using code pages. > > I agree, that UTF-16 is probably the best solution for these problems, but > as long as there might be problems with the resource compiler, we shouldn't > change everything to UTF-16 now. > > Best regards, > > Colin > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

2 1

Re: [ros-dev] Re : ReactOS doesn't compile well
by carlo.bramix 11 Jul '07

11 Jul '07

Hello, unfortunately, the problem really exists, since it seems that at least someone else saw the error when compiling. Hopefully, I discovered a solution. I changed windres.exe with another one. The one into RosBE 0.3.6 says: GNU windres (GNU Binutils) 2.17.50.20070608 Copyright 2007 Free Software Foundation, Inc. The one into my MSYS installation says: GNU windres 2.17.50 20060824 Copyright 2005 Free Software Foundation, Inc. I renamed windres.exe into c:\RosBE\4.1.3\bin and I copied the old one. And surprise, now it all works. Don't ask me why... at the moment I don't know the reason but this trick made it working. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Tue, 10 Jul 2007 19:01:28 +0200 Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > Hi, > > I just tested building latest trunk under Windows and 32-bit Linux (both > with RosBE 0.3.6) and both builds resulted in correct ISOs. > Our BuildBot also has no such problems. > > I tested your examples "intl.cpl" and "sysdm.cpl" and both are shown in > english for me. > When I switch the locale to any german locale, I get german versions of > these apps, meaning that the whole localization thing works for me. > > Maybe you have to do a clean build. > > Best regards, > > Colin > > > > -----Original Message----- > > From: ros-dev-bounces(a)reactos.org > > [mailto:ros-dev-bounces@reactos.org] On Behalf Of carlo.bramix > > Sent: Tuesday, July 10, 2007 5:25 PM > > To: ros-dev > > Subject: Re: [ros-dev] Re : ReactOS doesn't compile well > > > > Hello, > > yep, the errors don't interrupt the compilation of ReactOS. > > But the resources into those coffs seem corrupted to me. > > For example, if I open the control panel I will see inl.cpl > > in german language(!) while all others are in english or if I > > open the system applet I can see some text without sense. > > > > Sincerely, > > > > Carlo Bramini > > > > ---------- Initial Header ----------- > > > > >From : ros-dev-bounces(a)reactos.org > > To : "ReactOS Development List" ros-dev(a)reactos.org > > Cc : > > Date : Tue, 10 Jul 2007 15:07:58 +0000 (GMT) > > Subject : [ros-dev] Re : ReactOS doesn't compile well > > > > > hi, > > > I got some of them but it didnt bother the build. > > > > > > Kind regards, > > > Sylvain Petreolle (aka Usurp) > > > --- --- --- --- --- --- --- --- --- --- --- --- --- > > > Run your favorite Windows apps with free ReactOS : > > http://www.reactos.org > > > Listen to non-DRMised Music: http://www.jamendo.com > > > > > > > > > > > > > > > ----- Message d'origine ---- > > > De : carlo.bramix <carlo.bramix(a)libero.it> > > > À : ros-dev <ros-dev(a)reactos.org> > > > Envoyé le : Mardi, 10 Juillet 2007, 16h52mn 51s > > > Objet : Re: [ros-dev] ReactOS doesn't compile well > > > > > > > > > Hello, > > > while regedit compilation was done successfully, some files > > aren't still generated correctly: > > > > > > [WRC] obj-i386\base\shell\cmd\cmd.coff > > > [WRC] obj-i386\base\system\expand\expand.coff > > > [WRC] obj-i386\dll\cpl\intl\intl.coff > > > [WRC] obj-i386\dll\cpl\intl_new\intl.coff > > > [WRC] obj-i386\dll\cpl\sysdm\sysdm.coff > > > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > > > [WRC] obj-i386\dll\win32\hhctrl.ocx\hhctrl.coff > > > [WRC] obj-i386\dll\win32\shdocvw\shdocvw.coff > > > > > > <built-in>:0: fatal error: when writing output to : Invalid argument > > > compilation terminated. > > > > > > I hope it could be fixed. > > > > > > Sincerely, > > > > > > Carlo Bramini > > > > > > ---------- Initial Header ----------- > > > > > > >From : ros-dev-bounces(a)reactos.org > > > To : "ros-dev" ros-dev(a)reactos.org > > > Cc : > > > Date : Mon, 9 Jul 2007 18:34:34 +0200 > > > Subject : Re: [ros-dev] ReactOS doesn't compile well > > > > > > > Hello, > > > > problem with compilation of regedit seems to be gone with > > revision 27541. > > > > > > > > Sincerely, > > > > > > > > Carlo Bramini > > > > > > > > ---------- Initial Header ----------- > > > > > > > > >From : ros-dev-bounces(a)reactos.org > > > > To : "ros-dev" ros-dev(a)reactos.org > > > > Cc : > > > > Date : Mon, 9 Jul 2007 11:24:29 +0200 > > > > Subject : [ros-dev] ReactOS doesn't compile well > > > > > > > > > Hello, > > > > > it looks like something wrong happens when I compile ReactOS. > > > > > I also did a complete clean and a make for a total > > rebuild, but I'm still having problems. > > > > > > > > > > I saw the first problem when I tried to test Regedit > > after committed changes. > > > > > The tree window and the listview window aren't visible > > (or they aren't created successfully, I didn't check this yet). > > > > > I tested that executable into WinXP and those child > > windows aren't visible too. > > > > > So I did these steps: > > > > > 1) I compiled Regedit with Visual C and I verified that > > it worked fine. > > > > > 2) I grabbed regedit.res and I manually generated > > regedit.coff with "windres -i regedit.res -o regedit.coff". > > > > > 3) I launched "make" again and it regenerated regedit.exe. > > > > > This last regedit.exe works fine and it has all child > > window controls visible. It's really a problem when > > generating te coff file from resources. > > > > > > > > > > I also saw a possible second problem when compiling. > > > > > Some compilation of '.coff' files failed. > > > > > On the console I read some messages like this one: > > > > > > > > > > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > > > > > <built-in>:0: fatal error: when writing output to : > > Invalid argument > > > > > compilation terminated. > > > > > > > > > > Actually I'm using RosBE 0.3.6 but I never got such > > problems with previouses svn versions of the sources. > > > > > > > > > > Sincerely, > > > > > > > > > > Carlo Bramini > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------ > > > > > Leggi GRATIS le tue mail con il telefonino i-modeTM di Wind > > > > > http://i-mode.wind.it/ > > > > > > > > > > > > > > > _______________________________________________ > > > > > Ros-dev mailing list > > > > > Ros-dev(a)reactos.org > > > > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > > > > > > > > > > > > > ------------------------------------------------------ > > > > Leggi GRATIS le tue mail con il telefonino i-modeTM di Wind > > > > http://i-mode.wind.it/ > > > > > > > > > > > > _______________________________________________ > > > > Ros-dev mailing list > > > > Ros-dev(a)reactos.org > > > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > > > > > > > > > ------------------------------------------------------ > > > Scegli infostrada: ADSL gratis per tutta l´estate e > > telefoni senza canone Telecom > > > http://click.libero.it/infostrada > > > > > > > > > _______________________________________________ > > > Ros-dev mailing list > > > Ros-dev(a)reactos.org > > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > > _______________________________________________ > > > Ros-dev mailing list > > > Ros-dev(a)reactos.org > > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > > > > > ------------------------------------------------------ > > Scegli infostrada: ADSL gratis per tutta lestate e telefoni > > senza canone Telecom > > http://click.libero.it/infostrada > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

6 8

Re: [ros-dev] Re : ReactOS doesn't compile well
by carlo.bramix 11 Jul '07

11 Jul '07

Hello, unfortunately, you are right... Sigh! The old windres doesn't print errors, but the results into the executables are the same. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Tue, 10 Jul 2007 20:39:27 +0200 Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > MinGW GNU windres 2.17.50 20060824 also doesn't work for me, so maybe it's a MinGW problem rather than a version problem > > > carlo.bramix schrieb: > > Hello, > > unfortunately, the problem really exists, since it seems that at least someone else saw the error when compiling. > > Hopefully, I discovered a solution. > > I changed windres.exe with another one. > > The one into RosBE 0.3.6 says: > > > > GNU windres (GNU Binutils) 2.17.50.20070608 > > Copyright 2007 Free Software Foundation, Inc. > > > > The one into my MSYS installation says: > > > > GNU windres 2.17.50 20060824 > > Copyright 2005 Free Software Foundation, Inc. > > > > I renamed windres.exe into c:\RosBE\4.1.3\bin and I copied the old one. And surprise, now it all works. > > Don't ask me why... at the moment I don't know the reason but this trick made it working. > > > > Sincerely, > > > > Carlo Bramini > > > > ---------- Initial Header ----------- > > > > >From : ros-dev-bounces(a)reactos.org > > To : "ReactOS Development List" ros-dev(a)reactos.org > > Cc : > > Date : Tue, 10 Jul 2007 19:01:28 +0200 > > Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > > > > > >> Hi, > >> > >> I just tested building latest trunk under Windows and 32-bit Linux (both > >> with RosBE 0.3.6) and both builds resulted in correct ISOs. > >> Our BuildBot also has no such problems. > >> > >> I tested your examples "intl.cpl" and "sysdm.cpl" and both are shown in > >> english for me. > >> When I switch the locale to any german locale, I get german versions of > >> these apps, meaning that the whole localization thing works for me. > >> > >> Maybe you have to do a clean build. > >> > >> Best regards, > >> > >> Colin > >> > >> > >> > >>> -----Original Message----- > >>> From: ros-dev-bounces(a)reactos.org > >>> [mailto:ros-dev-bounces@reactos.org] On Behalf Of carlo.bramix > >>> Sent: Tuesday, July 10, 2007 5:25 PM > >>> To: ros-dev > >>> Subject: Re: [ros-dev] Re : ReactOS doesn't compile well > >>> > >>> Hello, > >>> yep, the errors don't interrupt the compilation of ReactOS. > >>> But the resources into those coffs seem corrupted to me. > >>> For example, if I open the control panel I will see inl.cpl > >>> in german language(!) while all others are in english or if I > >>> open the system applet I can see some text without sense. > >>> > >>> Sincerely, > >>> > >>> Carlo Bramini > >>> > >>> ---------- Initial Header ----------- > >>> > >>> >From : ros-dev-bounces(a)reactos.org > >>> To : "ReactOS Development List" ros-dev(a)reactos.org > >>> Cc : > >>> Date : Tue, 10 Jul 2007 15:07:58 +0000 (GMT) > >>> Subject : [ros-dev] Re : ReactOS doesn't compile well > >>> > >>> > >>>> hi, > >>>> I got some of them but it didnt bother the build. > >>>> > >>>> Kind regards, > >>>> Sylvain Petreolle (aka Usurp) > >>>> --- --- --- --- --- --- --- --- --- --- --- --- --- > >>>> Run your favorite Windows apps with free ReactOS : > >>>> > >>> http://www.reactos.org > >>> > >>>> Listen to non-DRMised Music: http://www.jamendo.com > >>>> > >>>> > >>>> > >>>> > >>>> ----- Message d'origine ---- > >>>> De : carlo.bramix <carlo.bramix(a)libero.it> > >>>> ´R : ros-dev <ros-dev(a)reactos.org> > >>>> Envoyé le : Mardi, 10 Juillet 2007, 16h52mn 51s > >>>> Objet : Re: [ros-dev] ReactOS doesn't compile well > >>>> > >>>> > >>>> Hello, > >>>> while regedit compilation was done successfully, some files > >>>> > >>> aren't still generated correctly: > >>> > >>>> [WRC] obj-i386\base\shell\cmd\cmd.coff > >>>> [WRC] obj-i386\base\system\expand\expand.coff > >>>> [WRC] obj-i386\dll\cpl\intl\intl.coff > >>>> [WRC] obj-i386\dll\cpl\intl_new\intl.coff > >>>> [WRC] obj-i386\dll\cpl\sysdm\sysdm.coff > >>>> [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > >>>> [WRC] obj-i386\dll\win32\hhctrl.ocx\hhctrl.coff > >>>> [WRC] obj-i386\dll\win32\shdocvw\shdocvw.coff > >>>> > >>>> <built-in>:0: fatal error: when writing output to : Invalid argument > >>>> compilation terminated. > >>>> > >>>> I hope it could be fixed. > >>>> > >>>> Sincerely, > >>>> > >>>> Carlo Bramini > >>>> > >>>> ---------- Initial Header ----------- > >>>> > >>>> >From : ros-dev-bounces(a)reactos.org > >>>> To : "ros-dev" ros-dev(a)reactos.org > >>>> Cc : > >>>> Date : Mon, 9 Jul 2007 18:34:34 +0200 > >>>> Subject : Re: [ros-dev] ReactOS doesn't compile well > >>>> > >>>> > >>>>> Hello, > >>>>> problem with compilation of regedit seems to be gone with > >>>>> > >>> revision 27541. > >>> > >>>>> Sincerely, > >>>>> > >>>>> Carlo Bramini > >>>>> > >>>>> ---------- Initial Header ----------- > >>>>> > >>>>> >From : ros-dev-bounces(a)reactos.org > >>>>> To : "ros-dev" ros-dev(a)reactos.org > >>>>> Cc : > >>>>> Date : Mon, 9 Jul 2007 11:24:29 +0200 > >>>>> Subject : [ros-dev] ReactOS doesn't compile well > >>>>> > >>>>> > >>>>>> Hello, > >>>>>> it looks like something wrong happens when I compile ReactOS. > >>>>>> I also did a complete clean and a make for a total > >>>>>> > >>> rebuild, but I'm still having problems. > >>> > >>>>>> I saw the first problem when I tried to test Regedit > >>>>>> > >>> after committed changes. > >>> > >>>>>> The tree window and the listview window aren't visible > >>>>>> > >>> (or they aren't created successfully, I didn't check this yet). > >>> > >>>>>> I tested that executable into WinXP and those child > >>>>>> > >>> windows aren't visible too. > >>> > >>>>>> So I did these steps: > >>>>>> 1) I compiled Regedit with Visual C and I verified that > >>>>>> > >>> it worked fine. > >>> > >>>>>> 2) I grabbed regedit.res and I manually generated > >>>>>> > >>> regedit.coff with "windres -i regedit.res -o regedit.coff". > >>> > >>>>>> 3) I launched "make" again and it regenerated regedit.exe. > >>>>>> This last regedit.exe works fine and it has all child > >>>>>> > >>> window controls visible. It's really a problem when > >>> generating te coff file from resources. > >>> > >>>>>> I also saw a possible second problem when compiling. > >>>>>> Some compilation of '.coff' files failed. > >>>>>> On the console I read some messages like this one: > >>>>>> > >>>>>> [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > >>>>>> <built-in>:0: fatal error: when writing output to : > >>>>>> > >>> Invalid argument > >>> > >>>>>> compilation terminated. > >>>>>> > >>>>>> Actually I'm using RosBE 0.3.6 but I never got such > >>>>>> > >>> problems with previouses svn versions of the sources. > >>> > >>>>>> Sincerely, > >>>>>> > >>>>>> Carlo Bramini > >>>>>> > >>>>>> > >>>>>> > >>>>>> ------------------------------------------------------ > >>>>>> Leggi GRATIS le tue mail con il telefonino i-modeTM di Wind > >>>>>> http://i-mode.wind.it/ > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Ros-dev mailing list > >>>>>> Ros-dev(a)reactos.org > >>>>>> http://www.reactos.org/mailman/listinfo/ros-dev > >>>>>> > >>>>>> > >>>>> ------------------------------------------------------ > >>>>> Leggi GRATIS le tue mail con il telefonino i-modeTM di Wind > >>>>> http://i-mode.wind.it/ > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Ros-dev mailing list > >>>>> Ros-dev(a)reactos.org > >>>>> http://www.reactos.org/mailman/listinfo/ros-dev > >>>>> > >>>>> > >>>> ------------------------------------------------------ > >>>> Scegli infostrada: ADSL gratis per tutta l´estate e > >>>> > >>> telefoni senza canone Telecom > >>> > >>>> http://click.libero.it/infostrada > >>>> > >>>> > >>>> _______________________________________________ > >>>> Ros-dev mailing list > >>>> Ros-dev(a)reactos.org > >>>> http://www.reactos.org/mailman/listinfo/ros-dev > >>>> > >>>> _______________________________________________ > >>>> Ros-dev mailing list > >>>> Ros-dev(a)reactos.org > >>>> http://www.reactos.org/mailman/listinfo/ros-dev > >>>> > >>>> > >>> ------------------------------------------------------ > >>> Scegli infostrada: ADSL gratis per tutta l´estate e telefoni > >>> senza canone Telecom > >>> http://click.libero.it/infostrada > >>> > >>> > >>> _______________________________________________ > >>> Ros-dev mailing list > >>> Ros-dev(a)reactos.org > >>> http://www.reactos.org/mailman/listinfo/ros-dev > >>> > >>> > >> _______________________________________________ > >> Ros-dev mailing list > >> Ros-dev(a)reactos.org > >> http://www.reactos.org/mailman/listinfo/ros-dev > >> > >> > > > > > > ------------------------------------------------------ > > Scegli infostrada: ADSL gratis per tutta l´estate e telefoni senza canone Telecom > > http://click.libero.it/infostrada > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

Re: [ros-dev] Re : ReactOS doesn't compile well
by carlo.bramix 10 Jul '07

10 Jul '07

Hello, Yes, you are right, I just checked regedit and it's bugged again. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Tue, 10 Jul 2007 20:17:20 +0200 Subject : Re: [ros-dev] Re : ReactOS doesn't compile well > Please try regedit, compiled unter Windows RosBE. I have the same > problem that carlo.bramix mentioned: no child windows shown, because of > messed up resources. regedit.exe is also smaller with LANGUAGE > LANG_DUTCH, SUBLANG_NEUTRAL. It seems to be a bug in wrc. > > Colin Finck schrieb: > > Hi, > > > > I just tested building latest trunk under Windows and 32-bit Linux (both > > with RosBE 0.3.6) and both builds resulted in correct ISOs. > > Our BuildBot also has no such problems. > > > > I tested your examples "intl.cpl" and "sysdm.cpl" and both are shown in > > english for me. > > When I switch the locale to any german locale, I get german versions of > > these apps, meaning that the whole localization thing works for me. > > > > Maybe you have to do a clean build. > > > > Best regards, > > > > Colin > > > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

Re: [ros-dev] Re : ReactOS doesn't compile well
by carlo.bramix 10 Jul '07

10 Jul '07

Hello, yep, the errors don't interrupt the compilation of ReactOS. But the resources into those coffs seem corrupted to me. For example, if I open the control panel I will see inl.cpl in german language(!) while all others are in english or if I open the system applet I can see some text without sense. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Tue, 10 Jul 2007 15:07:58 +0000 (GMT) Subject : [ros-dev] Re : ReactOS doesn't compile well > hi, > I got some of them but it didnt bother the build. > > Kind regards, > Sylvain Petreolle (aka Usurp) > --- --- --- --- --- --- --- --- --- --- --- --- --- > Run your favorite Windows apps with free ReactOS : http://www.reactos.org > Listen to non-DRMised Music: http://www.jamendo.com > > > > > ----- Message d'origine ---- > De : carlo.bramix <carlo.bramix(a)libero.it> > À : ros-dev <ros-dev(a)reactos.org> > Envoyé le : Mardi, 10 Juillet 2007, 16h52mn 51s > Objet : Re: [ros-dev] ReactOS doesn't compile well > > > Hello, > while regedit compilation was done successfully, some files aren't still generated correctly: > > [WRC] obj-i386\base\shell\cmd\cmd.coff > [WRC] obj-i386\base\system\expand\expand.coff > [WRC] obj-i386\dll\cpl\intl\intl.coff > [WRC] obj-i386\dll\cpl\intl_new\intl.coff > [WRC] obj-i386\dll\cpl\sysdm\sysdm.coff > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > [WRC] obj-i386\dll\win32\hhctrl.ocx\hhctrl.coff > [WRC] obj-i386\dll\win32\shdocvw\shdocvw.coff > > <built-in>:0: fatal error: when writing output to : Invalid argument > compilation terminated. > > I hope it could be fixed. > > Sincerely, > > Carlo Bramini > > ---------- Initial Header ----------- > > >From : ros-dev-bounces(a)reactos.org > To : "ros-dev" ros-dev(a)reactos.org > Cc : > Date : Mon, 9 Jul 2007 18:34:34 +0200 > Subject : Re: [ros-dev] ReactOS doesn't compile well > > > Hello, > > problem with compilation of regedit seems to be gone with revision 27541. > > > > Sincerely, > > > > Carlo Bramini > > > > ---------- Initial Header ----------- > > > > >From : ros-dev-bounces(a)reactos.org > > To : "ros-dev" ros-dev(a)reactos.org > > Cc : > > Date : Mon, 9 Jul 2007 11:24:29 +0200 > > Subject : [ros-dev] ReactOS doesn't compile well > > > > > Hello, > > > it looks like something wrong happens when I compile ReactOS. > > > I also did a complete clean and a make for a total rebuild, but I'm still having problems. > > > > > > I saw the first problem when I tried to test Regedit after committed changes. > > > The tree window and the listview window aren't visible (or they aren't created successfully, I didn't check this yet). > > > I tested that executable into WinXP and those child windows aren't visible too. > > > So I did these steps: > > > 1) I compiled Regedit with Visual C and I verified that it worked fine. > > > 2) I grabbed regedit.res and I manually generated regedit.coff with "windres -i regedit.res -o regedit.coff". > > > 3) I launched "make" again and it regenerated regedit.exe. > > > This last regedit.exe works fine and it has all child window controls visible. It's really a problem when generating te coff file from resources. > > > > > > I also saw a possible second problem when compiling. > > > Some compilation of '.coff' files failed. > > > On the console I read some messages like this one: > > > > > > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > > > <built-in>:0: fatal error: when writing output to : Invalid argument > > > compilation terminated. > > > > > > Actually I'm using RosBE 0.3.6 but I never got such problems with previouses svn versions of the sources. > > > > > > Sincerely, > > > > > > Carlo Bramini > > > > > > > > > > > > ------------------------------------------------------ > > > Leggi GRATIS le tue mail con il telefonino i-modeTM di Wind > > > http://i-mode.wind.it/ > > > > > > > > > _______________________________________________ > > > Ros-dev mailing list > > > Ros-dev(a)reactos.org > > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > > > > > ------------------------------------------------------ > > Leggi GRATIS le tue mail con il telefonino i-modeTM di Wind > > http://i-mode.wind.it/ > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > ------------------------------------------------------ > Scegli infostrada: ADSL gratis per tutta l´estate e telefoni senza canone Telecom > http://click.libero.it/infostrada > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

3 2

Re : ReactOS doesn't compile well
by Sylvain Petreolle 10 Jul '07

10 Jul '07

hi, I got some of them but it didnt bother the build. Kind regards, Sylvain Petreolle (aka Usurp) --- --- --- --- --- --- --- --- --- --- --- --- --- Run your favorite Windows apps with free ReactOS : http://www.reactos.org Listen to non-DRMised Music: http://www.jamendo.com ----- Message d'origine ---- De : carlo.bramix <carlo.bramix(a)libero.it> À : ros-dev <ros-dev(a)reactos.org> Envoyé le : Mardi, 10 Juillet 2007, 16h52mn 51s Objet : Re: [ros-dev] ReactOS doesn't compile well Hello, while regedit compilation was done successfully, some files aren't still generated correctly: [WRC] obj-i386\base\shell\cmd\cmd.coff [WRC] obj-i386\base\system\expand\expand.coff [WRC] obj-i386\dll\cpl\intl\intl.coff [WRC] obj-i386\dll\cpl\intl_new\intl.coff [WRC] obj-i386\dll\cpl\sysdm\sysdm.coff [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff [WRC] obj-i386\dll\win32\hhctrl.ocx\hhctrl.coff [WRC] obj-i386\dll\win32\shdocvw\shdocvw.coff <built-in>:0: fatal error: when writing output to : Invalid argument compilation terminated. I hope it could be fixed. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Mon, 9 Jul 2007 18:34:34 +0200 Subject : Re: [ros-dev] ReactOS doesn't compile well > Hello, > problem with compilation of regedit seems to be gone with revision 27541. > > Sincerely, > > Carlo Bramini > > ---------- Initial Header ----------- > > >From : ros-dev-bounces(a)reactos.org > To : "ros-dev" ros-dev(a)reactos.org > Cc : > Date : Mon, 9 Jul 2007 11:24:29 +0200 > Subject : [ros-dev] ReactOS doesn't compile well > > > Hello, > > it looks like something wrong happens when I compile ReactOS. > > I also did a complete clean and a make for a total rebuild, but I'm still having problems. > > > > I saw the first problem when I tried to test Regedit after committed changes. > > The tree window and the listview window aren't visible (or they aren't created successfully, I didn't check this yet). > > I tested that executable into WinXP and those child windows aren't visible too. > > So I did these steps: > > 1) I compiled Regedit with Visual C and I verified that it worked fine. > > 2) I grabbed regedit.res and I manually generated regedit.coff with "windres -i regedit.res -o regedit.coff". > > 3) I launched "make" again and it regenerated regedit.exe. > > This last regedit.exe works fine and it has all child window controls visible. It's really a problem when generating te coff file from resources. > > > > I also saw a possible second problem when compiling. > > Some compilation of '.coff' files failed. > > On the console I read some messages like this one: > > > > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > > <built-in>:0: fatal error: when writing output to : Invalid argument > > compilation terminated. > > > > Actually I'm using RosBE 0.3.6 but I never got such problems with previouses svn versions of the sources. > > > > Sincerely, > > > > Carlo Bramini > > > > > > > > ------------------------------------------------------ > > Leggi GRATIS le tue mail con il telefonino i-mode™ di Wind > > http://i-mode.wind.it/ > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > ------------------------------------------------------ > Leggi GRATIS le tue mail con il telefonino i-mode™ di Wind > http://i-mode.wind.it/ > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta l’estate e telefoni senza canone Telecom http://click.libero.it/infostrada _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

1 0

Re: [ros-dev] ReactOS doesn't compile well
by carlo.bramix 10 Jul '07

10 Jul '07

Hello, while regedit compilation was done successfully, some files aren't still generated correctly: [WRC] obj-i386\base\shell\cmd\cmd.coff [WRC] obj-i386\base\system\expand\expand.coff [WRC] obj-i386\dll\cpl\intl\intl.coff [WRC] obj-i386\dll\cpl\intl_new\intl.coff [WRC] obj-i386\dll\cpl\sysdm\sysdm.coff [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff [WRC] obj-i386\dll\win32\hhctrl.ocx\hhctrl.coff [WRC] obj-i386\dll\win32\shdocvw\shdocvw.coff <built-in>:0: fatal error: when writing output to : Invalid argument compilation terminated. I hope it could be fixed. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Mon, 9 Jul 2007 18:34:34 +0200 Subject : Re: [ros-dev] ReactOS doesn't compile well > Hello, > problem with compilation of regedit seems to be gone with revision 27541. > > Sincerely, > > Carlo Bramini > > ---------- Initial Header ----------- > > >From : ros-dev-bounces(a)reactos.org > To : "ros-dev" ros-dev(a)reactos.org > Cc : > Date : Mon, 9 Jul 2007 11:24:29 +0200 > Subject : [ros-dev] ReactOS doesn't compile well > > > Hello, > > it looks like something wrong happens when I compile ReactOS. > > I also did a complete clean and a make for a total rebuild, but I'm still having problems. > > > > I saw the first problem when I tried to test Regedit after committed changes. > > The tree window and the listview window aren't visible (or they aren't created successfully, I didn't check this yet). > > I tested that executable into WinXP and those child windows aren't visible too. > > So I did these steps: > > 1) I compiled Regedit with Visual C and I verified that it worked fine. > > 2) I grabbed regedit.res and I manually generated regedit.coff with "windres -i regedit.res -o regedit.coff". > > 3) I launched "make" again and it regenerated regedit.exe. > > This last regedit.exe works fine and it has all child window controls visible. It's really a problem when generating te coff file from resources. > > > > I also saw a possible second problem when compiling. > > Some compilation of '.coff' files failed. > > On the console I read some messages like this one: > > > > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > > <built-in>:0: fatal error: when writing output to : Invalid argument > > compilation terminated. > > > > Actually I'm using RosBE 0.3.6 but I never got such problems with previouses svn versions of the sources. > > > > Sincerely, > > > > Carlo Bramini > > > > > > > > ------------------------------------------------------ > > Leggi GRATIS le tue mail con il telefonino i-mode di Wind > > http://i-mode.wind.it/ > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > ------------------------------------------------------ > Leggi GRATIS le tue mail con il telefonino i-mode di Wind > http://i-mode.wind.it/ > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

Re: [ros-dev] Bug #2232 fixed.
by carlo.bramix 10 Jul '07

10 Jul '07

Ouch, sorry but I did a MISTAKE! I don't know why, but the version in my source tree is patched while the SVN one isn't. It's strange, I wonder how I could do this mistake because I use this one only for "svn up" and "make". (Since it's the PC that I use for work, I cannot spend time on it for other jobs, and I compile & debug & diff single applications separately at home, without the entire build system of ReactOS). However, I used this chance for creating a patch with "svn diff" and I posted it into bugzilla. Sincerely (and please excuse me...) Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Tue, 10 Jul 2007 11:51:44 +0200 Subject : [ros-dev] Bug #2232 fixed. > I checked the sources of r27553 and I saw that the patch has been applied. > I verified that the signaled bug doesn't happen anymore. > > Sincerely, > > Carlo Bramini. > > > > ------------------------------------------------------ > Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom > http://click.libero.it/infostrada > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

Bug #2232 fixed.
by carlo.bramix 10 Jul '07

10 Jul '07

I checked the sources of r27553 and I saw that the patch has been applied. I verified that the signaled bug doesn't happen anymore. Sincerely, Carlo Bramini. ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

Fix for few little warnings
by carlo.bramix 10 Jul '07

10 Jul '07

Hello, I would like to suggest to add these includes into these files. It will fix few very little warnings for unknown function. ------------------------------------- dll\win32\advpack\advpack.c: #include <stdlib.h> ------------------------------------- dll\win32\mpr\wnet.c: dll\win32\msi\database.c: dll\win32\msi\dialog.c: dll\win32\msi\table.c: dll\win32\oleaut32\vartype.c: #include <stdio.h> ------------------------------------- Sincerely, Carlo Bramini ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

Re: [ros-dev] ReactOS doesn't compile well
by carlo.bramix 09 Jul '07

09 Jul '07

Hello, problem with compilation of regedit seems to be gone with revision 27541. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Mon, 9 Jul 2007 11:24:29 +0200 Subject : [ros-dev] ReactOS doesn't compile well > Hello, > it looks like something wrong happens when I compile ReactOS. > I also did a complete clean and a make for a total rebuild, but I'm still having problems. > > I saw the first problem when I tried to test Regedit after committed changes. > The tree window and the listview window aren't visible (or they aren't created successfully, I didn't check this yet). > I tested that executable into WinXP and those child windows aren't visible too. > So I did these steps: > 1) I compiled Regedit with Visual C and I verified that it worked fine. > 2) I grabbed regedit.res and I manually generated regedit.coff with "windres -i regedit.res -o regedit.coff". > 3) I launched "make" again and it regenerated regedit.exe. > This last regedit.exe works fine and it has all child window controls visible. It's really a problem when generating te coff file from resources. > > I also saw a possible second problem when compiling. > Some compilation of '.coff' files failed. > On the console I read some messages like this one: > > [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff > <built-in>:0: fatal error: when writing output to : Invalid argument > compilation terminated. > > Actually I'm using RosBE 0.3.6 but I never got such problems with previouses svn versions of the sources. > > Sincerely, > > Carlo Bramini > > > > ------------------------------------------------------ > Leggi GRATIS le tue mail con il telefonino i-mode di Wind > http://i-mode.wind.it/ > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

Re: [ros-dev] Update patches into BugZilla
by carlo.bramix 09 Jul '07

09 Jul '07

Hello, Patch for bug #2365 has been updated with "svn diff taskmgr". Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Fri, 6 Jul 2007 15:04:24 +0200 Subject : [ros-dev] Update patches into BugZilla > Hello, > I updated the patch into bug #2356 and I generated it with "svn diff regedit" instead of using "diff -u" or Winmerge with a local copy. > I should do the same with the other patches that I posted, am I right? > > Sincerely, > > Carlo Bramini. > > ---------- Initial Header ----------- > > >From : ros-dev-bounces(a)reactos.org > To : "ros-dev" ros-dev(a)reactos.org > Cc : > Date : Thu, 5 Jul 2007 13:55:47 +0200 > Subject : [ros-dev] Italian fixes to TaskMgr > > > Hello, > > I posted some fixes to bug #2365. > > It fixes few things into the italian translation and I did a small improvement of the source code into affinity.c > > > > Sincerely, > > > > Carlo Bramini > > > > > > > > ------------------------------------------------------ > > Leggi GRATIS le tue mail con il telefonino i-mode di Wind > > http://i-mode.wind.it/ > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > ------------------------------------------------------ > Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom > http://click.libero.it/infostrada > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

ReactOS doesn't compile well
by carlo.bramix 09 Jul '07

09 Jul '07

Hello, it looks like something wrong happens when I compile ReactOS. I also did a complete clean and a make for a total rebuild, but I'm still having problems. I saw the first problem when I tried to test Regedit after committed changes. The tree window and the listview window aren't visible (or they aren't created successfully, I didn't check this yet). I tested that executable into WinXP and those child windows aren't visible too. So I did these steps: 1) I compiled Regedit with Visual C and I verified that it worked fine. 2) I grabbed regedit.res and I manually generated regedit.coff with "windres -i regedit.res -o regedit.coff". 3) I launched "make" again and it regenerated regedit.exe. This last regedit.exe works fine and it has all child window controls visible. It's really a problem when generating te coff file from resources. I also saw a possible second problem when compiling. Some compilation of '.coff' files failed. On the console I read some messages like this one: [WRC] obj-i386\dll\win32\comdlg32\rsrc.coff <built-in>:0: fatal error: when writing output to : Invalid argument compilation terminated. Actually I'm using RosBE 0.3.6 but I never got such problems with previouses svn versions of the sources. Sincerely, Carlo Bramini ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

Re: [ros-dev] Trunk freeze
by Aleksey Bragin 08 Jul '07

08 Jul '07

Trunk unfrozen, guilty revision partially reverted. WBR, Aleksey Bragin.

1 0

Trunk freeze
by Aleksey Bragin 08 Jul '07

08 Jul '07

Hello, trunk is frozen right now due to inability to boot into 2nd stage (it crashes with "Failure rendering glyph"). As soon as the issue is fixed, trunk will be unfrozen. Thanks for your patience. WBR, Aleksey Bragin.

1 0

Re: [ros-dev] [ros-diffs] [ekohl] 27514: - Fix indentation. - Replace tabs by spaces. - Replace STDCALL by WINAPI. - Replace Alex' unreadable single-line statements by readable ones. - No code changes.
by Alex Ionescu 08 Jul '07

08 Jul '07

While I don't mind your other re-formats, what's the purpose of insulting my code (which respected ReactOS Coding Guidelines, (please read them: http://www.reactos.org/wiki/index.php/Coding_Style)) and replacing it with non-ReactOS compliant code? Is a 71-character line so hard to read? -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of ekohl(a)svn.reactos.org Sent: July 8, 2007 1:09 PM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [ekohl] 27514: - Fix indentation. - Replace tabs by spaces. - Replace STDCALL by WINAPI. - Replace Alex' unreadable single-line statements by readable ones. - No code changes. Author: ekohl Date: Mon Jul 9 00:09:22 2007 New Revision: 27514 URL: http://svn.reactos.org/svn/reactos?rev=27514&view=rev Log: - Fix indentation. - Replace tabs by spaces. - Replace STDCALL by WINAPI. - Replace Alex' unreadable single-line statements by readable ones. - No code changes. Modified: trunk/reactos/dll/win32/kernel32/file/npipe.c Modified: trunk/reactos/dll/win32/kernel32/file/npipe.c URL:

1 0

Update patches into BugZilla
by carlo.bramix 07 Jul '07

07 Jul '07

Hello, I updated the patch into bug #2356 and I generated it with "svn diff regedit" instead of using "diff -u" or Winmerge with a local copy. I should do the same with the other patches that I posted, am I right? Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Thu, 5 Jul 2007 13:55:47 +0200 Subject : [ros-dev] Italian fixes to TaskMgr > Hello, > I posted some fixes to bug #2365. > It fixes few things into the italian translation and I did a small improvement of the source code into affinity.c > > Sincerely, > > Carlo Bramini > > > > ------------------------------------------------------ > Leggi GRATIS le tue mail con il telefonino i-mode di Wind > http://i-mode.wind.it/ > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

2 1

Italian fixes to TaskMgr
by carlo.bramix 05 Jul '07

05 Jul '07

Hello, I posted some fixes to bug #2365. It fixes few things into the italian translation and I did a small improvement of the source code into affinity.c Sincerely, Carlo Bramini ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

Re: [ros-dev] [ros-diffs] [cwittich] 27397: ZeroMemory the correct amount of bytes
by Aleksey Bragin 05 Jul '07

05 Jul '07

I think those changes are incorrect, because you're effectively zeroing sizeof(void *) instead of zeroing sizeof(PORT_DEVICE_EXTENSION). WBR, Aleksey Bragin. On Jul 5, 2007, at 5:24 AM, cwittich(a)svn.reactos.org wrote: > Author: cwittich > Date: Thu Jul 5 05:24:57 2007 > New Revision: 27397 > > URL: http://svn.reactos.org/svn/reactos?rev=27397&view=rev > Log: > ZeroMemory the correct amount of bytes > > Modified: > trunk/reactos/drivers/input/kbdclass/kbdclass.c > > Modified: trunk/reactos/drivers/input/kbdclass/kbdclass.c > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/input/ > kbdclass/kbdclass.c?rev=27397&r1=27396&r2=27397&view=diff > ====================================================================== > ======== > --- trunk/reactos/drivers/input/kbdclass/kbdclass.c (original) > +++ trunk/reactos/drivers/input/kbdclass/kbdclass.c Thu Jul 5 > 05:24:57 2007 > @@ -695,7 +695,7 @@ > } > > DeviceExtension = (PPORT_DEVICE_EXTENSION)Fdo->DeviceExtension; > - RtlZeroMemory(DeviceExtension, sizeof(CLASS_DEVICE_EXTENSION)); > + RtlZeroMemory(DeviceExtension, sizeof(PPORT_DEVICE_EXTENSION)); > DeviceExtension->Common.IsClassDO = FALSE; > DeviceExtension->DeviceObject = Fdo; > DeviceExtension->PnpState = dsStopped; > >

2 1

Re: [ros-dev] BugFixing in RegEdit
by carlo.bramix 04 Jul '07

04 Jul '07

Hello, following the suggestions that I received, I would like put your attention on these patches posted into bugzilla: - patch Posted into bug #2356. It closes these bugs: #982: some languages had IDOK and IDCANCEL in conflict because both declared as DEFPUSHBUTTON. It should be fixed. #1009: Context menu is now fully working. Fixed. - Patch posted into bug #2356. It fixes itself. - Patch posted into bug #2232 It fixes itself and some unsignaled bugs. I hope I didn't mistakes this time. Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Tue, 03 Jul 2007 12:30:36 +0200 Subject : Re: [ros-dev] BugFixing in RegEdit > carlo.bramix ha scritto: > > I'm also wondering why the patches sent to bugzilla aren't replied too. > > I don't know, perhaps I'm just unlucky. > > Just misguided. You post on Bugzilla for the posterity, and then you > post your Bugzilla number on the mailing list for the attention. You > need to get noticed *and* remembered. > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

1 0

GPLv3 Migration - flamewar warning
by Steven Edwards 04 Jul '07

04 Jul '07

Hi, I've been inactive for a while and most likely will be so for a while however I thought this would be a good time to bring up the GPLv3 due to its recent release. Does anyone have any objections to license as it stands now? If you've not had a chance to review it I suggest you do so. I am happy to help answer any questions regarding the license as I did take part in early drafting on behalf of the ReactOS and Wine Projects although I am not a lawyer and anything I say should be at least reviewed by the SFLC or your own lawyers. It is my suggestion that if there are no objections then we start to contact each developer requesting them to dual license existing code as GPLv2/GPLv3 and use the same tracking system as the audit system to do the migration. ReactOS has never been really clear on the "or later version" clause in the GPL. The ReactOS license includes the text and the license number is not specified in most of the ReactOS sources, though I don't think it would be fair to simply take all of the source and re-license it without some discussions and a vote. It would also be possible to distribute ReactOS under both licenses via dual licensing as a possible compromise if a dispute arises. This would mean if some third party (Third Party A) wants to take ReactOS enhance it and then resell it, they would not have to worry about another third party (Third Party B) taking their modifications and redistributing them for profit without the patent protections of the GPLv3 and the Anti-Tivoization clauses. The only downside to this is if Third Party A is only making changes under GPLv3 then those changes could not go back in to ReactOS trunk. I don't think this is a major issue, as I expect both third parties to be proprietary vendors making enhancements that the Project might not want/need in the trunk in any case. Third Party A in the interest of keeping forking to a minimal would still send bug fixes back up both licenses. Thanks -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo

10 21

Re: [ros-dev] [ros-diffs] [fireball] 27202: - Finally, removing frame pointer was a bad idea (think of exceptions / etc).
by Aleksey Bragin 03 Jul '07

03 Jul '07

No, I reverted all those "funny" things in revision 27367. WBR, Aleksey. On Jul 3, 2007, at 3:47 AM, Alex Ionescu wrote: > Have they been un-separated or are they still under one large file? > > -- > Best regards, > Alex Ionescu

2 1

Re: [ros-dev] BugFixing in RegEdit
by carlo.bramix 03 Jul '07

03 Jul '07

Ciao Gabriel, ti ringrazio per l'offerta, tuttavia non credo di poter accettare. Il PC "potente" e' un computer Pentium 4 3GHz che mi hanno fornito al lavoro per sbrigare una commessa. Spero, ma in realta' e' molto di piu' di una speranza, che possa diventare il mio PC definitivo. Infatti, il "vecchio" Pentium 3 lo rifilero' per svolgere il lavoro in oggetto. Anzi, mi sembra addirittura sovrastimato per quello che deve fare. Il PC che uso a casa e': Pentium 200 MHz con MMX. 48 MB di RAM Scheda video S3 VIRGE DX con 4 MB di ram. Harddisk 6.4GB (con 200 MB liberi). Monitor/tastiera/mouse. Continuo a tenere questo PC per questi motivi: 1) Per quello che devo fare io basta e avanza, ovvero scrivere e compilare codice. Nel caso specifico di ROS, io mi scarico solo i sorgenti delle applicazioni che mi interessano. Ora come ora, le compilo singolarmente e le verifico comodamente anche cosi'. E poi, tutto sommato, e' anche uno stimolo per fare meglio le cose. Se in un programma c'e' qualche cosa di inefficiente, sul mio PC si vede subito! 2) Il mio PC ha lo slot ISA. Di per se' si potrebbe pensare che sia una cavolata, ma io ho un paio di schede (tra cui i gloriosi emulatori per microcontrollore Hitachi H8) che si innestano proprio li'. La Renesas (la societa' che ha comprato e distribuisce i chip della famiglia H8) vende oggi prodotti che fanno la stessa cosa di queste schede, ma che si attaccano all'USB. Anni fa ne avevo fatto comprare uno, ma sono un'autentica porcheria, e' molto meglio quello che aveva fatto la Hitachi, anche se va su bus ISA. 3) Ho una certa linea di pensiero riguardo le applicazioni che girano sui computer. Mi rifiuto di credere che una macchina come la mia, sicuramente vetusta, non sia comunque in grado di far girare decentemente certi tipi di applicazioni. Un esempio di cio' di cui ti sto parlando: non mi era possibile vedere fluidamente i filmati DivX. Cosi' ho lavorato per un tot di tempo con il team dell'Xvid e voila': problema in buona parte risolto (per fortuna!). 4) Ci sono affezionato, l'ho comprato nel Natale del 1997(!) con i soldini guadagnati dal tirocinio fatto in un'azienda per conto del Politecnico di Torino. Il primo computer tutto mio! 5) Il case e' un desktop (di quelli che stanno comodamente sotto il monitor) e non un minitower cosi' tanto in voga oggi (chissa' poi perche'). Non avrei davvero lo spazio per un case diverso. Io abito vicino a Biella. A presto, Carlo. PS: Al momento della scrittura di questo messaggio, non c'e' stato ancora un'anima che mi abbia dato delle risposte. Bugfix su bugzilla: niente risposte. Bugfix direttamente su mailing list: niente risposte. Dannazione! Non ho ancora capito cosa ci vuole per mettere su un paio di varianti da due soldi... Non metto in dubbio il fatto che le varianti vorrebbero comunque provarle e riprovarle prima di dire "ok, chiudiamo il bug" e potrebbero non avere il tempo materiale di fare cio', pero'... il silenzio e' davvero seccante! A proposito, ce l'hai fatta poi a compilare con le mie patch? ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : ros-dev(a)reactos.org Cc : Date : Fri, 29 Jun 2007 19:34:09 +0000 Subject : Re: [ros-dev] BugFixing in RegEdit > Ciao Carlo, > > ti faccio qualche domandina? Hai detto che avevi che computer prima? E > adesso hai uno nuovo temporaneo? Di dove sei? Ti chiedo perché eventualmente > penso di aver un PIII da qualche parte, che sarei disposto a regalarti > perché tu possa collaborare in reactos... > Gabriel. > > _________________________________________________________________ > Cinema, Tv, Gossip e OrsoscopoTutto su MSN intrattenimento! > http://intrattenimento.it.msn.com/ > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lestate e telefoni senza canone Telecom http://click.libero.it/infostrada

3 2

Re: [ros-dev] BugFixing in RegEdit
by carlo.bramix 03 Jul '07

03 Jul '07

Hello, I'm also wondering why the patches sent to bugzilla aren't replied too. I don't know, perhaps I'm just unlucky. I will follow your request I'm going to post also this thing on bugzilla. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Tue, 3 Jul 2007 11:03:50 +0200 Subject : Re: [ros-dev] BugFixing in RegEdit > Hi, > > you should submit your corrections on BugZilla. > > Best regards, > Heis Spiter > > ----- Original Message ----- > From: "carlo.bramix" <carlo.bramix(a)libero.it> > To: "ros-dev" <ros-dev(a)reactos.org> > Sent: Tuesday, July 03, 2007 10:27 AM > Subject: Re: [ros-dev] BugFixing in RegEdit > > Hello, > I'm sorry, I simply forgot to remove "ros-dev(a)reactos.org" from the > destination address. > It also seems there is some people alive here, and so I'm also wondering if > those corrections could be accepted or not. > > Sincerely, > > Carlo Bramini. > > ---------- Initial Header ----------- > > >From : ros-dev-bounces(a)reactos.org > To : "ReactOS Development List" ros-dev(a)reactos.org > Cc : > Date : Tue, 3 Jul 2007 00:08:36 -0400 > Subject : Re: [ros-dev] BugFixing in RegEdit > > > Hey! I feel the love guys but... this is an english/greatlordish ML. > > Thank your for respecting the rest of us. > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

2 1

Re: [ros-dev] BugFixing in RegEdit
by carlo.bramix 03 Jul '07

03 Jul '07

Hello, I'm sorry, I simply forgot to remove "ros-dev(a)reactos.org" from the destination address. It also seems there is some people alive here, and so I'm also wondering if those corrections could be accepted or not. Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Tue, 3 Jul 2007 00:08:36 -0400 Subject : Re: [ros-dev] BugFixing in RegEdit > Hey! I feel the love guys but... this is an english/greatlordish ML. > Thank your for respecting the rest of us. > > On 7/2/07, carlo.bramix <carlo.bramix(a)libero.it> wrote: > > Ciao Gabriel, > > ti ringrazio per l'offerta, tuttavia non credo di poter accettare. > > Il PC "potente" e' un computer Pentium 4 3GHz che mi hanno fornito al lavoro per sbrigare una commessa. > > Spero, ma in realta' e' molto di piu' di una speranza, che possa diventare il mio PC definitivo. > > Infatti, il "vecchio" Pentium 3 lo rifilero' per svolgere il lavoro in oggetto. > > Anzi, mi sembra addirittura sovrastimato per quello che deve fare. > > > > Il PC che uso a casa e': > > Pentium 200 MHz con MMX. > > 48 MB di RAM > > Scheda video S3 VIRGE DX con 4 MB di ram. > > Harddisk 6.4GB (con 200 MB liberi). > > Monitor/tastiera/mouse. > > > > Continuo a tenere questo PC per questi motivi: > > 1) Per quello che devo fare io basta e avanza, ovvero scrivere e compilare codice. > > Nel caso specifico di ROS, io mi scarico solo i sorgenti delle applicazioni che mi interessano. > > Ora come ora, le compilo singolarmente e le verifico comodamente anche cosi'. > > E poi, tutto sommato, e' anche uno stimolo per fare meglio le cose. > > Se in un programma c'e' qualche cosa di inefficiente, sul mio PC si vede subito! > > 2) Il mio PC ha lo slot ISA. > > Di per se' si potrebbe pensare che sia una cavolata, ma io ho un paio di schede (tra cui i gloriosi emulatori per microcontrollore Hitachi H8) che si innestano proprio li'. > > La Renesas (la societa' che ha comprato e distribuisce i chip della famiglia H8) vende oggi prodotti che fanno la stessa cosa di queste schede, ma che si attaccano all'USB. > > Anni fa ne avevo fatto comprare uno, ma sono un'autentica porcheria, e' molto meglio quello che aveva fatto la Hitachi, anche se va su bus ISA. > > 3) Ho una certa linea di pensiero riguardo le applicazioni che girano sui computer. > > Mi rifiuto di credere che una macchina come la mia, sicuramente vetusta, non sia comunque in grado di far girare decentemente certi tipi di applicazioni. > > Un esempio di cio' di cui ti sto parlando: non mi era possibile vedere fluidamente i filmati DivX. > > Cosi' ho lavorato per un tot di tempo con il team dell'Xvid e voila': problema in buona parte risolto (per fortuna!). > > 4) Ci sono affezionato, l'ho comprato nel Natale del 1997(!) con i soldini guadagnati dal tirocinio fatto in un'azienda per conto del Politecnico di Torino. > > Il primo computer tutto mio! > > 5) Il case e' un desktop (di quelli che stanno comodamente sotto il monitor) e non un minitower cosi' tanto in voga oggi (chissa' poi perche'). Non avrei davvero lo spazio per un case diverso. > > > > Io abito vicino a Biella. > > > > A presto, > > > > Carlo. > > > > PS: > > Al momento della scrittura di questo messaggio, non c'e' stato ancora un'anima che mi abbia dato delle risposte. > > Bugfix su bugzilla: niente risposte. > > Bugfix direttamente su mailing list: niente risposte. > > Dannazione! > > Non ho ancora capito cosa ci vuole per mettere su un paio di varianti da due soldi... > > Non metto in dubbio il fatto che le varianti vorrebbero comunque provarle e riprovarle prima di dire "ok, chiudiamo il bug" e potrebbero non avere il tempo materiale di fare cio', pero'... il silenzio e' davvero seccante! > > A proposito, ce l'hai fatta poi a compilare con le mie patch? > > > > > > ---------- Initial Header ----------- > > > > >From : ros-dev-bounces(a)reactos.org > > To : ros-dev(a)reactos.org > > Cc : > > Date : Fri, 29 Jun 2007 19:34:09 +0000 > > Subject : Re: [ros-dev] BugFixing in RegEdit > > > > > Ciao Carlo, > > > > > > ti faccio qualche domandina? Hai detto che avevi che computer prima? E > > > adesso hai uno nuovo temporaneo? Di dove sei? Ti chiedo perché eventualmente > > > penso di aver un PIII da qualche parte, che sarei disposto a regalarti > > > perché tu possa collaborare in reactos... > > > Gabriel. > > > > > > _________________________________________________________________ > > > Cinema, Tv, Gossip e Orsoscopo...Tutto su MSN intrattenimento! > > > http://intrattenimento.it.msn.com/ > > > > > > _______________________________________________ > > > Ros-dev mailing list > > > Ros-dev(a)reactos.org > > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > > > > > ------------------------------------------------------ > > Scegli infostrada: ADSL gratis per tutta l'estate e telefoni senza canone Telecom > > http://click.libero.it/infostrada > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > -- > encoded > Samuel Serapión Vega > Computer Engineering, Polytechnic University of Puerto Rico. > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

2 1

A New Direction
by Alex Ionescu 03 Jul '07

03 Jul '07

It is with great excitement (and a certain amount of nostalgia) that I would like to announce two important changes in my professional life and in the direction in which I will pursue my knowledge and work on Windows Internals. The first of these changes is my debut as an instructor for David Solomon's Expert Seminars <http://www.solsem.com/>, and the second is my departure from ReactOS <http://www.reactos.org/>, effective immediately. These plans do not change in any way my internship at Apple which will take place during the summer. Some time ago, I had the great privilege of being approached by David Solomon, a well-known and highly regarded computer expert, teacher, consultant and co-author of Windows Internals 4th Edition<http://www.microsoft.com/technet/sysinternals/information/windowsinternals.…>(and Inside Windows 2000, 3 rd Edition). For the last couple of years, David had been working with Mark Russinovich, another respected figure in the world of Windows Internals, and co-founder of Winternals and Sysinternals as well as developer of some of the most useful Windows system tools available today. Apart from working on the two books (which Mark was a co-author of), they both provided trainings and seminars on Windows internals under the "David Solomon Expert Seminars" banner. As is widely known, Microsoft realized that Mark's experience and amazing work on the NT platform through his articles and tools could provide a highly beneficial new addition to the company. The company bought Winternals last year, and hired Mark at the highest technical level in the company, Technical Fellow. All this is history of course, and back to the matter at hand, Mark's recent new employment made him unavailable for teaching new classes, which made David Solomon start the search for a new instructor which could take on the responsibility of teaching new classes. I was highly honoured to have been chosen as this person, and accepted this unique opportunity to bring my knowledge out to many more people and to work with one of my most admired Windows experts. With this new job as an added task on top of my already busy life, as well as with the imminent Apple internship, I was already planning to cut back on my involvement with ReactOS. However, since it became clear that my level of contact with Microsoft employees and resources would be in conflict with my work at ReactOS, I made the difficult choice of amicably severing my ties with the project. This decision took some time for me to finalize, but the various motivations behind it had started cropping up since early this year. When I first joined ReactOS 3 years ago, the kernel was – in my opinion – highly disorganized and hodgepodge of Linux, NT 4, Wine and Windows 9x code which was very far from its actual goal of NT Driver compatibility. In fact, the development model seemed to focus on hacking NT drivers to work on ReactOS, and not vice-versa. Coincidentally, I joined the project just as the lead kernel developer, David Welch, had just burnt out and moved to other projects and goals. For the last three years, I rewrote key subsystems such as the thread scheduler, dispatcher, locking and IRQL mechanisms, HAL, executive support, object manager, process manager, I/O manager, basic VDM and 8086 support, and much more, as well as switched the project goals from NT4 to NT 5.2. My ability to do this came from my extensive reverse engineering of the kernel in the past, reading internals books, access to the DDK/IFS, as well as using WinDBG and .pdb type information. In return for all the code and guidance I provided, the project gave me a lot in return as well, including a unique perspective of working on such a project, the ability to work in large and distributed teams, and using open source tools for Windows NT kernel development. With millions of lines of code, ReactOS is the kind of project that an 18 year old could've only dreamt work ing on. I became adept in source control repositories, regression testing, unit testing, team management, IRC administration, as well as a much better coder in C. I also made friendships of all levels with various developers, testers and users, and had a chance to mentor two students during last year's Google Summer of Code. I was able to attend and give talks on ReactOS, exhibit it, and make connections with other people in the industry, and in the open source world. Overall, it's been an exhilarating adventure. After three years however, and with the many new responsibilities that had kept growing, my free time grew short. Additionally, my work in the kernel had almost reached completion. The parts that still need major work, in my opinion, require extremely skilled developers in those areas to ever be as close to NT as needed. They are also some of the most critical: the memory manager, the cache manager, the Power/PnP Manager, the configuration manager and the file system runtime library. With the current differences that exist, most modern WDM drivers as well as IFS drivers can only dream of running properly. Unfortunately, my knowledge in those areas was limited. I had never reverse engineered them as extensively as parts of the executive, and documentation on their guts is limited. In all honesty, they're also not parts of the system that interest me much. I could, of course, have continued working on user-mode parts of the system where my help would still bring a lot of the system forward, such as ntdll, csrss, smss, winsock and kernel32, but my interest in teaching with David Solomon and getting in touch with the developers behind NT outweighed that desire. After three years, I learned a tremendous amount of knowledge and skills while working on ReactOS, now the time has come for me to learn even more by expanding my horizons. In many ways, I had already outgrown the project, focusing more on security research, utilities and tools, articles and non-ReactOS related talks and conferences. It was time for me to step outside and take on a new opportunity with a larger audience and which would bring me many new experiences and teachings. I wish the ReactOS Project all the luck and I know that some significant new changes are on the horizon for them. I will keep watching from a distance, and I thank them for the most fun years of my life.- -- Best regards, Alex Ionescu

2 1

Re: [ros-dev] Ros-dev Digest, Vol 35, Issue 1
by Olaf Siejka 03 Jul '07

03 Jul '07

>Ciao Gabriel, >ti ringrazio per l'offerta, tuttavia non credo di poter accettare. This is english ML and please adhere to that.

1 0

Re: [ros-dev] [ros-diffs] [fireball] 27202: - Finally, removing frame pointer was a bad idea (think of exceptions / etc).
by Alex Ionescu 02 Jul '07

02 Jul '07

You guys are hilarious. Hint: putting all the trig functions into one file is a bad idea too. There's a reason they were made separate. Cookie for whoever finds out why. -- Best regards, Alex Ionescu -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of fireball(a)svn.reactos.org Sent: Saturday, June 16, 2007 5:29 AM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [fireball] 27202: - Finally, removing frame pointer was a bad idea (think of exceptions / etc). Author: fireball Date: Sat Jun 16 16:28:56 2007 New Revision: 27202 URL: http://svn.reactos.org/svn/reactos?rev=27202&view=rev Log: - Finally, removing frame pointer was a bad idea (think of exceptions / etc). Modified: trunk/reactos/lib/sdk/libcntpr/math/i386/fabs_asm.s trunk/reactos/lib/sdk/libcntpr/math/i386/log_asm.s trunk/reactos/lib/sdk/libcntpr/math/i386/sqrt_asm.s trunk/reactos/lib/sdk/libcntpr/math/i386/trig_asm.s Modified: trunk/reactos/lib/sdk/libcntpr/math/i386/fabs_asm.s URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/sdk/libcntpr/math/i386… ============================================================================== --- trunk/reactos/lib/sdk/libcntpr/math/i386/fabs_asm.s (original) +++ trunk/reactos/lib/sdk/libcntpr/math/i386/fabs_asm.s Sat Jun 16 16:28:56 2007 @@ -3,13 +3,47 @@ * PROJECT: ReactOS kernel * PURPOSE: Run-Time Library * FILE: lib/rtl/i386/fabs.S - * PROGRAMER: Magnus Olsen (greatlord(a)greatlord.com) -*/ + * PROGRAMER: Alex Ionescu (alex(a)relsoft.net) + * + * Copyright (C) 2002 Michael Ringgaard. + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. Neither the name of the project nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES// LOSS OF USE, DATA, OR PROFITS// OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + */ + .globl _fabs + .intel_syntax noprefix + +/* FUNCTIONS ***************************************************************/ + _fabs: - - fld qword ptr [esp+8] - fabs + push ebp + mov ebp,esp + fld qword ptr [ebp+8] // Load real from stack + fabs // Take the absolute value + pop ebp ret Modified: trunk/reactos/lib/sdk/libcntpr/math/i386/log_asm.s URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/sdk/libcntpr/math/i386… ============================================================================== --- trunk/reactos/lib/sdk/libcntpr/math/i386/log_asm.s (original) +++ trunk/reactos/lib/sdk/libcntpr/math/i386/log_asm.s Sat Jun 16 16:28:56 2007 @@ -3,14 +3,49 @@ * PROJECT: ReactOS kernel * PURPOSE: Run-Time Library * FILE: lib/rtl/i386/log.S - * PROGRAMER: Magnus Olsen (greatlord(a)greatlord.com) + * PROGRAMER: Alex Ionescu (alex(a)relsoft.net) + * + * Copyright (C) 2002 Michael Ringgaard. + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. Neither the name of the project nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + + * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES// LOSS OF USE, DATA, OR PROFITS// OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. */ + .globl _log + .intel_syntax noprefix +/* FUNCTIONS ***************************************************************/ + _log: - fld qword ptr [esp+8] - fldln2 - fxch st(1) - fyl2x + push ebp + mov ebp,esp + fld qword ptr [ebp+8] // Load real from stack + fldln2 // Load log base e of 2 + fxch st(1) // Exchange st, st(1) + fyl2x // Compute the natural log(x) + pop ebp ret Modified: trunk/reactos/lib/sdk/libcntpr/math/i386/sqrt_asm.s URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/sdk/libcntpr/math/i386… ============================================================================== --- trunk/reactos/lib/sdk/libcntpr/math/i386/sqrt_asm.s (original) +++ trunk/reactos/lib/sdk/libcntpr/math/i386/sqrt_asm.s Sat Jun 16 16:28:56 2007 @@ -3,15 +3,47 @@ * PROJECT: ReactOS kernel * PURPOSE: Run-Time Library * FILE: lib/rtl/i386/sqrt.S - * PROGRAMER: Magnus Olsen (greatlord(a)greatlord.com) + * PROGRAMER: Alex Ionescu (alex(a)relsoft.net) + * + * Copyright (C) 2002 Michael Ringgaard. + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. Neither the name of the project nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + + * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES// LOSS OF USE, DATA, OR PROFITS// OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. */ - .globl _sqrt .intel_syntax noprefix +/* FUNCTIONS ***************************************************************/ + _sqrt: - fld qword ptr [esp+8] - fsqrt + push ebp + mov ebp,esp + fld qword ptr [ebp+8] // Load real from stack + fsqrt // Take the square root + pop ebp ret Modified: trunk/reactos/lib/sdk/libcntpr/math/i386/trig_asm.s URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/sdk/libcntpr/math/i386… ============================================================================== --- trunk/reactos/lib/sdk/libcntpr/math/i386/trig_asm.s (original) +++ trunk/reactos/lib/sdk/libcntpr/math/i386/trig_asm.s Sat Jun 16 16:28:56 2007 @@ -4,33 +4,49 @@ * PURPOSE: Run-Time Library * FILE: lib/rtl/i386/trig_asm.s * PROGRAMER: Aleksey Bragin (aleksey reactos org) -*/ - + * + */ .globl _atan .globl _cos .globl _sin -.globl _tan - + .intel_syntax noprefix +/* FUNCTIONS ***************************************************************/ + _atan: - fld qword ptr [esp+8] + push ebp + mov ebp,esp + fld qword ptr [ebp+8] fld1 fpatan + pop ebp ret _cos: - fld qword ptr [esp+8] + push ebp + mov ebp,esp + fld qword ptr [ebp+8] fcos + pop ebp ret _sin: - fld qword ptr [esp+8] + push ebp + mov ebp,esp + fld qword ptr [ebp+8] fsin + pop ebp ret _tan: - fld qword ptr [esp+8] + push ebp + mov ebp,esp + sub esp,4 + fld qword ptr [ebp+8] fptan - fstp dword ptr [esp-4] + fstp dword ptr [ebp-4] + mov esp,ebp + pop ebp ret +

2 2

Re: [ros-dev] [ros-diffs] [greatlrd] 27364: experiment code adding DirectX opengl warper that using opengl lcd driver. it is Parallels modify source code of wine d3d for it. can not be compile in ReactX branch yet.
by Steven Edwards 02 Jul '07

02 Jul '07

On 7/2/07, greatlrd(a)svn.reactos.org <greatlrd(a)svn.reactos.org> wrote: > Author: greatlrd > Date: Mon Jul 2 23:47:58 2007 > New Revision: 27364 > > URL: http://svn.reactos.org/svn/reactos?rev=27364&view=rev > Log: > experiment code > adding DirectX opengl warper that using opengl lcd driver. it is Parallels modify source code of wine d3d for it. > can not be compile in ReactX branch yet. I've already fixed this locally to compile with mingw using dsw2mak if anyone wants my hacky diff and some makefiles. Contact me privately off the list and I can send you what I have thus far...wined3d.dll and d3d8.dll everything else should build as well but I have no futher need to work on this. -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo

1 0

Re : Ros-dev@reactos.org mailing list reminder
by Sylvain Petreolle 02 Jul '07

02 Jul '07

Hi people, Im receiving password reminders for the ros-dev list. Problems : - I didnt ask for it, - The password sent is not mine, - My password has been reset to the password sent in the reminder Feel free to say if you have similar problems & thanks for any help. Kind regards, Sylvain Petreolle (aka Usurp) ----- Message d'origine ---- De : "ros-dev-bounces(a)reactos.org" <ros-dev-bounces(a)reactos.org> À : spetreolle(a)yahoo.fr Envoyé le : Samedi, 30 Juin 2007, 16h40mn 54s Objet : Ros-dev(a)reactos.org mailing list reminder You, or someone posing as you, has requested a password reminder for your membership on the mailing list ros-dev(a)reactos.org. You will need this password in order to change your membership options (e.g. do you want regular delivery or digest delivery), and having this password makes it easier for you to unsubscribe from the mailing list. You are subscribed with the address: spetreolle(a)yahoo.fr Your Ros-dev password is: <removed>

1 0

BugFixing in RegEdit
by carlo.bramix 29 Jun '07

29 Jun '07

Hello, I did some testing/bug fixing into RegEdit. Bug #982: some languages still had this bug. Now seems fixed. Bug #997: In my opinion it happened because it tried to process an encoded UTF-16 registry file. Now if an UNICODE .reg file is detected, it won't be processed by ascii functions. Bug #1008: It doesn't happen into Microsoft WinXP, so it seems a bug of the edit control into ReactOS. Bug #1009: Fixed. Other bug fixes are: * Now the horizontal scrollbar is shown. * Fixed several bugs/memory leaks/destroying action into listview code. * Into the Listview, only the variable name is shown, without its entire path. * When importing a file, the handle was left open. Now it's fixed. The attached patch includes all these changes. Sincerely, Carlo Bramini ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

2 1

Re: [ros-dev] Error at compiling ReactOS
by carlo.bramix 26 Jun '07

26 Jun '07

I have the lastest thunk, it updated some files, but it doesn't work yet. In addition to this trouble, in makefile.auto there is also an error into lines like these ones: $(OUTPUT)\livecd\Profiles\Default\ User\My\ Documents: | $(OUTPUT)\livecd\Profiles\Default\ User $(ECHO_MKDIR) ${mkdir} $@ The rule must be: $(OUTPUT)\livecd\Profiles\Default\\ User\My\\ Documents: | $(OUTPUT)\livecd\Profiles\Default\\ User with two backslash otherwise the escape sequence won't work. Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Tue, 26 Jun 2007 10:04:23 +0200 Subject : Re: [ros-dev] Error at compiling ReactOS > Be sure you use the latest trunk. Weiden has fixed compilation problems. > So, update, clean, and it should work. > > ----- Original Message ----- > From: "carlo.bramix" <carlo.bramix(a)libero.it> > To: "ros-dev" <ros-dev(a)reactos.org> > Sent: Tuesday, June 26, 2007 9:39 AM > Subject: Re: [ros-dev] Error at compiling ReactOS > > Hello, > It looks like there is a bug somewhere. > I launched with "ROS_RBUILD_FLAGS=-v" and I got this output: > > [CC] tools/wpp/ppy.tab.c > [AR] output-i386/tools/wpp/libwpp.a > [LD] output-i386/tools/widl/widl.exe > [WIDL] obj-i386\include\psdk\wtypes.h > Could not open includepsdkwtypes.idl > make[1]: *** [obj-i386\include\psdk\wtypes.h] Error 2 > > Then I open makefile.auto and I manually patched '\' to '/' but just for > "wtypes". > I got this output: > > [WIDL] obj-i386/include/psdk/wtypes.h > [WIDL] obj-i386\include\psdk\exdisp.h > Could not open includepsdkexdisp.idl > make: *** [obj-i386\include\psdk\exdisp.h] Error 2 > > Sincerely, > > Carlo Bramini. > > ---------- Initial Header ----------- > > >From : ros-dev-bounces(a)reactos.org > To : "ReactOS Development List" ros-dev(a)reactos.org > Cc : > Date : Mon, 25 Jun 2007 17:12:33 +0200 > Subject : Re: [ros-dev] Error at compiling ReactOS > > > Hi, > > > > it's not important to have the latest versions, you've got to have the > > "right" versions. > > > > You seem to be using windows, just download the RosBE, the official > > ReactOS Build Environment. > > > > This should give you a start: > > http://www.reactos.org/wiki/index.php/RosBE-step-by-step > > > > Greets, > > > > David Hinz > > > > carlo.bramix schrieb: > > > Hello, > > > I can use a powerful PC for some days, so I downloaded latest ReactOS's > > > sources and I tried to compile them. > > > But after a short while, it appear this message: > > > > > > [WIDL] obj-i386\include\psdk\wtypes.h > > > Could not open includepsdkwtypes.idl > > > make: *** [obj-i386\include\psdk\wtypes.h] Error 2 > > > > > > In your opinion, what's wrong? > > > It happens into the CMD box and into MSYS too. > > > I'm sure that "Mingw & co." tools are the latest versions. > > > > > > Sincerely, > > > > > > Carlo Bramini. > > > > > > > > > ------------------------------------------------------ > > > Leggi GRATIS le tue mail con il telefonino i-modeTM di Wind > > > http://i-mode.wind.it/ > > > > > > > > > _______________________________________________ > > > Ros-dev mailing list > > > Ros-dev(a)reactos.org > > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > ------------------------------------------------------ > Leggi GRATIS le tue mail con il telefonino i-modeT di Wind > http://i-mode.wind.it/ > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

Re: [ros-dev] Error at compiling ReactOS
by carlo.bramix 26 Jun '07

26 Jun '07

Hello, It looks like there is a bug somewhere. I launched with "ROS_RBUILD_FLAGS=-v" and I got this output: [CC] tools/wpp/ppy.tab.c [AR] output-i386/tools/wpp/libwpp.a [LD] output-i386/tools/widl/widl.exe [WIDL] obj-i386\include\psdk\wtypes.h Could not open includepsdkwtypes.idl make[1]: *** [obj-i386\include\psdk\wtypes.h] Error 2 Then I open makefile.auto and I manually patched '\' to '/' but just for "wtypes". I got this output: [WIDL] obj-i386/include/psdk/wtypes.h [WIDL] obj-i386\include\psdk\exdisp.h Could not open includepsdkexdisp.idl make: *** [obj-i386\include\psdk\exdisp.h] Error 2 Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Mon, 25 Jun 2007 17:12:33 +0200 Subject : Re: [ros-dev] Error at compiling ReactOS > Hi, > > it's not important to have the latest versions, you've got to have the > "right" versions. > > You seem to be using windows, just download the RosBE, the official > ReactOS Build Environment. > > This should give you a start: > http://www.reactos.org/wiki/index.php/RosBE-step-by-step > > Greets, > > David Hinz > > carlo.bramix schrieb: > > Hello, > > I can use a powerful PC for some days, so I downloaded latest ReactOS's sources and I tried to compile them. > > But after a short while, it appear this message: > > > > [WIDL] obj-i386\include\psdk\wtypes.h > > Could not open includepsdkwtypes.idl > > make: *** [obj-i386\include\psdk\wtypes.h] Error 2 > > > > In your opinion, what's wrong? > > It happens into the CMD box and into MSYS too. > > I'm sure that "Mingw & co." tools are the latest versions. > > > > Sincerely, > > > > Carlo Bramini. > > > > > > ------------------------------------------------------ > > Leggi GRATIS le tue mail con il telefonino i-modeTM di Wind > > http://i-mode.wind.it/ > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

2 1

Thanks, Ros developers, I'm going to download the source
by Fan Decheng 26 Jun '07

26 Jun '07

I first saw this project in 2005, and today, in order to have a rough idea of Windows Cache Manager, I want to download the Ros source code to see if it is something alike and whether it can help me. Regards, Fan Decheng 2007-06-26

2 2

Re: [ros-dev] [ros-diffs] [fireball] 27272: - Change BSOD's size to 1200x900 to match OLPC. - Temporarily comment out CMPXCHG8B cpu feature support detection (Geode seems to be not recognized).
by Alex Ionescu 25 Jun '07

25 Jun '07

+#if 0 //FIXME: Investigate why it's reported that Geode does not support this. if (!(KeFeatureBits & KF_CMPXCHG8B)) { /* Copy the vendor string */ @@ -475,6 +476,7 @@ Vendor[1], Vendor[2]); } +#endif Umm, because it doesn't. -- Best regards, Alex Ionescu

3 4

Error at compiling ReactOS
by carlo.bramix 25 Jun '07

25 Jun '07

Hello, I can use a powerful PC for some days, so I downloaded latest ReactOS's sources and I tried to compile them. But after a short while, it appear this message: [WIDL] obj-i386\include\psdk\wtypes.h Could not open includepsdkwtypes.idl make: *** [obj-i386\include\psdk\wtypes.h] Error 2 In your opinion, what's wrong? It happens into the CMD box and into MSYS too. I'm sure that "Mingw & co." tools are the latest versions. Sincerely, Carlo Bramini. ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

2 1

Re: [ros-dev] Autoplay configuration.
by carlo.bramix 21 Jun '07

21 Jun '07

Hello, Hopefully, at work I have Windows XP and at home I have Win9x. This gave me great chances of testing when I develop a software. I was just guessing if the autoplay nightmare could be disabled in a more user-friendly way and natively into the configuration of the explorer into ReactOS. Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Thu, 21 Jun 2007 12:10:47 -0600 Subject : Re: [ros-dev] Autoplay configuration. > On 6/21/07, carlo.bramix wrote: > > > > I didn't use Vista yet, but I wouldn't like to decided every time the > > actions to do. > > Usually, when I double-click on the CD/DVD icon, I would like to explore > > the content of the disk. > > I don't want to see something asking me "explore disk? autoplay disk? play > > disk?", I just want to see the directory structure. > > > Haha, I wasn't saying that it should ask you every time you double click the > drive icon. I was talking about when you actually put in the disc or > connect a device. > > > I already solved this little need my Win9x platforms with a very little C > > programme. > > Personally, I can't see a valid reason for not putting this little thing > > (enable/disable autoplay features) somewhere. > > > Things have changed a lot with autoplay from earlier Windows versions to XP, > and even more from XP to Vista. Vista even has a section in the control > panel for autoplay configuration: > http://img160.imageshack.us/img160/6287/windowsvistaautoplayjs2.png (169 KB) > > Also, you have brought up a good point. Besides those parts of the autoplay > configuration, ReactOS should have an additional option to specify whether > to just view the contents of the drive with no autoplay prompts when you > double-click a drive or open up the autoplay options when you double click > the drive -- that is, if it will even support opening that up at all when > double-clicking a drive, which if it doesn't that's fine, too, as long as > the option is at least there when right-clicking the drive. > > -ShadowFlare > > > Sincerely, > > > > Carlo Bramini > > > > > > ---------- Initial Header ----------- > > > > >From : ros-dev-bounces(a)reactos.org > > To : "ReactOS Development List" ros-dev(a)reactos.org > > Cc : > > Date : Tue, 19 Jun 2007 17:05:13 -0600 > > Subject : Re: [ros-dev] Autoplay configuration. > > > > > On 6/19/07, carlo.bramix wrote: > > > > > > > > Hello, > > > > I would like to suggest the addition of a little feature into ReactOS. > > > > Here there is a little reference to be read near my suggestion: > > > > > > > > > > > > > > http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentr… > > > > > > > > Autorun could be useful, but sometimes it's very annoying. > > > > So: what about adding a little page somewhere for configuring it? > > > > Into Win9x it was partially configurable on CD/DVD units, but newer > > > > versions of Windows lost completely this ability. > > > > I think that a little page with some check-boxes: > > > > > > > > [ ] Disables Autoplay on removable drives > > > > [X] Disables Autoplay on fixed drives. > > > > > > > > ..etc > > > > would be really cool because it fixes a mess into modern Microsoft's > > > > products. > > > > I think it can be done in 100 lines of code (perhaps even less). > > > > If we decide that it can be added, we just need to decide where we > > could > > > > put them. > > > > > > > > I know that ReactOS haven't autoplay feature yet, but adding its > > > > configuration isn't too difficult. > > > > Where can it be placed? > > > > Personally, I wouldn't add a new applet into the control panel only > > for > > > > it. > > > > Or if you don't want it at all, or you don't want it for now, it's ok > > too. > > > > > > > > Sincerely, > > > > > > > > Carlo Bramini. > > > > > > > > _______________________________________________ > > > > Ros-dev mailing list > > > > Ros-dev(a)reactos.org > > > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > > > > > > Personally, I think Windows Vista's autorun/autoplay options are great, > > and > > > it does have a place to change the configuration for them easily. In my > > > opinion, Microsoft finally got it right on that version. It even asks > > > whether you want the run the program from autorun.inf, so no more > > holding > > > shift while inserting CDs. :) It also gives the other usual autoplay > > > options even on CDs that do have a program specified in autorun.inf. > > > > > > In my opinion, ReactOS should do it the same way, at least as far as > > asking > > > whether to run the program or not when you insert a CD or plug in a > > drive. > > > > > > -ShadowFlare > > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > >

1 0

Re: [ros-dev] Autoplay configuration.
by carlo.bramix 21 Jun '07

21 Jun '07

I didn't use Vista yet, but I wouldn't like to decided every time the actions to do. Usually, when I double-click on the CD/DVD icon, I would like to explore the content of the disk. I don't want to see something asking me "explore disk? autoplay disk? play disk?", I just want to see the directory structure. I already solved this little need my Win9x platforms with a very little C programme. Personally, I can't see a valid reason for not putting this little thing (enable/disable autoplay features) somewhere. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Tue, 19 Jun 2007 17:05:13 -0600 Subject : Re: [ros-dev] Autoplay configuration. > On 6/19/07, carlo.bramix wrote: > > > > Hello, > > I would like to suggest the addition of a little feature into ReactOS. > > Here there is a little reference to be read near my suggestion: > > > > > > http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentr… > > > > Autorun could be useful, but sometimes it's very annoying. > > So: what about adding a little page somewhere for configuring it? > > Into Win9x it was partially configurable on CD/DVD units, but newer > > versions of Windows lost completely this ability. > > I think that a little page with some check-boxes: > > > > [ ] Disables Autoplay on removable drives > > [X] Disables Autoplay on fixed drives. > > > > ..etc > > would be really cool because it fixes a mess into modern Microsoft's > > products. > > I think it can be done in 100 lines of code (perhaps even less). > > If we decide that it can be added, we just need to decide where we could > > put them. > > > > I know that ReactOS haven't autoplay feature yet, but adding its > > configuration isn't too difficult. > > Where can it be placed? > > Personally, I wouldn't add a new applet into the control panel only for > > it. > > Or if you don't want it at all, or you don't want it for now, it's ok too. > > > > Sincerely, > > > > Carlo Bramini. > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > Personally, I think Windows Vista's autorun/autoplay options are great, and > it does have a place to change the configuration for them easily. In my > opinion, Microsoft finally got it right on that version. It even asks > whether you want the run the program from autorun.inf, so no more holding > shift while inserting CDs. :) It also gives the other usual autoplay > options even on CDs that do have a program specified in autorun.inf. > > In my opinion, ReactOS should do it the same way, at least as far as asking > whether to run the program or not when you insert a CD or plug in a drive. > > -ShadowFlare >

2 2

Re: [ros-dev] Ros-dev Digest, Vol 34, Issue 14
by Olaf Siejka 21 Jun '07

21 Jun '07

> Personally, I think Windows Vista's autorun/autoplay options are great, and > it does have a place to change the configuration for them easily. In my > opinion, Microsoft finally got it right on that version. I hate autorun and always disable it. I always hate that menu where you can choose what to do with CD/connected storage device/camera etc. I`d love to see ROS silent or at least being allowed to disable all those unneeded extras. Regards Caemyr

1 0

Re: [ros-dev] Ros-dev Digest, Vol 34, Issue 14
by Olaf Siejka 21 Jun '07

21 Jun '07

>People developing ReactOS also usually join our IRC-channel #reactos >on freenode. >If you become a steady ReactOS developer, somebody will offer you SVN >write access so you don't need to submit everything to bugzilla, but >that will take a while... If you think you can participate in develompent of any particular subsystem/part of Ros you should speak with Fireball on #reactos. He may designate you to some specified field. This could speed up the joining process, but do it only if you feel experienced enough. Regards Caemyr

1 0

Mailings list
by fatih yedikapi 21 Jun '07

21 Jun '07

Hi,your mailling system showed me to send you this mail so you can get the decision on accepting me to join the development-team of ReactOSKind regards,Fatih Yedikapi** Greating from best friend, Fatih Yedikapi ** _________________________________________________________________ Via je PC gratis je vrienden hun PC bellen http://get.live.com/messenger/overview

2 1

Using ROS cmd.exe with pipes
by SqUe Squarious 21 Jun '07

21 Jun '07

Hi I am trying to use the cmd.exe of reactos (on Windows!) with redirected stdin/out/err. What I try to make is a remote shell application over internet, and this is an important requirement for me, that it will work with reacto's cmd.exe. I have build a test program that will redirect locally. open the process ( cmd.exe at least for now) and will forward output on a EditBox. The whole process works quite well with the cmd.exe of M$ Windows but its buggy with the cmd.exe of reactos. More specifically when I start the redirection I just get the current path and ">" usual prompt, but after that, the communication gets unresponsive. Whatever I send, there will be no return messages. I attached the test project, and I would like to advice me if there is a better approach that will work for ROS cmd.exe too.

2 1

Re: [ros-dev] Using ROS cmd.exe with pipes (SqUe Squarious)
by Jonathan Rennison 20 Jun '07

20 Jun '07

>Hi I am trying to use the cmd.exe of reactos (on Windows!) with redirected >stdin/out/err. What I try to make is a remote shell application over >internet, and this is an important requirement for me, that it will work >with reacto's cmd.exe. >I have build a test program that will redirect locally. open the process >(cmd.exe at least for now) and will forward output on a EditBox. The whole >process works quite well with the cmd.exe of M$ >Windows but its buggy with >the cmd.exe of reactos. More specifically when I start the redirection I >just get the current path and ">" usual prompt, but after that, the >communication gets unresponsive. >Whatever I send, there will be no return >messages. >I attached the test project, and I would like to advice me if there is a >better approach that will work for ROS cmd.exe too. What you have proposed is basically telnet. Extremely insecure. You really should consider using SSH or similar. Also it looks like you are using pipes to do the transferring from the code (but I could have misread it), and they only traverse local networks. You'd be better off with netcat or similar (if you're OK with low security). You could just use a command line like: netcat | cmd | netcat JGR _________________________________________________________________ MSN Music http://music.msn.no Finn din favorittmusikk blant nesten 1 million låter

2 1

Autoplay configuration.
by carlo.bramix 19 Jun '07

19 Jun '07

Hello, I would like to suggest the addition of a little feature into ReactOS. Here there is a little reference to be read near my suggestion: http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentr… Autorun could be useful, but sometimes it's very annoying. So: what about adding a little page somewhere for configuring it? Into Win9x it was partially configurable on CD/DVD units, but newer versions of Windows lost completely this ability. I think that a little page with some check-boxes: [ ] Disables Autoplay on removable drives [X] Disables Autoplay on fixed drives. ..etc would be really cool because it fixes a mess into modern Microsoft's products. I think it can be done in 100 lines of code (perhaps even less). If we decide that it can be added, we just need to decide where we could put them. I know that ReactOS haven't autoplay feature yet, but adding its configuration isn't too difficult. Where can it be placed? Personally, I wouldn't add a new applet into the control panel only for it. Or if you don't want it at all, or you don't want it for now, it's ok too. Sincerely, Carlo Bramini.

2 1

Re: [ros-dev] [ros-diffs] [spetreolle] 27203: revert previous r27194 ntoskrnl already exports InterlockedDe/Increment spotted by hpoussin still fails to link, thans to heisspiter for win32 test
by Alex Ionescu 17 Jun '07

17 Jun '07

So the reason you noticed this was wrong wasn't because DRIVERS SHOULDN'T IMPORT USER-MODE WIN32 DLLS... but because someone else was already exporting it. Sweet. Hint: Try including #intrin.h next time. -- Best regards, Alex Ionescu -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of spetreolle(a)svn.reactos.org Sent: Saturday, June 16, 2007 5:45 AM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [spetreolle] 27203: revert previous r27194 ntoskrnl already exports InterlockedDe/Increment spotted by hpoussin still fails to link, thans to heisspiter for win32 test Author: spetreolle Date: Sat Jun 16 16:45:02 2007 New Revision: 27203 URL: http://svn.reactos.org/svn/reactos?rev=27203&view=rev Log: revert previous r27194 ntoskrnl already exports InterlockedDe/Increment spotted by hpoussin still fails to link, thans to heisspiter for win32 test Modified: trunk/reactos/drivers/wdm/audio/backpln/portcls/portcls.rbuild Modified: trunk/reactos/drivers/wdm/audio/backpln/portcls/portcls.rbuild URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/wdm/audio/backpln/… ============================================================================== --- trunk/reactos/drivers/wdm/audio/backpln/portcls/portcls.rbuild (original) +++ trunk/reactos/drivers/wdm/audio/backpln/portcls/portcls.rbuild Sat Jun 16 16:45:02 2007 @@ -8,7 +8,6 @@ <library>ntoskrnl</library> <library>ks</library> <library>drmk</library> - <library>kernel32</library> <file>dll.c</file> <file>adapter.c</file>

1 0

Re: [ros-dev] [ros-diffs] [fireball] 27186: - Resurrect "old"bootvid. The plan is to * make it working in trunk * addframebuffer support for olpc and xbox kind of devices.
by Aleksey Bragin 16 Jun '07

16 Jun '07

I neved did and never intend to merge hacks from branches into the trunk. I don't know where from you are referring to "I'm afraid that fireballs sollution is merged into trunk in some time"?! I commented out almost all freeldr's bootsector boot stub in the branch, does that mean it will somewhen be merged in trunk? Obviously the answer is no. I don't know what do you smoke to think it will :-). WBR, Aleksey Bragin. On Jun 16, 2007, at 6:07 AM, Michael Fritscher wrote: > The problem: the new bootvid needs vga, which the olpc doesn`t have... > For the other problem (freeloader import problem): He can't press > enter on > this machine because of the bios. > Perhaps that could be better solved by a new option in freeldr, > which make > disappear all messages in say 3-5 seconds. > > I'm afraid that fireballs sollution is merged into trunk in some time, > which would hide this problem indead.

1 0

Re: [ros-dev] [ros-diffs] [fireball] 27186: - Resurrect "old" bootvid. The plan is to * make it working in trunk * add framebuffer support for olpc and xbox kind of devices.
by Alex Ionescu 16 Jun '07

16 Jun '07

Screwing up compatibility continues! Here's an idea, let's rename all the kernel exports! -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of fireball(a)svn.reactos.org Sent: Friday, June 15, 2007 3:59 AM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [fireball] 27186: - Resurrect "old" bootvid. The plan is to * make it working in trunk * add framebuffer support for olpc and xbox kind of devices. Author: fireball Date: Fri Jun 15 14:58:37 2007 New Revision: 27186 URL: http://svn.reactos.org/svn/reactos?rev=27186&view=rev Log: - Resurrect "old" bootvid. The plan is to * make it working in trunk * add framebuffer support for olpc and xbox kind of devices. Added: branches/olpc/drivers/base/bootvid/bar.bmp - copied unchanged from r25677, trunk/reactos/drivers/base/bootvid/bar.bmp branches/olpc/drivers/base/bootvid/bootimage.bmp - copied unchanged from r25677, trunk/reactos/drivers/base/bootvid/bootimage.bmp branches/olpc/drivers/base/bootvid/bootvid.h - copied unchanged from r25677, trunk/reactos/drivers/base/bootvid/bootvid.h branches/olpc/drivers/base/bootvid/resource.h - copied unchanged from r25677, trunk/reactos/drivers/base/bootvid/resource.h branches/olpc/drivers/base/bootvid/vid.c - copied unchanged from r25677, trunk/reactos/drivers/base/bootvid/vid.c branches/olpc/drivers/base/bootvid/vid_vga.c - copied unchanged from r25677, trunk/reactos/drivers/base/bootvid/vid_vga.c branches/olpc/drivers/base/bootvid/vid_vgatext.c - copied unchanged from r25677, trunk/reactos/drivers/base/bootvid/vid_vgatext.c branches/olpc/drivers/base/bootvid/vid_xbox.c - copied unchanged from r25677, trunk/reactos/drivers/base/bootvid/vid_xbox.c Removed: branches/olpc/drivers/base/bootvid/bootdata.c branches/olpc/drivers/base/bootvid/precomp.h branches/olpc/drivers/base/bootvid/vga.c Modified: branches/olpc/drivers/base/bootvid/bootvid.c (contents, props changed) branches/olpc/drivers/base/bootvid/bootvid.def (contents, props changed) branches/olpc/drivers/base/bootvid/bootvid.rbuild (contents, props changed) branches/olpc/drivers/base/bootvid/bootvid.rc (contents, props changed) Removed: branches/olpc/drivers/base/bootvid/bootdata.c URL: http://svn.reactos.org/svn/reactos/branches/olpc/drivers/base/bootvid/bootd… ============================================================================== --- branches/olpc/drivers/base/bootvid/bootdata.c (original) +++ branches/olpc/drivers/base/bootvid/bootdata.c (removed) @@ -1,309 +1,0 @@ -#include "precomp.h" - -USHORT AT_Initialization[] = -{ - 0x10 | CMD_STREAM_READ, // Major Command = 0x10. Minor Command = 0x08. - 0x3DA, // Index Status 1 Register Port Address - - // - // This Stream performs a USHORT Array Indexed Write at port 0x3C0 - // - 0x20 | 0x01, // Major Command = 0x20. Minor Command = 0x01. - 0x3C0, // Attribute Controller Data Register - 0x10, // Loop Count = 16 (Number of Pallette Entries) - 0x0, // Index to select (Index = 0, palettes) - 0x00, // Palette 0 - 0x01, // Palette 1 - 0x02, // Palette 2 - 0x03, // Palette 3 - 0x04, // Palette 4 - 0x05, // Palette 5 - 0x06, // Palette 6 - 0x07, // Palette 7 - 0x08, // Palette 8 - 0x09, // Palette 9 - 0x0A, // Palette 10 - 0x0B, // Palette 11 - 0x0C, // Palette 12 - 0x0D, // Palette 13 - 0x0E, // Palette 14 - 0x0F, // Palette 15 - - // - // This Stream performs a UCHAR READ of port 0x3DA - // - 0x10 | CMD_STREAM_READ, // Major Command = 0x10. Minor Command = 0x08. - 0x3DA, // Index Status 1 Register Port Address - - // - // This Stream performs a UCHAR WRITE of value 0x20 at port 0x3C0 - // - 0x10 | CMD_STREAM_WRITE, // Major Command = 0x10. Minor Command = 0x00. - 0x3C0, // Attribute Controller Data Register - 0x20, // Set Palette Address Source - - // - // End of Stream Marker - // - 0x0 // End of command stream -}; - -UCHAR FontData[256 * 13] = -{ - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 0 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 13 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 26 - 0x18, 0x24, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 39 - 0x14, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 52 - 0x00, 0x24, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 65 - 0x24, 0x18, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 78 - 0x10, 0x28, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 91 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x10, 0x10, // 104 - 0x14, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 117 - 0x28, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 130 - 0x10, 0x20, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 143 - 0x10, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 156 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x10, // 169 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 182 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 195 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 208 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 221 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 234 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 247 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 260 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 273 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 286 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 299 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 312 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 325 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 338 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 351 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 364 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 377 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 390 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 403 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 416 - 0x00, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x00, 0x00, 0x10, 0x00, 0x00, 0x00, // 429 - 0x24, 0x24, 0x24, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 442 - 0x00, 0x14, 0x14, 0x14, 0x7F, 0x28, 0xFE, 0x50, 0x50, 0x50, 0x00, 0x00, 0x00, // 455 - 0x10, 0x3C, 0x50, 0x50, 0x70, 0x38, 0x1C, 0x14, 0x14, 0x78, 0x10, 0x00, 0x00, // 468 - 0x00, 0x61, 0x92, 0x94, 0x68, 0x18, 0x16, 0x29, 0x49, 0x86, 0x00, 0x00, 0x00, // 481 - 0x00, 0x18, 0x24, 0x24, 0x38, 0x71, 0x89, 0x8E, 0xC6, 0x7E, 0x00, 0x00, 0x00, // 494 - 0x10, 0x10, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 507 - 0x06, 0x08, 0x10, 0x30, 0x20, 0x20, 0x20, 0x20, 0x30, 0x10, 0x08, 0x06, 0x00, // 520 - 0x60, 0x10, 0x08, 0x04, 0x04, 0x04, 0x04, 0x04, 0x04, 0x08, 0x10, 0x60, 0x00, // 533 - 0x00, 0x10, 0x52, 0x24, 0x3C, 0x24, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 546 - 0x00, 0x00, 0x00, 0x10, 0x10, 0x10, 0xFE, 0x10, 0x10, 0x10, 0x00, 0x00, 0x00, // 559 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x30, 0x30, 0x10, 0x20, 0x00, // 572 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x7E, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 585 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x30, 0x30, 0x00, 0x00, 0x00, // 598 - 0x01, 0x02, 0x02, 0x04, 0x08, 0x08, 0x10, 0x10, 0x20, 0x40, 0x40, 0x80, 0x00, // 611 - 0x00, 0x18, 0x24, 0x42, 0x42, 0x42, 0x42, 0x42, 0x24, 0x3C, 0x00, 0x00, 0x00, // 624 - 0x00, 0x30, 0xD0, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0xFE, 0x00, 0x00, 0x00, // 637 - 0x00, 0x78, 0x04, 0x04, 0x04, 0x08, 0x10, 0x20, 0x40, 0x7C, 0x00, 0x00, 0x00, // 650 - 0x00, 0x78, 0x04, 0x04, 0x08, 0x30, 0x0C, 0x04, 0x04, 0x78, 0x00, 0x00, 0x00, // 663 - 0x00, 0x08, 0x18, 0x28, 0x28, 0x48, 0x88, 0xFC, 0x08, 0x08, 0x00, 0x00, 0x00, // 676 - 0x00, 0x3C, 0x20, 0x20, 0x38, 0x04, 0x04, 0x04, 0x04, 0x38, 0x00, 0x00, 0x00, // 689 - 0x00, 0x1C, 0x20, 0x40, 0x5C, 0x62, 0x42, 0x42, 0x22, 0x1C, 0x00, 0x00, 0x00, // 702 - 0x00, 0x7E, 0x02, 0x04, 0x08, 0x08, 0x10, 0x10, 0x20, 0x20, 0x00, 0x00, 0x00, // 715 - 0x00, 0x3C, 0x42, 0x42, 0x24, 0x3C, 0x46, 0x42, 0x42, 0x3C, 0x00, 0x00, 0x00, // 728 - 0x00, 0x38, 0x44, 0x42, 0x42, 0x46, 0x3A, 0x02, 0x04, 0x38, 0x00, 0x00, 0x00, // 741 - 0x00, 0x00, 0x00, 0x18, 0x18, 0x00, 0x00, 0x00, 0x18, 0x18, 0x00, 0x00, 0x00, // 754 - 0x00, 0x00, 0x00, 0x30, 0x30, 0x00, 0x00, 0x00, 0x30, 0x30, 0x10, 0x20, 0x00, // 767 - 0x00, 0x00, 0x00, 0x02, 0x0C, 0x10, 0x60, 0x10, 0x0C, 0x02, 0x00, 0x00, 0x00, // 780 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x7E, 0x00, 0x7E, 0x00, 0x00, 0x00, 0x00, 0x00, // 793 - 0x00, 0x00, 0x00, 0x40, 0x30, 0x08, 0x06, 0x08, 0x30, 0x40, 0x00, 0x00, 0x00, // 806 - 0x00, 0x7C, 0x42, 0x02, 0x04, 0x08, 0x10, 0x00, 0x00, 0x10, 0x00, 0x00, 0x00, // 819 - 0x00, 0x3C, 0x62, 0xDE, 0xB2, 0xA2, 0xA6, 0x9B, 0x44, 0x3C, 0x00, 0x00, 0x00, // 832 - 0x00, 0x00, 0x18, 0x18, 0x24, 0x24, 0x24, 0x7E, 0x42, 0x81, 0x00, 0x00, 0x00, // 845 - 0x00, 0x00, 0x7C, 0x42, 0x42, 0x7C, 0x42, 0x42, 0x42, 0x7C, 0x00, 0x00, 0x00, // 858 - 0x00, 0x00, 0x3E, 0x40, 0x80, 0x80, 0x80, 0x80, 0x40, 0x3E, 0x00, 0x00, 0x00, // 871 - 0x00, 0x00, 0x78, 0x44, 0x42, 0x42, 0x42, 0x42, 0x44, 0x78, 0x00, 0x00, 0x00, // 884 - 0x00, 0x00, 0x7E, 0x40, 0x40, 0x40, 0x7C, 0x40, 0x40, 0x7E, 0x00, 0x00, 0x00, // 897 - 0x00, 0x00, 0x7E, 0x40, 0x40, 0x40, 0x7C, 0x40, 0x40, 0x40, 0x00, 0x00, 0x00, // 910 - 0x00, 0x00, 0x3E, 0x40, 0x80, 0x80, 0x8E, 0x82, 0x42, 0x3E, 0x00, 0x00, 0x00, // 923 - 0x00, 0x00, 0x42, 0x42, 0x42, 0x7E, 0x42, 0x42, 0x42, 0x42, 0x00, 0x00, 0x00, // 936 - 0x00, 0x00, 0x7C, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x7C, 0x00, 0x00, 0x00, // 949 - 0x00, 0x00, 0x3C, 0x04, 0x04, 0x04, 0x04, 0x04, 0x04, 0x78, 0x00, 0x00, 0x00, // 962 - 0x00, 0x00, 0x42, 0x44, 0x48, 0x70, 0x50, 0x48, 0x44, 0x42, 0x00, 0x00, 0x00, // 975 - 0x00, 0x00, 0x40, 0x40, 0x40, 0x40, 0x40, 0x40, 0x40, 0x7E, 0x00, 0x00, 0x00, // 988 - 0x00, 0x00, 0xC6, 0xC6, 0xAA, 0xAA, 0xAA, 0x92, 0x82, 0x82, 0x00, 0x00, 0x00, // 1001 - 0x00, 0x00, 0x42, 0x62, 0x52, 0x52, 0x4A, 0x4A, 0x46, 0x42, 0x00, 0x00, 0x00, // 1014 - 0x00, 0x00, 0x38, 0x44, 0x82, 0x82, 0x82, 0x82, 0x44, 0x38, 0x00, 0x00, 0x00, // 1027 - 0x00, 0x00, 0x7C, 0x42, 0x42, 0x42, 0x7C, 0x40, 0x40, 0x40, 0x00, 0x00, 0x00, // 1040 - 0x00, 0x00, 0x38, 0x44, 0x82, 0x82, 0x82, 0x82, 0x44, 0x38, 0x06, 0x03, 0x00, // 1053 - 0x00, 0x00, 0x78, 0x44, 0x44, 0x44, 0x78, 0x48, 0x44, 0x42, 0x00, 0x00, 0x00, // 1066 - 0x00, 0x00, 0x3E, 0x40, 0x40, 0x38, 0x04, 0x02, 0x02, 0x7C, 0x00, 0x00, 0x00, // 1079 - 0x00, 0x00, 0xFE, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x00, 0x00, 0x00, // 1092 - 0x00, 0x00, 0x42, 0x42, 0x42, 0x42, 0x42, 0x42, 0x42, 0x3C, 0x00, 0x00, 0x00, // 1105 - 0x00, 0x00, 0x81, 0x42, 0x42, 0x44, 0x24, 0x28, 0x38, 0x10, 0x00, 0x00, 0x00, // 1118 - 0x00, 0x00, 0x81, 0x81, 0x92, 0x5A, 0x5A, 0x6A, 0x66, 0x24, 0x00, 0x00, 0x00, // 1131 - 0x00, 0x00, 0x81, 0x42, 0x24, 0x18, 0x18, 0x24, 0x42, 0x81, 0x00, 0x00, 0x00, // 1144 - 0x00, 0x00, 0x82, 0x44, 0x28, 0x28, 0x10, 0x10, 0x10, 0x10, 0x00, 0x00, 0x00, // 1157 - 0x00, 0x00, 0xFE, 0x02, 0x04, 0x08, 0x10, 0x20, 0x40, 0xFE, 0x00, 0x00, 0x00, // 1170 - 0x1E, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x1E, 0x00, // 1183 - 0x80, 0x40, 0x40, 0x20, 0x10, 0x10, 0x08, 0x08, 0x04, 0x02, 0x02, 0x01, 0x00, // 1196 - 0x78, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x78, 0x00, // 1209 - 0x00, 0x08, 0x08, 0x18, 0x14, 0x24, 0x24, 0x42, 0x00, 0x00, 0x00, 0x00, 0x00, // 1222 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, // 1235 - 0x10, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 1248 - 0x00, 0x00, 0x00, 0x38, 0x04, 0x04, 0x3C, 0x44, 0x44, 0x3E, 0x00, 0x00, 0x00, // 1261 - 0x40, 0x40, 0x40, 0x5C, 0x62, 0x42, 0x42, 0x42, 0x62, 0x5C, 0x00, 0x00, 0x00, // 1274 - 0x00, 0x00, 0x00, 0x1E, 0x20, 0x40, 0x40, 0x40, 0x20, 0x1E, 0x00, 0x00, 0x00, // 1287 - 0x02, 0x02, 0x02, 0x3A, 0x46, 0x42, 0x42, 0x42, 0x46, 0x3A, 0x00, 0x00, 0x00, // 1300 - 0x00, 0x00, 0x00, 0x3C, 0x22, 0x42, 0x7E, 0x40, 0x40, 0x3E, 0x00, 0x00, 0x00, // 1313 - 0x1E, 0x20, 0x20, 0xFE, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x00, 0x00, 0x00, // 1326 - 0x00, 0x00, 0x00, 0x3A, 0x46, 0x42, 0x42, 0x42, 0x46, 0x3A, 0x02, 0x02, 0x3C, // 1339 - 0x40, 0x40, 0x40, 0x5C, 0x62, 0x42, 0x42, 0x42, 0x42, 0x42, 0x00, 0x00, 0x00, // 1352 - 0x18, 0x18, 0x00, 0x78, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x00, 0x00, 0x00, // 1365 - 0x18, 0x18, 0x00, 0x78, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x70, // 1378 - 0x40, 0x40, 0x40, 0x44, 0x48, 0x50, 0x60, 0x50, 0x48, 0x44, 0x00, 0x00, 0x00, // 1391 - 0x78, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x00, 0x00, 0x00, // 1404 - 0x00, 0x00, 0x00, 0xB6, 0xDA, 0x92, 0x92, 0x92, 0x92, 0x92, 0x00, 0x00, 0x00, // 1417 - 0x00, 0x00, 0x00, 0x5C, 0x62, 0x42, 0x42, 0x42, 0x42, 0x42, 0x00, 0x00, 0x00, // 1430 - 0x00, 0x00, 0x00, 0x3C, 0x42, 0x42, 0x42, 0x42, 0x42, 0x3C, 0x00, 0x00, 0x00, // 1443 - 0x00, 0x00, 0x00, 0x5C, 0x62, 0x42, 0x42, 0x42, 0x62, 0x5C, 0x40, 0x40, 0x40, // 1456 - 0x00, 0x00, 0x00, 0x3A, 0x46, 0x42, 0x42, 0x42, 0x46, 0x3A, 0x02, 0x02, 0x02, // 1469 - 0x00, 0x00, 0x00, 0x5C, 0x64, 0x40, 0x40, 0x40, 0x40, 0x40, 0x00, 0x00, 0x00, // 1482 - 0x00, 0x00, 0x00, 0x3C, 0x40, 0x60, 0x18, 0x04, 0x04, 0x78, 0x00, 0x00, 0x00, // 1495 - 0x00, 0x00, 0x20, 0xFC, 0x20, 0x20, 0x20, 0x20, 0x20, 0x1C, 0x00, 0x00, 0x00, // 1508 - 0x00, 0x00, 0x00, 0x42, 0x42, 0x42, 0x42, 0x42, 0x46, 0x3A, 0x00, 0x00, 0x00, // 1521 - 0x00, 0x00, 0x00, 0x82, 0x44, 0x44, 0x44, 0x28, 0x28, 0x10, 0x00, 0x00, 0x00, // 1534 - 0x00, 0x00, 0x00, 0x81, 0x91, 0x5A, 0x5A, 0x6A, 0x24, 0x24, 0x00, 0x00, 0x00, // 1547 - 0x00, 0x00, 0x00, 0x42, 0x24, 0x18, 0x18, 0x18, 0x24, 0x42, 0x00, 0x00, 0x00, // 1560 - 0x00, 0x00, 0x00, 0x81, 0x42, 0x42, 0x24, 0x24, 0x18, 0x18, 0x10, 0x30, 0xE0, // 1573 - 0x00, 0x00, 0x00, 0x7E, 0x02, 0x04, 0x08, 0x10, 0x20, 0x7E, 0x00, 0x00, 0x00, // 1586 - 0x1C, 0x10, 0x10, 0x10, 0x10, 0x60, 0x10, 0x10, 0x10, 0x10, 0x10, 0x0C, 0x00, // 1599 - 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x00, // 1612 - 0x30, 0x08, 0x08, 0x08, 0x08, 0x06, 0x08, 0x08, 0x08, 0x08, 0x08, 0x30, 0x00, // 1625 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x71, 0x8E, 0x00, 0x00, 0x00, 0x00, 0x00, // 1638 - 0x00, 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x3C, 0x00, 0x00, 0x00, // 1651 - 0x00, 0x00, 0x3E, 0x40, 0x80, 0x80, 0x80, 0x80, 0x40, 0x3E, 0x04, 0x02, 0x06, // 1664 - 0x00, 0x24, 0x00, 0x42, 0x42, 0x42, 0x42, 0x42, 0x46, 0x3A, 0x00, 0x00, 0x00, // 1677 - 0x08, 0x10, 0x00, 0x3C, 0x22, 0x42, 0x7E, 0x40, 0x40, 0x3E, 0x00, 0x00, 0x00, // 1690 - 0x18, 0x24, 0x00, 0x38, 0x04, 0x04, 0x3C, 0x44, 0x44, 0x3E, 0x00, 0x00, 0x00, // 1703 - 0x00, 0x24, 0x00, 0x38, 0x04, 0x04, 0x3C, 0x44, 0x44, 0x3E, 0x00, 0x00, 0x00, // 1716 - 0x10, 0x08, 0x00, 0x38, 0x04, 0x04, 0x3C, 0x44, 0x44, 0x3E, 0x00, 0x00, 0x00, // 1729 - 0x10, 0x28, 0x10, 0x38, 0x04, 0x04, 0x3C, 0x44, 0x44, 0x3E, 0x00, 0x00, 0x00, // 1742 - 0x00, 0x00, 0x00, 0x1E, 0x20, 0x40, 0x40, 0x40, 0x20, 0x1E, 0x08, 0x04, 0x0C, // 1755 - 0x18, 0x24, 0x00, 0x3C, 0x22, 0x42, 0x7E, 0x40, 0x40, 0x3E, 0x00, 0x00, 0x00, // 1768 - 0x00, 0x12, 0x00, 0x3C, 0x22, 0x42, 0x7E, 0x40, 0x40, 0x3E, 0x00, 0x00, 0x00, // 1781 - 0x10, 0x08, 0x00, 0x3C, 0x22, 0x42, 0x7E, 0x40, 0x40, 0x3E, 0x00, 0x00, 0x00, // 1794 - 0x00, 0x24, 0x00, 0x78, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x00, 0x00, 0x00, // 1807 - 0x18, 0x24, 0x00, 0x78, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x00, 0x00, 0x00, // 1820 - 0x10, 0x08, 0x00, 0x78, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x00, 0x00, 0x00, // 1833 - 0x24, 0x00, 0x18, 0x18, 0x24, 0x24, 0x24, 0x7E, 0x42, 0x81, 0x00, 0x00, 0x00, // 1846 - 0x10, 0x28, 0x10, 0x28, 0x28, 0x24, 0x44, 0x7E, 0x42, 0x81, 0x00, 0x00, 0x00, // 1859 - 0x08, 0x10, 0x7E, 0x40, 0x40, 0x40, 0x7C, 0x40, 0x40, 0x7E, 0x00, 0x00, 0x00, // 1872 - 0x00, 0x00, 0x00, 0xFC, 0x12, 0x12, 0x7E, 0x90, 0x90, 0x6E, 0x00, 0x00, 0x00, // 1885 - 0x00, 0x00, 0x0F, 0x18, 0x18, 0x28, 0x2E, 0x78, 0x48, 0x8F, 0x00, 0x00, 0x00, // 1898 - 0x18, 0x24, 0x00, 0x3C, 0x42, 0x42, 0x42, 0x42, 0x42, 0x3C, 0x00, 0x00, 0x00, // 1911 - 0x00, 0x24, 0x00, 0x3C, 0x42, 0x42, 0x42, 0x42, 0x42, 0x3C, 0x00, 0x00, 0x00, // 1924 - 0x20, 0x10, 0x00, 0x3C, 0x42, 0x42, 0x42, 0x42, 0x42, 0x3C, 0x00, 0x00, 0x00, // 1937 - 0x18, 0x24, 0x00, 0x42, 0x42, 0x42, 0x42, 0x42, 0x46, 0x3A, 0x00, 0x00, 0x00, // 1950 - 0x20, 0x10, 0x00, 0x42, 0x42, 0x42, 0x42, 0x42, 0x46, 0x3A, 0x00, 0x00, 0x00, // 1963 - 0x00, 0x24, 0x00, 0x81, 0x42, 0x42, 0x24, 0x24, 0x18, 0x18, 0x10, 0x30, 0xE0, // 1976 - 0x24, 0x00, 0x38, 0x44, 0x82, 0x82, 0x82, 0x82, 0x44, 0x38, 0x00, 0x00, 0x00, // 1989 - 0x24, 0x00, 0x42, 0x42, 0x42, 0x42, 0x42, 0x42, 0x42, 0x3C, 0x00, 0x00, 0x00, // 2002 - 0x00, 0x08, 0x1C, 0x28, 0x48, 0x48, 0x48, 0x68, 0x1C, 0x08, 0x00, 0x00, 0x00, // 2015 - 0x00, 0x0E, 0x10, 0x10, 0x10, 0x38, 0x10, 0x10, 0x20, 0x3E, 0x00, 0x00, 0x00, // 2028 - 0x00, 0x81, 0x42, 0x24, 0x18, 0x7C, 0x10, 0x7C, 0x10, 0x10, 0x00, 0x00, 0x00, // 2041 - 0x00, 0xE0, 0x90, 0x90, 0xE0, 0x96, 0xBC, 0x94, 0x92, 0x9E, 0x00, 0x00, 0x00, // 2054 - 0x0E, 0x10, 0x10, 0x3C, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0xE0, // 2067 - 0x08, 0x10, 0x00, 0x38, 0x04, 0x04, 0x3C, 0x44, 0x44, 0x3E, 0x00, 0x00, 0x00, // 2080 - 0x08, 0x10, 0x00, 0x78, 0x08, 0x08, 0x08, 0x08, 0x08, 0x08, 0x00, 0x00, 0x00, // 2093 - 0x08, 0x10, 0x00, 0x3C, 0x42, 0x42, 0x42, 0x42, 0x42, 0x3C, 0x00, 0x00, 0x00, // 2106 - 0x08, 0x10, 0x00, 0x42, 0x42, 0x42, 0x42, 0x42, 0x46, 0x3A, 0x00, 0x00, 0x00, // 2119 - 0x14, 0x28, 0x00, 0x5C, 0x62, 0x42, 0x42, 0x42, 0x42, 0x42, 0x00, 0x00, 0x00, // 2132 - 0x14, 0x28, 0x42, 0x62, 0x52, 0x52, 0x4A, 0x4A, 0x46, 0x42, 0x00, 0x00, 0x00, // 2145 - 0x00, 0x78, 0x08, 0x38, 0x48, 0x7C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 2158 - 0x00, 0x38, 0x44, 0x44, 0x44, 0x38, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 2171 - 0x00, 0x00, 0x00, 0x08, 0x00, 0x00, 0x08, 0x10, 0x20, 0x40, 0x42, 0x3E, 0x00, // 2184 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x7E, 0x40, 0x40, 0x00, 0x00, 0x00, 0x00, 0x00, // 2197 - 0x00, 0x00, 0x00, 0x00, 0x00, 0xFE, 0x02, 0x02, 0x00, 0x00, 0x00, 0x00, 0x00, // 2210 - 0x00, 0xC4, 0x48, 0x48, 0x50, 0x37, 0x21, 0x43, 0x44, 0x87, 0x00, 0x00, 0x00, // 2223 - 0x00, 0xC4, 0x48, 0x48, 0x50, 0x22, 0x26, 0x4A, 0x4F, 0x82, 0x00, 0x00, 0x00, // 2236 - 0x00, 0x00, 0x00, 0x10, 0x00, 0x00, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x00, // 2249 - 0x00, 0x00, 0x00, 0x00, 0x12, 0x24, 0x48, 0x24, 0x12, 0x00, 0x00, 0x00, 0x00, // 2262 - 0x00, 0x00, 0x00, 0x00, 0x48, 0x24, 0x12, 0x24, 0x48, 0x00, 0x00, 0x00, 0x00, // 2275 - 0x94, 0x00, 0x00, 0x94, 0x00, 0x94, 0x00, 0x00, 0x94, 0x00, 0x94, 0x00, 0x00, // 2288 - 0x49, 0x94, 0x00, 0x49, 0x94, 0x49, 0x00, 0x94, 0x49, 0x94, 0x49, 0x00, 0x94, // 2301 - 0xFF, 0x94, 0x94, 0xFF, 0x94, 0xFF, 0x94, 0x94, 0xFF, 0x94, 0xFF, 0x94, 0x94, // 2314 - 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, // 2327 - 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0xF0, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, // 2340 - 0x10, 0x10, 0x10, 0x10, 0x10, 0xF0, 0x10, 0xF0, 0x10, 0x10, 0x10, 0x10, 0x10, // 2353 - 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0xF4, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, // 2366 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFC, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, // 2379 - 0x00, 0x00, 0x00, 0x00, 0x00, 0xF0, 0x10, 0xF0, 0x10, 0x10, 0x10, 0x10, 0x10, // 2392 - 0x14, 0x14, 0x14, 0x14, 0x14, 0xF4, 0x04, 0xF4, 0x14, 0x14, 0x14, 0x14, 0x14, // 2405 - 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, // 2418 - 0x00, 0x00, 0x00, 0x00, 0x00, 0xFC, 0x04, 0xF4, 0x14, 0x14, 0x14, 0x14, 0x14, // 2431 - 0x14, 0x14, 0x14, 0x14, 0x14, 0xF4, 0x04, 0xFC, 0x00, 0x00, 0x00, 0x00, 0x00, // 2444 - 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0xFC, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 2457 - 0x10, 0x10, 0x10, 0x10, 0x10, 0xF0, 0x10, 0xF0, 0x00, 0x00, 0x00, 0x00, 0x00, // 2470 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xF0, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, // 2483 - 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x1F, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 2496 - 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 2509 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, // 2522 - 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x1F, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, // 2535 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 2548 - 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0xFF, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, // 2561 - 0x10, 0x10, 0x10, 0x10, 0x10, 0x1F, 0x10, 0x1F, 0x10, 0x10, 0x10, 0x10, 0x10, // 2574 - 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x17, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, // 2587 - 0x14, 0x14, 0x14, 0x14, 0x14, 0x17, 0x10, 0x1F, 0x00, 0x00, 0x00, 0x00, 0x00, // 2600 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x1F, 0x10, 0x17, 0x14, 0x14, 0x14, 0x14, 0x14, // 2613 - 0x14, 0x14, 0x14, 0x14, 0x14, 0xF7, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, // 2626 - 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x00, 0xF7, 0x14, 0x14, 0x14, 0x14, 0x14, // 2639 - 0x14, 0x14, 0x14, 0x14, 0x14, 0x17, 0x10, 0x17, 0x14, 0x14, 0x14, 0x14, 0x14, // 2652 - 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, // 2665 - 0x14, 0x14, 0x14, 0x14, 0x14, 0xF7, 0x00, 0xF7, 0x14, 0x14, 0x14, 0x14, 0x14, // 2678 - 0x10, 0x10, 0x10, 0x10, 0x10, 0xFF, 0x00, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, // 2691 - 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 2704 - 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x00, 0xFF, 0x10, 0x10, 0x10, 0x10, 0x10, // 2717 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, // 2730 - 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0x1F, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 2743 - 0x10, 0x10, 0x10, 0x10, 0x10, 0x1F, 0x10, 0x1F, 0x00, 0x00, 0x00, 0x00, 0x00, // 2756 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x1F, 0x10, 0x1F, 0x10, 0x10, 0x10, 0x10, 0x10, // 2769 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x1F, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, // 2782 - 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, 0xFF, 0x14, 0x14, 0x14, 0x14, 0x14, 0x14, // 2795 - 0x10, 0x10, 0x10, 0x10, 0x10, 0xFF, 0x10, 0xFF, 0x10, 0x10, 0x10, 0x10, 0x10, // 2808 - 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0xF0, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 2821 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x1F, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, // 2834 - 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, // 2847 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, // 2860 - 0xF0, 0xF0, 0xF0, 0xF0, 0xF0, 0xF0, 0xF0, 0xF0, 0xF0, 0xF0, 0xF0, 0xF0, 0xF0, // 2873 - 0x0F, 0x0F, 0x0F, 0x0F, 0x0F, 0x0F, 0x0F, 0x0F, 0x0F, 0x0F, 0x0F, 0x0F, 0x0F, // 2886 - 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 2899 - 0x00, 0x00, 0x00, 0x31, 0x49, 0x86, 0x84, 0x84, 0x8A, 0x71, 0x00, 0x00, 0x00, // 2912 - 0x38, 0x48, 0x48, 0x50, 0x50, 0x58, 0x44, 0x42, 0x42, 0x5C, 0x00, 0x00, 0x00, // 2925 - 0x00, 0x00, 0x3F, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x00, 0x00, 0x00, // 2938 - 0x00, 0x00, 0x00, 0x7F, 0x24, 0x24, 0x24, 0x24, 0x24, 0x24, 0x00, 0x00, 0x00, // 2951 - 0x00, 0x00, 0xFF, 0x40, 0x20, 0x10, 0x10, 0x20, 0x40, 0xFF, 0x00, 0x00, 0x00, // 2964 - 0x00, 0x00, 0x00, 0x7F, 0x84, 0x84, 0x84, 0x84, 0x84, 0x78, 0x00, 0x00, 0x00, // 2977 - 0x00, 0x00, 0x00, 0x42, 0x42, 0x42, 0x42, 0x42, 0x66, 0x5A, 0x40, 0x40, 0x40, // 2990 - 0x00, 0x00, 0x00, 0xFE, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x00, 0x00, 0x00, // 3003 - 0x00, 0x00, 0x10, 0x7C, 0x92, 0x92, 0x92, 0x92, 0x7C, 0x10, 0x00, 0x00, 0x00, // 3016 - 0x00, 0x00, 0x38, 0x44, 0x82, 0xBA, 0x82, 0x82, 0x44, 0x38, 0x00, 0x00, 0x00, // 3029 - 0x00, 0x00, 0x7C, 0xC6, 0x82, 0x82, 0x82, 0x84, 0x44, 0xEE, 0x00, 0x00, 0x00, // 3042 - 0x38, 0x40, 0x60, 0x18, 0x24, 0x42, 0x42, 0x42, 0x42, 0x3C, 0x00, 0x00, 0x00, // 3055 - 0x00, 0x00, 0x00, 0x00, 0x66, 0x99, 0x99, 0x99, 0x66, 0x00, 0x00, 0x00, 0x00, // 3068 - 0x10, 0x10, 0x10, 0x7C, 0x92, 0x91, 0x91, 0x91, 0x92, 0x7C, 0x10, 0x10, 0x10, // 3081 - 0x00, 0x00, 0x00, 0x1E, 0x20, 0x40, 0x7C, 0x40, 0x60, 0x1E, 0x00, 0x00, 0x00, // 3094 - 0x00, 0x00, 0x00, 0x38, 0x44, 0x82, 0x82, 0x82, 0x82, 0x82, 0x00, 0x00, 0x00, // 3107 - 0x00, 0x00, 0x00, 0x00, 0x7E, 0x00, 0x7E, 0x00, 0x7E, 0x00, 0x00, 0x00, 0x00, // 3120 - 0x00, 0x00, 0x00, 0x10, 0x10, 0xFE, 0x10, 0x10, 0x00, 0xFE, 0x00, 0x00, 0x00, // 3133 - 0x00, 0x00, 0x40, 0x30, 0x08, 0x06, 0x08, 0x30, 0x40, 0x00, 0x7E, 0x00, 0x00, // 3146 - 0x00, 0x00, 0x02, 0x0C, 0x10, 0x60, 0x10, 0x0C, 0x02, 0x00, 0x7E, 0x00, 0x00, // 3159 - 0x0C, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, // 3172 - 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x10, 0x60, // 3185 - 0x00, 0x00, 0x00, 0x10, 0x00, 0x00, 0xFE, 0x00, 0x00, 0x10, 0x00, 0x00, 0x00, // 3198 - 0x00, 0x00, 0x00, 0x00, 0x72, 0x4E, 0x00, 0x72, 0x4E, 0x00, 0x00, 0x00, 0x00, // 3211 - 0x00, 0x10, 0x28, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 3224 - 0x00, 0x00, 0x00, 0x00, 0x18, 0x3C, 0x3C, 0x18, 0x00, 0x00, 0x00, 0x00, 0x00, // 3237 - 0x00, 0x00, 0x00, 0x00, 0x18, 0x3C, 0x3C, 0x18, 0x00, 0x00, 0x00, 0x00, 0x00, // 3250 - 0x01, 0x01, 0x02, 0x02, 0x02, 0x04, 0x04, 0xC4, 0x28, 0x28, 0x18, 0x10, 0x00, // 3263 - 0x00, 0x3C, 0x24, 0x24, 0x24, 0x24, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 3276 - 0x00, 0x3C, 0x04, 0x18, 0x3C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // 3289 - 0x00, 0x00, 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, // 3302 - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 // 3315 -}; Modified: branches/olpc/drivers/base/bootvid/bootvid.c URL: http://svn.reactos.org/svn/reactos/branches/olpc/drivers/base/bootvid/bootv… ============================================================================== --- branches/olpc/drivers/base/bootvid/bootvid.c (original) +++ branches/olpc/drivers/base/bootvid/bootvid.c Fri Jun 15 14:58:37 2007 @@ -1,475 +1,290 @@ -#include "precomp.h" - -/* PRIVATE FUNCTIONS *********************************************************/ - -BOOLEAN -NTAPI -VgaInterpretCmdStream(IN PUSHORT CmdStream) -{ - PUCHAR Base = (PUCHAR)VgaRegisterBase; - USHORT Cmd; - UCHAR Major, Minor; - USHORT Count; - UCHAR Index; - PUSHORT Buffer; - PUSHORT ShortPort; - PUCHAR Port; - UCHAR Value; - USHORT ShortValue; - - /* First make sure that we have a Command Stream */ - if (!CmdStream) return TRUE; - - /* Loop as long as we have commands */ - while (*CmdStream) - { - /* Get the Major and Minor Function */ - Cmd = *CmdStream; - Major = Cmd & 0xF0; - Minor = Cmd & 0x0F; - - /* Move to the next command */ - CmdStream++; - - /* Check which major function this was */ - if (Major == 0x10) - { - /* Now let's see the minor function */ - if (Minor & CMD_STREAM_READ) - { - /* Now check the sub-type */ - if (Minor & CMD_STREAM_USHORT) - { - /* The port is what is in the stream right now */ - ShortPort = UlongToPtr((ULONG)*CmdStream); - - /* Move to the next command */ - CmdStream++; - - /* Read USHORT from the port */ - READ_PORT_USHORT(PtrToUlong(Base) + ShortPort); - } - else - { - /* The port is what is in the stream right now */ - Port = UlongToPtr((ULONG)*CmdStream); - - /* Move to the next command */ - CmdStream++; - - /* Read UCHAR from the port */ - READ_PORT_UCHAR(PtrToUlong(Base) + Port); - } - } - else if (Minor & CMD_STREAM_WRITE_ARRAY) - { - /* Now check the sub-type */ - if (Minor & CMD_STREAM_USHORT) - { - /* The port is what is in the stream right now */ - ShortPort = UlongToPtr(Cmd); - - /* Move to the next command and get the count */ - Count = *(CmdStream++); - - /* The buffer is what's next in the command stream */ - Buffer = CmdStream++; - - /* Write USHORT to the port */ - WRITE_PORT_BUFFER_USHORT(PtrToUshort(Base) + ShortPort, Buffer, Count); - - /* Move past the buffer in the command stream */ - CmdStream += Count; - } - else - { - /* The port is what is in the stream right now */ - Port = UlongToPtr(Cmd); - - /* Move to the next command and get the count */ - Count = *(CmdStream++); - - /* Add the base to the port */ - Port = PtrToUlong(Port) + Base; - - /* Move to next command */ - CmdStream++; - - /* Loop the cmd array */ - for (; Count; Count--, CmdStream++) - { - /* Get the byte we're writing */ - Value = (UCHAR)*CmdStream; - - /* Write UCHAR to the port */ - WRITE_PORT_UCHAR(Port, Value); - } - } - } - else if (Minor & CMD_STREAM_USHORT) - { - /* Get the ushort we're writing and advance in the stream */ - ShortValue = *CmdStream; - CmdStream++; - - /* Write USHORT to the port (which is in cmd) */ - WRITE_PORT_USHORT((PUSHORT)Base + Cmd, ShortValue); - } - else - { - /* The port is what is in the stream right now */ - Port = UlongToPtr((ULONG)*CmdStream); - - /* Get the uchar we're writing */ - Value = (UCHAR)*++CmdStream; - - /* Move to the next command */ - CmdStream++; - - /* Write UCHAR to the port (which is in cmd) */ - WRITE_PORT_UCHAR(PtrToUlong(Base) + Port, Value); - } - } - else if (Major == 0x20) - { - /* Check the minor function. Note these are not flags anymore. */ - switch (Minor) - { - case 0: - /* The port is what is in the stream right now */ - ShortPort = UlongToPtr(*CmdStream); - - /* Move to the next command and get the count */ - Count = *(CmdStream++); - - /* Move to the next command and get the value to write */ - ShortValue = *(CmdStream++); - - /* Add the base to the port */ - ShortPort = PtrToUlong(ShortPort) + (PUSHORT)Base; - - /* Move to next command */ - CmdStream++; - - /* Make sure we have data */ - if (!ShortValue) continue; - - /* Loop the cmd array */ - for (; Count; Count--, CmdStream++, Value++) - { - /* Get the byte we're writing */ - ShortValue += (*CmdStream) << 8; - - /* Write USHORT to the port */ - WRITE_PORT_USHORT(ShortPort, ShortValue); - } - break; - case 1: - /* The port is what is in the stream right now. Add the base too */ - Port = *CmdStream + Base; - - /* Move to the next command and get the count */ - Count = *++CmdStream; - - /* Move to the next command and get the index to write */ - Index = (UCHAR)*++CmdStream; - - /* Move to next command */ - CmdStream++; - - /* Loop the cmd array */ - for (; Count; Count--, Index++) - { - /* Write the index */ - WRITE_PORT_UCHAR(Port, Index); - - /* Get the byte we're writing */ - Value = (UCHAR)*CmdStream; - - /* Move to next command */ - CmdStream++; - - /* Write UCHAR value to the port */ - WRITE_PORT_UCHAR(Port, Value); - } - break; - case 2: - /* The port is what is in the stream right now. Add the base too */ - Port = *CmdStream + Base; - - /* Read the current value and add the stream data */ - Value = READ_PORT_UCHAR(Port); - Value &= *CmdStream++; - Value ^= *CmdStream++; - - /* Write the value */ - WRITE_PORT_UCHAR(Port, Value); - break; - default: - /* Unknown command, fail */ - return FALSE; - } - } - else if (Major != 0xF0) - { - /* Unknown major function, fail */ - return FALSE; - } - - /* Get the next command */ - Cmd = *CmdStream; - } - - /* If we got here, return success */ - return TRUE; -} - -BOOLEAN -NTAPI -VgaIsPresent(VOID) -{ - UCHAR VgaReg, VgaReg2, VgaReg3; - UCHAR SeqReg, SeqReg2; - UCHAR i; - - /* Read the VGA Address Register */ - VgaReg = READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE); - - /* Select Read Map Select Register */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE, 4); - - /* Read it back...it should be 4 */ - if (((READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE)) & 0xF) != 4) return FALSE; - - /* Read the VGA Data Register */ - VgaReg2 = READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF); - - /* Enable all planes */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, 3); - - /* Read it back...it should be 3 */ - if (READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF) != 0x3) - { - /* Reset the registers and fail */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, 0); - return FALSE; - } - - /* Select Bit Mask Register */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE, 8); - - /* Read it back...it should be 8 */ - if (((READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE)) & 0xF) != 8) - { - /* Reset the registers and fail */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE, 4); - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, 0); - return FALSE; - } - - /* Read the VGA Data Register */ - VgaReg3 = READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF); - - /* Loop bitmasks */ - for (i = 0xBB; i; i >>= 1) - { - /* Set bitmask */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, i); - - /* Read it back...it should be the same */ - if (READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF) != i) - { - /* Reset the registers and fail */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, 0xFF); - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE, 4); - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, 0); - return FALSE; - } - } - - /* Select Read Map Select Register */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE, 4); - - /* Read it back...it should be 3 */ - if (READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF) != 3) - { - /* Reset the registers and fail */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, 0); - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE, 8); - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, 0xFF); - return FALSE; - } - - /* Write the registers we read earlier */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, VgaReg); - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE, 8); - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, VgaReg2); - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE, VgaReg3); - - /* Read sequencer address */ - SeqReg = READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3C4); - - /* Select memory mode register */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3C4, 4); - - /* Read it back...it should still be 4 */ - if (((READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3C4)) & 7) != 4) - { - /* Fail */ - return FALSE; - } - - /* Read sequencer Data */ - SeqReg2 = READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3C5); - - /* Write null plane */ - WRITE_PORT_USHORT((PUSHORT)VgaRegisterBase + 0x3C4, 0x100); - - /* Write sequencer flag */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3C5, SeqReg2 ^ 8); - - /* Read it back */ - if ((READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3C5)) != (SeqReg2 ^ 8)) - { - /* Not the same value...restore registers and fail */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3C5, 2); - WRITE_PORT_USHORT((PUSHORT)VgaRegisterBase + 0x3C4, 0x300); - return FALSE; - } - - /* Now write the registers we read */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3C5, SeqReg2); - WRITE_PORT_USHORT((PUSHORT)VgaRegisterBase + 0x3C4, 0x300); - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3C4, SeqReg); - - /* VGA is present! */ - return TRUE; -} - -/* PUBLIC FUNCTIONS **********************************************************/ - /* - * @implemented + * ReactOS Boot video driver + * + * Copyright (C) 2003 Casper S. Hornstroup + * Copyright (C) 2004, 2005 Filip Navara + * + * This program is free software; you can redistribute it and/or + * modify it under the terms of the GNU General Public License + * as published by the Free Software Foundation; either version 2 + * of the License, or (at your option) any later version. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. + * + * $Id$ */ -BOOLEAN -NTAPI -VidInitialize(IN BOOLEAN SetMode) -{ - ULONG Context = 0; - PHYSICAL_ADDRESS TranslatedAddress; - PHYSICAL_ADDRESS NullAddress = {{0}}; - ULONG AddressSpace = 1; - BOOLEAN Result; - ULONG_PTR Base; - - /* Make sure that we have a bus translation function */ - if (!HalFindBusAddressTranslation) return FALSE; - - /* Get the VGA Register address */ - Result = HalFindBusAddressTranslation(NullAddress, - &AddressSpace, - &TranslatedAddress, - &Context, - TRUE); - if (!Result) return FALSE; - - /* See if this is I/O Space, which we need to map */ -TryAgain: - if (!AddressSpace) - { - /* Map it */ - Base = (ULONG_PTR)MmMapIoSpace(TranslatedAddress, 0x400, MmNonCached); - } - else - { - /* The base is the translated address, no need to map I/O space */ - Base = TranslatedAddress.LowPart; - } - - /* Set the VGA Register base and now check if we have a VGA device */ - VgaRegisterBase = Base; - if (VgaIsPresent()) - { - /* Translate the VGA Memory Address */ - NullAddress.LowPart = 0xA0000; - AddressSpace = 0; - Result = HalFindBusAddressTranslation(NullAddress, - &AddressSpace, - &TranslatedAddress, - &Context, - FALSE); - if (Result) - { - /* Success! See if this is I/O Space, which we need to map */ - if (!AddressSpace) - { - /* Map it */ - Base = (ULONG_PTR)MmMapIoSpace(TranslatedAddress, - 0x20000, - MmNonCached); - } - else - { - /* The base is the translated address, no need to map I/O space */ - Base = TranslatedAddress.LowPart; - } - - /* Set the VGA Memory Base */ - VgaBase = Base; - - /* Now check if we have to set the mode */ - if (SetMode) - { - // - // Reset the display - // - //HalResetDisplay(); - curr_x = 0; - curr_y = 0; - - /* Initialize it */ - VgaInterpretCmdStream(AT_Initialization); - return TRUE; - } - } - } - else - { - /* It's not, so unmap the I/O space if we mapped it */ - if (!AddressSpace) MmUnmapIoSpace((PVOID)VgaRegisterBase, 0x400); - } - - /* If we got here, then we failed...let's try again */ - Result = HalFindBusAddressTranslation(NullAddress, - &AddressSpace, - &TranslatedAddress, - &Context, - TRUE); - if (Result) goto TryAgain; - - /* If we got here, then we failed even past our re-try... */ - return FALSE; -} - -/* - * @implemented - */ -VOID -NTAPI -VidResetDisplay(IN BOOLEAN HalReset) -{ - /* Clear the current position */ - curr_x = 0; - curr_y = 0; - - /* Clear the screen with HAL if we were asked to */ - //if (HalReset) HalResetDisplay(); - - /* Re-initialize the VGA Display */ - VgaInterpretCmdStream(AT_Initialization); - - /* Re-initialize the palette and fill the screen black */ - InitializePalette(); - VidSolidColorFill(0, 0, 639, 479, 0); -} - + +/* INCLUDES ******************************************************************/ + +#include "bootvid.h" +#include "resource.h" + +#define NDEBUG +#include <debug.h> + +//#define USE_PROGRESS_BAR + +/* GLOBALS *******************************************************************/ + +static volatile LONG ShutdownNotify; +static KEVENT ShutdownCompleteEvent; + +/* DATA **********************************************************************/ + +static RGBQUAD _MainPalette[16]; +static UCHAR _Square1[9 * 4]; +static UCHAR _Square2[9 * 4]; +static UCHAR _Square3[9 * 4]; + +/* FUNCTIONS *****************************************************************/ + +static VOID NTAPI +BootVidAnimationThread(PVOID Ignored) +{ + UCHAR PaletteBitmapBuffer[sizeof(BITMAPINFOHEADER) + sizeof(_MainPalette)]; + PBITMAPINFOHEADER PaletteBitmap = (PBITMAPINFOHEADER)PaletteBitmapBuffer; + LPRGBQUAD Palette = (LPRGBQUAD)(PaletteBitmapBuffer + sizeof(BITMAPINFOHEADER)); + ULONG Iteration, Index, ClrUsed; + UINT AnimBarPos; + LARGE_INTEGER Interval; + + /* + * Build a bitmap containing the fade in palette. The palette entries + * are then processed in a loop and set using VidBitBlt function. + */ + + ClrUsed = sizeof(_MainPalette) / sizeof(_MainPalette[0]); + RtlZeroMemory(PaletteBitmap, sizeof(BITMAPINFOHEADER)); + PaletteBitmap->biSize = sizeof(BITMAPINFOHEADER); + PaletteBitmap->biBitCount = 4; + PaletteBitmap->biClrUsed = ClrUsed; + + /* + * Main animation loop. + */ + + for (Iteration = 0, AnimBarPos = 0; !ShutdownNotify; Iteration++) + { + if (Iteration <= PALETTE_FADE_STEPS) + { + for (Index = 0; Index < ClrUsed; Index++) + { + Palette[Index].rgbRed = + _MainPalette[Index].rgbRed * Iteration / PALETTE_FADE_STEPS; + Palette[Index].rgbGreen = + _MainPalette[Index].rgbGreen * Iteration / PALETTE_FADE_STEPS; + Palette[Index].rgbBlue = + _MainPalette[Index].rgbBlue * Iteration / PALETTE_FADE_STEPS; + } + + VidBitBlt(PaletteBitmapBuffer, 0, 0); + } +#ifdef USE_PROGRESS_BAR + else + { + break; + } + + Interval.QuadPart = -PALETTE_FADE_TIME; +#else + +#if 0 + if (AnimBarPos == 0) + { + VidSolidColorFill(0x173, 354, 0x178, 354 + 9, 0); + } + else if (AnimBarPos > 3) + { + VidSolidColorFill(0xe3 + AnimBarPos * 8, 354, + 0xe8 + AnimBarPos * 8, 354 + 9, + 0); + } + + if (AnimBarPos >= 3) + { + VidBufferToScreenBlt(_Square1, 0xeb + AnimBarPos * 8, 354, 6, 9, 4); + } + if (AnimBarPos >= 2 && AnimBarPos <= 16) + { + VidBufferToScreenBlt(_Square2, 0xf3 + AnimBarPos * 8, 354, 6, 9, 4); + } + if (AnimBarPos >= 1 && AnimBarPos <= 15) + { + VidBufferToScreenBlt(_Square3, 0xfb + AnimBarPos * 8, 354, 6, 9, 4); + } +#endif + + if (Iteration <= PALETTE_FADE_STEPS) + { + Interval.QuadPart = -PALETTE_FADE_TIME; + if ((Iteration % 5) == 0) + AnimBarPos++; + } + else + { + Interval.QuadPart = -PALETTE_FADE_TIME * 5; + AnimBarPos++; + } + AnimBarPos = Iteration % 18; +#endif + + /* Wait for a bit. */ + KeDelayExecutionThread(KernelMode, FALSE, &Interval); + } + + DPRINT("Finishing bootvid thread.\n"); + KeSetEvent(&ShutdownCompleteEvent, 0, FALSE); + + PsTerminateSystemThread(0); +} + + +NTSTATUS NTAPI +BootVidDisplayBootLogo(PVOID ImageBase) +{ + PBITMAPINFOHEADER BitmapInfoHeader; + LPRGBQUAD Palette; + static const ULONG BitmapIds[2] = {IDB_BOOTIMAGE, IDB_BAR}; + PUCHAR BitmapData[2]; + ULONG Index; + HANDLE BitmapThreadHandle; + CLIENT_ID BitmapThreadId; + NTSTATUS Status; + + KeInitializeEvent(&ShutdownCompleteEvent, NotificationEvent, FALSE); + + /* + * Get the bitmaps from the executable. + */ + + for (Index = 0; Index < sizeof(BitmapIds) / sizeof(BitmapIds[0]); Index++) + { + PIMAGE_RESOURCE_DATA_ENTRY ResourceDataEntry; + LDR_RESOURCE_INFO ResourceInfo; + ULONG Size; + + ResourceInfo.Type = /* RT_BITMAP */ 2; + ResourceInfo.Name = BitmapIds[Index]; + ResourceInfo.Language = 0x09; + + Status = LdrFindResource_U( + ImageBase, + &ResourceInfo, + RESOURCE_DATA_LEVEL, + &ResourceDataEntry); + + if (!NT_SUCCESS(Status)) + { + DPRINT("LdrFindResource_U() failed with status 0x%.08x\n", Status); + return Status; + } + + Status = LdrAccessResource( + ImageBase, + ResourceDataEntry, + (PVOID*)&BitmapData[Index], + &Size); + + if (!NT_SUCCESS(Status)) + { + DPRINT("LdrAccessResource() failed with status 0x%.08x\n", Status); + return Status; + } + } + + + /* + * Initialize the graphics output. + */ + + if (!VidInitialize(TRUE)) + { + return STATUS_UNSUCCESSFUL; + } + + /* + * Load the bar bitmap and get the square data from it. + */ + + VidBitBlt(BitmapData[1], 0, 0); + VidScreenToBufferBlt(_Square1, 0, 0, 6, 9, 4); + VidScreenToBufferBlt(_Square2, 8, 0, 6, 9, 4); + VidScreenToBufferBlt(_Square3, 16, 0, 6, 9, 4); + + /* + * Save the main image palette and replace it with black palette, so + * we can do fade in effect later. + */ + + BitmapInfoHeader = (PBITMAPINFOHEADER)BitmapData[0]; + Palette = (LPRGBQUAD)(BitmapData[0] + BitmapInfoHeader->biSize); + RtlCopyMemory(_MainPalette, Palette, sizeof(_MainPalette)); + RtlZeroMemory(Palette, sizeof(_MainPalette)); + + /* + * Display the main image. + */ + + VidBitBlt(BitmapData[0], 0, 0); + + /* + * Start a thread that handles the fade in and bar animation effects. + */ + + Status = PsCreateSystemThread( + &BitmapThreadHandle, + THREAD_ALL_ACCESS, + NULL, + NULL, + &BitmapThreadId, + BootVidAnimationThread, + NULL); + + if (!NT_SUCCESS(Status)) + { + VidCleanUp(); + return Status; + } + + ZwClose(BitmapThreadHandle); + + return STATUS_SUCCESS; +} + + +VOID NTAPI +BootVidUpdateProgress(ULONG Progress) +{ +#ifdef USE_PROGRESS_BAR + if (ShutdownNotify == 0) + { + VidSolidColorFill(0x103, 354, 0x103 + (Progress * 120 / 100), 354 + 9, 1); + } +#endif +} + + +VOID NTAPI +BootVidFinalizeBootLogo(VOID) +{ + InterlockedIncrement(&ShutdownNotify); + DPRINT1("Waiting for bootvid thread to finish.\n"); + KeWaitForSingleObject(&ShutdownCompleteEvent, Executive, KernelMode, + FALSE, NULL); + DPRINT1("Bootvid thread to finish.\n"); + //VidResetDisplay(); +} + + +NTSTATUS STDCALL +DriverEntry(PDRIVER_OBJECT DriverObject, PUNICODE_STRING RegistryPath) +{ + return STATUS_SUCCESS; +} Propchange: branches/olpc/drivers/base/bootvid/bootvid.c ------------------------------------------------------------------------------ --- svn:needs-lock (original) +++ svn:needs-lock (removed) @@ -1,1 +1,0 @@ -* Modified: branches/olpc/drivers/base/bootvid/bootvid.def URL: http://svn.reactos.org/svn/reactos/branches/olpc/drivers/base/bootvid/bootv… ============================================================================== --- branches/olpc/drivers/base/bootvid/bootvid.def (original) +++ branches/olpc/drivers/base/bootvid/bootvid.def Fri Jun 15 14:58:37 2007 @@ -1,15 +1,14 @@ -LIBRARY BOOTVID.DLL +LIBRARY bootvid.sys EXPORTS -VidBitBlt@12 -VidBufferToScreenBlt@24 -VidCleanUp@0 -VidDisplayString@4 -VidDisplayStringXY -VidInitialize@4 -VidResetDisplay@4 -VidScreenToBufferBlt@24 -VidSetScrollRegion@16 -VidSetTextColor@4 -VidSolidColorFill@20 - +VidInitialize +VidCleanUp +VidResetDisplay +VidBufferToScreenBlt +VidScreenToBufferBlt +VidBitBlt +VidSolidColorFill +VidDisplayString +BootVidDisplayBootLogo +BootVidUpdateProgress +BootVidFinalizeBootLogo Propchange: branches/olpc/drivers/base/bootvid/bootvid.def ------------------------------------------------------------------------------ --- svn:needs-lock (original) +++ svn:needs-lock (removed) @@ -1,1 +1,0 @@ -* Modified: branches/olpc/drivers/base/bootvid/bootvid.rbuild URL: http://svn.reactos.org/svn/reactos/branches/olpc/drivers/base/bootvid/bootv… ============================================================================== --- branches/olpc/drivers/base/bootvid/bootvid.rbuild (original) +++ branches/olpc/drivers/base/bootvid/bootvid.rbuild Fri Jun 15 14:58:37 2007 @@ -2,11 +2,13 @@ <importlibrary definition="bootvid.def"></importlibrary> <bootstrap base="$(CDOUTPUT)" nameoncd="bootvid.dll" /> <include base="bootvid">.</include> - <define name="__USE_W32API" /> + <define name="__USE_W32API" /> <library>ntoskrnl</library> <library>hal</library> <file>bootvid.c</file> - <file>bootdata.c</file> - <file>vga.c</file> + <file>vid.c</file> + <file>vid_vga.c</file> + <file>vid_vgatext.c</file> + <file>vid_xbox.c</file> <file>bootvid.rc</file> -</module> +</module> Propchange: branches/olpc/drivers/base/bootvid/bootvid.rbuild ------------------------------------------------------------------------------ --- svn:needs-lock (original) +++ svn:needs-lock (removed) @@ -1,1 +1,0 @@ -* Modified: branches/olpc/drivers/base/bootvid/bootvid.rc URL: http://svn.reactos.org/svn/reactos/branches/olpc/drivers/base/bootvid/bootv… ============================================================================== --- branches/olpc/drivers/base/bootvid/bootvid.rc (original) +++ branches/olpc/drivers/base/bootvid/bootvid.rc Fri Jun 15 14:58:37 2007 @@ -3,8 +3,12 @@ #include "resource.h" #define REACTOS_VERSION_DLL -#define REACTOS_STR_FILE_DESCRIPTION "VGA Boot Driver\0" -#define REACTOS_STR_INTERNAL_NAME "bootvid.dll\0" -#define REACTOS_STR_ORIGINAL_FILENAME "bootvid.dll\0" +#define REACTOS_STR_FILE_DESCRIPTION "ReactOS Boot Video\0" +#define REACTOS_STR_INTERNAL_NAME "bootvid\0" +#define REACTOS_STR_ORIGINAL_FILENAME "bootvid.sys\0" +#include <reactos/version.rc> -#include <reactos/version.rc> +IDB_BOOTIMAGE BITMAP DISCARDABLE "bootimage.bmp" +IDB_BAR BITMAP DISCARDABLE "bar.bmp" + + Propchange: branches/olpc/drivers/base/bootvid/bootvid.rc ------------------------------------------------------------------------------ --- svn:needs-lock (original) +++ svn:needs-lock (removed) @@ -1,1 +1,0 @@ -* Removed: branches/olpc/drivers/base/bootvid/precomp.h URL: http://svn.reactos.org/svn/reactos/branches/olpc/drivers/base/bootvid/preco… ============================================================================== --- branches/olpc/drivers/base/bootvid/precomp.h (original) +++ branches/olpc/drivers/base/bootvid/precomp.h (removed) @@ -1,46 +1,0 @@ -#include "ntddk.h" -#include "arc/arc.h" -#include "halfuncs.h" -#include "drivers/bootvid/bootvid.h" - -// -// Command Stream Definitions -// -#define CMD_STREAM_WRITE 0x0 -#define CMD_STREAM_WRITE_ARRAY 0x2 -#define CMD_STREAM_USHORT 0x4 -#define CMD_STREAM_READ 0x8 - -// -// Bitmap Header -// -typedef struct tagBITMAPINFOHEADER -{ - ULONG biSize; - LONG biWidth; - LONG biHeight; - USHORT biPlanes; - USHORT biBitCount; - ULONG biCompression; - ULONG biSizeImage; - LONG biXPelsPerMeter; - LONG biYPelsPerMeter; - ULONG biClrUsed; - ULONG biClrImportant; -} BITMAPINFOHEADER, *PBITMAPINFOHEADER; - -VOID -NTAPI -InitializePalette( - VOID -); - -// -// Globals -// -extern USHORT AT_Initialization[]; -extern ULONG curr_x; -extern ULONG curr_y; -extern ULONG_PTR VgaRegisterBase; -extern ULONG_PTR VgaBase; -extern UCHAR FontData[256 * 13]; Removed: branches/olpc/drivers/base/bootvid/vga.c URL: http://svn.reactos.org/svn/reactos/branches/olpc/drivers/base/bootvid/vga.c… ============================================================================== --- branches/olpc/drivers/base/bootvid/vga.c (original) +++ branches/olpc/drivers/base/bootvid/vga.c (removed) @@ -1,1274 +1,0 @@ -#include "precomp.h" - -/* GLOBALS *******************************************************************/ - -ULONG ScrollRegion[4] = -{ - 0, - 0, - 640 - 1, - 480 - 1 -}; -UCHAR lMaskTable[8] = -{ - (1 << 8) - (1 << 0), - (1 << 7) - (1 << 0), - (1 << 6) - (1 << 0), - (1 << 5) - (1 << 0), - (1 << 4) - (1 << 0), - (1 << 3) - (1 << 0), - (1 << 2) - (1 << 0), - (1 << 1) - (1 << 0) -}; -UCHAR rMaskTable[8] = -{ - (1 << 7), - (1 << 7)+ (1 << 6), - (1 << 7)+ (1 << 6) + (1 << 5), - (1 << 7)+ (1 << 6) + (1 << 5) + (1 << 4), - (1 << 7)+ (1 << 6) + (1 << 5) + (1 << 4) + (1 << 3), - (1 << 7)+ (1 << 6) + (1 << 5) + (1 << 4) + (1 << 3) + (1 << 2), - (1 << 7)+ (1 << 6) + (1 << 5) + (1 << 4) + (1 << 3) + (1 << 2) + (1 << 1), - (1 << 7)+ (1 << 6) + (1 << 5) + (1 << 4) + (1 << 3) + (1 << 2) + (1 << 1) + - (1 << 0), -}; -UCHAR PixelMask[8] = -{ - (1 << 7), - (1 << 6), - (1 << 5), - (1 << 4), - (1 << 3), - (1 << 2), - (1 << 1), - (1 << 0), -}; -ULONG lookup[16] = -{ - 0x0000, - 0x0100, - 0x1000, - 0x1100, - 0x0001, - 0x0101, - 0x1001, - 0x1101, - 0x0010, - 0x0110, - 0x1010, - 0x1110, - 0x0011, - 0x0111, - 0x1011, - 0x1111, -}; - -ULONG TextColor = 0xF; -ULONG curr_x = 0; -ULONG curr_y = 0; -BOOLEAN NextLine = FALSE; -ULONG_PTR VgaRegisterBase = 0; -ULONG_PTR VgaBase = 0; - -/* PRIVATE FUNCTIONS *********************************************************/ - -VOID -NTAPI -ReadWriteMode(UCHAR Mode) -{ - UCHAR Value; - - /* Switch to graphics mode register */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE, 5); - - /* Get the current register value, minus the current mode */ - Value = READ_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF) & 0xF4; - - /* Set the new mode */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, Mode | Value); -} - -VOID -NTAPI -__outpb(IN ULONG Port, - IN ULONG Value) -{ - /* Write to the VGA Register */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + Port, (UCHAR)Value); -} - -VOID -NTAPI -__outpw(IN ULONG Port, - IN ULONG Value) -{ - /* Write to the VGA Register */ - WRITE_PORT_USHORT((PUSHORT)(VgaRegisterBase + Port), (USHORT)Value); -} - -VOID -NTAPI -SetPixel(IN ULONG Left, - IN ULONG Top, - IN UCHAR Color) -{ - PUCHAR PixelPosition; - - /* Calculate the pixel position. */ - PixelPosition = (PUCHAR)VgaBase + (Left >> 3) + (Top * 80); - - /* Switch to mode 10 */ - ReadWriteMode(10); - - /* Clear the 4 planes (we're already in unchained mode here) */ - __outpw(0x3C4, 0xF02); - - /* Select the color don't care register */ - __outpw(0x3CE, 7); - - /* Select the bitmask register and write the mask */ - __outpw(0x3CE, (PixelMask[Left & 7] << 8) | 8); - - /* Read the current pixel value and add our color */ - WRITE_REGISTER_UCHAR(PixelPosition, - READ_REGISTER_UCHAR(PixelPosition) & Color); -} - -VOID -NTAPI -DisplayCharacter(CHAR Character, - ULONG Left, - ULONG Top, - ULONG TextColor, - ULONG BackTextColor) -{ - PUCHAR FontChar; - ULONG i, j, XOffset; - - /* Get the font line for this character */ - FontChar = &FontData[Character * 13 - Top]; - - /* Loop each pixel height */ - i = 13; - do - { - /* Loop each pixel width */ - j = 128; - XOffset = Left; - do - { - /* Check if we should draw this pixel */ - if (FontChar[Top] & (UCHAR)j) - { - /* We do, use the given Text Color */ - SetPixel(XOffset, Top, (UCHAR)TextColor); - } - else if (BackTextColor < 16) - { - /* This is a background pixel. We're drawing it unless it's */ - /* transparent. */ - SetPixel(XOffset, Top, (UCHAR)BackTextColor); - } - - /* Increase X Offset */ - XOffset++; - } while (j >>= 1); - - /* Move to the next Y ordinate */ - Top++; - } while (--i); -} - -VOID -NTAPI -DisplayStringXY(PUCHAR String, - ULONG Left, - ULONG Top, - ULONG TextColor, - ULONG BackColor) -{ - /* Loop every character */ - while (*String) - { - /* Display a character */ - DisplayCharacter(*String, Left, Top, TextColor, BackColor); - - /* Move to next character and next position */ - String++; - Left += 8; - } -} - -VOID -NTAPI -SetPaletteEntryRGB(IN ULONG Id, - IN ULONG Rgb) -{ - PCHAR Colors = (PCHAR)&Rgb; - - /* Set the palette index */ - __outpb(0x3C8, (UCHAR)Id); - - /* Set RGB colors */ - __outpb(0x3C9, Colors[2] >> 2); - __outpb(0x3C9, Colors[1] >> 2); - __outpb(0x3C9, Colors[0] >> 2); -} - -VOID -NTAPI -InitPaletteWithTable(IN PULONG Table, - IN ULONG Count) -{ - ULONG i; - PULONG Entry = Table; - - /* Loop every entry */ - for (i = 0; i < Count; i++, Entry++) - { - /* Set the entry */ - SetPaletteEntryRGB(i, *Entry); - } -} - -VOID -NTAPI -SetPaletteEntry(IN ULONG Id, - IN ULONG PaletteEntry) -{ - /* Set the palette index */ - __outpb(0x3C8, (UCHAR)Id); - - /* Set RGB colors */ - __outpb(0x3C9, PaletteEntry & 0xFF); - __outpb(0x3C9, (PaletteEntry >>= 8) & 0xFF); - __outpb(0x3C9, (PaletteEntry >> 8) & 0xFF); -} - -VOID -NTAPI -InitializePalette(VOID) -{ - ULONG PaletteEntry[16] = {0, - 0x20, - 0x2000, - 0x2020, - 0x200000, - 0x200020, - 0x202000, - 0x202020, - 0x303030, - 0x3F, - 0x3F00, - 0x3F3F, - 0x3F0000, - 0x3F003F, - 0x3F3F00, - 0x3F3F3F}; - ULONG i; - - /* Loop all the entries and set their palettes */ - for (i = 0; i < 16; i++) SetPaletteEntry(i, PaletteEntry[i]); -} - -VOID -NTAPI -VgaScroll(ULONG Scroll) -{ - ULONG Top; - ULONG SourceOffset, DestOffset; - ULONG Offset; - ULONG i, j; - - /* Set memory positions of the scroll */ - SourceOffset = VgaBase + (ScrollRegion[1] * 80) + (ScrollRegion[0] >> 3); - DestOffset = SourceOffset + (Scroll * 80); - - /* Clear the 4 planes */ - __outpw(0x3C4, 0xF02); - - /* Set the bitmask to 0xFF for all 4 planes */ - __outpw(0x3CE, 0xFF08); - - /* Set Mode 1 */ - ReadWriteMode(1); - - /* Save top and check if it's above the bottom */ - Top = ScrollRegion[1]; - if (Top > ScrollRegion[3]) return; - - /* Start loop */ - do - { - /* Set number of bytes to loop and start offset */ - Offset = ScrollRegion[0] >> 3; - j = SourceOffset; - - /* Check if this is part of the scroll region */ - if (Offset <= (ScrollRegion[2] >> 3)) - { - /* Update position */ - i = DestOffset - SourceOffset; - - /* Loop the X axis */ - do - { - /* Write value in the new position so that we can do the scroll */ - WRITE_REGISTER_UCHAR((PUCHAR)j, - READ_REGISTER_UCHAR((PUCHAR)j + i)); - - /* Move to the next memory location to write to */ - j++; - - /* Move to the next byte in the region */ - Offset++; - - /* Make sure we don't go past the scroll region */ - } while (Offset <= (ScrollRegion[2] >> 3)); - } - - /* Move to the next line */ - SourceOffset += 80; - DestOffset += 80; - - /* Increase top */ - Top++; - - /* Make sure we don't go past the scroll region */ - } while (Top <= ScrollRegion[3]); -} - -VOID -NTAPI -PreserveRow(IN ULONG CurrentTop, - IN ULONG TopDelta, - IN BOOLEAN Direction) -{ - PUCHAR Position1, Position2; - ULONG Count; - - /* Clear the 4 planes */ - __outpw(0x3C4, 0xF02); - - /* Set the bitmask to 0xFF for all 4 planes */ - __outpw(0x3CE, 0xFF08); - - /* Set Mode 1 */ - ReadWriteMode(1); - - /* Check which way we're preserving */ - if (Direction) - { - /* Calculate the position in memory for the row */ - Position1 = (PUCHAR)VgaBase + CurrentTop * 80; - Position2 = (PUCHAR)VgaBase + 0x9600; - } - else - { - /* Calculate the position in memory for the row */ - Position1 = (PUCHAR)VgaBase + 0x9600; - Position2 = (PUCHAR)VgaBase + CurrentTop * 80; - } - - /* Set the count and make sure it's above 0 */ - Count = TopDelta * 80; - if (Count) - { - /* Loop every pixel */ - do - { - /* Write the data back on the other position */ - WRITE_REGISTER_UCHAR(Position1, READ_REGISTER_UCHAR(Position2)); - - /* Increase both positions */ - Position2++; - Position1++; - } while (--Count); - } -} - -VOID -NTAPI -BitBlt(IN ULONG Left, - IN ULONG Top, - IN ULONG Width, - IN ULONG Height, - IN PUCHAR Buffer, - IN ULONG BitsPerPixel, - IN ULONG Delta) -{ - ULONG LeftAnd, LeftShifted, LeftPlusOne, LeftPos; - ULONG lMask, rMask; - UCHAR NotlMask; - ULONG Distance; - ULONG DistanceMinusLeftBpp; - ULONG SomeYesNoFlag, SomeYesNoFlag2; - PUCHAR PixelPosition, m; - PUCHAR i, k; - ULONG j; - ULONG x; - ULONG Plane; - UCHAR LeftArray[84]; - PUCHAR CurrentLeft; - PUCHAR l; - ULONG LoopCount; - UCHAR pMask, PlaneShift; - BOOLEAN Odd; - UCHAR Value; - - /* Check if the buffer isn't 4bpp */ - if (BitsPerPixel != 4) - { - /* FIXME: TODO */ - DbgPrint("Unhandled BitBlt\n" - "%lxx%lx @ (%lx,%lx)\n" - "Bits Per Pixel %lx\n" - "Buffer: %p. Delta: %lx\n", - Width, - Height, - Left, - Top, - BitsPerPixel, - Buffer, - Delta); - return; - } - - /* Get the masks and other values */ - LeftAnd = Left & 0x7; - lMask = lMaskTable[LeftAnd]; - Distance = Width + Left; - rMask = rMaskTable[(Distance - 1) & 0x7]; - Left >>= 3; - - /* Set some values */ - SomeYesNoFlag = FALSE; - SomeYesNoFlag2 = FALSE; - Distance = (Distance - 1) >> 3; - DistanceMinusLeftBpp = Distance - Left; - - /* Check if the distance is equal to the left position and add the masks */ - if (Left == Distance) lMask += rMask; - - /* Check if there's no distance offset */ - if (DistanceMinusLeftBpp) - { - /* Set the first flag on */ - SomeYesNoFlag = TRUE; - - /* Decrease offset and check if we still have one */ - if (--DistanceMinusLeftBpp) - { - /* Still have a distance offset */ - SomeYesNoFlag2 = TRUE; - } - } - - /* Calculate initial pixel position */ - PixelPosition = (PUCHAR)VgaBase + (Top * 80) + Left; - - /* Set loop buffer variable */ - i = Buffer; - - /* Switch to mode 0 */ - ReadWriteMode(0); - - /* Leave now if the height is 0 */ - if (Height <= 0) return; - - /* Set more weird values */ - CurrentLeft = &LeftArray[Left]; - NotlMask = ~(UCHAR)lMask; - LeftPlusOne = Left + 1; - LeftShifted = (lMask << 8) | 8; - j = Height; - - /* Start the height loop */ - do - { - /* Start the plane loop */ - Plane = 0; - do - { - /* Clear the current value */ - *CurrentLeft = 0; - LoopCount = 0; - - /* Set the buffer loop variable for this loop */ - k = i; - - /* Calculate plane shift and pixel mask */ - PlaneShift = 1 << Plane; - pMask = PixelMask[LeftAnd]; - - /* Check if we have a width */ - if (Width > 0) - { - /* Loop it */ - l = CurrentLeft; - x = Width; - do - { - /* Check if we're odd and increase the loop count */ - Odd = LoopCount & 1 ? TRUE : FALSE; - LoopCount++; - if (Odd) - { - /* Check for the plane shift */ - if (*k & PlaneShift) - { - /* Write the pixel mask */ - *l |= pMask; - } - - /* Increase buffer position */ - k++; - } - else - { - /* Check for plane shift */ - if ((*k >> 4) & PlaneShift) - { - /* Write the pixel mask */ - *l |= pMask; - } - } - - /* Shift the pixel mask */ - pMask >>= 1; - if (!pMask) - { - /* Move to the next current left position and clear it */ - l++; - *l = 0; - - /* Set the pixel mask to 0x80 */ - pMask = 0x80; - } - } while (--x); - } - - /* Set the plane value */ - __outpw(0x3C4, (1 << (Plane + 8) | 2)); - - /* Select the bitmask register and write the mask */ - __outpw(0x3CE, (USHORT)LeftShifted); - - /* Read the current Pixel value */ - Value = READ_REGISTER_UCHAR(PixelPosition); - - /* Add our mask */ - Value = (Value & NotlMask) | *CurrentLeft; - - /* Set current left for the loop, and write new pixel value */ - LeftPos = LeftPlusOne; - WRITE_REGISTER_UCHAR(PixelPosition, Value); - - /* Set loop pixel position and check if we should loop */ - m = PixelPosition + 1; - if (SomeYesNoFlag2) - { - /* Set the bitmask to 0xFF for all 4 planes */ - __outpw(0x3CE, 0xFF08); - - /* Check if we have any distance left */ - if (DistanceMinusLeftBpp > 0) - { - /* Start looping it */ - x = DistanceMinusLeftBpp; - do - { - /* Write the value */ - WRITE_REGISTER_UCHAR(m, LeftArray[LeftPos]); - - /* Go to the next position */ - m++; - LeftPos++; - } while (--x); - } - } - - /* Check if the first flag is on */ - if (SomeYesNoFlag) - { - /* Set the mask value */ - __outpw(0x3CE, (rMask << 8) | 8); - - /* Read the current Pixel value */ - Value = READ_REGISTER_UCHAR(m); - - /* Add our mask */ - Value = (Value & ~(UCHAR)rMask) | LeftArray[LeftPos]; - - /* Set current left for the loop, and write new pixel value */ - WRITE_REGISTER_UCHAR(m, Value); - } - } while (++Plane < 4); - - /* Update pixel position, buffer and height */ - PixelPosition += 80; - i += Delta; - } while (--j); -} - -VOID -NTAPI -RleBitBlt(IN ULONG Left, - IN ULONG Top, - IN ULONG Width, - IN ULONG Height, - IN PUCHAR Buffer) -{ - ULONG YDelta; - ULONG x; - ULONG RleValue, NewRleValue; - ULONG Color, Color2; - ULONG i, j; - ULONG Code; - - /* Set Y height and current X value and start loop */ - YDelta = Top + Height - 1; - x = Left; - for (;;) - { - /* Get the current value and advance in the buffer */ - RleValue = *Buffer; - Buffer++; - if (RleValue) - { - /* Check if we've gone past the edge */ - if ((x + RleValue) > (Width + Left)) - { - /* Fixeup the pixel value */ - RleValue = Left - x + Width; - } - - /* Get the new value */ - NewRleValue = *Buffer; - - /* Get the two colors */ - Color = NewRleValue >> 4; - Color2 = NewRleValue & 0xF; - - /* Increase buffer positition */ - Buffer++; - - /* Check if we need to do a fill */ - if (Color == Color2) - { - /* Do a fill and continue the loop */ - RleValue += x; - VidSolidColorFill(x, YDelta, RleValue - 1, YDelta, (UCHAR)Color); - x = RleValue; - continue; - } - - /* Check if the pixel value is 1 or below */ - if (RleValue > 1) - { - /* Set loop variables */ - i = (RleValue - 2) / 2 + 1; - do - { - /* Set the pixels */ - SetPixel(x, YDelta, (UCHAR)Color); - x++; - SetPixel(x, YDelta, (UCHAR)Color2); - x++; - - /* Decrease pixel value */ - RleValue -= 2; - } while (--i); - } - - /* Check if there is any value at all */ - if (RleValue) - { - /* Set the pixel and increase posititon */ - SetPixel(x, YDelta, (UCHAR)Color); - x++; - } - - /* Start over */ - continue; - } - - /* Get the current pixel value */ - RleValue = *Buffer; - Code = RleValue; - switch (Code) - { - /* Case 0 */ - case 0: - - /* Set new x value, decrease distance and restart */ - x = Left; - YDelta--; - Buffer++; - continue; - - /* Case 1 */ - case 1: - - /* Done */ - return; - - /* Case 2 */ - case 2: - - /* Set new x value, decrease distance and restart */ - Buffer++; - x += *Buffer; - Buffer++; - YDelta -= *Buffer; - Buffer++; - continue; - - /* Other values */ - default: - - Buffer++; - break; - } - - /* Check if we've gone past the edge */ - if ((x + RleValue) > (Width + Left)) - { - /* Set fixed up loop count */ - i = RleValue - Left - Width + x; - - /* Fixup pixel value */ - RleValue -= i; - } - else - { - /* Clear loop count */ - i = 0; - } - - /* Check the value now */ - if (RleValue > 1) - { - /* Set loop variables */ - j = (RleValue - 2) / 2 + 1; - do - { - /* Get the new value */ - NewRleValue = *Buffer; - - /* Get the two colors */ - Color = NewRleValue >> 4; - Color2 = NewRleValue & 0xF; - - /* Increase buffer position */ - Buffer++; - - /* Set the pixels */ - SetPixel(x, YDelta, (UCHAR)Color); - x++; - SetPixel(x, YDelta, (UCHAR)Color2); - x++; - - /* Decrease pixel value */ - RleValue -= 2; - } while (--j); - } - - /* Check if there is any value at all */ - if (RleValue) - { - /* Set the pixel and increase position */ - Color = *Buffer >> 4; - Buffer++; - SetPixel(x, YDelta, (UCHAR)Color); - x++; - i--; - } - - /* Check loop count now */ - if ((LONG)i > 0) - { - /* Decrease it */ - i--; - - /* Set new position */ - Buffer = Buffer + (i / 2) + 1; - } - - /* Check if we need to increase the buffer */ - if ((ULONG_PTR)Buffer & 1) Buffer++; - } -} - -/* PUBLIC FUNCTIONS **********************************************************/ - -/* - * @implemented - */ -ULONG -NTAPI -VidSetTextColor(ULONG Color) -{ - ULONG OldColor; - - /* Save the old color and set the new one */ - OldColor = TextColor; - TextColor = Color; - return OldColor; -} - -/* - * @implemented - */ -VOID -NTAPI -VidDisplayStringXY(PUCHAR String, - ULONG Left, - ULONG Top, - BOOLEAN Transparent) -{ - ULONG BackColor; - - /* If the caller wanted transparent, then send the special value (16), else */ - /* use our default and call the helper routine. */ - BackColor = (Transparent) ? 16 : 14; - DisplayStringXY(String, Left, Top, 12, BackColor); -} - -/* - * @implemented - */ -VOID -NTAPI -VidSetScrollRegion(ULONG x1, - ULONG y1, - ULONG x2, - ULONG y2) -{ - /* Assert alignment */ - ASSERT((x1 & 0x7) == 0); - ASSERT((x2 & 0x7) == 7); - - /* Set Scroll Region */ - ScrollRegion[0] = x1; - ScrollRegion[1] = y1; - ScrollRegion[2] = x2; - ScrollRegion[3] = y2; - - /* Set current X and Y */ - curr_x = x1; - curr_y = y1; -} - -/* - * @implemented - */ -VOID -NTAPI -VidCleanUp(VOID) -{ - /* Select bit mask register */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CE, 8); - - /* Clear it */ - WRITE_PORT_UCHAR((PUCHAR)VgaRegisterBase + 0x3CF, 255); -} - -/* - * @implemented - */ -VOID -NTAPI -VidBufferToScreenBlt(IN PUCHAR Buffer, - IN ULONG Left, - IN ULONG Top, - IN ULONG Width, - IN ULONG Height, - IN ULONG Delta) -{ - /* Make sure we have a width and height */ - if (!(Width) || !(Height)) return; - - /* Call the helper function */ - BitBlt(Left, Top, Width, Height, Buffer, 4, Delta); -} - -/* - * @implemented - */ -VOID -NTAPI -VidDisplayString(PUCHAR String) -{ - ULONG TopDelta = 14; - - /* Start looping the string */ - while (*String) - { - /* Treat new-line separately */ - if (*String == '\n') - { - /* Modify Y position */ - curr_y += TopDelta; - if (curr_y >= ScrollRegion[3]) - { - /* Scroll the view */ - VgaScroll(TopDelta); - curr_y -= TopDelta; - - /* Preserve row */ - PreserveRow(curr_y, TopDelta, TRUE); - } - - /* Update current X */ - curr_x = ScrollRegion[0]; - - /* Preseve the current row */ - PreserveRow(curr_y, TopDelta, FALSE); - } - else if (*String == '\r') - { - /* Update current X */ - curr_x = ScrollRegion[0]; - - /* Check if we're being followed by a new line */ - if (String[1] != '\n') NextLine = TRUE; - } - else - { - /* Check if we had a \n\r last time */ - if (NextLine) - { - /* We did, preserve the current row */ - PreserveRow(curr_y, TopDelta, TRUE); - NextLine = FALSE; - } - - /* Display this character */ - DisplayCharacter(*String, curr_x, curr_y, TextColor, 16); - curr_x += 8; - - /* Check if we should scroll */ - if (curr_x > ScrollRegion[2]) - { - /* Update Y position and check if we should scroll it */ - curr_y += TopDelta; - if (curr_y > ScrollRegion[3]) - { - /* Do the scroll */ - VgaScroll(TopDelta); - curr_y -= TopDelta; - - /* Save the row */ - PreserveRow(curr_y, TopDelta, TRUE); - } - - /* Update X */ - curr_x = ScrollRegion[0]; - } - } - - /* Get the next character */ - String++; - } -} - -/* - * @implemented - */ -VOID -NTAPI -VidBitBlt(PUCHAR Buffer, - ULONG Left, - ULONG Top) -{ - PBITMAPINFOHEADER BitmapInfoHeader; - LONG Delta; - PUCHAR BitmapOffset; - - /* Get the Bitmap Header */ - BitmapInfoHeader = (PBITMAPINFOHEADER)Buffer; - - /* Initialize the palette */ - InitPaletteWithTable((PULONG)(Buffer + BitmapInfoHeader->biSize), - (BitmapInfoHeader->biClrUsed) ? - BitmapInfoHeader->biClrUsed : 16); - - /* Make sure we can support this bitmap */ - ASSERT((BitmapInfoHeader->biBitCount * BitmapInfoHeader->biPlanes) <= 4); - - /* Calculate the delta and align it on 32-bytes, then calculate the actual */ - /* start of the bitmap data. */ - Delta = (BitmapInfoHeader->biBitCount * BitmapInfoHeader->biWidth) + 31; - Delta >>= 3; - Delta &= ~3; - BitmapOffset = Buffer + sizeof(BITMAPINFOHEADER) + 16 * sizeof(ULONG); - - /* Check the compression of the bitmap */ - if (BitmapInfoHeader->biCompression == 2) - { - /* Make sure we have a width and a height */ - if ((BitmapInfoHeader->biWidth) && (BitmapInfoHeader->biHeight)) - { - /* We can use RLE Bit Blt */ - RleBitBlt(Left, - Top, - BitmapInfoHeader->biWidth, - BitmapInfoHeader->biHeight, - BitmapOffset); - } - } - else - { - /* Check if the height is negative */ - if (BitmapInfoHeader->biHeight < 0) - { - /* Make it positive in the header */ - BitmapInfoHeader->biHeight *= -1; - } - else - { - /* Update buffer offset */ - BitmapOffset += ((BitmapInfoHeader->biHeight -1) * Delta); - Delta *= -1; - } - - /* Make sure we have a width and a height */ - if ((BitmapInfoHeader->biWidth) && (BitmapInfoHeader->biHeight)) - { - /* Do the BitBlt */ - BitBlt(Left, - Top, - BitmapInfoHeader->biWidth, - BitmapInfoHeader->biHeight, - BitmapOffset, - BitmapInfoHeader->biBitCount, - Delta); - } - } -} - -/* - * @implemented - */ -VOID -NTAPI -VidScreenToBufferBlt(PUCHAR Buffer, - ULONG Left, - ULONG Top, - ULONG Width, - ULONG Height, - ULONG Delta) -{ - ULONG Plane; - ULONG XDistance; - ULONG LeftDelta, RightDelta; - ULONG PixelOffset; - PUCHAR PixelPosition; - PUCHAR k, i; - PULONG m; - UCHAR Value, Value2; - UCHAR a; - ULONG b; - ULONG x, y; - - /* Calculate total distance to copy on X */ - XDistance = Left + Width - 1; - - /* Start at plane 0 */ - Plane = 0; - - /* Calculate the 8-byte left and right deltas */ - LeftDelta = Left & 7; - RightDelta = 8 - LeftDelta; - - /* Clear the destination buffer */ - RtlZeroMemory(Buffer, Delta * Height); - - /* Calculate the pixel offset and convert the X distance into byte form */ - PixelOffset = Top * 80 + (Left >> 3); - XDistance >>= 3; - - /* Loop the 4 planes */ - do - { - /* Set the current pixel position and reset buffer loop variable */ - PixelPosition = (PUCHAR)VgaBase + PixelOffset; - i = Buffer; - - /* Set Mode 0 */ - ReadWriteMode(0); - - /* Set the current plane */ - __outpw(0x3CE, (Plane << 8) | 4); - - /* Make sure we have a height */ - if (Height > 0) - { - /* Start the outer Y loop */ - y = Height; - do - { - /* Read the current value */ - m = (PULONG)i; - Value = READ_REGISTER_UCHAR(PixelPosition); - - /* Set Pixel Position loop variable */ - k = PixelPosition + 1; - - /* Check if we're still within bounds */ - if (Left <= XDistance) - { - /* Start X Inner loop */ - x = (XDistance - Left) + 1; - do - { - /* Read the current value */ - Value2 = READ_REGISTER_UCHAR(k); - - /* Increase pixel position */ - k++; - - /* Do the blt */ - a = Value2 >> (UCHAR)RightDelta; - a |= Value << (UCHAR)LeftDelta; - b = lookup[a & 0xF]; - a >>= 4; - b <<= 16; - b |= lookup[a]; - - /* Save new value to buffer */ - *m |= (b << Plane); - - /* Move to next destination location */ - m++; - - /* Write new value */ - Value = Value2; - } while (--x); - } - - /* Update pixel position */ - PixelPosition += 80; - i += Delta; - } while (--y); - } - } while (++Plane < 4); -} - -/* - * @implemented - */ -VOID -NTAPI -VidSolidColorFill(IN ULONG Left, - IN ULONG Top, - IN ULONG Right, - IN ULONG Bottom, - IN UCHAR Color) -{ - ULONG rMask, lMask; - ULONG LeftOffset, RightOffset, Distance; - PUCHAR Offset; - ULONG i, j; - - /* Get the left and right masks, shifts, and delta */ - LeftOffset = Left >> 3; - lMask = (lMaskTable[Left & 0x7] << 8) | 8; - RightOffset = Right >> 3; - rMask = (rMaskTable[Right & 0x7] << 8) | 8; - Distance = RightOffset - LeftOffset; - - /* If there is no distance, then combine the right and left masks */ - if (!Distance) lMask &= rMask; - - /* Switch to mode 10 */ - ReadWriteMode(10); - - /* Clear the 4 planes (we're already in unchained mode here) */ - __outpw(0x3C4, 0xF02); - - /* Select the color don't care register */ - __outpw(0x3CE, 7); - - /* Calculate pixel position for the read */ - Offset = VgaBase + (Top * 80) + (PUCHAR)LeftOffset; - - /* Select the bitmask register and write the mask */ - __outpw(0x3CE, (USHORT)lMask); - - /* Check if the top coord is below the bottom one */ - if (Top <= Bottom) - { - /* Start looping each line */ - i = (Bottom - Top) + 1; - do - { - /* Read the previous value and add our color */ - WRITE_REGISTER_UCHAR(Offset, READ_REGISTER_UCHAR(Offset) & Color); - - /* Move to the next line */ - Offset += 80; - } while (--i); - } - - /* Check if we have a delta */ - if (Distance) - { - /* Calculate new pixel position */ - Offset = VgaBase + (Top * 80) + (PUCHAR)RightOffset; - Distance--; - - /* Select the bitmask register and write the mask */ - __outpw(0x3CE, (USHORT)rMask); - - /* Check if the top coord is below the bottom one */ - if (Top <= Bottom) - { - /* Start looping each line */ - i = (Bottom - Top) + 1; - do - { - /* Read the previous value and add our color */ - WRITE_REGISTER_UCHAR(Offset, - READ_REGISTER_UCHAR(Offset) & Color); - - /* Move to the next line */ - Offset += 80; - } while (--i); - } - - /* Check if we still have a delta */ - if (Distance) - { - /* Calculate new pixel position */ - Offset = VgaBase + (Top * 80) + (PUCHAR)(LeftOffset + 1); - - /* Set the bitmask to 0xFF for all 4 planes */ - __outpw(0x3CE, 0xFF08); - - /* Check if the top coord is below the bottom one */ - if (Top <= Bottom) - { - /* Start looping each line */ - i = (Bottom - Top) + 1; - do - { - /* Loop the shift delta */ - if (Distance > 0) - { - for (j = Distance; j; Offset++, j--) - { - /* Write the color */ - WRITE_REGISTER_UCHAR(Offset, Color); - } - } - - /* Update position in memory */ - Offset += (80 - Distance); - } while (--i); - } - } - } -} -

3 2

Re: [ros-dev] [ros-diffs] [dgorbachev] 27187: Improve FIXME comment. For future generations of developers. :)
by Alex Ionescu 15 Jun '07

15 Jun '07

Is it really that hard to realize the line of code should've been: LdrEntry->SectionPointer = Section; -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of dgorbachev(a)svn.reactos.org Sent: Friday, June 15, 2007 5:12 AM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [dgorbachev] 27187: Improve FIXME comment. For future generations of developers. :) Author: dgorbachev Date: Fri Jun 15 16:11:48 2007 New Revision: 27187 URL: http://svn.reactos.org/svn/reactos?rev=27187&view=rev Log: Improve FIXME comment. For future generations of developers. :) Modified: trunk/reactos/ntoskrnl/mm/sysldr.c Modified: trunk/reactos/ntoskrnl/mm/sysldr.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/sysldr.c?rev=2… ============================================================================== --- trunk/reactos/ntoskrnl/mm/sysldr.c (original) +++ trunk/reactos/ntoskrnl/mm/sysldr.c Fri Jun 15 16:11:48 2007 @@ -1767,7 +1767,7 @@ NtHeader->OptionalHeader.AddressOfEntryPoint); LdrEntry->SizeOfImage = DriverSize; LdrEntry->CheckSum = NtHeader->OptionalHeader.CheckSum; - LdrEntry->SectionPointer = NULL; // ? + LdrEntry->SectionPointer = NULL; // FIXME: Bug 2151. /* Now write the DLL name */ LdrEntry->BaseDllName.Buffer = (PVOID)(LdrEntry + 1);

2 1

Re: [ros-dev] [ros-diffs] [fireball] 27186: - Resurrect "old" bootvid. The plan is to * make it working in trunk * add framebuffer support for olpc and xbox kind of devices.
by Aleksey Bragin 15 Jun '07

15 Jun '07

Are you allright, Alex? :-) This is in a branch, OLPC ("branches/olpc/"). I had to disable critical warnings in freeldr so I don't have to do a BIOS-less keyboard support in olpc-freeldr in order to just hit ENTER one time during the bootup. And certainly, when trunk's bootvid has VGA dependency coded into the very heart of it, I had to get old bootvid so that I could do the framebuffer support (no VGA bios in OLPC hardware). Also in that same branch. As for hto's (Dmitry) patches - there are controversial opinions, but I'm trying to review and discuss commits he is doing. WBR, Aleksey Bragin. On Jun 15, 2007, at 10:51 PM, Alex Ionescu wrote: > Screwing up compatibility continues! Here's an idea, let's rename > all the kernel exports! > > -----Original Message----- > From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs- > bounces(a)reactos.org] On Behalf Of fireball(a)svn.reactos.org > Sent: Friday, June 15, 2007 3:59 AM > To: ros-diffs(a)reactos.org > Subject: [ros-diffs] [fireball] 27186: - Resurrect "old" bootvid. > The plan is to * make it working in trunk * add framebuffer support > for olpc and xbox kind of devices. > > Author: fireball > Date: Fri Jun 15 14:58:37 2007 > New Revision: 27186 > > URL: http://svn.reactos.org/svn/reactos?rev=27186&view=rev > Log: > - Resurrect "old" bootvid. The plan is to > * make it working in trunk > * add framebuffer support for olpc and xbox kind of devices. > > Added: > branches/olpc/drivers/base/bootvid/bar.bmp

1 0

Re: [ros-dev] [ros-diffs] [fireball] 27185: - Set esp in the beginning to freeldr's stack, fixes a crash during a call to the kernel's entrypoint. - Comment out some annoying / unnecessary dprints (including messagebox about not resolved imports for pciide).
by Alex Ionescu 15 Jun '07

15 Jun '07

So the new ReactOS is all about adding hacks to the kernel and hiding existing bugs instead of finding solutions. Cool beans. Maybe you should also comment out other DPRINTs. I mean, if a critical warning that a driver wasn't properly loaded because FreeLDR doesn't process import tables and that thus the device won't work right is annoying, maybe stuff like "File not found" should also be removed and return success instead. I can't wait 6 months from now when everyone wonders how come some driver doesn't load in ReactOS. Are you and hto actually the same person? -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of fireball(a)svn.reactos.org Sent: Friday, June 15, 2007 3:27 AM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [fireball] 27185: - Set esp in the beginning to freeldr's stack, fixes a crash during a call to the kernel's entrypoint. - Comment out some annoying / unnecessary dprints (including messagebox about not resolved imports for pciide). Author: fireball Date: Fri Jun 15 14:27:27 2007 New Revision: 27185 URL: http://svn.reactos.org/svn/reactos?rev=27185&view=rev Log: - Set esp in the beginning to freeldr's stack, fixes a crash during a call to the kernel's entrypoint. - Comment out some annoying / unnecessary dprints (including messagebox about not resolved imports for pciide). Modified: branches/olpc/boot/freeldr/freeldr/arch/i386/arch.S branches/olpc/boot/freeldr/freeldr/arch/i386/loader.c branches/olpc/boot/freeldr/freeldr/arch/i386/macholpc.c Modified: branches/olpc/boot/freeldr/freeldr/arch/i386/arch.S URL: http://svn.reactos.org/svn/reactos/branches/olpc/boot/freeldr/freeldr/arch/… ============================================================================== --- branches/olpc/boot/freeldr/freeldr/arch/i386/arch.S (original) +++ branches/olpc/boot/freeldr/freeldr/arch/i386/arch.S Fri Jun 15 14:27:27 2007 @@ -395,7 +395,7 @@ //movw %dx,%fs //movw %dx,%gs //movw %dx,%ss - //movl $STACK32ADDR,%esp + movl $STACK32ADDR,%esp //movl $mb_info,%ebx /* See if the boot device was passed in */ Modified: branches/olpc/boot/freeldr/freeldr/arch/i386/loader.c URL: http://svn.reactos.org/svn/reactos/branches/olpc/boot/freeldr/freeldr/arch/… ============================================================================== --- branches/olpc/boot/freeldr/freeldr/arch/i386/loader.c (original) +++ branches/olpc/boot/freeldr/freeldr/arch/i386/loader.c Fri Jun 15 14:27:27 2007 @@ -487,7 +487,7 @@ } else { - DbgPrint("Don't yet support loading new modules from imports\n"); + //DbgPrint("Don't yet support loading new modules from imports\n"); Status = STATUS_NOT_IMPLEMENTED; } } Modified: branches/olpc/boot/freeldr/freeldr/arch/i386/macholpc.c URL: http://svn.reactos.org/svn/reactos/branches/olpc/boot/freeldr/freeldr/arch/… ============================================================================== --- branches/olpc/boot/freeldr/freeldr/arch/i386/macholpc.c (original) +++ branches/olpc/boot/freeldr/freeldr/arch/i386/macholpc.c Fri Jun 15 14:27:27 2007 @@ -253,7 +253,7 @@ BOOLEAN OlpcDiskGetDriveGeometry( ULONG DriveNumber, PGEOMETRY DriveGeometry ) { - ofwprintf("GetGeometry(%d)\n", DriveNumber); + //ofwprintf("GetGeometry(%d)\n", DriveNumber); DriveGeometry->BytesPerSector = 512; DriveGeometry->Heads = 16; DriveGeometry->Sectors = 63; @@ -262,7 +262,7 @@ ULONG OlpcDiskGetCacheableBlockCount( ULONG DriveNumber ) { - ofwprintf("GetCacheableBlockCount\n"); + //ofwprintf("GetCacheableBlockCount\n"); return 1; }

1 0

Re: [ros-dev] [ros-diffs] [dgorbachev] 27174: - Hackish solution of issue #2062. - Turn off title change, as it can cause a deadlock.
by Hervé Poussineau 15 Jun '07

15 Jun '07

Hi, > -----Message d'origine----- > De : ros-diffs-bounces(a)reactos.org > [mailto:ros-diffs-bounces@reactos.org] De la part de > dgorbachev(a)svn.reactos.org > Envoyé : jeudi 14 juin 2007 18:42 > À : ros-diffs(a)reactos.org > Objet : [ros-diffs] [dgorbachev] 27174: - Hackish solution of > issue #2062. - Turn off title change, as it can cause a deadlock. > > Author: dgorbachev > Date: Thu Jun 14 20:41:55 2007 > New Revision: 27174 > > URL: http://svn.reactos.org/svn/reactos?rev=27174&view=rev > Log: > - Hackish solution of issue #2062. > - Turn off title change, as it can cause a deadlock. > > Modified: > trunk/reactos/subsystems/win32/csrss/win32csr/conio.c > trunk/reactos/subsystems/win32/csrss/win32csr/dllmain.c > trunk/reactos/subsystems/win32/csrss/win32csr/guiconsole.c > Why hiding the real cause of bug 2062 by a hack, as you already did in r27107 for bug 2151? See desktop icons in explorer bar. They are not correct and I know when it appeared and I known how to hack a solution. But I won't do it because I don't want to hide the real problem. IMO, you should do the same thing and search the root problem or leave the effect visible, so it won't be forgotten. If you really need to add a hack in the code, please add a comment in the C code linking to bugzilla, and add a comment in BZ saying "hackish solution committed in rXXXXX" Hervé

2 1

(no subject)
by Cam 15 Jun '07

15 Jun '07

Way to go devs! Device manager finally works!

1 0

Re: [ros-dev] Smaller SVN REL ISO?
by carlo.bramix 11 Jun '07

11 Jun '07

Unfortunately, I'm not able to compile myself. So I download the SVN ISO images for testing. I was just wondering if it could be possible to reduce a bit my download times by including that flag into the REL builds. I also agree that it's better to leave the DEB builds without that flag. Thanks anyways, if it's not possible I can still download compressed ISO files at their current sizes. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Mon, 11 Jun 2007 14:28:37 +0400 Subject : Re: [ros-dev] Smaller SVN REL ISO? > It is possible to compile with this flag, but you need to build it > yourself then. Official ISOs are compiled with leanandmean set to no. > > > WBR, > Aleksey Bragin. > > On Jun 11, 2007, at 1:06 PM, carlo.bramix wrote: > > > Is the SVN REL Live CD compiled with "set ROS_LEAN_AND_MEAN = yes"? > > If not, is it possible to compile it with this flag? > > For other purposes beside the normal user testing, we have the SVN > > DEB Live CD image. > > > > Sincerely, > > > > LDChen > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

Re: [ros-dev] Smaller SVN REL ISO?
by Aleksey Bragin 11 Jun '07

11 Jun '07

It is possible to compile with this flag, but you need to build it yourself then. Official ISOs are compiled with leanandmean set to no. WBR, Aleksey Bragin. On Jun 11, 2007, at 1:06 PM, carlo.bramix wrote: > Is the SVN REL Live CD compiled with "set ROS_LEAN_AND_MEAN = yes"? > If not, is it possible to compile it with this flag? > For other purposes beside the normal user testing, we have the SVN > DEB Live CD image. > > Sincerely, > > LDChen

1 0

Smaller SVN REL ISO?
by carlo.bramix 11 Jun '07

11 Jun '07

Is the SVN REL Live CD compiled with "set ROS_LEAN_AND_MEAN = yes"? If not, is it possible to compile it with this flag? For other purposes beside the normal user testing, we have the SVN DEB Live CD image. Sincerely, LDChen ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

Re: [ros-dev] [ros-diffs] [dgorbachev] 27107: Fix issue #2151.
by Thomas Weidenmueller 11 Jun '07

11 Jun '07

Do you even know what you're doing? I've seen many commits where you call something a FIX and then just comment code out and add another FIXME.... dgorbachev(a)svn.reactos.org wrote: > Author: dgorbachev > Date: Sun Jun 10 15:11:05 2007 > New Revision: 27107 > > URL: http://svn.reactos.org/svn/reactos?rev=27107&view=rev > Log: > Fix issue #2151. > > Modified: > trunk/reactos/ntoskrnl/mm/sysldr.c > > Modified: trunk/reactos/ntoskrnl/mm/sysldr.c > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/sysldr.c?rev=2… > ============================================================================== > --- trunk/reactos/ntoskrnl/mm/sysldr.c (original) > +++ trunk/reactos/ntoskrnl/mm/sysldr.c Sun Jun 10 15:11:05 2007 > @@ -1767,7 +1767,7 @@ > NtHeader->OptionalHeader.AddressOfEntryPoint); > LdrEntry->SizeOfImage = DriverSize; > LdrEntry->CheckSum = NtHeader->OptionalHeader.CheckSum; > - LdrEntry->SectionPointer = LdrEntry; > + LdrEntry->SectionPointer = NULL; // ? > > /* Now write the DLL name */ > LdrEntry->BaseDllName.Buffer = (PVOID)(LdrEntry + 1); > > >

2 1

Re: [ros-dev] [ros-diffs] [dgorbachev] 26483: Undo r26482 change, waste more stack space.
by Alex Ionescu 07 Jun '07

07 Jun '07

Perhaps you could try convincing the GCC folks to actually properly support declspec_align like MSVC does, instead of claiming to support it, but actually ignoring it. Then you could also convince them to support SEH, PDBs, STDCALL-default calling convention, etc ;) -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of dgorbachev(a)svn.reactos.org Sent: April-24-07 1:06 AM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [dgorbachev] 26483: Undo r26482 change, waste more stack space. Author: dgorbachev Date: Tue Apr 24 09:05:49 2007 New Revision: 26483 URL: http://svn.reactos.org/svn/reactos?rev=26483&view=rev Log: Undo r26482 change, waste more stack space. Modified: trunk/reactos/ntoskrnl/include/internal/ex.h Modified: trunk/reactos/ntoskrnl/include/internal/ex.h URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/include/internal/… ============================================================================== --- trunk/reactos/ntoskrnl/include/internal/ex.h (original) +++ trunk/reactos/ntoskrnl/include/internal/ex.h Tue Apr 24 09:05:49 2007 @@ -106,9 +106,15 @@ // #ifdef __GNUC__ -#define DEFINE_WAIT_BLOCK(x) \ - PEX_PUSH_LOCK_WAIT_BLOCK x = __builtin_alloca(sizeof(EX_PUSH_LOCK_WAIT_BLOCK)); - +#define DEFINE_WAIT_BLOCK(x) \ + struct _AlignHack \ + { \ + UCHAR Hack[15]; \ + EX_PUSH_LOCK_WAIT_BLOCK UnalignedBlock; \ + } WaitBlockBuffer; \ + PEX_PUSH_LOCK_WAIT_BLOCK x = (PEX_PUSH_LOCK_WAIT_BLOCK) \ + ((ULONG_PTR)&WaitBlockBuffer.UnalignedBlock &~ 0xF); + #else // @@ -116,8 +122,8 @@ // local variable (the actual pointer) away, so we don't take any perf hit // by doing this. // -#define DEFINE_WAIT_BLOCK(x) \ - EX_PUSH_LOCK_WAIT_BLOCK WaitBlockBuffer; \ +#define DEFINE_WAIT_BLOCK(x) \ + EX_PUSH_LOCK_WAIT_BLOCK WaitBlockBuffer; \ PEX_PUSH_LOCK_WAIT_BLOCK x = &WaitBlockBuffer; #endif

11 19

Re: [ros-dev] About translation
by Aleksey 06 Jun '07

06 Jun '07

Hi Lucio, I must say, that there were a lot of efforts to get our tools working as easy as possible. Even a global login system was introduced way back so that you don't need to create an account for wiki, for bugzilla, for forum, for wiki, for the main website - you just create one. A lot of time was spent in order to do this (every piece of software needed to be customised - Ge and Klemens put a lot of their personal time into this). I will answer between the lines below so it makes better sense. ----- Original Message ----- From: "Lucio Diaz" <reactos_translate(a)yahoo.es> To: <ros-dev(a)reactos.org> Sent: Tuesday, April 17, 2007 2:08 AM Subject: [ros-dev] About translation -= skip =- > -Many like me can install SVN, and get the source > code, but never have made a patch, or even used > bugzilla(and probably wont have the time). If a contributor has SO small time that he can't even submit his work to a bugzilla or, at least, send a patch to a relevant person (the same language native speaker developer or another translator who has more time), then it's better to wait when he/she has more free time to contribute. -= skip =- > files, but sending them to bugzilla... i dont know how > to send them to bugzilla, i dont have a bugzilla > acount, it was tiring trying to find someone to send > the files, and i dont have the time or will to learn > bugzilla. That shows you really did not even slightly investigated how the website works. And instead you're proposing a whole workflow for developers, so they mandatory spent a few hours per week maintaining all the stuff you. During that 2 years you should have spent just a bit of time, even 20 minutes, to overview our website and systems we have there, and another 20 minutes to read online manuals/help for them. Excuses like "I didn't have time" hardly apply here. WBR, Aleksey Bragin.

3 2

RosBE Chatroom
by Daniel Reimer 29 May '07

29 May '07

Hi, I set up a Chatroom for RosBE (Windows/Linux) specific questions. Its on Freenode and is called #reactos-rosbe. I dont know if its so useful, but I was bored and thought this could be useful. Bye.

1 0

Re: [ros-dev] [ros-diffs] [dgorbachev] 26893: Do not free the string twice.
by Aleksey Bragin 25 May '07

25 May '07

Actually, I removed the hack from IopCreateDriver, and added a loop to prevent creation of drivers with the same name (which actually have no impact on the servicekeynode). What is the real cause of a double free? And which hack are you referring to in IopCreateDriver? WBR, Aleksey Bragin. On May 25, 2007, at 9:10 PM, dgorbachev(a)svn.reactos.org wrote: > Author: dgorbachev > Date: Fri May 25 21:10:11 2007 > New Revision: 26893 > > URL: http://svn.reactos.org/svn/reactos?rev=26893&view=rev > Log: > Do not free the string twice. > > Modified: > trunk/reactos/ntoskrnl/io/iomgr/driver.c > > Modified: trunk/reactos/ntoskrnl/io/iomgr/driver.c > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/ > iomgr/driver.c?rev=26893&r1=26892&r2=26893&view=diff > ====================================================================== > ======== > --- trunk/reactos/ntoskrnl/io/iomgr/driver.c (original) > +++ trunk/reactos/ntoskrnl/io/iomgr/driver.c Fri May 25 21:10:11 2007 > @@ -79,12 +79,14 @@ > ExFreePool(DriverObject->DriverName.Buffer); > } > > +#if 0 /* See a bit of hack in IopCreateDriver */ >

1 0

[ros-diffs] [jimtabor] 26877: - Fixed arithmetic semantics.
by jimtabor 24 May '07

24 May '07

Hi, Here is a test program. Thanks, James #include <stdio.h> #include <stdbool.h> #include <math.h> #include <float.h> //#define APIENTRY __stdcall #define APIENTRY //#define FASTCALL __fastcall #define FASTCALL #ifdef __GNUC__ #define FLOAT_TO_INT(in,out) \ __asm__ __volatile__ ("fistpl %0" : "=m" (out) : "t" (in) : "st"); #else #define FLOAT_TO_INT(in,out) \ __asm fld in \ __asm fistp out #endif /* the following deal with IEEE single-precision numbers */ #define EXCESS 126L #define SIGNBIT 0x80000000L #define SIGN(fp) ((fp) & SIGNBIT) #define EXP(fp) (((fp) >> 23L) & 0xFF) #define MANT(fp) ((fp) & 0x7FFFFFL) #define PACK(s,e,m) ((s) | ((e) << 23L) | (m)) typedef union // float_long { float f; unsigned long l; char c[4]; } gxf_long; #ifdef _X86_ typedef long FLOATL; #else /* !_X86_ */ typedef float FLOATL; #endif typedef struct _FLOATOBJ { unsigned long ul1; unsigned long ul2; } FLOATOBJ, *PFLOATOBJ; typedef struct _EFLOAT_S { long lMant; long lExp; } EFLOAT_S; //// //// void FASTCALL EF_Negate(EFLOAT_S * efp) { efp->lMant = -efp->lMant; } long FASTCALL EFtoF( EFLOAT_S * efp) { long Mant, Exp, Sign = 0; if (!efp->lMant) return 0; printf("EFtoF %x : %x\n", efp->lMant, efp->lExp); Mant = efp->lMant; Exp = efp->lExp; Sign = SIGN(efp->lMant); //// M$ storage emulation if( Sign ) Mant = -Mant; Mant = ((Mant & 0x3fffffff)>>7); Exp += (EXCESS-1); //// Mant = MANT(Mant); return PACK(Sign, Exp, Mant); } void FASTCALL FtoEF( EFLOAT_S * efp, FLOATL f) { long Mant, Exp, Sign = 0; gxf_long worker; printf("FtoEF\n"); #ifdef _X86_ worker.l = f; // It's a float stored in a long. #else worker.f = f; #endif Exp = EXP(worker.l); Mant = MANT(worker.l); if (SIGN(worker.l)) Sign = -1; //// M$ storage emulation Mant = ((Mant << 7) | 0x40000000); Mant ^= Sign; // invert/mask it Mant -= Sign; // sub it Exp -= (EXCESS-1); //// efp->lMant = Mant; efp->lExp = Exp; } void APIENTRY FLOATOBJ_Neg ( PFLOATOBJ pf ) { EFLOAT_S * efp = (EFLOAT_S *)pf; EF_Negate(efp); } long APIENTRY FLOATOBJ_GetFloat ( PFLOATOBJ pf ) { EFLOAT_S * efp = (EFLOAT_S *)pf; return EFtoF(efp); } void APIENTRY FLOATOBJ_SetFloat( PFLOATOBJ pf, FLOATL f ) { EFLOAT_S * efp = (EFLOAT_S *)pf; FtoEF( efp, f); } long APIENTRY FLOATOBJ_GetLong( PFLOATOBJ pf ) { EFLOAT_S * efp = (EFLOAT_S *)pf; gxf_long f; long l; f.l = EFtoF( efp ); FLOAT_TO_INT(f.f, l); // Let FPP handle it the fasty haxy way. return l; } void APIENTRY FLOATOBJ_SetLong( PFLOATOBJ pf, long l ) { EFLOAT_S * efp = (EFLOAT_S *)pf; gxf_long f; f.f = (float) l; // Convert it now. #ifdef _X86_ FtoEF( efp, f.l ); #else FtoEF( efp, f.f ); #endif } long FT_FixedFromFloat(float f) { short value = f; unsigned short fract = (f - value) * 0xFFFF; return (long)((long)value << 16 | (unsigned long)fract); } double F2F(PFLOATOBJ f) { printf("F2F --> %x : %x\n", f->ul1, f->ul2); if(SIGN(f->ul1)) // negate mant return (double) -(-f->ul1 * pow(2,(double)f->ul2-32)); else return (double) f->ul1 * pow(2,(double)f->ul2-32); } void Test_It(float fx) { FLOATOBJ pf; gxf_long f; f.f = fx; printf("Start 1 %f\n", f.f); printf(" 2 %x\n", f.l); #ifdef _X86_ FLOATOBJ_SetFloat( &pf, f.l ); #else FLOATOBJ_SetFloat( &pf, f.f ); #endif // FLOATOBJ_Neg ( &pf ); f.l = FLOATOBJ_GetFloat ( &pf ); printf("Fin 1 %f\n",f.f); printf("Fin 2 %x\n",f.l); printf("F2F --> %f\n\n",F2F( &pf )); } // // gcc -Os fpms.c -o f -lm // or // gcc -Os -D_X86_ fpms.c -o f -lm // main() { gxf_long f; f.f = 1.0; Test_It(f.f); f.f = -1.0; Test_It(f.f); f.f = 2.0; Test_It(f.f); f.f = -2.0; Test_It(f.f); f.f = 1.5; Test_It(f.f); f.f = -1.5; Test_It(f.f); f.f = 1235.0; Test_It(f.f); f.f = -1235.0; Test_It(f.f); f.f = 1235678.9; // Max it Test_It(f.f); f.f = -1235678.9; Test_It(f.f); }

1 0

Suggestion for making things a bit smaller
by carlo.bramix 23 May '07

23 May '07

When building the release versions of executables, DLLs, etc, I would suggest to add the "-s" switch to the linker flags. It will do stripping automatically and release-mode objects will be a bit smaller. Alternatively, we could "strip -s file.exe" but just adding the flag would be much simpler. Sincerely, Carlo Bramini. ------------------------------------------------------ Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom http://click.libero.it/infostrada

2 1

Re: [ros-dev] QEMU support broken!!!
by carlo.bramix 23 May '07

23 May '07

>From livecd-26861-rel it runs again under QEMU. Last tested image is livecd-26871-rel. Great job! Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ros-dev" ros-dev(a)reactos.org Cc : Date : Fri, 11 May 2007 17:21:55 +0200 Subject : Re: [ros-dev] QEMU support broken!!! > I just wanted to tell you that I downloaded and tested livecd-26700-rel.7z and it doesn't work yet. > > Sincerely, > > Carlo Bramini > > ---------- Initial Header ----------- > > >From : ros-dev-bounces(a)reactos.org > To : "ReactOS Development List" ros-dev(a)reactos.org > Cc : > Date : Fri, 11 May 2007 07:16:05 +0000 > Subject : Re: [ros-dev] QEMU support broken!!! > > > I also have a problem with booting LiveCD. > > Bugcheck in cmcontrl.c, line 151. > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > ------------------------------------------------------ > Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom > http://click.libero.it/infostrada > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom http://click.libero.it/infostrada

1 0

Re: [ros-dev] revision 26772, Mon May 14 03:18:42 2007 UTC
by jimtabor 23 May '07

23 May '07

Hi! > It should probably be > + Exp -= (1 - EXCESS); > in EFtoF() and > + Exp += (1 - EXCESS); > in FtoEF(). The other way round. > > No, this would break compatibility. The way to verify this. Write a driver, install it and send a packet to it, so to activate the test. Have the driver dump to WinDbg. > Suggestion to make it a little clearer: > #define BIAS 127 > Exp -+= (BIAS - 2); I know about the IEEE bias. I'm just using my old 68k code that I'm comfortable with. I'll change this later with the Dc handle stuff I'm still testing. Thanks, James

3 2

Re: [ros-dev] [ekohl] 26843: Update WIDL to rev 20070519.
by Aleksey Bragin 20 May '07

20 May '07

Hi, 2nd stage shows "Enable UsermodePnP failed", which doesn't appear with older WIDL. WBR, Aleksey Bragin. On May 20, 2007, at 3:02 AM, ekohl(a)svn.reactos.org wrote: > Author: ekohl > Date: Sun May 20 03:02:35 2007 > New Revision: 26843 > > URL: http://svn.reactos.org/svn/reactos?rev=26843&view=rev > Log: > Update WIDL to rev 20070519. >

1 0

Win32/Gdi32 Rewrite
by jimtabor 18 May '07

18 May '07

Hi all, On or about September 2006 I was asked by Aleksey (PC) and Alex if I could head up the win32 and gdi32 part of the rewrite. The discussion had taken place on irc. It was important that the rewrite would have one developer working alone (preferred method) or be the leading developer working with a small group of developers (no more than three). The rewrite was needed so that this section of ReactOS would be compatible with the new kernel and the very thing we are trying to do. Be compatible. This included interfaces, structures and the data that was contained in those structures. Just not only that, also dropping in the place of drivers and dlls, the real thing and still be compatible. Yes! Running with ReactOS. I do not recall any requirement for me to write a technical manual or any kind of web wiki. Even a How-To-Black-Box an OS interrupt calling hooky thingy with kmtest driver callback winpooch as an application interface. ReactOS developers should have a healthy tool box. This point on, the discussion is over. I have a job to do. I would like help and not debate everything I do. Some of you, need to, really think about, the future of this project. How can I help with this and how can I help make this work for compatibility with the very thing we are working toward. If you are thinking about something new and different other than something innovative, compatible and helpful? Maybe this project is not for you. Aros, FreeMint, Linux, Syllable, Visopsys, X, etc, these projects might be what you are looking for. If it breaks compatibility with interfaces and data stored in structures? I will reject it and post an email why it was rejected. Wine is not enough, okay? Thanks, James

1 0

revision 26772, Mon May 14 03:18:42 2007 UTC
by Timo Kreuzer 16 May '07

16 May '07

It should probably be + Exp -= (1 - EXCESS); in EFtoF() and + Exp += (1 - EXCESS); in FtoEF(). The other way round. Suggestion to make it a little clearer: #define BIAS 127 Exp -+= (BIAS - 2); jimtabor wrote: > --- trunk/reactos/dll/win32/gdi32/objects/painting.c 2006/12/28 22:36:53 25235 > +++ trunk/reactos/dll/win32/gdi32/objects/painting.c 2007/05/14 03:18:42 26772 > @@ -1,15 +1,66 @@ > [...] > +/* the following deal with IEEE single-precision numbers */ > +#define EXCESS 126L > +#define SIGNBIT 0x80000000L > +#define SIGN(fp) ((fp) & SIGNBIT) > +#define EXP(fp) (((fp) >> 23L) & 0xFF) > +#define MANT(fp) ((fp) & 0x7FFFFFL) > +#define PACK(s,e,m) ((s) | ((e) << 23L) | (m)) > [...] > +LONG > +FASTCALL > +EFtoF( EFLOAT_S * efp) > +{ > + long Mant, Exp, Sign = 0; > + > + if (!efp->lMant) return 0; > + > + Mant = efp->lMant; > + Exp = efp->lExp; > + Sign = SIGN(Mant); > + > +//// M$ storage emulation > + Mant = ((Mant & 0x3fffffff) >> 7); > + Exp += (1 - EXCESS); > +//// > + Mant = MANT(Mant); > + return PACK(Sign, Exp, Mant); > +} > + > +VOID > +FASTCALL > +FtoEF( EFLOAT_S * efp, FLOATL f) > +{ > + long Mant, Exp; > + gxf_long worker; > + > +#ifdef _X86_ > + worker.l = f; // It's a float stored in a long. > +#else > + worker.f = f; > +#endif > + > + Exp = EXP(worker.l); > + Mant = MANT(worker.l); > + > +//// M$ storage emulation > + Mant = ((Mant << 7) | 0x40000000 | SIGN(worker.l)); > + Exp -= (1 - EXCESS); > +//// > + efp->lMant = Mant; > + efp->lExp = Exp; > +} >

1 0

Re: [ros-dev] Bug into log10 function.
by carlo.bramix 16 May '07

16 May '07

Unfortunately, I just tested it into the latest working SVN build under QEMU (livecd-26665-rel) and this bug it is still into the CRT library. I also read the source code with SVN-WEB and it's still the same of 0.3.1. BTW, from livecd-26771-rel, a bad thing happens with QEMU: immediately after starting the boot, a blu screen appear with errors and everything is dead. Sincerely, Carlo Bramini ---------- This bug have already been fixed by me. log time ago. some time after 0.3.1 was relase or under 0.3.1 release process. plese use svn source code, and try make own build of reactos as well. the trunk is changes so fast, the code in 0.3.1 is already outdated in many areas. Citerar "carlo\\.bramix" <carlo.bramix at libero.it>: > While I was doing the final tests with ReactOS Calc before releasing the new > version, I discovered that it didn't work because a bug into log10 function. > This happens because the two operands are swapped into: > > \ReactOS-0.3.1\lib\crt\math\i386\log10_asm.s > > I attached the patch. > > Sincerely, > > Carlo Bramini. > > > > > ------------------------------------------------------ > Leggi GRATIS le tue mail con il telefonino i-mode di Wind > http://i-mode.wind.it/ > > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

1 0

Re: [ros-dev] Differences in Windows and Linux builds
by hto＠mail.cnt.ru 13 May '07

13 May '07

>> - At the boot screen, the version compiled under Windows shows >> "Service Pack 1" correctly, but the version compiled under Linux >> shows "Service Pac 1" > > I see this "Service Pac 1" in ReactOS compiled under Windows with GCC 4.1.2 (from RosBE). In ExpInitializeExecutive(): ... ANSI_STRING CsdString; ... RtlInitAnsiString(&CsdString, MsgEntry->Text); CsdString.Length -= sizeof(UNICODE_NULL); ... Why Unicode?

2 1

reactos.c compilation error
by Mikhail Y. Zvyozdochkin 13 May '07

13 May '07

Hi All Latest revisions of ReactOS produces compilation error at my system. Build Environment: RosBE 0.3.5b2 File: boot\freeldr\freeldr\reactos\reactos.c Error message (after 'make clean' and 'make'): cc1.exe: warnings being treated as errors boot\freeldr\freeldr\reactos\reactos.c: In function 'LoadAndBootReactOS': boot\freeldr\freeldr\reactos\reactos.c:524: warning: dereferencing type-punned pointer will break strict-aliasing rules mingw32-make: *** [obj-i386\boot\freeldr\freeldr\reactos\reactos.o] Error 1 WBR, DarkHobbit

1 0

tkreuzer r26742
by James Tabor 13 May '07

13 May '07

Sorry net split on irc. Physicus r26742 is right,,, I will change it this week once I have the rest of my changes ready. We should support 0x00010000 - 1 = 0xffff handles and it will give us 65K. Thanks James

1 0

Differences in Windows and Linux builds
by Colin Finck 12 May '07

12 May '07

Hello, After the latest Kernel changes, I noticed some differences in ReactOS builds compiled under Windows (RosBE 0.3.4) and under Linux (BuildBot and my 32-bit Ubuntu system): - At the boot screen, the version compiled under Windows shows "Service Pack 1" correctly, but the version compiled under Linux shows "Service Pac 1" - The version compiled under Linux hangs at "Flushing cache" for me, when I test it under VMware. Some other users also wrote that they could not run the latest ReactOS builds under QEMU. Although, I could not reproduce this problem with r26719, it might be related to these build differences. As I don't know, where this problem might originate from, maybe someone else could look at it. Regards, Colin

2 1

Re: [ros-dev] QEMU support broken!!!
by carlo.bramix 11 May '07

11 May '07

I just wanted to tell you that I downloaded and tested livecd-26700-rel.7z and it doesn't work yet. Sincerely, Carlo Bramini ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Fri, 11 May 2007 07:16:05 +0000 Subject : Re: [ros-dev] QEMU support broken!!! > I also have a problem with booting LiveCD. > Bugcheck in cmcontrl.c, line 151. > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom http://click.libero.it/infostrada

1 0

QEMU support broken!!!
by carlo.bramix 11 May '07

11 May '07

The last SVN builds don't run under qemu. The last working image is livecd-26665-rel.iso It looks like something wrong has been changed in the last 24 hours. Sincerely, Carlo Bramini. ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

3 2

Re: [ros-dev] QEMU support broken!!!
by carlo.bramix 10 May '07

10 May '07

Sorry, but before writing this messages I tested *ALL* SVN releases from livecd-26660-rel.7z to livecd-26672-rel.7z (except livecd-26671-rel.7z). I also tested livecd-26626-rel.7z and livecd-26650-rel.7z and they both worked (when I saw that livecd-26670-rel didn't work, I started with checking something older...). Here the last working version is still livecd-26665-rel.iso. Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Thu, 10 May 2007 17:43:22 +0400 Subject : Re: [ros-dev] QEMU support broken!!! > Hello, > the problem was introduced in 26666 and successfuly fixed in 26668 > (read commit logs for more details). > > > WBR, > Aleksey Bragin. > > On May 10, 2007, at 4:47 PM, carlo.bramix wrote: > > > The last SVN builds don't run under qemu. > > The last working image is livecd-26665-rel.iso > > It looks like something wrong has been changed in the last 24 hours. > > > > Sincerely, > > > > Carlo Bramini. > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

2 1

Re: [ros-dev] QEMU support broken!!!
by Aleksey Bragin 10 May '07

10 May '07

Hello, the problem was introduced in 26666 and successfuly fixed in 26668 (read commit logs for more details). WBR, Aleksey Bragin. On May 10, 2007, at 4:47 PM, carlo.bramix wrote: > The last SVN builds don't run under qemu. > The last working image is livecd-26665-rel.iso > It looks like something wrong has been changed in the last 24 hours. > > Sincerely, > > Carlo Bramini. >

1 0

Getting act together
by CK Raju 05 May '07

05 May '07

Wouldn't it be better if we got our act together from like minded groups. Crystalxp.net group's offering of Bricopacks http://www.crystalxp.net/bricopack/en.htm which mimics the look and feel of Vista. Is ReactOS ready for such an integration ? Plus, can this auditing be distributed and shared ? I have set up a group of volunteer professionals to work on ReactOS. CK Raju ros-dev-request(a)reactos.org wrote: Welcome to the Ros-dev(a)reactos.org mailing list! --------------------------------- Office firewalls, cyber cafes, college labs, don't allow you to download CHAT? Here's a solution!

2 1

Re : DbgPrint() - DPRINT() - DPRINT1()
by Sylvain Petreolle 03 May '07

03 May '07

Hi, You actually have to define YDEBUG to see messages produced by DPRINT() If NDEBUG is defined (default), no message is shown. DPRINT1 is used in case of error/ fix needed. Kind regards, Sylvain Petreolle (aka Usurp) --- --- --- --- --- --- --- --- --- --- --- --- --- Run your favorite Windows apps with free ReactOS : http://www.reactos.org Listen to non-DRMised Music: http://www.jamendo.com ----- Message d'origine ---- De : "breakoutbox(a)web.de" <breakoutbox(a)web.de> À : Ros-dev(a)reactos.org Envoyé le : Jeudi, 19 Avril 2007, 16h21mn 55s Objet : [ros-dev] DbgPrint() - DPRINT() - DPRINT1() Hello, can please anybody explain me how You want DbgPrint() - DPRINT() - DPRINT1() to be used ? I found a lot of DPRINT() _for_example_ in "win32/in32k/objects/dc.c" but it is not shown on serial debug (?) (and also SOME ot these DPRINT1() .. ) 1) If I use DPRINT1() instead, it is always shown. If I use DbgPrint() instead, it is only shown when #DEBUG is defined in the file + in *.rbuild But what's the sense of DPRINT() then ? => 2) 2nd stage: on installing from BootCD I can see serial debug only when I select DEBUG from startup options. Is this DPRINT1() suppressed when I DON'T select DEBUG ? 3) Why is there not one DbgPrint() in "win32/in32k/objects/dc.c" (and also in other files in /DRIVER/ and /NTOSKRNL/ ..) ? I now have to change every serial debug output to be able to see anything .. ( if You don't explain me ... ;-) ) Best regards, Peter. _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev

3 4

Re: [ros-dev] Bug into log10 function.
by carlo.bramix 03 May '07

03 May '07

Thank you for your reply. You are right, in theoury I should keep a copy of the sources at the same level of the ones into ReactOS's repository, and recompile a new version when something changed. Unfortunately, I cannot do it because my machine is an old Pentium MMX at 200MHz and 190 MB free into the harddisk. It is technically impossible for me to do that and my only chances are limited to the usage of a live CD or a QEMU session with a precompiled image. However, I'm happy that this small issue had been already tracked and solved! Sincerely, Carlo Bramini. ---------- Initial Header ----------- >From : ros-dev-bounces(a)reactos.org To : "ReactOS Development List" ros-dev(a)reactos.org Cc : Date : Tue, 1 May 2007 01:04:12 +0200 Subject : Re: [ros-dev] Bug into log10 function. > This bug have already been fixed by me. > log time ago. some time after 0.3.1 was relase or under 0.3.1 release process. > plese use svn source code, and try make own build of reactos as well. the trunk > is changes so fast, the code in 0.3.1 is already outdated in many areas. > > > > Citerar "carlo\\.bramix" <carlo.bramix(a)libero.it>: > > > While I was doing the final tests with ReactOS Calc before releasing the new > > version, I discovered that it didn't work because a bug into log10 function. > > This happens because the two operands are swapped into: > > > > \ReactOS-0.3.1\lib\crt\math\i386\log10_asm.s > > > > I attached the patch. > > > > Sincerely, > > > > Carlo Bramini. > > > > > > > > > > ------------------------------------------------------ > > Leggi GRATIS le tue mail con il telefonino i-mode di Wind > > http://i-mode.wind.it/ > > > > > > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

2 1

ReactOS 0.3.2- trunk feature-frozen!
by Aleksey Bragin 02 May '07

02 May '07

Hi, as I promised, it's time for a new release. But... After a quick analysis of the trunk, I found out following problems which block the release: 1. NPFS problem, leading to a non-working networking (and probably other problems related with PnP). 2. Regress of the VMWare's display driver support. 3. The command prompt doesn't work for some people, including me (see bug 2201). 4. Icons rendering problems (Ged said it could be hackfixed in a branch). Those 4 are quite important, and release is not going to happen if they are not fixed. !!I ATTENTION !! Dear ReactOS developers, having commit access! Those problems must be fixed as top priority, in trunk. We are not going to branch for a release and keep copying trunk commits into it, because those fundamental bugs must be fixed in trunk. So trunk is put into a frozen state now. Please commit *only* bugfixes, do not commit any new features, change something significantly without a reason, or any other kind of activity not aimed at fixing existing problems which prevent a scheduled release. Thank you for your understanding, WBR, Aleksey Bragin.

2 1

Notepad-Icon is from Windows Vista!
by theUser BL 01 May '07

01 May '07

Hi! Your actual ROS-Notepad Icons is absolutly the same like that on Windows-Vista. On March 2006 there was already something like that, there you used a WinXP-notepad-icon, what I sayd at http://www.reactos.org/pipermail/ros-dev/2006-March/007932.html The new icon, what you then choosed looks very like MS-Windows, but it wasn't a icon from Windows until WinXP. But now I have looked at Windows Vista (in a Virtual machine and on real hardware in an Internetcafé which I know) and there I see, that the ROS-notepad icon and the Windows-Vista Notepad icon are completely the same! But, existing at first the Vista icon or at first the ROS-icon??? What me wonder is, that the icon was in ROS before the first betas of Vista where out... And btw: For all the people who have still not seen Vista: It is the biggest crap I have ever seen. I hope ROS 1.0 looks more like WinXP then like Vista. - In Vista you can not run DOS-programs. But in C:\windows\system32 there are files like edit.com and edlin.exe. But if you want to run it, there comes a window: That there eixting a problem with this programs. If you want to continue or abort. If I choose contine, then Vista hangs up. - The german version of Windows have also the English-Filenames: C:\Program Files\ C:\User\ .. which you can easily see in the command-window (dos-box). but the Explorer shows for the user translated names like C:\Programme\ C:\Benutzer\ and there is a a possibility, if you are in such a directory to see in the address-field of the explorer the real directory name. But at first you see the wrong one. - The games like minesweeper wants D3D hardware-driver, to run fast enough. - the happy colors of XP don´t existing there. All is in black. Black here, black there. The only other look and feel is the look of Win2000. - The icons on the desktop are all very big, for me too big. In the explorer on the other side the icons are per default small, that you can´t see what a symbol it is ... 16x16 or so icons. - If you have a 64bit Windows you can not see, which programs are 32bit and whgich 64 bit. In the name it stand there if you run it. There stands in the "about"-window something like "I am a 64 bit window program". But you can also develop a 32bit window program, which says, that it is 64bit. You can not see, if it is right or not. With Linux - on the other side -, the command "file" do not show only information about the Linux-format files, if you have a 32bit or 64bit program, it shows also, if you have a 32bit or 64bit Windows *.exe file. Additional it says if the *.exe-file is completly of native-code (so, that WINE could run it for example), if it is completly .net-code (so that Mono could run it on Linux for example) or if it include native and .net code mixed like some developer do it with Visual C++.net / managed C++. There you can mix native and .net code and neither WINE nor Mono can run this files. The games of Vista are such files with mixed code. Windows XP is _much_ better then Windows Vista!! Greatings theuserbl _________________________________________________________________ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden!

4 3

Re: [ros-dev] [ros-diffs] [gedmurphy] 26616: quick hack to make sysdm.cpl open our standalone device manager it's a democracy : http://www.reactos.org/forum/viewtopic.php?t=3835
by Alex Ionescu 01 May '07

01 May '07

You don't run a software engineering project by user-based democracy. Doing that is called Microsoft. Listening to your developers and internal vision while ignoring users is called Apple. Which makes the more user-friendly product? Best regards, Alex Ionescu -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of gedmurphy(a)svn.reactos.org Sent: May-01-07 12:25 PM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [gedmurphy] 26616: quick hack to make sysdm.cpl open our standalone device manager it's a democracy : http://www.reactos.org/forum/viewtopic.php?t=3835 Author: gedmurphy Date: Tue May 1 20:25:26 2007 New Revision: 26616 URL: http://svn.reactos.org/svn/reactos?rev=26616&view=rev Log: quick hack to make sysdm.cpl open our standalone device manager it's a democracy : http://www.reactos.org/forum/viewtopic.php?t=3835 Modified: trunk/reactos/dll/cpl/sysdm/hardware.c Modified: trunk/reactos/dll/cpl/sysdm/hardware.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/cpl/sysdm/hardware.c?r… ============================================================================== --- trunk/reactos/dll/cpl/sysdm/hardware.c (original) +++ trunk/reactos/dll/cpl/sysdm/hardware.c Tue May 1 20:25:26 2007 @@ -14,6 +14,10 @@ BOOL LaunchDeviceManager(HWND hWndParent) { +/* hack for ROS to start our devmgmt until we have mmc */ +#ifdef __REACTOS__ + return ((INT)ShellExecuteW(NULL, L"open", L"devmgmt.exe", NULL, NULL, SW_SHOWNORMAL) > 32); +#else HMODULE hDll; PDEVMGREXEC DevMgrExec; BOOL Ret; @@ -33,6 +37,7 @@ Ret = DevMgrExec(hWndParent, hApplet, NULL /* ??? */, SW_SHOW); FreeLibrary(hDll); return Ret; +#endif /* __REACTOS__ */ } /* Property page dialog callback */

1 0

Re: [ros-dev] [ros-diffs] [dgorbachev] 26608: - Fix infinite loop. - Add debug msg.
by Alex Ionescu 01 May '07

01 May '07

You CANNOT return from PSEH! You must use SEH_LEAVE or the newest SHE construct that KJK added (forgot what he called it, check commit logs). -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of dgorbachev(a)svn.reactos.org Sent: May-01-07 4:53 AM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [dgorbachev] 26608: - Fix infinite loop. - Add debug msg. Author: dgorbachev Date: Tue May 1 12:52:59 2007 New Revision: 26608 URL: http://svn.reactos.org/svn/reactos?rev=26608&view=rev Log: - Fix infinite loop. - Add debug msg. Modified: trunk/reactos/ntoskrnl/ke/i386/exp.c Modified: trunk/reactos/ntoskrnl/ke/i386/exp.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/exp.c?rev… ============================================================================== --- trunk/reactos/ntoskrnl/ke/i386/exp.c (original) +++ trunk/reactos/ntoskrnl/ke/i386/exp.c Tue May 1 12:52:59 2007 @@ -980,7 +980,9 @@ /* Set EIP to the User-mode Dispatcher */ TrapFrame->Eip = (ULONG)KeUserExceptionDispatcher; - _SEH_LEAVE; + + /* Dispatch exception to user-mode */ + return; } _SEH_EXCEPT(KiCopyInformation) { @@ -1000,9 +1002,6 @@ } } _SEH_END; - - /* Dispatch exception to user-mode */ - return; } /* Try second chance */ @@ -1018,6 +1017,7 @@ } /* 3rd strike, kill the process */ + DPRINT1("Kill the process\n"); ZwTerminateProcess(NtCurrentProcess(), ExceptionRecord->ExceptionCode); KeBugCheckEx(KMODE_EXCEPTION_NOT_HANDLED, ExceptionRecord->ExceptionCode,

1 0

Bug into log10 function.
by carlo.bramix 30 Apr '07

30 Apr '07

While I was doing the final tests with ReactOS Calc before releasing the new version, I discovered that it didn't work because a bug into log10 function. This happens because the two operands are swapped into: \ReactOS-0.3.1\lib\crt\math\i386\log10_asm.s I attached the patch. Sincerely, Carlo Bramini. ------------------------------------------------------ Leggi GRATIS le tue mail con il telefonino i-mode di Wind http://i-mode.wind.it/

3 2

Uniform Driver Interface
by Jerry 30 Apr '07

30 Apr '07

http://udi.certek.cc/ >From what I can tell the example source code of this project is BSD (new). Should we add this driver interface to ReactOS? Why or why not? How could this be implemented while keeping compatibility with native NT drivers and not have it ROS specific?

1 0

Problem with out current NtGdiExtGetObjectW implementation
by Timo Kreuzer 30 Apr '07

30 Apr '07

Hi, although I like the way NtGdiExtGetObjectW is using the union, we will get a problem with it. We don't know how many styles an extpen has, so we cannot statically allocate a kmode buffer that is big enough. I can currently think of 3 possible solutions: 1. Add a big additional hack for GDI_OBJECT_TYPE_EXTPEN in NtGdiExtGetObjectW, that will copy the styles, wich seems to be a bad idea. 2. Use the old method of first calling IntGdiExtGetObjectW to get the needed buffer size then allocate a kernelmode buffer then call IntGdiExtGetObjectW again to tranfer the data then copy to usermode. This is slower and needs extra memory. 3. Move the copying to usermode to the XXX_GetObject functions. This would remove the need for an extra kernelmode buffer and we wouldn't really need IntGdiExtGetObjectW anymore. But it doesn't match the rest of our call chain design. Comments appreciated. Timo

4 5

CUnit
by theUser BL 29 Apr '07

29 Apr '07

Hi! Which testing-framefork do ReactOS use? I have seen, that CUnit for example outputs the result in a nice html-format: http://cunit.sourceforge.net/ss_automated.html Looks similar to the output of GNU Classpath (which trys to rewrite Java): http://builder.classpath.org/japi/jdk15-generics.html But GNU Classpath uses JUnit. And ReactOS is written in C, so in this case CUnit would be better. Existing for ReactOS also a side like this, where everytime stands, which test are passed and which not? Greatings theuserbl _________________________________________________________________ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden!

1 0

Re: [ros-dev] [ros-diffs] [tkreuzer] 26565: BRUSH_GetObject: - return sizeof(LOBRUSH) not BRUSHOBJ - don't return 0 on too small usermode buffer NtGdiExtGetObjectW: - remove unnecessary hacks - no need to align usermode buffer to words - add ENUMLOGFONTEXDVW, wich
by Alex Ionescu 29 Apr '07

29 Apr '07

Why did you randomly remove the hacks I added and call them useless? They're in Windows code, a checked GDI Server even prints out the size too big message! And why rename my variables? I don't really see the need to re-format code. -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of tkreuzer(a)svn.reactos.org Sent: April-28-07 5:53 PM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [tkreuzer] 26565: BRUSH_GetObject: - return sizeof(LOBRUSH) not BRUSHOBJ - don't return 0 on too small usermode buffer NtGdiExtGetObjectW: - remove unnecessary hacks - no need to align usermode buffer to words - add ENUMLOGFONTEXDVW, wich shou Author: tkreuzer Date: Sun Apr 29 01:53:06 2007 New Revision: 26565 URL: http://svn.reactos.org/svn/reactos?rev=26565&view=rev Log: BRUSH_GetObject: - return sizeof(LOBRUSH) not BRUSHOBJ - don't return 0 on too small usermode buffer NtGdiExtGetObjectW: - remove unnecessary hacks - no need to align usermode buffer to words - add ENUMLOGFONTEXDVW, wich should be the biggest structure needed more fixes for fonts and extpens needed in the corresponding subfunctions, but all of my other tests pass now. Modified: trunk/reactos/subsystems/win32/win32k/objects/brush.c trunk/reactos/subsystems/win32/win32k/objects/dc.c Modified: trunk/reactos/subsystems/win32/win32k/objects/brush.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/subsystems/win32/win32k/ob… ============================================================================== --- trunk/reactos/subsystems/win32/win32k/objects/brush.c (original) +++ trunk/reactos/subsystems/win32/win32k/objects/brush.c Sun Apr 29 01:53:06 2007 @@ -52,9 +52,8 @@ INT FASTCALL BRUSH_GetObject (PGDIBRUSHOBJ BrushObject, INT Count, LPLOGBRUSH Buffer) { - if( Buffer == NULL ) return sizeof(BRUSHOBJ); + if( Buffer == NULL ) return sizeof(LOGBRUSH); if (Count == 0) return 0; - if ((UINT)Count < sizeof(BRUSHOBJ)) return 0; /* Set colour */ Buffer->lbColor = BrushObject->BrushAttr.lbColor; @@ -106,7 +105,7 @@ */ /* FIXME */ - return sizeof(BRUSHOBJ); + return sizeof(LOGBRUSH); } Modified: trunk/reactos/subsystems/win32/win32k/objects/dc.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/subsystems/win32/win32k/ob… ============================================================================== --- trunk/reactos/subsystems/win32/win32k/objects/dc.c (original) +++ trunk/reactos/subsystems/win32/win32k/objects/dc.c Sun Apr 29 01:53:06 2007 @@ -1817,92 +1817,44 @@ OUT LPVOID lpBuffer) { INT iRetCount = 0; - INT iObjectType; - INT cbRealCount = cbCount; + INT cbCopyCount; union { - BITMAP bmpObject; - DIBSECTION disObject; - LOGPEN lgpObject; - LOGBRUSH lgbObject; - LOGFONTW lgfObject; - EXTLOGFONTW elgfObject; + BITMAP bitmap; + DIBSECTION dibsection; + LOGPEN logpen; + LOGBRUSH logbrush; + LOGFONTW logfontw; + EXTLOGFONTW extlogfontw; + ENUMLOGFONTEXDVW enumlogfontexdvw; } Object; - // - // Get the object type - // - iObjectType = GDIOBJ_GetObjectType(hGdiObj); - - // - // Check if the given size is too large - // - if (cbCount > sizeof(Object)) - { - // - // Normalize to the largest supported object size - // - DPRINT1("cbCount too big!\n"); - cbCount = sizeof(Object); - } - - // - // Check if this is a brush - // - if (iObjectType == GDI_OBJECT_TYPE_BRUSH) - { - // - // Windows GDI Hack: Manually correct the size - // - cbCount = sizeof(LOGBRUSH); - } - - // + // Normalize to the largest supported object size + cbCount = min((UINT)cbCount, sizeof(Object)); + // Now do the actual call - // iRetCount = IntGdiGetObject(hGdiObj, cbCount, lpBuffer ? &Object : NULL); - - // - // Check if this is a brush - // - if (iObjectType == GDI_OBJECT_TYPE_BRUSH) - { - // - // Fixup the size to account for our previous fixup - // - cbCount = min(cbCount, cbRealCount); - } - - // - // Make sure we have a buffer and a return size - // - if ((iRetCount) && (lpBuffer)) - { - // + cbCopyCount = min((UINT)cbCount, (UINT)iRetCount); + + // Make sure we have a buffer and a copy size + if ((cbCopyCount) && (lpBuffer)) + { // Enter SEH for buffer transfer - // _SEH_TRY { - // // Probe the buffer and copy it - // - ProbeForWrite(lpBuffer, min(cbCount, cbRealCount), sizeof(WORD)); - RtlCopyMemory(lpBuffer, &Object, min(cbCount, cbRealCount)); + ProbeForWrite(lpBuffer, cbCopyCount, 1); + RtlCopyMemory(lpBuffer, &Object, cbCopyCount); } _SEH_HANDLE { - // // Clear the return value. // Do *NOT* set last error here! - // iRetCount = 0; } _SEH_END; } - - // // Return the count - // return iRetCount; }

1 0

[ros-diffs] [tkreuzer] 26564: GetNonFontObject: - OBJECTTYPE_META_DC does not SetLastError() - beautify the code a little
by James Tabor 29 Apr '07

29 Apr '07

Hi! switch(dwType) { + case GDI_OBJECT_TYPE_PEN: //Check the structures and see if A & W are the same. + case GDI_OBJECT_TYPE_EXTPEN: + case GDI_OBJECT_TYPE_BRUSH: // Mixing Apples and Oranges? + case GDI_OBJECT_TYPE_BITMAP: + case GDI_OBJECT_TYPE_PALETTE: + return NtGdiExtGetObjectW(hGdiObj, cbSize, lpBuffer); + case GDI_OBJECT_TYPE_DC: case GDI_OBJECT_TYPE_REGION: case GDI_OBJECT_TYPE_METAFILE: case GDI_OBJECT_TYPE_ENHMETAFILE: case GDI_OBJECT_TYPE_EMF: - case GDI_OBJECT_TYPE_METADC: SetLastError(ERROR_INVALID_HANDLE); - return 0; This is wrong,,, you can not call NtGdiExtGetObjectW first before faulting on GDI_OBJECT_TYPE_DC. http://msdn2.microsoft.com/en-us/library/ms533268.aspx Normal DC's do not pass to kernel space. Please RTFM. Thanks, James

3 5

Re: [ros-dev] [ros-diffs] [tkreuzer] 26559: winetsts build fix - add needed #includes to test.h - add windef.h including psdk/windef.h
by Steven Edwards 29 Apr '07

29 Apr '07

Why can't use change the include path to use the normal windef.h? On 4/28/07, tkreuzer(a)svn.reactos.org <tkreuzer(a)svn.reactos.org> wrote: > Author: tkreuzer > Date: Sat Apr 28 12:58:18 2007 > New Revision: 26559 > > URL: http://svn.reactos.org/svn/reactos?rev=26559&view=rev > Log: > winetsts build fix > - add needed #includes to test.h > - add windef.h including psdk/windef.h > > Added: > trunk/reactos/include/reactos/wine/windef.h > Modified: > trunk/reactos/include/reactos/wine/test.h > > Modified: trunk/reactos/include/reactos/wine/test.h > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/include/reactos/wine/test.… > ============================================================================== > --- trunk/reactos/include/reactos/wine/test.h (original) > +++ trunk/reactos/include/reactos/wine/test.h Sat Apr 28 12:58:18 2007 > @@ -25,6 +25,8 @@ > #include <stdlib.h> > #include <windef.h> > #include <winbase.h> > +#include <wingdi.h> > +#include <winreg.h> > > #ifdef __WINE_WINE_LIBRARY_H > #error wine/library.h should not be used in Wine tests > > Added: trunk/reactos/include/reactos/wine/windef.h > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/include/reactos/wine/winde… > ============================================================================== > --- trunk/reactos/include/reactos/wine/windef.h (added) > +++ trunk/reactos/include/reactos/wine/windef.h Sat Apr 28 12:58:18 2007 > @@ -1,0 +1,3 @@ > +#include "../../psdk/windef.h" > + > + > > > -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo

2 1

Re: [ros-dev] [ros-diffs] [dgorbachev] 26555: Patch by Sbs (sbarthes [at] gmail [dot] com). Bugzilla report #2137.
by Aleksey 28 Apr '07

28 Apr '07

----- Original Message ----- From: <dgorbachev(a)svn.reactos.org> To: <ros-diffs(a)reactos.org> Sent: Saturday, April 28, 2007 8:02 AM Subject: [ros-diffs] [dgorbachev] 26555: Patch by Sbs (sbarthes [at] gmail [dot] com). Bugzilla report #2137. > Author: dgorbachev > Date: Sat Apr 28 10:02:22 2007 > New Revision: 26555 > > URL: http://svn.reactos.org/svn/reactos?rev=26555&view=rev > Log: > Patch by Sbs (sbarthes [at] gmail [dot] com). Bugzilla report #2137. > - _stprintf(Text, _T("%d%%"), (int)CpuUsage); > + wsprintf(Text, _T("%d%%"), (int)CpuUsage); Is this a correct change? IIRC, I talked with some dev (hpoussin?) about this, and he said those changes shouldn't be done. WBR, Aleksey Bragin.

3 2

Re: [ros-dev] [ros-diffs] [gedmurphy] 26541: - add support for .ocx files to rbuild - update project to VS2005
by Aleksey 27 Apr '07

27 Apr '07

----- Original Message ----- From: <gedmurphy(a)svn.reactos.org> To: <ros-diffs(a)reactos.org> Sent: Friday, April 27, 2007 5:18 PM Subject: [ros-diffs] [gedmurphy] 26541: - add support for .ocx files to rbuild - update project to VS2005 > Author: gedmurphy > Date: Fri Apr 27 19:18:34 2007 > New Revision: 26541 > > - update project to VS2005 I think it was specifically kept at low version, since autoconverting from old version to the new one can always be done, but "downgrading" the project file back to e.g. VS2003 is not guaranteed to be straight forward. WBR, Aleksey Bragin.

4 4

Re: [ros-dev] [ros-diffs] [arty] 26531: A perversely delightful hack to make hives of either BE or LE.
by Thomas Weidenmueller 27 Apr '07

27 Apr '07

C++ code in C code?! arty(a)svn.reactos.org wrote: > Modified: branches/powerpc/reactos/tools/mkhive/binhive.c > URL: http://svn.reactos.org/svn/reactos/branches/powerpc/reactos/tools/mkhive/bi… > ============================================================================== > --- branches/powerpc/reactos/tools/mkhive/binhive.c (original) > +++ branches/powerpc/reactos/tools/mkhive/binhive.c Fri Apr 27 09:48:13 2007 > @@ -35,6 +35,7 @@ > #include "binhive.h" > #include "registry.h" > > +using namespace ReactosBytesex; > > #define REG_HIVE_ID 0x66676572 > #define REG_BIN_ID 0x6e696268

1 0

Re: [ros-dev] Help ReactOS localize
by Aleksey 26 Apr '07

26 Apr '07

Hello Andranik, you have to find at least one more native Armenian language person, so you can proof-read each other's translation before submitting to ReactOS. Also, are you sure you have necessary english language skills to be able to translate all stuff correctly? As for keyboard layout - yes, you're welcome to implement the corresponding .dll for it, if it's missing. WBR, Aleksey. ----- Original Message ----- From: Andranik Haroyan To: ros-dev(a)reactos.org Sent: Thursday, April 26, 2007 8:46 AM Subject: [ros-dev] Help ReactOS localize Hi everybody I am beginner programmer from Armenia. One week ago I found alternative for MS Windows and sow ReactOS in http://www.reactos.org. I downloaded RO3.0.0 and tried. I think it is very interesting but I cant find in ReactOS Armenian support. Now I am download source and wont to localize it into Armenia. I am changing something in ( \boot\bootdata\hivesys.inf, hivecls.inf, hivesft.inf ) and write keyboard layout for Armenian language but after compile I sow it did not enough. If anybody have some help or some else documentation about localize please help me. Thanks respect Andranik Haroyan.

1 0

Help ReactOS localize
by Andranik Haroyan 26 Apr '07

26 Apr '07

Hi everybody I am beginner programmer from Armenia. One week ago I found alternative for MS Windows and sow ReactOS in http://www.reactos.org. I downloaded RO3.0.0 and tried. I think it is very interesting but I cant find in ReactOS Armenian support. Now I am download source and wont to localize it into Armenia. I am changing something in ( \boot\bootdata\hivesys.inf, hivecls.inf, hivesft.inf ) and write keyboard layout for Armenian language but after compile I sow it did not enough. If anybody have some help or some else documentation about localize please help me. Thanks respect Andranik Haroyan. --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos.

1 0

Re: [ros-dev] [ros-diffs] [dgorbachev] 26483: Undo r26482 change, waste more stack space.
by Aleksey 24 Apr '07

24 Apr '07

----- Original Message ----- From: "Alex Ionescu" <ionucu(a)videotron.ca> To: <ros-dev(a)reactos.org> Sent: Tuesday, April 24, 2007 7:44 AM Subject: Re: [ros-dev] [ros-diffs] [dgorbachev] 26483: Undo r26482 change,waste more stack space. > Perhaps you could try convincing the GCC folks to actually properly > support declspec_align like MSVC does, instead of claiming to support it, > but actually ignoring it. Then you could also convince them to support > SEH, PDBs, STDCALL-default calling convention, etc ;) Speaking of PDB, there is a person who is doing a PDB generator from the debug info gcc generates (No idea whether he's subscribed to this llist, probably not). But it looks like he's having some progress. The tool will be file rossym, but the output will not be an embedded rsym section, but a .pdb file [hopefully] readable by WinDBG. WBR, Aleksey Bragin.

1 0

Re: [ros-dev] [ros-diffs] [dgorbachev] 26482: Use allocation function instead of hack, save 12 bytes.
by Thomas Weidenmueller 24 Apr '07

24 Apr '07

This change is *wrong*. It won't guarantee the correct alignment!!! - Thomas dgorbachev(a)svn.reactos.org wrote: > Author: dgorbachev > Date: Tue Apr 24 02:06:34 2007 > New Revision: 26482 > > URL: http://svn.reactos.org/svn/reactos?rev=26482&view=rev > Log: > Use allocation function instead of hack, save 12 bytes. > > Modified: > trunk/reactos/ntoskrnl/include/internal/ex.h > > Modified: trunk/reactos/ntoskrnl/include/internal/ex.h > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/include/internal/… > ============================================================================== > --- trunk/reactos/ntoskrnl/include/internal/ex.h (original) > +++ trunk/reactos/ntoskrnl/include/internal/ex.h Tue Apr 24 02:06:34 2007 > @@ -102,22 +102,13 @@ > #define MAX_HIGH_INDEX (MID_LEVEL_ENTRIES * MID_LEVEL_ENTRIES * LOW_LEVEL_ENTRIES) > > // > -// Detect GCC 4.1.2+ > +// Detect GCC > // > -#if 1 // (__GNUC__ * 10000 + __GNUC_MINOR__ * 100 + __GNUC_PATCHLEVEL__) < 40102 > - > -// > -// Broken GCC with Alignment Bug. We'll do alignment ourselves at higher cost. > -// > -#define DEFINE_WAIT_BLOCK(x) \ > - struct _AlignHack \ > - { \ > - UCHAR Hack[15]; \ > - EX_PUSH_LOCK_WAIT_BLOCK UnalignedBlock; \ > - } WaitBlockBuffer; \ > - PEX_PUSH_LOCK_WAIT_BLOCK x = (PEX_PUSH_LOCK_WAIT_BLOCK) \ > - ((ULONG_PTR)&WaitBlockBuffer.UnalignedBlock &~ 0xF); > - > +#ifdef __GNUC__ > + > +#define DEFINE_WAIT_BLOCK(x) \ > + PEX_PUSH_LOCK_WAIT_BLOCK x = __builtin_alloca(sizeof(EX_PUSH_LOCK_WAIT_BLOCK)); > + > #else > > // > @@ -125,8 +116,8 @@ > // local variable (the actual pointer) away, so we don't take any perf hit > // by doing this. > // > -#define DEFINE_WAIT_BLOCK(x) \ > - EX_PUSH_LOCK_WAIT_BLOCK WaitBlockBuffer; \ > +#define DEFINE_WAIT_BLOCK(x) \ > + EX_PUSH_LOCK_WAIT_BLOCK WaitBlockBuffer; \ > PEX_PUSH_LOCK_WAIT_BLOCK x = &WaitBlockBuffer; > > #endif > @@ -725,7 +716,7 @@ > if (InterlockedBitTestAndSet((PLONG)PushLock, EX_PUSH_LOCK_LOCK_V)) > { > /* Someone changed it, use the slow path */ > - DbgPrint("%s - Contention!\n", __FUNCTION__); > + // DbgPrint("%s - Contention!\n", __FUNCTION__); > ExfAcquirePushLockExclusive(PushLock); > } > > @@ -763,7 +754,7 @@ > if (ExpChangePushlock(PushLock, NewValue.Ptr, 0)) > { > /* Someone changed it, use the slow path */ > - DbgPrint("%s - Contention!\n", __FUNCTION__); > + // DbgPrint("%s - Contention!\n", __FUNCTION__); > ExfAcquirePushLockShared(PushLock); > } > > @@ -977,7 +968,7 @@ > OldValue.Ptr)) > { > /* We have waiters, use the long path */ > - DbgPrint("%s - Contention!\n", __FUNCTION__); > + // DbgPrint("%s - Contention!\n", __FUNCTION__); > ExfReleasePushLock(PushLock); > } > } > > >

3 3

Re: [ros-dev] Legal Vista DVD free of charge
by theUser BL 23 Apr '07

23 Apr '07

Here the direct links to it: 64bit version: http://www.mediaonline.de/shop/product_5000_5000_-3_408234_5000.11951.12528… 32bit version: http://www.mediaonline.de/shop/product_5000_5000_-3_408232_5000.11951.12528… _________________________________________________________________ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden!

1 0

Legal Vista DVD free of charge
by theUser BL 23 Apr '07

23 Apr '07

Hi ReactOS-people! If you are from germany and are interested in Vista, then have a look at http://www.mediaonline.de/ There you can "buy" Microsoft Windows Vista Intallation DVDs 32bit and 64bit, german version, for 0 ! You only pay for shipment. This is already annonced on some places here in the internet. But if you still don't know it, I only want to tell it. The only problem: It comes without a key. It is only the Installation DVD, only the software - without key. But the DVD is legal! It is, if you have lost your DVD or if it is damaged or anything else, then you can together with you key again installing Vista. And if you have not a key, possible is it legal to test it 30 days, after it then shut down automatical. You can for example test it on an virtual machine, try to create some programs, which uses Vista-functions and run only on Vista, but not on XP. And then trying to let ReactOS also run this programs, which only runs on Vista. But for that better read the EULA, which is legal and which is not. But the DVDs are free of charge and legal. Greatings theuserbl _________________________________________________________________ Haben Spinnen Ohren? Finden Sie es heraus mit dem MSN Suche Superquiz via http://www.msn-superquiz.de Jetzt mitmachen und gewinnen!

1 0

Re: [ros-dev] Boot Rev 26382
by Aleksey 20 Apr '07

20 Apr '07

Uhm, yes, specifically, cromwell's usb 2.4/2.5 stack + wrapper lack synchronization somewheh (AFAIR). I tried to fix all that in the usb 2.6 attempt, however I don't have motivation anymore, since adapting woodhead's usb stack into reactos, which *just works* :-). It will be even better when usb storage devices support will be finished too. And then, with time, we can implement a proper Win2k3 USB drivers stack, including HID devices. WBR, Aleksey. ----- Original Message ----- From: "James Tabor" <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> To: "ReactOS Development List" <ros-dev(a)reactos.org> Sent: Thursday, April 19, 2007 11:44 PM Subject: Re: [ros-dev] Boot Rev 26382 > Hi! > Aleksey wrote: >> I will finally move those cromwell usb drivers somewhere so they won't be >> installed even by "make install" :-) >> >> WBR, >> Aleksey Bragin. > > It's due to the new kernel structure, I would think. If and when I get > time I can > check into it. No telling when. > Thanks, > James

1 0

Re: [ros-dev] A New RosBE made by me
by Aleksey 20 Apr '07

20 Apr '07

> OT: > Did we decide to place RosBE in our svn? Did the question ever come up? > Thanks, > James Do you mean the src code of the RosBE? It should already be there. As for binaries - as always we put them to sf.net. WBR, Aleksey.

1 0

Re: [ros-dev] Boot Rev 26382
by Aleksey 19 Apr '07

19 Apr '07

I will finally move those cromwell usb drivers somewhere so they won't be installed even by "make install" :-) WBR, Aleksey Bragin. ----- Original Message ----- From: "James Tabor" <jimtabor(a)adsl-64-217-116-74.dsl.hstntx.swbell.net> To: "ReactOS Development List" <ros-dev(a)reactos.org> Sent: Wednesday, April 18, 2007 10:47 PM Subject: Re: [ros-dev] Boot Rev 26382 > Hi! > I did get it to boot by removing the usb drivers. > 8^D > James

2 1

Re: [ros-dev] Ros-dev Digest, Vol 32, Issue 12
by Lucio Diaz 19 Apr '07

19 Apr '07

Aleksey Bragin wrote: --------------------------- That shows you really did not even slightly investigated how the website works. And instead you're proposing a whole workflow for developers, so they mandatory spent a few hours per week maintaining all the stuff you. During that 2 years you should have spent just a bit of time, even 20 minutes, to overview our website and systems we have there, and another 20 minutes to read online manuals/help for them. Excuses like "I didn't have time" hardly apply here. ------------------------- -Irony on- I suppouse that copying each individual resource file, every time it is updated, dont waste developers time.-Irony off- It is your operating system, your servers and your time, you can do as you please. It is not my intention to propose a whole workflow to developers, i only sugested an idea for an easy to use translation tool, noone have to waste time, something similar to the compilation environments, and the IDEs, but some people prefer making things by hand in the command line, but again, is your os and your time, i will decide what to do with my time and if i can or i want to use bugzilla. I feel molested by your tone, i have spent more time on reactos than what you could imagine, but thats not the matter, i think this is a good project, with a great goal, i believe that the easier for everybody to get involved, the best for the project, and my sugestion was going in that direction. I have read the ML for years, and almost never posted a word, i dont have the skill to help much, but offer what "i can", you can take it or not. Regards, Lucio Diaz. ____________________________________________________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com

2 1

Tr : [Qemu-devel] Re: QEMU drivers repository
by Sylvain Petreolle 19 Apr '07

19 Apr '07

May these VESA drivers be useful for ros testing ? ----- Message transféré ---- De : Jan Jezabek <jezabek(a)poczta.onet.pl> À : qemu-devel(a)nongnu.org Envoyé le : Mercredi, 18 Avril 2007, 21h25mn 40s Objet : [Qemu-devel] Re: QEMU drivers repository Natalia Portillo wrote: > Hi all, > I have collected all drivers I could for GD-5446 in > http://www.claunia.com/qemu/drivers/index.html > Hi, If you're interested in NT 3.51 you can find a graphics driver here: http://www.navozhdeniye.narod.ru/vbemp.htm It's a generic VESA driver, but it was the only one I could find that supported high resolution true-color display in NT 3.51, so maybe it's worth to put a link on your page. As for network - I had a good experience with the Realtek 8029 drivers: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=15&PFi… WBR, JJ

2 1

Re: [ros-dev] DbgPrint() - DPRINT() - DPRINT1()
by Aleksey 19 Apr '07

19 Apr '07

Hi Peter, it's a good idea to post an explanation here (might be someone will edit this into a page in our wiki). 1. Traditional DPRINT debug printing ("old way"): All source code files have an #define NDEBUG atop of them, a developer could get a detailed tracing of function calls inside this src code file. DPRINT1()s are used when that code branch must always notify a user / developer (examples are: critical error, not fully implemented branch with a reminder to finish implementation, and any other kind of a situation which occurs rarely and may have a severe impact on a system). 2. "Wine-way" of debug print messages. The printing is done using three macros: TRACE(), WARN(), ERR(). Respectively, TRACE() is the most frequently printed, WARN() is less frequently, and ERR() is an equivalent of a DPRINT1() - always printed, in error situations. In order to enable TRACE() and WARN() debug prints, one must add a #define YDEBUG to the respective place inside an interesting source code file. (Wine has a concept of debug channels, which can be turned on and off, however ReactOS for now does not implement this). 3. Other ways exist, specific for drivers / applications (e.g. for miniport / port / class drivers, client drivers usually use their class's driver's debug print routine, a custom one, having custom severities levels). 4. Newer ways of debug printing (kernel-specific, look for debug channels in windows 2003, debug printing in Vista, -- OSR magazine had a nice article about these). WBR, Aleksey Bragin. ----- Original Message ----- From: <breakoutbox(a)web.de> To: <Ros-dev(a)reactos.org> Sent: Thursday, April 19, 2007 4:21 PM Subject: [ros-dev] DbgPrint() - DPRINT() - DPRINT1() > Hello, > > can please anybody explain me how You want DbgPrint() - DPRINT() - > DPRINT1() to be used ? > I found a lot of DPRINT() _for_example_ in "win32/in32k/objects/dc.c" but > it is not shown on serial debug (?) > (and also SOME ot these DPRINT1() .. ) > > 1) > If I use DPRINT1() instead, it is always shown. > If I use DbgPrint() instead, it is only shown when #DEBUG is defined in > the file + in *.rbuild > But what's the sense of DPRINT() then ? > => > > 2) > 2nd stage: on installing from BootCD I can see serial debug only when I > select DEBUG from startup options. > Is this DPRINT1() suppressed when I DON'T select DEBUG ? > > 3) > Why is there not one DbgPrint() in "win32/in32k/objects/dc.c" (and also in > other files in /DRIVER/ and /NTOSKRNL/ ..) ? > I now have to change every serial debug output to be able to see anything > .. ( if You don't explain me ... ;-) ) > > > Best regards, > Peter.

1 0

DbgPrint() - DPRINT() - DPRINT1()
by breakoutbox＠web.de 19 Apr '07

19 Apr '07

Hello, can please anybody explain me how You want DbgPrint() - DPRINT() - DPRINT1() to be used ? I found a lot of DPRINT() _for_example_ in "win32/in32k/objects/dc.c" but it is not shown on serial debug (?) (and also SOME ot these DPRINT1() .. ) 1) If I use DPRINT1() instead, it is always shown. If I use DbgPrint() instead, it is only shown when #DEBUG is defined in the file + in *.rbuild But what's the sense of DPRINT() then ? => 2) 2nd stage: on installing from BootCD I can see serial debug only when I select DEBUG from startup options. Is this DPRINT1() suppressed when I DON'T select DEBUG ? 3) Why is there not one DbgPrint() in "win32/in32k/objects/dc.c" (and also in other files in /DRIVER/ and /NTOSKRNL/ ..) ? I now have to change every serial debug output to be able to see anything .. ( if You don't explain me ... ;-) ) Best regards, Peter. _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

1 0

Re: [ros-dev] Ros-dev Digest, Vol 32, Issue 12
by Aleksey 19 Apr '07

19 Apr '07

----- Original Message ----- From: "Lucio Diaz" <reactos_translate(a)yahoo.es> To: <ros-dev(a)reactos.org> Sent: Wednesday, April 18, 2007 11:08 PM Subject: Re: [ros-dev] Ros-dev Digest, Vol 32, Issue 12 > -Irony on- I suppouse that copying each individual > resource file, every time it is updated, dont waste > developers time.-Irony off- I don't want to disappoint you even more, but there is a whole concept of a so-called patches (or diffs), which are the thing to be placed in bugzilla, not whole files. I suggest some investigation in this area, like http://en.wikipedia.org/wiki/Patch_%28Unix%29 (it's automated on win32 using TortoiseSVN for example, in GUI mode, etc). And in general about version control systems, bug tracking systems, changesets, and other related terms. WBR, Aleksey Bragin.

1 0

Boot Rev 26382
by James Tabor 18 Apr '07

18 Apr '07

Hi! FYI: Real hardware boot log, (ntoskrnl\kd\kdio.c:193) ----------------------------------------------------- (ntoskrnl\kd\kdio.c:194) ReactOS 0.4-SVN (Build 20070417-r26382) (ntoskrnl\kd\kdio.c:195) Command Line: DEBUGPORT=COM1 (ntoskrnl\kd\kdio.c:199) ARC Paths: multi(0)disk(0)rdisk(0)partition(1) \ multi(0)disk(0)rdisk(0)partition(1) \ReactOS\ (ntoskrnl\ke\i386\cpu.c:518) Not handling AMD caches yet Used memory 1015744Kb (ntoskrnl\se\semgr.c:36) FIXME: SeAccessCheck has been HACKED to always grant access! (ntoskrnl\se\semgr.c:37) FIXME: Please fix all the code that doesn't get properrights! (ntoskrnl\ke\i386\kiinit.c:43) Large Page support detected but not yet taken advantage of! WARNING: HaliQuerySystemInformation at hal\halx86\generic\sysinfo.c:26 is UNIMPLEMENTED! (ntoskrnl\ke\i386\patpge.c:62) Advanced Memory features detected but not yet taken advantage of. (ntoskrnl\ke\i386\mtrr.c:24) Your machine supports MTRR but ReactOS doesn't yet. 0 bytes requested - initiating pool verification 0 bytes requested - initiating pool verification (ntoskrnl\io\iomgr\iorsrce.c:701) IoReportResourceUsage is unimplemented (ntoskrnl\io\iomgr\iorsrce.c:701) IoReportResourceUsage is unimplemented (ntoskrnl\io\iomgr\driver.c:798) Driver 'BUSLOGIC.SYS' load failed, status (c00000c0) (ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1 MmPageEntireDriver at ntoskrnl\mm\drvlck.c:87 is unimplemented, have a nice day MmPageEntireDriver at ntoskrnl\mm\drvlck.c:87 is unimplemented, have a nice day MmPageEntireDriver at ntoskrnl\mm\drvlck.c:87 is unimplemented, have a nice day (ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 10001 (ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1 (ntoskrnl\vdm\vdmmain.c:42) VME detected but not yet supported (lib\rtl\registry.c:362) RTL: Expand variables for %SystemRoot%\system32\cmd.exe failed - Status == c0000023 Size a8 > 7e <e> (lib\rtl\registry.c:362) RTL: Expand variables for %SystemRoot%\bin;%SystemRoot%\system32;%SystemRoot% failed - Status == c0000023 Size f4 > ac <14> (lib\fslib\vfatlib\vfatlib.c:215) VfatChkdsk() unimplemented! (lib\rtl\registry.c:362) RTL: Expand variables for %SystemRoot%\system32 failed - Status == c0000023 Size a4 > 7e <6> (ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff (ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff (ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff (ntoskrnl\se\semgr.c:1161) FIX caller rights (granted 0x8, desired 0x28, generic mapping 80C049E0)! (dll\win32\iphlpapi\ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (dll\win32\iphlpapi\ifenum_reactos.c:99) openTcpFile for <\Device\Tcp> failed: 0xc0000034 (ntoskrnl\io\iomgr\file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find mxdMessage (dll\ntdll\ldr\utils.c:2025) Failed to create or open dll section of 'msacm.drv' (Status c0000135) (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find auxMessage (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find mxdMessage (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find midMessage (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find widMessage (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find wodMessage (dll\win32\shell32\shellpath.c:1688) Failed to create directory 'L".\\Local Settings\\Temporary Internet Files"'. (dll\win32\shell32\shellpath.c:1688) Failed to create directory 'L".\\Local Settings\\History"'. (dll\win32\shell32\shellpath.c:1688) Failed to create directory 'L".\\Cookies"'. (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find mxdMessage (dll\ntdll\ldr\utils.c:2025) Failed to create or open dll section of 'msacm.drv' (Status c0000135) (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find auxMessage (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find mxdMessage (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find midMessage (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find widMessage (dll\ntdll\ldr\utils.c:1199) LdrGetExportByName(): failed to find wodMessage (dll\win32\newdev\newdev.c:680) SetupDiOpenDeviceInfoW() failed with error 0xe000020b (InstanceId HTREE\ROOT\0) (dll\win32\newdev\newdev.c:736) Installing PCI BIOS (Root\*PNP0A03\0000) (dll\win32\newdev\newdev.c:525) Installing driver (Generic system devices): PCIbus (dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\pci.sys" -> L"C:\\ReactOS\\System32\\drivers\\pci.sys" (dll\win32\rpcrt4\ndr_marshall.c:928) unhandled data type=09 (drivers\bus\pci\fdo.c:535) Unknown IOCTL 0xd (drivers\bus\pci\fdo.c:373) No bus number resource found (bug in acpi.sys?), assuming bus number #0 (0,8D7D0178,36) (dll\win32\newdev\newdev.c:736) Installing <NULL> (Root\*PNP0F13\0000) (dll\win32\newdev\newdev.c:525) Installing driver (Standard mice): PS/2 port for PS/2-style mice (dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\i8042prt.sys" -> L"C:\\ReactOS\\System32\\drivers\\i8042prt.sys" (dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\mouclass.sys" -> L"C:\\ReactOS\\System32\\drivers\\mouclass.sys" (dll\win32\rpcrt4\ndr_marshall.c:928) unhandled data type=09 (dll\win32\newdev\newdev.c:736) Installing <NULL> (Root\*PNP0303\0000) (dll\win32\newdev\newdev.c:525) Installing driver (Standard keyboards): IBM PC/AT keyboard (dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\i8042prt.sys" -> L"C:\\ReactOS\\System32\\drivers\\i8042prt.sys" (dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\kbdclass.sys" -> L"C:\\ReactOS\\System32\\drivers\\kbdclass.sys" (dll\win32\rpcrt4\ndr_marshall.c:928) unhandled data type=09 (dll\win32\newdev\newdev.c:736) Installing COM1 (Root\*PNP0501\0000) (dll\win32\newdev\newdev.c:525) Installing driver (Standard ports): Serial communication port (dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\serial.sys" -> L"C:\\ReactOS\\System32\\drivers\\serial.sys" (dll\win32\setupapi\queue.c:1521) copy error 2 L"C:\\ReactOS\\inf\\serenum.sys" -> L"C:\\ReactOS\\System32\\drivers\\serenum.sys" (dll\win32\rpcrt4\ndr_marshall.c:928) unhandled data type=09 (dll\win32\rpcrt4\ndr_marshall.c:928) unhandled data type=09 (drivers\serial\serenum\fdo.c:209) IRP_MJ_PNP / unknown minor function 0xd (drivers\serial\serial\pnp.c:400) Unknown minor function 0xd (drivers\serial\serial\pnp.c:221) KdComPort: D11025FF=üà <two lines of junk> Comm dies, it does continue to boot with a BSOD with the usb driver. Thanks, James

1 1

Automatic testing suite
by Aleksey 18 Apr '07

18 Apr '07

Hi, could someone please remind me what is the state of the automatic reactos testing suite? WBR, Aleksey Bragin.

3 2

Re: [ros-dev] [ros-diffs] [tkreuzer] 26396: NtGdiGetObject: - return 0 if buffer != 0 and count == 0 - don't write beyond umode buffer size (max count bytes!) - use SEH only once - No need for Ret & RetCount, use only RetCount - document the function
by Ged 18 Apr '07

18 Apr '07

> + * @remarks > + * The function will always return the complete size of the object's > data, > + * but will copy only a maximum of count bytes to the specified buffer. This isn't necessarily true, and the function is slightly flawed because of it. It's a rather weird API in terms of it's results. Your rewrite doesn't take into account the following cases, according to XP: ................................................................ BITMAP behaviour GetObjectW(hBmp, -1, &bmp) returns 24 and fills the struct GetObjectW(hBmp, 0, &bmp) returns 0 and doesn't fill the struct GetObjectW(hBmp, 1, &bmp) returns 0 and doesn't fill the struct GetObjectW(hBmp, sizeof(BITMAP), &bmp) returns 24 and fills the struct GetObjectW(hBmp, 5000, &bmp) returns 24 and fills the struct DIBSECTION behaviour GetObjectW(hBmp, -1, &dib) returns 24 and fills the struct GetObjectW(hBmp, 0, &dib) returns 0 and doesn't fill the struct GetObjectW(hBmp, 1, &dib) returns 0 and doesn't fill the struct GetObjectW(hBmp, sizeof(BITMAP), &dib) returns 24 and fills the struct GetObjectW(hBmp, sizeof(DIBSECTION), &dib) returns 24 and fills the struct GetObjectW(hBmp, 5000, &dib) returns 24 and fills the struct Non struct behaviour The function will always return 24, no matter what size is passed. ................................................................ So, we can conclude that if size is less than 0, it works. If size if between 0 and 23, it doesn't, and anything above works. If we pass NULL, as the struct, we return 24, but obviously don't fill the struct. I would have grabbed you on IRC, but you weren't around ;) Ged. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Amteus PLC 57 Cardigan Lane, Leeds, LS4 2LE t:+44 (0) 870 8368770 f: +44 (0) 870 8368701 Registered in England No 4760795 http://www.amteus.com

2 2

Assembly
by Jason Ward 18 Apr '07

18 Apr '07

I am new and am keen on developing ReactOS. I looked through the source of ReactOS, there are only 13 Nasm files. A while ago (2 weeks I think) I mentioned RosAsm, it was shunned a bit though by some of the devs. Anyway, I would prefer to develop in RosAsm rather than Nasm, I know how you guys feel about it stealing your name but I prefer it to Nasm. (Syntax is cleaner) So would it be possible for me to develop in RosAsm for ReactOS? It does run under ReactOS so it's just a case of your acceptance.

7 7

Re: [ros-dev] RosASM
by Olaf Siejka 17 Apr '07

17 Apr '07

I am sick of you, Betov, as for your outright lies. >Well, while I am at it, about the previous shocking absurdities: Shocking absurdities... what a great name for your post. >* RosAsm exist since September 1998. I started this Project the very >First day I heard of ReactOS. This is to say, I never wrote one single >Line for Windows, and I never used Windows any other way, but as >A development platform, as long as ReactOS was not usable. http://en.wikipedia.org/wiki/RosAsm History: In September 1998, René Tournois (also known as Betov), created SpAsm - The Specific assembler which was maintained and supported by him until 24 July 2003. It was then continued with its successor, RosAsm.... Spasm 4.15j ,was the last of the versions released and maintained by René. On 24 July 2003, he decided to take a higher step toward advancing the benefit of Assembly Language and the free programming community. Concerned about the ongoing of the Software and his constant efforts in keeping with his ethical and political views, he left the project. From that remarkable day, RosAsm was born! RosAsm 1.1a was the first version from the renewed Software, released on 27 July 2003. RosASM branched from SpASM in 2003. Thus statement as RosASM even EXISTED in 1998 is an outright lie. >* We are not used to promote our Tool, and would we have intention to >Do so, we would certainly not have suggested, with its name, that it >was, in any way, devoted to an OS that does not exist, yet. "The >Visual Assembler", or whatever such name would have been many >Times more appropriated. Using Ros as a part of your name is enough. Compare how many people know the name ReactOS, to the number of those who know about RosASM... it`ll be clear enough, who is leeching from who. >* The fact that our Assembler name is "RosAsm" expresses the flat fact >That it is devoted to ReactOS. Period. The fact is that the name RosASM was chosen to CREATE IMPRESSION that RosASM is in any way related to ReactOS project. It is not. ROS never used and never will be using RosASM. There is no relation to RosASM. You were asked to add a disclaimer on RosASM website, stating this fact. You failed to provide it. Why? You afraid of shattering the illusion of any RosASM-ROS relations? Your devs still think they are working for ROS project? >This irritates Alex because he Hates me, and this is OK to me to >irritates the very same individual, Who is implying that poor old >Harmut was a dirty guy, having done something bad to reactOS, >when leaving because of his conduct. I dont know you as well as Alex does, and you know what? Those several posts of yours i seen were enough. Alex doesnt hate you. You just make him laugh. But you DO IRRITATE ME. I think you have several mental issues, including paranoia, neurosis, as well as inferiority complex regarding Alex. I suggest you take a long break from any computer-related activities and rethink your behaviour. >* If ReactOS is a virtually dead Project, because of the topic that all of >you seem to carefully avoid and try to hide under the carpet, we (the >RosAsm Project), will effectively have serious problems, and not only >with its Name. See what I mean Alexey? ("Nothing has been found yet", ">these are rumors", and so on...). Again, another sign of your mental issues. If you are certain about Ros project being dead, you are free to change name as well as an object of your devotion. This should eliminate all the sources of your troubles. We would welcome this change with great joy. Please, do all of us a favour, and just GTFO with your ASM. >Betov. Regards Caemyr

1 0

About translation
by Lucio Diaz 17 Apr '07

17 Apr '07

First of All: The message is not in the wrong list, but directed to developers. A few facts about translators: -Most are not programmers or they would be coding the OS, just powerusers, or just users. -Many like me can install SVN, and get the source code, but never have made a patch, or even used bugzilla(and probably wont have the time). Now the matter: Actually the process of translating reactos, or even the web page is difficult, and for me it have been frustrating. I started following the project in the 0.1.9 version, and about two years ago i tried to help in the translation of ReactOS, and later in the translation of the web page, but with little success. I have the SVN, i got the code, i translated some files, but sending them to bugzilla... i dont know how to send them to bugzilla, i dont have a bugzilla acount, it was tiring trying to find someone to send the files, and i dont have the time or will to learn bugzilla. So time passed, and no translation was made. Something similar happened when i tried to translate the web page, i got translator access, but after making some translations, and sending it, i never saw it applied (probably i was doing something wrong, but never knew what). Almost two years have passed from that time, i have a hard job, and little free time, but still i wish to help. I feel there are other translators in my situation, as i see people that offer to help, but never comes back. So here is what i believe could be a solution: The possible solution: Html have an option to include code "as is", thus a wiki should have that option. -make a script that makes html files of all the rc files. -Add a page in the wiki (or another wiki) where those html files are displayed. -Anyone can get read access to them. -There is an easy way to get write access to that wiki. -Translator teams for each language are created... with a cordinator for each language (they give write access to other translators). -Translator access the rc files, that are in wiki format, and edit them. -Every week developers run a script to build rc files from the html wiki files in each language. Result: a translation effort, easy, coordinated, with minimal need of learning technical stuff and many developers that wont be molested by translators who want their translations added to the svn. Thanks, Lucio Diaz. PD: Please comment. ____________________________________________________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com

2 1

Re: [ros-dev] [ros-diffs] [dgorbachev] 26342: Fix a bug.
by Alex Ionescu 14 Apr '07

14 Apr '07

Please use descriptive messages in your commit logs, this must've been stressed by Fireball at least a dozen times (Sometimes even with consequences). When we have to go over the changelog (Which is textlog-only), what are we supposed to put when we see 10 "Fix a bug" entries? It means we have to check out the log for every revision with such a message, and try to understand the change. Since the log is usually done by non-technical people, this becomes impossible for them. Best regards, Alex Ionescu -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of dgorbachev(a)svn.reactos.org Sent: April-14-07 2:07 PM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [dgorbachev] 26342: Fix a bug. Author: dgorbachev Date: Sat Apr 14 22:07:08 2007 New Revision: 26342 URL: http://svn.reactos.org/svn/reactos?rev=26342&view=rev Log: Fix a bug. Modified: trunk/reactos/ntoskrnl/ps/query.c Modified: trunk/reactos/ntoskrnl/ps/query.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ps/query.c?rev=26… ============================================================================== --- trunk/reactos/ntoskrnl/ps/query.c (original) +++ trunk/reactos/ntoskrnl/ps/query.c Sat Apr 14 22:07:08 2007 @@ -267,7 +267,7 @@ VmCounters->PeakPagefileUsage = Process->QuotaPeak[2]; /* Set the return length */ - *ReturnLength = sizeof(VM_COUNTERS); + Length = sizeof(VM_COUNTERS); } _SEH_HANDLE {

1 0

Fix Italian translation for SNDVOL32
by carlo.bramix 13 Apr '07

13 Apr '07

Hello, I suggest this patch for fixing the italian translation of SNDVOL32. Sincerely, Carlo Bramini ------------------------------------------------------ Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom http://click.libero.it/infostrada

2 1

My vacation
by Aleksey Bragin 11 Apr '07

11 Apr '07

Hello, I'm leaving for a 3 weeks vacation (starting today) and will be accessible mostly via email. Have fun with the ReactOS development, and do not introduce new bugs :). Remember - when I'm back, we're going to prepare a new release - 0.3.2. If trunk is not ready for a release by the moment I'm back, I'll start killing devs one by one until it's ready. -- WBR, Aleksey Bragin ReactOS Project Coordinator http://www.reactos.org P.S. The last sentence is a joke, obviously.

1 0

Why so small?
by Jason Ward 10 Apr '07

10 Apr '07

The source code for ReactOS is only 30MB. The project has been going for 10 years so why so small? Is there a need for any developers who can program assembler? I use the ReactOS assembler. RosAsm. http://www.rosasm.org Or do you only program in C and C++?

12 18

(no subject)
by hto＠mail.cnt.ru 04 Apr '07

04 Apr '07

> We shouldn't allow attaching to a device that's still > initlizaing, but ROS currently does because of some > device that tries to do this, in the PnP manager or > early boot-phase drivers (it has an auto-generated name). > Please fix this! Init function of that driver (PnpDriverInitializeEmpty() in pnpmgr.c) is not called at all because of hack in IopCreateDriver(), line 1206.

1 1

Re: [ros-dev] [ros-diffs] [greatlrd] 26246: fixing the build for gcc 3.4.5
by gerard.murphy 02 Apr '07

02 Apr '07

Why have all these 'initialization bugs' suddenly been highlighted, and only in GCC 3.4.5 Has the latest PSEH code highlighted a GCC 3.4.5 issue which we are just hiding by double initializing variables?? We've seen initialization bugs with 3.4.5 before but always ignored them as they appear in development. This is on a different scale. Taking the AFD as an example, as this was also briefly batted around in IRC, line 769 holds: PDEVICE_OBJECT DeviceObject; Line 773 then holds: DeviceObject = IoGetRelatedDeviceObject(TransportObject); This is before any calls to _SEH_TRY, so it's not an issue of stuff being wrapped in PSEH In the words of Mr. Poussineau - if error message is correct, fix the bug - if error message is incorrect, report to GCC Therefore as this code is not a real error, we should either send a bug report off to mingw, or more realistically, drop 3.4.5 and move to 4.1.2 (as the latest RosBE already does). We shouldn't really be hiding incorrect errors by double initializing. Ged. -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of greatlrd(a)svn.reactos.org Sent: 02 April 2007 10:49 To: ros-diffs(a)reactos.org Subject: [ros-diffs] [greatlrd] 26246: fixing the build for gcc 3.4.5 Author: greatlrd Date: Mon Apr 2 13:48:51 2007 New Revision: 26246 URL: http://svn.reactos.org/svn/reactos?rev=26246&view=rev Log: fixing the build for gcc 3.4.5 Modified: trunk/reactos/ntoskrnl/cm/ntfunc.c trunk/reactos/ntoskrnl/ex/sysinfo.c trunk/reactos/ntoskrnl/ex/timer.c trunk/reactos/ntoskrnl/fsrtl/fastio.c trunk/reactos/ntoskrnl/io/iomgr/driver.c trunk/reactos/ntoskrnl/io/iomgr/file.c trunk/reactos/ntoskrnl/io/iomgr/iofunc.c trunk/reactos/ntoskrnl/io/iomgr/irp.c trunk/reactos/ntoskrnl/io/pnpmgr/plugplay.c trunk/reactos/ntoskrnl/ke/i386/usercall.c trunk/reactos/ntoskrnl/ke/thrdobj.c trunk/reactos/ntoskrnl/mm/section.c trunk/reactos/ntoskrnl/mm/virtual.c trunk/reactos/ntoskrnl/ob/obdir.c trunk/reactos/ntoskrnl/ob/obhandle.c trunk/reactos/ntoskrnl/ob/obwait.c trunk/reactos/ntoskrnl/ps/job.c trunk/reactos/ntoskrnl/ps/query.c trunk/reactos/ntoskrnl/ps/thread.c trunk/reactos/ntoskrnl/se/acl.c trunk/reactos/ntoskrnl/se/priv.c trunk/reactos/ntoskrnl/se/sd.c trunk/reactos/ntoskrnl/se/sid.c trunk/reactos/ntoskrnl/se/token.c Modified: trunk/reactos/ntoskrnl/cm/ntfunc.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/cm/ntfunc.c?rev=26 246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/cm/ntfunc.c (original) +++ trunk/reactos/ntoskrnl/cm/ntfunc.c Mon Apr 2 13:48:51 2007 @@ -299,7 +299,7 @@ unsigned i; REG_PRE_CREATE_KEY_INFORMATION PreCreateKeyInfo; REG_POST_CREATE_KEY_INFORMATION PostCreateKeyInfo; - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; UNICODE_STRING CapturedClass = {0}; HANDLE hKey; @@ -1308,7 +1308,7 @@ IN POBJECT_ATTRIBUTES ObjectAttributes) { UNICODE_STRING RemainingPath; - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; PVOID Object = NULL; HANDLE hKey = NULL; NTSTATUS Status = STATUS_SUCCESS; @@ -2145,7 +2145,7 @@ NTSTATUS Status; REG_DELETE_VALUE_KEY_INFORMATION DeleteValueKeyInfo; REG_POST_OPERATION_INFORMATION PostOperationInfo; - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; UNICODE_STRING CapturedValueName; PAGED_CODE(); Modified: trunk/reactos/ntoskrnl/ex/sysinfo.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ex/sysinfo.c?rev=2 6246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/ex/sysinfo.c (original) +++ trunk/reactos/ntoskrnl/ex/sysinfo.c Mon Apr 2 13:48:51 2007 @@ -232,10 +232,10 @@ ANSI_STRING AName; UNICODE_STRING WName; BOOLEAN Result; - PCH Value; + PCH Value = NULL; ANSI_STRING AValue; UNICODE_STRING WValue; - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; NTSTATUS Status = STATUS_SUCCESS; PAGED_CODE(); @@ -378,7 +378,7 @@ { UNICODE_STRING CapturedName, CapturedValue; ANSI_STRING AName, AValue; - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; NTSTATUS Status; PAGED_CODE(); Modified: trunk/reactos/ntoskrnl/ex/timer.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ex/timer.c?rev=262 46&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/ex/timer.c (original) +++ trunk/reactos/ntoskrnl/ex/timer.c Mon Apr 2 13:48:51 2007 @@ -510,7 +510,7 @@ { PETIMER Timer; KPROCESSOR_MODE PreviousMode = ExGetPreviousMode(); - NTSTATUS Status; + NTSTATUS Status = STATUS_UNSUCCESSFUL; PTIMER_BASIC_INFORMATION BasicInfo = TimerInformation; PAGED_CODE(); Modified: trunk/reactos/ntoskrnl/fsrtl/fastio.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/fsrtl/fastio.c?rev =26246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/fsrtl/fastio.c (original) +++ trunk/reactos/ntoskrnl/fsrtl/fastio.c Mon Apr 2 13:48:51 2007 @@ -83,7 +83,7 @@ IN PDEVICE_OBJECT DeviceObject) { - PFSRTL_COMMON_FCB_HEADER FcbHeader; + PFSRTL_COMMON_FCB_HEADER FcbHeader = NULL; LARGE_INTEGER Offset; PFAST_IO_DISPATCH FastIoDispatch; PDEVICE_OBJECT Device; @@ -258,7 +258,7 @@ BOOLEAN Result = TRUE; PFAST_IO_DISPATCH FastIoDispatch; PDEVICE_OBJECT Device; - PFSRTL_COMMON_FCB_HEADER FcbHeader; + PFSRTL_COMMON_FCB_HEADER FcbHeader = NULL; /* WDK doc. Offset=0xffffffffffffffff indicates append to the end of file */ BOOLEAN FileOffsetAppend = ((FileOffset->HighPart == 0xffffffff) && (FileOffset->LowPart == 0xffffffff)); @@ -915,7 +915,7 @@ OUT PIO_STATUS_BLOCK IoStatus, IN PDEVICE_OBJECT DeviceObject) { - PFSRTL_COMMON_FCB_HEADER FcbHeader; + PFSRTL_COMMON_FCB_HEADER FcbHeader = NULL; BOOLEAN Result = TRUE; LARGE_INTEGER Offset; PFAST_IO_DISPATCH FastIoDispatch; @@ -1159,7 +1159,7 @@ BOOLEAN Result = TRUE; PFAST_IO_DISPATCH FastIoDispatch; PDEVICE_OBJECT Device; - PFSRTL_COMMON_FCB_HEADER FcbHeader; + PFSRTL_COMMON_FCB_HEADER FcbHeader = NULL; LARGE_INTEGER OldFileSize; LARGE_INTEGER OldValidDataLength; Modified: trunk/reactos/ntoskrnl/io/iomgr/driver.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/driver.c? rev=26246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/io/iomgr/driver.c (original) +++ trunk/reactos/ntoskrnl/io/iomgr/driver.c Mon Apr 2 13:48:51 2007 @@ -1475,7 +1475,7 @@ UNICODE_STRING ImagePath; UNICODE_STRING ServiceName; UNICODE_STRING CapturedDriverServiceName = {0}; - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; NTSTATUS Status; ULONG Type; PDEVICE_NODE DeviceNode; Modified: trunk/reactos/ntoskrnl/io/iomgr/file.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/file.c?re v=26246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/io/iomgr/file.c (original) +++ trunk/reactos/ntoskrnl/io/iomgr/file.c Mon Apr 2 13:48:51 2007 @@ -1629,7 +1629,7 @@ IN PVOID ExtraCreateParameters OPTIONAL, IN ULONG Options) { - KPROCESSOR_MODE AccessMode; + KPROCESSOR_MODE AccessMode = {0}; HANDLE LocalHandle = 0; LARGE_INTEGER SafeAllocationSize; PVOID SystemEaBuffer = NULL; Modified: trunk/reactos/ntoskrnl/io/iomgr/iofunc.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/iofunc.c? rev=26246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/io/iomgr/iofunc.c (original) +++ trunk/reactos/ntoskrnl/io/iomgr/iofunc.c Mon Apr 2 13:48:51 2007 @@ -198,12 +198,12 @@ { NTSTATUS Status = STATUS_SUCCESS; PFILE_OBJECT FileObject; - PDEVICE_OBJECT DeviceObject; - PIRP Irp; + PDEVICE_OBJECT DeviceObject = NULL; + PIRP Irp = NULL; PIO_STACK_LOCATION StackPtr; PKEVENT EventObject = NULL; BOOLEAN LockedForSynch = FALSE; - ULONG AccessType; + ULONG AccessType = 0; OBJECT_HANDLE_INFORMATION HandleInformation; ACCESS_MASK DesiredAccess; KPROCESSOR_MODE PreviousMode = ExGetPreviousMode(); @@ -1212,9 +1212,9 @@ { PFILE_OBJECT FileObject; PLARGE_INTEGER LocalLength = NULL; - PIRP Irp; - PIO_STACK_LOCATION StackPtr; - PDEVICE_OBJECT DeviceObject; + PIRP Irp = NULL; + PIO_STACK_LOCATION StackPtr = NULL; + PDEVICE_OBJECT DeviceObject = NULL; PKEVENT Event = NULL; BOOLEAN LockedForSync = FALSE; KPROCESSOR_MODE PreviousMode = KeGetPreviousMode(); @@ -1386,8 +1386,8 @@ IN PUNICODE_STRING FileName OPTIONAL, IN BOOLEAN RestartScan) { - PIRP Irp; - PDEVICE_OBJECT DeviceObject; + PIRP Irp = NULL; + PDEVICE_OBJECT DeviceObject = NULL; PFILE_OBJECT FileObject; PIO_STACK_LOCATION StackPtr; KPROCESSOR_MODE PreviousMode = ExGetPreviousMode(); @@ -1627,9 +1627,9 @@ OBJECT_HANDLE_INFORMATION HandleInformation; PFILE_OBJECT FileObject; NTSTATUS Status = STATUS_SUCCESS; - PIRP Irp; - PDEVICE_OBJECT DeviceObject; - PIO_STACK_LOCATION StackPtr; + PIRP Irp = NULL; + PDEVICE_OBJECT DeviceObject = NULL; + PIO_STACK_LOCATION StackPtr = NULL; KPROCESSOR_MODE PreviousMode = ExGetPreviousMode(); PKEVENT Event = NULL; BOOLEAN LocalEvent = FALSE; @@ -1938,8 +1938,8 @@ { NTSTATUS Status = STATUS_SUCCESS; PFILE_OBJECT FileObject; - PIRP Irp; - PDEVICE_OBJECT DeviceObject; + PIRP Irp = NULL; + PDEVICE_OBJECT DeviceObject = NULL; PIO_STACK_LOCATION StackPtr; KPROCESSOR_MODE PreviousMode = KeGetPreviousMode(); PKEVENT EventObject = NULL; @@ -2197,9 +2197,9 @@ { PFILE_OBJECT FileObject; NTSTATUS Status = STATUS_SUCCESS; - PIRP Irp; - PDEVICE_OBJECT DeviceObject; - PIO_STACK_LOCATION StackPtr; + PIRP Irp = NULL; + PDEVICE_OBJECT DeviceObject = NULL; + PIO_STACK_LOCATION StackPtr = NULL; KPROCESSOR_MODE PreviousMode = ExGetPreviousMode(); PKEVENT Event = NULL; BOOLEAN LocalEvent = FALSE; @@ -2576,9 +2576,9 @@ { PFILE_OBJECT FileObject; PLARGE_INTEGER LocalLength = NULL; - PIRP Irp; - PIO_STACK_LOCATION StackPtr; - PDEVICE_OBJECT DeviceObject; + PIRP Irp = NULL; + PIO_STACK_LOCATION StackPtr = NULL; + PDEVICE_OBJECT DeviceObject = NULL; PKEVENT Event = NULL; BOOLEAN LocalEvent = FALSE; KPROCESSOR_MODE PreviousMode = KeGetPreviousMode(); @@ -2760,8 +2760,8 @@ { NTSTATUS Status = STATUS_SUCCESS; PFILE_OBJECT FileObject; - PIRP Irp; - PDEVICE_OBJECT DeviceObject; + PIRP Irp = NULL; + PDEVICE_OBJECT DeviceObject = NULL; PIO_STACK_LOCATION StackPtr; KPROCESSOR_MODE PreviousMode = KeGetPreviousMode(); PKEVENT EventObject = NULL; @@ -3027,9 +3027,9 @@ IN FS_INFORMATION_CLASS FsInformationClass) { PFILE_OBJECT FileObject; - PIRP Irp; - PIO_STACK_LOCATION StackPtr; - PDEVICE_OBJECT DeviceObject; + PIRP Irp = NULL; + PIO_STACK_LOCATION StackPtr = NULL; + PDEVICE_OBJECT DeviceObject = NULL; PKEVENT Event = NULL; BOOLEAN LocalEvent = FALSE; KPROCESSOR_MODE PreviousMode = KeGetPreviousMode(); @@ -3190,9 +3190,9 @@ IN FS_INFORMATION_CLASS FsInformationClass) { PFILE_OBJECT FileObject; - PIRP Irp; - PIO_STACK_LOCATION StackPtr; - PDEVICE_OBJECT DeviceObject; + PIRP Irp = NULL; + PIO_STACK_LOCATION StackPtr = NULL; + PDEVICE_OBJECT DeviceObject = NULL; PKEVENT Event = NULL; BOOLEAN LocalEvent = FALSE; KPROCESSOR_MODE PreviousMode = KeGetPreviousMode(); Modified: trunk/reactos/ntoskrnl/io/iomgr/irp.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/irp.c?rev =26246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/io/iomgr/irp.c (original) +++ trunk/reactos/ntoskrnl/io/iomgr/irp.c Mon Apr 2 13:48:51 2007 @@ -610,8 +610,8 @@ IN PLARGE_INTEGER StartingOffset, IN PIO_STATUS_BLOCK IoStatusBlock) { - PIRP Irp; - PIO_STACK_LOCATION StackPtr; + PIRP Irp = NULL; + PIO_STACK_LOCATION StackPtr = NULL; /* Allocate IRP */ Irp = IoAllocateIrp(DeviceObject->StackSize, FALSE); @@ -745,7 +745,7 @@ IN PKEVENT Event, IN PIO_STATUS_BLOCK IoStatusBlock) { - PIRP Irp; + PIRP Irp = NULL; PIO_STACK_LOCATION StackPtr; ULONG BufferLength; Modified: trunk/reactos/ntoskrnl/io/pnpmgr/plugplay.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/pnpmgr/plugplay .c?rev=26246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/io/pnpmgr/plugplay.c (original) +++ trunk/reactos/ntoskrnl/io/pnpmgr/plugplay.c Mon Apr 2 13:48:51 2007 @@ -443,7 +443,7 @@ UNICODE_STRING DeviceInstance; ULONG BufferSize; ULONG Property = 0; - PVOID Buffer; + PVOID Buffer = NULL; DPRINT("IopGetDeviceProperty() called\n"); DPRINT("Device name: %wZ\n", &PropertyData->DeviceInstance); Modified: trunk/reactos/ntoskrnl/ke/i386/usercall.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/usercall.c ?rev=26246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/ke/i386/usercall.c (original) +++ trunk/reactos/ntoskrnl/ke/i386/usercall.c Mon Apr 2 13:48:51 2007 @@ -148,8 +148,8 @@ OUT PVOID *Result, OUT PULONG ResultLength) { - ULONG_PTR NewStack, OldStack; - PULONG UserEsp; + ULONG_PTR NewStack =0, OldStack = 0; + PULONG UserEsp = NULL; NTSTATUS CallbackStatus = STATUS_SUCCESS; PEXCEPTION_REGISTRATION_RECORD ExceptionList; PTEB Teb; Modified: trunk/reactos/ntoskrnl/ke/thrdobj.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/thrdobj.c?rev=2 6246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/ke/thrdobj.c (original) +++ trunk/reactos/ntoskrnl/ke/thrdobj.c Mon Apr 2 13:48:51 2007 @@ -723,7 +723,7 @@ ULONG i; PKWAIT_BLOCK TimerWaitBlock; PKTIMER Timer; - NTSTATUS Status; + NTSTATUS Status = STATUS_UNSUCCESSFUL; /* Initalize the Dispatcher Header */ KeInitializeDispatcherHeader(&Thread->DispatcherHeader, Modified: trunk/reactos/ntoskrnl/mm/section.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/section.c?rev=2 6246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/mm/section.c (original) +++ trunk/reactos/ntoskrnl/mm/section.c Mon Apr 2 13:48:51 2007 @@ -3670,7 +3670,7 @@ SIZE_T SafeViewSize; PROS_SECTION_OBJECT Section; PEPROCESS Process; - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; PMADDRESS_SPACE AddressSpace; NTSTATUS Status = STATUS_SUCCESS; ULONG tmpProtect; Modified: trunk/reactos/ntoskrnl/mm/virtual.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/virtual.c?rev=2 6246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/mm/virtual.c (original) +++ trunk/reactos/ntoskrnl/mm/virtual.c Mon Apr 2 13:48:51 2007 @@ -554,10 +554,10 @@ IN ULONG NumberOfBytesToRead, OUT PULONG NumberOfBytesRead OPTIONAL) { - PMDL Mdl; + PMDL Mdl = NULL; PVOID SystemAddress; - KPROCESSOR_MODE PreviousMode; - PEPROCESS Process, CurrentProcess; + KPROCESSOR_MODE PreviousMode = {0}; + PEPROCESS Process, CurrentProcess = NULL; NTSTATUS Status = STATUS_SUCCESS; PAGED_CODE(); @@ -769,11 +769,11 @@ IN ULONG NumberOfBytesToWrite, OUT PULONG NumberOfBytesWritten OPTIONAL) { - PMDL Mdl; - PVOID SystemAddress; + PMDL Mdl = NULL; + PVOID SystemAddress = NULL; PEPROCESS Process; - KPROCESSOR_MODE PreviousMode; - NTSTATUS CopyStatus, Status = STATUS_SUCCESS; + KPROCESSOR_MODE PreviousMode = {0}; + NTSTATUS CopyStatus = STATUS_SUCCESS, Status = STATUS_SUCCESS; DPRINT("NtWriteVirtualMemory(ProcessHandle %x, BaseAddress %x, " "Buffer %x, NumberOfBytesToWrite %d)\n",ProcessHandle,BaseAddress, Modified: trunk/reactos/ntoskrnl/ob/obdir.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ob/obdir.c?rev=262 46&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/ob/obdir.c (original) +++ trunk/reactos/ntoskrnl/ob/obdir.c Mon Apr 2 13:48:51 2007 @@ -466,7 +466,7 @@ KPROCESSOR_MODE PreviousMode = ExGetPreviousMode(); ULONG SkipEntries = 0; NTSTATUS Status = STATUS_SUCCESS; - PVOID LocalBuffer; + PVOID LocalBuffer = NULL; POBJECT_DIRECTORY_INFORMATION DirectoryInfo; ULONG Length, TotalLength; ULONG Count, CurrentEntry; Modified: trunk/reactos/ntoskrnl/ob/obhandle.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ob/obhandle.c?rev= 26246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/ob/obhandle.c (original) +++ trunk/reactos/ntoskrnl/ob/obhandle.c Mon Apr 2 13:48:51 2007 @@ -3150,7 +3150,7 @@ IN ULONG HandleAttributes, IN ULONG Options) { - PEPROCESS SourceProcess, TargetProcess, Target; + PEPROCESS SourceProcess, TargetProcess, Target = NULL; HANDLE hTarget; KPROCESSOR_MODE PreviousMode = ExGetPreviousMode(); NTSTATUS Status = STATUS_SUCCESS; Modified: trunk/reactos/ntoskrnl/ob/obwait.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ob/obwait.c?rev=26 246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/ob/obwait.c (original) +++ trunk/reactos/ntoskrnl/ob/obwait.c Mon Apr 2 13:48:51 2007 @@ -56,7 +56,7 @@ ULONG i = 0, ReferencedObjects = 0, j; KPROCESSOR_MODE PreviousMode = ExGetPreviousMode(); LARGE_INTEGER SafeTimeOut; - BOOLEAN LockInUse; + BOOLEAN LockInUse = FALSE; PHANDLE_TABLE_ENTRY HandleEntry; POBJECT_HEADER ObjectHeader; PHANDLE_TABLE HandleTable; @@ -457,7 +457,7 @@ { KPROCESSOR_MODE PreviousMode = ExGetPreviousMode(); POBJECT_TYPE Type; - PVOID SignalObj, WaitObj, WaitableObject; + PVOID SignalObj, WaitObj, WaitableObject = NULL; LARGE_INTEGER SafeTimeOut; OBJECT_HANDLE_INFORMATION HandleInfo; NTSTATUS Status = STATUS_SUCCESS; Modified: trunk/reactos/ntoskrnl/ps/job.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ps/job.c?rev=26246 &r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/ps/job.c (original) +++ trunk/reactos/ntoskrnl/ps/job.c Mon Apr 2 13:48:51 2007 @@ -225,8 +225,8 @@ { HANDLE hJob; PEJOB Job; - KPROCESSOR_MODE PreviousMode; - PEPROCESS CurrentProcess; + KPROCESSOR_MODE PreviousMode = {0}; + PEPROCESS CurrentProcess = NULL; NTSTATUS Status = STATUS_SUCCESS; PAGED_CODE(); @@ -396,7 +396,7 @@ ACCESS_MASK DesiredAccess, POBJECT_ATTRIBUTES ObjectAttributes) { - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; HANDLE hJob; NTSTATUS Status = STATUS_SUCCESS; Modified: trunk/reactos/ntoskrnl/ps/query.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ps/query.c?rev=262 46&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/ps/query.c (original) +++ trunk/reactos/ntoskrnl/ps/query.c Mon Apr 2 13:48:51 2007 @@ -484,7 +484,7 @@ PEPROCESS Process; KPROCESSOR_MODE PreviousMode = ExGetPreviousMode(); ACCESS_MASK Access; - NTSTATUS Status; + NTSTATUS Status = STATUS_NOT_IMPLEMENTED; HANDLE PortHandle = NULL; HANDLE TokenHandle = NULL; PROCESS_SESSION_INFORMATION SessionInfo = {0}; @@ -719,7 +719,7 @@ PETHREAD Thread; ULONG Access; KPROCESSOR_MODE PreviousMode = ExGetPreviousMode(); - NTSTATUS Status; + NTSTATUS Status = STATUS_INVALID_PARAMETER; HANDLE TokenHandle = NULL; KPRIORITY Priority = 0; KAFFINITY Affinity = 0, CombinedAffinity; Modified: trunk/reactos/ntoskrnl/ps/thread.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ps/thread.c?rev=26 246&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/ps/thread.c (original) +++ trunk/reactos/ntoskrnl/ps/thread.c Mon Apr 2 13:48:51 2007 @@ -141,7 +141,7 @@ PspSystemThreadStartup(IN PKSTART_ROUTINE StartRoutine, IN PVOID StartContext) { - PETHREAD Thread; + PETHREAD Thread = NULL; PSTRACE(PS_THREAD_DEBUG, "StartRoutine: %p StartContext: %p\n", StartRoutine, StartContext); Modified: trunk/reactos/ntoskrnl/se/acl.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/se/acl.c?rev=26246 &r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/se/acl.c (original) +++ trunk/reactos/ntoskrnl/se/acl.c Mon Apr 2 13:48:51 2007 @@ -275,7 +275,7 @@ IN BOOLEAN CaptureIfKernel, OUT PACL *CapturedAcl) { - PACL NewAcl; + PACL NewAcl = NULL; ULONG AclSize = 0; NTSTATUS Status = STATUS_SUCCESS; Modified: trunk/reactos/ntoskrnl/se/priv.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/se/priv.c?rev=2624 6&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/se/priv.c (original) +++ trunk/reactos/ntoskrnl/se/priv.c Mon Apr 2 13:48:51 2007 @@ -184,7 +184,7 @@ PLUID_AND_ATTRIBUTES* Dest, PULONG Length) { - ULONG BufferSize; + ULONG BufferSize = 0; NTSTATUS Status = STATUS_SUCCESS; PAGED_CODE(); @@ -300,7 +300,7 @@ ULONG PrivilegeControl = 0; ULONG Length; BOOLEAN CheckResult; - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; NTSTATUS Status = STATUS_SUCCESS; PAGED_CODE(); Modified: trunk/reactos/ntoskrnl/se/sd.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/se/sd.c?rev=26246& r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/se/sd.c (original) +++ trunk/reactos/ntoskrnl/se/sd.c Mon Apr 2 13:48:51 2007 @@ -394,7 +394,7 @@ { PISECURITY_DESCRIPTOR OriginalSecurityDescriptor = _OriginalSecurityDescriptor; SECURITY_DESCRIPTOR DescriptorCopy; - PISECURITY_DESCRIPTOR NewDescriptor; + PISECURITY_DESCRIPTOR NewDescriptor = NULL; ULONG OwnerSAC = 0, GroupSAC = 0; ULONG OwnerSize = 0, GroupSize = 0; ULONG SaclSize = 0, DaclSize = 0; Modified: trunk/reactos/ntoskrnl/se/sid.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/se/sid.c?rev=26246 &r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/se/sid.c (original) +++ trunk/reactos/ntoskrnl/se/sid.c Mon Apr 2 13:48:51 2007 @@ -236,7 +236,7 @@ OUT PSID *CapturedSid) { ULONG SidSize = 0; - PISID NewSid, Sid = (PISID)InputSid; + PISID NewSid = NULL, Sid = (PISID)InputSid; NTSTATUS Status = STATUS_SUCCESS; PAGED_CODE(); Modified: trunk/reactos/ntoskrnl/se/token.c URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/se/token.c?rev=262 46&r1=26245&r2=26246&view=diff ============================================================================ == --- trunk/reactos/ntoskrnl/se/token.c (original) +++ trunk/reactos/ntoskrnl/se/token.c Mon Apr 2 13:48:51 2007 @@ -669,8 +669,8 @@ ULONG Ulong; } Unused; PTOKEN Token; - ULONG RequiredLength; - KPROCESSOR_MODE PreviousMode; + ULONG RequiredLength = 0; + KPROCESSOR_MODE PreviousMode = {0}; NTSTATUS Status = STATUS_SUCCESS; PAGED_CODE(); @@ -1253,7 +1253,7 @@ IN ULONG TokenInformationLength) { PTOKEN Token; - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; ULONG NeededAccess = TOKEN_ADJUST_DEFAULT; NTSTATUS Status = STATUS_SUCCESS; @@ -1496,7 +1496,7 @@ IN TOKEN_TYPE TokenType, OUT PHANDLE NewTokenHandle) { - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; HANDLE hToken; PTOKEN Token; PTOKEN NewToken; @@ -2134,7 +2134,7 @@ PVOID EndMem; ULONG uLength; ULONG i; - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; ULONG nTokenPrivileges = 0; LARGE_INTEGER LocalExpirationTime = {{0}}; NTSTATUS Status = STATUS_SUCCESS; @@ -2464,7 +2464,7 @@ OBJECT_ATTRIBUTES ObjectAttributes; SECURITY_DESCRIPTOR SecurityDescriptor; PACL Dacl = NULL; - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; NTSTATUS Status = STATUS_SUCCESS; PAGED_CODE(); @@ -2661,7 +2661,7 @@ IN HANDLE SecondTokenHandle, OUT PBOOLEAN Equal) { - KPROCESSOR_MODE PreviousMode; + KPROCESSOR_MODE PreviousMode = {0}; PTOKEN FirstToken, SecondToken; BOOLEAN IsEqual; NTSTATUS Status = STATUS_SUCCESS; This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Amteus PLC 57 Cardigan Lane, Leeds, LS4 2LE t:+44 (0) 870 8368770 f: +44 (0) 870 8368701 Registered in England No 4760795 http://www.amteus.com

1 0

Inability to work on RosDE/TE
by Alex Ionescu 01 Apr '07

01 Apr '07

Hi, I promised a new testing/development environment but unfortunately I cannot pursue my work because nobody has been able to fix rbuild to my requirements. If anyone does want to see the standardized environment I promised, please prod your local ReactOS developer for the following features: 1) *Working* ROS_INTERMEDIATE and ROS_OUTPUT directories. They are broken in many ways: a. Don't work with relative pats. b. Don't work at all for .pch files and/or compilation units. c. Create other sorts of unpredictable errors due to hard-coded strings/directories in makefiles or rbuild. 2) ROS_TOOLS_DIRECTORY. The ability for the tools to be outside the ROS_OUTPUT directory, such as in c:\rosde\tools. Someone committed such a patch but it was reverted without a newer version/fix. a. Also requires making rbuild check if the binaries are present, and if so, NOT to rebuild them. b. Create -forcetools switch to rbuild which would force it to bypass the check in 2a. 3) Tools must be built and work with the -O3 optimization setting. Of course, I won't go into the fact that my request for the other rbuild features such as a graphical dependency map have gone unanswered. Many thanks to those who _have_ worked on some of the MSVC features/bugfixes I brought forward and do the small attempt at a depmap. -- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

3 3

Re: [ros-dev] [ros-diffs] [fireball] 26210: - Revert useless commit: * No need to copy stuff from DDK, it's prohibited (#define _INC_NEWDEV) * #pragma was put there especially, and no reason to remove it was said * pushpack / poppack does not do anything if there a
by Alex Ionescu 30 Mar '07

30 Mar '07

While I agree in spirit with the revert, we should use DDK #defines for compatibility. Please re-commit that part. -----Original Message----- From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of fireball(a)svn.reactos.org Sent: March-30-07 11:39 AM To: ros-diffs(a)reactos.org Subject: [ros-diffs] [fireball] 26210: - Revert useless commit: * No need to copy stuff from DDK, it's prohibited (#define _INC_NEWDEV) * #pragma was put there especially, and no reason to remove it was said * pushpack /

1 0

Some Questions
by Daniel Nikolić 29 Mar '07

29 Mar '07

I recenly found out about this website. I checked out the sources (great) and tried to run React OS under VMware player (not so great) and even tried some of my sw to run under it (disaster!). I have a few questions: 1. I noted some inconsistencies in handling 8-bit/UTF-16 translation in ..A/..W calls between ...A functions in graphics (TextOut...) and synchronization (CreateSemaphore...). Graphics part always allocates memory (HeapAlloc) - a waste of time, IMHO. 2. I'm, not sure if is there a list of already checked/done, but not verified/not implemented API? 3. How could I help (I know some C) Regards, dn PS Meanwhile, I was reading Doxygen & could not figure out how MultiByteToWideChar() works (=i.e. how you implemented it), but I think it calls RtlMultiByteToUnicodeN(), which implements CP -> UTF-16 mapping for currently selected CP, and RtlCustomCPToUnicodeN() for any other CP. Some my programs use MultiByteToWideChar() with CP_UTF8 which is IMHO NOT implemented!?!? May I work on this (in my spare time)? Is somebody else working on this area?

2 1

Letting adding to Scan.Coverity.com
by theUser BL 28 Mar '07

28 Mar '07

Is it possible, that one of the official ROS-developer can contact http://scan.coverity.com/index.html to let also searched the ROS-code for bugs? Greatings theuserbl _________________________________________________________________ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden!

3 2

Re: [ros-dev] Some Questions
by Daniel Nikolić 28 Mar '07

28 Mar '07

We'll.... I found out how MultiByteToWideChar (MBTWC) is implemented, and looks OK. But then, there are following issues: 1 some functions (DefWindowProcA) call MBTWC, but with CP_ACP and HeapAlloc ALWAYS (IMHO should be: CP_THREAD_ACP, use some local cache if the 8-bit string is short enough, for performance) 2 some functions (GetMonitorInfoA) call MBTWC using CP_THREAD_ACP 3 yet other functions (RegisterClassExA) call RtlCreateUnicodeStringFromAsciiz and and RtlFreeUnicodeString later (no TEB cache, allocation ALWAYS) 4 and some other functions (CreateEventExA) call RtlAnsiStringToUnicodeString and use cache from TEB 5 other functions use RtlAnsiStringToUnicodeString with allocation, and RtlFreeUnicodeString later. 6 and some other functions (SetWindowTextA) call RtlAnsiStringToUnicodeString and RtlFreeUnicodeString (allocation ALWAYS) Is this inconsistent or what?! Best regards Daniel

1 0

About BUG 2093/2078
by João Jerónimo 27 Mar '07

27 Mar '07

I verified that bug occuring on a Pentium MMX, and then ran the liveCD on bochs with a breakpoint at the faulty instruction... It's a CMOVZ (Conditional MOVe if Zero flag set)... Conditional moves were introduced in Pentium II, but never mind! What *really* matters is that that code looks like resulting from compilation (because of the C calling convention clearly used, and no one uses C calling conventions in handwritten ASM code)... So..... Either this isn't a bug (and recompilation is required for non-default configurations), or there is a -march option when compiling the default LiveCD that shouldn't be there... Personally, I would go for the later... PS: Can I view a symbol map for the freeloader image in the prebuilt liveCD? JJ _______________________________________________________ Yahoo! Mail - Sempre a melhor op��o para voc�! Experimente j� e veja as novidades. http://br.yahoo.com/mailbeta/tudonovo/

1 0

SVN upgraded to 1.4.3
by Aleksey Bragin 26 Mar '07

26 Mar '07

Hello, I just finished upgrading svn.reactos.org to SVN 1.4.3. You should feel noticeable improvements - faster work and less traffic. However, if any problem arise, don't hesitate to email ros-general / ros-dev. For a full list of changes over previous version, please look to http://subversion.tigris.org. With the best regards, Aleksey Bragin.

1 0

Re: [ros-dev] Interest in ReactOS and some requets
by Aleksey Bragin 26 Mar '07

26 Mar '07

Hi and welcome, thanks for your offer to help - we were just discussing today in the irc-channel that there are some people in our current team who are willing to guide newbies through the process (get src code, build, run, modify something, try writing something new, send in patches, etc). If you have ability, please join #reactos on freenode irc network. If not, then email is allright (ask questions right here, so other can read and learn too). WBR, Aleksey Bragin. On Mar 13, 2007, at 11:33 PM, Arko Provo Mukherjee wrote: > Dear friends, > We are 3 undergrad comp sc. and IT students from India. We have > some coding experience but have never worked for the Open Source > Community as developers. Yet we have always admired the concept and > used FLOSS stuff like GNU/Linux. > We came across ReactOS project and got really interested in it. We > really want to contribute to the development of React OS and since > we are new in Open Source development, we would require your > guidance and support in stuff like understanding the code, building > the build environment etc. > Among other shortfalls that we have, we haven't programmed much on > Windows platform (almost always Linux ie) and hence know little > about the Windows API. But we are eager to learn and can definitely > learn parts of the API as long as you can guide us. > We humbly request you to guide us and give us some problems so that > we can try and support this community. A lot is left to be done in > ReactOS and it would be great being a part of such a project. > Also we are better at writing C codes than reading them ( like > almost everyone ;) ) and hence would request you to give us some > problems that we can write from stratch rather than bug fixing that > would require reading all codes. > But we are ready to contribute in any way you feel we can as > developers and support this community. > Regards > Arko Provo Mukherjee > Abhishek Biswas > Biswanath Banik

5 4

Thanks. ReactOS helped me develop and debug Windows drivers.
by Drew Scott Daniels 24 Mar '07

24 Mar '07

Hi, I wanted to extend my thanks to ReactOS developers. I have used the ReactOS source code on several occasions to help develop and debug drivers intended for Microsoft Windows (WDM NT). I also used it to help diagnose a hardware problem. The Vista Windows Driver Kit sometimes include sample driver code that will not work on systems newer than Windows 2003. I think I actually used OpenRCE.org to help figure this out, but ReactOS does a better job of letting me follow kernel level function logic. The new PREfast annotations are also poorly documented but I don't expect ReactOS will help with that. Perhaps its drivers could help though. One computer we had was bug checking (BSoD) with an NMI error with Windows XP. Microsoft's documentation on this was poor and sometimes misleading. Many other web sites provided incomplete (mostly just inquiries), or misleading information (speculation that the wrong hardware was at fault). With WinDBG, a search engine, and the ReactOS source code, I managed to find what hardware was generating the bug check. I then looked up the specifications from Intel and got quite a bit of a better understanding. I vaguely recall Walter Oney's WDM driver book provides a stub driver which will help newer Windows drivers run on older versions of Windows (although it's not redistributable and is documented as a workaround he doesn't want others to use). Pointers to this may help ReactOS driver developers. Making sure source code is easy to search with Google is very useful. I see that Google's source code search seems to search ReactOS, and there's some Doxygen documentation that can be searched. Unfortunately SVN or even other current source code seemingly cannot be searched without using alternate methods (such as downloading and searching offline). Ideally, something like lxr would be available for ReactOS, and through Google. I also have the same wish for the most recent version of the Linux kernel (Google doesn't seem to index lxr). Having more sample driver code (even third party) would certainly be useful. I'd like to sell companies on using ReactOS, but there seems to be a real anti production use message widely conveyed. I feel ReactOS is far more stable than is given credit. That said, it would be nice if even just some basic core part of ReactOS was stabilised (not even at a Desktop user level). By "stabilised", I mean if people could test and testify certain kinds of qualified stability (e.g. Version q ran x days, but it was only doing y and had z hardware). Also it would be nice to have even more information about changes to ReactOS that have/might make things likely to break (bugcheck, freeze, not behave...). At least one of the recent newsletters helped with that. I'd love to use ReactOS to replace simple Windows XP Embedded images (with many drivers and features stripped out). Once again, thanks for all the ReactOS efforts. I'm sure I do not yet fully appreciate the resources available to me because of ReactOS, but the ones I've found have been extremely useful. Drew Daniels Resume: http://www.boxheap.net/ddaniels/resume.html

2 1

replacement for winecalc
by Timo Kreuzer 23 Mar '07

23 Mar '07

Hi, Someone from the forum has written a replacement for winecalc and asks, if we would want to use it. I think it deserves some attention: http://www.reactos.org/forum/viewtopic.php?t=3585 - The code is smaller than winecalc. - It seems to (almost, see below) work correctly as far as I have tested (type 2+3*4 in winecalc and you will get 12 as result....) - brackets are working (not implemented in winecalc) - inv is working (not implemented in winecalc) - It looks a little better than winecalc "bugs" found so far: - there's an issue with foucs, that is put on a button when switching to another app - grad calculates with 200 instead of 400 = 360° - modulo and hyp seem unimplemented - you can't use and, xor, ... in dec mode Greetings, Timo

1 0

Re: [ros-dev] [ros-diffs] [janderwald] 26147: - fix makefiles to depend on TOOLS_OUT_ value than directly hardcoding it to $(OUTPUT)
by Aleksey Bragin 21 Mar '07

21 Mar '07

This breaks the very beginnings of the compile process. WBR, Aleksey Bragin. On Mar 20, 2007, at 11:12 PM, janderwald(a)svn.reactos.org wrote: > Author: janderwald > Date: Tue Mar 20 23:12:10 2007 > New Revision: 26147 > > URL: http://svn.reactos.org/svn/reactos?rev=26147&view=rev > Log: > - fix makefiles to depend on TOOLS_OUT_ value than directly > hardcoding it to $(OUTPUT) >

1 0

hello out there
by Tim Taubert 20 Mar '07

20 Mar '07

Hi, I am from Berlin, Germany and really interested in joining the ROS project as a developer. I started as proposed with digging into the code a little bit and wrote some patches. So my first question is, which developer (with svn write access) do i have to contact so that he can help my to review and (hopefully) apply some of my patches? Second thing is that i read that you are already planning a complete rewrite of the explorer code. I would really like to be a part of the explorer project but others are also welcome. If you have any idea how to start just let me know. With best regards, Tim Taubert

3 4

Summer of Code 2007?
by Nate DeSimone 20 Mar '07

20 Mar '07

Hi all, Is ReactOS doing SoC this year? I didn't see you on the list, though I know you did it last year. ~Nate DeSimone

3 2

Build problem ()
by Radu Bulboaca 16 Mar '07

16 Mar '07

Hi, I tried to build the ReactOS main trunk, but I've run into some problems. 'make all' fails with the message: mkdir: cannot create directory `obj-i386\\lib\\inflib_host': No such file or directory Up until now, I've got the 'trunk' directory from SVN (using TortoiseSVN), I exported the sources to a directory in the ros Build Environment (I was asked for that directory on install) and attempted to build from there. I also looked at the Makefile and set the '-mi' flag (ROS_RBUILDFLAGS = -mi), but that didn't help. Just for the record, I'm building on a WinXP SP2, using ReactOS Build Environment 0.3.5b2. I also tried the 0.3.4 version, but I run into the same issues. Do you have any ideas? Thanks, Radu

5 8

Re: [ros-dev] Endianess
by Tristan Miller 14 Mar '07

14 Mar '07

>Sorry for waiting until now to reply. It's all good. : ) >What do you think? I think we should convert to BE, but not away from PE-COFF. There are too many differences between them, and while it would be less work in the short term to switch to ELF, in the long term, implementing all of the features of PE would be very troublesome. Not the least concern is that information such as import data and file headers aren't even mapped into a process's address space with ELF. As I understand it, when you get an IHANDLE to a linked in DLL it's just a pointer to the mapped in PE file header. I'm sure there are programs that require this on a source level to run (which, for quite some time will be the only thing that affects us on the PowerPC side of things). That being said, a proper pe-powerpcbe target in gcc should then be the first priority. Binutils already more or less properly creates pe-powercbe files (with what I assume are your patches on the wiki, and a little monkeying to make sure that the MZ header and PE signature are always written as little-endian regardless of the target architecture). What kind of issues had you had on the EABI side of things, and what was your plan in more detail for emulating the features of PE in ELF? Also how much progress had you made in the port up to now? ~Tristan Miller (monocasa)

2 3

Interest in ReactOS and some requets
by Arko Provo Mukherjee 13 Mar '07

13 Mar '07

Dear friends, We are 3 undergrad comp sc. and IT students from India. We have some coding experience but have never worked for the Open Source Community as developers. Yet we have always admired the concept and used FLOSS stuff like GNU/Linux. We came across ReactOS project and got really interested in it. We really want to contribute to the development of React OS and since we are new in Open Source development, we would require your guidance and support in stuff like understanding the code, building the build environment etc. Among other shortfalls that we have, we haven't programmed much on Windows platform (almost always Linux ie) and hence know little about the Windows API. But we are eager to learn and can definitely learn parts of the API as long as you can guide us. We humbly request you to guide us and give us some problems so that we can try and support this community. A lot is left to be done in ReactOS and it would be great being a part of such a project. Also we are better at writing C codes than reading them ( like almost everyone ;) ) and hence would request you to give us some problems that we can write from stratch rather than bug fixing that would require reading all codes. But we are ready to contribute in any way you feel we can as developers and support this community. Regards Arko Provo Mukherjee Abhishek Biswas Biswanath Banik

2 1

How can I help?
by Sam Banks 11 Mar '07

11 Mar '07

Hi Guys I have recently discovered ReactOS through my research for Linuxforums.org, I have written an article on ReactOS, which should show up online in the near future. Basically I like your work and I would be keen to contribute some of my (unfortunately limited) time and skills to your project. I cant code but I can write ok. Could I be of any use to you guys? Cheers Sam -- Did you know that if you play a Windows XP cd backwards, you will hear the voice of Satan? That's nothing! If you play it forward, it'll install Windows XP.

2 4

Endianess
by Tristan Miller 11 Mar '07

11 Mar '07

Hey, Sorry, having problems with internet or else I'd ask this on IRC. I was curious as to why the emphasis on little-endian mode in powerpc. Mac G5's don't even have le-mode, and it definitely seems that (although im not totally sure, as theres not much info out in the wild yet) that the XBox360 lacks le-mode as well. Also, on the processors that support le-mode, it seems in all cases (although theres probably some embedded guy that I'm missing : P) that do support it, it's selectable at the minimum at the user/supervisor level with only a bit of work. Perhaps eventually a thunking layer (maybe a part of NTVDM, would it need to be that complex?) that would translate the calls from le usermode to a be kernel could be written, allowing one to run NT-PPC applications that are out there. We wouldn't be able to load drivers (or any le kernel code), but are there actually any PPC drivers out in the wild? Plus, it seems that it would definitely be a good thing for the kernel source to be tested on multiple endians as early as possible in its development to ease porting later on. ~ Tristan Miller (monocasa)

2 1

Re: [ros-dev] [ros-diffs] [ion] 26032: - Tree cleanups proposed on the mailing list. Move all non-Core OS modules to rosapps. Tests were already moved by Fireball to rostests.
by Aleksey Bragin 11 Mar '07

11 Mar '07

It's all about re-thinking what rosapps is. Initially it was supposed to be a place for various "app"lications. Right now it turned out to become a kind of a trashcan, where stuff unapplicable for trunk goes. Since this is wrong, it's perfectly fine to "force" devs to build with rosapps (and rostests, if they are interested in thorough testing) module. Otherwise, with make/make all, we again end up with rudimentary rosapps. Also there will be some kind of "unmaintained" module (undecided yet - discussions are welcome) where some stuff from rosapps is going to be moved (which is not currently maintained, and not interesting for devs). WBR, Aleksey. On Mar 9, 2007, at 2:38 AM, Ged Murphy wrote: > Upon thinking about this, I'm not sure it's such a good idea with > respect to usermode stability as it will get less testing now from > non-included apps. > > This would allow us to have the best of both world. > Many of the tests we run at application level rely on the apps which > have just been moved being easily accessable. > If these are gone, I suspect less feedback will be collected about the > status of usermode. > > Ged.

2 1

Re: [ros-dev] How can I help?
by Aleksey Bragin 11 Mar '07

11 Mar '07

Hi, yes definately. Our project would certainly benefit from a good PR and spread the word, because it eventually brings new developers and thus development speed rises. Thanks a lot, and feel free to email here or me. With the best regards, Aleksey Bragin. On Mar 8, 2007, at 3:20 AM, Sam Banks wrote: > Hi Guys > > I have recently discovered ReactOS through my research for > Linuxforums.org, I have written an article on ReactOS, which should > show up online in the near future. Basically I like your work and I > would be keen to contribute some of my (unfortunately limited) time > and skills to your project. I cant code but I can write ok. > > Could I be of any use to you guys? > > Cheers > > Sam

1 0

Re: [ros-dev] [ros-diffs] [ion] 26032: - Tree cleanups proposed on the mailing list. Move all non-Core OS modules to rosapps. Tests were already moved by Fireball to rostests.
by Ged Murphy 09 Mar '07

09 Mar '07

ion(a)svn.reactos.org wrote: > Author: ion > Date: Thu Mar 8 21:59:45 2007 > New Revision: 26032 > > URL: http://svn.reactos.org/svn/reactos?rev=26032&view=rev > Log: > - Tree cleanups proposed on the mailing list. Move all non-Core OS modules to rosapps. Tests were already moved by Fireball to rostests. > This will break 'make bootcd' Upon thinking about this, I'm not sure it's such a good idea with respect to usermode stability as it will get less testing now from non-included apps. Another idea, instead of moving everything out of the main trunk would be to give each component a new tag in rbuild. This tag could be something like core="yes|no". Everything which has been moved to rosapps could be labeled with a core="no" 2 new build commands would be available, make core and make corebootcd. This would allow us to have the best of both world. Many of the tests we run at application level rely on the apps which have just been moved being easily accessable. If these are gone, I suspect less feedback will be collected about the status of usermode. Ged.

2 1

Re: [ros-dev] [ros-diffs] [fireball] 25971: ReactOS FOSDEM 2007 talk slides
by Aleksey Bragin 04 Mar '07

04 Mar '07

I forgot to mention that I used Ged Murphy's .ppt as a base (design mostly), and I used some parts of information about the kernel given by Alex Ionescu. WBR, Aleksey Bragin. On Mar 3, 2007, at 4:18 PM, fireball(a)svn.reactos.org wrote: > Author: fireball > Date: Sat Mar 3 16:17:47 2007 > New Revision: 25971 > > URL: http://svn.reactos.org/svn/reactos?rev=25971&view=rev > Log: > ReactOS FOSDEM 2007 talk slides

1 0

Re: [ros-dev] Ros-dev Digest, Vol 31, Issue 1
by Aleksey Bragin 02 Mar '07

02 Mar '07

Setting autoreply while being subscribed to a mailing list - that's something not good to do. Unsubscribed... WBR, Aleksey Bragin. On Mar 2, 2007, at 2:02 PM, tim-sobolev wrote: > В связи с седлительностью сервера ящик обьявлен закрытым > Адресат переехал на tim тточчка sobolev сссоббаккка gmail ттточчка ком > _______________________________________________

1 0

Re: [ros-dev] Hello all
by Aleksey Bragin 02 Mar '07

02 Mar '07

Hi, thanks for your interest. Yes, Arty is indeed The Man to contact regarding the PPC port, but anyway post your questions here if you can't catch him on irc, and they will be answered sooner or later. WBR, Aleksey Bragin. On Mar 2, 2007, at 12:15 PM, Tristan Miller wrote: > Hey everyone, > I'm interested in becoming a kernel developer, especially with > the PowerPC port. Almost all of my experience comes from > supervisor code (or embedded systems without MMU's), or from type- > safe byte-code (and ironically enough, a weird combination of the > two). However, this would be the first project that I've worked > with others on. Any idea's where I should start. Those on IRC > specifically pointed out Arty in regards to the PowerPC. > > ~Tristan Miller

1 0

Re: [ros-dev] Ros-dev Digest, Vol 31, Issue 1
by tim-sobolev 02 Mar '07

02 Mar '07

В связи с седлительностью сервера ящик обьявлен закрытым Адресат переехал на tim тточчка sobolev сссоббаккка gmail ттточчка ком

1 0

Hello all
by Tristan Miller 02 Mar '07

02 Mar '07

Hey everyone, I'm interested in becoming a kernel developer, especially with the PowerPC port. Almost all of my experience comes from supervisor code (or embedded systems without MMU's), or from type-safe byte-code (and ironically enough, a weird combination of the two). However, this would be the first project that I've worked with others on. Any idea's where I should start. Those on IRC specifically pointed out Arty in regards to the PowerPC. ~Tristan Miller

1 0

Re: [ros-dev] [ros-diffs] [dgorbachev] 25911: Indonesian translation by Zaenal Mutaqin
by Aleksey Bragin 27 Feb '07

27 Feb '07

On Feb 27, 2007, at 3:04 AM, dgorbachev(a)svn.reactos.org wrote: > Author: dgorbachev > Date: Tue Feb 27 03:04:43 2007 > New Revision: 25911 > > URL: http://svn.reactos.org/svn/reactos?rev=25911&view=rev > Log: > Indonesian translation by Zaenal Mutaqin > > -= skip =- > trunk/reactos/ntoskrnl/mm/npool.c > I don't think that was intended, so please undo the change. WBR, Aleksey Bragin.

1 0

dcote info
by Dominic Cote 27 Feb '07

27 Feb '07

Hi, Just a quick email to let you know that I am a kernel programmer working with Alex. I am now working on the fsrtl lib. I am almost done with fastio.c at this point. Thanks --Dom

2 1

Re: [ros-dev] Marlett font
by mf 24 Feb '07

24 Feb '07

> Nevertheless the fonts should look fine with default settings. But it may look better with all features enabled. Fonts look fine, yes, but don't expect them to look better by adding bytecode which is IGNORED. Sigh, mf

2 1

Re: [ros-dev] Marlett font
by mf 24 Feb '07

24 Feb '07

Thomas Weidenmueller wrote: > No, the disabled functionality doesn't affect the output in any way > except speed. Only the byte code interpreter is affected by patents, but > the hinting is still done correctly, although slower. Exactly. This byte code is the hinting that Ged suggests embedding in our Marlett font. Of course freetype still hints, but it ignores the bytecode and works around it. Hence embedding hints in the TTF would be rather useless. Ask wierd_w, he's been having a lot of trouble with hinting and freetype. The only solution we could come up with is adding a hack for greyscale bitmap fonts that substitute the outlines for certain font sizes. mf

2 1

Re: [ros-dev] Marlett font
by mf 24 Feb '07

24 Feb '07

Hi, > Another area that will need attention is adding hints to all the glyphs and > making it a TTF. Patent pansies have disabled hinting in ReactOS' freetype. So hinting will do us no good, as hints are not parsed by the font engine. Regards, mf

2 1

Interesting article series about NT 6 ntoskrnl on MS TechNet
by Klemens Friedl 23 Feb '07

23 Feb '07

Inside the Windows Vista Kernel: Part 1: http://www.microsoft.com/technet/technetmag/issues/2007/02/VistaKernel/Defa… Inside the Windows Vista Kernel: Part 2: http://www.microsoft.com/technet/technetmag/issues/2007/03/VistaKernel/Defa…

1 0

Fwd: Important Daylight Savings Time Update for Developers
by David Johnson 22 Feb '07

22 Feb '07

Begin forwarded message: > From: "Microsoft US Developer Team" <developer(a)response.microsoft.com> > Date: February 22, 2007 11:54:45 AM CST > To: <davidjohnson.johnson(a)gmail.com> > Subject: Important Daylight Savings Time Update for Developers > Reply-To: "Microsoft US Developer Team" > <developer(a)response.microsoft.com> > > > > > Dear Valued Microsoft Customer, > > In 2005, the United States government passed the Energy Policy Act > of 2005. This act changes the start and end dates for Daylight > Saving Time (DST) as of spring 2007. These changes may impact the > way applications run. Microsoft is releasing an update for Windows > through Microsoft Update that reflects these changes. > > Developers who use the .NET Framework may find their applications > affected if the application uses the time zone information for > historical purposes or if they have derived custom classes from > System.TimeZone to provide custom time zone information. The > standard System.TimeZone class provides a managed wrapper for the > underlying Windows Operating System time zone functions. > > In addition, developers who use Visual C++ may find their > applications affected if they use the CRT time functions, or the TZ > environment variable. Microsoft is currently working on a fix for > this issue and will post information about its availability on the > Visual Studio Support page. > > Most applications that use these affected classes will not need to > be modified as this update will ensure that the correct data is > provided seamlessly to the application. However, applications that > use these classes or the underlying Windows API to perform > historical time look-ups will need to be modified. > > In most cases, developers who have extended the .NET Framework’s > time zone support by creating custom time zone classes derived from > System.TimeZone, or by direct access to the Win32 API, will not > have to update their applications as long as the available updates > to the operating system are applied. However, solutions that rely > on private time zone data, or that retrieve system time zone > information by accessing the registry directly, may need to be > updated. Applications that deal with historical time zone data may > also need to be updated. > > Microsoft advises all developers who make use of time zone data to > test their applications against this update to ensure that their > applications function correctly. > > For more detailed information and the latest updates please visit > http://msdn2.microsoft.com/en-us/vstudio/bb264729.aspx, Preparing > for daylight saving time changes in 2007, and KB928388: 2007 time > zone update for Microsoft Windows operating systems. > > Further Assistance > > Microsoft values your business. For more information visit http:// > www.microsoft.com/dst2007, or contact Microsoft for assistance. A > list of phone numbers is located at http://support.microsoft.com. > Microsoft Premier Customers may engage their Technical Account > Manager directly. > > Please DO NOT REPLY to this email as this is not a monitored inbox. > If you have questions/inquiries please visit http:// > www.microsoft.com/dst2007 > > This e-mail is intended for distribution within the United States. > Please contact your local Microsoft subsidiary for similar > offerings outside the US. > > Thank you, > > Microsoft US Developer Team > > > > > > > _________________________________ Dave Johnson http://www.davefilms.us DaveFILMS® San Diego, CA & Nashville, TN http://thevoicezone.us The Voice Zone™ Voice Talent Writer, Producer, Director Independent Audio Theater Producer Voice mail and Fax#:(206)350-2915 Skype & Msn Live messanger "DaveFilms"

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev