Hello!
Thank you for your reply, I wasn't actually aware of those builds. I tried
build #57337 (while I am writing this, it seems that 57338 is being released),
but it went from bad to worse.
While the transfer seemed to work longer than before (could be wrong about that
though, not enough statistical data), it still ended with NTOSKRNL.EXE crashing.
*** STOP: 0x0000001E (0xC000046, 0x808847C7, 0xF83495A8, 0x00000000)
*** NTOSKRNL.EXE - Address 808847C7 base at 80800000
On top of that, trying to start Filezilla 3.5.3 now results in another BSOD of
NTOSKRNL.EXE (also 0x0000001E), which did not happen in 0.3.14.
Additionally, that build boots into a BSOD on VMware Player 4.0.1, but boots up
fine on VirtualBox 4.2, but that could easily be a fault of my configuration, as
I'm not currently using the settings from the 0.3.14 VM images, but fresh ones,
as this is a different host machine now.
It kind of looks like I'm not going to get my preferred software to work in a
stable fashion on ReactOS, at least when virtualized..
I guess there is nothing I can do but to try new ReactOS builds every now and
then?
Thanks anyway!
Aleksey Bragin wrote:
> Hello!
>
> Could you try latest build from here http://www.reactos.org/getbuilds/ ?
> It contains a number of networking improvements, however as for general
> stability with regards to kernel crashes, the kernel memory manager is
> still work in progress, so it may crash as easy as 0.3.14. But it would
> be great to see whether the situation imprpved.
>
> If there is anything I can help with - let me know.
>
> Best regards,
> Aleksey Bragin.
>
> On 17.09.2012 11:19, Michael Lackner wrote:
>> Greetings!
>>
>> I would like to ask a question, maybe there is already an easy fix for this
>> that I just cannot find using Google.
>>
>> So, I have set up ReactOS in both VirtualBox and VMware Player (4.0 & 5.0).
>>
>> What I am trying to do is to download a large ~700MB file using ftp.exe or
>> Filezilla 2. Alternatively, I also tried to copy it from an ISO CD image.
>>
>> This never succeeds however. Either the machine just freezes or BSODs,
>> according to bt it's something like "can't access memory at <some address>",
>> with the error caused by the application doing the transfer.
>>
>> Mostly it just freezes though, especially when copying from CD ISO.
>>
>> So what I did then was to boot Knoppix and copy the file to ReactOS's
>> partition offline. It's actually a video stream file. When I then tried to
>> run my actual test (x264 video transcode), it works for a few minutes, then
>> NTOSKRNL.EXE BSODs again, I didn't do a backtrace for that crash yet.
>>
>> Am I doing something specifically wrong to cause so many Kernel crashes, or
>> is this still "normal" in 0.3.14? I mean: Is it normal to have the Kernel
>> crash like that when just downloading or copying some files?!
>>
>> Thanks for any help you might be able to provide!
--
Michael Lackner
Lehrstuhl für Informationstechnologie (CiT)
Montanuniversität Leoben
Tel.: +43 (0)3842/402-1505 | Mail: michael.lackner(a)unileoben.ac.at
Fax.: +43 (0)3842/402-1502 | Web: http://institute.unileoben.ac.at/infotech
Greetings!
I would like to ask a question, maybe there is already an easy fix for this
that I just cannot find using Google.
So, I have set up ReactOS in both VirtualBox and VMware Player (4.0 & 5.0).
What I am trying to do is to download a large ~700MB file using ftp.exe or
Filezilla 2. Alternatively, I also tried to copy it from an ISO CD image.
This never succeeds however. Either the machine just freezes or BSODs,
according to bt it's something like "can't access memory at <some address>",
with the error caused by the application doing the transfer.
Mostly it just freezes though, especially when copying from CD ISO.
So what I did then was to boot Knoppix and copy the file to ReactOS's
partition offline. It's actually a video stream file. When I then tried to
run my actual test (x264 video transcode), it works for a few minutes, then
NTOSKRNL.EXE BSODs again, I didn't do a backtrace for that crash yet.
Am I doing something specifically wrong to cause so many Kernel crashes, or
is this still "normal" in 0.3.14? I mean: Is it normal to have the Kernel
crash like that when just downloading or copying some files?!
Thanks for any help you might be able to provide!
--
Michael Lackner
Lehrstuhl für Informationstechnologie (CiT)
Montanuniversität Leoben
Tel.: +43 (0)3842/402-1505 | Mail: michael.lackner(a)unileoben.ac.at
Fax.: +43 (0)3842/402-1502 | Web: http://institute.unileoben.ac.at/infotech
Normally this list is used to announce new releases of ReactOS operating
system, however this time is an exception. There is a significant, rare
event which I would like to get your attention to.
ReactOS Fundraiser 2012.
The ReactOS Project has engaged in several fundraising efforts in the
past, and thanks to their success and non-monetary donations, an
industry-grade infrastructure
<http://www.reactos.org/en/Infrastructure.html> was developed and
deployed, and is being continuously improved.
Donations have also helped developers travel to several conferences and
events to promote and present ReactOS. These presentations were crucial
in drawing attention to the project and often helped spur further donations.
This year we want to do something different, something even grander.
ReactOS is quite close to transitioning to beta testing and we are
constantly improving the development process itself. However for many
core developers ReactOS remains a hobby in which they participate in
their spare time as all have other real life obligations to meet. All of
the developers are extremely skilled and every contribution they make
helps significantly improve ReactOS' quality.
For the first time ever, the ReactOS Foundation seeks to go beyond the
usual small fundraising campaigns aimed at paying infrastructure
expenses. We wish to raise money
<http://www.reactos.org/en/foundation_donate.html> *to formally hire as
many core developers as possible*, to work on the project they believe
in, the project they've been working on, to transform a hobby into a job
so they can dedicate all of their time to the ReactOS project.
In light of the significant advances the project enjoyed thanks to work
done as part of Google's Summer of Code 2011, it became even more
obvious that the fastest way to accelerate the development of ReactOS is
by directly funding developers to contribute to ReactOS. As such, the
project is reaching out to our many fans and believers to help make this
happen.
Together, we can make ReactOS into a true competitor and alternative for
computer users worldwide.
Thanks,
Aleksey Bragin
ReactOS Project Coordinator
Links:
Official news text: http://www.reactos.org/en/news_page_75.html (other
languages may be available)
ReactOS Fundraising Campaign 2012 Progress bar (updated daily):
http://www.reactos.org on top of the page.
Donation page: http://www.reactos.org/en/foundation_donate.html (other
languages may have country-specific ways of donation)
_______________________________________________
Ros-announce mailing list
Ros-announce(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-announce
The ReactOS team is proud to announce the release of ReactOS 0.3.14.
This version includes a significant amount of changes including both
user visible and architectural improvements. Also included in this
release is the valuable work accomplished as part of the Google Summer
of Code 2011 event, of which ReactOS was a mentoring project.
One of the more significant sets of improvements was to ReactOS’
networking stack. As part of the GSoC, ReactOS gained a new TCP/IP
driver built around the LwIP project. The LwIP library is a popular and
stable implementation of TCP/IP originally intended for embedded use.
The new driver has significantly increased both stability and
performance, allowing the use of high bandwidth applications such as
torrents. Furthermore, ReactOS has improved compatibility with NT5.1
drivers with the export of scatter/gather DMA functionality. Last but
not least, ReactOS now includes wireless network support and is able to
connect to both open and WEP encrypted networks.
One of the more obvious user visible changes includes the implementation
of theme support. Users can now change the look and feel of ReactOS’
user interface by installing XP based themes and changing the appearance
of the desktop from the default classic look to something more exciting.
Architecturally, the addition of a kernel mode testing framework has
helped to identify a variety of bugs in kernel mode components. This is
an important change with regards to core stability and is proving
invaluable in ensuring the project does not suffer unexpected
regressions in the kernel.
Support for building ReactOS using the Microsoft toolset has also played
a large part in the release. This is now at a stage where ReactOS can be
entirely built using an MSVC based environment and can produce a working
boot and livecd. Along with GCC, ReactOS can now be built using two
different toolsets and on a variety of platforms including Windows,
Linux and Mac OS X.
During the preparation of this release 789 bugs were fixed, including
118 regressions with the oldest regression being issue #1009 (can't open
context menu with Shift-F10). The oldest bug fixed was #209 (PrintScreen
doesn't work) from over eight years ago. 811 new bugs were opened since
the release of 0.3.13.
A list of some of the more significant changes includes:
* ACPI
Advanced Configuration and Power Interface support is now enabled
automatically when the ACPI Hardware Abstraction Layer is used,
providing support for power buttons and full system power off.
* LwIP
A new TCP/IP driver using the LwIP driver has been integrated into
ReactOS, significantly improving network performance and stability and
also presenting an upgrade path to IPv6.
* MSVC Compatibility
ReactOS can now be built using Microsoft's compiler to create a working
boot or livecd.
* Scatter/Gather Support
Scatter/Gather DMA operations are now supported, significantly improving
compatibility with network drivers written for NT5.1 and later.
* Shell Improvements
The shell32 library rewrite in C++ has been merged in and brings with it
various architectural improvements that will help serve as a foundation
for future work on the new explorer shell.
* Special Pool
A special pool designed to guard against misuses of kernel pool memory
has been implemented.
* Theme Support
ReactOS now has the infrastructure needed to theme the user interface
and shell, allowing users to install and use something besides the
classic Windows theme.
* WiFi Support
ReactOS now supports wireless network drivers and is able to join open
and WEP encrypted wireless networks.
The detailed 0.3.14 changelog is available here:
http://www.reactos.org/wiki/index.php/ChangeLog-0.3.14
Main news link: http://www.reactos.org/en/news_page_70.html
Download link: http://www.reactos.org/en/download.html
I would like to thank all the past and present members of the ReactOS
team for their hard work and of course all those in the community that
support us.
We will never forget involvement and contribution of those who left our
world too early.
http://www.reactos.org/pipermail/ros-dev/2011-June/014419.html
--
Aleksey Bragin
ReactOS Foundation President
http://www.reactos.org
_______________________________________________
Ros-announce mailing list
Ros-announce(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-announce
Hi,
sorry about the flood on the list due to auto-responder put on a member
mailbox. The member has been informed about the issue and won't be able
to send mails before it's fixed.
With my best regards,
Pierre Schweitzer