|
Post by herman on Oct 4, 2020 20:11:51 GMT 1
vDos probleem juiste prg file gebruik na het er overheen copieren van oudere prg files in Windows 10 Het huidige probleem is gerelateerd ook aan een vorige melding in topic: dBase5 for DOS error in vDos Versie 01-03-2020Jos, Ik heb een probleem getraceerd, door een melding van een variabele niet gevonden als onterechte melding omdat die variabele niet kon bestaan in de oudere prg versie. Door de oudere files weer over de nieuwere heen te kopieren zag ik dat dus. Ook zag ik het pas veel later aan het geprojecteerde versie nummer in mijn hoofdmenu, dat het maar aldoor dezelfde versie was, waar ik in werkte. De bestandsnamen in deze zijn niet gewijzigd t.o.v. de oudere. In de bijlage een log bestand en foutmeldingen.mijn Engels is niet zo sterk; vandaar NL en Google ENG vertaald hieronder. vDos problem correct prg file use after copying older prg files over it in Windows 10 The current problem is related also to a previous reportin topic: dBase5 for DOS error in vDos Version 01-03-2020Hello Jos, I tracked down a problem by stating a variable not found as an incorrect message because that variable could not exist in the older prg version. I saw that by copying the older files over the newer ones. I also saw it much later on the projected version number in my main menu, that it was the same version I was working in all the time. The file names in this one have not been changed from the older ones. In the attachment a log file and error messages.
Herman Attachments:vDos.log (14.85 KB)
|
|
|
Post by Jos on Oct 4, 2020 20:46:41 GMT 1
You have to help me out: It seems you’re running in NTVDM.
vDos won’t report 1023932928 bytes free on any drive. No (external) COMMAND.COM, so nothing to load. The memory summary shows amounts vDos doesn’t supply…
Jos
|
|
|
Post by herman on Oct 4, 2020 22:56:09 GMT 1
Sorry wrong pictures uploaded they are from other errors in NTVDMHow I can upload a right one (white only a dbase error from a not existing var) and another error from dBase
I don't see with this replay how I can added him.Here are the correct files Attachments:vDos.log (14.85 KB)
|
|
|
Post by herman on Oct 4, 2020 22:59:56 GMT 1
Many errors are driving me crazy, so I mixed someone.
It likes with this error that vDos not refresh his memory alocation table, If the filenames are the same, but from a different version.
It seems with this error that vDos cannot reload the files from the memory allocation table, if the filenames are the same, but from a different version
There are no problems in NTVDM with te same actions.
|
|
|
Post by Jos on Oct 4, 2020 23:08:41 GMT 1
I can’t do much with that, especially since your problematic example was with NTVDM.
Could you replicate that in vDos, submit a screenshot, dBase and the vDos log file (…vDos.exe /log).
Jos
|
|
|
Post by herman on Oct 5, 2020 7:05:54 GMT 1
I have little or no experience with proboards to correct problems, but I have now done it; see the corrections
Sorry about that
|
|
|
Post by Jos on Oct 5, 2020 8:07:38 GMT 1
Sorry, still don’t really understand the issue. That GENMENU.PRG program is replaced by a newer version, but vDos still loads the older version even while it’s no longer available?
Jos
|
|
|
Post by herman on Oct 5, 2020 10:42:07 GMT 1
Is replaced with an older one were the variable m_arch2 not exist (the older were in the variable not exist is copyed over the newer, were the variable m_arch2 exist)
|
|
|
Post by Jos on Oct 5, 2020 11:24:57 GMT 1
GENMENU.PRG is changed, but vDos loads the previous version that shouldn’t be present at all? Are you sure GENMENU.PRG is loaded from the correct location, not some directory containing the old version?
Jos
|
|
|
Post by herman on Oct 5, 2020 14:15:43 GMT 1
I'm shure'; I always copy the version from a different location when I needed to be changing. The workmap is always the same (C:\GENEALOG)
Version in NTVDM can not directly reach for vDos in Windows 10 x64; thats in Hyper V Windows 7 x86 there is no Network to be directly reach for that
Mayby an isue: The name of the vDos workmap is C:\vDos_01-03-2020 ?
|
|
|
Post by Jos on Oct 5, 2020 15:21:13 GMT 1
The directory name of vDos.exe is of no concern.
Make sure you have only one DOS drive letter assigned in autoexec.txt. Then search that Windows directory for all GENMENU.PRG file occurrences. Should be the changed one only, I guess there’s at least one more (the old one).
Jos
|
|
|
Post by herman on Oct 5, 2020 19:17:41 GMT 1
I just did a similar action from version 955 to 956 (see the print screen) So dBase is in C:\DBASE\DBASE.EXE Initially started with: vDos.exe clicked CD GENEALOG C:\dbase\dbase genmenu Copied new prgs to C: \ GENEALOG from _DAT_TMP \ __ TESTEN_NewGENv956_0310 and restart it with C:\dbase\dbase genmenu in autoexec.txt: USE C: C:\ USE D: D:\ On D:\ is no GENMENU.PRG Attachments:
|
|
|
Post by herman on Oct 5, 2020 19:32:11 GMT 1
IF I start the compiled program GENEALOG.EXE then it is the correct version
These are in the same locations as the prg's
|
|
|
Post by Jos on Oct 5, 2020 19:52:59 GMT 1
At the vDos command prompt in GENEALOG, could you do a DIR genmenu.prg before and after the copy?
Jos
|
|
|
Post by herman on Oct 5, 2020 20:06:55 GMT 1
I did on both ways Attachments:
|
|