Why do you need to start on real hardware?
This is fairly unsupported at the moment, so you’re really in no-mans-land here.
I’d suggest a virtual machine until you become more familiar with it.
Anyway, looking at your hardware spec I don’t see any untoward.
Continuing down the real hardware path, your next step is to obtain debug output.
The only current method to do this is via a null-modem cable, as specified in the link I gave you.
Ged.
From: James Muthee [mailto:jsoftpacks@yahoo.co.uk]
Sent: 31 December 2008 09:12
To: Ged
Subject: RE: [ros-dev] Problems installing REACTOS
Hello Ged.
Thanks for the prompt reply.
First, I need to test the software on a real machine. No Virtualization, no support form any other OS.
As for the exact configuration of the system, I am forwarding the entire report from the windows system info.
I know its lengthy but, then again you would be looking for someting specific.
My disks are FAT32
Please help.
Thanks
James I. M.
--- On Tue, 30/12/08, Ged <gedmurphy(a)gmail.com> wrote:
From: Ged <gedmurphy(a)gmail.com>
Subject: RE: [ros-dev] Problems installing REACTOS
To: jsoftpacks(a)yahoo.co.uk, "'ReactOS Development List'" <ros-dev(a)reactos.org>
Date: Tuesday, 30 December, 2008, 1:59 PM
It could be a whole range of things.
Without having your hardware spec and debug output, it’s impossible to tell.
If you just want to test it, it’s better to run it in a virtual machine.
If you’re insistent on running it on hardware, then you’ll need to start by supplying your hardware details.
If that doesn’t show any obvious problems (e.g. SATA, NTFS, etc) then you will need to grab debug output via a null cable modem <http://www.reactos.org/wiki/index.php/Debugging#Real_computer:_Physical_ser…> http://www.reactos.org/wiki/index.php/Debugging#Real_computer:_Physical_ser…
Good luck.
Ged.
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of James Muthee
Sent: 30 December 2008 11:21
To: ros-dev(a)reactos.org
Subject: [ros-dev] Problems installing REACTOS
Hello.
Having downloaded the software (I was amazed it was less than 40MB), I wrote the ISO on a CD and started the installation.
0.3.7 failed to install completely, stopping dead just after loading the initial files.
I downloaded the 0.3.6 and tried again. This time, I was able to install the first portion (copying the textmode installation to the hard disk and modifying the MBR).
On restart, A GUI window flashed then a blue screen with a single line about the Build, and that was the end.
What am I doing wrong?
I would appreciate any help. I really want to test drive this software.
James I. M.
Just wanted to tell this is a great work, and with such test suite we
will always notice if something breaks.
WBR,
Aleksey Bragin.
On Dec 30, 2008, at 7:04 AM, hyperion(a)svn.reactos.org wrote:
> Author: hyperion
> Date: Mon Dec 29 22:04:51 2008
> New Revision: 38461
>
> URL: http://svn.reactos.org/svn/reactos?rev=38461&view=rev
> Log:
> modified tests/pseh2/psehtest.c
> finally_13 test re-enabled, as it doesn't crash anymore
> finally_14 test fixed. Now we know how exceptions thrown in a
> __finally are supposed to be handled
> PSEH test suite now has 91 tests and passes all of them with
> both GCC and Visual C++
Hello.
Having downloaded the software (I was amazed it was less than 40MB), I wrote the ISO on a CD and started the installation.
0.3.7 failed to install completely, stopping dead just after loading the initial files.
I downloaded the 0.3.6 and tried again. This time, I was able to install the first portion (copying the textmode installation to the hard disk and modifying the MBR).
On restart, A GUI window flashed then a blue screen with a single line about the Build, and that was the end.
What am I doing wrong?
I would appreciate any help. I really want to test drive this software.
James I. M.
Hi,
I imported function ReplaceFileW from Wine, but it do not work in ReactOS.
RepleceFileW there do not pass 11 tests (kernel32_winetest file). I think,
that a problem in call MoveFileEx. Somebody can help with it?
Function in Wine: http://www.reactos.org/paste/index.php/2745/
Patch for ReactOS: http://www.reactos.org/paste/index.php/2744/
--
WBR,
Dmitry Chapyshev
Hi ALL!
Okay, not sure what is going on but here is the original output:
Unhandled exception
ExceptionCode: c0000005
Faulting Address: 682000
Address: 7c91e6ae C:\ReactOS\system32\ntdll.dll
CS:EIP 1b:7c91e6ae
DS 23 ES 23 FS 3b GS 0
EAX: 011f0020 EBX: 011f0020 ECX: 090b071d
EDX: 242c2c64 EBP: 008afc54 ESI: 00681ffe ESP: 008afc4c
EDI: 011f1010 EFLAGS: 00010212
Frames:
77e30000+211d2 C:\ReactOS\system32\user32.dll
77e30000+21365 C:\ReactOS\system32\user32.dll
77e30000+20c56 C:\ReactOS\system32\user32.dll
400000+892c C:\ReactOS\user32_crosstest.exe
400000+8e73 C:\ReactOS\user32_crosstest.exe
400000+a3ab C:\ReactOS\user32_crosstest.exe
400000+b4ac8 C:\ReactOS\user32_crosstest.exe
400000+b4c56 C:\ReactOS\user32_crosstest.exe
400000+1247 C:\ReactOS\user32_crosstest.exe
400000+1298 C:\ReactOS\user32_crosstest.exe
7c700000+218e4 C:\ReactOS\system32\kernel32.dll
(subsystems/win32/csrss/api/wapi.c:115) CSR: received hard error c0000144
(subsystems/win32/csrss/win32csr/dllmain.c:528) The instruction at
"0x7c91e6ae" referenced memory at "0x00682000". The memory could not
be "read".
After patch:
We have a thread overrun, these are already freed! pi -> 18808864 bi -> 6819854
We have a thread overrun, these are already freed! pi -> 18808864 bi -> 6819854
Than, get two exit strings at the command console.
bi -> 6819854 (0x68100E) is the one and it is from MapViewOfFile. The
difference from 0x682000 is 4082.... Well with in the normal page but
why is 0x68100E the start address and not 0x681000?
It could be just simply bad math being used in LoadBitmapImage. Wine
does use the same code in user32 from gdi32 to handle bitmap and
friends.
Thanks,
James
Hi rosdevs!
This is an issue I've been working on for a while on the Wine side of
things and now they have initial support for it. If any of you
Win32k/GDI hackers are interested in making ReactOS look a bit better
on LCDs please enable support in freetype and review the following
Wine patch to get an idea of the requirements.
Thanks
http://source.winehq.org/git/wine.git/?a=commitdiff;h=028617b90ba586bdb3072…
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo