Level 21

Any other hint on how to interpret the l..s ? I seem to be stuck here.
I get the following sequence: [6,3], [10,3],[6,8] ... is this correct?

Thanks,

Peter.

OK, I've cracked it. For clues on the first part, look at my earlier post. For the l__s - you've done this before, but slightly differently.

This level's got me stuck!!
I get the (6,3), (10,3), (6,8) , .. sequence mentionned by Peter above
And I can find the wrong HIJJIIHIJJ answer hinted at by Uncle Timmy.
But I can't seem to find anything useful.
Should I be looking at my l__s graphically or textually? - I've tried both without much sucess Sad(
And I haven't a clue what the game is!!

Well I've *finally* got it. ouff!
As has been said here something similar has been done before but I was thinking of something else. I tried around 20 ways of interpreting the l__s before getting it.

Maybe I am indeed an idiot but I think this level needs an extra hint for the l__s interpretation phase - the last time you did it it was more obvious due to the mixed types.
How about "bees are black..."

I've found the (6.3) sequence and I'm stuck trying to get some meaning out of it. Maybe a hint as to *where* I've seen it before? I'd go back through all the solutions, but I foolishly didn't save them and I've lost my wiki cookie over the weekend.

By the way, the repeating 7 byte pattern was meaningful to me - it's what set me on the right track for finding the sequence.

Maybe a hint as to *where* I've seen it before?

which hill...?

What's the length of sequence? I get a list of 6 tuples, is it large enough?

And I get a "8086 relxxxxxble (Microsoft)". Is it useful?

after re-reading readme.txt, i realize the answers are both no.

still stuck with package.pack

found 6 times 7 at the beginning with meaningful bytes but if i split it, each new part fails to come out (z-errorz), same if i only use one of the 6 with the rest.

any more hints for the very first step here?

Split? nah don't do that. Go back and read jtauber's hints

i yield to despair.

could somebody PM me the first step of un-pack-ing?

ashamed-ly yrs

EDIT: got it, I was thinking along the right lines all the time... just too complicated. just had to unwrap.

I solved this level two days ago and I have to say that I was confused too when I got to the l__s part. Even reading the hints wasn't that helpful as I only understood their meanings after I eventually solved it. So here's what I can add without giving out too much: once you have the sequence that people have written about, you have to do something that you have done before, as people have also hinted - but there are only a couple of things you could do with it that you have done before. If that still doesn't help you, you may be missing some l__ information. Read mfuzzey's message as it can be helpful too.

[...] So here's what I can add without giving out too much: once you have the sequence that people have written about, you have to do something that you have done before [...]

I've reread all the past solutions but I couldn't find something aplicable. I tried to interpret it graphically (in 2 or 3 ways), and textually. It's a weird sequence to convert to anything because the numbers are fairly low and don't vary much. It really does not seem to contain anything useful.

I'm starting to get discouraged... Can someone post another hint on what to do with the mentioned sequence?

EDIT: Got it. It took me so long because I was thinking in terms of high res graphics...

And I get a "8086 relxxxxxble (Microsoft)". Is it useful?

I'm exactly at same point...

I don't know why, but I get the felling that I'm missing something... any enlightment?

And I get a "8086 relxxxxxble (Microsoft)". Is it useful?

I'm exactly at same point...

I don't know why, but I get the felling that I'm missing something... any enlightment?

file's got the wrong end of the stick. When I did this level, this result was a sign that I was doing things backwards.

Don't be surprised if file identifies some things as "data"; it's expecting a header first. However, the Python module's from 1950, and the header was introduced in 1952. The data does still have a (short) magic at the start, though.

Am I giving too much away?

I'm affraid I need some help with this level...

I'm unable to find the correct sequence... any help on that? I do know what the 'similar' level is, and what module is needed for to make the sequence useful...

What I (so far) failed to understand is what is meant by: 'period 7 at the start' (or what is intresting about it)...

The period 7 thing is not actually important. All that should concern you at first is that you have a file with an extension that should be suggestive as to what you need to do with it. The trick is, finding the right module(s) That's step one.

After you done that, step two should be fairly obvious, although you will probably have to re-do step one

Depending on how you look at it, there is a step three also