Ros-dev

ros-dev@reactos.org

2 participants
5791 discussions

Betov is move againts nasm32
by Magnus Olsen 10 Aug '07

10 Aug '07

Hi is betov are moreon or idot or brian dead person I can not longer keep my feeling in shape thanks to him It seam that betov is out damges every good open source project on the market. Let see now which project he is trying damges 1.ReactOS It is well known he dislike us, and my advice we ignore him it seam he does not known what his is talking about, and it seam in my eyes his claim is not vaild 2. Sano ReactOS borro some code from this project and that code betov trying convice it is illage 3. SDL Almost same code can be found in SDL for same part we talking about, the code are almost same as Sano code. That mean Betov trying destor this project as well 4. Nasm32 what he have gone after NASM 32, now and claim it is illage for they do not ship the source code in the binary. or the licen agreemtn, and some other stuff more we can read about his stupied http://groups.google.com/group/alt.lang.asm/browse_thread/thread/35cd7e11ff… it is not wonder people do not take him serius he is like a big moron and trying sabtages opensource project world wide for people do not support his rosasm project. And I have follow now his writting for few month and more I read, more it seam it is something wrong with his brain. he calling people with bad names and attact people when they ask him simple question, it mean he socal skill is bad or is is brain dead, that is my cludtions after reading his vaurs stuff he writitning on the net. Or even better bethov is getting pay leading sabtages agaist opensource project that is well known, He maybe getting pay from MS/DMCA/NOVELL how knowns, but it seam not in this case it seam he is complete brian dead.

1 0

crash in rbuild creating vcproj
by ich 09 Aug '07

09 Aug '07

Hello list, I'm new here, so at first I'd like to greet everyone ;) second: I had some problems running rbuild on WinXP SP2 self compiled with msvc 8.0 (Express) to produce .vcproj files. I've found the problem in vcprojmaker.cpp and another thing, which prevents me from building rbuild in genguid.cpp and I would like to contribute a patch. Kind regards, Michael Sprauer

1 0

Re: [ros-dev] RosBuild Release Build Problem
by Aleksey Bragin 09 Aug '07

09 Aug '07

Fixed in 28257. WBR, Aleksey Bragin. On Aug 9, 2007, at 9:37 AM, James Tabor wrote: > ./include/internal/kd.h:212:KdpKdbgInit( > > obj-i386/ntoskrnl/kd/kdinit.o: In function `KdInitSystem@8': > /mnt/reactos/fullrel/build/ntoskrnl/kd/kdinit.c:(.data+0x24): > undefined reference to `_KdpKdbgInit@8'

1 0

XP, System Call List, Wrong size?
by James Tabor 09 Aug '07

09 Aug '07

From the SDK! Come on! get upto date! W32KAPI BOOL APIENTRY NtGdiAlphaBlend( __in HDC hdcDst, __in LONG DstX, __in LONG DstY, __in LONG DstCx, __in LONG DstCy, __in HDC hdcSrc, __in LONG SrcX, __in LONG SrcY, __in LONG SrcCx, __in LONG SrcCy, __in BLENDFUNCTION BlendFunction, __in HANDLE hcmXform // I saw a zero here. ); We have this in psdk/ntgdi.h W32KAPI BOOL APIENTRY NtGdiSetIcmMode( IN HDC hdc, IN ULONG nCommand, // see below,,,, I saw 1 -> 4 here. IN ULONG ulMode ); /* NtGdiSetIcmMode */ #define ICM_SET_MODE 1 #define ICM_SET_CALIBRATE_MODE 2 #define ICM_SET_COLOR_MODE 3 #define ICM_CHECK_COLOR_MODE 4 Using a good hook and compare eax to the list will set you free. James

1 0

RosBuild Release Build Problem
by James Tabor 09 Aug '07

09 Aug '07

./include/internal/kd.h:212:KdpKdbgInit( obj-i386/ntoskrnl/kd/kdinit.o: In function `KdInitSystem@8': /mnt/reactos/fullrel/build/ntoskrnl/kd/kdinit.c:(.data+0x24): undefined reference to `_KdpKdbgInit@8' ntoskrnl/include/internal/ntoskrnl.h: #include "ldr.h" #ifndef _WINKD_ #include "kd.h" #else #include "kd64.h" #endif #include "fsrtl.h" ntoskrnl.rbuild : snip.... <define name="_IN_KERNEL_" /> <if property="_WINKD_" value="1"> <define name="_WINKD_" /> snip.... <file>pnproot.c</file> </directory> </directory> <if property="_WINKD_" value="0"> <directory name="kdbg"> <if property="ARCH" value="i386"> snip.... <file>kdmain.c</file> </directory> </if> <if property="_WINKD_" value ="1"> <directory name="kd64"> <file>kdapi.c</file> snip.... Does this help in finding the problem? James

1 0

rev 28153 (obhandle.c)
by Timo Kreuzer 08 Aug '07

08 Aug '07

rev 28153 (obhandle.c) breaks bootcd with KDBG = 1 "Assertion 'HandleTable->HandleCount == 0' failed at ntoskrnl\ob\obhandle.c line 2034"

1 0

r28205 : Empty ntoskrnl/ke/i386/init.S in trunk
by Sylvain Petreolle 07 Aug '07

07 Aug '07

After r28205, ntoskrnl/ke/i386/init.S has no more contents and is removed from build. Remove it from trunk too. 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

1 0

Re: [ros-dev] CRT source code issue
by Aleksey Bragin 06 Aug '07

06 Aug '07

Yes, the whole issue is at pushing operands to stack, performing well- documented assembly instructions to perform the asked action (div, mul, shl, shr, etc), and handling some special, though obvious, cases (like if you do a shl of some longlong number by more than 64 bits, you always end up with 0, there is no need to call math instructions in order to compute this). I will let you know results when I speak with SDL. WBR, Aleksey Bragin. On Aug 4, 2007, at 8:52 PM, Daniel Hazelton wrote: > On Saturday 04 August 2007 12:28:09 Aleksey Bragin wrote: > > I can't see where that file has anything to do with the functions > (e.g: > sqrt()/alldiv()) that Betov claims are duplicated. (I've gone > through that > file and can't find any single place where it does any more math than > controlled bit-shifts. No advanced math or anything.) > > While there might be similar code, for, say, memory barriers, that > codes > construction would be dictated by the specification of the target > machine > (and, to some extent, the OS). If the code for sqrt/alldiv is the same > between SDL/ROS I don't see a problem - they are both GNU projects > and "cross > pollination" like that is legal. > > Whats more is that, while assembly is abstract enough to let some > things be > done in more than one way, most of the more complex functionality - > like math > algorithms - are so limited in the possibilities of variation that > I can > easily see two unconnected people arriving at the exact same > solution. QED: > Even if the code appears identical (except for things like variable > names, > et. al) there is a compelling reason for it and it does not mean > the code has > been copied in any way, shape or form. (And if you look at the ROS > commit > history I'm sure the code in question existed before MS released > the SSCLI2.0 > source. Which means that the code can't be an "illegal use of MS > property" - > it was around before said property was available). > > ...Okay, enough of this outsider sticking his neck out. I've said > enough and > it's time to disappear and wait for a really usable version of ROS > to hit. > (though I have compared it to XP under Qemu and ROS rocks!) > > DRH

1 0

Re: [ros-dev] CRT source code issue
by Aleksey Bragin 04 Aug '07

04 Aug '07

Just so people don't build up rumours, this code is located in SSCLI 2.0, in the file clr/src/vm/i386/jithelp.asm . Function names are different, however assembly code is similar. License issues are not fully cleared up, so opinions from people having knowledge in this area are welcome. WBR, Aleksey Bragin. On Aug 4, 2007, at 7:52 PM, Daniel Hazelton wrote: > On Saturday 04 August 2007 04:32:32 Mike Swanson wrote: >> On Friday 03 August 2007 16:28:21 Daniel Hazelton wrote: >>> unless you hold full copyright to the software (ie: you are the >>> one who >>> has released it under the GPL) then there is no way you can >>> distribute it >>> for commercial purposes. (You can make money to cover >>> distribution costs >>> and/or make money from support but not off the software itself.) >>

2 1

CRT source code issue
by Aleksey Bragin 04 Aug '07

04 Aug '07

Hi, Recently Betov made some accusations regarding possible usage of MS's copyrighted code in ReactOS's CRT library (example lib/sdk/libcntpr/ math/i386/sqrt_asm.s, alldiv_asm.s, and other files). Here is my official statement in regarding to this false accusation: This source code originally was imported into ReactOS from SanOS project, where it was said as having GPL license (all original copyrights are kept). After a lot of complains from Betov (aimed at getting attention to his own project, not at improving ReactOS), developers thought it worths looking into the issue deeper. I performed some investigation, and found that SDL project (www.libsdl.org) has the same code in trunk and in v1.2 branch (http://www.libsdl.org/cgi/viewvc.cgi/trunk/SDL/src/stdlib/ SDL_stdlib.c?view=markup). Everyone can compare asm source code with respective functions found in MSVC's CRT source code. It matches up to label names, however numbers have been converted from dec to hex representation. The code in SDL project is marked as "GPL" and author is stated as "Sam Lantinga". It may look like a serious problem, but in reality, the source code of these functions is released by Microsoft in SSCLI 2.0, with a license which allows GPLing of the source code, with one restriction: "You may not use or distribute this Software and any derivative works in any form for commercial purposes.". SSCLI 2.0 can be freely downloaded by everyone, license is also certainly available to read. I'm going to communicate with SDL about this issue, but since ReactOS is not used commercially, it's not a problem for ReactOS now. We are ready to collaborate with SDL on removing this issue, if it's considered a real problem. With the best regards, Aleksey Bragin.

4 4

Jump to page:

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