Page 1 of 3

Blog: Spilling the Wine

Posted: Mon Jun 23, 2014 6:19 pm
by Z98

Re: Blog: Spilling the Wine

Posted: Mon Jun 23, 2014 7:02 pm
by Webunny
Title could also have been:

"To be frustrated or not to be frustrated, that is the question."

:P

Well, it was an interesting read, but it seems progress remains elusive these last weeks...

Re: Blog: Spilling the Wine

Posted: Mon Jun 23, 2014 7:50 pm
by PurpleGurl
Or "Crying Over Spilled Wine." ;-)

Wow! You use a debugger tool that you cannot debug. Then you fix things to work better in ROS only to find that they break in WINE. I hope the week gets better.

Re: Blog: Spilling the Wine

Posted: Mon Jun 23, 2014 7:55 pm
by Webunny
PurpleGurl wrote:Or "Crying Over Spilled Wine." ;-)

Wow! You use a debugger tool that you cannot debug. Then you fix things to work better in ROS only to find that they break in WINE. I hope the week gets better.
:idea:

Maybe he should use another debugger on the debugger he wants to debug ROS? And if that one fails, use a debugger on that one too. And if that one also fails... etc. rince, repeat, ad infinitum.

:ugeek:

Re: Blog: Spilling the Wine

Posted: Mon Jun 23, 2014 8:56 pm
by gigaherz
Lol. I don't believe debugging WinDbg would be of much use, when the code itself is simply designed to make this specific task (following the code) very hard. Other than the author of the software deciding to let us have an unobfuscated build, I don't believe there's much I can do.

That doesn't mean all is lost, on that aspect, someone with very deep knowledge of x86 assembly and with a chess-worthy mind may be able to solve the puzzle. It's just, that person isn't me.

Re: Blog: Spilling the Wine

Posted: Mon Jun 23, 2014 8:58 pm
by hbelusca
@gigaherz, where can I find this Deleaker app you are using?

Re: Blog: Spilling the Wine

Posted: Mon Jun 23, 2014 9:20 pm
by gigaherz
Here: http://www.deleaker.com/download.html

EDIT: Yes, it requires "registration" for the trial, sadly.

Re: Blog: Spilling the Wine

Posted: Tue Jun 24, 2014 9:57 pm
by gigaherz
Hello, to anyone interested, here are a new set of builds from the branch, right after yesterday's trunk sync (r63640).

You can choose between
  1. Compiled with Mingw-GCC, or
  2. Compiled with VS2013
Remember that VS builds need WinDbg attached to the serial port in order to start the installer (not required afterwards).

[EDIT: Replaced links with reactos-hosted files.]

Re: Blog: Spilling the Wine

Posted: Wed Jun 25, 2014 11:26 am
by rachid
When i set display settings on 32bits

Image

Re: Blog: Spilling the Wine

Posted: Wed Jun 25, 2014 12:29 pm
by gigaherz
You have to reboot after changing the bit depth, it is a known issue.

Re: Blog: Spilling the Wine

Posted: Wed Jun 25, 2014 1:25 pm
by rachid
gigaherz wrote:You have to reboot after changing the bit depth, it is a known issue.
Image

yes, that works
thanks

Re: Blog: Spilling the Wine

Posted: Wed Jun 25, 2014 1:39 pm
by EmuandCo
Oh, you tried Clover... did it work?

Re: Blog: Spilling the Wine

Posted: Wed Jun 25, 2014 1:44 pm
by hbelusca
Hmm there is a problem concerning menus positioning, @gigaherz : see the last picture of rachid, where the "Accessories" menu is cutted down because it is too long for being displayed from where it begins (the same remark also applies for the "System Tools" submenu).

Re: Blog: Spilling the Wine

Posted: Wed Jun 25, 2014 1:48 pm
by gigaherz
hbelusca wrote:Hmm there is a problem concerning menus positioning, @gigaherz : see the last picture of rachid, where the "Accessories" menu is cutted down because it is too long for being displayed from where it begins (the same remark also applies for the "System Tools" submenu).
I believe that screenshot was cropped, since it's properly aligned to the bottom of the screen for me. If that's not the case, I'll need more info to replicate the issue.

Re: Blog: Spilling the Wine

Posted: Wed Jun 25, 2014 2:00 pm
by gigaherz
I'm collecting a list of known issues and missing features for these builds. I'm using a collaborative text editor based on the source of EtherPad, so that anyone can contribute their findings. The list is not supposed to include extra things that Windows 2003 never did.

The issues in the list will be triaged and included in my TODO list.

Disregard the bad-sounding name of the site, there's nothing illegal in the link: http://piratepad.net/1TSvbV9Gez

EDIT: The links in the other post have been updated.