># running
># > loadros system32\ntoskrnl.exe system32\hal.dll /DEBUGPORT=SCREEN
>bootc.lst
I think, you tried to run ROS from DOS, too.
But have a look at
http://reactos.com:8080/archives/public/ros-general/2004-March/000824.html
Let ROS installed in C:\reactos and create additional a boot-floppy-disk, on
which FreeLoader is.
Then let the floppy in its drive and run it be rebooting the computer.
Greatings
theuserbl
_________________________________________________________________
Wußten Sie, daß Sie Ihren Hotmail-Posteingang auch über den MSN Messenger
abrufen können? http://www.msn.de/messenger Jetzt kostenlos downloaden und
einfach testen!
>From: Bernd Blaauw <bblaauw(a)home.nl>
>Reply-To: ros-general(a)reactos.com
>To: ros-general(a)reactos.com
>Subject: Re: [ros-general] Booting problem [0.2.0]: can't find exports &
>mouse
>Date: Thu, 11 Mar 2004 15:08:29 +0100
>
>how to create the bootfloppy?
At first download
http://reactos.csh-consult.dk/download.php?sid=FreeLoader-20040310-bochs.i3…
The newest version of FreeLoader you can find at
http://reactos.csh-consult.dk/index.php?page=snapshots
Then unpack it with WinZip (http://www.winzip.com/) or on Linux/Unix with
"tar xvfz fileename".
Then you have an floppy image called freeldr.img
To write this image to a floppy disk use RawWrite
(http://uranus.it.swin.edu.au/~jn/linux/rawwrite.htm) for example. Or an
linux type in: "dd if=freeldr.img of=/dev/fd0"
>is the program for writing freeldr to diskette delivered with ReactOS?
No.
>can it run from DOS?
Yes, please use RawWrite for DOS for this:
http://www.tux.org/pub/dos/rawrite/
>can it run from Windows? (autorun.inf entry maybe?)
Yes, then use RwawWrite for Windows:
http://uranus.it.swin.edu.au/~jn/linux/rawwrite.htm
But you can use RawWrite for DOS, too. But that it isn't with GUI.
>can it run from ReactOS? (guess not, as long as floppy is disabled).
don't know.
Greatings
theuserbl
_________________________________________________________________
Schluß mit Spam! http://www.msn.de/antispam/prevention/junkmailfilter Wir
helfen Ihnen, unerwünschte E-Mails zu reduzieren.
I wrote on ~Feb 24 that has a problem booting ROS (binary dist. v0.2.0). JH
asked me for debug log, so after a small delay here it comes (my own comments
're prepended by dash #):
# running
# > loadros system32\ntoskrnl.exe system32\hal.dll /DEBUGPORT=SCREEN bootc.lst
# Now I'm in a blue screen & receiving next messages
# ...
DriverBase for \SystemRoot\System32\kbdus.dll: ce488000
(ntuser/input.c: 86) Win32K: Failed to open mouse
# although I have Microsoft-compartible mouse on COM1
LdrGetExportByOriginal (Original 167) = 76168223
LdrGetExportByOriginal (Original 71) = 76167600
LdrGetExportByOriginal (Original 151) = 76168a2c
LdrGetExportByOriginal (Original 328) = 7616948e
LdrGetExportByOriginal (Original 386) = 7616a345
LdrGetExportByOriginal (Original 332) = 761696da
LdrGetExportByOriginal (Original 334) = 7616979f
LdrGetExportByOriginal (Original 339) = 76169cc9
LdrGetExportByOriginal (Original 338) = 76169c6f
LdrGetExportByOriginal (Original 154) = 76168af2
LdrGetExportByOriginal (Original 169) = 76167fe6
LdrGetExportByOriginal (Original 73) = 76167b6a
LdrGetExportByOriginal (Original 152) = 76167ede
(NTDLL: ldr/utils.c: 2041) Failed to create or open dll section of
'wineoss.drv' (Status c0000135)
(NTDLL: ldr/utils.c: 1191) LdrGetExportByName(): failed to find
GetModuleHandle16
(NTDLL: ldr/utils.c: 1191) LdrGetExportByName(): failed to find LoadLibrary16
(NTDLL: ldr/utils.c: 2041) Failed to create or open dll section of
'msacm.drv' (Status c0000135)
(NTDLL: ldr/utils.c: 2041) Failed to create or open dll section of
'midimap.drv' (Status c0000135)
# after this point it hangs up
Can anybody deal with this? ROS is unpacked into c:\reactos (as should be),
loaded from clear DOS (which is itself booted from floppy). If you need more
info, ask.
One more problem: this log is handwritten from screen, I've no machine near
me to write a log to it through COMx, so how do I make ROS loader write log
to a file (you see, those errors appear after drives're detected)?
>The following programmes have failed to install:
Not all programs can currently run on RectOS.
But what me more wunder: ReactOS 0.2.0 runs Solitaire (with its own
cards.dll) perfect.
But ReactOS 0.2.1 fails to run it. It ends with kernel panic. (blue screen)
>Bug detected (code 1e param 0 0 0 0)
> KMODE_EXCEPTION_NOT_HANDLED
>
>Page Fault Exception: 14(0)
>Processor: 0 CS:EIP 8:cde8a020 <win32k: 34020>
>cr2 3 cr3 2a63000 Proc: c156d938 Pid: a <gvim61> Thrd: c156dbe0 Tid: 33
>DS 10 ES 10 FS 30 GS 10
>EAX: 00000000 EBX: 00000010 ECX: cdeb5460
>EDX: 00000000 EBP: ce577f04 ESI: 005274cc
>EDI: ce577f84 EFLAGS: 00010206 kESP ce577e70 kernel stack base ce575000
>ESP ce577e70
>Frames: <win32k: 34222> <win32k: 3385c> <ntoskrnl.exe: 32f7> Page fault at
>high IRQL was 2
>ExceptionRecord->ExceptionAddress = 0xc0001cf5
>KeBugCheckWithTf at ke/catch.c:168
>Bug detected (code 1e param 0 0 0 0)
> KMODE_EXCEPTION_NOT_HANDLED
>
>Recursive bug check halting now
Yes, something like this comes after starting Solitair on ROS 0.2.1. Only
the values are different.
An other point what me wonder is the standard-driver of ReactOS.
It seems, that ReactOS itself runs with the standard-driver (and I don't
have installed any other one) in 16 or 32 colors. And the resolution is very
low.
But at starting, the starting-picture with the ReactOS-logo seams to have a
lot of more colors then ReactOS, when it runs. And it seems that the logo
have a better resolution, then the running ReactOS.
Btw: To an other point: I think it would be nice, if you change cmd.exe so,
that an "dir" can - with or without an option, thats unimportant - show it
like an Win95/Win98 "dir".
On my computer ReactOS runs on the Win98-partition. And all file-names
existing so, in twi versions: In the long names version (VFat) and in 8+3
(DOS-FAT) version.
But after typing in "dir" it shows only the long versions.
And after typing in the option "dir /w" it shows only the 8+3 versions.
Would be nice, if there existing an option (or as default) where the long
version and 8+3 version are _both_ shown.
Is possible, that the NFS don't have a 8+3 part. So, then it would be nice,
that only on DOS/Win95/Win98 partitions the 8+3 files will be shown. And on
NFS filesystems only the long versins like yet.
Greatings
theuserbl
_________________________________________________________________
MSN Messenger - sehen, welche Freunde online sind!
http://www.msn.de/messenger Jetzt kostenlos downloaden und mitmachen!
Pentium 3 450Mhz 64mb ram Reactos 0.2.1
The following programmes have failed to install:
VIM 6.1
verifies - installer window (full screen) little window, click on yes button, then ros's command prompt window
comes up with the message " 460 error number: 2 press enter key to continue " . Hit enter, then installer screen comes
to front and then license window (Nullsoft Install System v1.95), click on agree and ros dies with the following
error messages:
Bug detected (code 1e param 0 0 0 0)
KMODE_EXCEPTION_NOT_HANDLED
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:cde8a020 <win32k: 34020>
cr2 3 cr3 2a63000 Proc: c156d938 Pid: a <gvim61> Thrd: c156dbe0 Tid: 33
DS 10 ES 10 FS 30 GS 10
EAX: 00000000 EBX: 00000010 ECX: cdeb5460
EDX: 00000000 EBP: ce577f04 ESI: 005274cc
EDI: ce577f84 EFLAGS: 00010206 kESP ce577e70 kernel stack base ce575000
ESP ce577e70
Frames: <win32k: 34222> <win32k: 3385c> <ntoskrnl.exe: 32f7> Page fault at high IRQL was 2
ExceptionRecord->ExceptionAddress = 0xc0001cf5
KeBugCheckWithTf at ke/catch.c:168
Bug detected (code 1e param 0 0 0 0)
KMODE_EXCEPTION_NOT_HANDLED
Recursive bug check halting now
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CDex
installation screen (Nullsoft Install System v1.43) click on next button, then it crashes with the following error messages:
Bug detected (code 1e param 0 0 0 0)
KMODE_EXCEPTION_NOT_HANDLED
Page Fault Exception: 14(0)
Processor: 0 CS:EIP 8:cde8a020 <win32k: 34020>
cr2 3 cr3 25b8000 Proc: c1574110 Pid: c <cdex_140> Thrd: c15857a8 Tid: 37
DS 10 ES 10 FS 30 GS 10
EAX: 00000000 EBX: 00000010 ECX: cdeb5460
EDX: 00000000 EBP: ce199f04 ESI: 00519490
EDI: ce199f84 EFLAGS: 00010206 kESP ce199e70 kernel stack base ce197000
ESP ce199e70
Frames: <win32k: 34222> <win32k: 3385c> <ntoskrnl.exe: 32f7> Page fault at high IRQL was 2
ExceptionRecord->ExceptionAddress = 0xc0001cf5
KeBugCheckWithTf at ke/catch.c:168
Bug detected (code 1e param 0 0 0 0)
KMODE_EXCEPTION_NOT_HANDLED
Recursive bug check halting now
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The following progs also crash after one or two windows, with similar error messages, as above:
Crack Attack (nullsoft in v1.96) crashes
dia (nullsoft in v1.93) crashes
Ethereal (nullsoft in v1.98) crashes
Exodus (nullsoft in v1.98) crashes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have noticed that self extracting installers do not work in ros
I think that I have sent enough error messages in for installation failures on ros 0.2.1 ,
so I will not send any more for this release.
Regards,
jh
Pentium 3 450Mhz 64mb ram Reactos 0.2.1
I have successfully installed the following programmes from cd. I did not alter the suggested file path,
which was the normal C:\program files
tuxpaint:
This runs in ros, but as with some other programmes such as abiword, the buttons are not fully developed, also ' save ' does not work.
This installation failed in ros 0.2.0.
FileZilla 2.1.2:
This installed ok but rendered ros useless (but not locked up) after finishing installation.
It runs in ros, but I have not used it beyond the profile window.
These and other programmes can be found here: http://gnuwin.epfl.ch/apps/en/index.html
Regards,
jh
Dear ReactOs-Team,
first of all i have to tell you that you make a great job. Go on with it.
Unfortunately i have no skills in programming, but in computergraphics.
Of course the programming is now more important than the design. So i think that you
dont pay the design much attention now. But in this point i can help you - if
you want.
I started to make a new icon set for ReactOs (click on the link). I tried to
make it different from
Windows, but not too different. Just enough to see a difference, but also to
understand immediately
what the icons stand for, if you know Windows. They look very serious and have
not that
"colorful-mainstream-children-windows-xp" design... :-)
Notice: The icon for the unknown file types are changed right now by me. As you
can see in the forum on the website, there were advices for a better icon. I´ll
follow them.
http://www.rene.boyke.de/newicons.jpg
If you want, take a look. There are just three on the website. If you dont like
them, i will stop
designing more. If you do like them, i will go on with the work.
Of course they are all for free. Here is my eMail, if you are interested:
boyke-jura(a)stud-mailer.uni-marburg.de
greetings
>Hi,
>I have an old 486 DX2 66Mhz computer with 32MB memory 261MB hard drive
>which I have unzipped the ros binaries onto, they are in C:\reactos. When I
>run ros it prints info to screen up to checking drive ' C: ok ', the drive
>light continues flashing away for about 15 to 20 seconds, then ros dies
>with no error message and falls back to bios. No initialization screen is
>ever shown.
Have a look at
http://reactos.com:8080/archives/public/ros-general/2004-March/000824.html
Let your installation in C:\reactos and creating additionaly an floppy-disk
with freeloader.
Greatings
theuserbl
_________________________________________________________________
Wußten Sie, daß Sie Ihren Hotmail-Posteingang auch über den MSN Messenger
abrufen können? http://www.msn.de/messenger Jetzt kostenlos downloaden und
einfach testen!
Hi,
When I load abiword in ros, it displays most of the menus in german, with the exception of the words ' default EN_US '.
Is the ros explorer getting entangled with abiword ? If I run the very same abiword in win95, it displays in english.
I have tried the latest version from http://abiword.pchasm.org/builds/periodic/ and a older version that I have already got installed, both behave the same.
Regards,
jh
For your information , with this last patch , The display card "Matrox
mystique" is supported successfully by Reactos in real hardware.
(Pentium 233)
The Desktop has been displayed on the screen and I was able to select
start menu bar as a first basic test..
Thanks to filip and all others to have made this possible.
Regards
Gearrd