I'm working on a list of things to test ReactOS with, and I already
have a good list of networking apps to try. I am interested in what
others use for personal "regression tests", particularly non-network
apps. I would like to make a comprehensive list of manual regression
tests to use in combination with programmatic ones.
Any info on our programmatic regression testing would be useful also.
Some things I scribbled down:
Changing the wallpaper
Ros on ros compilation
rosperf
I'm not including "Installing from the bootcd/running the livecd"
since alot of people do that anyway.
Thanks!
WD
--
"<arty> the tree was touched a lot recently"
I run though the first stage installer (formatting the disk) and after
it asks where I want to install freeldr (I choose MBR) ReactOS then
bugchecks:
(cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in
remaining path: "\Hardware
Profiles\Current\System\CurrentControlSet\Services\vmx_svga\Device0"!)
(cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in
remaining path: "\Hardware
Profiles\Current\System\CurrentControlSet\Services\vmx_svga"!)
(cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in
remaining path: "\Hardware
Profiles\Current\System\CurrentControlSet\Services"!)
(cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in
remaining path: "\Hardware
Profiles\Current\System\CurrentControlSet"!)
(cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in
remaining path: "\Hardware Profiles\Current\System"!)
(cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in
remaining path: "\Hardware Profiles\Current"!)
(cm/ntfunc.c:383) NtCreateKey() doesn't create trees! (found '\' in
remaining path: "\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00\0000"!)
(bootsup.c:1760) System path: '\Device\Harddisk0\Partition1'
(bootsup.c:1966) No or unknown boot loader found
(bootsup.c:1974) Copy: \Device\CdRom0\loader\freeldr.sys ==>
\Device\Harddisk0\Partition1\freeldr.sys
(bootsup.c:1989) Copy: \Device\CdRom0\loader\freeldr.sys ==>
\Device\Harddisk0\Partition1\freeldr.ini
(inicache.c:1037) BufferSize: 694
(bootsup.c:2003) Save bootsector: \Device\Harddisk0\Partition1 ==>
\Device\Harddisk0\Partition1\bootsect.old
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0x138 could not be read: Page not present.
kdb:> bt
Eip:
<vfatfs.sys:b592 (rw.c:572 (VfatRead))>
Frames:
<vfatfs.sys:d1f4 (misc.c:110 (VfatDispatchRequest))>
<vfatfs.sys:d3ee (misc.c:168 (VfatBuildRequest))>
<ntoskrnl.exe:4c898>
<ntoskrnl.exe:4c810>
<ntoskrnl.exe:487bf>
<ntoskrnl.exe:36d2>
<smss.exe:19c3>
<smss.exe:426f>
<smss.exe:16f18>
<smss.exe:17623>
<deadbeef>
kdb:>
Thanks to Alex for showing me how to enable serial output for the bootcd!
WD
--
"<arty> the tree was touched a lot recently"
Hi
Few days ago, I did my check of the state of ReactOS. I was surprised by
the progress made and decided to do some hacking with it. So I did a SVN
checkout of the source tree and wanted to build it, BUT! I realized that
cross-compiling ReactOS on linux is not as easy as I thought. So my
question is: what is needed to get cross-compilation enviroment capable
of building ReactOS on linux? I don't have any Windows box here and I
must admit I don't like the idea of having one either.
If there's anybody hacking ReactOS on Linux, I would apreciate his help.
I would personaly love to see some information about cross-compiling
on the website - it's really concise on this topic :(
Thanks for your help
Vit Herman
Hi,
if I browse the repository on svn.reactos.com, I see for
trunk/reactos/subsys/system/expand an old version and not all files. I'm
missing En.rc, expand.rc and resource.h. I get this files with a
checkout or an update. I've merged the trunk to a clean source tree of
the cache_mangeger_rewrite branch on my disk and committed the changes.
Exactly this three files wasn't committed to the branch, but they are in
my tree.
- Hartmut
hbirr(a)svn.reactos.com wrote:
>
>
> Deleted files:
> branches/cache_manager_rewrite/reactos/lib/msgina/
Just out of curiosity, what's that deleting+adding for?
Best Regards,
Thomas
Hi!
A patch, committed within the last two weeks, broke the named pipe
filesystem driver. The result is the message:
service/sctrl.c:305 Pipe read failed
The error code is ERROR_BROKEN_PIPE.
This bug keeps user-mode services from starting up. I assume the bug is
caused by one on the patches to ntoskrnls IO code because npfs has not
been touched for a few more weeks.
Please fix this bug as soon as possible as it keeps me from working on
PnP and RPC!
Regards,
Eric
David Johnson wrote:
> I asked too. No reply also.
> What gives?
>
> On 5/17/05, Fero Vlkolinsky <f.vlkolinsky(a)alcatel.sk> wrote:
> > Hi,
> >
> > I've read that Alex Ionescu wanted to start JANITOR project for reactOS.
I'd like to join but he didn't reply my > mail. So is this
> > project alive or is it abandoned completely?
> >
> > Fero
It's been put on hold for a while until Alex finishes school, (and winsock2,
and object manager and .... ) heh.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hi,
I've read that Alex Ionescu wanted to start JANITOR project for reactOS. I'd like to join but he didn't reply my mail. So is this
project alive or is it abandoned completely?
Fero
