Ros-dev

ros-dev@reactos.org

5788 discussions

by ea

Hi all, even if it is only an empty framework, I want to make you know yesterday I committed the source code of an optional environment subsystem for emulating VMS. Note it is far from complete and it has no ReactOS specific code (which will be *required* to run), but it may be used as a template. Recently ReactOS, which is a free and open source reimplementation of the core NT kernel+executive and driver model with multiple user mode OS personalities, was added the effective ability to load other optional subsystem, like POSIX (researched) or, say, VMS. If somebody on the list is interested in this project, please, feel free to contact me privately. Emanuele Aliberti ea(a)reactos.com

19 years, 8 months

Multiple problems with HEAD

by Ge van Geldorp

1st problem: when booting rev 14873 (DBG := 1, KDBG := 0) it crashes with: DriverBase for \SystemRoot\system32\drivers\fs_rec.sys: 9cf7c000 (io/file.c:898) Status :0 (io/file.c:898) Status :0 (io/file.c:898) Status :0 DriverBase for \SystemRoot\system32\drivers\beep.sys: 9cf8b000 (io/file.c:898) Status :0 Assertion NewRefCount >= 0 failed at ob/object.c:1150 KeBugCheckWithTf at ke/catch.c:217 A problem has been detected and ReactOS has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ntoskrnl.exe KMODE_EXCEPTION_NOT_HANDLED Technical information: *** STOP: 0x0000001E (0x80000003,0x800057a4,0x8005d08b,0x8071c9ec) *** ntoskrnl.exe - Address 0x800057a4 base at 0x80000000, DateStamp 0x0 Breakpoint Exception: 3(0) Processor: 0 CS:EIP 8:800057a4 <ntoskrnl.exe: 57a4> cr2 8ccfc000 cr3 27000 Proc: 8053fcf8 Pid: 4 <System> Thrd: 805407f0 Tid: 0 DS 10 ES 10 FS 30 GS 10 EAX: 00000036 EBX: 8004515d ECX: 00000000 EDX: 000003f8 EBP: 800e47a4 ESI: 800e4a84 ESP: 800e4730 EDI: 800e49f4 EFLAGS: 00200286 kESP 800e4730 kernel stack base 800e3000 Frames: <ntoskrnl.exe: 72a9f> <ntoskrnl.exe: 45f2a> <ntoskrnl.exe: 456e1> <vfatfs.sys: 2d00> <vfatfs.sys: d1de> <vfatfs.sys: d3ee> <ntoskrnl.exe: 45158> <ntoskrnl.exe: 40487> <ntoskrnl.exe: 414dd> <ntoskrnl.exe: 3602> <7D83F045> <ntoskrnl.exe: 3e6c0> <ntoskrnl.exe: 3602> <EC83FC45> <ntoskrnl.exe: 3de8e> <800A48CE> <800A21D4> <ntoskrnl.exe: 10004> <800A07AA> <ntoskrnl.exe: 104b> 2nd problem: the crash info is only written to the debug log and not shown as a BSOD. 3rd problem: the stack trace only shows addresses, not source file/line as it should for a DBG build 4th problem: booting with /DEBUGPORT=GDB results in a kernel stack fault very early in the boot process. Gé van Geldorp.

19 years, 8 months

Re: [ros-svn] [ion] 14884: Add hack for ROS's weird behavior. Will investigate but this lets you boot for now

by Alex Ionescu

ion(a)svn.reactos.com wrote: >Add hack for ROS's weird behavior. Will investigate but this lets you boot for now > > >Updated files: >trunk/reactos/ntoskrnl/io/irp.c > > > The problem is that a bunch of places in the code set the FileObject Event as the UserEvent. This is incredibly wrong, because both are used to signal completely different things and shouldn't be used like that. I've changed them to local stack KEVENTS, but this still fails, because you cannot dereference them. The check for !IRP_SYNCHRONOUS_API is meant to ensure against this (Syncronous IRPs have KEVENTS, Async ones have Executive Events, in short terms.) I've researched some more and this is because of a bigger problem. The routines doing the hack all assumed that the File Object is Synchronous and build a Sync FSD (with IRP_SYNCH_API set), and then set a KEVENT UserEvent. They should actually check if the File Object is Sync or Async, and in case of Async they should use the Local Stack KEVENT (which won't be dereferenced because of the check in IoCompleteRequest APC (2nd stage)), while in case of async they shouldn't use any event at all and wait on the file object instead of waiting on the local event. Also, in case of a sync operation, we must eventually include some sort of locking/unlocking of the file object for serialized access which is required. I will spend some time tomorrow working with these issues so the hack can be removed and proper kernel functionality to be restored, but I wanted to share the background information. Best regards, Alex Ionescu

19 years, 8 months

Re: [ros-dev] 0.2.7?

by reactos

>>> It's still not fully stable, card support is not great and it's only configurable through regedit at the moment. However it's all being worked on. Arty has done a fantastic job so far. Ged. <<< Actually lately no regedit is needed, as long as reactos registry supports your card only the dhcp software is needed, then everything is working... ...and soon the controlpanel app will be ready and everyone with a compatible card will be able to configure easy. The thing that we really need is support for driver installation. But on the other hand when we releas a new version we could transfer it to a usual textfile and put it on the welcome screen. /Jaix Bly ----Ursprungligt meddelande----- From: Gedi gedi(a)ntlworld.com Date: Sat, 30 Apr 2005 15:21:39 +0200 To: ReactOS Development List ros-dev(a)reactos.com Subject: Re: [ros-dev] 0.2.7? > Michael B. Trausch wrote: > > >Uh... Networking? > > > >I know at the very least *I* haven't seen ping working yet... > > > Networking has been up and running since before christmas now. > Along with the Mozilla control, you can now browse the web with ROS' > built in ibrowser, or use something like dillo. > There are many other programs running too, email, IRC too name but a few. > > >Networking support at the very least should be a staple for most overly > >popular cards before you think about trying to require a web page be > >displayed for something. Instead, put a static page on the CD that gets > >copied to the installed system. > > > > > It's still not fully stable, card support is not great and it's only > configurable through regedit at the moment. > However it's all being worked on. Arty has done a fantastic job so far. > > Ged. > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

19 years, 8 months

Re: [ros-dev] 0.2.7?

by reactos

Good idea, but ones a month is to frequent, people will get tired of testing new versions that they can't see any difference between. I think it has to be focust releases where something actually can be tested or seen, a feature not just read about in a change-log, everyone doesn't read the changelog. By the way, to be able to get people test the right thing when a new versin is released, we should have a welcome-screen packed with information about things changed since last release and so forth, this in a way that people can know how to test the new feature. This welcome screen could be a page in the WIKI so every developer easy can add what they want the testers to try out and how to do it. I know this opens for another problem, we need a browser to do that, can we add the mozilla-com plugin to the release? Or can we include another one? ----Ursprungligt meddelande----- From: WaxDragon waxdragon(a)gmail.com Date: Fri, 29 Apr 2005 19:13:29 +0200 To: ReactOS Development List ros-dev(a)reactos.com Subject: [ros-dev] 0.2.7? > I would like to see a 0.2.7 release soon. 0.3.0 is getting closer > every day, but it's not there yet IMHO. On the other hand, we have > had lots of big patches from Mr. Ionescu (and others), major changes, > go in and appear to be stable since we have released 0.2.6. I would > like to see us have another release in this lull, instead of having a > release right after committing a pile of patches *right before* the > release like we did with 0.2.6. > > I know it's been less than a month since 0.2.6, but my the time we > branch and do a couple RC's, it will have been over a month. > > I just have this feeling that we miss some regressions from release to > release, since alot of us just use HEAD on a regular basis? > > Just my $0.2US > WD > -- > "<tinus_> and also win32k should be fixed up a bit" > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev

19 years, 8 months

ROS System Updater

by Rick Langschultz

I have a simple request for when ReactOS wants to add updates to system software when Service Packs and Updates become available. I think that a ReactOS computer should utilize a small system service that indexes file version numbers, indexes them on importance, size, type, and other information. This can be done on a flatfile, XML, or a SQL Database connection. Then the server sends reponses back to the computer offering service packs, files, device drivers, etc. I think that kind of system will allow easy updates to ReactOs on users computers while not having to reinstall or reformat. Something like up2date, or mac os x¹s update program. The system can maybe support rollback of files. Just an idea.

19 years, 8 months

reactos.com available again

by Ge van Geldorp

Yesterday reactos.com crashed. Unfortunately, I was unable to go onsite to fix the problem yesterday. This morning, I rebooted the box and everything seems to be up and running again. It seems some mail sent to @reactos.com yesterday may have been dropped. Ge van Geldorp.

19 years, 8 months

Re: [ros-general] ROS installer scribbled over my ext2 partition :-(

by Michael B. Trausch

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Christof Petig wrote: | | This limitation really hurts if you do not plan to use ROS exclusively | on that computer (e.g. if you do not want to throw XP away completely or | you already use a first primary partition for linux). | ROS and XP can share the same partition. It just cannot be NTFS. You can always move partitions around. And yes, while the limitation "hurts," that's a workaround that you can use. Short of editing the source code, I'm not sure if there's much that can be done. I'll cc: this to the dev list and ask if the limitation still is there, but I personally don't see anything about it having changed. Consider that ROS is still in "early" stages of use/release. 0.3 hasn't even been released yet. I am sure that when the partition/fs code is better able to deal with multiple partition setups, it will all work as it would be anticipated it would. - Mike - -- Michael B. Trausch <fd0man(a)gmail.com> Website: http://fd0man.chadeux.net/ Jabber: mtrausch(a)jabber.com Phone: +1-(678)-522-7934 FAX (US Only): 1-866-806-4647 =================================================================== Do you have PGP or GPG? Key at pgp.mit.edu, Please Encrypt E-Mail! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCbiTLPXInbkqM7nwRAwl+AJ9U7aJ/HjCf72KuEkj4SjcM0wrpXgCfb6bs k9UbhobagYdusxcub9csK7U= =w/H8 -----END PGP SIGNATURE-----

19 years, 8 months

gcc-4.0 mingw crossbuild script

by Steven Edwards

Hi, If you need it here it is. Only explorer.exe does not build. The rest will compile if you shutup -Werror. For the C++ code that I have compared vs 3.4.1 its almost 2x faster. Thanks Steven __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

19 years, 8 months

not sure if it's been said already but...

by Jeff Smith

Vote results (Which kernel you prefer to see as base of osFree kernel?): What Percentage Votes L4 30.6 % 609 Linux 13.4 % 267 Mach 7.2 % 144 ReactOS 43.9 % 874 Other 4.4 % 87 This poll is taken from http://www.osfree.org/index.php

19 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev