xBase++ having trouble finding files on startup, Win 64bit

[richardc]

I am having problems with my xBase++ application finding files on startup. This is only happening on a few machines out of 50. It seems to be doing this on Windows 7 Profession 64bit and Windows 10 - 64bit. On the Win7 machines, I replaced the 64bit OS with 32bit versions and that solved the problems. I have also noticed that when given the "cannot find file" error, if I say retry, then everything works as expected. Another symptom is on reboot, things work perfect for 2 or 3 times, then it errors. Rebooting starts over with 2 - 3 times OK and then errors again.

I have checked network communication and it is OK. I can plug the troubled machine in any port on the network that I know has no issues with running the app, and it still errors with file not found.

I added some code at startup that checks for the file using FExists(). I put it in a 10 iteration loop. It will always fail on loop 1, but on loop 2, it finds the file and continues with no errors.

This is really strange. Has anyone else experienced this problem?

Richard

[rdonnay]

Richard -

I recommend that you copy this message to Alaska Software.
Steffen Pirsig often has insights into these issues and may be able to help.

support@alaska-software.com

[bwolfsohn]

Doesn't find it 1st time but finds it later ??

Sounds like it might be related to ops locks...

[rdonnay]

Sounds like it might be related to ops locks...

If this is true, then a registry entry may fix it.

Look at the files in \exp20\samples\oplocks.

Another solution is to open all of the files and leave them open in another application.
Steffen gave us this solution in Phoenix a few years back.

[tcampbell_nc]

Richard,

You can probably eliminate the 64-bit vs 32-bit issue. I have this problem on 32-bit Windows 7, and 64-bit Windows 7.

[richardc]

I received a reply back from Alaska support:

Mr Covington,

Thank you for contacting Alaska Technical Support.

From your description I would assume the issue is not strictly related to Xbase++. First it is only 2 of many machines. Because the same code (and Xbase++ version) runs on all machines a defect or shortcoming with the Xbase++ runtime would show up more consistently.

Another very strong indication is that the low level file function FExists() shows this symptom. FExists() is tightly bound to the Windows File API functions. There is not much intelligence between the OS layer and the Xbase++ function. In case of inacurate behaviour of the OS layer there is little we can do about that.

Another indication is that when you have changed from 32 Bit to 64 Bit operating system the behaviour improved. Additional to that according your description only startup code is affected - a simple retry fixes the behaviour. Seems so that hardware some hardware (network card, chords,.....) or software (driver) is not ready on first attemp.

You might be able to identify common chipset and driver versions on the failing machines. Also pay some attention to network adapter settings.

As far as Xbase++ is related we have the option to trace filesystem access using the Process Monitor from SysInternals. The tool can be configured to trace system startup scenarios. At the end we will find a log entry that tells us that some file can not be found which is the root cause why FExists() fails with the same error.

I hope all this makes some sense.

with regards/mit besten Grüßen
Support


We love Xbase++, and you?
Alaska Software Inc.
European Office:
Phone: +49 (0)6196 - 77999951; Fax: +49 (0)6196 - 77999923
US Office:
Phone: +1 (646) 218 1280; Fax: +1 (646) 218 1281
http://www.alaska-software.com
nntp://news.alaska-software.com

[rdonnay]

We love Xbase++, and you?

So, Richard, it appears to be questionable whether they also love you.