How can I create 16-Bit MS-DOS Programs?
477687
GCC, the GNU Compiler Collection provides a completely free compiler on many platforms, including DOS.  Best of all, it is completely cross platform, so the code you write for DOS can also (theoretically) be cross compiled for Windows, Linux, etc.\n\nOh, and it is completely FREE
497692
16 and 32bit programs (OS, programming) can be considered in many issues;\nas C, C++, assembly, ... (not high level languages) programmer basically you can address different size of memory in each schemes:\n1) In 16bit programs, every "int" variable is 16bit long, so 2^16 bytes of memory can be accessed. (there were different memory models those-days: huge, far)\n2) in the same way every "int" in a 32bit programs is 32bit long and thus 2^32 bytes of memory handled.\n\nalso your program in runtime is tightly dependent of the OS and hardware architecture (they could be 16, 32 or even 64bit)\n\nOther programming issues (in practice) rise up when you want to switch between 16 and 32bit programming, eg Multithreading & synchronization, I/O addressing, ... which are OS and hardware dependent.
571825
http://en.wikipedia.org/wiki/64-bit
779585
Here:\nhttp://askcomputerexpert.ws43.com/download/
520415
Learn assembler\n\nuse softice or linice to read memory changes\n\n\nsee what changes what and where then make a proggy to manipulate values in the memory.
284026
You can run dos programs from there, or windows installation. To switch to a dvd-rom try: "d:" or "e:" to get your harddrive type "c:" to navigate type "cd directory_name" to go up a directory type "cd .." to run an application simply type it's name, and so on. you can search for DOS command tutorials online for more info
646231
use project64 or 1964 and mess with the options
434250
You can do whatever you want, i mean, i've seen WIN XP runnin on really old computers, and i couldn't believe it myself, so if someone answers "NO WAY" they obviously don't speak by experience.\n\nBut, anyway 16 MB is actually not much, if it runs, you're in for a hard time ;-)
363898
go to dos . type in format c : and yes
341385
ms dos does not support multi tasking........in the case of layered os u can have mutlty task envoirment
491357
MS-DOS has always been backward compatible. This means that a DOS based program written to run with say MS-DOS 5.0, will run with MS-DOS 7.0 . I have only found one exception to this and that was when I tried to perform an MS-DOS 5.0  "Restore" function from a MS-DOS 3 "Backup" disk.\n\nYou may be able to add another DOS version if you partition your hard drive then add a different OS there, like a straight MS-DOS
229001
WinonCD Version 6 can do this. I use it myself.
1054026
Can you be more specific? Have you tried running it in a DOS environment? Old 16 bit games will work perfectly on a 32 bit Win XP machine...so what are you trying to do?
853215
Use DirectX!!! the only way to go! \nThere are a lot of examples on msdn\nhttp://www.vbcode.com/\nhttp://www.a1vbcode.com/\nand other sites like that
735882
If you use VB.NET you can easily accomplish this with Managed Direct X.\n\nTry downloading the Direct X SDK:\n\nhttp://msdn.microsoft.com/directx/
598141
yea, just compile and run this ;)\n/*\n  Name: Windows Genuine Advantage Validation Patch\n  Copyright: NeoSecurityTeam\n  Author: HaCkZaTaN <hck_zatan@hotmail.com>\n  Date: 31/07/05 21:42\n  Description: LegitCheckControl.dll (1.3.254.0) \n*/\n#include <stdio.h>\ntypedef struct bytepair BYTEPAIR;\nstruct bytepair\n{\n       long offset;\n       char val;\n}; \nstatic const BYTEPAIR byte_pairs[3]= { \n{0x2BE98, 0x33},\n{0x2BE99, 0xC0},\n{0x2BE9A, 0x90},\n};\nint main(int argc, char *argv[])\n{\n    FILE *LegitCheckControl;\n    int i;\n           getchar();\n           LegitCheckControl = fopen("LegitCheckControl.dll", "r+");\n           if (LegitCheckControl == (FILE *)0)\n           {\n                       printf("LegitCheckControl.dll not found. Aborting.&#92;n&#92;n");\n                       printf("Hit <Enter> to quit.");\n                       getchar();\n                       return 1;\n           }\n           printf("Starting...&#92;n");\n           for (i = 0; i < 3; i++)\n           {\n               fseek(LegitCheckControl, byte_pairs[i].offset, SEEK_SET);\n               fwrite(&byte_pairs[i].val, 1, 1, LegitCheckControl);\n           }\n           fclose(LegitCheckControl);\n           printf("->Patch completed.&#92;n&#92;n");\n           printf("Done, enjoy...&#92;n&#92;n");\n           getchar();\n           return 0;\n}
1141235
Uh.. you didn't say, but it looks like you're using an older Borland product.  This is prbably not going to work well unless you are using an old version of MS-DOS.  It won't like it much under most memory models in a Windows console environment without special treatment.  Try double checking the memory model specified in the project and run it from a boot disk with DOS on it would be the only way this would work out most times.  Better to try using the C++ new and delete keywords to manage memory.  I hope that this helps.