ReactOS Forum

It's that time of year again and we are looking to spin out version 0.4.2. I think at this point we can all agree that attempts to find a new versioning scheme are dead. Anyway, before we initiate the process of actually spinning out a release the team would like to check ReactOS' pulse so to speak. As such we request that community members grab the release candidate and test applications listed https://www.reactos.org/wiki/Tests_for_0.4.2 by noting the results and revision tested. This will help us determine whether trunk is in decent enough shape to attempt a release or if there is a major problem that the devs need to look into. Have fun.

*ZWabbit puts down transcript*

ZWabbit: There, that sound release engineery enough or should we do another recording?

Z: *inaudibletoaudiencebutobviouslysayingsomething*

ZWabbit: What do you mean that was live?

RAPPS DB is updated/fixed as far as possible. If anything listed as test case for 0.4.2 does not load, let me know ^^

Actual release candidate now uploaded.

Well, I can tell you that it doesn't like VMWare Workstation very much. As with 0.4.1, the first boot after installation is a BSOD. (No BSOD in VirtualBox 5.1.2)

Unlike 0.4.1, anything I download in the Application Manager stops at 98%. The first time this happened, I gave up and tried to close the dialog with the Cancel and X buttons to no avail, and then used Ctrl+Alt+Del to request the Task Manager, which froze the system and required a reboot. I later learned that it will hit 99% after about 3 minutes, and 100% 3-5 minutes after that. In VirtualBox 5.1.2, the delay at 99% is about a second.

It's a long wait, but when I eventually installed Opera 12.18 and Firefox 45.0.1, they worked great. Opera 12.18 doesn't support SVG transformations (my current obsession), so Firefox is your only option for a modern web experience. One odd thing with Firefox, though, is there was no maximize button on the title bar. I had to use Alt+Spacebar to bring up the option.

Interestingly, I can't get Firefox 45.0.1 to work in VirtualBox 5.1.2. It installed fine, but froze the system when it brought up the default pages. Upon reboot, I was able to visit one of my websites, which had all of the text overlapping at the top of the page. I then visited cnn.com, which was starting to display properly when it froze the system. Again, there's no maximize button, so Alt+Space FTW. Opera 12.18 works great but, again, no SVG animations, so I can't use the modern web in ReactOS 0.4.2 RC1 in VirtualBox.

0.4.2 working on bare metal, ASUS EEE PC 1000

Running into issues trying to install chipset/graphics drivers though, installer says it's not compatible with "WNT_5.2" (NT vers 5.2) though I am using the XP 32-bit drivers on a 32-bit system

I am new to ROS.

I burned the 41 live cd and it works fine.

Where do I download the 42 live cd?

C1

cirrus one wrote:I am new to ROS.

I burned the 41 live cd and it works fine.

Where do I download the 42 live cd?

C1

Here you are: https://sourceforge.net/projects/reacto ... z/download

That's not a livecd, Victor.

We do not test livecds while preparing a release, since whether a livecd works or not does not tell us anything useful about application compatibility.

42 is broken on my PC.

I burned the ISO you gave me the link to.

I get the following error:

Error reading NLS file
Multi(0)
Disk(0)
Cdrom(111)\
Reactos\system32\l_intl.nls

The PC is an ASUS K53E I5 with a built in DVD reader.

41 boots just fine.

C1

wHat you could do if there are no current bugs
Is to

Boot the DVDs in the 42 way

If it fails then try the 41 way

Before print the error msg and exit

c2

There is no "0.4.1 way" and "0.4.2 way" that could be switched, unfortunately. There are many components collaborating to be able to boot and some combination of changes in them, between these two releases, caused the boot to not work anymore in 0.4.2 even though 0.4.1 did work. Also all this might happen only on your machine, there may be other people who didn't boot with 0.4.1 but now do with 0.4.2... which makes it harder to find the root cause for your machine.

There must be code changes at the source level between 41 and 42.
The problem has to be developing between the very first line of code
that executes in the boot sequence and where it prints the error.

I suggest identifying these differences as a starting point.

Then rule them out one by one.

At 41 when I booted I saw 4 options to select including debug modes.

I don't see this at 42. This would help.

I will be glad to help you track this down.

C1

I had burned several ISO files before the 41 iso that worked.

The ones that DONT work and DO work BOTH say

multi(0) disk(0) cdrom(111) this is a starting point.

Is there a way do download old nightly builds?

if so I can identify the first build where the problem
started happening.

cirrus one wrote:Is there a way do download old nightly builds?

https://reactos.org/getbuilds/

How I got there:
Choose "BACK TO WEBSITE" link at the top of this page.
Scroll down the page to the "Daily Builds" button on the right side of the page.
Choose the "Daily Builds" button to expand it. Choose the "Download here!" button that appears.

As 41 is ok if you tell me which incremental build number
in the 7xxx format corresponds to 41 I will test ISO files
starting there in increments of say 25 until I find it then in
increments of 1 until it is narrowed downed.

Is there a way to access source code?

C1