Hi,
looking through our file functions, we do always access a file object
after it was dereferenced by the completion routine and if the
FO_SYNCHRONOUS_IO flag is set. If FO_SYNCHRONOUS_IO is set, the
completion routine should not dereference the file object or we have to
add an additional reference. If FO_SYNCHRONOUS_IO is set, we have also
to dereference the file object after calling the driver.
- Hartmut
Hello.
I am trying to boot ReactOS by freeldr on floppy from SCSI harddrive
(80h) on an aic78xx.
Freeldr loads and display Welcome message. I run Reactos HardDrive (C:)
and got :
An error occured in FreeLoader
FreeLoader v2.1
Report this ...
Exception 06: INVALID OPCODE
EAX:00000001 ESP:0000FEFC CR0:00000011 DR0:00000000
EBX:2046C700 EBP:C7000000 CR1:00000000 DR1:00000000
ECX:00000000 ESI:FFFFFFFF CR2:00000000 DR2:00000000
EDX:00000001 EDI:002846C7 CR3:00000000 DR3:00000000
DR6:FFFF0FF0
DR7:00000400
CS:0008 EIP:FFFF2C46
DS:0010 ERROR CODE:00000000
ES:0010 EFLAGS:00010016
FS:0010 GDTR Base:0000842C Limit:0027
GS:0010 IDTR Base:000086E0 Limit:0100
SS:0010 LDTR:0000 TR:0000
Frames:
Nothing more displayed.
Computer is Dual PIII machine, Reactos is todays svn version builded on
linux with mingw, 512 MB RAM.
There is w2k server on second partition of the SCSI harddrive and boots
and runs without errors. First partition is 4 GB FAT32, disk capacity is
18GB.
Thank you.
David
Anyone else seeing this under linux?
Detecting netwide assembler...detected (nasm)
Detecting compiler -pipe support...detected
Detecting compiler pre-compiled header support...detected
Processing modules...done
Creating directories...done
Unpacking WINE resources...done
Generating test support code...done
Generating compilation unit support code...done
Generating syssetup.inf...done
Generating proxy makefiles...done
Checking automatic dependencies...done
[CC] tools/cdmake/cdmake.c
[CC] tools/cdmake/llmosrt.c
[LD] output-i386/tools/cdmake/cdmake
[LD] output-i386/tools/mkhive/mkhive
gcc: obj-i386/lib/inflib_host/infcore.o: No such file or directory
gcc: obj-i386/lib/inflib_host/infget.o: No such file or directory
gcc: obj-i386/lib/inflib_host/infput.o: No such file or directory
gcc: obj-i386/lib/inflib_host/infhostgen.o: No such file or directory
gcc: obj-i386/lib/inflib_host/infhostget.o: No such file or directory
gcc: obj-i386/lib/inflib_host/infhostglue.o: No such file or directory
gcc: obj-i386/lib/inflib_host/infhostput.o: No such file or directory
make: *** [output-i386/tools/mkhive/mkhive] Error 1
WD
--
<mikedep333> but if it isnt working, why is it even included on the CD?
Hi,
There is some code in the C Runtime that was part of the Win32 port of
perl. As such it carries the copyright Microsoft. I suggest we remove
and rewrite these functions, as this will hinder us from being able to
say
"ReactOS is 100% free of Microsoft Code"
Even if it is GPL it does not sit well with me. Anyone up to help on this?
--
Steven Edwards - ReactOS and Wine developer
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
http://neowin.ath.cx/twotailedfox/Error.png
Can anyone help me shed some light on this rather perculiar error?
GCC 3.4.4/G++ 3.4.2, MSYS 1.0, GNU Make 3.80, NASM 0.98, Binutils
2.16.91, MinGW 4.1.0
--
"I had a handle on life, but then it broke"
sedwards(a)svn.reactos.com wrote:
> more crt, crtdll and msvcrt cleanup
> +#include "precomp.h"
That doesn't work, it should be <precomp.h>....
- Thomas
ion(a)svn.reactos.com wrote:
>- Remove KTSS_NOIOMP from NDK.
>- Fix KTSS definition.
>- Fix KTRAP_FRAME definition.
>- Fix RTL_PROCESS_BACKTRACE_INFORMATION and RTL_PROCESS_BACKTRACES definitions.
>- Fix/rename RUNDOWN_DESCRIPTOR definition.
>- Rename PPF_ definitions to RTL_USER_PROCESS_PARAMETERS_
>- Setup a global _REACTOS_ define when code is compiled.
>- #ifdef out the multiboot flags from the NDK so they'll only be available for ReactOS. Dirty 'hack' until we stop using them.
>- Update NDK Fixme list, since all major bugs are fixed now.
>
>
>
>
Hi,
Sorry, this breaks compiling. I think there is a bug in compilation
units. I did make ntoskrnl_clean about 3 times, and even a complete
"make depends -j2" and it compiled the whole tree fine. Then I started
doing other changes, and I started getting build failures.
Best regards,
Alex Ionescu
It seems to me that is always best to do it right first time.
Then it is easier to get quality,
Well anyway it is my opinion.
Like the Japanese car manufacturers discovered first,
that is always best to track down and solve problems in early stage,
than later......
Bierá L. gaino
ion(a)svn.reactos.com wrote:
> - Add DDK alignment macros and move/rename the ones in the NDK for user-mode only (since kernel-mode should use the DDK ones).
> - Fix helper.h's alignment macros to protect properly and also use a faster implementation.
> - Update NDK readme.
> Modified: trunk/reactos/include/ndk/lpctypes.h
>
>
> ------------------------------------------------------------------------
> *Modified: trunk/reactos/include/ndk/lpctypes.h*
> --- trunk/reactos/include/ndk/lpctypes.h 2005-11-26 23:26:04 UTC (rev 19665)
> +++ trunk/reactos/include/ndk/lpctypes.h 2005-11-27 02:55:13 UTC (rev 19666)
> @@ -234,9 +234,9 @@
> // Maximum total Kernel-Mode LPC Message Structure Size
> //
> #define LPCP_MAX_MESSAGE_SIZE \
>
> - ROUND_UP(PORT_MAXIMUM_MESSAGE_LENGTH + \
>
> + ALIGN_UP(PORT_MAXIMUM_MESSAGE_LENGTH + \
>
> sizeof(LPCP_MESSAGE) + \
>
> - sizeof(LPCP_CONNECTION_MESSAGE), 16)
>
> + sizeof(LPCP_CONNECTION_MESSAGE), sizeof(ULONGLONG) * 2)
>
>
> //
> // Maximum actual LPC Message Length
>
> ------------------------------------------------------------------------
This or the definition of ALIGN_UP is wrong. ALIGN_UP needs a type as
second parameter. Now the value of LPCP_MAX_MESSAGE_SIZE,
LPC_MAX_MESSAGE_LENGTH and LPC_MAX_DATA_LENGTH are changed. ReactOS
won't boot because csrss uses hard coded values in CsrpCreateListenPort.
- Hartmut
Only developers can vote.
Brandon
Alex Buell wrote:
> On Sun, 27 Nov 2005, Casper Hornstrup wrote:
>
>> http://www.reactos.org/forum/viewtopic.php?p=10398#10398
>
>
> Since I cannot vote (even though I've signed up), I'll stand up and
> say I'd vote for option B if I could.
>
turner(a)svn.reactos.com wrote:
> Don't hardcode user to .DEFAULT when reading registry
>
> Modified: trunk/reactos/subsys/win32k/ntuser/misc.c
> + NtClose(CurrentUserKey);
This needs to be ZwClose
- Thomas
Hi,
For background in the Debian win32 port see the mailing list archives
[1]. Basically, the only reason the port is allowed by Debian is that it
could run on ReactOS or wine which are both DFSG [2] compliant.
Microsoft Windows, OS/2... aren't DFSG compliant.
I've read [3] that the Debian win32 ports "failed because most unix
software made unforgivable presumptions about file system semantics;
mainly that you could delete files that were in-use, and rename open
files on top of other open files, etc." Is this something that could be
resolved? I'd imagine the Installable File System (IFS) driver would
need to be modified to remember open files, or perhaps something could
intercept calls to an IFS driver? I think this is what some virus
scanners do, and what clamav is missing.
Porting Debian to ReactOS would give ReactOS a huge number of packages.
The BSD ports collection method or gentoo's build systems may be useful
too. All three would probably mean porting some base software though.
Any comments about porting the base of another OS to ros? Packages like
perl, bash, gcc, glibc seem to have native MS Windows ports.
http://packages.debian.org/stable/base/ lists all the various packages
in Debian's base (note some are specific to various ports, and there are
some semi-duplicated packages).
Another advantage of a Debian win32 port using ReactOS would be a really
nice flexible, modular installer (debian-installer or d-i for short).
I've had problems with the ros installer in the past, specifically I
couldn't install on one system without a mouse. It also asked many
questions, couldn't resize partitions... d-i is nice in that it can be
used with about three prompts, has partition resizing, can download
additional modules... I'd suggest checking it out (I feel like I'm
starting to just advertise it). Fwiw, longhorn seems to boot from a CD
to do it's graphical install that is supposed to have file system
resizing.
Can/does ReactOS support ELF? Alex Ionescu said that there's now an ELF
loader [4]. If so, would there be anything special that would need to be
done to run Linux binaries on ReactOS (beyond syscalls and porting
dependencies)? Is there any advantages to the PE format? If ReactOS
could support running Linux binaries it would be an easier sell to port
Debian to ReactOS as it could reuse things that are already compiled for
Debian. I believe the FreeBSD port (kFreeBSD that is) [5] re-uses some
packages compiled for Linux. OTOH, PE would be a nicer way to go so that
some support for MS Windows could be allowed... Or could MS Windows be
made to support ELF? I'm afraid I also don't know much about the coff
format.
[1] http://lists.debian.org/debian-win32/
[2] http://www.debian.org/social_contract#guidelines (very similar or
the same as the OpenSource definition)
[3] http://lists.debian.org/debian-win32/2005/10/msg00003.html
Message-id: <43663BFE.9010004(a)liddicott.com>
[4] http://www.reactos.org/bugzilla/show_bug.cgi?id=293
[5] http://www.debian.org/ports/kfreebsd-gnu/
Drew Daniels
Resume: http://www.boxheap.net/ddaniels/resume.html
I think the registry is messed up. desk.cpl isnt writing the wallpaper
style values, SystemParametersInfoW isnt wrtiting the path, and
IntSystemParametersInfo isnt able to read the wallpaper settings from
it. Also, my livecd wont boot with an error about not finding the
codepage. This all leads me to believe that something is up with the
registery. The last update i have is w3seek's where he reverted filip's
registry changes. I dont know when this started happening, last day or
so. It all worked fine when i commited 19476.
Royce: The reason you werent getting the bugcheck with my stretch patch
was because desk.cpl wasnt writing the wallpaper style values to the
registry and tat is why the wallpaper didnt stick.
I'm kinda busy right now. But hopfully within an hour I will be free
and be able to do some more debuging.
Brandon
In Short, A Lot.
ReactOS needs a proper shutdown and restart sequence (Like Linux does,
when it sends TERM to all processes). Log Off is a tad harder.
In order for Log Off to work properly, all the core processes need to
be kept running (csrss, winlogon, etc), and the system needs to "Fall
back" to a login screen. To do this, a User Logon System must be
implemented, complete with per-user registry files, settings storage,
and all the associated functions therein. AFAIK.
On 11/26/05, Alex Buell <alex.buell(a)munted.org.uk> wrote:
> On Fri, 25 Nov 2005, TwoTailedFox wrote:
>
> > No, the Shutdown/Restart and Log Off portions are in need of a
> > re-write, AFAIK. Since Local User Accounts are not implemented yet, we
> > cannot "Log Off" per se on ReactOS just yet.
>
> Ok, what needs doing to implement this properly? I'd like to help if I
> can.
>
> --
> http://www.munted.org.uk
>
> Anyone that thinks an imaginary deity is going to protect them against
> earthquakes and hurricanes needs psychiatric help.
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
--
"I had a handle on life, but then it broke"
> From: navaraf(a)svn.reactos.com
>
> Don't make cells smaller than they are.
Wow. Isn't it time we factor out the common code in cm, mkhive and freeldr
and put it in a static library?
GvG
navaraf(a)svn.reactos.com wrote:
> Don't make cells smaller than they are.
> Modified: trunk/reactos/ntoskrnl/cm/regfile.c
>
> ------------------------------------------------------------------------
> *Modified: trunk/reactos/ntoskrnl/cm/regfile.c*
> --- trunk/reactos/ntoskrnl/cm/regfile.c 2005-11-26 13:26:48 UTC (rev 19635)
> +++ trunk/reactos/ntoskrnl/cm/regfile.c 2005-11-26 15:21:44 UTC (rev 19636)
> @@ -3431,7 +3431,7 @@
>
> RtlZeroMemory(*Cell,
> CellSize);
>
> - ((PCELL_HEADER) (*Cell))->CellSize = -CellSize;
>
> + ((PCELL_HEADER) (*Cell))->CellSize *= -1;
>
> }
>
> return STATUS_SUCCESS;
>
This change is wrong. Possible we have split the cell. In this case, we
have to set the new cell size.
- Hartmut
> From: chorns(a)svn.reactos.com
>
> Speed up compilation of ntoskrnl
Hmm, an unexpected consequence is that we can no longer enable DPRINTs per
file by removing the "#define NDEBUG" statement. At the moment, the first
source files included by io.c and cc.c (resp io/adapter.c and cc/cacheman.c)
don't define NDEBUG before including debug.h. As a result, all DPRINTs in
every file included by io.c/cc.c are enabled.
GvG