IRC Logs

Network: freenode Channel: #reactos

	Enter your search terms Submit search form
	Web www.irclog.org

[00:00]<zxyfr>most my coding involves either C# or VB
[00:00]<wd-afk>no ideas on the bootvid crash. ok.
[00:00]<gznzvljzm>I got a ideay
[00:00]<gznzvljzm>why
[00:01]<gznzvljzm>some how the mapping to video memmory are not done yet
[00:01]<gznzvljzm>so it try write to a memmory
[00:01]<gznzvljzm>that does not easists yet
[00:02]<wd-afk>ooh
[00:02]<zxyfr>psu?
[00:02]<ggajmgm>power supply
[00:02]<wd-afk>mixing my viewpoints again.
[00:02]<zxyfr>oh
[00:02]<wd-afk>I think I may have one...
[00:03]<gznzvljzm>if u like we can make a hack so it work, but it will not show reactos start logo
[00:03]<gznzvljzm>then
[00:03]<wd-afk>:0/
[00:03]<wd-afk>I'm trying to figure out why it works in trunk.
[00:04]<wd-afk>Maybe NDK fixed it.
[00:04]<gznzvljzm>2 weeks
[00:04]<gznzvljzm>max
[00:04]<gznzvljzm>it was fixed in trunk
[00:04]<wd-afk>LISTEN TO ME
[00:04]<wd-afk>21879 is broken, 21890 works.
[00:04]<wd-afk>There is the range
[00:05]<wd-afk>There is very little other than NDK is that range.
[00:05]<ggajmgm>lol we are never gonna release 0.
[00:05]<ggajmgm>3
[00:05]<wd-afk>Well, Abiword is still broken also.
[00:06]<ggajmgm>we can release 0.3.1 soon ;)
[00:06]<fyzn2rff>abiword gonna become a known regression shipped with 0.3
[00:06]<cia-7>03fireball * r22315 10reactos/media/doc/HACKING: Slightly update the doc to make it correspond to nowadays reality
[00:06]<wd-afk>hmm ok
[00:08]<gznzvljzm>21779, 21280 unlock files
[00:08]<gznzvljzm>Fireball _ I talk with w3seek
[00:09]<gznzvljzm>last time he told he is working on it
[00:09]<fyzn2rff>yes, I wish he fixed it
[00:09]<fyzn2rff>ah, he posted a few patches today afaik btw
[00:10]<gznzvljzm>He told mem before to fix it something else need be fixed
[00:10]<gznzvljzm>frist
[00:10]<fyzn2rff>yes
[00:10]<ggajmgm>zomg
[00:10]<ggajmgm>reactos is leaking
[00:11]<wd-afk>maybe I just need to regression test it.. I know I was selfhosting with release builds not too long ago.
[00:11]<ggajmgm>and lsass.exe is using 90% of proc time
[00:13]<emurgmcj>BRB
[00:14]<gznzvljzm>WD-AFK : maybe Revision: 21886
[00:14]<ggajmgm>debug output is filled wth (dll\wn32\lsasrv\lsarpc.c:132 LsarClose(0x00000000) called!
[00:14]<ggajmgm>debug output is filled wth (dll\win32\lsasrv\lsarpc.c:132 LsarClose(0x00000000) called!
[00:15]<gznzvljzm>wax try 21886
[00:16]<wd-afk>GL: no
[00:16]<gznzvljzm>for w3seek did ask for a revert
[00:16]<wd-afk>I reverted that out in 0.3.0
[00:16]<wd-afk>and it still happens
[00:16]<ggajmgm>LsaOpenPolicy-stub called
[00:17]<gznzvljzm>only thing I can see it is ndk
[00:17]<gznzvljzm>then
[00:18]<gznzvljzm>or hpoussin changes
[00:18]<wd-afk>I'm 99% sure I merged that into 0.3.0 also
[00:18]<wd-afk>setupapi and newdev were synced to trunk.
[00:19]<wd-afk>Hell, I'm about ready to just put out RC1 with that. It works fine on my hardware. ;0)
[00:20]<gznzvljzm>can u try for fun merge down ndk
[00:20]<gznzvljzm>local in a tree
[00:20]<wd-afk>You and I have differing definitions of "fun"
[00:20]<gznzvljzm>see if that happen
[00:21]<gznzvljzm>it is fun gussing what fualt it can be
[00:21]<gznzvljzm>;)
[00:21]<gnmmuzlxd>lol
[00:21]<gznzvljzm>or let other ppl do the work
[00:23]<fyzn2rff>merging ndk into 0.3 is a BIG fun :-)
[00:24]<emurgmcj>Nah, not today again.... still a headace
[00:24]<gznzvljzm>that remind me I need pay so bills
[00:24]<gnmmuzlxd>lame excuse
[00:25]<fyzn2rff>dumb question:
[00:25]<fyzn2rff>nvm
[00:25]<fyzn2rff>I won't ask it lol
[00:25]<wd-afk>oh, and if I boot 0.3.0 with a freeldr bootdisk and choose serial debugging, it boots.
[00:26]<wd-afk>and it will continue to boot after that without the bootdisk.
[00:28]<wd-afk>and there is no real fix for the 0.3.0 under qemu issue, but we can revert out the change.
[00:28]<wd-afk>afk for real
[00:37]<emurgmcj>How much of ReactOS code could/should ba able to be shared with wine code without any changes?
[00:38]<ggajmgm>enough
[00:40]<emurgmcj>So automatic sharing would reduce work enough to be risked/tried?
[00:41]<ggajmgm>yes
[00:42]<ggajmgm>ofcourse many dlls cant be shared
[00:42]<ggajmgm>but those that can..
[00:42]<ggajmgm>will save us alot of trouble
[00:42]<emurgmcj>I think nobody really cares, but I'm for 2. ;-)
[00:42]<fyzn2rff>lol
[00:43]<ggajmgm>EmuandCo, building wine code takes forever
[00:43]<ggajmgm>if we remove the code and compile it in a server...
[00:43]<gnmmuzlxd>going for option 3 will speed up our build :)
[00:43]<ggajmgm>what GedMurphy said :)
[00:43]<fyzn2rff>and that speed up will be very noticable
[00:44]<emurgmcj>Hmm... But you cant control the build process of those files anymore.
[00:44]<gnmmuzlxd>I don't want to build them
[00:44]<emurgmcj>Not relevant for me, but....
[00:44]<gnmmuzlxd>we shouldn't need to change them
[00:44]<fyzn2rff>what do you mean - control?
[00:45]<emurgmcj>Stuff like useing a different compiler or stuff like -O3
[00:45]<fyzn2rff>ah

Back to #reactos
Or go to some related logs:
#gentoo
#debian
#macosx
#gentoo
#gentoo