Ros-dev

ros-dev@reactos.org

5788 discussions

by Timo Kreuzer

Hi, Bugs in bugzilla: - There are still some bugs in bugzilla. you cannot view a single attachment, you can only view them all together. This is because the link doesn't include the attachment id. Same for diff and edit. - When trying to edit a patch from the view all page, you will see the reactos.org main page inside the edit window, wich is probably a similar bug. - Searching doesn't work anymore from the main page Enhancements: - Add VMWare Server to "Hardware" list - Compontenst: we currently have Documentation, Drivers, Kernel, Networking, Patches, Setup, Shell, sound, Win32 We should add Applications, Services, Tools, Subsystems, maybe unknown, if you don't know where the bug is located. Maybe also add bugzilla to Web Services component list. - Maybe a flag for regression would be nice - A flag for "3rd party comaptiblity" would also be nice, so we see, if the bug is effecting ROS itself or "only" a 3rd party app. Greetings, Timo

17 years, 8 months

Re: [ros-dev] ROS Livecd issue

by Murphy, Ged (Bolton)

Why are you trying to partition a vmware drive? The correct way to setup vmware is to create a virtual disk (a few 100Mb will do) and allocate the space for this drive upon creation. You then install ROS into this. ROS needs to play no part in creating partition, it only needs to format the partition created by vmware. ROS is quite stable in vmware and qemu at the moment. -----Original Message----- From: Muguntharaj Subramanian [mailto:mugunth@gmail.com] Sent: 09 January 2007 07:18 To: ReactOS Development List Subject: Re: [ros-dev] ROS Livecd issue Hi All, I checked out the source again yesterday and built a fresh iso (bootcd). And again i find the same issue i.e "partition signature != 55AA" error while trying out the created iso with VMware. Has anybody else tried the same way? My objective is to compile the reactos iso from source first. Then plan to add applications and try to fix some bugs in my free time. For that i feel its better to use VMware instead of running fresh install (also i dont have spare machine to do fresh installation). Is the current builds working in QEMU? Regards, Mugunth On 1/8/07, Mikhail Y. Zvyozdochkin <mzvyozd(a)narod.ru <mailto:mzvyozd@narod.ru> > wrote: Felipe Villarroel wrote: >On 1/5/07, Muguntharaj Subramanian < mugunth(a)gmail.com <mailto:mugunth@gmail.com> > wrote: > > >>... >>partition signature != 55AA >>... >> >> >You have a corrupted MBR or partition table. Reinstall ReactOS and do >proper partitioning. > > Hm, Hm... It's not so simply. I got same error with _fresh-installed_ ReactOS. WBR, DarkHobbit _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org <mailto:Ros-dev@reactos.org> http://www.reactos.org/mailman/listinfo/ros-dev <http://www.reactos.org/mailman/listinfo/ros-dev> -- http://mugunth.blogspot.com <http://mugunth.blogspot.com> http://thamizha.com <http://thamizha.com> http://tamilblogs.com <http://tamilblogs.com> -- http://webspace2host.com <http://webspace2host.com> "Your friendly hosting provider"

17 years, 8 months

Important News and Updates

by Alex Ionescu

Dear ReactOS Users, Testers and Developers, I've chosen to write up a small letter with some recent news on ReactOS' development. I'm hoping that putting my name behind it will increase the number of people interested and informed. - First of all, a small update on the kernel. I'm currently working on Ob, the Object Manager. I have a large patch that I've split up into 4. The first patch addresses several bugs and adds more security paths and checks that will be required for later functionality. The second patch adds some lacking functionality to the Object Manager which might have caused bugs in the I/O Manager. The third patch adds locking and scalability improvements to the Object Manager, and fixes multiple race conditions which could've led to random crashes. The last patch should cleanup and remaining bugs/fixmes apart from non-implemented but not-critical functionality. After this is done, I plan on working in the Kernel itself to make sure that ReactOS boots on VMWare 6.0 and VMWare Server 1.1 (my current Vmware testing platforms). I generally use KQEMU, so VMWare bugs are usually hidden from me. I also have a nice piece of code from one of our older developers (blight/Gregor Anich) which should allow me to fix Mesa, aka OpenGL. After these low-level regressions have been fixed, I will then commit my new LPC code, and start working on cleaning up some old Ex code. These changes will basically make ReactOS more compatible and reliable, by auditing for broken code. - Secondly, on the topic of regression testing. I'm hoping most of you are now using the official RosBE, the ReactOS Building Environment. If you're not, please do so (on Windows). It is the *only* supported environment. If you're having problems with headers, compiling, or are seeing boot failures, please do not come to ask us for help until you are using the RosBE. This will help us avoid many compiler incompatibilities and make us bettter able to help you in a timely fashion. Because such problems can also arise from badly configured emulators, I will create the RosTE, or ReactOS Testing Environment. This will be a packaged version of KQEMU along with several helpful utilities and scripts, which will allow you to mount and unmount your qemu image, use make_install properly, use make install_registry properly, test ReactOS and the LiveCD/BootCD in the latest patched QEMU with the KQEMU Accelerator module in full-kernel mode (an improvement of 4x+ over standard QEMU), as well as the Serial Port Redirection Gateway which will allow you to get qemu's output in a telnet box with unlimited easy scrolling, as well as the ability to copy/paste text from it, which is normally impossible with QEMU. This version will also support using WinDBG to debug ReactOS, when our kernel implements Kd. In the end, the RosBE and RosTE should make it a lot easier to identify the source of some common problems experienced by testers. I cannot offer a similar TE for VMWare unfortunately, since that's a commercial product, and VMWare still offers an interesting testing framework because it behaves differently from QEmu in many ways. However, if you have an issue in VMWare, I strongly suggest you then try out to reproduce it in RosTE, once it will be available. That way, we'll be able to isolate the bug to an emulator. - I have been invited as a speaker to multiple conferences this year, where I will have a chance to talk about, and present ReactOS, in hopes of making stronger ties with the FOSS community, raise awareness for the project, and get more developers/support. One of them is the SOCAL 2007 Expo in Los Angeles in Feburary this year, and another one is the Intertional Free Software Forum in April, in Brazil. There also remains the possibility of other such expos. Because these conferences are not commercial, even speakers do not usually have their air fare or hotel costs covered. As I am a student, travel fare to these places makes a large dent in my savings, since a single conference alone can cost me 1500$ or more including air travel, hotel, food, transporation, etc. As a result, your donations would be greatly appreciated. The ReactOS Foundation should start an official fundraiser tomorrow or later this week as soon as the new webpage is properly working. I urge you to donate and help me out so that I can have the chance to promote ReactOS. Additionally, the money you donate will also help ReactOS with bandwidth costs, server upgrades, etc, so it's not a personal Alex fund. - Finally, Aleksey made some suggestions on my behalf recently, as well as posted some requests. I will re-address the latter here, because these are really important to me: 1) Someone please look at rbuild's dependency code and make it output a dependency tree, that can be read by a human. This should let me see things such as "oh ok, ntdll needs libfoo, and libfoo needs libbar". Or "oh, this 10KB application requires a 100MB library, can we do something better here?". 2) Someone please look at rbuild's XML parsing and "Component/module" creation so that it is possible to build an entire directory as a component. For example, "make drivers" should work, as well as "make base". - That's all, thank you for your time. -- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

17 years, 8 months

Re: [ros-dev] ROS Livecd issue

by Alex Ionescu

hto(a)mail.cnt.ru wrote: >>IIRC, partitioning is broken in ROS, so you have to >>create the partition with something different than >>the ReactOS installer. I'd guess FreeDOS should work. > > > There is temporary patch to broken partitioning code: > www.reactos.org/bugzilla/attachment.cgi?id=1181&action=view > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > I don't think that's where the bug is... I'm going to write a test driver that calls the ROS and the Windows function and compare the results. -- Best regards, Alex Ionescu Project Lead, TinyKRNL Kernel-Mode Software Design Engineer, ReactOS

17 years, 8 months

ROS Livecd issue

by hto＠mail.cnt.ru

> IIRC, partitioning is broken in ROS, so you have to > create the partition with something different than > the ReactOS installer. I'd guess FreeDOS should work. There is temporary patch to broken partitioning code: www.reactos.org/bugzilla/attachment.cgi?id=1181&action=view

17 years, 8 months

Re: [ros-dev] ROS Livecd issue

by David Ianno

Hello, You need to change the bootup device options in the BIOS from the harddisk to the cdrom and run the bootcd again. Regards, David Ianno (Quip) Muguntharaj Subramanian <mugunth(a)gmail.com> wrote: On 1/5/07, Felipe Villarroel <fvillarroels(a)gmail.com> wrote: 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) Hi Felipe Villarroel, I have set the following in rbuild.conf <property name="DBG" value="1" /> And have successfully built bootcd (ReactOS.iso). When I tried it using vmware, I get the following error: partition signature != 55AA what could be the reason? How to get more information, where can i get the logs? Regards, Mugunth good luck, Logan_V8 -- http://mugunth.blogspot.com http://thamizha.com _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

17 years, 8 months

Re: [ros-dev] ROS Livecd issue

by David Hinz

IIRC, partitioning is broken in ROS, so you have to create the partition with something different than the ReactOS installer. I'd guess FreeDOS should work. Greets, David Hinz Felipe Villarroel schrieb: > On 1/5/07, Muguntharaj Subramanian <mugunth(a)gmail.com> wrote: >> When I tried it using vmware, I get the following error: >> >> partition signature != 55AA >> >> what could be the reason? How to get more information, where can i get the >> logs? >> > You have a corrupted MBR or partition table. Reinstall ReactOS and do > proper partitioning. For logs you have to redirect your virtual serial > port, look at the wiki for information. > > Best regards, > Logan_V8 > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev >

17 years, 8 months

Re: [ros-dev] ROS Livecd issue

by Felipe Villarroel

On 1/5/07, Muguntharaj Subramanian <mugunth(a)gmail.com> wrote: > > When I tried it using vmware, I get the following error: > > partition signature != 55AA > > what could be the reason? How to get more information, where can i get the > logs? > You have a corrupted MBR or partition table. Reinstall ReactOS and do proper partitioning. For logs you have to redirect your virtual serial port, look at the wiki for information. Best regards, Logan_V8

17 years, 8 months

Re: [ros-dev] ROS Livecd issue

by Muguntharaj Subramanian

On 1/5/07, Felipe Villarroel <fvillarroels(a)gmail.com> wrote: > > 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) Hi Felipe Villarroel, I have set the following in rbuild.conf <property name="DBG" value="1" /> And have successfully built bootcd (ReactOS.iso). When I tried it using vmware, I get the following error: partition signature != 55AA what could be the reason? How to get more information, where can i get the logs? Regards, Mugunth good luck, > Logan_V8 > -- http://mugunth.blogspot.com http://thamizha.com

17 years, 8 months

Re: [ros-dev] [ros-diffs] [mbosma] 25290: Make Downloader perform better un der ReactOS: - Use other font. - Redraw buttons at resize.

by Murphy, Ged (Bolton)

mbosma(a)svn.reactos.org wrote: > ResizeControl(hApps, Split_Vertical+5, 60, > LOWORD(lParam)-10, Split_Hozizontal); > + RECT Rect = {Split_Vertical+5, Split_Hozizontal+5, > LOWORD(lParam)-10, HIWORD(lParam)-50}; > DescriptionRect = Rect; C++ hiccup

17 years, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev