|
Post by nitkot on Aug 21, 2018 7:29:55 GMT 1
Hi,
I have large ERP application for my business developed in Microsoft COBOL 2.0 compiler. Until now I was running the same in windows XP machines, but now I have to upgrade all system. On windows 10, I have tried using VDOS, but it does not allow to load ISAM of COBOL 2.0 in the memory. Loading ISAM is must to read the index data files created in MS COBOL 2.0 compiler. I am stuck now.
Can you help me with any other solution?
Thanks
Nitin
|
|
|
Post by Jos on Aug 21, 2018 9:31:33 GMT 1
What do you mean with “does not allow to load”. It is a TSR that exits without an error message?
Jos
|
|
|
Post by Jos on Aug 24, 2018 9:29:33 GMT 1
Although this is from MS Cobol 2.2, loading ISAM.EXE seems w/o problems. Jos
|
|
|
Post by nitkot on Sept 19, 2018 9:14:18 GMT 1
Hi Jos, Apology for delay in response. I am using COBOL 2.0 version. ISAM.EXE is required to be memory resident to refer to index files. When I try to load it is giving message as given in screen shot here. I think, It is all about changing the version of DOS in vDOS. I have to change to DOS 2.0 or 3.0. Which I can do in DOSBOX, but don't know how to do the same in vDOS. vDOS window is hanging after I try to load ISAM.EXE, I need to kill the process. Kindly help. Thanks in advance. Attachments:
|
|
|
Post by Jos on Sept 19, 2018 9:29:10 GMT 1
No option to change the reported DOS version. That would also be incorrect since it still remains DOS 5.0, not 2.0 or 3.0.
You could try attached MS-ISAM 2.41. If it’s backward compatible with your ISAM version and MSCobol doesn’t test for the exact version. Like ISAM.EXE should do with the DOS version: Is it at least version 2.0.
If it doesn’t work, submit your ISAM.EXE, I’ll patch it to work with vDos/DOS 2.0+.
Jos
|
|
|
Post by nitkot on Sept 19, 2018 15:09:59 GMT 1
Hi Jos, Thanks for your assistance. I dig further and found there is a way in config file to change the reported version. I provided DOSVER = 3.00, and voila, it worked well. ISAM could able to install properly. I will disturb you if there is any further assistance required. Thanks Nitin No option to change the reported DOS version. That would also be incorrect since it still remains DOS 5.0, not 2.0 or 3.0. You could try attached MS-ISAM 2.41. If it’s backward compatible with your ISAM version and MSCobol doesn’t test for the exact version. Like ISAM.EXE should do with the DOS version: Is it at least version 2.0. If it doesn’t work, submit your ISAM.EXE, I’ll patch it to work with vDos/DOS 2.0+. Jos
|
|
|
Post by Jos on Sept 19, 2018 21:59:59 GMT 1
“DOSVER=” is not a vDos config directive. That would be of vDosPlus. I don’t support vDosPlus, it’s just too infantile. So you can’t consult me for problems with that.
Jos
|
|