sedwards(a)svn.reactos.com wrote:
>__USE_W32API
>
>
>Added files:
>trunk/reactos/lib/msgina/makefile
>
>Updated files:
>trunk/reactos/lib/msgina/msgina.c
>trunk/reactos/lib/msgina/stubs.c
>
>Deleted files:
>trunk/reactos/lib/msgina/Makefile
>
>
This library should probably be moved to reactos/subsys because it is
loaded exclusively by winlogon.
It seems that Longhorn drops the GINA. Is it confirmed? Is it due to a
broken (=insecure) design that can not be fixed? If so, should we spend
time implementing GINA?
Emanuele
mingw32-linux is not setting ARCH=i386,
this breaks make bootcd for it.
(although there is an easy workaround)
Kind regards,
Usurp (aka Sylvain Petreolle)
humans are like computers,
yesterday the BIOS was all
- today its just a word
--- Richard Campbell <eek2121(a)comcast.net> wrote:
> *faints*
*grabs the smellinbg salts for Richard and waves hi to Phillip.
Phillip, welcome back! I was looking at some of your code a while back (RAM Disk Driver) and was
wondering if we should add support to it to be a general purpose RAM driver while keeping suppport
for loading from bochs images as it does now.
Thanks
Steven
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
Hi,
it seems we have now a file en.rc and En.rc. This will not work on windows.
- Hartmut
weiden(a)svn.reactos.com wrote:
>corrected file name so it matches the include in slayer.rc
>
>
>Added files:
>trunk/reactos/lib/shellext/slayer/En.rc
>
>_______________________________________________
>Ros-svn mailing list
>Ros-svn(a)reactos.com
>http://reactos.com:8080/mailman/listinfo/ros-svn
>
>
>
>
On Mar 30, 2005 12:49 PM, James Dodd <admin(a)doddnetwork.co.uk> wrote:
> I think people are right with the about page.
The whitepaper and FAQ will answer more than enough. The entire first
set of links at the top links to various 'about' topics.
> I've also moved the language bar to the top of the screen...
That I like.
> Even these companies are moving away from this and creating a more user
> friendly approach to their sites which intern represents their OS.
Yes, those *companies*. Apache.org seems to be doing fine with their
minimalist design.
> The new site at the moment does seem more appropriate to developers as
> apposed to attracting new audiences.
What new audiences? Developers are really what is most important to
this project right now. I'm going to stop short of chanting
"developers! developers! developers!" ;)
Cheers
Jason
Hi all
Jh sent me a better look: http://reactos.com/newsite/reactos_index.html
I think it looks better!
I've also reworded our slogan at the top to read what Steven suggested.
Magnus: I'm sorry but your critism is not constructive! Which links do
you want on the frontpage that aren't already there? You cannot link
to everything on the frontpage either!
Cheers
Jason
And needs an SVN account ;)
I'm glad to see everyone kept the project going without me, I am
impressed with the progress!
Hopefully now I can get back to contributing.
--- Robert K�pferl <rob(a)koepferl.de> wrote:
> I can think of an infrasturcture where one could update a list and
> gather packageinformation from all over the internet and install random
> apps hosted by theirs creators or sf.net
Yeah thats kinda my thinking. We maintain a database of all of the free Win32 software on
SourceForge and try to get them all to use MSI or NSIS to package them.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Sports - Sign up for Fantasy Baseball.
http://baseball.fantasysports.yahoo.com/
Hi,
--- Maarten Bosma <maarten.paul(a)bosma.de> wrote:
> As you might remember firk85 and me have started coding a package
> manager for ReactOS. More information and a download linkcan be found on
> the wiki on http://wiki.reactos.com/PackageManager .
>
> Since it is now so far that it is at least a bit useful, I'd like to ask
> what you think of adding it to the svn-tree ?
MSI already does everything you want to do. Add support for loading MSI packages by developing
your application on Windows and then it should work in ReactOS as we share msi.dll and msiexec
with wine. Vendors can already use Wix to package thier applications. For bonus points make it tie
in nicely with NSIS.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com
Hi,
--- Maarten Bosma <maarten.paul(a)bosma.de> wrote:
> I missed to introduce a concept of the package manager here. Packages
> are not a Archive file with an instruction for installing like apt
> packages. The more an instruction to download the program, that might be
> running the setup with a special parameter or downloading an arrive
> file with the binaries. That is a little bit of BSD ports or Gentoo Emerge.
>
> This is why I think MSI files aren't the right think to replace the
> basic based scripts, that are used at the moment. It simply not what
> they have been made for. But if the vendor of the application provides a
> msi file of cause it can be used; with a "msi"-script-command.
I think the idea of a central repository containting information on Free(Open) Win32 is a good
idea.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Personals - Better first dates. More second dates.
http://personals.yahoo.com