rosapps/games/ArchBlackmann/tech.txt

   1 What do you think I am, your personal tech support?
   2 You *know* a FAST_MUTEX is non-re-entrant, right?
   3 The answer to that is so simple, I'm not going to waste my time telling you.
   4 Well, of course... if you're not below DISPATCH_LEVEL, ros is gonna explode on ya.
   5 I don't think that functionality has been implemented, yet.
   6 What do you mean it crashed? It can't crash there!
   7 Wow. That's a new one.
   8 Ask Filip, I bet he knows.. he knows everything...
   9 When's the last time you rebuilt?
  10 Have you tried a make clean?
  11 Is it plugged in?
  12 Well it works on *my* system :P
  13 Well don't do that, and you won't have that problem.
  14 Didn't we already fix that?
  15 Well... I don't know.. I just have that code disabled in my tree.
  16 Try surrounding it with parenthesis.
  17 Don't you know going around dereferncing null pointers all day can be hazardous to your health?
  18 Well, duh!
  19 There's a bit in cr3 for problems like that.
  20 Just add a field to the PEB to keep track of it!
  21 Don't worry about it... the garbage collector in the kernel will clean it up for you.
  22 Did I do that?
  23 Yes, I think I've seen that bug before... no... that was another program.
  24 I could tell you, but then I'd have to unlink() you.
  25 Well if you'd get some sleep, maybe you'd figure it out... not all of us can keep the hours arty can...
  26 You did what? Uh oh... that can't be good.
  27 Well... I could tell you, but the answer's pretty complicated. Why don't you wait to read about it in the book I'm writing.
  28 Yeah, that's happened to me, before, too. All you have to do is wrap it in an SEH block and forget about it.
  29 ASSERT is your friend!
  30 I dunno.. but I bet GvG could find it for you.
  31 I hereby declare that code is perfect. Your problem must be elsewhere.
  32 I wrote that code... it must be perfect.
  33 maybe I broke it in my last commit. Maybe I did it on purpose...
  34 Have you tried debugging it? I got a can of Raid...
  35 Try queueing a work item...
  36 My DPC fell in love with an APC in the scheduler, and the code has been hell since...
  37 Maybe the PEB is getting corrupted. Try allocating a new PEB and overwriting the old one. That's what I did last time I had a bug like that.
  38 Hmm.. that seems to have been introduced by my last commit... I bet CVS mixed up the bits during the commit.
  39 It can't possibly be my fault, so I don't care.
  40 I'm not experiencing that problem, perhaps it's all in your mind.
  41 Well... like a good friend of mine said... "Don't Panic!"
  42 It just shows you how far ReactOS has come along! A year ago a bug like that wouldn't have even been possible!
  43 Just surround the code with an #if 0/#endif block, it solves all my problems!
  44 You know.. if kjk_hyperion had implemented lsa for us, we wouldn't be having this problem.
  45 I say we move on to the next function, since we can't seem to figure this one out.
  46 Well, sure, that would have been my first guess, too.... TEN YEARS AGO :p
  47 yup, that sounds like a problem.
  48 If I wanted to talk about VB, I'd go bug Alex...
  49 ask arty
  50 Thank you for that amazingly keen insight, Commander Obvious.
  51 I dont know about that, but I just fixed a problem in MSAFD for Arty.
  52 How should I know? I'm still trying to figure out this main() thing... ooh! wanna see what I did in the kernel?
  53 lol!
  54 *wink*