Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Is Paradox 16 bit or 32 bit?

10 views
Skip to first unread message

Ken Loomis

unread,
Sep 30, 2004, 10:57:48 PM9/30/04
to corel.wpoffice.paradox9

A customer with perhaps too much time on his hands has measured
Paradox and found that Paradox, the application, is 32bit, but the
fdls are 16bit. He says that putting 16bit bytes into 32bit spaces
can cause instability. Is he right?

Ken

Jeff Shoaf

unread,
Oct 1, 2004, 4:52:15 PM10/1/04
to corel.wpoffice.paradox9

My understanding is that the forms'headers say that the files are 16 bit
dlls, but that they really aren't.

Bertil Isberg

unread,
Oct 1, 2004, 5:18:48 PM10/1/04
to corel.wpoffice.paradox9

Jeff

I recalled Dan Alder once explained this as: Forms have the structure of a
16 bits dll, but they are not dlls at all.

--
Bertil Isberg - CTECH
Paradox buglist:
online: http://w1.826.comhem.se/~u82608896/
FAQ newsgroup: corel.wpoffice.paradox-faq

Ken Loomis

unread,
Oct 1, 2004, 7:22:16 PM10/1/04
to corel.wpoffice.paradox9

On Fri, 1 Oct 2004 23:18:48 +0200, "Bertil Isberg"
<bertil.isberg@NOcomhemSPAMdotse> wrote:

>
>Jeff
>
>I recalled Dan Alder once explained this as: Forms have the structure of a
>16 bits dll, but they are not dlls at all.

And are they 16 or 32 bits in size?

KEn


Bertil Isberg

unread,
Oct 2, 2004, 5:47:37 AM10/2/04
to corel.wpoffice.paradox9

Ken

<<
And are they 16 or 32 bits in size?
>>

I don't understand what that means, and even if I did, I have no answer.

Jeff Shoaf

unread,
Oct 2, 2004, 9:53:54 AM10/2/04
to corel.wpoffice.paradox9

I don't believe that has any meaning in this context. It's like asking
if a text file is 16 or 32 bits in size. As far as I know, that only has
real meaning when discussing executable programs and that depends on
whether the compiler generates 16 bit or 32 bit executables. In that
context, your client is correct to some extent since 16 bit machine code
executables don't take advantage of the full width of the processor
registers and 32 bit commands on a 32 bit processor. He's also probably
remembering early tests that demonstrated that 16 bit Windows programs
ran slower on Win95 thatn they did on Windows 3.1.

Other than that, I doubt any of us understand enough about how forms,
libraries, scripts, etc. are actually ran under Paradox to say much more.

Where's Paul Cronk when we need him?

Bertil Isberg

unread,
Oct 2, 2004, 4:00:19 PM10/2/04
to corel.wpoffice.paradox9

Jeff

<<
Where's Paul Cronk when we need him?
>>

As forms created in Paradox 7 (Win95) can be run in P5 (Win31), there can't
be any fundamental changes in the structure of the fsl format.

Jeff Shoaf

unread,
Oct 2, 2004, 6:30:32 PM10/2/04
to corel.wpoffice.paradox9

And there was a 16-bit version of P7...

Kasey Chang (send reply to HOTMAIL.COM instead!)

unread,
Oct 3, 2004, 1:33:29 AM10/3/04
to corel.wpoffice.paradox9

"Ken Loomis" <kloomis@it-re--.com> wrote in message
news:qmhpl0dv82alcmf58...@4ax.com...

He's wrong. Alignment may slow down the PC slightly and wastes
memory space, but cause instability? Only if the OS is a piece of
junk to start with.

--KC

Jeff Shoaf

unread,
Oct 3, 2004, 9:29:49 AM10/3/04
to corel.wpoffice.paradox9

We are talking Windows here!

Sorry, couldn't resist...

0 new messages