What operating system are you using? It's different for each one. And what API are you using? It is also different for each one of those.
I'm having some difficulty working out what you're talking about. For starters C does not have a "for each" loop. Did you post this in the wrong...
>>my problem is if it more than two decimal value i have to change every time the 10 to 100 Why is that a problem? However you do it, you're...
Not too difficult, if they've taught you so far: - how to declare a string variable; - how to read from the console into a string variable (scanf,...
There's no single function that'll do this for you. You'll have to define C as int[3][3] then copy the members of A and B over one by one.
No, you haven't just misspelled. The assignment is not asking you to copy a single byte.
>>Copying the 4th address' value of the 1st chip to DL You need to re-read the assignment.
Looks OK. The only thing I would check if you're using the 16-bit mov[bx] (because you specified 0000h, not 00h), this writes 2 bytes: one to...
>>I am using fgets >>scanf("%d",&n); Look again. >>to input the number i have to use scanf Why? There is a function to clear stdin but I can't...
>>(Physical Address)=(Logical Address)*10h+(Offset) Logical Address is also sometimes known as a segment. Might be easier to think of in those...
There's an error on line 10. Does it compile OK? If not, what errors do you get? What output do you get when you run the program? Try adding...
Where exactly are you stuck? Do you understand the question? Have you figured out what value(s) of A16-A19 you need to enable the chip? If there...
scanf is crap, use fgets instead. Read the input into a string, then use atoi to convert that string to a number (or sscanf if you're a glutton...
What's it doing wrong? What input do you give it? What output do you expect? What output did you get? Or is it a compile-time problem rather...
In what way exactly doesn't it work?
What exactly goes wrong? Does the code compile OK, or do you get any errors? If you get errors, what are they? If it compiles OK, what goes wrong...
Are you sure the file wasn't created at all? It's likely to have been created where you don't expect it. Try "dir/s c:\reports.log" and repeat...
Change while to if and see if that fixes it.
Hobbyist is correct - the behaviour is UNDEFINED. All arguments of the form "my compiler does X therefore you are wrong" are nonsense....
When you don't prototype a function, C sometimes (and in your case does) give you an "automatic" prototype, which is "int print();" You then go...
Separate names with a comma.
