Should ReactOS copy unnecessary restrictions that Windows has?
The example I'm thinking of is NtSetLdtEntries. In Windows NT (and
currently ReactOS as well), this function will not let you create an LDT
entry whose limit is above the user/kernel barrier. This restriction sounds
like it was made with security in mind, but it doesn't affect security. The
processor's page table will already block access to kernel memory no matter
what selector you use. After all, the default user CS and DS already have a
limit of FFFFFFFF.
Should such a problem be fixed?
Fireball said "no, unless some 3rd party app or driver depends on them" when
I asked about whether such restrictions should be copied. Pretty much the
only thing using NtSetLdtEntries is NTVDM, and this restriction already
causes some DOS programs to break that would otherwise work. (Such programs
are usually setting selectors that wrap the address space.)
Melissa
I've noticed that in the ReactOS source code, there are many places where a
parameter or structure is ULONG when it should really be SIZE_T. Using
ULONG instead of SIZE_T is not portable. It will be difficult to port
ReactOS to x64 and Itanium in the future because of this.
I think the project should stop the bleeding by requiring all new code to
make proper use of ULONG versus SIZE_T. This does mean going against the
documentation of native syscalls on the Internet, but it must be done
sometime.
Of course, I'm not really part of the project...
Melissa
Hi all
Could be all based on wine patches, I can no longer get xchat 2 and the new one to run. I noticed it
can not find the lib directory in the launch directory. Wine has this problem too. Also when
installing the new X-Chat 2 from http://www.silverex.org/download/xchat-2.6.2-1.exe, It installs the
Font to C:\ReactOS\Fonts not C:\ReactOS\media\fonts. I had to create C:\ReactOS\Fonts so I can have
a clean install.
I tested my GGO patch and the SVN and the result are the same.
Okay, wine does this too, I tested it.
(dll/ntdll/ldr/utils.c:2019) Failed to create or open dll section of 'libgtk-win
32-2.0-0.dll' (Status c0000135)
(dll/ntdll/ldr/utils.c:1347) failed to load libgtk-win32-2.0-0.dll
(dll/ntdll/ldr/utils.c:1812) failed to load libgtk-win32-2.0-0.dll
(dll/ntdll/ldr/utils.c:1934) LdrFixupImports() failed for xchat.EXE
(dll/ntdll/ldr/startup.c:485) Failed to initialize image
Then do it from lib, "..\xchat"
(dll/ntdll/ldr/utils.c:2019) Failed to create or open dll section of
'pango-1.8.2/lib/pango/1.4.0/modules/pango-basic-win32.dll"' (Status c0000135)
You will get a popup.
This has been a problem for years!
Thanks,
James
Hi,
I'm getting this with Mozilla, Firefox and SeaMonkey.
KeBugCheck at ntoskrnl/cm/regobj.c:528
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
Technical information:
*** STOP: 0x00000051 (0x00000000,0x00000000,0x00000000,0x00000000)
Frames:
<ntoskrnl.exe:1d50 (ntoskrnl/ke/bug.c:493 (KeBugCheckEx))>
<ntoskrnl.exe:1d67 (ntoskrnl/ke/bug.c:514 (KeBugCheck))>
<ntoskrnl.exe:129c6 (ntoskrnl/cm/regobj.c:528 (CmiObjectDelete))>
<ntoskrnl.exe:52c6b (ntoskrnl/ob/oblife.c:151 (ObpDeleteObject))>
<ntoskrnl.exe:1290c (ntoskrnl/cm/regobj.c:523 (CmiObjectDelete))>
<ntoskrnl.exe:52c6b (ntoskrnl/ob/oblife.c:151 (ObpDeleteObject))>
<ntoskrnl.exe:50f4c (ntoskrnl/ob/obhandle.c:153 (ObpDecrementHandleCount))>
<ntoskrnl.exe:510b0 (ntoskrnl/ob/obhandle.c:244 (ObpDeleteHandle))>
<ntoskrnl.exe:52166 (ntoskrnl/ob/obhandle.c:1125 (NtClose))>
<ntoskrnl.exe:66527 (ntoskrnl/ke/i386/trap.s:306 (KiFastCallEntry))>
<ADVAPI32.dll:7dd9 (dll/win32/advapi32/reg/reg.c:1178 (RegDeleteKeyA))>
All three are the same,
James
I cant seem to make a stable qemu install for the release, wmare works
fine though. On the first boot to the installed desktop, it just shuts
down after about 1 sec. I usually see the device wizard pop up for a
sec and then it just turns off. Anyone else having thse problems? Any
hints?
Brandon
Do we have a target harware spec?
Or will ROS be for general harware like regular Windows?
--
Dave Johnson
http://www.davefilms.us DaveFILMS(r)
http://thevoicezone.us The Voice Zone™
Voice Talent
Writer, Producer, Director
Independent Audio Theater Producer
http://www.perditioncity.us
voiceoverjobs(a)gmail.com
Member of the Darker Projects team.
http://www.darkerprojects.comShadoeWorld.com Correspondent
----------------------------------------------------------
Tired of a proprietary Windows on your computer ?
Use free ReactOS instead ( http://www.reactos.org )
0.3.0 is now RC1. Hopefully Brandon will have time to put up RC1 on
SF soon, but those inclined can check out a copy now. While I will
allow a wallpaper to be added before release, anything else needs to
be a bugfix against a bug in Bugzilla.
WD
--
ReactOS is a hub, follow the spokes and you'll
immediately find absolutely everything you need
to know about Windows. ReactOS is not just
software, it's people.
kjk_hyperion
My name is Kate Chauca and I represent MSCoder Independent magazine for
developers using Microsoft platforms (www.mscoder.eu/es).
We would like to invite all of you to help us to promote ReactOS. We are
looking for people who will write articles about ReactOS for our magazine.
We would like to place live ReactOS on the CD of our magazine.
If you find it interesting please let me know. Every one can cooperate with
us.
Best Regards
Kate Chauca
katarzyna.chauca(a)software.com.pl
www.mscoder.eu/es
There are three integrated systems needed for authentication in ReactOS:
1. Winlogin
2. MSGINA (ROSGINA would work better, no?)
3. Some sort of Identity Management system with support for local and
remote authentication (remote can come with SMB support later)
Tiers 2 & 3 can be developed and tested on a non ReactOS system (aka a
real Windows system) initially (tho with the code staying in the ROS
Subversion tree), while Tier 1 is ReactOS specific.
I thus see three stages (aligned with the systems mentioned above):
1. Identity Management System with basic tools (get Setup to use it, at
least some basic command line tools to add and remove users and change
passwords, no need for a UI yet)
2. A ROSGINA that uses the Identity Management System
3. Get Winlogin back up and running and using the ROSGINA for
authentication.
Since its stage 1:
The identity management system's sole purpose is to create a
cross-subsystem, ReactOS-wide way to authenticate users. How each
subsystem uses the information provided is up to the individual
subsystem. As such, I see a database (Berkerly DB or Sqlite) of users
(and possibly a separate one with groups) with some basic metadata
describing the user:
1. Username
1. Real Name / Nickname
2. Encrypted Password (encrypted with a choice of algorithms, AES,
Blowfish, etc..)
4. Groups user belongs in (by name)
Any other metadata that should be stored in the authentication database?
The identity management system's API can be quite simple:
BOOL AuthenticateUserA( LPCSTR username, LPCSTR password );
BOOL AuthenticateUserW( LPCWSTR username, LPCWSTR password );
Basically, returning a TRUE if the particular user is valid and FALSE
otherwise. Other APIs to get other metadata can come later?
Any other ideas?
--Justin Haygood
justin.haygood(a)gmail.com
There has been very little activity in 0.3.0, so I am putting out a
last call before feature freeze. If no one comes forward, we will
feature freeze during the weekend so we can start bughunting.
I've also bumped trunk to 0.4.0-SVN, and created an 0.3.0 entry in Bugzilla.
WD
--
ReactOS is a hub, follow the spokes and you'll
immediately find absolutely everything you need
to know about Windows. ReactOS is not just
software, it's people.
kjk_hyperion
I'm interested in translate any article about ReactOs or the ReacOs to
Portuguese.
What article is interesting to Brazilian comunity?
How can I help to translate the ReactOs to Portuguese?
Thanks,
Sandro.
Looks like r22100 breaks the build (at least for me):
[CC] ntoskrnl\cm\ntfunc.c
ntoskrnl\cm\ntfunc.c: In function `NtCreateKey':
ntoskrnl\cm\ntfunc.c:474: warning: implicit declaration of function
`ObpReleaseCapturedName'
make: *** [obj-i386\ntoskrnl\cm\ntfunc.o] Error 1
The ReactOS website frontpage content has remained the same for
several months and it has lead to some confused visitors who has asked
a lot questions in the forums.
We need a high quality text for the frontpage which need to be
reviewed by native speekers. The current text is good, but not
brilliant. There is for example no single line where it states that
ReactOS not using the linux kernel. Or the following sentense is not
optimal: "Finally, a FOSS operating system for everyone!". End-User
does not need to know what "FOSS" is nor any other technical slang.
This are just a few example which shows some downsides of the current
frontpage content.
I am talking about the following page:
http://www.reactos.org/xhtml/en/index.html
... to be exactly, the main part, starting with "ReactOS Project" and
ending with the "W3C" icons.
Please take some time and review the text and post your suggestions
here (ReactOS Mailing List).
The text does not have to have the same length or same
structure/layout. It would be great to have a longer text splitted up
into several sub-topics suitable for a website frontpage.
Visit other website's and compare the content.
To sum up, we need a lot of volunteers (with good english language and
grammar knowledge) who want to help ito improve the ReactOS website.
Even if you are not a native speaker and/or not good in english, you
are welcome to post your suggestions/ideas/etc.
I hope this email will get a lot of response and I am looking forward
to an efficient conversation.
Klemens Friedl
ReactOS Dev & Website Admin
http://www.reactos.org
amunger(a)svn.reactos.org schrieb:
> Author: amunger
> Date: Fri May 26 19:14:13 2006
> New Revision: 22052
>
> URL: http://svn.reactos.ru/svn/reactos?rev=22052&view=rev
> Log:
> Bump trunk to 0.4.0, no turning back now.
Wouldn't it be smater set it to 0.3.1 ? I mean the next version is 0.4.0
actually very unlikely.
Maarten Bosma
Hi,
It is based on Wine implementation. It has other hax with it mostly tests.
There is a hax for NtGdiGetCharABCWidths to allow it to pass one of the
"gdi32_crosstest font" tests.
Over all, it is truly Ugly and going to change. WYSIWUG ATM.
Thanks,
James
I was just looking at the graphics system at many open source
operating systems. Seems to be most of them rely on other engines to
take care of their GUI system. I was thinking what about creating a
GUI or Window Server that draws MPEG2 or MPEG4 compliant graphics.
This implention is wrong please revert it
it shall and must be implement in win32k not direcly to gdi32
NtGdiGetCharWidth
----- Original Message -----
From: <jimtabor(a)svn.reactos.org>
To: <ros-svn(a)reactos.org>
Sent: den 21 January 2006 01:52
Subject: [ros-svn] [jimtabor] 20958: Port Wine GetCharWidth32A.
> Port Wine GetCharWidth32A.
>
>
> Updated files:
> trunk/reactos/lib/gdi32/objects/font.c
>
> _______________________________________________
> Ros-svn mailing list
> Ros-svn(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-svn
I think few of the devs ever read the Design forum (???)
There are a some nice GUI designs, mostly done with a drawing program.
So I thought it would be great to make those designs available inside
ROS. Some of them (I think kokodin made a good and quite good
programmable design) could be done by changing the user32 code, but it's
not a good idea to make theming by changing user32 code. So I had the
following idea: all code really needed to draw the GUI elements could be
exported into an external dll (gui.dll or something like that) so some
basic theming would be pretty easy and still fast. We would only need a
kind of GUI API that would allow changing most things, but would not be
too complex.
What do you think of this?
If you think it's a good idea, I would try to outsource the gui code out
of user32 and try to develop a basic and a secondary (based on kokodin's
design) dll.
greatlrd(a)svn.reactos.org wrote:
> Author: greatlrd
> Date: Fri May 26 23:23:34 2006
> New Revision: 22062
>
> URL: http://svn.reactos.ru/svn/reactos?rev=22062&view=rev
> Log:
> replace djgpp hell bugs fcvtbuf with project http://www.jbox.dk/sanos/source/lib/fcvt.c.html with small modification's to match ReactOS arch. Floating point to string conversion routines Copyright (C) 2002 Michael Ringgaard. All rights reserved.
>
> Make wine test for fcvt shut up we are failing 64 of wine test in msvrt printf, but we pass all fcvt test. before we did fail 75 test in wine test of msvrt printf test. Before we did fail almost all test case for fcvt in wine test
>
I've been actually importing a LOT of the SanOS code into rtl back when
I was working on fixing many of the broken inlined GAS routines, and his
code REALLY kicks ass. I strongly recommend using the SanOS CRT
functions when possible.
Best regards,
Alex Ionescu
Murphy, Ged (Bolton) wrote:
>
>
> amunger(a)svn.reactos.org wrote:
> >
> > URL: http://svn.reactos.ru/svn/reactos?rev=22052&view=rev
> > Log:
> > Bump trunk to 0.4.0, no turning back now.
> >
>
> Ehh???
Oh I see, nevermind.
I read it wrong initially.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
amunger(a)svn.reactos.org wrote:
>
> URL: http://svn.reactos.ru/svn/reactos?rev=22052&view=rev
> Log:
> Bump trunk to 0.4.0, no turning back now.
>
Ehh???
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hi!
ReactOS.Bugzilla(a)reactos.org wrote:
> http://www.reactos.org/bugzilla/show_bug.cgi?id=1172
>
>
> hpoussin(a)reactos.org changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC|hpoussin(a)reactos.org |
> Summary|Network driver will not |VIA Rhine II net driver
> |install. |doesn't detect miniport
>
>
>
>
> ------- Comment #9 from hpoussin(a)reactos.org 2006-05-23 22:18 CET -------
> Changing title, as it is no more a installation problem.
> (btw, the wrong name in ncpa control panel is due to a missing entry in
> [Strings] section)
>
>
Funny, it once worked.
[MANUF]
%PCI\VEN_1106&VT3065.DeviceDesc% = VT3065_ndi,PCI\VEN_1106&DEV_3065
;%PCI\VEN_1106&VT3065.DeviceDesc% = VT3065_ndi,PCI\VEN_1106&DEV_3065&SUBSYS_734C1462
<snip >
Manuf = "VIA Technologies, Inc."
VT3106S.DeviceDesc = "VIA Rhine III Management Adapter"
VT3106J.DeviceDesc = "VIA Rhine III Fast Ethernet Adapter"
VT3065.DeviceDesc = "VIA Rhine II Fast Ethernet Adapter"
VT3043.DeviceDesc = "VIA VT86C100A Rhine Fast Ethernet Adapter"
FET.Service.DispName = "VIA Rhine Family Fast Ethernet Adapter Driver Service"