Please tell me

[Fan Zhang]

Hi guys,

I want to know how do you debug ReactOS. For example, when I change the
code, I used to execute 'Make bootcd'. After that, I will install the
ReactOS system by ReactOS.iso. So I'm confused if I have to install the whoe
system after compiling. Do you have some easy way?
Thanks.

Fan

[Javier Agustìn Fernàndez Arroyo]

http://www.reactos.org/wiki/Debugging

;)

On Mon, Oct 25, 2010 at 12:02 PM, Fan Zhang <fanzi2009(a)gmail.com> wrote:

>   Hi guys,
>
>  I want to know how do you debug ReactOS. For example, when I change the
>  code, I used to execute 'Make bootcd'. After that, I will install the
>  ReactOS system by ReactOS.iso. So I'm confused if I have to install the whoe
>  system after compiling. Do you have some easy way?
>  Thanks.
>
>  Fan
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>

[Olaf Siejka]

You should be able to overwrite the files the code of which you changed. The
exception is with freeldr as well as registry entries.

2010/10/25 Fan Zhang <fanzi2009(a)gmail.com>

>   Hi guys,
>
>  I want to know how do you debug ReactOS. For example, when I change the
>  code, I used to execute 'Make bootcd'. After that, I will install the
>  ReactOS system by ReactOS.iso. So I'm confused if I have to install the whoe
>  system after compiling. Do you have some easy way?
>   Thanks.
>
>  Fan
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>

[Fan Zhang]

Thanks Olaf.  The method below is what I think, do you think it's
reasonalbe?
1.Install both Windows and ReactOS on the virtual machine such as
VirtualBox.
2.Enter windows system, cause it can share file between virtual machine and
the PC outside the virtual machine.
3.In windows, overwrite the file which I modified and reboot the virtual
machine.


On Mon, Oct 25, 2010 at 7:03 PM, Olaf Siejka <caemyr(a)gmail.com> wrote:

>   You should be able to overwrite the files the code of
> which you changed.
>  The exception is with freeldr as well as registry entries.
>
>  2010/10/25 Fan Zhang <fanzi2009(a)gmail.com>
>
> >   Hi guys,
> >
> >  I want to know how do you debug ReactOS. For example, when I change the
> >  code, I used to execute 'Make bootcd'. After that, I will install the
> >  ReactOS system by ReactOS.iso. So I'm confused if I have to install the whoe
> >  system after compiling. Do you have some easy way?
> >   Thanks.
> >
> >  Fan
> >
> >  _______________________________________________
> >  Ros-dev mailing list
> >  Ros-dev(a)reactos.org
> >  http://www.reactos.org/mailman/listinfo/ros-dev
> >  
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>

[victor martinez]

>  >Thanks Olaf.  The method below is what I think, do
> you think it's reasonalbe?
> >1.Install both Windows and ReactOS on the virtual machine such as VirtualBox.
> >2.Enter windows system, cause it can share file between virtual machine and the PC
> outside the virtual machine.
> >3.In windows, overwrite the file which I modified and reboot the virtual machine.

I am not Olaf but i don't know what you are trying to achieve.

If you want to test the behavior of a ReactOS file in Windows (replacing the original with
the ReactOS one) then you are right, that is the way.
If you want to test your compiled file in ReactOS then use MagicISO/PowerISO to create an
ISO file from that compiled file, then attach that ISO file to your ReactOS Virtual
Machine (as you did when installing ReactOS on it).Run the ReactOS VM, access to the CdRom
drive and voila you will find there the compiled file.

[Fan Zhang]

Thanks. But I don't know if i run ReactOS, how could I replace the kernel
file, such as ntoskrl.exe ?

On Mon, Oct 25, 2010 at 8:54 PM, victor martinez <vicmarcal(a)hotmail.com>wrote;wrote:

>  
>
> >  >Thanks Olaf.  The method below is what I
> > think, do you think it's 
>  reasonalbe?
> >  >1.Install both Windows and ReactOS on the
> > virtual machine such as 
>  VirtualBox.
> >  >2.Enter windows system, cause it can share
> > file between virtual machine 
>  and the PC outside the virtual machine.
> >  >3.In windows, overwrite the file which I
> > modified and reboot the virtual 
>  machine.
>
>
>  I am not Olaf but i don't know what you are trying to achieve.
>
>  If you want to test the behavior of a ReactOS file in Windows (replacing
>  the original with the ReactOS one) then you are right, that is the way.
>  If you want to test your compiled file in ReactOS then use
>  MagicISO/PowerISO to create an ISO file from that compiled file, then attach
>  that ISO file to your ReactOS Virtual Machine (as you did when installing
>  ReactOS on it).Run the ReactOS VM, access to the CdRom drive and voila you
>  will find there the compiled file.
>
>
>
>
>
>
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>

[Bernd Blaauw]

Op 25-10-2010 16:09, Fan Zhang schreef:
>   Thanks. But I don't know if i run ReactOS, how
> could I replace the 
>  kernel file, such as ntoskrl.exe ? 
So basicly running a ReactOS installation with RosBE installed as 
application, sources downloaded and modified, and then you want a way to 
update files from this ReactOS installation itself?
As long as ReactOS installs only on FAT filesystem, I guess you could 
use a DOS bootdisk/installation to overwrite any files. It's not 
entirely convenient.

Is there basicly a set of lists of ReactOS files for the following:
* which ReactOS files can be overwritten by a new file while you're 
still running in ReactOS? .inf files? small games like solitaire?
* which ReactOS files can be overwritten, but require a reboot to be 
properly noticed? some drivers perhaps?
* which ReactOS files require you to be outside of ReactOS in order to 
replace them? ntoskrnl comes to mind, explorer I guess

All in all, mr Fan Zhang might be asking for some kind of update 
mechanism. If you had an old machine which you run ReactOS on, together 
with same casual data (audio files perhaps), do you need to reformat the 
disk to update ReactOS? or only remove the installation directory? or 
pick a different installation directory? or same directory? After all, 
you don't want to lose any user data.

[Timo Kreuzer]

Hi,

What I usually do is mount the virtual machine image using VMware mount
utility, replace the files and umount again. Additionally I have a set
of batch files to one-click-update a number of freshly compiled binaries
from my working copy.

Regards,
Timo



Am 25.10.2010 14:41, schrieb Fan Zhang:
>   Thanks Olaf.  The method below is what I think, do you
> think it's
>  reasonalbe?
>  1.Install both Windows and ReactOS on the virtual machine such as
>  VirtualBox.
>  2.Enter windows system, cause it can share file between virtual
>  machine and the PC outside the virtual machine.
>  3.In windows, overwrite the file which I modified and reboot the
>  virtual machine.
>
>
>  On Mon, Oct 25, 2010 at 7:03 PM, Olaf Siejka <caemyr(a)gmail.com
>  <mailto:[e-mail]>> wrote:
>
>      You should be able to overwrite the files the code of which you
>      changed. The exception is with freeldr as well as registry entries.
>
>      2010/10/25 Fan Zhang &lt;fanzi2009(a)gmail.com
>      <mailto:[e-mail]>>
>
>          Hi guys,
>
>          I want to know how do you debug ReactOS. For example, when I
>          change the code, I used to execute 'Make bootcd'. After that,
>          I will install the ReactOS system by ReactOS.iso. So I'm
>          confused if I have to install the whoe system after compiling.
>          Do you have some easy way?
>           Thanks.
>
>          Fan
>
>          _______________________________________________
>          Ros-dev mailing list
>          Ros-dev(a)reactos.org <mailto:[e-mail]>
>          http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
>      _______________________________________________
>      Ros-dev mailing list
>      Ros-dev(a)reactos.org <mailto:[e-mail]>
>      http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev

[Aleksey Bragin]

Hi Fan,
reinstalling to test every small change is quite timeconsuming. I  
suggest you directly mount your virtual machine's harddrive (tools  
exists for this, e.g. VDK, or some virtual machines provide their own  
tools), and directly copy changed files into existing ros  
installation. Furthermore, if you set an env var ROS_INSTALL to Z: 
\ReactOS, and you mount VM harddrive to the letter Z:\, you can issue  
"make module_install" (e.g. make ntoskrnl_install) in RosBE, and it  
will automatically build and copy the file to the installation  
directory.

Hope this helps,
Aleksey.

On Oct 25, 2010, at 2:02 PM, Fan Zhang wrote:

>   Hi guys,
>
>  I want to know how do you debug ReactOS. For example, when I change  
>  the code, I used to execute 'Make bootcd'. After that, I will  
>  install the ReactOS system by ReactOS.iso. So I'm confused if I  
>  have to install the whoe system after compiling. Do you have some  
>  easy way?
>  Thanks.
>
>  Fan