greatlrd(a)svn.reactos.org wrote:
> revers r25623
Yeeey, greatlord is back to his old reverting ways ;)
> Acdring to Sylvain Petreolle, spetreolle at yahoo.fr
> this is copy paste from windows xp cpl, it is not allown
> todo a copy paste of sentence from windows xp, he did
> compare it.
Most of our control panel text is the same as Windows.
SSDD,,, Hardware, etc,,,,
kdb:> (ntoskrnl/kd/kdio.c:193) -----------------------------------------------------
(ntoskrnl/kd/kdio.c:194) ReactOS 0.3.1-SVN (Build 20070124-r25623)
(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:502) Not handling AMD caches yet
Used memory 1015744Kb
(ntoskrnl/se/semgr.c:41) FIXME: SeAccessCheck has been HACKED to always grant access!
(ntoskrnl/se/semgr.c:42) FIXME: Please fix all the code that doesn't get proper rights!
(ntoskrnl/ke/clock.c:92) FIXME: TIMER UPDATE NOT DONE!!!
(ntoskrnl/ke/i386/kiinit.c:41) Your machine supports PGE but ReactOS doesn't yet.
WARNING: HaliQuerySystemInformation at hal/halx86/generic/sysinfo.c:26 is UNIMPLEMENTED!
(ntoskrnl/ke/i386/patpge.c:62) Your machine supports PAT but ReactOS doesn't yet.
(ntoskrnl/ke/i386/cpu.c:745) Your machine supports XMMI exceptions but ReactOS doesn't
(ntoskrnl/io/iomgr/driver.c:905) Driver 'buslogic.sys' load failed, status (c0000001)
(ntoskrnl/io/iomgr/file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1
(ntoskrnl/ldr/loader.c:259) Could not open module file: \SystemRoot\system32\drivers\mpu401.sys
(Status 0xc0000034)
(ntoskrnl/ldr/loader.c:259) Could not open module file: \SystemRoot\system32\drivers\sndblst.sys
(Status 0xc0000034)
(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/fslib/vfatlib/vfatlib.c:215) VfatChkdsk() unimplemented!
(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/io/iomgr/file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff
(./subsystems/win32/win32k/objects/dc.c:324) No InstalledDisplayDrivers value in service entry found
(./subsystems/win32/win32k/objects/dc.c:479) FindDriverFileNames failed
(ntoskrnl/io/iomgr/file.c:410) FIXME: Broken Parse due to invalid DesiredAccess: 1f01ff
(dll/ntdll/ldr/utils.c:1198) LdrGetExportByName(): failed to find mxdMessage
(dll/ntdll/ldr/utils.c:2024) Failed to create or open dll section of 'msacm.drv' (Status c0000135)
(dll/ntdll/ldr/utils.c:2024) Failed to create or open dll section of 'midimap.drv' (Status c0000135)
<Here.......>
(lib/cmlib/hiveinit.c:31) Verify Hive Header failed:
(lib/cmlib/hiveinit.c:32) Signature: 0x66676572 and not 0x66676572, Major: 0x1 and not 0x1
(lib/cmlib/hiveinit.c:34) Minor: 0x3 is not >= 0x3, Type: 0x0 and not 0x0
(lib/cmlib/hiveinit.c:36) Format: 0x1 and not 0x1, Cluster: 0x1 and not 1
(lib/cmlib/hiveinit.c:38) Sequence: 0x17 and not 0x17, Checksum: 0x70e9199b and not 0x0
(lib/cmlib/hiveinit.c:159) Registry is corrupt: ChunkSize 20480 < sizeof(HBASE_BLOCK) 4096, or
HvpVerifyHiveHeader() failed
(ntoskrnl/cm/regfile.c:580) Failed to open hive
(ntoskrnl/mm/mm.c:193) Page fault at high IRQL was 2, address cccccc94
Entered debugger on last-chance exception (Exception Code: 0xc0000006) (Unknown/
User defined exception)
kdb:> bt
Eip:
<ntoskrnl.exe:4f24e (ntoskrnl/mm/npool.c:1556 (ExFreeNonPagedPool))>
Frames:
<ntoskrnl.exe:5296e (ntoskrnl/mm/pool.c:237 (ExFreePool))>
<ntoskrnl.exe:5299e (ntoskrnl/mm/pool.c:249 (ExFreePoolWithTag))>
<ntoskrnl.exe:71ff2 (ntoskrnl/rtl/libsupp.c:61 (RtlpFreeMemory))>
<ntoskrnl.exe:97966 (lib/rtl/unicode.c:392 (RtlFreeUnicodeString))>
<ntoskrnl.exe:11cb0 (ntoskrnl/cm/regfile.c:585 (CmiLoadHive))>
<ntoskrnl.exe:105e9 (ntoskrnl/cm/ntfunc.c:2348 (NtLoadKey2))>
<ntoskrnl.exe:1071f (ntoskrnl/cm/ntfunc.c:2238 (NtLoadKey))>
<ntoskrnl.exe:7ce34 (ntoskrnl/ke/i386/trap.s:250 (KiFastCallEntry))>
<ntdll.dll:85ad (dll/ntdll/main/i386/dispatch.S:265 (KiFastSystemCallRet@0))>
<userenv.dll:3ab6 (dll/win32/userenv/profile.c:292 (CreateUserProfileW))>
<syssetup.dll:1a2f (dll/win32/syssetup/install.c:619 (InstallReactOS))>
<setup.exe:1099 (base/setup/setup/setup.c:107 (WinMain))>
<setup.exe:133c (lib/mingw/main.c:78 (main))>
<setup.exe:124d (lib/mingw/crt1.c:228 (__mingw_CRTStartup))>
<setup.exe:128f (lib/mingw/crt1.c:262 (WinMainCRTStartup))>
<kernel32.dll:1a8bd (dll/win32/kernel32/process/create.c:68 (BaseProcessStartup))>
<00000000>
kdb:>
I haven't tested the RosBE 4.1.2 build yet.
Thanks,
James
There has been much talk about different GCC versions in #reactos. So
i just want a clear straight answer. Do we need a vote? are we waiting
for something/someone to give the go ahead? What version is RosBuild
using? Are we moving to a new recommended compiler?!?
--
encoded
Samuel Serapión Vega
Computer Engineering, Polytechnic University of Puerto Rico.
hyperion(a)svn.reactos.org wrote:
> Author: hyperion
> * __rdtsc: removed "__volatile__" attribute from the inline asm. Hyperion recommends you fix your goddamn code instead
Congrats, you just broke ReactOS... did you even test this change, or
did you just assume that the "goddamn code sucks"? Even if it did, you
should've fixed it before breaking the OS.
--
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design Engineer, ReactOS
Eduard Glatz wrote:
> Now the question arised
> if there would be an interest in student thesis works
> as contributions to the reactos project.
>
> An overview of thesis works completed in the area of
> systems software can be found under:
>
> http://windows.hsr.ch/studienarbeiten.html
Many of the listed topic areas are either not relevant or too advanced for
ReactOS to support at the moment.
> If there is an interest in such contributions then
> we will have to discuss next the type of suitable tasks.
If the standard of work is high enough, i.e. if the student(s) are
proficient in C and NT programming, then there would certainly be great
interest from the ReactOS project in something like this.
However, even if the standard of work was not particularly high, we would
still encourage people to try and we would help in any way we could (or were
permitted to). The only concern from submitting low quality work would be
that it may not make it into the final ReactOS source code.
A few good examples of things we are looking for are listed in our 2006
Google Summer of Code page.
Two good contributions we received from this was a Windows clipboard
implementation and Remote Desktop.
Some suggestions are:
- Network card drivers
- mmc.exe replacement
- printer spooler support
- Explorer theming
- a choice of directx dlls
- bug fixing or improvements to a large choice of operating system
components.
- choosing existing win32 software, and ensuring ReactOS has the relevant
support to run it.
e.g. Apache, Ms Office, Photoshop, AutoCAD
Hope this helps.
Ged.
Hello all,
at our university we are offering thesis works for computer science students
in several areas of interest. Many of those works result in contributions to
existing open source projects or even initiate new ones.
My interests are in the area of operating systems. Now the question arised
if there would be an interest in student thesis works as contributions to
the reactos project.
An overview of thesis works completed in the area of systems software can be
found under:
http://windows.hsr.ch/studienarbeiten.html
Unfortunatley those descriptions are only in german. But at least many of
the english titles give you an indication what the tasks were.
If there is an interest in such contributions then we will have to discuss
next the type of suitable tasks.
Kind regards,
Edy
Eduard Glatz, Prof. Dipl.-Ing.
University of Applied Sciences HSR (Hochschule Rapperswil)
Department of Computer Sciences (Abt. Informatik)
Oberseestr. 10; 8640 Rapperswil; Switzerland; www.hsr.ch
P.s. it might help if I attached the app I mentioned ;)
James Tabor wrote:
> I have some arc code but it's not tested and I really want to finish this
ASAP!
After someone mentioned the state of the radio buttons the other day, I had
a quick look at it.
Our user32 code draws them pretty well (with one or two mods)
As we're swapping test apps, I've attached one comparing the Windows and ROS
variants.
The problem ultimately comes down to NtGdiPie, NtGdiEllipse.
If you don't have any updates to these 2 functions, I'll look at them when I
get chance.
> Here is a test program. Guess what part doesn't work?
They all look pretty good, but strangely, they all appear to draw 1 pixel
larger than the Windows version.
Does the Windows code draw slightly undersize?
Ged.