reactos-kernel

Re: Re: [ros-kernel] Cannot boot current cvs tree

[<kr...@mb...>]

I'm stupid, I use nonstandard e-mail client.

It eats backslashes.

They are there in the right places.

Scsiport.sys,atapi.sys,class2.sys and disk.sys are loaded succesfly.


David

V 06/16/2002 - 11:57, Eric Kohl napsal:

> 
> "David Kredba" <kr...@mb...> wrote:
> 
> > Initializing system32driversvfatfs.sys
> 
> Where are the backslashes? This line should be "Initializing
> system32driversvfatfs.sys".
> 

Re: Re: [ros-kernel] Cannot boot current cvs tree

[<kr...@mb...>]

I'm so paranoid that I do full rebuild from clear updated source every time.



David



V 06/17/2002 - 20:53, Eric Kohl napsal:

> 
> "David Kredba" <kr...@mb...> wrote:
> 
> Hello David!
> 
> > It told :
> >
> > (ke/main.c:710) CommandLine:
> > multi(0)disk(0)rdisk(0)partition(1)reactos /DEBUGPORT=SCREEN
> >
> > and crash in the same funtctions.
> 
> Do you have a clean source tree or did you update your source tree when the
> crashes started?
> If you updated your source tree, make a full rebuild. Run "make clean" and
> then "make".
> 
> Since you seem to be the only one who experiences this crash, I assume you
> didn't run a full rebuild after the update.
> 
> 
> Eric
> 
> 
> 
> _______________________________________________________________
> 
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel
> 

Re: Re: [ros-kernel] Cannot boot current cvs tree

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

<kr...@mb...> wrote:

> I'm so paranoid that I do full rebuild from clear updated source every
time.

Then have a look at InitSystemSharedUserPage() in ntoskrnl/ke/main.c. There
are several calls to KeBugCheck(). If the function above the KeBugCheck()
call is a CPRINT macro, change "CPRINT" to "DPRINT1" and rebuild ntoskrnl
(run "make ntoskrnl"), install it and boot it. Now you should get  more
detailed information about where ntoskrnl actually crashes.

Eric

Re: Re: [ros-kernel] Cannot boot current cvs tree

[<kr...@mb...>]

Is it possible, that PCDOS causes my problem ?

I use PCDOS bootable diskette to switch my NT/Linux station into real DOS.

David

Re: Re: [ros-kernel] Cannot boot current cvs tree

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

<kr...@mb...> wrote:


> Is it possible, that PCDOS causes my problem ?
>
> I use PCDOS bootable diskette to switch my NT/Linux station into real DOS.

That's not impossible!

The current FreeDOS works as well as FreeLoader. Btw, using FreeLoader to
boot ReactOS is a lot faster than using DOS.

Eric

Re: Re: [ros-kernel] Cannot boot current cvs tree

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

<kr...@mb...> wrote:

> I'm stupid, I use nonstandard e-mail client.
>
> It eats backslashes.
>
> They are there in the right places.
>
> Scsiport.sys,atapi.sys,class2.sys and disk.sys are loaded succesfly.

Okay! What about the kernel command line and SystemRoot?
Please change ntoskrnl/ke/main.c line 710 "CPRINT(..." to "DPRINT1(..." and
rebuild ntoskrnl.

Is should say something like
"multi(0)disk(0)rdisk(0)partition(1)\reactos...".


Eric

Re: [ros-kernel] Cannot boot current cvs tree

[David K. <kr...@mb...>]

It told :

(ke/main.c:710) CommandLine:
multi(0)disk(0)rdisk(0)partition(1)\reactos /DEBUGPORT=SCREEN

and crash in the same funtctions.

David


> 
> Is should say something like
> "multi(0)disk(0)rdisk(0)partition(1)\reactos...".
> 
> 
> Eric
> 

Re: [ros-kernel] Cannot boot current cvs tree

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

"David Kredba" <kr...@mb...> wrote:

Hello David!

> It told :
>
> (ke/main.c:710) CommandLine:
> multi(0)disk(0)rdisk(0)partition(1)\reactos /DEBUGPORT=SCREEN
>
> and crash in the same funtctions.

Do you have a clean source tree or did you update your source tree when the
crashes started?
If you updated your source tree, make a full rebuild. Run "make clean" and
then "make".

Since you seem to be the only one who experiences this crash, I assume you
didn't run a full rebuild after the update.


Eric