Ros-dev

ros-dev@reactos.org

1 participants
5793 discussions

win32k public headers
by Timo Kreuzer 03 Apr '08

03 Apr '08

I am currently trying to clean up our win32k headers. The situation so far: - ntgdi.h in psdk which should be compatible to ms version of ntgdi.h from the sdk - ntgdytyp.h containing a bunch of gdi related types in include/reactos/win32k - ntgdihdl.h containing handle related types and macros in include/reactos/win32k - ntgdibad.h containing private and ms incompatible functions and structures in include/reactos/win32k - ntuser.h containing ntuser functions and types in include/reactos/win32k - ntusertyp.h containing ntuser related types in include/reactos/win32k - W32CLIENTINFO is defined in both ntusertyp.h and ntgdityp.h (less complete). - there is the PATRECT structure in ntuser.h, and if ntuser.h is not included, also in ntgdityp.h, this should be named POLYPATBLT as defined in ntgdi.h, but there is only an incomplete type without the structure definition. (IMO ms should have put this structure into wingdi.h together with PolyPatBlt, but they don't seem to want anyone use that gdi32 exported function.) I wonder why ms put ntgdi.h into the sdk at all, as it's completely useless to user mode application writers, but well, ncie to have the prototypes ;-) So how do we clean up this mess? Suggestions: - when ms puts ntgdi.h into the sdk, we could also put ntuser.h there. - if we want to stay 100% compatible with sdk headers, we can add a define, like #ifdef USE_NON_SDK // put non sdk compatible but still windows compatible definitions here #endif - use a version definition, like I did with the simplecall definitions in ntuser.h to make it compatible to different windows versions - keep ntgdibad.h and create ntuserbad.h for incompatible definitions - ntgdihdl.h is used by win32k and gdi32, both also import ntgdityp.h. So I'd suggest merging that stuff into ntgdityp.h - maybe merge types into ntgdi.h and ntuser.h? Some definitions are already in there. - create win32ktypes.h and put ntuser/ntgdi shared stuff there, like W32CLIENTINFO - maybe add POLYPATBLT and PolyPatBlt() (others?) to wingdi.h inside USE_NON_SDK ifdef plus a POLYPATBLT_DEFINED I don't think it's a problem to make our sdk headers more complete than ms ones. This might help if we don't want a header mess or extra definitions inside the .c files. Comments appreciated. Thanks, Timo

2 3

[ros-diffs] [tkreuzer] 32743: - make Simplecall definitions (NtUserCallXxx) compatible to different Win versions
by James Tabor 02 Apr '08

02 Apr '08

Hi! Thank you Timo, I can not believe I missed this one.... This fixes a commit back at rev 14041. With out starting a review in real world history,, once an enemy gains control the first thing they do is erase history. New eras evolve and build on top of old ones. Our old world ruins are a good example. Look at Cuzco, Greece and Rome. You see them now uncovering the past. Thanks again! James

1 0

A question about SepCreateSystemProcessToken
by Xiaoming Gao 24 Mar '08

24 Mar '08

SepCreateSystemProcessToken calls ObCreateObject like this: Status = ObCreateObject(KernelMode, SepTokenObjectType, NULL, KernelMode, NULL, sizeof(TOKEN), 0, 0, (PVOID*)&AccessToken); the ObjectAttributes parameter is set to NULL,and ObCreateObject passes ObjectAttributes to call ObpCaptureObjectAttributes like this: Status = ObpCaptureObjectAttributes(ObjectAttributes, ProbeMode, FALSE, ObjectCreateInfo, &ObjectName); and in ObpCaptureObjectAttributes ,there's a check condition that checks if ObjectAttributes is NULL, if ObjectAttributes is NULL,it will cause ObpCaptureObjectAttributes fail,and then cause ObCreateObject fail,then cause SepCreateSystemProcessToken fail,and the return value of SepCreateSystemProcessToken will ever be NULL. Could someone explain why???am i wrong??

1 0

ReactOS 0.34 (Installation CD) issues
by Bernd Blaauw 23 Mar '08

23 Mar '08

While installing and using ReactOS 0.34 (on Windows XP Professional with VmWare Workstation 6.03) I'm experiencing a couple of issues. - Are there any new requirements to install ReactOS? 586+ with 64MB for example instead of earlier 486+/16MB ? - Are there any new requirements to bootup ReactOS? 586+ with 64MB? would/should swapfile work with lower amount of system memory installed on the machine? - Are there any new requirements to use ReactOS? 586+ with 64MB? Does swapfile work? - Is commandline-only supported on machines with not enough memory installed? Ofcourse booting from CD has to be supported on the target machine, either natively or through tricks like Smart Boot Manager or GRUB(-4-DOS) (or FreeLDR even?). The actual trouble I'm having is completing 0.34's installation process with Dutch language and USA keyboard layout (which isn't default, you seem to prefer Belgium keyboard layout by default, which might be just as strange as a Dutch keyboard layout by default. Those keyboards hardly exist at all). It seems to hang on this machine at a random moment of time during the file copy phase. In the end, I cannot install FreeLDR to diskette (empty WinImage 1.44MB diskette image), nor can I return to previous screen to select "install to harddisk". My goal was having a FreeLDR bootdisk in case I mess up the partition bootsector. Anyway, using English as installation language and its defaults, I can complete SETUP properly. While in ReactOS booted from harddisk, opening a simple console window (CMD) and doing DIR A: results in a blue screen (instead of a message like "no floppydrive installed") Same issue as known earlier I guess - non-working floppydrive(r). My old FreeLoader diskette is based on a FreeLDR bootdisk that Casper Hornstrup(?) had available at the time. It's available from http://odin.fdos.org/odin2005/ Booting the diskette, pressing CTRL-C, then doing a simple COPY /Y C:\FREELDR.SYS A:\FREELDR.SYS does the trick for updating FreeLDR from 2.xx to 3.xx, resulting in being able to boot ReactOS 0.34 from a diskette. Strangely enough no single DOS tool/command can handle FREELDR.INI (copy, ren, del, edit, all fail) - any idea why? Last of all, SHUTDOWN doesn't shut off the computer (guess you want to be sure everything in cache is flushed?), and LOGOFF won't allow me to get out of entering my username and password. Looking forward to a ReactOS with OpenOffice and FireFox 3.xx in a while, Any help, ideas or recommendations much appreciated (as well as pointing me to the correct mailinglist if it shouldn't be ros-dev) Bernd Blaauw

1 0

Reactos booting to CLI
by Marc Piulachs 19 Mar '08

19 Mar '08

As we know Windows (at least till Windows 7) was designed to be a GUI based operating system. All applications can safely assume that the windowing subsystem is running. Windows/Reactos can run native applications without starting the windowing subsystem like usetup during 1st stage setup but of course without having access to Win32 apis as Win32k is not loaded. AFAIK win32k is designed to be the main subsystem and is the responsible of starting the windowing subsystem so my question is . Would be technically possible to have a striped win32k version without the GUI code? + command line enabled winlogon, syssetup etc.. so you can boot and run cli based applications like cmd.exe ? what other parts of the boot process relay on having the GUI running? It's more of a design curiosity question rather than a real request Regards, Marc

5 5

Regarding Tsonic OS (2)
by David Eckert 15 Mar '08

15 Mar '08

whoops, -fairview, i meant the FBI lol :P -- -David W. Eckert

1 0

Regarding Tsonic OS
by David Eckert 15 Mar '08

15 Mar '08

With regards to Tsonic OS, It would be very advisable at this point to get all DNS information and ISP information and report this individual(s) to either their ISP or Fairview, or perhaps both. -- -David W. Eckert

1 0

Re: [ros-dev] Hello , we are searching for people with programing skills for the operating system Tsonic OS.
by Mark Tempel 13 Mar '08

13 Mar '08

Two things: 1) Please take me off your list. I know that you pulled my email address from the reactos mailing list. Since your project is not reactos, I'm not interested in hearing about it. 2) Posting links to leaked Microsoft source code in any forum related to reactos shows a complete lack of good judgment, and a lack of knowledge of recent reactos history. I certainly hope that you don't intend to try to check a derivative of leaked Windows source into the reactos tree. That would taint reactos and make it vulnerable to legal action (at least here in the US). Further, since you are acting as a spokesperson for TonicOs, and are passing around links to stolen Microsoft intellectual property, I would consider TonicOs already tainted. Please take conversations about leaked Windows source to some other venue. --mark On Wed, 12 Mar 2008 12:44:18 -0800 "Tsvetan Banchev" <tsvetanmail(a)gmail.com> wrote: > http://[cut]/Windows_2000_source_code > http://[cut]/Windows_XP_Source_Code > obtained from a friend inside ms ;) > > rar password needs cracking, working on it now. could >take a few days. if > anyone's got a high end machine it'd be appreciated if >they could use a RAR > password recovery app to get it.

3 2

Re: [ros-dev] [ros-diffs] [fireball] 32667: - Fix build.
by Steven Edwards 13 Mar '08

13 Mar '08

Hi, On Wed, Mar 12, 2008 at 2:07 PM, <fireball(a)svn.reactos.org> wrote: > Author: fireball > Date: Wed Mar 12 14:07:32 2008 > New Revision: 32667 > > URL: http://svn.reactos.org/svn/reactos?rev=3D32667&view=3Drev > Log: > - Fix build. > > Modified: > trunk/reactos/ntoskrnl/ntoskrnl-generic.rbuild > > Modified: trunk/reactos/ntoskrnl/ntoskrnl-generic.rbuild > URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ntoskrnl-gen= > eric.rbuild?rev=3D32667&r1=3D32666&r2=3D32667&view=3Ddiff > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D Diffs have been broken since the recent email problems. Is there any estimate on when/if this is going to be fixed? 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

1 0

Re: [ros-dev] [ros-diffs] [greatlrd] 32652: part 2/2 for implement GetAppCompatFlags left todo implemented set AppCompatFlags
by Aleksey Bragin 11 Mar '08

11 Mar '08

Why did that big chunk of MS's support database text got into our codebase? Even not edited, so that I can read up about "tax form 1040 would not print correctly" in ReactOS Source code? What is the use from it? If you wanted SO MUCH, you could at least edit it, or ask someone to edit it for you (we have quite a few people in our team). But then, I could insert half of WDK docs into the kernel source code and drivers source code (which in fact would violate copyrights, since it would not even be fair use). Providing URL is quite enough, though, if I don't mistake (I'm not up to date with their position), Wine is already removing URLs from source code because they should be kept somewhere else. Source code is source code, not a collector to store everything. There is no point in sticking various garbage into reactos source code with a note "so it doesn't get lost", we've come over that point quite a few years ago. With the best regards, Aleksey Bragin. On Mar 11, 2008, at 3:09 AM, greatlrd(a)svn.reactos.org wrote: > Author: greatlrd > Date: Mon Mar 10 19:09:23 2008 > New Revision: 32652 > > URL: http://svn.reactos.org/svn/reactos?rev=3D32652&view=3Drev > Log: > part 2/2 for implement GetAppCompatFlags > left todo implemented set AppCompatFlags = > > > Modified: > trunk/reactos/dll/win32/user32/misc/stubs.c > > + /* NOTE : GetAppCompatFlags retuns which compatible flags should > be send= > back = > > + * the return value is any of http://support.microsoft.com/kb/82860 > + * This text are direcly copy from the MSDN URL, so it does not > get lost > + > *--------------------------------------------------------------------- > -= > -------- > + * Bit: 1 Lots of text here > + = > > + return ti->dwAppsCompatibleFlags; > } > = > > /*

2 1

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