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