|
Post by balmydrizzle on Sept 23, 2022 3:11:17 GMT 1
I happen to got two versions. When run 2020.03.01 under win10 64-bit, it can run correctly and show a vdos window. However, when run 2022.05.01, it doesn't show any window but the vdos process is indeed in task window list. Very interesting bug, I presume.
|
|
|
Post by Jos on Sept 23, 2022 7:54:16 GMT 1
You certainly are not the only one using Windows 10 64-bit, the vDos window not showing is strange.
Could you start vDos with the log option (….\vDos.exe /log) and post the generated vDos.log file. Perhaps that will show what’s going on.
Jos
|
|
|
Post by micros on Sept 29, 2022 21:59:48 GMT 1
Hello!
I have the same situation with the 2022 version. It does not open under either Win10Pro or Win11Pro, and the content of the log is only this: vDos 05.01.2022 CodePage: 852
The explanation might be that the Windows system is not an English language version (Hungarian), but that might be a bad idea.
Fortunately, the 2021 version runs without problems.
|
|
|
Post by Jos on Sept 30, 2022 7:49:32 GMT 1
The codepage seems not related, mine is for instance 850.
You also get vDos.exe listed in the Task Manager?
What happens if you start config.txt with some bogus option, like SHOWTHIS = ON?
Jos
|
|
|
Post by atis on Dec 1, 2022 10:06:42 GMT 1
If i put invalid option like SHOWTHIS = ON , program said no valid options. Log show only the above that people said (vDos 2022.05.01, CodePage: 852 ). Tested Windows 10 pro 32bit , 64bit, windows server 2016. Any idea how to run the program (2022.05 version)?
|
|
|
Post by Jos on Dec 1, 2022 10:19:57 GMT 1
The log should only show vDos 2022.05.01, no CodePage: 852.
What if you remove SHOWTHIS = ON from config.txt, and start autoexec.txt with PAUSE?
Jos
|
|
|
Post by atis on Dec 1, 2022 11:33:55 GMT 1
I realized the problem, The windows that i tried to run vDos all is hungarian language default, when i try to run in an english windows the vDos start without problem, but not on hungarian windows version...
|
|
|
Post by atis on Dec 1, 2022 11:38:41 GMT 1
if i put pause on the first line in the autoexec, simply nothing happens and the log show vDos 2022.05.01, CodePage: 852
|
|
|
Post by Jos on Dec 1, 2022 14:15:57 GMT 1
Strange, I tested with codepage 852. No problems.
Only to narrow down where vDos seemingly stalls or quits: Add the line IDLELOW=12345 to config.txt, and see if the log contains IDLELOW set at 12345.
Jos
|
|
|
Post by atis on Dec 1, 2022 17:17:07 GMT 1
yes it's in: vDos 2022.05.01 CodePage: 852 IDLELOW set at 12345
but vDos doesnt start
|
|
|
Post by Jos on Dec 1, 2022 19:24:48 GMT 1
It just was the last possible log entry to see how far vDos got.
I first thought vDos wouldn’t show its window because balmydrizzle reported vDos.exe was listed in the Task Manager. But then you would have more entries in the log, not stopping at Codepage: or IDLELOW.
So instead vDos would end up in some loop, though no idea where/why. I’ll send you a vDos.exe by wetransfer.com, that logs more initialization steps. So that should at least reveal where vDos is hold up.
Jos
|
|
|
Post by atis on Dec 1, 2022 19:32:44 GMT 1
Log: vDos 2022.xx.xx TUI_Init CodePage: 852 IDLELOW set at 12345 IO_Init MEM_Init CALLBACK_Init PIC_Init PROGRAMS_Init TIMER_Init VGA_Init CPU_Init FPU_Init KEYBOARD_Init BIOS_Init INT10_Init MOUSE_Init SERIAL_Init PARALLEL_Init DOS_Init
|
|
|
Post by atis on Dec 1, 2022 19:34:51 GMT 1
and i didnt seeing vDos in the task manager
|
|
|
Post by Jos on Dec 1, 2022 20:32:27 GMT 1
Did you perhaps start vDos.exe from some file manager, it would then be grouped by that.
DOS_Init is the offending routine. I'll send you a second vDos.exe that will log the routines in that.
Jos
|
|
|
Post by atis on Dec 1, 2022 20:56:27 GMT 1
Log: vDos 2022.xx.xx CodePage: 852 IDLELOW set at 12345 DOS_Init CALLBACK_Install DOS_SetupDevices DOS_SetupTables You are right, when i try to start it from desktop i see it for 2-3 sec then vDos dissappear from running process
Windows event log:
Exception code: 0xc0000005 Error position: 0x000bd2f0
|
|