#pentagram@irc.freenode.net logs for 26 Oct 2005 (GMT)

Archive Today Yesterday Tomorrow
Pentagram homepage


[00:11:08] <-- Kirben_ has left IRC (Read error: 104 (Connection reset by peer))
[00:11:22] --> Kirben_ has joined #pentagram
[00:11:22] --- ChanServ gives channel operator status to Kirben_
[00:11:51] <-- Kirben has left IRC (Nick collision from services.)
[00:11:56] --- Kirben_ is now known as Kirben
[01:14:37] --> oaK_ has joined #pentagram
[01:15:13] <-- oaK has left IRC (Read error: 104 (Connection reset by peer))
[04:59:35] --> Colourless has joined #Pentagram
[04:59:41] --- ChanServ gives channel operator status to Colourless
[10:30:34] <-- Kirben has left IRC ("System Meltdown")
[12:14:04] <-- oaK_ has left IRC (Read error: 110 (Connection timed out))
[12:57:39] --> oaK has joined #pentagram
[13:16:00] <-- Colourless has left IRC ("casts improved invisibility")
[17:55:45] --> Beeble_ has joined #pentagram
[17:55:48] <Beeble_> hmm
[17:55:51] <Beeble_> hey wjp
[17:56:05] <Beeble_> is it not possible to walk up stairs in u8 through pentagram?
[17:58:03] <oaK> should be
[17:59:11] <wjp> hi
[17:59:31] <oaK> Doesn't work at all places
[17:59:45] <wjp> it's working somewhat suboptimally currently :/
[18:00:04] <oaK> for example guard house in very beginning
[18:00:34] <wjp> at the docks it also seems to want to walk the stairs diagonally
[18:01:16] <wjp> I'll have to see what's causing it to think it can't walk straight up or down
[18:02:24] <Beeble_> I can't walk up any stairs
[18:02:25] <Beeble_> currently
[18:02:27] <Beeble_> :/
[18:04:53] <Beeble_> except the dock steps
[18:05:23] <Beeble_> well like I just can't get up stairs in houses
[18:06:20] <Lightkey> sometimes confusing if two have only three letters in a chat.. especially if both are coloured the same *grr*
[18:07:31] <wjp> it probably fails to walk up stairs if they're too narrow to walk diagonally
[18:33:18] <Beeble_> yeah I'm definitely not able to get up any stairs at all
[18:33:21] <Beeble_> I've tested a ton
[18:33:51] <wjp> yeah, there's something very wrong with the code that checks if you can move up a step
[18:51:57] <wjp> ah... oops
[18:58:13] <-- Darke has left IRC (Read error: 110 (Connection timed out))
[18:58:45] <wjp> hm, fixed the 'only diagonal' problem, but that exposed another issue
[19:00:14] <wjp> there are invisible objects above the stairs in the guardhouse
[19:05:36] <Beeble_> btw I'm e4man from 2 days ago
[19:06:43] <wjp> yeah, I noticed the hostmask
[19:07:18] <wjp> (efourman.res)
[19:16:22] <Beeble_> :P
[19:16:47] <wjp> ok, located the other problem as well...
[19:23:42] <wjp> right; fixed now
[19:23:59] <wjp> the next available snapshot from our homepage should contain these two fixes
[21:50:18] --> Darke has joined #pentagram
[22:02:12] --> nONSENCE has joined #pentagram
[22:02:29] <nONSENCE> hi
[22:02:42] <nONSENCE> got a quick question if anyone is there
[22:02:43] <wjp> hi
[22:02:48] <nONSENCE> hey wjp
[22:03:28] <nONSENCE> do you know why you would push the stack segment register?
[22:03:53] <nONSENCE> cseg133:08A1 loc_81CA1: ; CODE XREF: LoadUseCode2+29Dj
[22:03:53] <nONSENCE> cseg133:08A1 push [bp+var_C]
[22:03:53] <nONSENCE> cseg133:08A4 push [bp+var_E]
[22:03:53] <nONSENCE> cseg133:08A7 push 0C8h ; '+' ; stream
[22:03:53] <nONSENCE> cseg133:08AA push ss ; n
[22:03:54] <nONSENCE> cseg133:08AB lea ax, [bp+s1]
[22:03:56] <nONSENCE> cseg133:08AF push ax ; s
[22:03:58] <nONSENCE> cseg133:08B0 call _fgets
[22:04:00] <nONSENCE> there is a snippet
[22:04:19] <wjp> probably because you're pushing a 32bit pointer to a stack variable
[22:04:58] <wjp> the 'push ss' is the high part and the 'push ax' the low part
[22:05:32] <wjp> note that ax is set to the address (offset) of a stack variable by that lea opcode
[22:07:16] <nONSENCE> ah
[22:07:45] <nONSENCE> thanks i've been hitting my head for an hour
[22:09:04] <nONSENCE> but wait, ax is past as the second arg and n is past as the first to fgets
[22:09:49] <wjp> they form a single argument together
[22:09:56] <nONSENCE> ah do ida is confused
[22:09:58] <nONSENCE> so
[22:10:05] <wjp> and the stack grows downward
[22:10:48] <wjp> so it ends up looking like this in memory: AXSS, which is how they should be given that x86 is little endian
[22:12:43] <wjp> I'm not sure what ida means by the comments it added to the pushes
[22:13:06] <nONSENCE> i ran flirt on it
[22:13:18] <wjp> ah, yes, I guess it is indeed confused
[22:13:42] <nONSENCE> i used borland 16bit library? would that do it?
[22:13:43] <wjp> the ss,ax pair forms s, the 0xC8 would be n, and the 32bit pointer var_C,var_E is stream
[22:14:01] <wjp> I have no experience with flirt
[22:14:01] <nONSENCE> :)
[22:14:47] --> Kirben has joined #pentagram
[22:14:47] --- ChanServ gives channel operator status to Kirben
[22:14:48] <nONSENCE> was ultama8 compiled on a 32bit or 16bit borland compiler?
[22:15:23] <wjp> 32 bit, I would say
[22:15:32] <wjp> but most of U8 uses 16 bit ints
[22:16:08] <nONSENCE> because i've only see 16 registers used
[22:16:15] <nONSENCE> seen
[22:16:22] <nONSENCE> 16bit
[22:17:33] <nONSENCE> well anyways thank you for your time
[22:18:05] <wjp> you're not looking closely enough if you can't find the 32 bit regs :-)
[22:18:09] <wjp> you're welcome
[22:18:23] <wjp> they're not used often, though
[22:18:40] <nONSENCE> i haven't done any searches ^_^ i've only look and the code traced from it loading eusecode.flx
[22:19:37] <nONSENCE> at
[22:20:13] <nONSENCE> sorry about the typos
[22:21:30] <-- Darke has left IRC (Read error: 104 (Connection reset by peer))
[22:37:00] <nONSENCE> did you guys doc ultama8's flx load code?
[22:38:07] --> Darke has joined #pentagram
[22:44:44] <-- nONSENCE has left IRC ()
[23:26:22] <-- Lightkey has left IRC (Read error: 110 (Connection timed out))
[23:27:37] --> Lightkey has joined #pentagram