You thought that memset would put an integer 5 into each element of your array, but that isn't how it works. It is putting a 5 into each byte.

5*256*256*256 + 5*256*256 + 5*256 + 5*1 = 84215045

Someone who ignores sociopaths, once he knows who they are.

Because the OP created the arrays without a size.

You're the first one in this thread to be rude. Why drive off responders?

Well, just my two cents, I only lurk in these forums because I otherwise don't get enough practice at C, which will soon be a significant part of my job for the first time in many years.

First,...

I missed the part about 80186, so it is probably DOS. If they type the number, getting it from standard input might be easiest, and ASCII/ANSI characters will be the input.

Here's some help on...

How will the user enter the number?
Will you get it in ASCII?
What operating system?

Try: struct poly {
int len;
char *name;
int arr[];
};

BTW, your structure won't alway take up the same number of bytes. That might be fine for a particular situation.

See if this helps:
http://www.arl.wustl.edu/~lockwood/class/ece291/books/CH20/CH20-3.html

You just use the command string as the argument, so (in unix) to delete "/mypath/myfile", you do:
system("/usr/bin/rm /mypath/myfile");
I tend to use the path when I know it, but:
system("rm...

Aha! We (other posters) made assumptions about the code, because we had only a snippet. Looking back at the error received by the original poster, I'd say Aia has hit the nail on the head.

There are a million ways to do anything in C, and I'm glad someone got it to compile. Personally, rather than:
struct RECORD *head=(struct RECORD*)malloc(sizeof(struct RECORD));
I would have done...

The C compiler will cause the executable to save and restore certain registers before and after a call, but not others, so the point of this exercise must be to get you thinking along those lines. ...

Ha! Isn't funny how we overlook the obvious? When you pointed DX at 0002, you forgot that your program actually loads at 0100. Just change
MOV DX,0002
to
MOV DX,0102

BTW, here's how...

Hmmm... not a fasm user, so just some other observations. No org statement, or use 16 statement. Thought fasm syntax was a dollar symbol before hex numbers, but that may be optional. Some assemblers...

Strange.

Presumably DOS, or you'd get nothing.

I notice the lack of a return statement. The control chars may appear at the beginning of the line, but that doesn't mean they were printed...

I don't have an assembler on this box, so I wrote this in the old MS-DOS debug command. That's why it looks a little funny, isn't optimal, whatever, but hey, we're just making the best of a bad...

A few items:

You XOR a DWORD with 0ffh, but you need to XOR each byte in the buffer, not some randomly chosen DWORD in memory.

So, point something at your buffer and XOR byte-wise for the...

Goto http://cis.ysu.edu/~rick/class3714/ch5.html and search for OpenInputFile and you will find the three functions documented near one another.

I see that you need to use EAX after that first...

Ummm.... actually do your assignment for you? How about a little effort... or at least some idea why you are so completely stumped that you haven't generated any code.

Those functions could be in some library that I don't have, but perhaps writing those functions is the REAL assignment.

Could you give us some idea what assembler you use, on what operating...

I just can't bear the thought of deciphering what your variables represent. You need meaningful variable names.

Also, indent your control structures so that you know what is nested. (You may...

If memory serves, it could be any even address on the 16 bit processors. Of course, if you're running 16 bit code on a 32 bit processor, go with divisible by four.

You need a terminating null character, \0. You could add it any number of ways. If you just change "for(i=0; i<n2; i++)" so that "i" goes from 0 to "n2" then it will copy the null at the end of the...

You never initialize time1, time2, or time3. Perhaps they have random garbage that isn't less than 1. But then why print zero? I don't know, but I like to test values AFTER giving them a value. ...

I should also point out that having the function call itself repeatedly until you get proper user input is dangerous. If you really had wanted to force good input, then a while loop would be...

You are correctly putting a value in seed, but your function refuses to end until you get a good value. The caller, getInput(), never checks the result (which will always be true, as presently...

You can be sure that you are expected to do the if/else inside the function that gets the data. That is fairly standard practice, as it allows you to reuse the function to do validation in other...

Thanks, NotNull, I overlooked the single-quotes.

So that let's us say exactly how the processor perceives this code, and having "defined" the variable within the code actually looks like:
mov...

There must be no stack segment, that is the biggest problem I remember having with exe2bin.

You will still use the x86 instructions on the other processors that you mentioned. So, those books may be useful. The real question for an x86 book is what operating system the examples were...

deostroll,

I can see that you're doing this in DOS.

If your execution actually begins at "mov ax,3", then the "var db '$'" is executed next. $ is just a counter of the current program...

My first thought was "Well, you're probably rebooting because of a triple-fault. Have you defined your interrupt descriptor table (IDT)?"

But now I really see the 7c00, and suppose you're writing...

Looked at Fine's stuff, good in itself, doesn't help you, though.

Here's from http://en.wikipedia.org/wiki/Protected_mode


; set PE bit
mov eax, cr0
or eax, 1
mov cr0, eax

As I recall, we sometimes needed to specify the jump to protected mode in a DB statement. Google for John Fine, he has something to get you over that problem, I think.