Hi all,
Today I have had ms notepad running in ros and I have been able to save what I typed. The menus at the top do not work, but when I was exiting the programme, it asked if I wanted to save the changes that had been made, so with a few clicks and a bit more typing, it save the file in the windows directory.
It is very slow, but I am excited about it, just like a little child. Well done team, keep it up.
Regards
jh
Hello,
How are video card drivers installed in ros. Do we just drop the dll's in \system32 and any sys files in \drivers.
I have down loaded the nt4 drivers for a S3virge DX card that I have, what do I do with them?
This is the list:
Blocking.cfg - S3switch.dll - S3virge.dll - S3mini.sys - S3virge.inf
I also down loaded a little prog that finds the S3 chip used. This prog works in part in ros, it reports that you need admin privileges without displaying any data.
Regards
jh
Hi all
The news is that Aleksey Bragin has taken on the role of ReactOS
Translation Coordinator! This means that we'll be seeing some
internationalization that's everyone's being wanting. But don't
everyone
go asking what they can translate just yet - Aleksey needs to get
familiar with ezPublish (CMS used by reactos.com) and get organized
for
the role first - but watch this space.
Cheers
Jason
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
I was wonderng if/what improvements we are likely to create, like will we try to create our own Networking protocol just for ReactOS, or our own Binary format, new API's, or other idea I'm not getting right now, will we add to reactOS after we have base Win32 compatibility?
*~*
I also agree with this,
We should take Firebird (since its only the browser (not mail, IRC,
composer, etc.) and its faster than IE) and add in the ActiveX control
plug in (which you can get at:
http://www.iol.ie/~locka/mozilla/plugin.htm) and also make a COM wrapper
for the Gecko rendering engine, between those two we should have a full
replacement to IE for the OS. I think that there was some Netscape
employees working on making a COM wrapper for Mozilla, but I can't
remember the website, and development seemed to be pretty inactive, but
its better than starting from scratch.
*~*
No, no, I don't think you get what I'm suggesting. Both Mozilla and
Firebird have the same engine under the hood. The speed difference is
mostly because seamonkey loads more than just the browser. The ActiveX
control is simply a way to access the browser, all of those other
features are actually add-ons that don't need to be installed.
As for the dummy-browser, it's actually quite simple to do. I would if
I better understood ActiveX, but the "official" website for the control
has a variety of demos to work from. The dummy-browser would be a
little bit more useful than just plain Firebird, since we could
integrate bookmarking features with ros explorer much in the same way
microsoft does with IE.
If modified properly, the control could replace IE completely. It
wouldn't be needed for anything anymore.
What would happen if you installed IE on ReactOS?
Does the licence allow this?
Whilst I'm thinking about it... What would happen if a user went to the
windows update site?
-----Original Message-----
From: Nate DeSimone [mailto:desimn@rpi.edu]
Sent: 05 February 2004 07:12
To: ros-general(a)reactos.com
Subject: Re: [ros-general] Browsers
I also agree with this,
We should take Firebird (since its only the browser (not mail, IRC,
composer, etc.) and its faster than IE) and add in the ActiveX control
plug in (which you can get at:
http://www.iol.ie/~locka/mozilla/plugin.htm) and also make a COM wrapper
for the Gecko rendering engine, between those two we should have a full
replacement to IE for the OS. I think that there was some Netscape
employees working on making a COM wrapper for Mozilla, but I can't
remember the website, and development seemed to be pretty inactive, but
its better than starting from scratch.
David Dunn wrote:
> I went through the forum and heard a lot of things about which browser
> (mostly mozilla) should be used as the default for ROS.
>
> Just my idea, but I think that we should use a modified version of the
> Mozilla ActiveX control instead with a dummy browser placed on top.
> There are 3 reasons why I think that this (even though it may be more
> difficult) is probably the best choice in the long run.
>
> -Programs that require IE will instead be redirected to use Mozilla's
> rendering engine instead
> -The dummy browser could store it's bookmarks in a similar manner to
> the way IE does adding to the startbutton/bookmarks compatibility
> -Still promotes OSS
>
> Firebird and Mozilla are great and all, but if there isn't
> compatability with the myriads of programs that want to call IE for
> some reason or another ROS will be slower to be adopted
> _______________________________________________
> ros-general mailing list
> ros-general(a)reactos.com
> http://reactos.com/mailman/listinfo/ros-general
>
>
_______________________________________________
ros-general mailing list
ros-general(a)reactos.com
http://reactos.com/mailman/listinfo/ros-general
Sorry if you have had mail bounced to me and all of that. I am still on
post-wineconf vacation until monday and my mailbox is a little
overflowing.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
IIRC windows sockets were based on BSD sockets.
>
>
> On Thu, 5 Feb 2004, Vizzini wrote:
>
> > On Thu, 2004-02-05 at 17:15, Ian McLean wrote:
> > > I thought IE was based on NCSA Mosaic ? Or is Mozilla based on this also ?
>
> Actually, I think IE is based on the Spyglass browser, which is probably
> only a distant cousin at this point to Mosaic.
>
> BTW: Has anybody considered that the BSD TCP stack may be easier to port
> to ReactOS? I work with another open-source operating system called eCos,
> and it uses the BSD networking stack but its design is not like a
> traditional UNIX kernel.
>
> Perhaps this might be an easier path. I think the BSD stacks were designed
> to be ported more easily than the Linux one. I guess the things we would
> need are:
>
> * TDI "glue"
> * NDIS "glue"
> * A wrapper for a memory pool to allow the mbuf allocator to run.
> (we could just tie the mbuf allocator to the non-paged pool?)
>
> Another cool thing would be to port OpenPF from the OpenBSD project to
> ReactOS. Its an excellent packet filter and designed to work with the
> OpenBSD stack as well.
>
> But I really do think that ReactOS needs to get a working TCP stack before
> people worry too much about what browser to use.
>
> L8r,
> Mark G.
>
> _______________________________________________
> ros-general mailing list
> ros-general(a)reactos.com
> http://reactos.com/mailman/listinfo/ros-general
I went through the forum and heard a lot of things about which browser
(mostly mozilla) should be used as the default for ROS.
Just my idea, but I think that we should use a modified version of the
Mozilla ActiveX control instead with a dummy browser placed on top.
There are 3 reasons why I think that this (even though it may be more
difficult) is probably the best choice in the long run.
-Programs that require IE will instead be redirected to use Mozilla's
rendering engine instead
-The dummy browser could store it's bookmarks in a similar manner to the
way IE does adding to the startbutton/bookmarks compatibility
-Still promotes OSS
Firebird and Mozilla are great and all, but if there isn't compatability
with the myriads of programs that want to call IE for some reason or
another ROS will be slower to be adopted
Hello,
I got an offer of a PHP web programmer via private email to help
developing the ReactOS web site:
> I am actually more of a PHP web-programmer. If you need any web
> programming for ROS, I can certainly help you in that area!
I know, the current reactos home works quite well - just in
case there are some ideas for improvement.
Regards,
Martin
