Hello Everybody,
I am Erkal from Istanbul, Turkey. I am a C/C++ developer generally coding on
Windows. I have a deep experience of C and C++ coding in fields like
networking, 3D graphics, GUI programming.
I want to be part of ReactOS development team. I'd like to start with
localizing ReactOS for Turkey. There were no Turkish keyboard DLL's. I think
it may be a good entrypoint.
As an excited newbie, I am waiting for your valuable advices and
directions.
Best regards,
Erkal Dinçer
http://www.ibsyazilim.com
IBS, İstanbul Bilgi İletişim Sistemleri Tic. ve San. A.Ş
İstanbul Teknik Üniversitesi, Teknokent Arı 1 Binası No:6
34469 Maslak- İstanbul
Tel : +90 212 328 26 26
Fax : +90 212 328 25 94
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MmCopyFromCaller is deprecated! Use probing and SEH instead. All Code
using MmCopyFromCaller or MmCopyToCaller should be fixed, these APIs
should no longer be used for new code.
tkreuzer(a)svn.reactos.org wrote:
> Author: tkreuzer
> Date: Mon Jan 8 00:18:34 2007
> New Revision: 25352
>
> URL: http://svn.reactos.org/svn/reactos?rev=25352&view=rev
> Log:
> My first commit!
> NtGdiExtTextOut:
> - Unlock dc if failed
> - Copy string from usermode using MmCopyFromCaller
>
> Modified:
> trunk/reactos/subsystems/win32/win32k/objects/text.c
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
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"
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
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
> 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
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.comhttp://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
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
>
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
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.comhttp://thamizha.com
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
So I logged in and registered my user name about a week ago with
ReactOS, and now I am unable to log in. I tried resetting my password
on the site, and it still won't let me log in. Can you direct me to
information on how I can get logged in, or what may have happened?
Thanks,
Nathan
Ged Murphy wrote:
>
> *lots of things*
>
As there were no responses, I'm assuming everyone was relatively happy with
the proposed system.
The lack of action isn't doing ROS any favours though, the 0.3.1 release has
been promised on various news sites for 31st December, and we haven't even
branched for it yet!!
I'm prepared to help kick start this new release system off, if it'll help
to stop ROS going for another year without releasing.
I propose we pick the most stable recent release, branch it and prepare for
a Dec 31st release according to the new release system.
If everyone is in agreement, I'll start making the necessary arrangements.
Ged.
Hello,
there are a few ideas I would like to get feedback about:
1) iBrowser. Do we need it nowadays in the tree, when we have firefox
working?
2) In order to slightly decrease a load to our build servers, Alex
proposes to build Debug version without any optimizations at all,
thus increasing compilation speed.
For regression testing, release builds should be used, since release
builds are the most sensitive to possible errors.
3) RBuild improvement - the "components bundles" concept should be
(re)introduced: if I type "make <directory name>", I would like to
get all components inside that directory to be built.
4) Dependency map of ReactOS - maybe this should be implemented
inside of RBuild too. Dependency map is a tree, which shows how
modules depend from each other. Fortunately, we don't need to do this
by hand, since we can use rbuild's parsers/etc. Output format of the
map - open for suggestions.
If someone feels he is able to do point 3 or 4 - this is greatly
appreciated, and will help development of ReactOS.
With the best regards,
Aleksey Bragin.