Code Puzzle

[MarillionFan]

I must have missed this, but i am assuming we had to rearrange the following words into a sentence.

Loser AtW A Is Churchill Bigger Than

Where

First statement is

Bigger Loser than Everyone else.

Bit tricky this, but I reckon you guys can work it out.

[d000hg]

Looks like Churchy made an arse of himself with some poor code from the 1980's.

Nope, I thought I'd have a go at posting something that some people may enjoy playing with hence the title of the post.

AtW decided to be a twat and spoil it.

So you got in a strop and deleted it...

[Churchill]

So you got in a strop and deleted it...

Yep, can't be arsed.

[MarillionFan]

So you got in a strop and deleted it...

Yep, can't be arsed.

Good. Another 14000 more to go and you should be done.

[AtW]

Yep, can't be arsed.

I've got it saved into a file though - will post tomorrow in General, I am sure that thread will get good response

[Churchill]

I've got it saved into a file though - will post tomorrow in General, I am sure that thread will get good response

Do what you want. You spoiled a harmless bit of fun by being a cock.

[AtW]

You spoiled a harmless bit of fun by being a cock.

I've actually read your code, made some improvements and noted some serious flaws - one of which was that it would not run on Win XP 64-bit since it has got no debug command!

FFS, what fun were you expecting people to have with poorly written 16-bit DOS assembly code??!?!


More to the point: are you gonna bark all day, little doggy, or are you gonna bite?

[d000hg]

Do what you want. You spoiled a harmless bit of fun by being a cock.

Without having seen the code, I don't see how AtW spoiled it with his comments. You know he'll post it, so why not reinstate it and then ignore the thread?

[AtW]

Without having seen the code, I don't see how AtW spoiled it with his comments. You know he'll post it, so why not reinstate it and then ignore the thread?

The idea was (probably) that nobody would recognise 16-bit DOS code with int 21 interrupt called to exit program. It was very poorly optimised, but I suppose that was the idea, however it was totally ruined by usage of absolute jump addresses, I mean FFS, thats hard enough to program in low level assembly language without having to calculate manually exact offsets for jumps, FFS - I did assembly from back 1992 - that's nearly 20 years ago, and I've never seen anyone using absolute addresses, it's totally retarded waste of programmers time.

This "debug" command has always been a joke - TASM FTW

P.S. Last time I did assembly was about this time last year using Intel C/C++ inline 64-bit assembly, you can't beat that...

[Churchill]

I've actually read your code, made some improvements and noted some serious flaws - one of which was that it would not run on Win XP 64-bit since it has got no debug command!

FFS, what fun were you expecting people to have with poorly written 16-bit DOS assembly code??!?!

If you read the original post properly you will have seen that one of the requirements was that it should be able to be entered via debug.

Also that if it was to be entered via a hex listing for example in the case of 386 code that the source should also be supplied.

You were a cock and spoiled a harmless piece of fun.