To a person:
1. It does work correctly. Check out Micalson eye candy whore entry for 4E3.
2. I understnad that. But I'm not doing any of that becasue I want it to run on slow comps. I'm not goign to be doing any float point ops in my prog becasue they are slow, and I will avoid long operations.
3. I understand that, I just wanted to make it clear that everyhting will be sotred inthe COM file and will be under 4K.
4. RDTSC is not such a terrible way to generate ranodm numbers. It depends on when the program starts and the speed of the persons computer since I will be wait for a certain number of timer tick before I do ceratin animations. Also, if the person runs it with windows running, no one can tell you how many CPU cycles windows and other progs steal here and there. I am not lazy, I'm not. I don't know why you would say that. I have clearly stated that I have looked at others. Now as for looking different, thats a good thing and I don't know how a rain can look really bad
.
5. I will be doing sound but thats not the point of the post.
6. Thankyou, I think I might try that
.
7. Your right and I knew that but I won't be allocating anything. I will basically have everything in my 64K segment.
With all that said, I think you should check out Michalsons eye candy whore entry (link anyone?). Besides, I have a really neat way of conveying my character and my scene. Also, if you think I don't have the skills, you are sadly mistaken. I optimized Michalson's 999 byte entry down to 972 bytes on my comp.
Also good point, I will scratch the whole call thing, and just put an rdtsc where I need it. I am just trying to get some basic routines down right now. You know that people can make mistakes right?
Now for blueEbola. I got mad becasue people weren't really answering my original post. Anyway, it would be a seed generator if I was using the edx:eax pair but i'm only using ax so it continually wraps around and is actually pretty good.
[edited by - Puzzler183 on August 13, 2002 8:07:04 PM]