Hi,
> Can you please explain this. Where exactly I have to make changes?
Different timings and different memory locations could hide (or show) problems.
You need to build bootcd. (mingw32-make bootcd)
you can set DBG to 1 in config.rbuild to compile with debug messages.
(based on config.template.rbuild).
Boot your virtual machine with the created bootcd (ReactOS.iso,
created after sucessful compilation), and install ReactOS on a virtual
disk (> 200MiB should be good). (I'm assuming that you have the free
VMware Server)
good luck,
Logan_V8
On 1/4/07, Muguntharaj Subramanian <mugunth(a)gmail.com> wrote:
>
>
> On 1/4/07, Felipe Villarroel <fvillarroels(a)gmail.com> wrote:
> > Hi,
> > sometimes trunk is unstable, but have you tried to install bootcd in a
> > disk image instead?.
> > Try to select ReactOS (debug) in Freeloader, instead of the ReactOS
> > entry. Sometimes the debug messages make it works.
>
> Hi Felipe Villarroel,
> Thanks for your reply.
>
> Can you please explain this. Where exactly I have to make changes?
>
> Regards,
> Mugunth
>
> > If the current bootcd/livecd doesn't work, try again in a few days.
> >
> > Best regards,
> > Logan_V8
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
Muguntharaj Subramanian wrote:
> Then I tried using this ReactOS-LiveCD.iso
> using VMware installed in another Linux Machine.
> It progresses upto ReactOS splash screen, then stops responding.
> What could be the issue? Am I missing something?
Livecd in trunk is broken, use the bootcd instead.
There is no need to use a livecd in vmware anyway.
On 1/4/07, Felipe Villarroel <fvillarroels(a)gmail.com> wrote:
>
> Hi,
> sometimes trunk is unstable, but have you tried to install bootcd in a
> disk image instead?.
> Try to select ReactOS (debug) in Freeloader, instead of the ReactOS
> entry. Sometimes the debug messages make it works.
Hi Felipe Villarroel,
Thanks for your reply.
Can you please explain this. Where exactly I have to make changes?
Regards,
Mugunth
If the current bootcd/livecd doesn't work, try again in a few days.
>
> Best regards,
> Logan_V8
Dear All,
I am newbie to this list.This is my first post. I came to know about reactos
recently. And tried reactos vmware image and was very much impressed. I
would like to thank all of you who have been involved in this project.
I tried my hand in building ReacOS Livecd today.
I used WindowsXP machine to build this. Followed the steps given in these
URLs:
http://www.reactos.org/wiki/index.php/HOWTO/setup_a_build_environment_for_W…http://www.reactos.org/wiki/index.php/Building_ReactOS
I used GCC 3.4.5 ReactOS build Environment and successfuly built
ReactOS-LiveCD.iso in about 45 Minutes time.
Then I tried using this ReactOS-LiveCD.iso using VMware installed in another
Linux Machine.
It progresses upto ReactOS splash screen, then stops responding.
What could be the issue? Am I missing something?
Regards,
Mugunth
--
http://mugunth.blogspot.comhttp://thamizha.com
(forwarded for maarten bosma)
> [03 Jan 07 16:03] * Morpheouss * i am here just to say, that change made
in 25283 revision is not accurate
> [03 Jan 07 16:04] * Morpheouss * it was introduced in windows 2000, and it
fails when user have installed OS, MBR is not written, and OS is bootable...
> [03 Jan 07 16:05] * Morpheouss * eg. i use Linux and grub to boot it up
> [03 Jan 07 16:05] * Morpheouss * and windows 2000 doesn't show this
message and boots up
> [03 Jan 07 16:05] * Morpheouss * even if i wanted to boot linux
> [03 Jan 07 16:06] * Morpheouss * so i don't think it was a good idea
> [03 Jan 07 16:06] * Morpheouss * sometimes when i install windows i forget
to eject CD :P
> [03 Jan 07 16:06] * Morpheouss * it was better done in my opinion
> [03 Jan 07 16:07] * Morpheouss * when user could control it even MBR is
not written
> [03 Jan 07 16:09] * Morpheouss * in my opinion it should be reverted
Please comment.
> Author: mbosma
> Date: Wed Jan 3 17:33:41 2007
> New Revision: 25283
>
> URL: http://svn.reactos.org/svn/reactos?rev=25283&view=rev
> Log:
> Do not show "Press any key to boot from CD"-Message if there is no MBR on
the hard drive.
>
> Modified:
> trunk/reactos/boot/freeldr/bootsect/isoboot.asm
>
> Modified: trunk/reactos/boot/freeldr/bootsect/isoboot.asm
> URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/bootsect/isob…
>
==============================================================================
> --- trunk/reactos/boot/freeldr/bootsect/isoboot.asm (original)
> +++ trunk/reactos/boot/freeldr/bootsect/isoboot.asm Wed Jan 3 17:33:41
2007
> @@ -139,13 +139,21 @@
> jmp .kbd_buffer_test
> .kbd_buffer_empty:
>
> - ; Check if there is harddisk
> + ; Check for MBR on harddisk
> pusha
> - mov ax, 0800h
> + mov ax, 0201h
> mov dx, 0080h
> + mov cx, 0001h
> + mov bx, trackbuf
> int 13h
> popa
> - jc .boot_cdrom
> + jc .boot_cdrom ; could not read hdd
> +
> + push ax
> + mov ax, word [trackbuf]
> + cmp ax, 0
> + je .boot_cdrom ; no boot sector found (hopefully there are no
weird bootsectors which begin with 0)
> + pop ax
>
> ; Display the 'Press key' message and wait for a maximum of 5 seconds
> call crlf
Timo Kreuzer wrote:
> Doesn't this break build of rosapps on linux?
no
> I thought everything has to be lower case(?)
Nothing _needs_ to be lower case.
The problem you're referring to is that Linux file names are case sensitive,
where Windows isn't. This causes problem in Linux when rbuild files have the
opposite case to the actual file.
This normally flags up issues in asm files and resource files, e.g
asm.S / asm.s
En.rc / en.rc
> Greetings and Happy New Year,
And you ;)
Ged.
> Author: greatlrd
> Date: Mon Jan 1 16:37:24 2007
> New Revision: 25261
>
> URL: http://svn.reactos.org/svn/reactos?rev=25261&view=rev
> Log:
> Adding stubed arm4 for my CpuToIntel tool.
> Now we got tree diffent arch we can port over to intel x86 asm. But this
> tool are experment tool
>
> Modified:
> trunk/rosapps/devutils/cputointel/CpuToIntel.c
> trunk/rosapps/devutils/cputointel/cputointel.rbuild
>
> Modified: trunk/rosapps/devutils/cputointel/CpuToIntel.c
I miss the new files ;)
Hehe, perhaps reactos once boots up my psion 5 *g*
Happy new year to all!
mifritscher
Hi!,
I just wanted to say Happy New Year to everyone that works or likes
ReactOS!.
I hope that this new year will be better than 2006 for
you and your family and that the changes in ReactOS will reflect
the great and hard work of each of the developers that contribute
to the project.
I hope that 2007 will be a great year for ReactOS.
Best Regards,
Logan_V8
Magnus,
I beg my pardon, but since when is it allowed to revert someone
else's commit without discussing first?
There is a rule which might allow revert provided:
1) The change breaks booting
2) More than 24hours passed from the commit time
3) Author can not be contacted by any means
None of the above was true, so why did you make a reverting commit?
With the best regards,
Aleksey Bragin.
On Dec 30, 2006, at 4:11 AM, greatlrd(a)svn.reactos.org wrote:
> Author: greatlrd
> Date: Sat Dec 30 04:11:14 2006
> New Revision: 25246
>
> URL: http://svn.reactos.org/svn/reactos?rev=25246&view=rev
> Log:
> do not use hacked vfat drv revers the 25243
> the hacked do not delete pendling or incomplte data
> and so on,
>
> Modified:
> trunk/reactos/drivers/filesystems/vfat/cleanup.c
> trunk/reactos/drivers/filesystems/vfat/close.c
> trunk/reactos/drivers/filesystems/vfat/create.c
>
greatlrd(a)svn.reactos.org wrote:
> Author: greatlrd
> Date: Fri Dec 29 03:09:54 2006
> New Revision: 25236
>
> URL: http://svn.reactos.org/svn/reactos?rev=25236&view=rev
> Log:
> freetype cache glyth patch pass last all my test.patch
> ogrinal author of this patch is royce3, modify by tinus so it work again with trunk, ThePhysicist (timo dot kreuzer at web dot de) did fix the last bugs in it. at last long leave freetype glyth patch, now we got faster text output in reactos. and I where up to 38fps in winquake with this patch (debugbuild + serial debug on). This is very fast. I wonder what speed it give in release build or qemu now.
>
>
I think you should remove the hits++ and misses++ and hits > 100/misses
>100 code because it seems perf-debugging related only.
--
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design Engineer, ReactOS