|
Post by herman on Jan 25, 2022 10:22:30 GMT 1
Jos, I was hesitant to report this, but still. A problem that I had on 12 januari this year. For the operating conditions: Windows 10 is completely updated Same issue again, but in a different combination and another program. There is a difference between Windows Explorer and Q.EXE (Dos editor) in vDos with the filenames and the active use from it. Unfortunately not reproducible again at the moment. In the printscreens in this report you see something strange again similar to the problem I reported here earlier. VDHTM.PRG is the copied file and RENAMED (the same as VDHTMXML.PRG) that is not exist for vDos There is a VDHTM~1.PRG with a DIR-command in vDos. In Q-edit there is no text in it and see him as a new file to make. Again to reproduced this: RENAMED to VDHMXXX.PRG als there also nothing in Q-edit, but only with notepad P.S. Unfortunately not visible to you now, no prtscrn made from the notepad edit from under the filename VDHTM.PRG. There was text in the file with notepad and not with Q-edit. Sorry for my bad English and difficult explanation.
|
|
|
Post by herman on Jan 25, 2022 10:24:41 GMT 1
And this one: Herman Attachments:
|
|
|
Post by Jos on Jan 25, 2022 11:13:05 GMT 1
Seems like Windows once created alternative short names (…~) for the files at renaming those to non-DOS 8.3. Renaming back to DOS 8.3 left those alternative short names intact.
What if you do a DIR *.prg /b at the Windows command prompt?
Eventually rename the files once more, open them in Notepad and save with the desired name. Or copy them to a drive without short name creation set (only C: by default has), and copy them back.
Jos
|
|
|
Post by herman on Jan 25, 2022 16:08:42 GMT 1
Jos,
Thanks you for your reply
By opening the text file in Windows Explorer, there was the correct info in the correct file name. The VDHTM~1.PRG file was there not visible or somthing like that.
At that moment it was only displayed incorrectly in vDos and therefore not in the Windows explorer and the text in Notepad
When and why it disappeared is a mystery to me, because I wasn't paying attention and was therefore surprised.
Unfortunately, this is also not easy to reproduce (which I tried) and so can't now be viewed in the Windows cmd-prompt
It seems that I have to wait for the weather to arise and then gather more information with it than I did so far.
For now I don't think it's a Windows problem because there was nothing wrong with the info there.
Herman
|
|
|
Post by Jos on Jan 25, 2022 18:05:15 GMT 1
You fixed it? I meant DIR *.prg /x, not /b. Generated short names don't appear in Windows Explorer, only the long file names.
Jos
|
|
|
Post by herman on Jan 25, 2022 21:50:14 GMT 1
Maybe I'm explaining it a bit unhappily. I don't know how else to say it. If you look at the first photo you will see the black part vDos files and in the Window Explorer in the left the same files; but there is a difference. Except for one That is not a long file name; thats not t issue. It's about VDHTM.PRG and can not open in vDos with Q-edit.
I didn't fix anything; It is automatic as far as I can remember after a few minutes.
What matters was no long filename.
The file you see with a dir in vDos is VDHT~1.PRG and is in Windows Explorer VDHTM.PRG for that moment when the issue there was for a longer time.
|
|
|
Post by Jos on Jan 25, 2022 22:35:45 GMT 1
Seems to be a Windows caching issue (not including/updating short names).
If you get it again (for a longer period), eventually copy the directory to a drive that doesn’t create alternative short names (probably any except C:). Rename the original directory, and copy it back from that other drive.
Jos
|
|