Related topics

should I install XP 64 bits?
As an exception, if the compiler implements long as two or more 32-bit or longer words, then int32/uint32 should be used instead. It might be useful to allow (or perhaps recommend) that counters and indexes be of type size_t. Another option might be the use of some other C99 standard integer types.

What Assembly Language Should I Use?
The o/s can be booted only in 32 bit if you require it later. via: Edit your boot-file environment variable from the ok prompt. (To get to this prompt, halt your system.) setenv boot-file kernel/unix E280 is 64-bit only machine. You can run 32-bit applications, but can't boot 32-bit kernel.

BC 4.5 --> Win32, why should I use C++ Builder and not MFC
You can (and really shouldn't) under Windows 95 from a 16-bit program. You can't under NT or from a 32-bit program under 95. Regarding DOS and BIOS access... You should probably never directly access MSDOS or BIOS interrupts from a Windows program. Instead, you should use the corresponding Windows API call to

Should I use 16 bit textures or take the texture detail down a ...
In addition, because RST segments may also be received or sent without complete state information, any segment with the RST bit set must use the standard TCP checksum. The option may not be sent in any segment that does not have the SYN bit set. An implementation of TCP which does not support the option should

Should I use 16 bit or 32 bit??
I'd say that as long as 32-bit integers are adquate, stick with default integer. Integer literals just show up in *TOO* many places to stick kind numbers But don't just assume that 32 bits is going to be a better size and therefore you should use it. For particular cases where you need integers bigger than 32

DLL prob ??
The 32 bit memory is located on the accelerator card, and it shows two blocks of memory, which are probably 2 SIMM memory modules. I don't know the configuration of the Zeus accelerator, but it may support either simply adding additional ram, or replacing those already present. Its instructions should cover that.

Answer: ethics of open files
3c509 is a 16-bit card. 3c579 is a 32-bit card. Both are EISA-compatible. 579 is EISA-only. What else, but the slot-connector is 32-bit ? The 3C509 is not only EISA- compatible like *any* ISA card, it supports EISA slot-I/O, which doesn't work in an ISA board. Have I missed something ? Ahhh, I see.

Expand libdisk to use 64bit size/offset
There are 16-bit systems with 32-bit return items; conversely there are 32-bit systems with 16-bit return items, etc. It makes sense that there should also be no loop-sys items left on such a >R stack, but this is not guaranteed. Local variables may be implemented using the return stack; and any other use of

Win 95 + Win 3.11 Possible ????
2) The WDC drive needs its own driver(s) for 32-bit file/disk access in windows; but if the promise and wdc drivers are both used I get a conflict error when loading windows (and then kicked out). You should use the Promise driver. Both drivers have similar functionality but the Promise driver will use controller

101 Things a Loyal Mac Owner Can't Do (TROLL!) (HUMOR!) (TRUTH!)
The question really should be how good is the Delphi 2/1 combo at generating _both_ 16 and 32 bit executables from the same (or virtually the same) code base. Is there a conditional compile and does it allow you to reuse your code with a minimum of "tweaking" between compilers. I don't know the answer to that.

Basic Precision Control Question
In any case, there is still a 64-bit integer available, and that is the type that should be used for INTVAL since it will be optimal for the CPU. **Again, this does not mean If we keep supporting immediate values in the bytestream, the Lx ops would use 2 opcode slots on 32-bit hardware, 1 opcode slot on 64-bit.

Which version of Access should I use?
Besides, 32-bit has a the real debugger <g>. -- Russ Eggen www.radfusion.com "Jim March" <WENATVMPB...@spammotel.com> wrote in message news:ofc9juoojcesv47jt82mc9ffitb17bcu8q@4ax.com... C5.5EE ABC I noticed in the app properties an option to choose between 16 bit and 32 bit. What are the pro's and con's?

ATTN: need help from TOASTER USERS
If one looks at a SISD 32-bit ADD in terms of its logic and a SIMD 4x 8-bit ADD, then you realise that the only appreciable difference is that we don't carry across eight bit boundaries (ie where in a normal ADD, we use ADC-like semantics for all but the first bit to carry the carry bits through the value...we,

GPF's--should I use a DOS compiler?
Let's ignore 64-bit systems ans stick to 32-bit, since X has the CARD32 type. GNUstep Currently: makes use of this field to set window levels and contains at least one kludge to work around the fact that the set of levels implemented is limited. Should: be updated to remove any existing workarounds.

Need help with afio on powerpc
If you cannot see the difference between 16 and 32-bit textures in terms of image quality, set it for 16-bit to reduce the texture load while keeping detail high instead of down notch. The background color depth should be left at 32-bit since this affects the rendering quality of transparency effects a lot.

USE flags for amd64 (running in 32 bit)
It will be under djgpp, so it is 32-bit protected mode. The processor is a 386SXL-25. I assume that it isn't possible to use the system timer - in fact, Should be short and easy. Calibrate that routine using a variety of loop iteration counts, by reading the timer counter's counter before and after,

OS Development: Should I or shouldn'tI?
You must differentiate between RGB (15, 16, 24, 32 bit) and palette (1, 4, 8 bit) Bitmaps. For a fast sequential access to pixels in a RGB bitmap you should use ScanLine. You should convert the bitmap to 32 bit (PixelFormat) for direct compare the values (mask the pixel value with $00FFFFFF).

Amateur question of Color quality...
Should I stick with my 32-bit one right now, or upgrade to 64-bit? (If I have to upgrade, I'm probably switching distros. Recompiling my whole Gentoo system isn't exactly a fun thing to do.) You should probably stay on a 32 bit platform, since many non-free software bits you probably use are unavailable or

Norwegian character
Instead of counting microseconds, use a separate 32 bit counter to count 1/2^32 units of time. With the 18.2.. Hz interrupt rate, during each clock interrupt 235902838 (235902837,62.. rounded up) is added to the phase accumulator. When this accumulator overflows )ie the Carry bit is set), it is time to update the

Bit ordering
Or that win 3.11 could use almost any version of dos(5.0 +) to start with? So, what's your point? 5.Isn't it true that any 32-bit protected mode OS should give you a choice of which dos version you would want without booting to dos_mode? Why should I care? 6.Or that it should NOT boot in real mode on startup?