|
Post by iamuser3443 on Aug 28, 2023 17:01:08 GMT 1
Hello,
new pc in august 2023: Win11 64bit: if I start old-erp.exe via vDOS I see only a
blinking cursor in the black DOS field.
Win10 64bit TEST PC : it is working Win10 64bit upgraded to Win11 64bit it is working (old original pc)
QUESTION: do you think there are big differents between win10 and win11 ?
What could be the cause?
Right clic start as administrator = same problem:
Right clic compatibility mode = XP = same problem
|
|
|
Post by Jos on Aug 28, 2023 17:13:23 GMT 1
So far there are no reports vDos behaving differently in Windows 7 up to and including 11, 32 or 64 bit.
vDos doesn’t display a blinking cursor (never made anything blinking). Look in Task Manager what is actually running.
Jos
|
|
|
Post by iamuser3443 on Aug 28, 2023 18:40:55 GMT 1
Hello Jos,
thx!
Test Procedure :
on windows > win11-pc has mounted K: to \\server\data start doubleclic vdos use k: \\server\data k: cd dosprog dir name-of-the-owner folder missing (folders with more that 8 letters are missing?) renamed to the folder owner dir now owner foldervisible cd owner start.bat black windows is opening but closing in one sec
Test2: windows: rightclic start.bat (start a administrator) back to vDOS start.bat File faksjsys.ovl is missing, system-path: K:\data\dosprog\owner\system (but the file is there)
|
|
|
Post by Jos on Aug 28, 2023 19:11:59 GMT 1
vDos only shows 8.3 file and folder names (SFN). If a LFN, for instance “LONGFI~1.TXT” will be shown. It doesn’t generate/compose a SFN for a LFN, that is the responsibility of the OS managing the drive. So it seems the server doesn’t. If Windows: SFN's are by default only generated for the boot drive (C):. You have to enable that by fsutil for other drives. I don’t know what start.bat is about. But vDos.exe by default will not run with elevated right (Run as administrator). It will then show this message: Jos
|
|
|
Post by iamuser3443 on Aug 28, 2023 19:35:43 GMT 1
no LFN´s visibile
>If Windows: SFN's are by default only generated for the boot drive (C):. You have to enable that by fsutil for other drives.
ok, fsutil on the windows 11 client needed I assume.
Windows 2022 K:\data\dosprog Win11 Client K:\data\dosprog << mounted from the server
|
|
|
Post by Jos on Aug 28, 2023 20:21:36 GMT 1
fsutil has to be run at the OS managing the drive, so the server.
Creating a SFN involves some work for the OS: It has to ensure the generated SFN is unique, while there can be many LFN’s with the same (case insensitive) first characters.
If only a few file or directory names, just rename those to a SFN.
Jos
|
|
|
Post by Jos on Aug 29, 2023 9:46:50 GMT 1
LOL, the program turned out to be a Windows 32-bit CLI program. It looks like DOS, but isn’t.
So vDos isn’t needed, moreover starting it inside vDos just caused a Windows CMD window to open. Though with incorrect Windows drive/path assignments.
Jos
|
|