Wow!
Current SVN (Head)!
Used memory 1015744Kb
(mm/mminit.c:375) Kernel Stack Limits. InitTop = 0x80133000, Init = 0x80130000
(mm/virtual.c:214) FIXME: MEMORY_AREA_SYSTEM case incomplete (or possibly wrong)
for NtQueryVirtualMemory()
(ke/bug.c:56) Found Bugcheck Resource Data!
(ke/bug.c:67) Got Pointer to Bugcheck Resource Data!
(ke/clock.c:80) KiInitializeSystemClock()
(ke/clock.c:99) Finished KiInitializeSystemClock()
No current process
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0x9c could not be read: Page not present.
No current process
KeBugCheckWithTf at ke/catch.c:224
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED
Technical information:
*** STOP: 0x0000001E (0xc0000005,0x8002f410,0x00000000,0x00000018)
*** ntoskrnl.exe - Address 0x8002f410 base at 0x80000000, DateStamp 0x0
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:8002f410 <ntoskrnl.exe:2f410>
cr2 18 cr3 26000 Proc: 0
DS 10 ES 10 FS 30 GS 10
EAX: 00000000 EBX: 00000680 ECX: 00026000
EDX: 00000064 EBP: 8013245c ESI: 80132834 ESP: 801323ac
EDI: 80132be0 EFLAGS: 00210046 kESP 801323ac Frames:
<ntoskrnl.exe:300fc>
<ntoskrnl.exe:de31>
<ntoskrnl.exe:1285>
<ntoskrnl.exe:1aff>
<ntoskrnl.exe:382d>
<ntoskrnl.exe:c4a3e>
<46C>
KeBugCheckWithTf at ke/catch.c:224
A problem has been detected and ReactOS has been shut down to prevent damage to
your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
KMODE_EXCEPTION_NOT_HANDLED
Technical information:
*** STOP: 0x0000001E (0x80000003,0x80005c47,0x00000000,0x00000000)
*** ntoskrnl.exe - Address 0x80005c47 base at 0x80000000, DateStamp 0x0
Hi Hartmut,
> I'm not sure but a native application can only import ntdll.dll. If you
> enable the code, smss will import smdll.dll.
You are probably right. It is the time to make smdll static.
Thank you.
Emanuele
____________________________________________________________
Navighi a 2 MEGA e i primi 3 mesi sono GRATIS.
Scegli Libero Adsl Flat senza limiti su http://www.libero.it
I was wondering if there was a project that would be doing a binary compatible OS X system. What reactos does for windows maybe this project can do for OS X. I was just wondering. I know that pearpc emulates a ppc processor, but wether or not a full os exists is the question. I know also that some versions of linux exist for ppc.
Thanks
Also - is reactos going to do a mips, ppc, arm, ia64 system?
weiden(a)svn.reactos.com wrote:
>Alex Ionescu <ionucu(a)videotron.ca>
>
> Dispatcher Objects Rewrite (minus Queues, coming in next patch).
>
>
>
There is now only one large patch left + a smaller one related to it,
which will complete the Dispatcher fixes. After those two patches,
everything in my branch will have been committed. The branch will be
destroyed and I will create the Winsock branch on which Arty and I will
work.
Best regards,
Alex Ionescu
Hi,
Right now, someone has set up an XDCC IRC bot to distribute copies of
ReactOS. While I welcome the move, it raises a question on who is
responsible for the quality of those files. Even if the person means no
harm, the files can get corrupted/infected by the following events:
1) Download corruption
2) Viral infection
3) Hard-disk damage
And perhaps many more. In all cases, this would result in unusable,
dangerous or even damaging releases of ReactOS, which we could not
control. As such, I propose a vote:
[ ] Yes, allow 3rd-party distribution of the OS through the #ros-xdcc
channel and ROS-XDCC-001 bot. (support and encourage this distribution)
[ ] Yes, allow 3rd-party distribution of the OS, but it must clearly
distance itself from officially supported releases (tolerate but do not
support this distribution)
[ ] No, only sourceforge and other official ReactOS distribution points
should be used.
Myself I vote for the first choice, but I would like the following to be
done:
1) Create MD5 Hashes to verify authenticity
2) Set up official communications with the bot's maintainer and
establish a set of guidelines.
Best regards,
Alex Ionescu
screens? :P
greatlrd(a)svn.reactos.com wrote:
>GetDeviceData
>fix the choppy mouse in UT and fix some other small bugs.
>I can now use the mouse with out any problem in UT
>
>
>
>
>Updated files:
>trunk/reactos/lib/dinput/mouse.c
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
Hi,
--- Jason Filby <jason.filby(a)gmail.com> wrote:
> Another question is: can we really say limit people from
> redistributing ReactOS? I don't think that our license(s) prohibit
> this.
>
> Perhaps some guidelines for such people are all that is needed.
I think we should allow use of the name in limited situations. As another poster stated having a
"Dropline ReactOS" is not a bad thing provided that we setup standards on what has the right to be
called "ReactOS" and what does not. If anyone making or distributing a custom version of ReactOS
violates the standards we set forth then we have the right to refuse use of the name.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
