Easy to Create, Easy to Change - Easy to use!


Stretching the limits? DataEase for Dos v5.16 on Windows 7 32bit


Started by Wendy Parker
Search
You will need to Sign In to be able to add or comment on the forum!

Stretching the limits? DataEase for Dos v5.16 on Windows 7 32bit

Hi, I do realise I am stretching the limits here. I am running a vintage DataEase for Dos app on v5.16 which has run very successfully on WinXP. However, since upgrading some workstations to Win7, am having frequent crashes and "index inconsistent" errors - Unfortunately users not always noting exactly what happened and not interested in exact error messages, so tricky.  Recently discovered one user getting BlueScreenofDeath with "APC_Index_Mismatch" error or "Bad_Pool_Caller" error. Tried altering \windows\system32\Config.nt to files=200 (rather than 40), but still getting same error.  Error always seems to happen when they press F2 to save or F8 to modify. The app does have sub-forms and I wondered if this might be the problem?

I have seen suggested to try running in XP compatibility mode, but when I have tried that, cannot get DataEase to run at all!

Any suggestions would be very welcome else my M$-pushing colleagues are going to get their way! :-(

Many thanks

Wendy

Written by Wendy Parker 09/05/13 at 11:37:15

Re:Stretching the limits? DataEase for Dos v5.16 on Windows 7 32bit

Hi Wendy.

You have stretched the limit as far as it will go (almost...;-) as Windows 7 x32 is as far as we know the furthest you can go with DFD.

However it shouldn't work any worse in Windows 7 x32 than it do in XP so the problem is not Windows 7 x32 itself.

From what you tell us, I gather this is a network setup and that is most likely the culprit. The Network handling in DataEase for DOS is ancient and as file based database like this is no longer the order of the day the network support in "modern" operating systems have changed.

Most file servers these days focus on serving documents etc instead of data and to help along with that the suppliers set up multi-user functionality of their own like caching, document locking etc.

The problem with this is that DataEase share files very intensively and need them to be current (not cached) and not locked by other users other than the locking DataEase itself perform.

Depending on what server you are running there is different solutions.

1. Did you upgrade the server at the same time as upgrading the workstations? If so, the culprit is most likely the server itself.
if so. What server are you running? If it is a Windows 2003 or 2008 server it most like are settings on the server for caching etc you need to disable. If you search in our news section for Windows 2003 or 2008 you will find some articles on this.

2. If the server is the same, then the problem is on your workstation.
Then you most likely run a Novell server. Problem with Novell is that they stopped supporting record locking etc after client version 4.x something, so you will need to downgrade your novell drivers to 4.6x.



Written by DataEase Support 09/05/13 at 12:24:04 LegEasy DOS