reactos-kernel

Re: [ros-kernel] Freeldr path fixes.

[Nick D. <nic...@ya...>]

Hi Eric,

----- Original Message -----
From: "Eric Kohl" <ek...@rz...>
To: <rea...@li...>
Sent: Tuesday, May 21, 2002 3:29 PM
Subject: Re: [ros-kernel] Freeldr path fixes.


> "Nick Date" <nic...@ya...> wrote:
>
> > If anyone has any other suggestions as to how I can boot ROS then it
would
> > be much appreciated. I can't seem to find loadros anywhere.
>
> You will find loadros in 'loaders/dos' of the reactos module. I use it all
> the time and it works very well.

Ah, I see the error of my ways - I didn't set up the makefile to build
loadros. Just one thing, though - I know there were some issues booting ROS
from FreeDOS. Do you know if this has been resolved yet or if it's just one
of those things?

--
Nick Date
Bath, England, UK




---
Outgoing mail is certified virus free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.363 / Virus Database: 201 - Release Date: 21/05/2002


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: [ros-kernel] Freeldr path fixes.

[Eric K. <ek...@rz...>]

"Nick Date" <nic...@ya...> wrote:


> If anyone has any other suggestions as to how I can boot ROS then it would
> be much appreciated. I can't seem to find loadros anywhere.

You will find loadros in 'loaders/dos' of the reactos module. I use it all
the time and it works very well.

Eric

[ros-kernel] Bootloaders

[Robert K. <ro...@ko...>]

Hi people.

Is it possible for you to give me a short introduction about which
loaders
exist for ROS,
why and why not they work,
who wrote them,
if they use Flat-Real-Mode
and Dis/Advances?

Thanks

Re: [ros-kernel] Freeldr path fixes.

[<we...@cw...>]

Quoting Nick Date <nic...@ya...>:
> 
> If anyone has any other suggestions as to how I can boot ROS then it
> would be much appreciated. I can't seem to find loadros anywhere.
> 
It should still be in reactos/loaders/dos though perhaps it isn't built
by default. Grub (http://www.gnu.org/software/grub) can also be used to
boot ReactOS.

[ros-kernel] Freeldr path fixes.

[Nick D. <nic...@ya...>]

Hi guys,

I've fixed the incorrect paths in freeldr, but I have no idea why neither
the bootsector code or install program refuses to compile.

I've attached a file with my changes in it (the only files I've modified are
INSTALL\MAKEFILE and INSTALL\INSTALL.C) and a new error report.

If anyone has any other suggestions as to how I can boot ROS then it would
be much appreciated. I can't seem to find loadros anywhere.

Kind regards,

Nick.

--
Nick Date
Bath, England, UK




---
Outgoing mail is certified virus free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.363 / Virus Database: 201 - Release Date: 21/05/2002

Re: [ros-kernel] Problems building freeldr

[Nick D. <nic...@ya...>]

Hi Casper,

----- Original Message -----
From: "Casper Hornstrup" <ch...@us...>
To: <rea...@li...>
Sent: Tuesday, May 21, 2002 1:01 PM
Subject: Re: [ros-kernel] Problems building freeldr

[snip]

> > I have no idea whatsoever what the "TIMES value is negative" error is
all
> > about. My assembler knowledge is very limited. The line in FAT.ASM reads
...
> >
> >     times 510-($-$$) db 0   ; Pad to 510 bytes
> >
>
> I have never seen this before. Which nasm version are you using? My best
> guess is that fat.asm assembles to a binary larger than 510 bytes.

I'm using the latest version of NASM (3.0.5?). I've managed to compile the
freeldr part of the program and have found that the problem with the TIMES
value is related to the bootsect directory and the missing/bad path for
header problems is related to the install part of freeldr.

Where's Brian Palmer when you need him? :-) If and when I get freeldr
working I'll submit any tweaks here so that someone can update the CVS. It's
just a pity that loadros doesn't seem to be in the tree anymore cos I can't
load ros! ;-)

Thanks again for your help, Casper.

Nick.

--
Nick Date
Bath, England, UK




---
Outgoing mail is certified virus free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.363 / Virus Database: 201 - Release Date: 21/05/2002


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: [ros-kernel] Fwd: Reorganizing the cvs repository beforestarting reactos.org

[Robert K. <ro...@ko...>]

And what about the earlier mentioned Idea of someone:

o Let win32k.sys as it is ( graphics ss with other stuff)
o Leave win32-core libs as win32-dlls
o Create a native win32k.dll that interfaces with sys.
o Make the win32 core libs base on win32k.dll

David Welch schrieb:

> On Tue, May 14, 2002 at 10:56:01AM -0400, Steven Edwards wrote:
> > Do to upgrade win32 (not counting win32k, user32, and kernel32)
> >
> Also gdi32 and advapi32.
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel

Re: [ros-kernel] Problems building freeldr

[Casper H. <ch...@us...>]

tir, 2002-05-21 kl. 13:58 skrev Nick Date:
> Casper, Eric, thanks.
> 
> I made the (rather stupid) assumption that DJGPP had an assembler that came
> with it. However, having downloaded the latest version of NASM, FREELDR
> still chucks a wobbly.
> 
> Now it's saying: (it does the same with NASM and NASMW ...)
> 
> C:\rosdev\build\freeldr>make -k
> make -C bootsect
> make[1]: Entering directory `C:/rosdev/build/freeldr/bootsect'
> nasm -o fat.bin -f bin fat.asm
> fat.asm:379: error: TIMES value -9 is negative
> make[1]: *** [fat.bin] Error 1
> make[1]: Target `all' not remade because of errors.
> make[1]: Leaving directory `C:/rosdev/build/freeldr/bootsect'
> make: *** [bootsect] Error 2
> make -C install
> make[1]: Entering directory `C:/rosdev/build/freeldr/install'
> gcc -Wall -o install.o -c install.c
> install.c:26: ../bootsect/fat.h: No such file or directory
> make[1]: *** [install.o] Error 1
> make[1]: Target `all' not remade because of errors.
> make[1]: Leaving directory `C:/rosdev/build/freeldr/install'
> make: *** [install] Error 2
> make: Target `all' not remade because of errors.
> 
> 
> Looking at the source, I can see why it would have trouble finding it's
> header files - they are in various subdirectories and there seems to be
> nothing in either the makefile or actual source that mentions the path. Even
> copying the header files to a common subdirectory and changing the path in
> the source causes GCC to claim the files don't exist.
> 
> I have no idea whatsoever what the "TIMES value is negative" error is all
> about. My assembler knowledge is very limited. The line in FAT.ASM reads ...
> 
>     times 510-($-$$) db 0   ; Pad to 510 bytes
> 

I have never seen this before. Which nasm version are you using? My best
guess is that fat.asm assembles to a binary larger than 510 bytes.

Re: [ros-kernel] Problems building freeldr

[Nick D. <nic...@ya...>]

Casper, Eric, thanks.

I made the (rather stupid) assumption that DJGPP had an assembler that came
with it. However, having downloaded the latest version of NASM, FREELDR
still chucks a wobbly.

Now it's saying: (it does the same with NASM and NASMW ...)

C:\rosdev\build\freeldr>make -k
make -C bootsect
make[1]: Entering directory `C:/rosdev/build/freeldr/bootsect'
nasm -o fat.bin -f bin fat.asm
fat.asm:379: error: TIMES value -9 is negative
make[1]: *** [fat.bin] Error 1
make[1]: Target `all' not remade because of errors.
make[1]: Leaving directory `C:/rosdev/build/freeldr/bootsect'
make: *** [bootsect] Error 2
make -C install
make[1]: Entering directory `C:/rosdev/build/freeldr/install'
gcc -Wall -o install.o -c install.c
install.c:26: ../bootsect/fat.h: No such file or directory
make[1]: *** [install.o] Error 1
make[1]: Target `all' not remade because of errors.
make[1]: Leaving directory `C:/rosdev/build/freeldr/install'
make: *** [install] Error 2
make: Target `all' not remade because of errors.


Looking at the source, I can see why it would have trouble finding it's
header files - they are in various subdirectories and there seems to be
nothing in either the makefile or actual source that mentions the path. Even
copying the header files to a common subdirectory and changing the path in
the source causes GCC to claim the files don't exist.

I have no idea whatsoever what the "TIMES value is negative" error is all
about. My assembler knowledge is very limited. The line in FAT.ASM reads ...

    times 510-($-$$) db 0   ; Pad to 510 bytes


Kind Regards,

Nick.

--
Nick Date
Bath, England, UK


----- Original Message -----
From: "Nick J. Date" <nic...@ya...>
To: <rea...@li...>
Sent: Monday, May 20, 2002 4:14 PM
Subject: [ros-kernel] Problems building freeldr


> Hi guys,
>
> I'm probably doing my usual being thick thing, but I can't get freeldr to
> build. I have WinXP Pro and DJGPP is installed properly (to the best of my
> knowledge) in C:\DJGPP with a path to C:\DJGPP\BIN and set DJGPP to
> C:\DJGPP\DJGPP.ENV.
>
> I have a primary NTFS partition with XP on it and a primary FAT partition
> that I intend to install ROS on (and maybe use XP's bootloader if it'll
> work - does that mean I don't need FREELDR?)
>
> Anyways, FREELDR won't build. The output is attached so if anyone could
give
> me some pointers it would be much appreciated.
>
> Thanks,
>
> Nick.
>
> --
> Nick Date
> Bath, England, United Kingdom
>
>
>
> ---
> Outgoing mail is certified virus free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.362 / Virus Database: 199 - Release Date: 07/05/2002
>


---
Outgoing mail is certified virus free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.362 / Virus Database: 199 - Release Date: 07/05/2002


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: [ros-kernel] Problems with the last changes (mdl.c..)

[Eric K. <ek...@rz...>]

"David Welch" <we...@cw...> wrote:

> Yes of course, I hadn't considered the possibly that the stack could be
> mapped by a lazily allocated page table. I don't think this fixes all the
> problems however since, in principle, a thread could be switched to while
> it is attached to a different process. Would it be possible to try the
> attached patch instead?

I saw the same crash yesterday when I came home and tried the latest CVS.
Your patch fixes the crash!

Thanks,
Eric

Re: [ros-kernel] Restructuring CVS Take 2

[Robert K. <ro...@ko...>]

>
> >If I remember previous threads here, if I replace nt dll's on startup nt
> >will restore them to the ms versions again, is a work around available?
>
> Delete the copies in the dllcache folder of the files you want to replace:
> WFP won't be able to restore the original files without your intervention.
> Another trick involves cracking the WFP dll and setting some parameter in
> the registry

An elegant way around WFP is using these two commands in CMD

>sfc /cachesize:1
reboot <- it is recommended but should work without
>sfc /Purgecache

>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel

Re: [ros-kernel] Problems with the last changes (mdl.c..)

[David W. <we...@cw...>]

On Mon, May 20, 2002 at 10:05:07PM +0200, Hartmut Birr wrote:
> It seems, that cr3 is not printed correct. The faulting eip points to 'sti' 
> within Ki386ContextSwitch. The correct value for cr3 is in eax. The 
> faulting thread is created with PsCreateSystemThread from win32k. The 
> context (cr3) is from win32k. The faulting address (cr2) points to the 
> stack. It seems, that the stack is not visible for some processes. I've 
> added a KeAttachProcess/KeDetacheProcess sequence in PsInitializeThread. 
> This solves my problem.
> 
Yes of course, I hadn't considered the possibly that the stack could be 
mapped by a lazily allocated page table. I don't think this fixes all the 
problems however since, in principle, a thread could be switched to while 
it is attached to a different process. Would it be possible to try the
attached patch instead?

Re: [ros-kernel] Restructuring CVS Take 2

[KJK::Hyperion <no...@li...>]

At 21.46 20/05/2002, you wrote:
> > Well the WINE related stuff can really be blown away. We should keep
> > thecurrent makefilesBut everything else in our wine tree can be zapped. We
> > need to write ashell script to take the wine makefiles and convert them in
> > to ReactOSmakefiles.
>do you mind putting binaries dll's online, so people will be able to test 
>them now on ms-win32 environments? will they work on win98?

Not the core DLLs (kernel32, user32, gdi32), because they talk directly to 
the kernel

>If I remember previous threads here, if I replace nt dll's on startup nt 
>will restore them to the ms versions again, is a work around available?

Delete the copies in the dllcache folder of the files you want to replace: 
WFP won't be able to restore the original files without your intervention. 
Another trick involves cracking the WFP dll and setting some parameter in 
the registry

Re: [ros-kernel] Problems with the last changes (mdl.c..)

[Hartmut B. <har...@te...>]

> -----Ursprungliche Nachricht-----
> Von:	we...@cw... [SMTP:we...@cw...]
> Gesendet am:	Montag, 20. Mai 2002 13:42
> An:	rea...@li...
> Betreff:	Re: [ros-kernel] Problems with the last changes (mdl.c..)
>
> I don't know. The crash report you posted shows the cr3 value as zero so
> most likely either the thread (or its parent process) being switched to
> is corrupt.

It seems, that cr3 is not printed correct. The faulting eip points to 'sti' 
within Ki386ContextSwitch. The correct value for cr3 is in eax. The 
faulting thread is created with PsCreateSystemThread from win32k. The 
context (cr3) is from win32k. The faulting address (cr2) points to the 
stack. It seems, that the stack is not visible for some processes. I've 
added a KeAttachProcess/KeDetacheProcess sequence in PsInitializeThread. 
This solves my problem.

- Hartmut

 ------ =_NextPart_000_01C2004A.FF5A19B0
Content-Type: application/octet-stream; name="create.c.diff"
Content-Transfer-Encoding: base64

DQpKOlxTYW5kYm94XFJvc1xyZWFjdG9zX3dvcmtcbnRvc2tybmxccHM+Y3ZzLmV4ZSAtZCA6ZXh0
OmhiaXJyQG1vay5sdmNtLmNvbTovQ1ZTL1JlYWN0T1MgLXo5IGRpZmYgLXUgY3JlYXRlLmMgICAg
ICAgDQpJbmRleDogY3JlYXRlLmMNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NClJDUyBmaWxlOiAvQ1ZTL1JlYWN0T1Mv
cmVhY3Rvcy9udG9za3JubC9wcy9jcmVhdGUuYyx2DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuNDYN
CmRpZmYgLXUgLXIxLjQ2IGNyZWF0ZS5jDQotLS0gY3JlYXRlLmMJNSBNYXIgMjAwMiAwMDoyMDo1
NCAtMDAwMAkxLjQ2DQorKysgY3JlYXRlLmMJMjAgTWF5IDIwMDIgMjA6MDk6MTcgLTAwMDANCkBA
IC00MDAsOCArNDAwLDExIEBADQogICAgRFBSSU5UKCJUaHJlYWQgPSAleFxuIixUaHJlYWQpOw0K
ICAgIA0KICAgIFBpTnJUaHJlYWRzKys7DQotICAgDQorDQorICAgS2VBdHRhY2hQcm9jZXNzKFBy
b2Nlc3MpOw0KICAgIEtlSW5pdGlhbGl6ZVRocmVhZCgmUHJvY2Vzcy0+UGNiLCAmVGhyZWFkLT5U
Y2IsIEZpcnN0KTsNCisgICBLZURldGFjaFByb2Nlc3MoKTsNCisNCiAgICBUaHJlYWQtPlRocmVh
ZHNQcm9jZXNzID0gUHJvY2VzczsNCiAgICAvKg0KICAgICAqIEZJWE1FOiBXaGF0IGxvY2sgcHJv
dGVjdHMgdGhpcz8NCg==

RE: [ros-kernel] Restructuring CVS Take 2

[Steven E. <Ste...@ya...>]

> do you mind putting binaries dll's online, so people will be 
> able to test them 
> now on ms-win32 environments? will they work on win98? If I 
> remember previous 
> threads here, if I replace nt dll's on startup nt will 
> restore them to the ms 
> versions again, is a work around available?

Some of them may work under 98 but I am not going to support it and
neither is the 
Wine project. There is a fix for Windows2000 replacing the files, you
will need to search google for "disable windows file protection"

So you want to help me test? KICKASS. I will put a link up with the
current binarys tonight.

> riched32.dll: are there stubs functions or is it <fully> 
> working? Please 
> update from wine's cvs, since I know that currently bidi is 
> introduced into 
> wine by IBM Israel and some users. I wonder how bad will it work ;)

Not 100% sure but if you want you can help me test everything.

Here is the list of dlls we can compile with a Mingw host as of 5-20-02.
Once again some of these are mostly stubs. 

	avicap32.dll
	crtdll.dll
	crypt32.dll
	dciman32.dll
	imagehlp.dll
	imm32.dll
	mapi32.dll
	mpr.dll
	msdom.dll
	msimg32.dll
	msisys.ocx
	netapi.dll
	oledlg.dll
	olepro32.dll
	olesvr32.dll
	rasapi32.dll
	riched32.dll
	serialui.dll
	shdocvw.dll
	tapi32.dll
	twain_32.dll
	urlmon.dll
	winnls.dll
	winspool.drv
	wintrust.dll

Builds with easy fix -
	comcat.dll (needs msvcrt import due to swprintf usage)
	dinput.dll (needs msvcrt import do to _assert usage)
	odbc32.dll (needs msvcrt import do to _assert usage)

Re: [ros-kernel] Restructuring CVS Take 2

[Diego I. <ias...@ac...>]

On Monday 20 May 2002 05:56, Steven Edwards wrote:
> Well the WINE related stuff can really be blown away. We should keep
> thecurrent makefilesBut everything else in our wine tree can be zapped. We
> need to write ashell script to take the wine makefiles and convert them in
> to ReactOSmakefiles.
do you mind putting binaries dll's online, so people will be able to test them 
now on ms-win32 environments? will they work on win98? If I remember previous 
threads here, if I replace nt dll's on startup nt will restore them to the ms 
versions again, is a work around available?

riched32.dll: are there stubs functions or is it <fully> working? Please 
update from wine's cvs, since I know that currently bidi is introduced into 
wine by IBM Israel and some users. I wonder how bad will it work ;)

  - diego

-- 
The so-called lessons of history are for the most part the rationalizations
of the victors.  History is written by the survivors.
		-- Max Lerner

Re: [ros-kernel] Problems building freeldr

[Eric K. <ek...@rz...>]

"Nick J. Date" <nic...@ya...> wrote:

> Anyways, FREELDR won't build. The output is attached so if anyone could
give
> me some pointers it would be much appreciated.

The log file says that NASM is missing. Install it if you don't have it and
make sure the path to the nasm binary is in your PATH.


Eric Kohl

Re: [ros-kernel] Problems building freeldr

[Casper H. <ch...@us...>]

man, 2002-05-20 kl. 17:14 skrev Nick J. Date:
> Hi guys,
> 
> I'm probably doing my usual being thick thing, but I can't get freeldr to
> build. I have WinXP Pro and DJGPP is installed properly (to the best of my
> knowledge) in C:\DJGPP with a path to C:\DJGPP\BIN and set DJGPP to
> C:\DJGPP\DJGPP.ENV.
> 
> I have a primary NTFS partition with XP on it and a primary FAT partition
> that I intend to install ROS on (and maybe use XP's bootloader if it'll
> work - does that mean I don't need FREELDR?)
> 
> Anyways, FREELDR won't build. The output is attached so if anyone could give
> me some pointers it would be much appreciated.

I remember having to hack the makefiles to get it to build properly. I
had to use MinGW to compile some of the applications because the DJGPP
generated applications would not run on Windows XP. Your particular
problem seems to be that you don't have nasm.exe in your path. If you
have nasmw, try copying it and then rename it to nasm. If not, then you
can get it from the website.

[ros-kernel] Problems building freeldr

[Nick J. D. <nic...@ya...>]

Hi guys,

I'm probably doing my usual being thick thing, but I can't get freeldr to
build. I have WinXP Pro and DJGPP is installed properly (to the best of my
knowledge) in C:\DJGPP with a path to C:\DJGPP\BIN and set DJGPP to
C:\DJGPP\DJGPP.ENV.

I have a primary NTFS partition with XP on it and a primary FAT partition
that I intend to install ROS on (and maybe use XP's bootloader if it'll
work - does that mean I don't need FREELDR?)

Anyways, FREELDR won't build. The output is attached so if anyone could give
me some pointers it would be much appreciated.

Thanks,

Nick.

--
Nick Date
Bath, England, United Kingdom



---
Outgoing mail is certified virus free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.362 / Virus Database: 199 - Release Date: 07/05/2002

[ros-kernel] FW: Requested Change to the wine build system

[Steven E. <Ste...@ya...>]

This will be cool when then new binutils comes out.

"Steven Edwards" <Ste...@ya...> wrote:

> In the ReactOS tree we have a "make implib" rule to generate all of 
> the import Libs for our shared libs. This way we are not dependant on 
> the mingw win32api.
> I think the wine tree needs to do something similer. Once this is done
> we can 
> go ahead and build the import libs for ntdll, msvcrt and User32 that
are
> needed 
> for the wine dlls. 
> 
> The command line is something like this
> dlltool --as=as --dllname user32.dll --def user32.spec.def 
> --output-lib libuser32.a

I would recommend the following command lines to build both import
library and dll with *correct* import/export tables:

DLLWRAPFLAGS = -mno-windows -k --def $(MODULE).spec.def
-Wl,--kill-at,--enable-stdcall-fixup

(probably --enable-stdcall-fixup is now obsoleted by recent winebuild
changes)

$(RM) $(TOPOBJDIR)/dlls/lib$(MODULE).a
$(DLLWRAP) $(DLLWRAPFLAGS) $(ALL_OBJS) -o $@ $(IMPORTS:%=-L$(DLLDIR)
-l%) $(ALL_LIBS)
$(DLLTOOL) --kill-at --input-def $(MODULE).spec.def --output-lib
lib$(MODULE).a
$(CP) lib$(MODULE).a $(TOPOBJDIR)/dlls/lib$(MODULE).a

You need dlltool from binutils CVS because my fix regarding
decorated/non-decorated imports/exports haven't found its way to 2.12
yet. This fix allows to not require to have *two* .def file sets (with
decorated and non-decorated exports as in ReactOS).

Also, since $(MODULE) has an extension included now, you need some
workaround for this.

-- 
Dmitry.

Re: [ros-kernel] Problems with the last changes (mdl.c..)

[<we...@cw...>]

Quoting Hartmut Birr <har...@te...>:
> I've some problems with the last changes. Some weeks (month ?) ago, I've
> changed the parameter in subsys/smss/init.c line 374 from FALSE to TRUE.
> This means, the registry files are build, if they do not exist. With the
> last changes and existing registry files, ros does crash. Without the 
> registry files, ros builds the registry files and does boot without any
> problems. I've remove the last changes (mdl.c, aspace.c ..) and there is
> no problem. What's wrong between the registry and the last changes ?
> 
I don't know. The crash report you posted shows the cr3 value as zero so
most likely either the thread (or its parent process) being switched to
is corrupt. The mdl changes set up a large (256MB) region in the kernel address 
space so it may be causing some problems just by shuffling pointer values 
around. The parent process seems to be c0238a0a so if the system you
debugging on can set memory breakpoints it would be interesting to see what
happens to the PageDirectoryBase member; if this thread has been run before
then a pointer to it will be on the stack otherwise Ki386ContextSwitch
could be changed (e.g. load the process pointer into edi rather than ebx) so it 
is possible to read it off from an exception report.

[ros-kernel] Problems with the last changes (mdl.c..)

[Hartmut B. <har...@te...>]

Hi,

I've some problems with the last changes. Some weeks (month ?) ago, I've 
changed the parameter in subsys/smss/init.c line 374 from FALSE to TRUE. 
This means, the registry files are build, if they do not exist. With the 
last changes and existing registry files, ros does crash. Without the 
registry files, ros builds the registry files and does boot without any 
problems. I've remove the last changes (mdl.c, aspace.c ..) and there is no 
problem. What's wrong between the registry and the last changes ?

- Hartmut



  

RE: [ros-kernel] Restructuring CVS Take 2

[Steven E. <Ste...@ya...>]

>> * Move WINE related DLLs now?

Well the WINE related stuff can really be blown away. We should keep the
current makefiles
But everything else in our wine tree can be zapped. We need to write a
shell script to take the wine makefiles and convert them in to ReactOS
makefiles.

We still will not be able to use wine untill some internal non-win32
functions are fixed in the wine tree. 

I have put together a little guide for Wine/ReactOS hacking. Once we get
a little more along I will break the guide up and make a Mingw Developer
Guide for the WINE project and a ReactOS wine Hacker guide.

I will email more tommrow I'm kinda in a rush.

Thanks
Steven

"Every revolution was once a thought in one man's mind"
- Ralph Waldo Emerson 

[ros-kernel] Restructuring CVS Take 2

[Jason F. <jas...@ya...>]

Ok... now that things seem to have quietened down a bit again, let's
take up the issue of restructuring our source tree.

Here's what I have based on previous mails:

apps/*: removing apps/test, move apps/system to subsys
lib/bzip2: move to services/lib
lib/crtdll: move to win32 module
lib/dflat32: move to rosapps module (?)
lib/fmifs: move to win32 module
lib/msvcrt: move to win32 module
lib/ole32: move to win32 module
lib/oleaut32: move to win32 module
lib/psapi: move to win32 module
lib/shell32: move to win32 module
lib/version: move to win32 module
lib/zlib: move to services/lib
lib/ole: move to win32 module
lib/ole32: move to win32 module
lib/rpcrt4: move to win32 module
lib/psapi: move to win32 module (?)
subsys/os2/*: move to os2 module
subsys/psx/*: move to posix module

* Move WINE related DLLs now?

Input please
Thanks

- Jason







__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com

Re: [ros-kernel] sectest

[Casper H. <ch...@us...>]

s=F8n, 2002-05-19 kl. 22:50 skrev David Kredba:
>=20
>=20
> Machine is 2*866 PIII, 1024 MB RAM
> booted with aboot.bat, config: kdbg=3D1, dbg=3D1, acpi=3D1.
>=20
>=20
> There are two problems with sectest.
>=20
>=20
> The first :
>=20
> The makefile of sectest breaks the build process:
>=20
> make -C apps/sectest implib
> : Invalid argument
> : No such file or directoryk
> '.  Stop.*** No rule to make target `tools/helper.mk
> make[1]: Entering directory `C:/ros/reactos/apps/sectest'
> make[1]: Leaving directory `C:/ros/reactos/apps/sectest'
> make: *** [sectest_implib] Error 2
>=20
> If I copy there makefile from directory isotest and remade it for sectest
> build process goes its way.
>=20
> Perhaps wrong EOF or EOLN ? I don`t know.

Possibly, but shouldn't CVS take care of this?

> The second :
>=20
>=20
> After runnig sectest I got :
>=20
> Section Test
>=20
> Bug detected code: 0x1D
> Divide Error Exception: 0(0)
>=20
> ntoskrnl.exe: _ObFindObject
>=20
> cr2 0 cr3 3f7ef000
>=20
> ntoskrnl.exe: _ObCreateObject@20
>                     _MmCreateDataFileSection
>                     _NtCreateSection@28
>                     _interrupt_handler2e

The memory manager still needs some work before sectest can be
successfully run on ReactOS.