I took a picture of the screen:
http://mike.warpedbelief.com/images/ros-crash.jpg
It crashed immediately after I hit a key during the "Press any key to
boot CD..." prompt.
I can't really figure out if any hardware could cause problems. This
is the configuration:
Pentium 120 MHz
64 MB of RAM
2 GB hard disk (I think it's Western Digital)
2 MB ET4000 video
36x CD-ROM drive
One floppy drive
The hard disk partition scheme is this:
One primary partition. FAT16. Windows NT 4 Server install on it. Takes
up the whole 2 GB.
Hello,
While you guys are working on the website changes I would like to add
that the Wine application database is GPL, in CVS and is done in PHP.
http://cvs.winehq.com/cvsweb/appdb/
Thanks
Steven
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
chorns(a)cvs.reactos.com wrote:
>CVSROOT: /CVS/ReactOS
>Module name: reactos
>Repository: reactos/tools/
>Changes by: chorns(a)mok.osexperts.com 04/10/24 10:51:33
>
>Modified files:
> ./: ChangeLog
> reactos/ntoskrnl/: Makefile
> reactos/regtests/regtests/: regtests.c regtests.def
> reactos/regtests/shared/: regtests.h
> reactos/tools/: regtests.c
>Added files:
> reactos/ntoskrnl/tests/: .cvsignore Makefile setup.c stubs.tst
> reactos/ntoskrnl/tests/tests/: .cvsignore
>
>Log message:
> 2004-10-24 Casper S. Hornstrup <chorns(a)users.sourceforge.net>
>
> * ntoskrnl/Makefile (TARGET_REGTESTS): Define to yes.
> * regtests/regtests/regtests.c (_ExitProcess): Declare.
> * regtests/regtests/regtests.def (_ExitProcess@4): Ditto.
> * regtests/shared/regtests.h (_ExitProcess): Ditto.
> * tools/regtests.c: Exit process using _ExitProcess();
> Properly support fastcall symbols.
> * ntoskrnl/tests: New directory.
> * ntoskrnl/tests/tests: Ditto.
> * ntoskrnl/tests/.cvsignore: New file.
> * ntoskrnl/tests/Makefile: Ditto.
> * ntoskrnl/tests/setup.c: Ditto.
> * ntoskrnl/tests/stubs.tst: Ditto.
> * ntoskrnl/tests/tests/.cvsignore: Ditto.
>
>_______________________________________________
>Ros-cvs mailing list
>Ros-cvs(a)reactos.com
>http://reactos.com/mailman/listinfo/ros-cvs
>
>
>
Hi,
I can't say I'm terribly overjoyed with having the /tests directory in
/ntoskrnl. Would it be possible instead to have a /tests root (on the
new SVN server) where all the tests would go? like /tests/ntoskrnl,
/tests/kmregtests etc...
I think it would make it a bit clearer...it just bugs me to have /tests
in ntoskrnl.
Best regards,
Alex Ionescu
Hi Everyone,
We got very good feedback from LinuxWorld.de and I will be returning
next year. 90% of the people visting our booth left thinking very
highly of our work. All in all the results were much better than the
last expo. I very surprised that so many people came up to us and said
"we have heard of ReactOS or we have tried it out".
Here is my rough list of notes on where I think we need to go from here
after discussion with the developers and users.
1. We need a roadmap for the future.
THIS DOES NOT MEAN THAT THERE ARE FIRM DATES ATTACHED!!!!
But we do need to plan our 0.3, 0.4, 0.5 and 1.0 releases. During a
dinner discussion with some of the dev team I asked the question "What
do we need before we can have a ReactOS Workstation 1.0" and it does
not seem to be to far out of grasp. Dont get me wrong there are LOTS of
little things that must be done but the major things we need to have a
real replacement workstation are below. If you think about what Windows
NT 4 had even with Service Pack 6 we are not that far off. Note I am
not talking about a server replacement here. Just a usable client OS.
- Networking (0.3)
- Samba port needs to implemented (0.4)
- We need to implement Windows style printing support (0.4 or 0.5)
- Most applications need to install..Office 2000/XP, Quicken, etc
(0.4)
- We have to develop our own Hardware Compatibity List (0.5)
- NTFS (????)
- It must be stable (1.0)
2. We have to have regression testing in place.
Lack of stablity and regressions are killing us. We have to have the
Wine tests in ReactOS. We also need a suite of kernel mode tests.
Casper's system seems like its going to work well for the kernel mode
side but most of us seem to be worried about the lack of being able to
use Winehq regression tests for user mode.
3. We need to improve our documentation and website.
After much discussion and two too many beers on my part our discussions
turned to documentation and the website. We all agreed that the current
system is not working and we need to develop a method of storing most
of the website in CVS so that people can send us a patch. Same thing
with the documentation....none of us wants to use ezPublish to develop
documentation when we can all use docbook right out of cvs and submit
diffs. Most of us even like the Wiki system as its not hassle and can
maintain a history as well.
4. We need to develop relationships with vendors.
This ties in to getting ReactOS stable and usable. Once we have 0.3 out
the door I expect things will change for us in ways no one can see. I
am going to focus more on this in the coming months, first in the way
of hardware donations.
5. Moving to subversion.
There still seems to be some problems with this and while we all seem
to look forward to it, CVS is doing its job for the moment. GvG has
offered to setup a CVS mirror to help with some of the bandwith
problems of mok.
In closing it was very cool to get to meet all of the developers that
were able to make it, I feel like we are going in the right direction
and I look forward to your feedback.
Thanks
Steven
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
--- "Aaron W. LaFramboise" <aaron77thyme(a)aaronwl.com> wrote:
> I know nothing about ReactOS internals, but theres a chance someone
> might be able to help if you could check all objects with the bad
> binutils against all objects with the good binutils, and somewhere
> post
> the objects that differed. I'd take a look if you could post this
> much
> information.
According to Filip Navara there was a bug in binutils that is fixed in
current CVS. I dont really have the time to check all the objects.
Thanks
Steven
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
>
> Today's Topics:
>
> 1. Re: What I have learned on my time off
> (LinuxWorld) (Jason Filby)
----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 6 Nov 2004 10:07:57 +0200
> From: Jason Filby <jason.filby(a)gmail.com>
> Subject: Re: [ros-dev] What I have learned on my
> time off (LinuxWorld)
> To: ReactOS Development List <ros-dev(a)reactos.com>
> Message-ID:
> <e7a1591e04110600072d5b1306(a)mail.gmail.com>
> Content-Type: text/plain; charset=US-ASCII
>
> Steven
>
> >1. We need a roadmap for the future.
>
> Agreed.
>
> >2. We have to have regression testing in place.
>
> Yes - Casper's doing a lot of great work on this;
> with regards to
> WineHQ tests, well, we'll have to see if we can't
> find a way to
> integrate them. Right now let's just focus on
> getting the Continuous
> Integration System going.
>
> >3. We need to improve our documentation and
> website.
>
> I've already thought about this a lot; definitely a
> wiki for the
> Library - with access only to devs to make changes;
> a wiki doesn't
> have to allow just anyone to make a change and I
> don't think that's a
> good idea. I've already introduced MedaWiki at work
> (it powers
> Wikipedia.com) and would really want to get this on
> reactos.com for
> our Library -- probably a few other pages as well.
>
> I don't want to see a wiki only site. A wiki doesn't
> enforce
> structure, which is nice for something like a blog
> or list of
> compatible hardware/software, or forum. We'll use
> the best software
> suited to the job -- this means that a lot of effort
> will have to go
> into integration: search but more importantly login.
>
> It's just that to get there is a ton of work! The
> website needs its
> own roadmap, for sure.
>
Mr. Filby, i have ofered twice to colaborate with my
limited capabilities in the proyect, i have offered to
actualize the website from time to time, and the made
of a FAQ (this will be more difficult, as i will have
to test and ask many howtos on reactos) if you find
this could be usefull.
I am still waiting for an answer.
Best regards,
Lucio Diaz-Flores.
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
Hello,
The most recent binutils package might have a bug in it but I am not
quite sure. When running ReactOS after building with the newer binutils
you will see errors like in this thread
http://reactos.com:8080/archives/public/ros-dev/2004-November/000492.html
Sorry I dont have time to dig in to it further.
Thanks
Steven
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
The current Rosapps module in CVS fails to build
I am using the recommended compiler indicated in Reactos.com
Regards
Gerard
------------------------------------------------------
mingw32-make[1]: Leaving directory `D:/Gerard/Reactos/Ros/rosapps/sysutils'
mingw32-make -C sysutils\ctm
mingw32-make[1]: Entering directory
`D:/Gerard/Reactos/Ros/rosapps/sysutils/ctm'
windres --include-dir ../../../reactos/include --include-dir
../../../reactos/w32api/include ctm.rc -o ctm.coff
gcc -I. -I../../../reactos/include -I../../../reactos/w32api/include
-pipe -march=i486 -D_M_IX86 -g -c ctm.c -o ctm.o
ctm.c:41:20: epsapi.h: No such file or directory
ctm.c: In function `PerfDataRefresh':
ctm.c:430: warning: assignment makes pointer from integer without a cast
ctm.c:433: warning: assignment makes pointer from integer without a cast
ctm.c:444: warning: assignment makes pointer from integer without a cast
ctm.c:532: warning: assignment makes pointer from integer without a cast
mingw32-make[1]: *** [ctm.o] Error 1
mingw32-make[1]: Leaving directory
`D:/Gerard/Reactos/Ros/rosapps/sysutils/ctm'
mingw32-make: *** [sysutils\ctm] Error 2
D:\Gerard\Reactos\Ros\rosapps>
-------------------------------------------------------