>--
>Richard B. Hall, Software Design Team (ED14)
>544-3789 (voice)
>544-8480 (fax)
>richard.b.h...@msfc.nasa.gov

> Richard,

> Of course! Builder can only produce programs that run under the Win32
> API and one of the major features of Windows NT is that it implements
> the full Win32 API.

> FWIW Builder created applications can also usually run under Win9x
> because those versions implement most of the Win32 API.

> Similarly Builder programs can run under Win2K. As far as we can tell
> any program that runs under WinNT will run under Win2K.

> Having said all that it is possible to develop an application which
> will only run on Win9x or WinNT but not both. Usually this will be
> because of something you are choosing to do (such as calling a
> function that Win9x doesn't implement or allocating too many
> resources for Win9x or performing direct hardware access [forbidden
> under NT]).

> The bottom line is that Builder was designed to create programs for
> Win32 and that means WinNT, Win9x and Win2K.

> Andrue Cope
> [Bicester, UK]

> Richard,

> > I hope you are right about this

> I am <s>.

> > I got a small error box that told me
> > bascially nothing about what was wrong. Got any ideas?

> Without knowing what the message was I don't stand much chance of
> answering that do I <S>?

> As I said in my previous posting it is possible for *you* to create a
> program which can't run under NT4. These are two "off the top of my
> head" ways how you could do this:

>   1.Develop a program that uses DirectX 4 or higher.
>   NT4 doesn't support this.

>   2.Develop a program which directly accesses or manipulates hardware
> I/O ports. NT4 (and FWIW Win2K) don't allow this.

> Neither of these are Builder faults - they are both caused by the
> programmer. The first is the result of using an API call which is not
> supported on all versions of Windows. The second is the result of
> obsolete and (IMHO) bad programming practice.

> The bottom line is that Builder creates Win32 programs it's just that
> "Win32" is a bit of a movable feast and different versions of Windows
> support different bits of it in different ways.

> Andrue Cope
> [Bicester, UK]

>> fopen, fgets, fputs, and fclose

> These are part of the C++ language standard and work fine under

> Builder. The only problems are that you can't easily use them to

> access files bigger than 2GB but that shouldn't cause AVs - it just

> means your seeks() don't go where you expect them to <s>.

> Andrue Cope

> [Bicester, UK]

> Richard,

> > fopen, fgets, fputs, and fclose

> These are part of the C++ language standard and work fine under
> Builder. The only problems are that you can't easily use them to
> access files bigger than 2GB but that shouldn't cause AVs - it just
> means your seeks() don't go where you expect them to <s>.