|
|
Post by rickmontreal on Jun 2, 2020 22:05:02 GMT 1
A recent update to the latest version of vDos is causing my Clipper program to crash.
At first, I thought it might be something else, so I reindexed all the files and things worked for a few weeks. Now it is crashing again and I cannot reindex one particular file. It is the biggest file by far (740,000 records and 47M in size) I tried rebooting and have just vDos start and try to reindex just the one file. It will always crash
Most of the time I get the description Illegal CPU opcode 109 at 0184:2435
sometimes I get the desc IRET: Illegal descriptor type 123
When I moved my client to 64bit Windows, I started with an older vDos, then moved to vDosPlus. When I learned vDosPlus won't be maintained, I found the newer vDos (2020-03-01) and switched back.
Strange, but if I switch back to vDosPlus (Edward build from 2018) everything works perfectly. The index doesn't crash.
What do people suggest for a network (file/record locking) app? vDos (which version) or vDosPlus?
Thanks
|
|
|
|
Post by Jos on Jun 2, 2020 22:28:26 GMT 1
Clipper is notorious to cause problems, especially when using third-party libraries.
If vDosPlus 2017 (still) works, vDos 2017 should of course also do.
Generally, best is to use the latest version. For instance the emulated CPU of 2020 is twice as fast than that of 2017, while other issues will be resolved and new functionality added.
No idea why vDos 2020 would cause a problem with your big file. I would need some test environment of you to have a look.
Jos
|
|
|
|
Post by rickmontreal on Jun 3, 2020 14:15:07 GMT 1
Hi Jos,
3rd party...
t convert to six driver indexes. This apps uses plain NTX files.
For the moment, I reverted to vDos 2019 as the client has a lot of work and needs a stable version.
I didn't realize the 2020 version was much faster. I'll test it out on my own PC as I have both version of vDos as well as vDosPlus.
Latest version...
I agree. I usually wait a few weeks (or months) for the inevitable .01 version to patch the new release.
I'll see if I can isolate the reindex code and maybe post the DBF somewhere. I'll have to do more testing, but I blew most of yesterday getting them going and I have to catch up with regular work.
What is your opinion on vDosPlus? That seems to work perfectly. I'm not sure if I should use vDos 2019 or vDosPlus 2018 until I figure out why vDos 2020 isn't working properly.
|
|
|
|
Post by Jos on Jun 3, 2020 14:34:33 GMT 1
vDosPlus 2018 doesn’t exist, the latest version (2017…) is based on vDos 2017.08.01.
You would have found one or more vDosPlus additions useful. So you then also have to stick with vDosPlus since those additions won’t make it to vDos.
Jos
|
|
|
|
Post by rickmontreal on Jun 3, 2020 18:33:31 GMT 1
Sorry for the confusion, I meant vDosPlus with the additions from "Edward Mendelson's customized vDosPlus build page", that has 2018 in the filename (vDosPlus-201708-Ed2018.zip)
I was using the plain vDosPlus2017 before switching to vDos2018 and then vDos2019 and things were fine.
When I recently upgraded to vDos 2020, I started to have problems. I visited vDosPlus and tried the latest vDosPlus and it worked (as did the previous vDos2019), I knew the problem was vDos2020.
I'm not really using any additions or customization. All my apps are Clipper 5.x networked accounting, so I need something reliable.
What would you suggest?
vDos 2019
vDosPlus 2017
vDos 2020
|
|
|
|
Post by Jos on Jun 3, 2020 20:09:04 GMT 1
The newer, the better. You can have a look at www.vdos.info/download.html what 2020 brings. Besides the apparently bug with reindexing your big file. That will probably be prolonged in next versions if not dealt with. Jos |
|
|
|
Post by rickmontreal on Jun 9, 2020 13:56:15 GMT 1
Hi Jos. I agree with you that newer is better, but I never update right away, I give it a few weeks to a month before putting the latest into production. I think of all brand new releases as 'Gamma versions'  Downgrading to 2019 seems to have stabilized my client. Once I catch up a bit and hopefully things will slow during the summer, I should have time to investigate the vDos2020 indexing problem. I will post my findings here. I was wondering if there might be something strange like DBF corruption that might cause the problem. Is there a good diagnostic tools to check integrity of DBF files? I could also test recreating the file with something like. use badfile copy to goodfile use goodfile index on <key> to <ntx> Thanks for all your help! Richard |
|
