> Can't really fix this, this is a side effect of
> the fact that NT checks that the initial boot
> process didn't die, and the fact that our setup
> code actually replaces the initial process.
It can be fixed on process level, not on the kernel level.
http://www.superheterodyne.net/reactos/freelist_remove_type.diff
This removes the redundant notion of .Flags.Type in freelist, and leaves only
the non-redundant MM_PHYSICAL_PAGE_BIOS. MM_PHYSICAL_PAGE_FREE is reported
when the page has a 0 reference count and MM_PHYSICAL_PAGE_USED is reported
when the reference count is nonzero.
A function, MmGetPageType is added to replace the old functionality.
Init memory being freed seems to cause a lot of grief. I'm going to see if
there's a way to decentralize how those pages are set up, given that the
method used to dispose of them is spread out too.
--
Discordant is the murmur at such treading down of lovely things while
god's most lordly gift to man is decency of mind. Call that man only
blest who has in sweet tranquility brought his life to close.
If only I could act as such, my hope is good.
-- Aeschylus' Agamemnon (translated by H. W. Smyth)
This patch makes ReferenceCount include MapCount so we don't get into the
quite common situation where the balance manager wants to expel a mapped
section. I've been seeing this error running quite a number of things and
recently even in the first stage installer.
Lightly tested, probably wrong as usual.
http://www.superheterodyne.net/reactos/fix_page_reference.diff
--
Discordant is the murmur at such treading down of lovely things while
god's most lordly gift to man is decency of mind. Call that man only
blest who has in sweet tranquility brought his life to close.
If only I could act as such, my hope is good.
-- Aeschylus' Agamemnon (translated by H. W. Smyth)
Hi!
Look at the cmd line options! It did display the debug printout for the devices.
Cool, Kick A$$, Rosxor! Alex!
James
(ntoskrnl/kd/kdio.c:193) -----------------------------------------------------
(ntoskrnl/kd/kdio.c:194) ReactOS 0.4-SVN (Build 20070126-r25642)
(ntoskrnl/kd/kdio.c:195) Command Line: DEBUGPORT=COM1 NOGUIBOOT SOS
(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:514) Not handling AMD caches yet
Used memory 1015744Kb
(ntoskrnl/se/semgr.c:36) FIXME: SeAccessCheck has been HACKED to always grant access!
(ntoskrnl/se/semgr.c:37) FIXME: Please fix all the code that doesn't get proper rights!
(ntoskrnl/ke/i386/kiinit.c:43) Large Page support detected but not yet taken advantage of!
WARNING: HaliQuerySystemInformation at hal/halx86/generic/sysinfo.c:26 is UNIMPLEMENTED!
(ntoskrnl/ke/i386/patpge.c:62) Advanced Memory features detected but not yet taken advantage of.
(ntoskrnl/ke/i386/mtrr.c:24) Your machine supports MTRR but ReactOS doesn't yet.
(ntoskrnl/io/iomgr/driver.c:908) 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
*** Fatal System Error: 0x0000001e
(0x80000003,0x81022F94,0x00000000,0x00000000)
<ntoskrnl.exe:2891 (ntoskrnl/ke/bug.c:1078 (KeBugCheckEx))>
<ntoskrnl.exe:86b66 (ntoskrnl/ke/i386/exp.c:995 (KiDispatchException))>
<ntoskrnl.exe:8913b (ntoskrnl/ke/i386/trap.s:681 (CommonDispatchException))>
<81022F95>
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.
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.
FAO JimT (or anyone else who may have secret fixes in their tree, Filip ;) )
Do you have any improvements to the mentioned functions.
They need attention/improvement to improve the drawing of some of our UI
controls.
Don't wanna double up on work if someone already has something on this.
Cheers,
Ged.
I have just tried to compile the current trunk and it was broken. I am using
the latest trunk with the latest ROS Build.
Grant A. Brady
CIP
Way too Much Fun Productions
Email: Bragrsibak(a)gmail.com
Email: WTMFP1(a)gmail.com
Current project: Console Suite
--
This email may or may not contain a virus. I really don't know because it
was
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.13/632 - Release Date: 1/16/2007
4:36 PM
I read in the news that a new virtual machine software got released
under GNU GPL v.2 (dual license) today (2007-01-15). It's called
VirtualBox (VirtualBox.org) and is partly based on qemu code. On of
the advantages are that it support Intel's VT (vanderpool), run as GUI
app on Win and Unix and support WinNT 6 without glitches (as heise.de
says).
News entry and review (both in german):
http://www.heise.de/newsticker/meldung/83680http://www.heise.de/open/artikel/83678
Heise.de said it is ready to compete with the latest versions of
VMware, Parallels and VirtualPC. If that statement is based on facts
or not and if it is a good reliable tool; I don't know as I have not
tested it myself, as I am busy right now. I just posted it here, as it
might be useful for someone.
Klemens
I'll probably get another weird email from the postmaster for this, but
it is sufficient to me to say that the GPL allows commercial ventures to
include code without the requirement of making the product open source.
There are a few rules though - and I'm not the one to ask about those,
but I know of many companies that include GPL code in their product
without the need to make their product open source.
Nathan
-----Original Message-----
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org]
On Behalf Of Alex Ionescu
Sent: Tuesday, January 16, 2007 8:41 AM
To: ReactOS Development List
Subject: Re: [ros-dev] Yet another VM
Colin Finck wrote:
> Thanks for the information.
>
> This VM seems to be very good.
> I also did not test it, but looked at the screenshots: VirtualBox
supports
> multiple snapshots and the closed-source version, which is also
available at
> no price for personal use, also supports USB devices. You can connect
to
> virtual machines over RDP and the virtual USB ports will also be
available
> through RDP.
> The closed-source version also has some unique features like mounting
iSCSI
> targets as virtual disks. AFAIK no other Workstation virtualization
product
> supports this at the moment.
>
> In my opinion, we should support VirtualBox as a new testing platform
for
> ReactOS, since it contains more features than QEMU and is open-source
unlike
> VMware.
> It would also be easier to use for new users, who did not run a PC
emulator
> before.
>
> Regards,
>
> Colin
It's funny how you're all going on about how good it is without even
having tested it.
QEmu supports multiple snapshots as well, as it does USB, and it's fully
open source. QEmu supports named pipes, mounting raw hard drives and any
other disk that Windows can see, audio, networking etc. So I don't think
it contains anywhere near as many features as QEMU, especially since
most of the advanced ones you mentionned are *not* Open Source.
I'm also quite curious on how they were able to take QEMU (a GPL
product) and add USB support under closed source (which QEMU already has
as GPL). Sounds like a bunch of hacks to me.
--
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design Engineer, ReactOS
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
I noticed a small problem with ROS's calculator; it was missing 8 pixels
from the bottom in both normal and scientific modes. This lead to the
calculator appearing chopped off at the bottom and looking rather bad. Here
is a small patch fixing it.
Grant A. Brady
A.K.A bragr
p.s. Here is the unmodified ROS calculator compared to Microsoft's on
Windows XP: http://wtmfp.boldlygoingnowhere.org/calcs.png
--
This email may or may not contain a virus. I really don't know because it
was checked with
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.7/620 - Release Date: 1/8/2007
4:12 PM
Felipe Villarroel wrote:
>On 1/5/07, Muguntharaj Subramanian <mugunth(a)gmail.com> wrote:
>
>
>>...
>>partition signature != 55AA
>>...
>>
>>
>You have a corrupted MBR or partition table. Reinstall ReactOS and do
>proper partitioning.
>
>
Hm, Hm... It's not so simply.
I got same error with _fresh-installed_ ReactOS.
WBR, DarkHobbit
Hi,
So of you might already know that I have been working on desk.cpl
appearance page patch for some time. (bugzilla #1732, but I have already
some more local changes/fixes)
Eric Kohl is working on the same area now, so I'd like to talk about it
with him, so we will not do the same work twice.
I could not contact him so far.
so if you read this, Eric, please reply, or if someone can contact him,
please tell him.
Thanks,
Timo