MrBrant

2 words: Die Hard

I haven't had a problem - seems like I just split the weaves a bit, not breaking any threads. YMMV If you're in doubt, have a rigger look at it (preferably a master rigger, or at least one who had alot of textile knoweledge)

When you're putting the pin in the keeper, make sure you put some slack into the riser, then insert it straight. If you try to put it in at an angle, and kind of "lever" it in, it'll go trough the riser. I was doing that when I first got mine, without thinking, and had the same thing happen (oops.. ). go me......

Depends on your processor. Not on a PowerPC, for example. Good catch. I apologize for the generalization. As an egotistical bastard, I should have said "My embedded world" - which mainly means 8-bit micro's - predominantly Microchip. As you say, that depends on your compiler. The spec only mandates that a long int is at least as large as an int. long is a synonym for long int. Microsoft Visual C++ 2002, for example, uses 4 bytes for both an int and a long. Ah, now that is interesting. I didn't know that. I wonder if it's the same for the ANSI C standard. They're fundamentally different. One is a long integer and one is a double precision floating-point number. Unless the C++ spec is being ignored in your space (and that's quite possible), a double must be a floating point number. More here. C may be different - I don't know what's mandated by the spec wrt data types. Hummmm. it appears that I may have to retract a good portion of my last statements. As I said earlier, floating point operations can be pretty impractical for most of my stuff - It appears that I have slacked off learning (well, remembering anyway ) most of that "useless" crap. Thanks for enlightening me (and motivating me to do my own searching ). Sorry to everybody else for some of the misleading info in my last post.

In the embedded world, an int is usually a 16 bit number. (integer) So, if you need to store a number larger than 65535, (or, during the course of a calculation, your result at any stage will exceed that) you'll need to use a Long. (i think sometimes called a double - I always just use long). A long can usually either be 24bits (16.7 million), or 32 bits (4 billion) - depending on your compiler and the options you set in your preprocessor directives. All of these can be unsigned (positive only) as the examples given above, or signed (+ or -). For signed variables, basically divide your range by 2. (and if memory serves me right, the negative number will be 1 number "longer" than the positive number. i.e. a signed INT is -32768 to +32767 I think) Somebody mentioned doubles as floating point number - I don't think this is the case - in the embedded world anyway. A "float" is usually the only data type that is floating-point - and tend to be 32 bit I believe - I'd have to check on that one. I don't usually use them - takes too much memory and time (instruction cycles). Ever try to do floating point division running at 32kHz? I'm not sure how any of that translates to the C++ computer world. As for your extra brackets. As was mentioned - it's a good habit to get into. Some quasi-C compilers might not follow the order of operations. They also help to make your expressions clearer for reading - so I would agree with your answer. (even if it wasn't the one they were looking for)

I didn't like my 28" PC, so I had a 33" one made up. I've been extremely pleased with it. I do 1-second delays from the 182, as well as terminal openings and it works great! - best PC I've ever had. I jump a Samurai, and it opens great every time (so far ). With the exception of my locking stows, all the others are nice and loose too. (not that I advise this, but it works for me). I ordered the 33 because I really didn't like to be able to feel each line stow come undone before I got to line stretch when dumping at terminal! The old 28" also gave me a couple hesitations on the shorter (

Night jumps into the forrest, then subsequent ATV rescues?

If you're refering to the series of short beeps that gets faster and faster until your target altitude - yes the Neptune has that now. (in the new v3.0 firmware). I think they call it the "swoop coridoor". The only downside is that you cannot yet use the new firmware with the Wave.

The answer is "all of the above"

bribe them with beer

Don't forget to add some seam allowance. Uh, are canopies cut and sewn together without a seam allowance these days? Mark I think what was meant is that if you scale down a canopy, it will shrink the seam allowances. These will have to be re-increased since you'll still need the same allowance for your seams, whether the canopy itself is smaller or not.

Yeah, but what did you score?

It always suprised me to hear turbine babies sound upset at that idea. Comeon - just pull off the step!!

Could you elaborate for the purpose of discussion?

yeah, the 2 inch difference was a little surprising to me too.

So, I was thinking the other day (uh oh! ) about cutaway cable timing. Conventional wisdom dictates that we trim cables so that the NON-rsl side releases first. That way, if somebody only cuts away 1 riser, the RSL will not deploy the reserve into a still-attached main. The recent Chicagoland incident got me thinking. It was speculated that the student cut away only a single riser, then deployed the reserve. If a rig was equipped with a Collin's lanyard - would it not make sense to cut away the RSL side first (or even just at the same time). This way, if the jumper only cuts away 1 riser before deploying the reserve, the Coliins lanyard would cut away the other riser before the reserve has a chance to inflate. This, of course, assumes the gear owner (or maintainer) is head's up enough to correctly route the cutaway cable.... Comments? For reference, from the Vector 3 manual:

Nope, just the Seagrams distillery!!

Probably PIM 4 or something. Might be somewhere else, but the PIMs are probably a good place to start...

Traffic. Lots and lots of traffic. And smog....

They were sent out on the CSPA e-mail chatlist. I've ripped out the CP scores from the rest of them (the original file was 1.2 MB ). Below in 3 parts:

I read one a while ago - I can't remember where, so I can't quote its source, but: "Tis better to have jumped and bounced, than never to have jumped at all"

never heard of them, but I can guarentee that if you did find them, they would be MUCH more expensive than just buying some THT resistors Digikey will have them to you the next moring, as long as you order before 8PM.

I love the last paragraph of that article: Wait a sec. Run tap water through a filter, sell it for $2 a 600 mL bottle, and NOT make a lot of profit? (sorry, I guess it's usually only $1.75 for 600 mL....)

You can go earthbouncing while skydiving right now, without all that balloon crap.....................usually only once though

floatation gear for 4 feet of water???