Hi,
Can anyone please let me know how to run React 0.2.8 RC1 on VMware 5.5
Beta.When i run it on vmware its asking to install certain vmwarre tools, i
guess its the graphics driver.Then vmware complains that the driver is not
found for this OS and i dont see anything on the screen.
regards
Jay
Hi I should love to see some new gudieles
how to get svn access. Today it seam anyone
that provide with a patch that is coder can
getting svn access. But I think we need
start think how we should handle it,
Here is some ideas how it can be
1. A maling list with patch or in Bugzila
I love see a maling list with the patch
2. When people have submit the patch
to us we start examing it see if it any godd
(we are doning that already)
3. To get SVN write access u need lest
provide patch in regual basic under
6 month lest, Then after 6 month the provider
can write to mailing list see if can getting
SVN write access before he grant SVN
write access, the full name and mailing
address must be provided, and we should
have a vote if that provder can getting
SVN write access. no accpect from all
this rules.
Yestday some was granted svn access
his name was not on the mailing list
why he got one, he did not write either
on the mailing list asking for svn access
that why I want see new guide lines how
svn write access handles. so every one
know how he is and why he was granted
to be granted after few patcher are not
accpect in my eys. For we are starting
getting alot with people with svn write
access. And new guide lines must be
create.
BestReagds
Magnus Olsen
Hi,
I am new to React-OS but following the project for quite sometime. I would
like to know how the memory managemnet and cache manger works in React
OS.Isit similar to NT?.If anyone can let me know the arcitecture of
these two
components in ReactOS, it would be helpful for me to follow the
code.Youcould also give me a few pointers as of where to start of in
the code for MM
and CM so that i could dissect the flow.
regards
Jay
gvg(a)svn.reactos.com wrote:
>
> - co_IntSendMessage(Window->hSelf, WM_WINDOWPOSCHANGING, 0, (LPARAM) WinPos);
>
> + co_IntPostOrSendMessage(Window->hSelf, WM_WINDOWPOSCHANGING, 0, (LPARAM) WinPos);
>
I think the whole co_IntPostOrSendMessage function is wrong and crazy.
Who made it? Sending and posting messages are completely different things.
I think something like co_IntSendMessageTimeout should be used instead,
but i dont think its implemented yet.
G.
Hi!
From running Setup in the via8233 directory.
http://www.qdigrp.com/qdisite/eng/support/d_downloadcd.htmhttp://www.qdigrp.com/qdisite/driver/utility/sound/Via8233.zip
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(lib/ntdll/ldr/utils.c:2072) Relocating (76160000 -> 6e0000) C:\ReactOS\system32
\comctl32.dll
(lib/ntdll/ldr/utils.c:2072) Relocating (777d0000 -> 782000) C:\ReactOS\system32
\winmm.dll
(lib/ntdll/ldr/utils.c:2072) Relocating (76260000 -> 7db000) C:\ReactOS\system32
\oleaut32.dll
(lib/ntdll/ldr/utils.c:2072) Relocating (77a90000 -> 4b1000) C:\ReactOS\system32
\VERSION.dll
(lib/comctl32/theming.c:138) Could not re-register class L"#32770": 57
FIXME: CopyImage doesn't support IMAGE_ICON correctly!
(lib/ntdll/ldr/utils.c:1190) LdrGetExportByName(): failed to find mxdMessage
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'msacm.drv'
(Status c0000135)
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'midimap.dr
v' (Status c0000135)
(lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1240000) C:\DOCUME~1\ADMINI
~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\193e5.DLL
(lib/ntdll/ldr/utils.c:2015) Failed to create or open dll section of 'C:\DOCUME~
1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\_ISUSER.DLL' (Status c00001
35)
(lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 1263000) C:\DOCUME~1\ADMINI
~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_WUTL951.DLL
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
WARNING: ModifyMenuA at lib/user32/windows/menu.c:4327 is UNIMPLEMENTED!
WARNING: ModifyMenuA at lib/user32/windows/menu.c:4327 is UNIMPLEMENTED!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(lib/ntdll/ldr/utils.c:2072) Relocating (10000000 -> 4c1000) C:\DOCUME~1\ADMINI~
1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP0.DIR\v32audio.dll
(lib/setupapi/devinst.c:1818) : flag DIGCF_PRESENT ignored
Unhandled exception
ExceptionCode: c0000005
Faulting Address: 0
Address: 7c9250bc C:\ReactOS\system32\ntdll.dll
CS:EIP 1b:7c9250bc
DS 23 ES 23 FS 3b GS 0
EAX: 005df4a0 EBX: 7ffdf000 ECX: 7668543c
EDX: 00000000 EBP: 005df4a4 ESI: 00000000 ESP: 005df498
EDI: 00696120 EFLAGS: 00010202
Frames:
76660000+5ccc C:\ReactOS\System32\SETUPAPI.DLL
76660000+6ba9 C:\ReactOS\System32\SETUPAPI.DLL
76660000+55fc C:\ReactOS\System32\SETUPAPI.DLL
76660000+540c C:\ReactOS\System32\SETUPAPI.DLL
4c1000+1452 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_ISTMP
0.DIR\v32audio.dll
400000+fff8 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55
76._MP
400000+10b29 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55
76._MP
400000+16912 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55
76._MP
400000+16bff C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55
76._MP
400000+10e60 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55
76._MP
400000+113ad C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55
76._MP
400000+76b77 C:\DOCUME~1\ADMINI~1.REA\LOCAL_~1\Temp\_ISTMP3.DIR\_INS55
76._MP
7c800000+31255 C:\ReactOS\system32\KERNEL32.dll
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
(subsys/win32k/ntuser/class.c:125) Failed to lookup class atom!
The linux sound system does work.
Thanks,
James
I started compiling ReactOS 0.2.7 on my Linux box
uname -a
Linux localhost 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 Celeron
(Coppermine) unknown GNU/Linux
This was the result.
I'm using i586-mingw32mscv-*. Now my question is, in which file do I find the
elusive (PREFIX)? Because I can't find it in Makefile.
[wparish@localhost reactos027]$ make
[MKDIR] obj-i386/tools
[MKDIR] obj-i386/tools/rbuild
[MKDIR] obj-i386/tools/rbuild/backend
[MKDIR] obj-i386/tools/rbuild/backend/mingw
[CC] tools/rbuild/backend/mingw/mingw.cpp
[CC] tools/rbuild/backend/mingw/modulehandler.cpp
[CC] tools/rbuild/backend/mingw/proxymakefile.cpp
[MKDIR] obj-i386/tools/rbuild/backend/devcpp
[CC] tools/rbuild/backend/devcpp/devcpp.cpp
[CC] tools/rbuild/backend/backend.cpp
[CC] tools/rbuild/automaticdependency.cpp
[CC] tools/rbuild/bootstrap.cpp
[CC] tools/rbuild/cdfile.cpp
[CC] tools/rbuild/compilerflag.cpp
[CC] tools/rbuild/configuration.cpp
[CC] tools/rbuild/define.cpp
[CC] tools/rbuild/exception.cpp
[CC] tools/rbuild/filesupportcode.cpp
[CC] tools/rbuild/include.cpp
[CC] tools/rbuild/installfile.cpp
[CC] tools/rbuild/linkerflag.cpp
[CC] tools/rbuild/module.cpp
[CC] tools/rbuild/project.cpp
[CC] tools/rbuild/ssprintf.cpp
[CC] tools/rbuild/stubbedcomponent.cpp
[CC] tools/rbuild/testsupportcode.cpp
[CC] tools/rbuild/wineresource.cpp
[CC] tools/rbuild/XML.cpp
[CC] tools/rbuild/rbuild.cpp
[MKDIR] output-i386/tools
[MKDIR] output-i386/tools/rbuild
[LD] output-i386/tools/rbuild/rbuild
[MKDIR] obj-i386/tools/bin2res
[CC] tools/bin2res/bin2res.c
[CC] tools/bin2res/mkstemps.c
[MKDIR] output-i386/tools/bin2res
[LD] output-i386/tools/bin2res/bin2res
[MKDIR] obj-i386/tools/buildno
[CC] tools/buildno/buildno.cpp
[CC] tools/buildno/exception.cpp
[CC] tools/buildno/ssprintf.cpp
[CC] tools/buildno/XML.cpp
[MKDIR] output-i386/tools/buildno
[LD] output-i386/tools/buildno/buildno
[BUILDNO] include/reactos/buildno.h
[MKDIR] obj-i386/tools/wmc
[CC] tools/wmc/getopt.c
[CC] tools/wmc/lang.c
[CC] tools/wmc/mcl.c
[CC] tools/wmc/utils.c
[CC] tools/wmc/wmc.c
[CC] tools/wmc/write.c
[CC] tools/wmc/y_tab.c
[CC] tools/wmc/misc.c
[MKDIR] output-i386/tools/wmc
[LD] output-i386/tools/wmc/wmc
[WMC] include/reactos/bugcodes.h
[WMC] include/reactos/errcodes.h
[MKDIR] obj-i386/tools/nci
[CC] tools/nci/ncitool.c
[MKDIR] output-i386/tools/nci
[LD] output-i386/tools/nci/nci
[NCI] ntoskrnl/include/internal/napi.h
[MKDIR] obj-i386/tools/gendib
[CC] tools/gendib/gendib.c
[MKDIR] output-i386/tools/gendib
[LD] output-i386/tools/gendib/gendib
[GENDIB] subsys/win32k/dib/dib16gen.c
[RBUILD] makefile.auto
Reading build files...done
Detecting compiler...not detected
Detecting netwide assembler...detected (nasm)
Detecting compiler -pipe support...not detected
Detecting compiler pre-compiled header support...not detected
Processing modules...done
Creating directories...done
Unpacking WINE resources...done
Generating test support code...done
Generating proxy makefiles...done
Checking automatic dependencies...done
[DLLTOOL] obj-i386/lib/kernel32/libkernel32.a
make: mingw32-dlltool: Command not found
make: *** [obj-i386/lib/kernel32/libkernel32.a] Error 127
[wparish@localhost reactos027]$
--
Clinersterton beademung, with all of love - RIP James Blish
-----
Mau e ki, he aha te mea nui?
You ask, what is the most important thing?
Maku e ki, he tangata, he tangata, he tangata.
I reply, it is people, it is people, it is people.
This is not the right fix... I will revert these changes when i come up
with a proper fix. I also dont understand how this can fix bug 805
(eternal loop in thread windows cleanup routine). Even with your changes
the eternal loop is still there, it just doesnt run out of stack?
G.
hbirr(a)svn.reactos.com wrote:
> Don't use alloca in a macro, which may be used in a loop. This does fix bug #805.
>
Hi,
during install, I see the following two lines:
(lib\setupapi\queue.c:1441) copy error 2 L"C:\\ReactOS\\inf\\ne2000.sys" -> L"C:\\ReactOS\\System32\\drivers\\ne2000.sys"
(lib\setupapi\queue.c:1441) copy error 2 L"C:\\ReactOS\\inf\\pci.sys" -> L"C:\\ReactOS\\System32\\drivers\\pci.sys"
Why does ROS try to copy drivers from the inf directory?
- Hartmut
After switching too DBG = 0 i get the following error:
[WRC] obj-i386\apps\utils\net\tcpsvcs\quotes.coff
[WRC] obj-i386\apps\utils\net\tcpsvcs\tcpsvcs.coff
[LD] output-i386\apps\utils\net\tcpsvcs\tcpsvcs.exe
[RSYM] output-i386\apps\utils\net\tcpsvcs\tcpsvcs.exe
[CC] apps\utils\net\telnet\src\ansiprsr.cpp
[CC] apps\utils\net\telnet\src\keytrans.cpp
C:/RosBE/bin/../lib/gcc/mingw32/3.4.4/../../../../include/c++/3.4.4/bits/stl_uni
nitialized.h: In member function `void std::vector<_Tp,
_Alloc>::reserve(size_t)
[with _Tp = KeyMap, _Alloc = std::allocator<KeyMap>]':
C:/RosBE/bin/../lib/gcc/mingw32/3.4.4/../../../../include/c++/3.4.4/bits/stl_uni
nitialized.h:82: warning: '__cur' might be used uninitialized in this
function
mingw32-make: *** [obj-i386\apps\utils\net\telnet\src\keytrans.o] Error 1
Do i need to update anything?
Brandon
Hi,
As many of you know, I've been working on Winsock for the last 3 weeks,
then lost all my work. I have finished writing everything that I had
lost and did some serious tests with MIRC. I want to update Ged,
Waxdragon, Ge, Magnus and the others which were interested in a status
report.
MIRC uses some serious features, including asyncronous hostname lookups,
which is an extremly complex part of ws2_32.dll. After fixing about 20
bugs (let me add a small note here: Microsoft has done some SERIOUSLY
amazing work with MSVC 2005. The latest RC1 is now even faster, since
the internal build system was updated and now supports multi-threaded
compiles: ws2_32 takes me 2.5 seconds (officially timed) to compile AND
link AND rc with full optimizations + pdb generated... not only did fast
rebuild times help out during testing, but the integrated debugger just
keeps getting better too. Finding those 20 bugs was extremly easy), I
was able to connect to MIRC by using /server irc.freenode.net and join
the channels, identify and talk normally. DCC transfer worked as well.
Almost all of the ws2_32 APIs were being called, and both TCP and UDP
(from dnsapi) communication seemed to work fine. In other words, mirc
was fully usable with my ws2_32.dll
My next test app is firefox. As of now, it loads fine but hangs at 100%
cpu usage. I'm guessing it must be another small bug causing an inifite
loop somewhere. Since it's 4AM now, I'll go sleep and check it out tomorrow.
Best regards,
Alex Ionescu