Rick Hoffman wrote:

if the context is consistent, don't discount the possibility that something is
hosed..


offhand, I don't know where you got that one from.. I don't know of any threads
where we've ever told people to mess with config, autoexec, or any shortcut
settings..


that's a good way to get locked up coming back from the "suspend".. uncheck that
one.. and several threads have said that the "powersave" machine "suspend"can
cause problems, too..


--

Steve Green - Diamond Software Group, Inc - Waldorf Maryland USA
Corel CTech Paradox - http://www.diamondsg.com - Support/Downloads/Links
---------------------------------------------------------------------------------

Do you need a Sanity Check? http://www.diamondsg.com/sanity.htm
Upgrade/Downgrade versions? http://www.diamondsg.com/upgrade.htm
-------------------------------------------------------------------------

Well, Rick, I'm curious what memory settings you are talking about!
I have looked everywhere for memory settings and can't find them!
What are you refering to? How are you getting there?

This is what my machine does if I invoke the command prompt and type mem :

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Dave>mem

655360 bytes total conventional memory
655360 bytes available to MS-DOS
633984 largest executable program size

1048576 bytes total contiguous extended memory
0 bytes available contiguous extended memory
941056 bytes available XMS memory
MS-DOS resident in High Memory Area



REM Install CD ROM extensions
lh %SystemRoot%\system32\mscdexnt.exe

REM Install network redirector (load before dosx.exe)
lh %SystemRoot%\system32\redir

REM Install DPMI support
lh %SystemRoot%\system32\dosx

That last line above would be important to Paradox..... and if the redir
thing isn't there I think you'll be in deep yogurt
The only lines in my config.nt that do anything are:

dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=40

is..
Is your CPU overheating?
When it "locks up" is Windows still running and usable?
Are you running it full screen or in a window... I think in a window is
better...

tutility is worthless, did you rebuild and then restructure?
Or just restructure? Be sure to backup before you rebuild or resructure...

I hate problems like you are experiencing...

Dave

the .pif thee .pif ! THE .pif
delete the @#^() .pif
Unless you use that to start Paradox, which you sure as shoot shouldn't, it
is just taking up disk space!
Unless, of course, you use Windows 3 ! Now there was an "Operating System" !
;-)
Dave
"Lorrin Moore" <mSoPoArMe (AT) 0S1PdAeMsSiPgAnM (DOT) com> wrote

You can delete pif all you want. It will be recreated in same directory
as the program, or the C:\windows\pif directory.

Dave Porter wrote...
--
Lorrin Moore (filter the spam to reply)
______________________________________
news://pnews.thedbcommunity.com
http://www.thedbcommunity.com/support/
for Paradox® support
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯

The saga continues....I deleted all .pif files. I had tried running Paradox
with cmd.exe and command.com (that was the icon with memory settings I tried
adjusting). I was getting a strange error message with cmd.exe and that
went away when I deleted the .pif files but the application still locked up.
I set up an icon to point directly to the Paradox startup batch file which
didn't make any difference (I didn't touch the icon/property defaults). I
restructured all the tables to no avail. There are no other problems with
this Compaq laptop computer. It's only DOS Paradox.

The biggest hint is that the problem is truly intermittent. I've been
working on a new section of code so I thought that could be the problem but
it sometimes works perfectly. When it locks up it sometimes deletes tables
in the current directory which I can easily restore. If I restore the
tables, delete the .lck files, and cross my fingers it often gets through
the report section I'm working on successfully. The next time I run it is
bound to freeze up but often at different parts of the code. I've never
seen anything quite like it. I HATE intermittent problems! I'm running out
of creative ideas but I keep trying. I usually can fix these kinds of
problems on my own. It's a strange one. I keep wondering if it's memory
related?!?

I never had a problem like this with NT or 2000 Pro. I've tried NT and 2000
compatibility mode and it doesn't seem to make a difference.

Any new thoughts are welcome.




"Steven Green" <greens (AT) diamondsg (DOT) com> wrote

An icon to c:\windows\system32\command.com.
An icon to c:\windows\system32\cmd.com.
An icon to c:\pdox45\startpdx.bat (normal batch file for starting
Paradox.exe with the usual suggested flags)
They all work fine until the random lockup later when running the
report.

which had some problem in it that prevented Paradox from running
(CANCEL/IGNORE). Without the pif files the message went away so this is no
longer a problem.


(1 to 200 or so). It may lock up on the first one or the last one or
actually complete with no problems. Eventually it always seems to lock up
(like when you're viewing the report on the screen at the end).

I'll try this and see if helps. Thank you. So Tutility is bad to trust for
verify but better for restructure than Modify/Restructure within the Paradox
program?

Rick Hoffman wrote:

the Verify option misses a lot of stuff that the Rebuild fixes.. if Verify says
it's bad, it is.. but if Verify says it's good, it might not be.. when in doubt,
Rebuild..

the Restructure option within Paradox does *not* repair tables..


--

Steve Green - Diamond Software Group, Inc - Waldorf Maryland USA
Corel CTech Paradox - http://www.diamondsg.com - Support/Downloads/Links
---------------------------------------------------------------------------------

Do you need a Sanity Check? http://www.diamondsg.com/sanity.htm
Upgrade/Downgrade versions? http://www.diamondsg.com/upgrade.htm
-------------------------------------------------------------------------