0.3.1 Released

[Radhad]

VMWare uses some ressources of the pc directly, qemu emulates all hardware. Try the Qemu pre-installed version instead of the VMWare pre-installed version.

[Sosekoppen]

I've not used KQEMU, but I wonder if I forgot to exit and reopen Qemu when I rebooted ROS...

[fritz.mueller]

Hi,
I once again tried to install Reactos on a 4,3 GB HD - it still does not work. I created an encase image and looked on it.
In my eyes the reason is very simple:
Freeldr.sys starts at physical sector 152.679 of the HD, CL 17012
Freeldr.ini starts at physical sector 153.335 of the HD, CL 17094
Bootsector.old starts at physical sector 153343, CL 17095.

Usually the kernel should be at the beginning of the FAT HD. So I am not astonished that it does not work.

I will report it as bug.

[barker]

thanks for the suggestion Radhad, unfortunately qemu doesn't compile with gcc-4, at least fails to run on my machine. I used to run it when I had a gcc-3 based system.
I'll probably hunt out an old HDD and try and install 0.31

cheers

barker

[simonsphotos]

I had this with this and the previous version. if I go into "my computer" and open a drive (that opens a new window) when I close it again I am left with a grey rectangle where the windows was. only solution is to close "my computer"

I have an Intel C2D E6300 asus P5GZ-MX mainboard an asus PCIe video card with the nvidia EN6200LE GPU on it and 64 MB of ram the main pc ram is 2 GB DDR2. I had the problem when I used the live cd on the last edition and use the virtual machine version this time

[dawinsor87]

Hello ReactOS Devlopers-

I am pretty new to reactOS.

I download 0.3.0 full install about two weeks ago and tried it on a computer (I have the enormous luxury of working in a technology department), and I had no end of trouble with it.

Right now I am running 0.3.1 on Qemu on my computer and it's working great. I wanted to thank you for giving hope to us who don't like microsoft, and feel crippled in linux (me, me!!!)

So yes, thanks

-Dustin

[GreyGhost]

Hello dawinsor87 ,
Nice to hear that you are liking ROS !!
please hang around and support ReactOS

[Martin Lemke]

Bad news!

After splash the screen leaves black. Nothing else.

Testing machine: AMD 64, 1 GB RAM

Martin

[GreatLord]

known problem with amd64 with vmware or real hw

this is cause of unfinish code in trap.s

[Jaix]

Wonderful!
ReactOS 0.3.1 works good under QEmu on Transmeta just as good as 0.2.8.

[bastetfurry]

known problem with amd64 with vmware or real hw

this is cause of unfinish code in trap.s

No chance for some hotfix/quick workaround?

I dont have any intel machine here, only amd, so i am pretty much f*

[simonsphotos]

known problem with amd64 with vmware or real hw

this is cause of unfinish code in trap.s

No chance for some hotfix/quick workaround?

thats the reason why windows is so bad... a big patch up of hotfixes and second hand solutions give it time they will fix it

[mvent2]

known problem with amd64 with vmware or real hw

this is cause of unfinish code in trap.s

No chance for some hotfix/quick workaround?

I dont have any intel machine here, only amd, so i am pretty much f*

If you want to use ROS so badly then use a VM (it needs to be either VMWare or QEmu)

[GreatLord]

No chance for some hotfix/quick workaround?

it does not exists any real fix for it yet or any real work around.

and it is on our list this bug, and it will be fixed when it be.

it exists some higher piror bugs at moment

1. Remove of software emulations of PIC
this cause a faster reactos and irq start been sending right

2. rewrite some code in hal after remove software pic
the old code did devlier wrong irq at wrong level and other thing
even some time to wrong hw device.

this issue are highest prior that why reactos trunk have some issue after alex did fix thuse issue, it end in other regress that none did preditc
like no qemu or vmware then alex did work hard getting back qemu working now it is some timer issue with vmware and work are progress to solv it. after this big issuse and all known regress it cause we can start constrated on other bugs again.