Hi,guys
I'm just a fan of ReactOS,now I have two questions.
1, Is(or will be) there an disk management utility for ReactOS, or in
another way, will we make an implementation of Microsoft diskmgmt.msc?
2, Will ReactOS group make an implementation of Microsoft Management
Console for ReactOS?
Thank you!
Yeah, sorry, the target device should be used to send a
TARGET_DEVICE_CUSTOM_NOTIFICAITON of type GUID_IO_VOLUME_CHANGE at the
end of the function (IoReportTargetDeviceChange).
FYI, Pierre, when you implement the notification system.
On 4-Jan-09, at 5:12 AM, fireball(a)svn.reactos.org wrote:
> Author: fireball
> Date: Sun Jan 4 04:12:38 2009
> New Revision: 38552
>
> URL: http://svn.reactos.org/svn/reactos?rev=38552&view=rev
> Log:
> - Revert changes to NtSetVolumeInformationFile made in 38550, it
> should indeed use IoGetRelatedDeviceObject, not target device.
>
> Modified:
> trunk/reactos/ntoskrnl/io/iomgr/iofunc.c
>
> Modified: trunk/reactos/ntoskrnl/io/iomgr/iofunc.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/io/iomgr/iofunc.c…
> =
> =
> =
> =
> =
> =
> =
> =
> ======================================================================
> --- trunk/reactos/ntoskrnl/io/iomgr/iofunc.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/io/iomgr/iofunc.c [iso-8859-1] Sun Jan 4
> 04:12:38 2009
> @@ -3307,8 +3307,7 @@
> }
>
> /* Get the device object */
> - Status = IoGetRelatedTargetDevice(FileObject, &DeviceObject);
> - if (!NT_SUCCESS(Status)) return Status;
> + DeviceObject = IoGetRelatedDeviceObject(FileObject);
>
> /* Clear File Object event */
> KeClearEvent(&FileObject->Event);
>
Best regards,
Alex Ionescu
Hi,
the declaration of FsRtlNotifyReportChange was correct, even if this function is now deprecated (that's why it doesn't need to be in DDK).
WBR,
P. Schweitzer
_________________________________________________________________
Inédit ! Des Emoticônes Déjantées! Installez les dans votre Messenger !
http://www.ilovemessenger.fr/Emoticones/EmoticonesDejantees.aspx
Why do you need to start on real hardware?
This is fairly unsupported at the moment, so you’re really in no-mans-land here.
I’d suggest a virtual machine until you become more familiar with it.
Anyway, looking at your hardware spec I don’t see any untoward.
Continuing down the real hardware path, your next step is to obtain debug output.
The only current method to do this is via a null-modem cable, as specified in the link I gave you.
Ged.
From: James Muthee [mailto:jsoftpacks@yahoo.co.uk]
Sent: 31 December 2008 09:12
To: Ged
Subject: RE: [ros-dev] Problems installing REACTOS
Hello Ged.
Thanks for the prompt reply.
First, I need to test the software on a real machine. No Virtualization, no support form any other OS.
As for the exact configuration of the system, I am forwarding the entire report from the windows system info.
I know its lengthy but, then again you would be looking for someting specific.
My disks are FAT32
Please help.
Thanks
James I. M.
--- On Tue, 30/12/08, Ged <gedmurphy(a)gmail.com> wrote:
From: Ged <gedmurphy(a)gmail.com>
Subject: RE: [ros-dev] Problems installing REACTOS
To: jsoftpacks(a)yahoo.co.uk, "'ReactOS Development List'" <ros-dev(a)reactos.org>
Date: Tuesday, 30 December, 2008, 1:59 PM
It could be a whole range of things.
Without having your hardware spec and debug output, it’s impossible to tell.
If you just want to test it, it’s better to run it in a virtual machine.
If you’re insistent on running it on hardware, then you’ll need to start by supplying your hardware details.
If that doesn’t show any obvious problems (e.g. SATA, NTFS, etc) then you will need to grab debug output via a null cable modem <http://www.reactos.org/wiki/index.php/Debugging#Real_computer:_Physical_ser…> http://www.reactos.org/wiki/index.php/Debugging#Real_computer:_Physical_ser…
Good luck.
Ged.
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of James Muthee
Sent: 30 December 2008 11:21
To: ros-dev(a)reactos.org
Subject: [ros-dev] Problems installing REACTOS
Hello.
Having downloaded the software (I was amazed it was less than 40MB), I wrote the ISO on a CD and started the installation.
0.3.7 failed to install completely, stopping dead just after loading the initial files.
I downloaded the 0.3.6 and tried again. This time, I was able to install the first portion (copying the textmode installation to the hard disk and modifying the MBR).
On restart, A GUI window flashed then a blue screen with a single line about the Build, and that was the end.
What am I doing wrong?
I would appreciate any help. I really want to test drive this software.
James I. M.
Just wanted to tell this is a great work, and with such test suite we
will always notice if something breaks.
WBR,
Aleksey Bragin.
On Dec 30, 2008, at 7:04 AM, hyperion(a)svn.reactos.org wrote:
> Author: hyperion
> Date: Mon Dec 29 22:04:51 2008
> New Revision: 38461
>
> URL: http://svn.reactos.org/svn/reactos?rev=38461&view=rev
> Log:
> modified tests/pseh2/psehtest.c
> finally_13 test re-enabled, as it doesn't crash anymore
> finally_14 test fixed. Now we know how exceptions thrown in a
> __finally are supposed to be handled
> PSEH test suite now has 91 tests and passes all of them with
> both GCC and Visual C++
Hello.
Having downloaded the software (I was amazed it was less than 40MB), I wrote the ISO on a CD and started the installation.
0.3.7 failed to install completely, stopping dead just after loading the initial files.
I downloaded the 0.3.6 and tried again. This time, I was able to install the first portion (copying the textmode installation to the hard disk and modifying the MBR).
On restart, A GUI window flashed then a blue screen with a single line about the Build, and that was the end.
What am I doing wrong?
I would appreciate any help. I really want to test drive this software.
James I. M.
Hi,
I imported function ReplaceFileW from Wine, but it do not work in ReactOS.
RepleceFileW there do not pass 11 tests (kernel32_winetest file). I think,
that a problem in call MoveFileEx. Somebody can help with it?
Function in Wine: http://www.reactos.org/paste/index.php/2745/
Patch for ReactOS: http://www.reactos.org/paste/index.php/2744/
--
WBR,
Dmitry Chapyshev
Hi ALL!
Okay, not sure what is going on but here is the original output:
Unhandled exception
ExceptionCode: c0000005
Faulting Address: 682000
Address: 7c91e6ae C:\ReactOS\system32\ntdll.dll
CS:EIP 1b:7c91e6ae
DS 23 ES 23 FS 3b GS 0
EAX: 011f0020 EBX: 011f0020 ECX: 090b071d
EDX: 242c2c64 EBP: 008afc54 ESI: 00681ffe ESP: 008afc4c
EDI: 011f1010 EFLAGS: 00010212
Frames:
77e30000+211d2 C:\ReactOS\system32\user32.dll
77e30000+21365 C:\ReactOS\system32\user32.dll
77e30000+20c56 C:\ReactOS\system32\user32.dll
400000+892c C:\ReactOS\user32_crosstest.exe
400000+8e73 C:\ReactOS\user32_crosstest.exe
400000+a3ab C:\ReactOS\user32_crosstest.exe
400000+b4ac8 C:\ReactOS\user32_crosstest.exe
400000+b4c56 C:\ReactOS\user32_crosstest.exe
400000+1247 C:\ReactOS\user32_crosstest.exe
400000+1298 C:\ReactOS\user32_crosstest.exe
7c700000+218e4 C:\ReactOS\system32\kernel32.dll
(subsystems/win32/csrss/api/wapi.c:115) CSR: received hard error c0000144
(subsystems/win32/csrss/win32csr/dllmain.c:528) The instruction at
"0x7c91e6ae" referenced memory at "0x00682000". The memory could not
be "read".
After patch:
We have a thread overrun, these are already freed! pi -> 18808864 bi -> 6819854
We have a thread overrun, these are already freed! pi -> 18808864 bi -> 6819854
Than, get two exit strings at the command console.
bi -> 6819854 (0x68100E) is the one and it is from MapViewOfFile. The
difference from 0x682000 is 4082.... Well with in the normal page but
why is 0x68100E the start address and not 0x681000?
It could be just simply bad math being used in LoadBitmapImage. Wine
does use the same code in user32 from gdi32 to handle bitmap and
friends.
Thanks,
James
Hi rosdevs!
This is an issue I've been working on for a while on the Wine side of
things and now they have initial support for it. If any of you
Win32k/GDI hackers are interested in making ReactOS look a bit better
on LCDs please enable support in freetype and review the following
Wine patch to get an idea of the requirements.
Thanks
http://source.winehq.org/git/wine.git/?a=commitdiff;h=028617b90ba586bdb3072…
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
Hi,
Mozilla Firefox 2.0: install it, run it, then quit - total hang
without KDBG or any exception, TAB+K doesn't work.
Then, reboot - try to navigate via Start Menu to Applications ->
Mozilla Firefox. Explorer will die with exception in dll/win32/user32/
misc/exticon.c:88 (find_entry_by_id). Maybe due to files corruption.
WBR,
Aleksey.
tkreuzer(a)svn.reactos.org wrote:
> For some unknown reason wmc likes to include string.h from the wine folder
and we cannot link it on linux hosts. This hack should hopefully resolve the
issue.
Not that mysterious actually.
The "include/reactos/wine" directory is shared among Wine host and target
tools while "include/crt" contains target-only headers and thus it's only
available for target components.
Therefore #include_next cannot find any other "string.h" file, when you use
it inside host tools. Furthermore, #include_next is a GCC-only thing, so we
should avoid it wherever possible.
To circumvent these problems and remove the hacks from the actual CRT/PSDK
headers, I propose we i.e. add '#include <reactos/wine/string.h>' to the CRT
"string.h" and do the appropriate thing for other files.
This is the prettiest solution I can think of without editing a bunch of
Wine files.
Best regards,
Colin
Sooner or later, this problem should be solved somehow. And not only for
Armenians, but also for other peoples of the world, who live without code
pages.
I concur with James.
Eric, I think what you meant to say is you don't have time to work on
ReactOS in its current state -- ie: the slow, time-consuming
procedures and behaviors that take up more than 50% of your free time.
What if ReactOS provides you with your own branch, and the ReactOS
project assumes the responsibility of merging your changes to trunk,
performing the testing and regression testing. You might be afraid
that your code will "rot" and that it would never make it inline, but
I'm sure the people respect your work as much as I do and would make
sure that things stay up to date (much like we sync with Wine).
This would allow you to keep committing code, have your own branch
which at least works for you, and we'd take care of merging. Your only
real responsibility would be to "sync up" with trunk every once in a
while -- could even be only ever 3 months, or if you notice something
obvious that might affect you (RPC changes, WIDL changes, SCM etc).
I know this may sound unfair to other developers, but as James pointed
out, you deserve everyone's time, considering how much you've put in
all this time.
On 19-Dec-08, at 9:22 PM, James Tabor wrote:
> Hi Eric!
> Eric Kohl wrote:
>> Hi!
>>
>> Effective immediately I am taking a break from working on ReactOS
>> for an
>> undetermined period of time. It may even be the end of my involvement
>> with ReactOS.
>>
>> There are several reasons for me to quit but the most important one
>> is
>> lack of time. I have a pretty exhausting job and spend more than 2
>> hours
>> a day to commute so there is not much time left to spend on ReactOS.
>> So working on ReactOS happened on weekends only.
>>
>> After my latest patch was partially reverted, I decided that I am not
>> willing to create and maintain a development branch for
>> improvements to
>> LSA and SAM. I am not willing to spend an hour or two each weekend
>> for
>> branch maintenance and debugging and another two or three hours for
>> developing new code. It just does not make sense to me.
>>
>> Maybe I will be back one day, maybe I will not. Time will tell.
>>
>> Over and out!
>> Eric
>>
> Your resignation is disapproved! You are an integral part of this
> project.
>
> You are the last of the root members of this project. We need your
> help
> and if that means breaking ReactOS truck that is your right to do
> so. We will
> learn to live with it. I have followed your work for years and I
> would like
> to see you more. Based on your tenure with this project, this gives
> you
> rights, influences and guidance to this project.
>
> Please recommence with your changes,
> James
> _______________________________________________
> Ros-general mailing list
> Ros-general(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-general
Best regards,
Alex Ionescu
Hi,
we are a software development company that develops and maintains a
Linux-based server solution called IServ, designed for use in schools.
We are in business since 2003, and there are currently about 370 schools
in Germany using IServ as their portal server.
One feature that we would like to integrate into our product is the
possibility to customize the ntconfig.pol file. This file, located on
the server's netlogon share, can deploy registry settings to Windows
clients - it is especially important because it can deploy
HKEY_LOCAL_MACHINE settings. This file is a binary registry hive. At the
moment, we have to create this file manually with poledit.exe.
We need a Linux program which can automatically generate this file.
1) It should read plain text files as input, for example an INF file.
2) The resulting policy file must work with Windows 2000 and XP x86
clients. It should be possible to easily test this by using the command
"Load Hive" in Regedit.
3) The preferred programming language is Perl, C/C++ is also OK. Other
languages should also be possible, but only after prior consultation
(just to make sure nobody comes up with Java ;) ).
4) The resulting source code should be released as open source, e.g.
under the GPL.
We would like the program being finished in one month. We will pay you
EUR 300 for it. If the program is very much work and you feel you need
more money, submit us an offer.
A Perl library to dump binary registry files to plain text:
http://search.cpan.org/~jmacfarla/Parse-Win32Registry-0.30/
Attachments:
ntconfig.pol - Our current policy. This must be generated automatically.
ntconfig.pol.dump - Plain text dump of that file, generated with
Parse::Win32Registry.
winnt.adm - Template to edit our policy file with poledit.exe.
Our homepage: http://iserv.eu (only in German, though)
--
Yours sincerely,
Martin v. Wittich
IServ
Falk & Ludwig GbR
Rebenring 33
38106 Braunschweig
Germany
Telephone: +49 531 380 4450
E-Mail: martin.von.wittich(a)iserv.eu
Internet: http://www.iserv.eu
hi, i'm a newbie of ReacOS.
I looked a piece of code in syscall.S which is come from 0.2.7 edtion.
/* Raise IRQL to APC_LEVEL */
movl $1, %ecx
call @KfRaiseIrql@4
could anybody help me explain why the function is decorated by @ in the head?
and why transfer argument by ecx?
Thank you
___________________________________________________________
好玩贺卡等你发,邮箱贺卡全新上线!
http://card.mail.cn.yahoo.com/