[Fwd: Nantucket Clipper 5.01 under Windows95 ???]
Jay Burrell
Path: nntp.msstate.edu!not-for-mail
From: Jay Burrell <jg...@Net.MsState.Edu>
Newsgroups: comp.databases.xbase.misc
Subject: Nantucket Clipper 5.01 under Windows95 ???
Date: Mon, 18 Aug 1997 14:33:44 -0700
Organization: Mississippi State University
Message-ID: <33F8BF...@Net.MsState.Edu>
Reply-To: jg...@Net.MsState.Edu
NNTP-Posting-Host: burrellpc.cc.msstate.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01Gold (WinNT; I)
CC: jg...@net.msstate.edu
Xref: nntp.msstate.edu comp.databases.xbase.misc:13517
I have an old legacy application written in Clipper 5.01 Rev 1.29
that has not been touched since August 1994, and I don't want
to turn back now!!! When I attempt to launch the application
I get the following error message:
EST0001: Illegal format in loadable file
Then it simply exits back to Windows95.
Does anyone have a clue what the issues are for running an
old Clipper app under 95 are? Is it possible?
Please send email if you can as I hardly have an opportunity
to read newgroups much any more!
Thanks in advance,
Jay Burrell jg...@Net.MsState.Edu
LAN Systems, Systems & Networks
Mississippi State University
Carl Zebooker
This is a multi-part message in MIME format.
--------------4614615C7EBA
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Jay Burrell wrote:
> I have an old legacy application written in Clipper 5.01 Rev 1.29
> that has not been touched since August 1994, and I don't want
> to turn back now!!! When I attempt to launch the application
How do you attempt to launch the appilcation?
> I get the following error message:
> EST0001: Illegal format in loadable file
> Then it simply exits back to Windows95.
This looks like a Win95 error. Have you consulted the knowledge base
for Win95 at microsoft.com? (not that it will be exceptionally
illuminating, but you never know)
> Does anyone have a clue what the issues are for running an
> old Clipper app under 95 are? Is it possible?
Please see attachment.
> Please send email if you can as I hardly have an opportunity
> to read newgroups much any more!
--
ca...@nowhere.bitxbit.com
^^^^^^^^
To send me e-mail, delete the "nowhere."
Notice:
------------------------------------------------------------------------
Usage of my email address for commercial purposes without my express
prior consent first had and obtained in writing costs US$ 50 per
message. By using this email address you agree to this condition.
Technical discussions of programming problems and solutions are not
"for commercial purposes" for the purpose of this Notice.
------------------------------------------------------------------------
And for you automated email spammers out there, here of the current
board of the Federal Communications C
Chairman Reed Hundt: rhu...@fcc.gov
Commissioner James Quello: jqu...@fcc.gov
Commissioner Susan Ness: sn...@fcc.gov
Commissioner Rachelle Chong: rch...@fcc.gov
And let's help you send some spam to the USPS, too:
cust...@email.usps.gov
--------------4614615C7EBA
Content-Type: text/plain; charset=us-ascii; name="win95.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="win95.txt"
Q: How do I run Clipper applications under Windows 95?
A: My experience doing so is with Clippr 5.01a applicatins linked as protected-mode executables using Blinker 3.3.
To begin with, understand that you are running the app in a "DOS Box." The better that DOS box simulates a DOS runtime environment, the fewer problems you will have.
Next thing to understand is that, under Win95, every 32-bit app gets its own work space, while 8- and 16-bi apps share a single work space. If you are (or your client is) running exactly one 8- or 16-bit app, that will not be a problem. If there are multiple 8- and/or 16-bit apps running on the machine in question, it is highly likelly that the Clipper app will get stomped for no apparent reason. In such a case, consider a move to Blinker 4, with all the latest patches.
When running a Clipper app linked with Blinker 3.3 under Win95, I take the following steps:
1) Create a batch file, say C:\MYAPP\MYAPP.BAT, which looks something like this:
@ECHO OFF
SET COMSPEC=C:\WINDOWS\COMMAND\COMMAND.COM
SET CLIPPER=<whatever>
C:
CD \MYAPP
MYAPP.EXE
PAUSE
EXIT
2) Create a shorcut with the folloing "Program" properties:
Cmd line: C:\WINDOWS\COMMAND\COMMAND.COM
Working: C:\MYAPP
Batch File: C:\MYAPP\MYAPP.BAT
Use that shortcut to run the application.
There are some other concerns, such as native Clipper features (INKEY(), ACHOICE(), MENU TO, etc.) which hog all the CPU time in a multi-threading environment, but I have not needed to address them. Phil Barnett is coordinating work on this topic.
2nd Windows 95 issue:
In a post of <16 Aug 1997> on comp.lang.clipper, "Victor" wrote:
We have been having problems with our application where the clipper program opens a DBF table with its compund CDX index in shared mode. Then when doing FLOCK(), it returns FALSE. Even though they are the only users that have this particular table (DBF) open.
They were running Windows 95 with Netware directory services, now they are running command prompt only with VLM's. This problem is not affecting other customers with the same version of the software. Machines are Compaq & Server is Novell 4.11. It appears that problem did not happen until more users were allowed into the system, and also they have an NT Citrix machine for remote users to login (T1 line).
Has anyone had problems when trying to obtain locks after a certain period of time? It seems to be fine for about an hour of processing, after that point the problem appears. We can ALT+C out of the app, then try the same operation and it is fine. IS manager has been modifying and applying patches to server, but no difference. We thought it may have been that utilization was high. Now it has been reduced and still same problem.
Reply by Phil Barnett:
I suspect that this is your problem. Does this computer have FAT32 partitions? If so, it is OSR2.
Bill has stuck it in us again.
I have no idea what the solution is.
Reply by Terry Carmen:
OSR2 with FAT-32 is a horrible kludge.
It allows using large disks by allocating amazingly huge clusters, and has no locking for anything running in a DOS window.
The only two suggestions I have are:
[1] backup the disk, reformat it and install WIn 95 with standard FAT support.
or
[2] Try it with the Clipper database is on a Netware server machine, since the original DOS locks are probably still supported by the network redirector.
--------------4614615C7EBA--